Jump to content


  • Posts

  • Joined

  • Last visited


0 Neutral
  1. Jeddy, FAR 15.101-2(b)(1) states, in part: I would make completion of the pricing table an evaluation factor and state award will not be considered if the pricing table is not completely filled out, unless you are willing to entertain discussions. Curiously, I presume you are making a single award. If so, I would also include in Section M that only the lowest priced proposal will be evaluated and if determined acceptable will be awarded the contract and no further proposals will be evaluated. If you plan on awarding multiple contracts based on some range of lowest priced proposals, I would state the same.
  2. Sorry for the delayed response. I was prepping for the Marine Corps Marathon. Here's what I initially sent apsofacto: "I don't think anything is wrong with the sentence as written. The word 'which' is used as a pronoun, indicating a relationship between the red tag and the engines. Therefore, logic would dictate that only engines with a red tag are to be removed and rebuilt. Perhaps to be more clear, I would suggest the following revision: The Contractor shall only remove and rebuild engines marked with a red tag." After reading Vern's comments, I concur that the sentence is in fact misleading and one could interpret the instructions as indicating all engines have a red tag. The bottom line from this exercise, be careful when drafting a document as contra proferentem will dictate in most cases.
  3. Rye, Did your employer or did the Government provide you with the Performance Improvement Plan? If the Government did, is this a personal or non-personal services contract?
  4. Culham, Where does it state in FAR Paragraph 8.404(a) that the use of LPTA is strictly prohibited?
  5. The passage you quoted states "Any order issued during the effective period of this contract and not completed within that period shall be completed by the Contractor within the time specified in the order." I agree that if the base period or option period is issued during the effective period of the contract then the contractor can continue performing until said period ends, even after the contract period of performance expires. However, if the contract's period of performance expired no new options can be exercised.
  6. It is my understanding that when an IDIQ is awarded the government does not know the exact amount of goods or services it requires nor when it will need them. When a specific bona fide need arises, the government will issue an order under the IDIQ's scope, terms and conditions. If the order itself is indefinite in quantity or delivery, what then was ordered? The FAR defines a delivery order as "an order for supplies placed against an established contract or with Government sources" and a task order as "an order for services placed against an established contract or with Government sources." If the order itself is open-ended, did the government really order something?
  7. Vern/Fizzy, Yes, the award is acting like a BPA (I understand that you cannot award an IDIQ against an IDIQ). I do not know the dollar amount, but if it did exceed $103 million I can see where this is an issue because it could run afoul of 8.405-3(a)(3)(ii). Assuming it is less than $103 million, there is no legal issue in having a task order act like a "mini-IDIQ" when the intent of a task order is to have the contractor perform a specific task(s)?
  8. Good Morning, I overheard a KO state that he awarded a competitively procured T&M task order under a GSA FSS contract. Each POP has an estimated NTE and the government sends the contractor specific projects and tasks that it needs to submit a FFP for before proceeding. If the government accepts the FFP it fully funds the project while at the same time technically incrementally funding the overall total estimated NTE of the task order. I am assuming that there is a minimum guarantee in the task order to make it legally binding but I am not sure. Nonetheless, I was curious what others think of this practice. In theory it reduces the government's risk by requiring the contractor to perform work under FFP once specific projects/information is known. It also reduces the overall PALT by not having to procure the service using FAR Part 15 procedures (assuming that the work fits under the scope of the FSS contract). When the task order was procured, I am assuming that the government could not provide enough specifics for contractors to provide FFP across the board. I plan on following up with the KO but wanted to start a discussion on this and see what issues/ideas come from it. Prezmil2020
  9. From the VA Handbook 6500.6: "d. Custom software development and outsourced operations must be located in the U.S. to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the contractor/subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor." Does anyone know of any federal policies or VA policy/mandates that would prohibit software development OCONUS? Thanks, Prezmil2020
  10. RJH46, I would explain to the KO that he/she still has the ability to invoke -9 via a bilateral modification. Since the government failed to provide you of its intent to extend at least sixty days the government can no longer unilaterally exercise the option. However, this does not mean that the two parties cannot agree via a bilateral modification to exercise the option.
  11. I've always had a problem with the FSS contracts in so far that when the solicitation is amended, the contracts are mass modified to reflect the deleted, added and changed clauses. However, the solicitation and resultant mass modification happens every so often; therefore, the contracts tend to lag behind the current FAR. With that said, wouldn't it behoove the OCO to review the current solicitation and contract and add the current FAR clauses into it even if that means adding the current 52.212-4 in the task order solicitation? Also, there are times when the FSS contract does not contain every clause that is applicable to the OCO's procurement (data rights, options, DFARs, etc.).
  12. Let's assume that 52.217-8 does flow down to individual task orders. Since the task order solicitation was absent on how each offeror was to price the possible 6 months but did require offerors to propose on the two one-year option periods, could one conclude that the offerors received equitable treatment in the evaluation of their offers as each offeror should have considered the possibility of 52.217-8 being invoked some time in the future as it is in their respective FSS contracts?
  13. Vern, That's a good point. Even though 52.217-8 flows down to the task order, it is the OCO's responsibility to consider it during evaluations and ultimate award, exercising it appropriately in the future. In this particular case, just because 52.217-8 flowed down the OCO didn't take it into consideration at time of evaluations because there was no language in the task order solicitation requesting offerors to submit pricing for those six months and that offers would be evaluated inclusive of that clause. The only language in the task order solicitation was that the offers were evaluated inclusive of the base period and two one-year option periods.
  14. Although the clause was incorporated into the task order, it was done so after offers were evaluated and an award made. Executing the clause doesn't take away the fact that this, in my opinion, constitutes a sole source modification because none of the other offerors were given an opportunity to provide pricing and be considered at time of evaluation and award. I am referencing the task order solicitation, not the parent FSS contract solicitation. However, you raise a good point with regards to 52.217-8 being included in the FSS contract, which it is. The FSS contract contains 52.216-18 ORDERING (OCT 1995) (DEVIATION II -- FEB 2007), which states "( All delivery orders or task orders are subject to the terms and conditions of this contract. In the event of conflict between a delivery order or task order and this contract, the contract shall control." Therefore, the task order would be subject to 52.217-8 as it is included in the FSS contract. I would presume that one could argue that since 52.217-8 is included in the FSS contract all contractors understand that this clause flows down to their respective task orders and may be unilaterally exercised by the task order Contracting Officers (OCO). Since task orders are viewed as contracts, 52.217-8 could be exercised for this task order independently from the FSS contract even if the FSS contract was extended using 52.217-8. That being said, the OCO didn't need to bilaterally modify the task order including 52.217-8 as it was already included in the task order due to it flowing down from the FSS contract. Have I correctly interpreted your post?
  • Create New...