Kristen Smith 
- Veal argues that connected systems alone do not make data usable
- Three JADC2 readiness tests cover data mapping, correlation speed and traceability
- Battlefield information dominance will take center stage at the Potomac Officers Club’s 2027 Defense R&D Summit
Measuring Joint All-Domain Command and Control progress by what reaches a commander’s screen misses where the capability actually succeeds or fails, according to Cloudera‘s Jonathan Veal.
The group vice president for defense and intelligence laid out his case in a blog post published in October, arguing that a complete operating picture, faster alerts and better recommendations all depend on what happens before information arrives at the interface. Connecting more systems is part of the JADC2 architecture, he wrote, but connection alone does not make data useful to someone deciding what to do.
Battlefield information dominance and assured connectivity will take center stage at the Potomac Officers Club’s 2027 Defense R&D Summit, to be held Feb. 4 in Virginia. The day’s agenda also features dedicated sessions on artificial intelligence and advanced space technologies. Register today to secure your seat.
What Are the Three JADC2 Readiness Tests?
Veal frames JADC2 readiness around three questions, each aimed at a different failure point:
- Can you see where mission-critical data lives and how it moves? Veal recommends picking a mission-critical decision and working backward to the systems holding what it depends on, looking for where the path slows and what happens when information crosses formats, classifications or security domains. Teams once bridged those gaps by knowing which system to check or whom to call, he wrote, but those workarounds lose viability as data volume and velocity climb.
- Can you connect the dots fast enough to matter? A vessel changing course signals little on its own, in Veal’s example. Set against new satellite imagery, known activity patterns and recent intelligence, it may warrant attention. He locates the value in correlation — pulling those signals together within the decision window — and notes that a system can produce the right answer yet still do so too late.
- Can an operator trust what they’re seeing? Veal lists four things an operator needs before acting on a recommendation drawn from several systems: where the information originated, what happened to it along the way, when it was last updated, and whether it is appropriate for that user and mission context. Operational pressure leaves no time to trace that chain back manually, he wrote.
Veal highlights Cloudera’s automated data lineage capabilities, which harvest metadata and generate lineage graphs, noting that they could help preserve contextual records without requiring operators to manually reconstruct information flows or navigate complex access policies.
Why Does Coalition C2 Make the Problem Harder?
Integrating allied and coalition partners expands the number of disparate systems, security domains, classification levels, and access policies, creating complex friction points across national boundaries.
Veal noted that while manual workarounds remain manageable across two internal systems, they collapse when mission decisions rely on 10 systems spanning three partner nations with distinct security privileges. Expanding the enterprise architecture without addressing these core data fundamentals multiplies existing vulnerabilities, he explained.
How Much Is the Pentagon Spending on Joint Command and Control?
The Department of War requested more than $2 billion for its Mission Command Applications program in fiscal 2027, a sharp step up from roughly $240 million in fiscal 2026 and $103 million the year before, DefenseScoop reported in May. DOW plans to request more than $1.9 billion annually for the program through fiscal 2031. Budget materials tie the increase to moving joint command and control from fragmented deployments to enterprise tooling supported across all domains.
The Government Accountability Office reported in April 2025 that DOW had not established a framework to guide CJADC2 investments or to track progress against its goals, noting that military departments were pursuing independent data integration efforts in parallel. GAO identified overly restrictive data classification as a significant obstacle to sharing command and control data, and said officials it interviewed were unaware of any entity working on a solution. CJADC2 leadership told GAO that addressing such challenges fell outside its purview.
