Original broadcast 6/24/25
Presented by HII Mission Technologies
Garry Schwartz, Chief Operating Officer at HII Mission Technologies, provides a grounded and deeply experienced perspective on the Department of Defense's evolving vision for Combined Joint All-Domain Command and Control, or CJADC2. In a candid conversation for DefenseTech TV, Schwartz breaks down the difference between JADC2—the U.S.-only warfighting concept—and CJADC2, which incorporates coalition and allied forces. His message is clear: the ambition is high, but the technical and operational integration required to bring the vision to life is still in its early stages.
"CJADC2 isn't a thing," Schwartz notes. "It's not a system. It's a suite of capabilities—many still in PowerPoint." The promise of interconnected systems that can sense, decide, and act with speed across domains is real, but as Schwartz explains, we're still solving basic challenges around how to move the right data to the right systems at the right time.
The conversation begins with a framing of what CJADC2 must achieve: true interoperability between U.S. and allied systems, delivering real-time data exchange and decision-making capabilities. Yet the legacy architectures that support today’s platforms were never built with this in mind. Most are built for specific functions and data types, not the many-to-many communications required for multi-domain operations. Schwartz underscores that the term "CJADC2" implies the need to go beyond U.S. capabilities to support combined operations with coalition partners. The "C" for combined, he points out, introduces exponential complexity, especially when operating in contested environments.
Schwartz argues that much of the current integration work is still focused on "individual threads" rather than a unified, adaptable fabric. While discussions of AI and data mesh architectures are encouraging, the operational realities are still a long way from the vision. A truly flexible, AI-assisted data environment must be able to recognize system needs, identify what’s missing, translate formats dynamically, and route information reliably even under contested or degraded conditions.
He also acknowledges the tension between strict standards and practical field performance. While rigid gateways and specifications were once the norm, Schwartz contends they no longer serve today’s fast-paced battlefield environment. Instead, AI and machine learning tools that understand system requirements and network realities are needed to facilitate rapid adaptation.
"We're finally at a point," Schwartz says, "where it's less about rigid standards and more about having these kinds of automatic abilities within AI/ML to work the translation."
Equally important is the question of ownership: who drives the architecture? Schwartz calls out the long-standing chicken-and-egg dilemma between industry innovation and government directives. Defense leaders with technical or operational backgrounds bring different assumptions to the table, and that diversity must be harnessed through open dialogue and experimentation.
This underscores the value of initiatives like the Chief Digital and AI Office (CDAO) and a federated approach to experimentation. Industry brings dual-use innovation and technical insight, while defense experts offer operational context and mission alignment. Bringing these together through coordinated trials can narrow down viable solutions without over-constraining innovation. Schwartz advocates for small-group experimentation governed by broader shared objectives, where new technologies can be tested and either validated or quickly discarded.
He also touches on the organizational dynamics affecting CJADC2. With administration changes and agency realignments, priorities can shift quickly. "There’s a lot of resetting going on," he observes, adding that leadership clarity is key to progress. When multiple services develop their own systems in isolation, even under a shared concept, integration often falters. Schwartz calls for a unifying layer—a shared infrastructure or approach that ties service-specific solutions into a coherent whole.
Schwartz also highlights HII's contribution through the Mission Partner Environment (MPE)—a key enabler of the "C" in CJADC2. MPE facilitates secure data exchange with coalition partners, using a cloud-based data platform called IONIC. Designed to protect data and ensure secure transmission, this architecture could eventually scale to support broader command and control applications. The IONIC platform, built with scalability in mind, is currently being used to support cybersecurity elements within the MPE but has potential for broader data fabric implementation.
Ultimately, Schwartz’s message is one of cautious optimism. There is progress. The technology is evolving. AI capabilities are becoming more robust. But to achieve CJADC2 in practice, the defense community must remain flexible, collaborative, and focused on realistic, field-ready solutions.
"We've taken steps," he concludes, "but we're still solving the problem one thread at a time."
Key Takeaways:
-
CJADC2 is a vision, not yet a functioning system. Interoperability remains the core challenge.
-
AI/ML should replace rigid standards to handle real-time data translation and adaptability.
-
A federated approach to experimentation can help align government needs with industry innovation.
-
The Mission Partner Environment is an early step in enabling coalition-level data sharing.
Excerpts from this conversation are featured on DefenseTech TV. Watch the full program at DefenseTech.TV.