What does JADC2 stand for?

JADC2 stands for Joint All-Domain Command and Control. It is the US Department of Defense's concept for connecting sensors, decision-makers, and weapons across the air, land, maritime, space, cyber, and electromagnetic domains so that the joint force can sense, make sense, and act faster than an adversary.

What is the difference between JADC2 and CJADC2?

CJADC2 (Combined Joint All-Domain Command and Control) extends JADC2 from the US joint force to allies and coalition partners. The 'combined' reflects that most real operations are coalition operations, so data sharing, classification, and releasability across nations are core requirements rather than add-ons. In February 2024 the Deputy Secretary of Defense announced that a minimum viable CJADC2 capability had been delivered.

What are the five lines of effort in the JADC2 Strategy?

The unclassified summary of the JADC2 Strategy (March 2022) lists five lines of effort: establish the data enterprise, establish the human enterprise, establish the technical enterprise, integrate nuclear command, control, and communications (NC2/NC3) with JADC2, and modernize mission partner information sharing.

Is JADC2 a program of record?

No. JADC2 is a department-wide concept and strategy, not a single acquisition program. Capabilities that contribute to it are delivered by service efforts such as the Air Force's Advanced Battle Management System (ABMS), the Army's Project Convergence campaign of learning, and the Navy's Project Overmatch, along with joint and OSD-level initiatives.

What does 'sense, make sense, act' mean in JADC2?

It is the decision cycle the JADC2 Strategy is organized around. Sense means collecting data from sensors and sources across domains. Make sense means fusing and analyzing that data into an understanding of the situation. Act means making and executing a decision, then feeding the results back into the next cycle.

Why does DDIL matter for JADC2?

DDIL (denied, degraded, intermittent, or limited) describes communications that an adversary, terrain, or weather can interrupt. A C2 architecture that only works with persistent connectivity to a central data center loses its picture exactly when it is needed. Designing for DDIL means units can keep sensing, fusing, and deciding locally, and share results when links return.

What is JADC2? Joint All-Domain C2

Joint All-Domain Command and Control (JADC2) is the US Department of Defense's concept for connecting sensors, decision-makers, and weapons across every warfighting domain: air, land, maritime, space, cyberspace, and the electromagnetic spectrum. The goal is a force that can share data across services and echelons, understand a situation faster than its adversary, and act on that understanding before the adversary can.

JADC2 is a concept and a strategy, not a single system or program. It describes what the joint force's command and control should be able to do, and leaves the services, combatant commands, and defense agencies to build the pieces. That is the main reason it is so often misunderstood.

For short answers on the service programs, JADO doctrine, and related acronyms, see the JADC2 FAQ.

JADC2 in one paragraph

Traditional command and control grew up domain by domain. Air defense, ground maneuver, naval warfare, space, and cyber each built their own sensors, data links, displays, and chains of command. Those systems work within their lane but share poorly across lanes. An adversary who deliberately combines effects across domains, such as drones, jamming, cyber intrusion, and disinformation timed together, can exploit the seams. JADC2 is the effort to remove those seams: common data, common standards, and networks that let any authorized user find and use information from any domain, at the echelon and speed the mission requires.

Where JADC2 came from

JADC2 grew out of a decade of concern that near-peer competitors had closed the technological gaps the US military relied on and had built forces designed to contest every domain at once.

Multi-Domain Operations (2018). The Army's concept, The U.S. Army in Multi-Domain Operations 2028 (TRADOC Pamphlet 525-3-1), argued that future fights would require converging effects from all domains. The Air Force and Navy pursued related concepts in parallel. All of them depended on command and control that could work across domains, which existing systems could not.
From service concepts to a joint concept (2019-2020). The Joint Staff took up all-domain command and control as a joint problem, and "JADC2" became the umbrella term for the effort.
The JADC2 Strategy (2021-2022). The Secretary of Defense signed the JADC2 Strategy in 2021. The Department released an unclassified summary in March 2022, alongside a classified implementation plan.
From JADC2 to CJADC2 (2023-2024). The "C" for combined was added to make allied and partner integration explicit. In February 2024, Deputy Secretary of Defense Kathleen Hicks announced that a minimum viable CJADC2 capability was "real and ready now," with the Chief Digital and Artificial Intelligence Office (CDAO) playing a central role in data integration.

What the JADC2 Strategy says

The unclassified strategy summary frames JADC2 around a familiar decision cycle: sense, make sense, and act, at all levels and phases of war, across all domains, and with partners. It then organizes the work into five lines of effort:

Data enterprise. Common data standards, metadata tagging, and data that is visible, accessible, understandable, linked, trustworthy, interoperable, and secure.
Human enterprise. Training, doctrine, and the people who have to use JADC2 capabilities under pressure.
Technical enterprise. The networks, compute, transport, and security architecture that move and protect the data.
Integration of nuclear command, control, and communications (NC2/NC3). Making sure conventional all-domain C2 and nuclear C2 work together without compromising either.
Modernization of mission partner information sharing. Sharing data with allies and partners by design, which later became the "combined" in CJADC2.

