If the Lockheed consortium's software-defined approach gains NATO endorsement, it shifts the GBAD procurement lever from hardware compatibility (which favors a single prime and locks out competitors) to software integration (which favors systems integrators and creates recurring SaaS-style contracts).
Raytheon, which has been pushing a proprietary Integrated Air Picture standard, will face pressure to open its APIs or cede the architecture contract to Lockheed. The second-order effect: whichever prime wins the software layer contract will control the kill-chain data flow for every NATO member's air defense for the next 15 years—and that's worth an estimated $8-12B in sustainment revenue alone.
This is the first concrete NATO GBAD architecture proposal to surface since the alliance formally prioritized air defense integration at the 2024 summit, and it directly addresses the fragmentation problem that has blocked coordinated defense against drone and missile salvos across the European theater.
The mechanism is software-defined interoperability—meaning each nation keeps its own sensors and C2 but routes targeting data through a common layer, rather than forcing hardware standardization or replacement.
This matters because it sidesteps the capital-expenditure veto that killed the previous SHORAD harmonization effort: Poland, Germany, and the Netherlands can keep their existing radar suites and just plug in software bridges.
Watch the NATO CNAD (Conference of National Armaments Directors) review cycle in Q4 2026 for formal concept approval—if it passes, the FY27 supplemental budget request will signal which primes get the integration contracts.
What is the actual data-sharing latency in the proposed architecture, and does it meet the <2-second targeting cycle requirement that EUROCORPS published in its 2025 air defense roadmap? The article doesn't specify.
Strategic intelligence, synthesized daily — with a public track record. Every call graded against what actually happened.