Air Force to Get First Next-Gen Tactical C2 Centers By Year’s End

TL;DR

The Air Force awarded Booz Allen Hamilton a $315 million rapid prototyping contract to produce and scale the Tactical Operations Center-Light (TOC-L) MR2, the next-generation ground-based air battle management system. The contract requires delivery of 70 units to Air Force units by year’s end and will replace legacy Control and Reporting Centers with a more agile, software-defined C2 system expected to serve for 30–40 years. This marks a material shift in Air Force ground C2 procurement and creates near-term production, integration, and sustainment work as prototypes are fielded and assessed. Follow-on quantities and additional procurement actions are possible as the operational community refines requirements. Contractors should treat this as an active market signal: validate compliance posture (CMMC (Cybersecurity Maturity Model Certification), NIST 800-171 (NIST Special Publication 800-171), ITAR (International Traffic in Arms Regulations), DFARS (Defense Federal Acquisition Regulation Supplement)), reassess capture plans against TOC-L MR2 technical needs, and prepare to engage with prime integrators and the Air Force on sustainment and scaling opportunities.

Key Points

• What happened: The Air Force awarded a $315 million rapid prototyping contract to Booz Allen Hamilton to produce and scale the TOC-L MR2 next-generation ground-based air battle management system, replacing legacy Control and Reporting Centers.
• Who is affected: Defense market participants and companies aligned to the listed NAICS codes (541512, 334511, 541330, 541715, 336414) and agencies (DOD, Air Force); market segments include Command and Control Systems, Air Battle Management, Software-Defined Systems, Tactical Communications, Ground-Based C2, and Military Electronics. Compliance surfaces called out include CMMC, NIST 800-171, ITAR, and DFARS.
• Timeline: The contract will deliver 70 units to Air Force units by year’s end.
• What contractors should do NOW: perform a rapid gap assessment vs. the named compliance regimes; map product and service capabilities to TOC-L MR2 mission requirements; update capture and subcontracting plans targeting prototype sustainment and scale phases; notify capture and proposal teams; and begin monitoring for follow-on solicitations and tasking.

Who Is Affected

• Market segments at risk/opportunity: Defense, Command and Control Systems, Air Battle Management, Software-Defined Systems, Tactical Communications, Ground-Based C2, Military Electronics.
• Specific NAICS codes: 541512, 334511, 541330, 541715, 336414.
• Agencies: DOD, Air Force.
• Contract vehicle: Rapid Prototyping Contract (as stated).
• Compliance regimes: CMMC, NIST 800-171, ITAR, DFARS.

Specific NAICS codes, agencies, and contract vehicles pending source review for any additional associated vehicles or classified tasking.

Frequently Asked Questions

Q: Who won the award and what is the contract value?

A: Booz Allen Hamilton was awarded the contract at $315 million for rapid prototyping and scaling of the TOC-L MR2, per the event summary.

Q: How many systems will be delivered and by when?

A: The contract requires delivery of 70 units to Air Force units by year’s end.

Q: Will there be follow-on production or additional procurements?

A: The summary states potential follow-on opportunities as quantities are refined by the operational community. Specific schedules, quantities, and follow-on vehicle details are pending source review.

Definitions

• Tactical Operations Center-Light (TOC-L) MR2: The named next-generation ground-based air battle management system being produced under this prototyping contract.
• Control and Reporting Centers: Legacy Air Force ground C2 nodes being replaced by the TOC-L MR2 rollout.
• Software-defined C2 system: A command-and-control approach emphasizing software-based routing, processing, and mission capability that replaces hardware-centric legacy systems.
• Ground-based air battle management system: A land-deployed system providing command, control, and battle management for air operations.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Use War Room to track ongoing reporting, government announcements, and public notices tied to the prototyping contract.
• Cabrillo Signals Match Engine — Re-score opportunity pipelines and partner/subcontractor lists to reflect heightened probability for C2, air battle management, and software-defined system opportunities.
• Cabrillo Signals Intelligence Hub — Create saved searches for follow-on solicitations tied to the Rapid Prototyping Contract, for the listed NAICS codes and agencies; receive alerts when relevant solicitations or modifications appear on SAM.gov (System for Award Management).
• Proposal Studio (Proposal OS) & Proposal Studio Workflow Tracker — Initiate a bid/no-bid evaluation, generate a compliance matrix mapping to CMMC, NIST 800-171, ITAR, and DFARS requirements, and run the 9-gate capture workflow to produce audit-ready documentation.

Who to notify:

• Capture/BD lead — to re-prioritize pursuit plans and partner engagements.
• Proposal manager — to start compliance matrices and bid/no-bid activity.
• Security & Compliance officer — to validate CMMC/NIST/ITAR/DFARS posture and remediate gaps.
• CTO/Systems engineering lead — to map technical capabilities to TOC-L MR2 requirements.
• Supply chain manager — to validate production and sustainment readiness for rapid deliveries.

First 48-hour response playbook:

• Hour 0–4: Notify capture, proposal, security, systems engineering, and supply chain leads; push event to Cabrillo Signals War Room and enable saved-search alerts for follow-ons.
• Hour 4–12: Run Match Engine rescore on existing opportunity pipeline; conduct a rapid compliance gap assessment against CMMC, NIST 800-171, ITAR, and DFARS.
• Hour 12–24: Use Proposal Studio to start a bid/no-bid and draft a high-level capture plan; identify subcontracting roles and potential teaming leads tied to prototyping and sustainment.
• Hour 24–48: Execute outreach to prime integrators and potential partners (as appropriate), finalize initial compliance remediation tasks, and configure Intelligence Hub saved searches and alerts for new actions on the Rapid Prototyping Contract.

Primary reading and operational guidance: Winning Federal Contracts Guide (/insights/winning-federal-contracts). For security and CUI (Controlled Unclassified Information) handling, consult CMMC Compliance Guide (/insights/cmmc-compliance-guide) and CUI-Safe CRM Guide (/insights/cui-safe-crm-guide).