April 2020 GPS SPS PS
5th Edition Page B-2
Long ago, the GPS Joint Program Office (JPO), which has been reorganized within SMC, began
developing all three segments of GPS. Although the United States Air Force (USAF) was the
executive service responsible for the JPO, the GPS JPO was truly a "joint" program office in that
it included members from all branches of the U.S. military and later grew to include personnel
from allied nations (with particularly strong participation from the North Atlantic Treaty
Organization [NATO] countries) and from other Departments of the USG. The GPS JPO not only
developed the initial Control, Space, and User Segments of GPS; the GPS JPO also operated
and maintained them as well. Around the end of the 1970s, the GPS JPO either owned or directly
controlled virtually every GPS receiver in the entire world. Back then it made sense to specify
GPS requirements in terms of the PVT performance seen by the end user since all three segments
were under GPS JPO control. The GPS receiver's displayed PVT was the final interface at the
end of the GPS process.
During the 1980s, the GPS JPO developed and deployed the Operational Control System (OCS)
which it initially ran before turning it over to Air Force Space Command (AFSPC), now the USSF.
The GPS JPO developed and began deploying the operational Block II series of satellites which
were then handed over to AFSPC for on-orbit operations and maintenance. The GPS JPO also
developed and procured many different types of PPS receivers which were delivered to the Army,
Navy, and Air Force, as well as other federal agencies and allied governments. Not all PPS
receivers were developed or produced by the GPS JPO, however. Programs with specialized
applications that required unique capabilities began developing and producing their own PPS
receivers. Some NATO governments also initiated their own PPS receiver development efforts.
A few civil electronics manufacturers even started producing and selling commercial SPS
receivers. Since the bulk of the world's GPS receivers were still configuration managed by the
GPS JPO, specifying GPS requirements in terms of the PVT performance delivered to the end
user still made sense. But as evidenced by the PPS user equivalent range error (UERE) budgets
which appeared at the end of the 1980s, it had become necessary to specify the PPS SIS
performance to accommodate those PPS receivers not developed by the GPS JPO.
By the late 1990s, most PPS receivers were being bought by military system integrators directly
from the manufacturer for use as a sensor embedded in other products. The GPS JPO was still
developing and procuring a few types of stand-alone PPS receivers for domestic use and foreign
military sales, but those were only a very small fraction of the world's production of PPS receivers.
More and more, PPS receivers have become just another component in integrated systems. End
users often do not see PPS-based PVT, they instead see navigation signals based on integrated
PPS-inertial, PPS-Doppler, or PPS-terrain matching. The PPS receivers embedded in these
systems are purchased, operated, and maintained by organizations other than SMC. Neither
SMC nor the Joint Service System Management Office (JSSMO) nor USSF’s 50
th
Space Wing
(50 SW), who are SMC’s partners for maintaining SMC-procured PPS receivers and for operating
and maintaining the Control/Space Segments respectively), are responsible for the performance
of these PPS receivers. SMC, JSSMO, and 50 SW responsibilities end at the PPS SIS interface
as shown in Figure B.1-1. The same principle applies to the huge number of SPS receivers
produced in the 1990s -- those SPS receivers are not purchased, operated, or maintained by the
GPS program organization; and the GPS program organization's responsibility towards those
SPS receivers ends at the SPS SIS interface.
The GPS program organizational line of demarcation is at the SPS SIS interface (and PPS SIS
interface) as shown in Figure B.1-1. Operating and maintaining the Control/Space Segments to
produce the SPS SIS is the responsibility of the GPS program organization. The SPS User
Segment is not the responsibility of the GPS program organization.