NPOESS Interface Data Processing Segment Architecture and Software
Abstract
The National Oceanic and Atmospheric Administration (NOAA), Department of Defense (DoD), and National Aeronautics and Space Administration (NASA) are jointly acquiring the next-generation weather and environmental satellite system; the National Polar-orbiting Operational Environmental Satellite System (NPOESS). NPOESS is an estimated \$6.5 billion program replacing the current Polar-orbiting Operational Environmental Satellites (POES) managed by NOAA and the Defense Meteorological Satellite Program (DMSP) managed by the DoD. The NPOESS satellites carry a suite of sensors that collect meteorological, oceanographic, climatological, and solar-geophysical observations of the earth, atmosphere, and space. The ground data processing segment for NPOESS is the Interface Data Processing Segment (IDPS). The IDPS processes NPOESS satellite data to provide weather, oceanographic, and environmental data products to NOAA and DoD processing centers and field terminals operated by the United States government. This paper describes Raytheon's high performance computer and software architecture for the NPOESS IDPS. NOAA, the DoD, and NASA selected this architecture after a 2.5-year Program Definition and Risk Reduction (PDRR) competition. The PDRR phase concluded in August of 2002, and has been followed by the NPOESS Preparatory Project (NPP) phase. The NPP satellite, scheduled to launch in late 2006, will provide risk reduction for the future NPOESS satellites, and will enable data continuity between the current EOS missions and NPOESS. Efforts within the PDRR and NPP phases consist of: requirements definition and flowdown from system to segment to subsystem, Object-Oriented (OO) software design, software code development, science to operational code conversion, integration and qualification testing. The NPOESS phase, which supports a constellation of three satellites, will also consist of this same lifecycle during the 2005 through 2009 timeframe, with operations and support efforts extending out to approximately the year 2020. The IDPS must process a data volume an order of magnitude greater than the current POES and DMSP systems and within significantly reduced processing times. This will also result in 3.8 TB of data during NPP and 7.8 TB of data during NPOESS delivered to the users on a daily basis. The IDPS architecture meets the following key NPOESS design requirements: · Daily processing of 650 GB of satellite data resulting in 3.8 (NPP)/ 7.8 (NPOESS) TB of data products · Generate 95% of the NPOESS data products within 5 minutes · Process and deliver data products for at least 99.99% of the NPOESS satellite data · A scalable architecture producing all NPOESS data products for the NOAA and DOD processing centers while also deploying the architecture on shipboard, battlefield, and mobile "laptop" field terminals · DII-COE compliant and Joint Technical Architecture Interoperability · Robust architecture exceeding an availability of 99.99% · Maximize use of COTS hardware and software This paper will describe the architecture approach to hardware and software that is necessary to meet these challenging NPOESS IDPS design requirements.
- Publication:
-
AGU Fall Meeting Abstracts
- Pub Date:
- December 2004
- Bibcode:
- 2004AGUFMSF23A0039T
- Keywords:
-
- 3360 Remote sensing;
- 4275 Remote sensing and electromagnetic processes (0689);
- 1640 Remote sensing