JADC2
Also known as: Joint All-Domain Command and Control
Definition
The U.S. military concept for connecting sensors and decision-makers across every operational domain — land, sea, air, space, and cyber — into a single unified network, extending C4ISR capability integration across domain and military service boundaries.
Key Points
- Extends C4ISR's integration of command, control, communications, and intelligence functions specifically across domain and military service boundaries, rather than within a single domain or service's own systems
- Aims to let a sensor in any domain — a satellite, a ship, an aircraft, a ground unit — feed data to any decision-maker or weapon system that can act on it, regardless of which military service or domain originally owns that sensor or shooter
- Directly targets sensor-to-shooter timeline compression as a core objective, since connecting sensors and shooters across domains that previously required manual, slower cross-service coordination can substantially reduce the elapsed time from detection to engagement
- Represents a significant data architecture and standards challenge as much as a network connectivity challenge, since sensors and systems across different services and domains have historically used incompatible data formats and standards not originally designed for cross-domain sharing
- Requires resilient, redundant connectivity across domains specifically because a JADC2 architecture's value depends entirely on data actually being able to flow between domains reliably, including under contested or denied communications conditions an adversary has direct incentive to target
Concept
Where traditional C4ISR systems have historically been organized largely within a single domain or military service — a service's own sensors feeding that same service's own command systems — JADC2 aims to break down those boundaries, letting any sensor across any domain feed data to any decision-maker or weapon system positioned to act on it, regardless of which service or domain originally fields that sensor or shooter, dramatically expanding the pool of sensor-to-shooter combinations available for any given target.
Explainer
The data standardization challenge JADC2 faces is arguably as consequential as its networking and connectivity requirements, since sensors and command systems developed independently across different military services over decades were generally never designed with cross-domain data sharing as a requirement, meaning connecting them meaningfully requires resolving incompatible data formats and standards before the underlying network connectivity can deliver its full intended value — a JADC2 network connecting incompatible data formats still leaves decision-makers unable to actually use data arriving from an unfamiliar domain's systems. This is precisely why JADC2's sensor-to-shooter timeline compression goal depends on solving both problems together: network connectivity alone doesn't help if the data arriving through that connectivity isn't in a form the receiving system or decision-maker can actually act on, meaning JADC2 implementation requires coordinated progress on data standards alongside the network and connectivity investment more visibly associated with the concept. For CE government and defense verticals, JADC2's resilience requirements under contested and denied communications conditions directly connect to this corpus's broader electromagnetic spectrum operations and denied-communications-environment material, since JADC2's cross-domain value proposition is specifically what an adversary capable of denying or degrading that cross-domain connectivity has the strongest incentive to target.
Cite this entry
JADC2. ConnectedEarth Knowledge Base. https://connectedearth.space/knowledge-base/jadc2/ (updated 13 September 2026).