JADC2: What European and Allied Vendors Need to Know

Joint All-Domain Command and Control (JADC2) is the US Department of Defense's overarching concept for connecting sensors, decision-makers, and effectors across all military domains — land, sea, air, space, and cyberspace — into a single, integrated network. With total programme investments estimated above $10 billion and spanning dozens of individual programmes across all military services, JADC2 is the largest C2 modernisation initiative in US history. For European and allied software vendors, it represents both a market opportunity and a technical alignment challenge.

The market opportunity is real but indirect. Direct participation in JADC2 contracting is largely inaccessible to non-US companies due to security and ITAR restrictions. However, the architectural standards and interoperability requirements that JADC2 establishes are already influencing NATO's own C2 modernisation agenda, and understanding JADC2 architecture positions European vendors to develop compatible products for NATO markets that will be required to interoperate with US JADC2 systems in coalition operations.

What JADC2 Is and Why It Matters for Allied Vendors

JADC2 emerged from the recognition that the US military's existing C2 architecture — built around service-specific systems that do not interoperate well — is inadequate for the speed and simultaneity of modern multi-domain operations. The concept envisions a network where any sensor (a satellite, a radar system, a drone, a soldier's weapon sight) can pass data to any decision-maker (a commander, an AI decision-support system) and any effector (an aircraft, a ship's weapons system, a cyber capability) in near-real time, regardless of which military service or nation owns the sensor, decision-maker, or effector.

The principal JADC2 programmes are service-specific implementations of the shared concept: the US Army's Project Convergence/Combined Arms Center programme, the US Air Force's Advanced Battle Management System (ABMS), the US Navy's Project Overmatch, and the US Marine Corps' Project Dynamis. These programmes are developing the technical components of JADC2 within their respective domains, with the Joint Staff's Joint All-Domain Command and Control office responsible for ensuring the components can interoperate.

For allied vendors, JADC2 matters because the US military is the largest C2 customer in the world, and systems that European militaries procure will need to interoperate with US JADC2 systems in coalition operations. A European C2 system that cannot exchange data with ABMS or Project Convergence in a multinational exercise is operationally limited regardless of its technical quality. Understanding JADC2 architecture is therefore a prerequisite for designing European C2 products that will be operationally viable in the coalition context in which most European forces will actually operate.

JADC2 Architecture: Transport, Data, and Application Layers

The JADC2 technical architecture is structured around three conceptual layers: transport, data, and application. Understanding these layers is essential for vendors seeking to develop compatible systems.

The transport layer encompasses the physical and logical network infrastructure over which JADC2 data travels: military satellite communications, tactical radio networks, fibre connections at fixed sites, and the emerging network of low Earth orbit commercial satellite constellations that are increasingly integrated into military communications architectures. The key transport layer requirement for JADC2-compatible systems is support for the Combat Cloud concept — the ability to operate across heterogeneous transport networks with automatic path selection and appropriate data handling for each network's security level.

The data layer is where the architectural requirements most directly affect software vendors. JADC2 data exchange relies on a set of data standards and protocols designed to enable interoperability without requiring custom integration between each pair of systems. The core data standards include the Unified Data Library (UDL) for space domain awareness data, the Tactical Data Link (TDL) family for real-time tactical track data, the NIEM framework for structured data exchange, and the emerging Combat Cloud API standards for application-level data exchange. For European vendors, the most relevant of these is the TDL family — specifically Link 16 and the NATO standard extensions to it — since these are the data exchange standards used by NATO forces in operational contexts.

The application layer is where the decision-support, analytics, and user interface applications that JADC2 is designed to support operate. These applications consume data from the data layer and present it to human decision-makers or feed it to automated systems. The application layer is the most accessible for European vendors, since the application-level APIs are relatively well documented through NATO's Federated Mission Networking standards, and the political and security barriers to participation are lower than at the transport and data layers.

Where EU/UA Vendors Can Contribute

European vendors have realistic contribution opportunities at two points in the JADC2 ecosystem. The first is in the supply chain of US prime contractors working on JADC2 programmes. US primes including Northrop Grumman, Raytheon, L3Harris, and SAIC are actively seeking specialist software capabilities for specific JADC2 components, and European vendors with unique capabilities in areas such as advanced analytics, machine translation, multi-spectral image processing, or RF signal intelligence have a realistic case to make as subcontractors. The ITAR constraints apply here — subcontractor access to classified JADC2 programme information requires appropriate clearances and controlled access arrangements — but technology partnership arrangements that share algorithmic capability without sharing classified architecture details are feasible.

The second and more immediately accessible contribution opportunity is in NATO-aligned C2 systems that are designed to interoperate with JADC2 in coalition contexts. NATO's FMN framework specifies the interoperability standards that NATO systems must meet to exchange data with US systems in exercises and operations. A European C2 system that implements FMN Spiral 4 and 5 standards — including the tactical data exchange standards that align with JADC2's data layer — is positionally aligned with JADC2 interoperability without requiring direct JADC2 programme participation.

Interoperability with NATO FMN: Common Points

The NATO Federated Mission Networking framework and the JADC2 architecture share a common set of interoperability requirements that create the technical bridge between them. The key shared requirements are: RESTful API interfaces for application-level data exchange; JSON and XML data serialisation for structured data; NATO Message Text Format (NMTF) for operational message exchange; Link 16 and SIMPLE support for tactical track data; and PKI-based authentication for cross-domain data sharing.

European vendors who implement these standards in their C2 products are simultaneously meeting NATO FMN requirements and the coalition interoperability requirements of JADC2. The key difference is in the classified architecture components: FMN specifies the interoperability interfaces but leaves the internal architecture of compliant systems to national discretion, while JADC2 has additional internal architecture requirements that apply specifically to US-service systems. European vendors building to FMN will be interoperable with JADC2 at the coalition interface level without needing to meet the additional US-internal requirements.

For vendors investing in JADC2/FMN alignment, the practical starting point is participation in NATO's Interoperability Testing Programme — specifically the Connected Forces Initiative exercises where FMN standards are operationally tested across allied systems. Vendors whose products successfully complete CFI exercise testing have a credible claim to JADC2-compatible interoperability that is based on operational evidence rather than paper compliance assertions.