
SPY-6 integration is not a production constraint — it's a test-and-validation constraint. If Raytheon owns all integration work, they can modulate throughput by staffing test ranges and lab capacity.
But if the Navy is trying to accelerate DDG-51 Flight III deliveries (already behind schedule), and integration is the gating factor, then this contract is a de facto admission that Bath Iron Works or the Navy's own test infrastructure cannot absorb the workload.
The second-order effect: Raytheon can negotiate sustainment and modernization contracts for SPY-6 variants with minimal competition risk, since no other firm will have built the institutional knowledge of the integration process.
This contract sustains Raytheon's dominance in naval air defense radar at a moment when the Navy is scaling SPY-6 across the DDG-51 Flight III and other platforms — meaning Raytheon's test and integration capacity becomes the binding constraint on how fast the Navy can deliver ships to the fleet.
The $515M commitment signals the Navy is willing to front integration costs rather than compress schedules, which protects Raytheon's margin but also locks in a 18-24 month integration window per hull class. Watch the FY27 FYDP for whether the Navy requests additional test-range capacity or splits integration work to a second source — either move would signal doubt about Raytheon's throughput.
Does this $515M cover integration for all planned SPY-6 installations (DDG-51 Flight III, Constellation-class, and future platforms), or is it limited to a specific platform subset?
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.