Fourteen Waivers in Two Days, and Three Skipped Part 6
DoD posted 2,329 notices to SAM.gov on Thursday and Friday. Fourteen were justifications for not competing something, and ten of those were DLA and NAVSUP buying parts. The three that touched real services scope went through the fair-opportunity door instead, where there is no synopsis and usually no protest. Inside: the Space Force cloud waiver that fired because a ceiling ran out, the two no one can read, and five live sources-sought worth a response.
If you run capture against a multiple-award vehicle, the competition you lose is rarely the one you watched.
DoD published 2,329 notices to SAM.gov on Thursday and Friday. Fourteen of them were justifications, which is the government writing down why it is about to not compete something.
Ten cited FAR Part 6, and most of those ten were the Defense Logistics Agency and NAVSUP buying hubs, cylinders, sight indicators and a display processor. The scope that would actually show up in a pipeline review went a different way (chart below).
"Where does a services waiver go when it never has to be synopsized?"
The ceiling that ran out
DISA's DITCO posted justification JA26-080 at 20:52Z Friday, covering order HC1050-27-F-0047 against the JWCC basic contract HC1050-23-D-0005. The order was signed October 22.
The customer is Space Force System Delta 81, and the requirement is SpaceDEN: model-based systems engineering, modeling and simulation, DevSecOps, data analytics and digital twin work for roughly 3,000 guardians and supporting users, at unclassified, TS and SAP levels.
The awardee is AWS, named, on the ground that it holds the only ATO for the existing architecture and the only platform accredited to the SAP level the program needs.
Section 9 is where the mechanism is. The reason this justification exists now, in the agency's own words: "The current task order ceiling has been reached."
So the prior order, FA2057-24-F-8551, runs on paper to December 31, 2028, and it ran out of money in 2026. And that prior order was itself an exception to fair opportunity.
Two more details a capture plan can use. The agency polled all four JWCC cloud providers in July 2026: one confirmed it could meet the requirement, one responded without the SAP architecture, and two never answered.
The underlying JWCC market research report was signed November 9, 2021, revalidated July 29, 2024, and recertified February 6, 2026.
One footnote, because the desk collects these. Section 4 cites the exception as "FAR 16.507-6(b)(2)."
Subpart 16.5 ends at 16.506, and the real home of that exception is 16.505(b)(2). We flagged the same genre of slip on DISA's Link 39 presolicitation on October 28.
Two more, and neither one reads
MDA posted MDA27SNJA01 Friday morning, titled, with no ambiguity at all, "SBX Development, Operations and Sustainment, Justification for Exception to Fair Opportunity." Order HQ0856-27-F-E001 under HQ0859-26-D-E008, signed October 23, NAICS 541715, performed in Woburn, Massachusetts.
Air Force District of Washington posted the third at 23:31Z Friday: modification P00002 to order FA7014-26-F-0064, a bridge for the 1 DTA managed cloud services work, NAICS 541330. The vehicle underneath it is 47QRAA25D0052, which is a GSA-awarded contract, not a DoD one.
Both attachments are scans. pdftotext returns 91 bytes from the SBX justification and 3 bytes from the Air Force one, so the reasoning in each is machine-unreadable and will stay that way for anyone running an automated watch.
The rest of this brief is for subscribers.
The specific solicitations, dockets, and dates to act on sit past this line.
$50 a month, or $500 a year.
Already a subscriber? Sign in