The Pentagon has reportedly ended OCX, the Next Generation Operational Control System meant to run the military’s GPS constellation, closing out what appears to be a 15-year acquisition effort that consumed billions of dollars and never produced an operational system. According to reports, the Department of Defense’s acquisition chief signed the termination in April at the recommendation of the Space Force’s acting acquisition executive, according to SpaceNews.

The decision closes what may be one of the most expensive software failures in Pentagon history and effectively concedes that the “big bang” modernization model no longer fits how the Space Force wants to buy technology.

A 15-year program that never went live

OCX was supposed to replace the aging Architecture Evolution Plan (AEP) ground system, plus a separate system handling launch, anomaly response and satellite disposal. The idea was clean: one modern command-and-control platform for both legacy GPS satellites and the new GPS III spacecraft now flying the encrypted, anti-jam M-code signals the military considers essential for modern warfare.

The execution was not clean. RTX (then Raytheon) reportedly won the contract in 2010 with an initial delivery target and price tag that would later prove unrealistic. By the time the Pentagon pulled the plug, budget projections had ballooned significantly, according to Ars Technica, with costs reportedly rivaling those of an entire fleet of replacement GPS satellites.

The Space Force formally accepted an initial version of the software in 2025 after years of factory testing. Then integrated testing began with real satellites, ground stations and user equipment. That is when the program effectively collapsed.

What broke in integration

Reports indicate that extensive system issues arose during the integrated testing of OCX with the broader GPS enterprise, with military officials noting problems across a broad range of capability areas that would put current GPS military and civilian capabilities at risk.

That last clause matters. Swapping in OCX wasn’t just failing to add capability — it threatened to degrade the GPS service that billions of civilian users and every branch of the U.S. military depend on every day. At that point, the math changes. You are no longer weighing new capability against cost. You are weighing new capability against the risk of breaking something that already works.

Military officials reportedly concluded that the work remaining on OCX, when compared with the current GPS control system capability, meant that additional investment in OCX was no longer the best solution.

The quiet winner: the system OCX was meant to replace

While OCX struggled, the Space Force kept patching AEP. Over the past decade, incremental upgrades let AEP support newer GPS III satellites and absorb functions originally assigned to OCX. The Space Force recently awarded contracts to keep that modernization going.

That dynamic — the legacy system quietly eating the replacement’s lunch — is not unique to GPS. It is a recurring pattern in Pentagon software acquisition, where the incumbent stack gets just enough investment to stay relevant while the flagship replacement drifts further off schedule. A Government Accountability Office review flagged OCX’s persistent software defect rate, poor acquisition decisions, and repeated failures to catch problems before they compounded. Reports suggest the Pentagon had considered canceling the program years earlier.

Why RTX isn’t entirely the story

It is tempting to frame OCX as a contractor failure. RTX delivered late, delivered buggy software, and delivered a system that couldn’t survive contact with the real GPS enterprise. In a statement acknowledging the cancellation, an RTX spokesperson said the company delivered the system in 2025 and has continued to support the Space Force in post-delivery activities, Aviation Week reported.

But framing this as just a vendor problem misses the more uncomfortable truth. The Pentagon designed OCX as a monolithic, all-or-nothing replacement for a system that had to remain live every single second. You cannot run a decade-long waterfall project against a moving target like GPS and expect the final integration to go smoothly. The architecture of the acquisition guaranteed that any discovered defect late in the program would be catastrophic, because there was no partial-delivery path.

The real signal: Pentagon acquisition is changing

The most important line in the Space Force’s announcement didn’t come from the GPS operations team. It came from senior acquisition officials emphasizing the importance of refining and updating acquisition processes to prioritize rapid, incremental capability delivery versus complex ‘all or nothing’ system deliveries, with the Department of Defense making clear that warfighting capability needs to be delivered at a faster rate.

Read that twice. Senior Pentagon officials are explicitly repudiating the monolithic program-of-record model that produced OCX, and by extension, programs like JSTARS recapitalization, NPOESS, and a long list of expensive software modernizations that never shipped.

This lines up with the broader policy direction the Space Force appears to be moving toward — smaller, faster, modular contracts, more commercial leverage, and a willingness to kill programs that no longer pencil out. The same philosophy appears to underpin recent initiatives in Space Force acquisition reform and the broader shift toward proliferated, commercially sourced space architectures.

What this means for the next generation of ground systems

The GPS constellation isn’t going anywhere. The satellites work. AEP, upgraded and patched, will keep flying them. The military’s next bet appears to be iterative improvement of what already works rather than another decade-long push to replace everything at once.

That is probably the right call, but it comes with a caveat. GPS III satellites carry capabilities — M-code, regional anti-jamming, higher-power signals — that were partly predicated on a more capable ground system. Incremental AEP upgrades have closed some of that gap. Whether they can close all of it, especially as adversaries invest in jamming and spoofing, is an open question.

The contractors who win work in this next phase will look different from the RTX of 2010. They will deliver software in months, not years. They will operate under contracts structured around capability increments rather than a single cliff-edge delivery. And they will be judged on whether their code actually runs alongside the existing system, not whether it passes factory acceptance tests in isolation.

OCX spent 15 years proving that the old way doesn’t work. The interesting question now is whether the Pentagon has actually learned it, or whether the next multi-billion dollar program is already being written somewhere in the same shape as the last one.

Photo by Sander on Pexels