Modern War Demands a Data-Centric, Cloud-Based Command and Control Architecture

Real Clear Defense  |  Jessica Ho, Mark Montgomery

The United States Department of Defense is facing operational pressure to overhaul its fragmented command and control architecture by incorporating lessons from Ukraine’s combat-tested Delta system. Traditional American battle management relies on siloed networks like Link 16 and C2BMC, which create tactical data bottlenecks across service branches. To establish enterprise-wide interoperability, the Pentagon designated Palantir’s AI-driven Maven Smart System in March 2026 as the backbone for its Combined Joint All-Domain Command and Control operational framework.

However, incorporating thousands of discrete sensor streams across legacy service protocols remains a primary hurdle alongside training 1.3 million active-duty personnel. A 2025 Government Accountability Office report highlighted ongoing difficulties in tracking joint command integration, raising concerns over implementation discipline. To match Ukraine’s success—where Delta autonomously detects targets and integrates with foreign platforms like Poland’s TOPAZ artillery system—the Pentagon must enforce strict cross-service data standards and ensure seamless allied platform integration.

Comment

The tactical bottleneck in legacy battle management stems from data translation overhead between incompatible node protocols rather than bandwidth limits alone. When Link 16 networks exchange sensor tracks with Navy Aegis combat systems or Army C2BMC nodes, information must pass through custom translation gateways that introduce latency into time-sensitive targeting cycles. Ukraine’s operational deployment of the Delta C2 architecture bypassed this structural friction by establishing an enterprise-wide cloud layer where sensors publish raw feeds directly to a shared operating picture.

Transitioning the U.S. military to Palantir’s Maven Smart System requires resolving who holds binding authority over sensor data validation across service boundaries. Without unified data governance, service-level fire direction centres will continue to prioritise internal operational pictures over joint CJADC2 air-ground kill chains. In combined operations, this friction compounds when integrating allied strike systems like Poland’s TOPAZ, where fire control loops depend on unmediated target handoffs.

Strategic Question for Discussion

If Palantir's Maven Smart System is successfully adopted as the CJADC2 standard, which factor will present the greater barrier to combined fire support—service-level data classification protocols or the operational integration of allied fire control networks like Poland's TOPAZ?

The available evidence points toward service-level data classification as the initial operational barrier, as legacy security boundaries frequently impede real-time sensor sharing across U.S. branches. Once internal joint access is resolved, the primary bottleneck will shift toward integrating external NATO platforms, where fire control handoffs like those in Poland's TOPAZ system require reciprocal cryptographic standards. Consequently, technical cloud unification under Maven Smart System will likely outpace the procedural reform required for coalition multi-domain targeting.

Share your assessment in the comments below.

To read in details click here