Daily acquisition brief // October 15, 2026

CMCoE Meme Intel: Access Denied, Deadline Approved

A locked protest report, a cyber standard denied retirement, and an Army bidding window that requires player two.

8 storiesRSS feed
VA / GAO / Protest access

The report was locked. The comment deadline kept running.

Sterling could not open the VA report, then lost its protest for missing the response deadline.

Bad Luck Brian meme: AGENCY REPORT: ACCESS DENIED / PROTEST: DISMISSED FOR NOT RESPONDING
AGENCY REPORT: ACCESS DENIED / PROTEST: DISMISSED FOR NOT RESPONDING

What happened

GAO denied reconsideration on October 13. VA had filed its July 24 report as protected, leaving self-represented Sterling unable to view it. VA supplied neither a redacted copy nor an emailed version.

Comments were due August 3 at 5:30 p.m. Eastern. Sterling first alerted GAO to the access problem at 8:57 p.m. that evening. The underlying protest challenged a sole-source purchase of Walsh inspection software.

Why CMCoE cares

Document access and the filing clock became separate problems. GAO said an inaccessible report does not automatically extend the deadline.

Regulatory fine print

GAO expected Sterling to notify it and request an extension before the deadline. Agencies are expected to provide usable redacted information to unrepresented protesters. This decision upheld the procedural dismissal; it did not approve the sole-source procurement on its merits or find intentional withholding.

Sources

  1. GAO: Sterling Readiness Rounds, reconsideration, B-424607.2 (GAO, )
DOE / Cybersecurity / Contract requirements

The cyber standard retired in 2021. One DOE contract still required it.

A newly posted inspector-general evaluation found contract language keeping an obsolete standard on the job.

One Does Not Simply meme: NIST RETIRED REVISION 4 / CONTRACT: RETIREMENT REQUEST DENIED
NIST RETIRED REVISION 4 / CONTRACT: RETIREMENT REQUEST DENIED

What happened

DOE-OIG-27-02 is dated October 8 and was posted October 14. In its fiscal 2025 review, inspectors found four of six sites still using NIST Revision 4 for 21 of 42 systems. NIST had withdrawn that revision in September 2021.

At one site, the contract required Revision 4. Three sites said the newer Cybersecurity Framework 2.0 was not contractually required. Inspectors identified gaps between current federal guidance and local requirements.

Why CMCoE cares

Modern cybersecurity expectations need to reach the instruments that govern contractor performance.

Regulatory fine print

These are findings about the audited period, not an October system inventory or a reported breach. DOE agreed with 46 of 55 new recommendations, disputed nine and reported two already addressed. Inspectors considered the planned actions responsive. The department also closed 57 prior recommendations; using the old contract standard is not itself proof of contractor noncompliance.

Sources

  1. DOE OIG: DOE-OIG-27-02, findings and management response (DOE Office of Inspector General, )
  2. DOE: October 14 posting (Department of Energy, )
Army / MAPS / Competition

MAPS reopens bidding, but the new window requires a team.

The Army is accepting new proposals from small-business teaming arrangements after GAO rejected its teaming prohibition.

Futurama Fry meme: MAPS BIDDING IS OPEN AGAIN / PLEASE INSERT PLAYER TWO
MAPS BIDDING IS OPEN AGAIN / PLEASE INSERT PLAYER TWO

What happened

Amendment 0011, posted October 13, sets November 12 at 11:59:59 a.m. Eastern as the new deadline. Only small-business teaming arrangements may submit new proposals in this window.

An existing offeror may withdraw its earlier individual proposal and join a qualifying team. Other offerors cannot revise or newly submit individual proposals; eligible proposals already submitted remain in consideration.

Why CMCoE cares

The correction opens a path for teams while preserving different submission opportunities for existing individual bidders.

Regulatory fine print

GAO sustained the teaming challenge on August 11 and denied other grounds. This is an amended solicitation, not an award or a ruling that the new window is unlawful. It is a new development distinct from the MAPS scorecard decision featured October 3. The meme describes new submissions, not all eligible offers.

Sources

  1. Army: MAPS amendment 0011 and updated solicitation attachments (U.S. Army / SAM.gov, )
  2. GAO: MAPS teaming decision, B-424433.3 and B-424433.7 (GAO, )
Defense / Responsible AI / Workforce

Responsible AI had ten authorized positions and three people.

GAO found the central Responsible AI office short of staff while the department pressed for faster AI adoption.

Awkward Look Monkey Puppet meme: RESPONSIBLE AI: TEN AUTHORIZED POSITIONS / SEVEN STAFFED BY WISHFUL THINKING
RESPONSIBLE AI: TEN AUTHORIZED POSITIONS / SEVEN STAFFED BY WISHFUL THINKING

What happened

The October 14 report says only three of ten authorized Responsible AI positions were filled as of February 2026. Officials linked the vacancies to continuing restructuring and new strategy requirements.

The first implementation task had been to staff the office with technology, policy, acquisition and governance expertise. GAO also found that the working council lacked a charter defining responsibilities and meeting frequency.

Why CMCoE cares

Buying and deploying AI faster still requires people to coordinate assessment, policy and oversight.

Regulatory fine print

The headcount is a February snapshot of this division, not all defense AI staff or a verified October count. The council resumed meetings in August 2025 after a hiatus; staff had been developing other AI resources during that gap. The department agreed with GAO’s two new recommendations on staffing and the council charter.

Sources

  1. GAO: Responsible AI implementation, GAO-27-107837 (GAO, )
Defense / Telecom / Security oversight

The wireless plan came before the security-results check.

