Mission thread versus enterprise
A kill web focuses on alternative pathways that connect sensing, decision, authority, support, effects, and assessment. JADC2 addresses the larger institutional and technical environment needed to make those pathways possible across domains and organizations.
Treating JADC2 as one universal network or one software product would hide the real work: governance, data semantics, resilient transport, coalition releasability, acquisition, training, and command relationships.
Service contributions must converge
| Perspective | Typical contribution | Joint requirement |
|---|---|---|
| Air | Wide-area sensing, airborne battle management, long-range operations | Publish and consume joint-quality data without making every platform host every application |
| Maritime | Distributed ships, aircraft, submarines, and uncrewed systems | Operate through intermittent beyond-line-of-sight links and coalition task groups |
| Land | Dense tactical sensors, air defense, fires, and mobile command posts | Normalize data across functions and sustain DDIL operations |
| Expeditionary | Forward, low-signature sensing and effects | Share compact weapons-quality data while preserving mobility and delegated bounds |
| Space | Warning, tracking, transport, communications, and PNT | Deliver timely, trusted data across orbital and terrestrial layers while resisting common-mode failure |
A common data foundation, not one identical display
Different users need different views. A tactical node may need track, uncertainty, control measures, and status. An analyst may need source history and competing hypotheses. A commander may need risk, readiness, and decision points. A partner may receive a releasable representation with protected sources removed.
The common operating picture is therefore an output of the data fabric, not the integration layer itself.
Combined operations add policy to every edge
- Federated identity and partner credentials
- Machine-readable classification and releasability
- Agreed semantic and track-quality profiles
- National caveats and engagement authorities
- Cross-domain guards, sanitization, and audit
- Fallback procedures for disconnected partner operations
The central implementation risk is fragmentation
Service-specific solutions can improve local performance while leaving the joint enterprise fragmented. Public oversight cited in the research corpus emphasizes the need for a comprehensive framework, common progress measures, clearer responsibilities, and better sharing of lessons.
End-to-end mission-thread performance must be owned and tested even when no single platform program owns the entire path.
Research basis: KW-RPT-007 and KW-RPT-013.