Data readiness is the foundation for AI-enabled JADC2

Federal News Network | Jonathan Veal

The United States Department of Defense faces systemic data governance friction that threatens to undermine artificial intelligence adoption within Joint All-Domain Command and Control frameworks. An April 2025 Government Accountability Office review highlighted that isolated legacy systems force personnel into manual "swivel chair" operations, delaying decision-making across tactical environments.

Modern combat tempo requires automated data exchange across distributed cloud and edge networks. Interoperability remains hampered by incompatible data schemas across hundreds of service-specific platforms, alongside complex cross-border sharing arrangements. During exercise Bold Quest 22, over 1,000 participants across 19 partner nations evaluated Combined JADC2 capabilities, revealing significant technical and classification bottlenecks. Overly restrictive classification designators routinely prevent vital intelligence sharing among trilateral partners and coalition allies. Integration is stalled. Resolving these structural data readiness gaps and establishing shared data structures are crucial prerequisites before defense agencies can safely deploy AI-driven tactical edge systems in high-consequence operational environments.

Comment

The operational viability of Combined Joint All-Domain Command and Control hinges on resolving data provenance friction within coalition command nodes. In multinational exercises like Bold Quest 22, stovepiped battle management systems prevented real-time target data synthesis between allied combat identification platforms. Machine-learning algorithms placed at the operational edge cannot process unvalidated multi-source feeds without generating high false-alarm rates in tactical air-picture generation. Command authorities facing compressed decision windows cannot delegate engagement authority to automated tools when underlying sensor provenance remains unverified.

This friction stems from disparate cryptographic enclaves and incompatible Sensor Open Systems Architecture implementations across participating coalition forces. Without standardized cryptographic labeling at the telemetry layer, cross-domain solution guards automatically quarantine sensor feeds from platforms like the E-7 Wedgetail before analytics engines can process them. Until coalition networks like Link 16 integrate standardized attribute-based access controls, JADC2 nodes will remain constrained by manual human-in-the-loop validation protocols.

Strategic Question for Discussion

If cross-domain guards continue to quarantine unvalidated coalition telemetry from platforms like the E-7 Wedgetail during joint operations, will command authorities be forced to abandon machine-speed JADC2 targeting in favour of legacy manual validation protocols?

My assessment is that command authorities will repeatedly revert to legacy manual validation protocols whenever telemetry provenance cannot be cryptographically verified at the tactical edge. While this conservative approach preserves positive identification standards during contested operations, it forfeits the machine-speed decision cycle that AI integration into JADC2 is designed to achieve. Operational commanders consequently face an acute trade-off between targeting speed and risk mitigation until cross-domain data standards are fully deployed across coalition assets.

Share your assessment in the comments below.

Read the original article