Pentagon Seeks $2B+ in FY27 to Consolidate Fragmented CJADC2 Systems Onto Single Interface
The $2B figure is the down payment on a larger industrial problem. If the Pentagon is requesting this much in a single year, the actual total cost to decommission legacy systems and migrate operational data likely exceeds $5-6B over the FYDP.
This creates a procurement opportunity for Palantir (already embedded in CJADC2 pilots), Northrop Grumman (Mission Systems division), and Raytheon (Intelligence & Space), but it also exposes a risk: if the integration stumbles, the Pentagon will need a fallback architecture mid-deployment.
CENTCOM's current rotation tempo in the Middle East means any C2 disruption during the Iran contingency window (next 18 months) becomes politically unacceptable, which hardens the FY27 deadline into an operational requirement, not a budget preference.
The constraint isn't funding availability—it's integration complexity across incompatible legacy systems already fielded to INDOPACOM, CENTCOM, and EUCOM.
If the consolidation misses the FY27 timeline, the Pentagon faces a choice between maintaining three separate operational pictures or forcing a disruptive cutover mid-conflict. Watch the FY27 budget markup on the Hill for line-item specificity: does Congress appropriate the $2B as a single CJADC2 integration account, or does it fragment across service-specific C2 line items?
The latter signals skepticism about the delivery timeline.
What is the current fragmentation—how many distinct command-and-control platforms are INDOPACOM, CENTCOM, and EUCOM actually running today, and what is the interoperability loss measured in decision latency or targeting accuracy?
Fault Lines
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.