Are we building the most advanced military in history, or just a really expensive collection of incompatible gadgets? The Department of Defense is pouring billions into cutting-edge technologies – artificial intelligence, data meshes, secure networks – all geared towards a faster, more resilient battlefield. But the real story here isn't acquiring the tools; it’s connecting them. We’re facing an “integration gap” that threatens to render these investments little more than sophisticated science projects, unable to deliver real-world combat capability.
The echoes of past defense anxieties are unsettlingly familiar. In the 1950s, American strategists fretted over a “bomber gap” and then a “missile gap,” driving massive spending that ultimately built a credible nuclear deterrent. Today, the perceived deficit isn’t in raw capability, but in the ability to use what we already have. Major Ryan McLean, a flight test engineer at the Air National Guard Air Force Reserve Command Test Center and a veteran of fourteen years building command-and-control technologies, argues the joint force’s greatest risk isn’t a funding gap, but this crippling integration problem.
Source material: mwi.westpoint.edu.
This isn’t about a lack of investment. The money is flowing. The Army’s Next Generation Command and Control, the combatant commands’ Global Information Dominance Experiment, and the Marine Corps’ Project Dynamis are just a few examples of major initiatives designed to modernize warfighting. But these efforts are hampered by a fundamental disconnect: the inability to seamlessly share data and coordinate actions across different systems. Three foundational technologies – enterprise ontology management, conflict-free replicated data types (CRDTs), and zero-trust network architecture – are proliferating, yet remain frustratingly siloed.
Think of it like building a smart home. You can buy a smart thermostat, smart lights, and a smart security system, but if they all speak different languages, you’re left with a collection of expensive, unconnected devices. The Department of Defense is making the same mistake, acquiring brilliant components without ensuring they can communicate effectively. McLean points to ontology management – essentially a shared vocabulary for machines – as a key piece of the puzzle. The Chief Digital and AI Office (CDAO) is funding the Maven Smart System, a $1.3 billion contract aimed at scaling this capability across the military, while the Army awarded Palantir a $10 billion contract to consolidate seventy-five existing contracts under a single data platform. These are significant investments, but they won’t deliver on their promise if the underlying data models remain fragmented and inaccessible.
The problem isn’t a lack of standards, but their fragmented implementation. Standards like the Open Mission Network Interface have gained traction because they’re published as code, readily available to developers. However, critical specifications are often buried in disparate repositories, locked behind access restrictions, and published as static PDF documents – machine-unfriendly and difficult to integrate. A software engineer at Fort Bragg and a data officer at Indo-Pacific Command might independently solve the same integration problem simply because they can’t easily discover what the other has already built. This isn’t a technical limitation; it’s an organizational failure.
The Department of Defense’s push for a “first preference for commercial solutions” is laudable, but it’s undermined by this integration bottleneck. The 2025 executive order on defense acquisition reform aims to accelerate innovation, but without a streamlined process for integrating commercial technologies, these efforts risk becoming isolated experiments. Warfighters need fielded, sustained capabilities, not perpetual beta tests. The current operational test and evaluation framework, designed for traditional hardware programs, is ill-equipped to assess the rapid iteration cycles of commercial software.
McLean proposes three concrete steps to close the integration gap. First, establish a unified, accessible code repository and data model registry. Second, publish critical interoperability standards in machine-readable formats with open access for developers. Third, modernize the operational test and evaluation process to keep pace with the speed of commercial innovation. These aren’t revolutionary ideas, but they require a fundamental shift in mindset – a commitment to interoperability as a core principle, not an afterthought.
The stakes are high. A data mesh that connects the global sensing enterprise with the tactical shooter enterprise – replacing the outdated hub-and-spoke model – is essential for achieving the Joint Warfighting Concept’s vision of a faster, more resilient battlefield. But that vision will remain just that – a vision – unless the Department of Defense prioritizes integration. The tools are arriving. The question now is whether we can connect them before a potential adversary exploits our fragmented systems.
Watch for this: in the next eighteen months, pay attention to whether the CDAO can successfully establish a truly unified data model registry, accessible to both government and commercial developers. If it remains a fragmented collection of siloed repositories, the integration gap will widen, and the billions invested in modernization will yield a fraction of their potential return.
