Skip to content
View in the app

A better way to browse. Learn more.

The Wifcon Forums and Blogs - 27 Years Online

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

GeoJeff

Members
  • Joined

  • Last visited

  1. Thanks for the book recommendation, Vern: (The AI Prompt Playbook: Master AI Prompt Engineering with 140 Ready-to-Use Templates for ChatGPT, Claude, Gemini & Copilot (2026), by James Caldwell.) My copy will be here in two days.
  2. I researched this at great length back in 2020/2021. I believe it began with a couple of individual deviations in ~2006, which turned into a class deviation, which turned into GSAR 536.71 ~2020. We concluded we (different civilian agency) didn't have the regulatory authority to do it without a deviation at the time. We ended up doing something similar that approximated firm fixed price by establishing a ceiling price to construct at ~35% design and having a shared savings incentive if the contractor was able to beat that price once design was finalized. One of the first things I thought of when RFO 16 was published was that we would no longer need a deviation if we wanted to try a true CMAR out. But, now I would have to justify an other than FFP contract to the agency head, and anything worth doing as CMAR would almost certainly exceed $10M, so would require Secretarial approval on top of the million other things that need to be approved.
  3. I see this change as actually having moved in the opposite direction than the OP's point of view; to wit, I think it has become more restrictive. 13.004(b) used to say "...preferably in writing." Preferably does not mean mandatory. 12.201-1(b) now says "...either by written acceptance of the purchase order or substantial performance..." "In writing" means "...any worded or numbered expression that can be read, reproduced, and later communicated, and includes electronically transmitted and stored information," which clearly includes an email. No more phone calls that say "Thanks for the PO, we'll get right on that!" The most relevant case I could find on the topic was B-416601, in which I think the GAO made something up out of thin air. They wrote in part: Rather, in the context of an RFQ, it is the government’s purchase order which represents an offer that the vendor may accept through performance or by a formal acceptance document. Id.; FAR § 13.004(a), (b). A "formal acceptance document" was never required by FAR and is not/was not defined. Dehler Manufacturing Company, Inc. | U.S. GAO Especially if all correspondence has been electronic, I think it's quite clear that a reply email as the OP received is acceptance and he has a termination for cause on his hands. I'd be interested to see what would happen if he did that, and the vendor tried to challenge that they never "accepted" anything in the first place.
  4. At the MATOC level, one could ask for: Direct labor rates (fully loaded) for any in-house labor Materials markup for any materials purchased directly by the prime contractor Markup on subcontractors Markup on other direct costs Profit rate Task order proposed fixed prices would be built under those parameters. So would requests for equitable adjustments. You could also ask for bond premium percentages, which I've seen vary between as low as 0.555% and 3%. Also, great commentary above that if a sample task is priced, it is best if it is real and someone will actually have to do it for the proposed price. It keeps the sample task pricing from being totally fictitious.
  5. Vern wrote: "Don has studied the RFO deeply, and the point of his questions was to try to show that the RFO did not really change much of substance. Like previous acquisition reforms it's mostly noise, "a disturbance, especially a random and persistent disturbance, that obscures or reduces the clarity of a signal." I agree with that, although I note the RFO 12.102(a) "...only one source is available..." vice the legacy "...reasonably available..." seems significant, as does the explicit construction as a commercial service business (which I think is silly). Jamaal commented on agencies using FAR and RFO simultaneously. That's really ridiculous and disruptive. RFO Part 12 was issued 08/14/2025 and some agencies still have not deviated. Why not?
  6. That's fascinating, I hadn't realized. I'm with DOI and they have been slow-walking deviations, but they have still issued a few. The Executive Order was dated April 15 and called for results within 180 days, which would have been October 15. RFO model deviations were done by September 30, with Part 2 and 52 done October 28 and version 2 of the Companion Guide dated October 30. I wonder what's going on behind closed doors with DoD/DoW having issued zero deviations? DFARS obviously complicates their compliance, but still.
  7. I think we can ignore GAO's findings, don't you? After all, GAO shouldn't exist. Russ Vought says Government Accountability Office ‘shouldn’t exist’
  8. Vern, I remember that! That language about "routine painting or carpeting..." is mirrored exactly at GSAM 512.203(c): (bold added) (c) Contracting for Construction. The provisions and clauses in FAR 36 and GSAM part 536 address the fundamental aspects of construction contracting. FAR 36 and GSAM part 536 apply well-established commercial principles that are designed to result in an equitable distribution of risk between the Government and its contractors. The contracting officer should consider the following when contemplating a construction acquisition as a commercial purchase— (1) FAR 12, as currently promulgated, should rarely be used for new construction acquisitions or non-routine alteration and repair services. (2) FAR 12 and GSAM part 512 may be used in limited circumstances involving construction contracting, primarily for routine alteration and repair services as well as for the acquisition of commercial construction materials and associated ancillary services. It may be appropriate to use FAR 12 and GSAM part 512 for routine projects such as painting or carpeting, simple hanging of drywall, everyday electrical or plumbing work, and similar noncomplex services, as well as for purchases of commercial construction material and associated ancillary services. (3) Whether a construction acquisition is conducted under FAR 36 or FAR 12, the contracting officer must adhere to the policies of FAR Subpart 22.4. This subpart addresses labor standards for contracts involving construction. Prior to making the determination that a construction acquisition can be conducted as a commercial purchase, the contracting officer should conduct appropriate market research in accordance with FAR 10 and GSAM part 510. (4) Construction contracts in excess of $2,000 must include an applicable Construction Wage Rate Requirements statute wage determination found under the System for Award Management Wage Determinations at https://www.sam.gov. If the construction contract is greater than $30,000, then the SF 1442 should be used in lieu of the SF 1449 and the bonds or alternate payment protection provisions of FAR 28.102-1, 28.102-2 and 28.102-3 apply. (5) Construction contracts awarded as commercial acquisitions should not exceed the prospectus threshold. The prospectus threshold as referenced in section 102-73.35 of the Federal Management Regulation (FMR) is posted at https://www.gsa.gov/annualprospectusthreshold I think that also tracks with the FAR definition of commercial services needing to have "established catalog or market prices." Painting, carpeting, drywall, concrete, asphalt...these are all things that have a market, unit price like per square foot or per cubic yard. Building a new office building, not so much.
  9. AIA A201 is entitled "General Conditions for the Contract of Construction." Section 7 talks about changes, and, to my reading, is actually very similar to the traditional 52.243-4 or -5 arrangement. The "Owner" can issue a "Construction Change Directive" within the general scope of the contract in advance of a mutually agreed upon price impact and the contractor has to perform. There are procedures laid out for how to resolve the dispute, blah blah blah. VERY different than the "mutual agreement of the parties" language at 52.212-4. Sample AIA document here: AIA Document A201-2017 - Sample
  10. 52.212-4 can be tailored except as limited by RFO 12.205(b)(1)(ii). As an example, that says you cannot tailor the payment paragraph. So, how do you deal with the inherent conflicts between the commercial payment paragraph and 52.232-5? What about the huge difference in changes? Would you suggest just tailoring RFO 52.212-4(d) changes so that it looks like 52.243-4 or -5?
  11. RFO Part 2 now explicitly defines (at least some) construction as a commercial service. Link to RFO Part 2: FAR Overhaul - Part 2 | Acquisition.GOV Text in question: (2) Services, including construction, of a type offered and sold competitively in substantial quantities in the commercial marketplace based on established catalog or market prices for specific tasks performed or specific outcomes to be achieved and under standard commercial terms and conditions... (blah blah blah). Setting aside the question of how one might decide which types of projects are commercial and which are not (and I have my ideas about that), it seems there are some fundamental and perhaps irreconcilable differences in standard commercial terms and conditions and federal construction terms and conditions. Changes come immediately to mind. Any thoughts on how the powers that be are going to unscramble this egg, or is this just going to be a regulatory free-for-all while everyone behaves differently?
  12. In Part 43, they deleted 43.000(a), writing "FAR part 43 now applies to contract modifications for orders for supplies or services not otherwise changing the terms of contracts or agreements (e.g., delivery orders under indefinite delivery contracts). This aligns the FAR to practice." That explanation doesn't make sense to me. A delivery order is not a modification. The revised text makes sense, because I always sort of read it as "well, of course that doesn't apply because a delivery order is not a modification." Thoughts?
  13. I'm confused. I thought the NMR applied over $25K? 13 CFR 121.406(d) is clear, yet see FAR 19.102(f)(7) and 52.219-6(d). Is this yet another case of FAR not having "caught up" with an underlying regulation, as is the case with the limitations on subcontracting changes?
  14. Agreed, that is what the regulation says. My original question stems from CAFC's ruling in Digitalis, which seems to imply that if a prospective contractor misses the boat during the synopsis period, he is no longer an "actual or prospective bidder." This seems contrary to the plain language at 5.207( c )(16). Perhaps there is a different answer when using SAP? What about a synopsis that says: "Other prospective contractors may submit a capabilities statement by the closing date of this announcement. All submissions will be evaluated for the sole purpose of determining whether competitive opportunities exist, and the prospective contractor will be advised of the results of the government's evaluation. Late submissions will not be considered. If no submissions are received, the government will proceed with the intended noncompetitive action. An informational copy of the noncompetitive solicitation will be made publicly available IAW FAR 5.102(a) on or after (date), but competitive (quotations/bids/proposals) will not be considered." I'm sure there will be several objections to this. I'm used to rejection.
  15. OK, assume we're using SAP and soliciting a single source. I shall amend my hypothetical synopsis to the following: "(Agency X) intends to solicit a quotation on a single source basis IAW FAR 13.106-1(b)(1)(i) from (company Y) for (product/service Z.) Company Y is the only source reasonably available to fulfill this requirement under the circumstances because (reasons). IAW FAR 5.207(16)(i), all responsible sources may submit a quotation which shall be considered by (Agency X). The request for quotation will be available on or after 01 May 2016." You post that synopsis on 15 April 2016 and let it sit for 15 days. Nobody responds. You prepare your RFQ but don't include evaluation criteria or quotation submission instructions and post it to FBO IAW 5.102(a) on 02 May 2016. Company Y has told you they need a week to put together a price quotation, so you leave the RFQ open for a week, closing 09 May 2016. On 08 May, out of nowhere, company A emails you a quotation. It may or may not (likely not) contain any meaningful information because you haven't included evaluation criteria or quotation submission instructions in the RFQ. The synopsis advised that any quotation submitted "shall be considered by Agency X," and 13.106-2(a)(3) says "all quotations...shall be considered." So the question is - on what basis and/or to what extent are we "considering" this other quotation? We have not provided evaluation criteria suitable for a competitive environment in the RFQ. Must we amend the RFQ to include competitive evaluation criteria and re-release, as Todd Davis suggested yesterday? I think that's certainly a safe way to proceed. Or may this other quotation be "considered" by saying "no thanks?" I have practical reasons for this mental exercise that are systems related. Our procurement system (PRISM) allows one to post the "notice of intent" we've been discussing above to FBO either as a "special notice" or as a "presolicitation notice." As a practical matter, prospective contractors go looking for competitive opportunities by searching for presolicitation notices and combined synopsis/solicitations in FBO, not by reading special notices. When something shows up as a presolicitation, they think it's competitive. PRISM will not allow us to attach a solicitation to a special notice - a solicitation must first be announced via a presolicitation notice or it will not "release" to FBO. So we're stuck between a rock and a hard place; when we use the special notice as we've been trained to do, and which seems more intuitive to vendors, we then can't post the solicitation IAW FAR 5.102(a). If we use the presolicitation notice, prospective contractors often don't notice the presolicitation text and think they have a competitive opportunity, so we get junky quotes that aren't responsive and are then bound to "consider" them in some way. This is compounded by the fact that PRISM uses a proprietary portal called FedConnect, and the FBO announcement directs prospective contractors to FedConnect "for more information about this opportunity." When they get there, if they register with FedConnect, there is a "quote" button, where they can enter a price and hit submit. And bless their hearts, some specialists at my agency try to comply with 5.102(a) by first posting a special notice that says "notice of intent to award...," then after that closes, they post essentially a blank presolicitation notice that references the previous special notice so they can get the RFQ in FBO. If the vendor notices that, he's got to work really hard to find the referenced notice of intent, so he legitimately thinks there is a competitive RFQ available to him, and with no stated evaluation criteria, it looks like low price gets the job. I'm looking for a practical solution to these problems.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.