One of the long-standing issues for support of IIA vehicles after the future GPS Operational Ground Control Segment’s (OCX’s) ready-to-operate (RTO) date, which should fall in December 2016 at the latest, is what ground command-and-control (C2) system will steer GPS IIA satellites, do navigation uploads, and so on. The issue is that AEP, the current C2 system, will no longer be available once the transition to OCX takes place, and OCX has no requirement to control IIA satellites.
The OCX program, which struggled early, is now under new Program leadership within Raytheon Space Systems, and while Ray Kolibaba, the new OCX program manager, is making great progress, OCX does not need to be burdened with additional requirements at this stage of the program.
Just how big an issue is GPS IIA C2? Initially the Aerospace projections were that there would only be one or two GPS IIAs left on orbit in 2017, and it was not worth the costs to include the C2 software for the legacy system in the new software code. However, I have long maintained that Aerospace and Space Missile Systems Command (SMC) neglected to count the residual satellites, maintained by Launch, Anomaly, and Disposal Operations (LADO), which might very well actually amount to 3–4 additional IIAs. Added to the two IIAs on orbit, this could amount to six IIA SVs that need to be maintained.
The solution announced during the National Space Symposium (NSS, April 16–19) by General William Shelton, the four-star chief of Air Force Space Command, is to fund the current LADO operator, Braxton Technologies, to build in this support for the IIAs. This is significant for several reasons: One of course is that it solves the IIA C2 issues, it does it now, and at a relatively modest cost, and it utilizes more of the capabilities of the Braxton Technologies’ LADO software. Additionally it provides a true backup capability for assets on orbit that become increasingly valuable as the number of available launch slots for GPS decreases.
Braxton Technologies initially demonstrated this capability years ago in a lifeboat drill during the transition to AEP, but the navigation upload capability was never maintained for LADO after the successful transition. This is certainly a step in the right direction and provides a simple solution to a vexing problem that has plagued the GPS program for the last several years.