243 Joint Polar Satellite System (JPSS) Common Ground System (CGS) Technical Performance Measures of the Block 2 Architecture

Monday, 23 January 2017
4E (Washington State Convention Center )
Kerry Grant, Raytheon Company, Aurora, CO; and S. W. Miller and M. Panas

The National Oceanic and Atmospheric Administration (NOAA) and National Aeronautics and Space Administration (NASA) are jointly acquiring the next-generation civilian weather and environmental satellite system: the Joint Polar Satellite System (JPSS).   JPSS replaced the afternoon orbit component and ground processing of NOAA’s old POES system. JPSS satellites carry sensors that collect meteorological, oceanographic, climatological, and solar-geophysical observations of the earth, atmosphere, and space.  The ground processing system for JPSS is known as the JPSS Common Ground System (JPSS CGS). Developed and maintained by Raytheon Intelligence, Information and Services (IIS), the CGS is a globally distributed, multi-mission system serving NOAA, NASA and their national and international partners, such as NASA’s Earth Observation System (EOS), NOAA’s current POES, the Japan Aerospace Exploration Agency’s (JAXA) Global Change Observation Mission – Water (GCOM-W1), and DoD’s Defense Meteorological Satellite Program (DMSP). The CGS has demonstrated its scalability and flexibility to incorporate multiple missions efficiently and with minimal cost, schedule and risk, while strengthening global partnerships in weather and environmental monitoring. The CGS architecture has been upgraded to Block 2.0 to satisfy several key objectives, including: “operationalizing” the first satellite, Suomi NPP, which originally was a risk reduction mission; leveraging lessons learned in multi-mission support, taking advantage of newer, more reliable and efficient technologies and satisfying constraints due of the continually evolving budgetary environment. To ensure the CGS meets these needs, we have developed 48 Technical Performance Measures (TPMs) across 9 categories: Data Availability, Data Latency, Operational Availability, Margin, Scalability, Situational Awareness, Transition (between environments and sites), WAN Efficiency, and Data Recovery Processing. This paper will provide an overview of the CGS Block 2.0 architecture, with particular focus on the 9 TPM categories listed above. We will describe how we ensure the deployed architecture meets these TPMs to satisfy our multi-mission objectives with the deployment of Block 2.0
- Indicates paper has been withdrawn from meeting
- Indicates an Award Winner