Inspectors found gaps in how defense officials verified carrier security for the Spiral 4 wireless contract.

Roll Safe meme: SPIRAL 4 SECURITY VERIFICATION / THE UNLIMITED TRUST PLAN
SPIRAL 4 SECURITY VERIFICATION / THE UNLIMITED TRUST PLAN

What happened

The report is dated October 9 and listed publicly October 14. Third-party assessment results were not required as a condition of the May 2024 awards. Officials said they lacked contractual authority to obtain them until a modification.

A May 8, 2026 modification now requires results. But the response did not describe a process to review them before exercising options. Inspectors also sought an assessment of protections needed for carrier-held metadata.

Why CMCoE cares

Collecting a security report and using it in a renewal decision are separate controls.

Regulatory fine print

The $2.67 billion figure is a contract ceiling, not spending. The report identified no carrier breach affecting Spiral 4 metadata. NAVSUP agreed to the review recommendation and cited the modification; officials disputed parts of the metadata approach and authority. All three recommendations remained open and unresolved in the report. The joke targets the verification gap, not a claim that carriers performed no security work.

Sources

  1. DoW OIG: Spiral 4 audit, DOWIG-2027-001 (Department of War Office of Inspector General, )
  2. Oversight.gov: October 14 listing and recommendation status (Oversight.gov, )
DHS / Body cameras / Program management

One ICE location had cameras and training, but had not started using them.

A newly public GAO report shows the gap between delivering equipment and making its use clear.

Woman Yelling at a Cat meme: ICE CAMERAS DELIVERED AND TRAINING COMPLETE / GREAT. WHEN DO WE USE THEM?
ICE CAMERAS DELIVERED AND TRAINING COMPLETE / GREAT. WHEN DO WE USE THEM?

What happened

GAO’s September 15 report was publicly released October 14. At one ICE location visited, personnel said cameras had been deployed and training completed, but use had not begun because they were unsure when to record.

Across ten visited CBP and ICE locations, personnel at six described uncertainty over activation. GAO found that most offices lacked operational guidance tailored to their work.

Why CMCoE cares

A completed purchase and training session do not finish deployment when users still need instructions for real situations.

Regulatory fine print

The ten locations were a nongeneralizable selection, not a measure of the entire workforce. Both agencies have camera policies and supervisory controls. DHS agreed with six recommendations but opposed automatic activation, citing privacy and other operational risks; GAO said additional controls could help. The finding does not establish deliberate failure to record. A 2025 deployment pause was followed by a July 2026 expansion announcement.

Sources

  1. GAO: body-camera program management, GAO-26-108157 (GAO, )
  2. GAO: October 14 public release and response (GAO, )
State / Deloitte / Incumbent dependency

State identified six qualified alternatives and extended Deloitte anyway.

An October 14 justification explains why available competitors did not eliminate State’s continuity problem.

Confused Travolta meme: WE FOUND SIX OTHER VENDORS / THEY DON’T KNOW WHERE ANYTHING IS
WE FOUND SIX OTHER VENDORS / THEY DON’T KNOW WHERE ANYTHING IS

What happened

The September 18 modification extends analytics and technology support through September 29, 2027, with two six-month options. The justification names six qualified vendors identified through informal market research.

State says those alternatives would need four to six months to onboard, with some security processing taking longer. It cites Deloitte’s embedded knowledge, proprietary workflows, agency reorganization and the risk of interrupting mission support.

Why CMCoE cares

Technical capability in the market does not erase the transition burden created by an incumbent’s accumulated knowledge.

Regulatory fine print

This is State’s justification for a logical follow-on, not an audit finding of improper favoritism. It says the earlier order was competed and plans a later limited EVOLVE competition when requirements stabilize. The extension amount is redacted; no dollar value is inferred. The meme’s lost visitor is not a procurement participant.

Sources

  1. State Department: Deloitte follow-on justification, 19AQMM21F7091 P00115 (Department of State / SAM.gov, )
VA / Oracle EHR / Congressional oversight

Lawmakers want the paperwork behind VA’s larger Oracle contract ceiling.

An October 13 oversight release questions the increase from roughly $10 billion to $27 billion.

Surprised Pikachu meme: ORACLE EHR CONTRACT CEILING: $27B / EVEN THE CEILING GOT AN UPGRADE
ORACLE EHR CONTRACT CEILING: $27B / EVEN THE CEILING GOT AN UPGRADE

What happened

Senator Blumenthal and Representative Takano released a demand for contract records and explanations, with a response requested by October 30. The letter questions the scale and basis of the expanded Oracle electronic-health-record contract.

VA’s official notice records an August 18 modification with a base-and-options action value of about $16.94 billion. That figure is distinct from both the resulting contract ceiling and VA’s broader program cost forecast.

Why CMCoE cares

A higher contractual limit needs a clear account of scope, pricing and expected delivery; it is not itself a measure of expenditures.

Regulatory fine print

These are oversight questions, not established fraud findings. The letter’s cover is dated October 6; later page headers say September 22. Oracle’s September 2 congressional statement says recent deployments improved, cites sixteen months without outages and supports completion in 2031. Those are the vendor’s claims. A ceiling is not an obligation or payment.

Sources

  1. Senate: October 13 oversight release (Office of Senator Richard Blumenthal, )
  2. House: underlying oversight letter (House Veterans’ Affairs Committee Democrats, )
  3. VA: August 18 contract modification notice (Department of Veterans Affairs / SAM.gov, )
  4. Oracle: September 2 statement submitted to Congress (U.S. House of Representatives / Oracle statement, )