Defense Primes Lock In DoD with Proprietary Data Formats and APIs

The five major defense primes (Lockheed Martin, RTX, Northrop Grumman, Boeing, and General Dynamics) routinely deliver weapons systems with proprietary data formats, closed interfaces, and contractual restrictions that prevent the government from modifying, maintaining, or integrating the systems without paying the original contractor. When the DoD wants to add a new sensor to an aircraft or update a ship's combat system, it must go back to the prime — often sole-source — at whatever price the prime sets. Technical data rights that should belong to the government are routinely negotiated away during contracting. This vendor lock-in costs the DoD billions annually in sustainment costs and, more importantly, prevents rapid capability integration. When a new threat emerges, the warfighter cannot quickly integrate a new electronic warfare pod or software update because the platform's interfaces are proprietary. The speed of capability delivery — the single most important factor in modern warfare — is held hostage by a contractor's business model. In Ukraine, forces modify commercial drones in days. The US military takes months to modify its own aircraft because it does not control the interfaces. The problem persists because of a fundamental misalignment of incentives in the defense contracting model. Primes bid low to win development contracts knowing they will make their profits in decades of sustainment. Proprietary lock-in is the mechanism that guarantees those sustainment profits. The DoD's contracting workforce is trained to evaluate lowest price technically acceptable (LPTA) bids, not total lifecycle cost including switching costs. Even when contracting officers understand the lock-in risk, they face pressure to award contracts quickly and lack the technical expertise to specify open interface requirements precisely enough to be enforceable. Congress has mandated modular open systems approaches (MOSA) since the FY2017 NDAA, and the DoD has published open architecture standards. But compliance is largely performative — primes deliver systems that technically meet open standards requirements while ensuring that the truly valuable integration logic remains proprietary. The government lacks the organic engineering talent to audit whether a delivered system is genuinely open or merely superficially compliant.