The summary also sets guiding principles. In short: build information sharing at the enterprise level, layer security throughout, adopt common data standards and architectures, stay resilient in degraded and contested electromagnetic environments, unify development across the Department, and field capability faster.

JADC2, CJADC2, JADO, and MDO

These terms are related but not interchangeable.

Term	What it is	Who owns it
MDO (Multi-Domain Operations)	An operational concept for converging effects across domains	Originated with the Army; now used across services
JADO (Joint All-Domain Operations)	Joint doctrine for operating across all domains	Joint Staff and services
JADC2	The command and control concept and strategy that makes JADO executable	OSD, Joint Staff, services, and combatant commands
CJADC2	JADC2 extended to allies and coalition partners	Same, plus mission partners

A useful shorthand: MDO and JADO describe how to fight; JADC2 and CJADC2 describe how to command and control that fight.

How the services contribute

No single office builds JADC2. Each service contributes through its own efforts, sized to its own operational problem:

Air Force: ABMS. The Advanced Battle Management System connects airborne, space, and ground sensors with command nodes and strike platforms.
Army: Project Convergence. An annual campaign of learning that tests sensor-to-shooter chains across services and, increasingly, with allies.
Navy: Project Overmatch. Networking, data, and infrastructure for a distributed maritime force. Much of it is classified.
Joint and OSD. The Joint Staff J6, the DoD CIO, and the CDAO coordinate standards, data integration, and enterprise capability. Combatant commands, especially those facing near-peer threats, drive operational requirements and experimentation.

The JADC2 FAQ covers each program in more detail.

The technical building blocks

Strip away the acronyms and JADC2 depends on a handful of engineering capabilities. Most of the difficulty lives here.

Data that can be shared

Every sensor and system describes the world differently: different coordinate systems, time references, identifiers, classification schemes, and uncertainty models. Before anything can be correlated across domains, data has to be normalized into common schemas and tagged with enough metadata (source, time, accuracy, classification, releasability) that downstream users can trust and share it. This is the data enterprise line of effort in practice, and it is the least glamorous and most important part of the job.

Fusion

Data sharing alone produces a crowded map, not understanding. Sensor fusion combines detections from radar, RF, EO/IR, acoustic, and cooperative sources into single tracks with position, velocity, identity, and confidence. Intelligence fusion adds context from other disciplines, such as signals, imagery, open-source, financial, and space data, to explain what those tracks mean. Together they are the "make sense" step of the JADC2 cycle.

A shared picture

A Common Operational Picture is where fused data becomes visible and actionable for operators and commanders. In JADC2 terms, the same picture should be available at every echelon, filtered by role and authority, rather than rebuilt from scratch at each level.

Transport and resilience

JADC2 data has to move over everything from fiber and SATCOM to tactical data links such as Link 16, mesh radios, and commercial LEO constellations. All of them can be jammed, degraded, or destroyed. Designing for DDIL (denied, degraded, intermittent, or limited) communications means each node keeps working with what it has and synchronizes when links return.

Security and identity

Sharing across services and nations multiplies the attack surface. Zero-trust architecture, strong identity for people and machines, encryption in transit and at rest, and data-level access control are prerequisites, not features.

Decision support and automation

The "act" step depends on decision aids and automation that are fast, explainable, and bounded by policy: rules of engagement, airspace control measures, and authority to engage. Automation that operators cannot understand or override will not be trusted, and untrusted automation does not get used.

Common misconceptions

"JADC2 is one network." It is a family of networks, standards, and applications. Interoperability matters more than uniformity.
"JADC2 is a cloud program." Enterprise cloud plays a role, but tactical units cannot assume persistent connectivity. Much of the hard work is at the edge.
"JADC2 means fully automated kill chains." The strategy is about decision advantage, not removing people from decisions. Human judgment and authority remain central.
"JADC2 is only for the military." The same problems, fragmented sensors, incompatible data, and decisions under time pressure, apply to homeland security, critical infrastructure, emergency management, and coalition humanitarian operations.

Empyrean's view: build sensor-up

Our position is that JADC2 succeeds when it is built from the sensor up rather than from the headquarters down. The decisions with the shortest timelines, such as engaging an inbound missile or a drone over a perimeter, are made at the tactical edge, often with degraded connectivity. That argues for fusing data where the sensors are, keeping a working picture when links drop, and passing fused results upward when they return. We make the full case in Why JADC2 Needs Sensor Fusion at the Edge.

Empyrean's Fusion & Decision Engine, Common Operational Picture, and Policy & Decision Layer are built on that model: single-tenant, edge-deployable, and air-gap capable, with the same software at every echelon and in the Simulation & Wargaming engine used for training.

What is JADC2 (Joint All-Domain Command and Control)?