IN43C-1749
Joint Polar Satellite System (JPSS) Common Ground System (CGS) Current Technical Performance Measures

Thursday, 17 December 2015
Poster Hall (Moscone South)
Milt Panas1, Michael L Jamilkowski2 and Shawn William Miller1, (1)Raytheon Company Aurora, Aurora, CO, United States, (2)Raytheon Company Riverdale, Riverdale, MD, United States
Abstract:
ABSTRACT

 

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). The Joint Polar Satellite System will replace the afternoon orbit component and ground processing system of the current Polar-orbiting Operational Environmental Satellites (POES) managed by NOAA. The JPSS satellites will carry a suite of sensors designed to collect meteorological, oceanographic, climatological and geophysical observations of the Earth.

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 multi-mission enterprise system serving NOAA, NASA and their national and international partners. 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 is being upgraded to Block 2.0 in 2015 to “operationalize” S-NPP, leverage lessons learned to date in multi-mission support, take advantage of more reliable and efficient technologies, and satisfy new requirements and constraints in the continually evolving budgetary environment. To ensure the CGS meets these needs, we have developed 49 Technical Performance Measures (TPMs) across 10 categories, such as data latency, operational availability and scalability.

This paper will provide an overview of the CGS Block 2.0 architecture, with particular focus on the 10 TPM categories listed above. We will provide updates on how we ensure the deployed architecture meets these TPMs to satisfy our multi-mission objectives with the deployment of Block 2.0.