NPPNational Polar-orbiting Operational Environmental Satellite System Preparatory Project<br />Interface Data Processing  ...
IDP<br />@<br />Science <br />Centrals<br />Users<br />Field<br />Terminal<br />Software<br />NPP Mission Data Flow<br />C...
NPP Data Product Definitions<br />S<br />3<br />Comm<br />Comm<br />Comm<br /><br />  Data<br />  Store<br />C<br />Receiv...
Interfaces<br />Air Force Weather Agency (AFWA)<br />NOAA Satellite and Information Service (NESDIS)<br />Fleet Numerical ...
IDPS Functional Overview<br />Infrastructure<br />Data Delivery<br />Ingest<br />Data Management<br />Processing<br />Data...
I-P-O Construct<br /><ul><li>The current PRO design is based on an I-P-O model
Input (I) retrieves all needed input data
Processing (P) creates EDRs and IPs from the input data
Output (O) sends products and metadata to the DMS for storage, formatting & delivery
The use of modular software isolates impacts of changes to the basic architecture and provides for rapid, low impact recov...
Additionally, granule based processing allows the generation of high quality products within latency timelines
This construct allows the decoupling of algorithms from I/O</li></ul>Input<br />Output<br />Processing<br />
NPP EDRs<br />
Upcoming SlideShare
Loading in...5
×

MO3.L10 - NATIONAL POLAR-ORBITING OPERATIONAL ENVIRONMENTAL SATELLITE SYSTEM PREPARATORY PROJECT (NPP) INTERFACE DATA PROCESSING SEGMENT (IDPS)

751

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
751
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

MO3.L10 - NATIONAL POLAR-ORBITING OPERATIONAL ENVIRONMENTAL SATELLITE SYSTEM PREPARATORY PROJECT (NPP) INTERFACE DATA PROCESSING SEGMENT (IDPS)

  1. 1. NPPNational Polar-orbiting Operational Environmental Satellite System Preparatory Project<br />Interface Data Processing Segment (IDPS) <br />Joe Mulligan, IPO Ground Systems Division Deputy Chief <br />Marge Ripley, IPO IDPS IPT Lead <br />
  2. 2. IDP<br />@<br />Science <br />Centrals<br />Users<br />Field<br />Terminal<br />Software<br />NPP Mission Data Flow<br />C3S<br />C3S<br />IDP<br />IDP<br />Centrals <br />@<br />@<br />C3S<br />C3S<br />CONUS <br />CONUS <br />NPP Spacecraft<br />Space Vehicle 1<br />Svalbard <br />Ground<br />Centrals<br />Centrals<br />SMD<br />SMD<br />DHN & <br />DHN & <br />Gateways<br />Gateways<br />SMD<br />Ground<br />FEP<br />FEP<br />(4x)<br />(2x)<br />Receptor<br />CLASS<br />(@ IDPS)<br />(@ IDPS)<br />Bus<br />Sensors<br />Sensors<br />Bus<br />Mission <br />Mission <br />SDS<br />Ground<br />Management <br />Management <br />Station<br />Center<br />Center<br />IDPS<br />IDPS<br />Stored Mission Data flow for<br />Centrals and Science Data Users <br />Deliver Data<br />Products<br />HRD<br />Field <br />Users<br />Field<br />Field<br />Terminal<br />Terminal<br />Software<br />Software<br />Field Terminals (LRD, HRD)<br />Field Terminals (HRD)<br />Deliver Data<br />Products<br />HRD Data flow for <br />Field Users<br />Timely, Accurate, Reliable Data from Sensors to Users<br />
  3. 3. NPP Data Product Definitions<br />S<br />3<br />Comm<br />Comm<br />Comm<br /><br /> Data<br /> Store<br />C<br />Receiver<br />Processing<br />Xmitter<br />CCSDS Level<br />SPACE SEGMENT<br />CCSDS (mux, code, frame) <br />Packetization<br />IDPS<br />RDR<br />Production<br />RDR Level<br />Compression<br />SENSORS<br />Anc.<br />Sensor<br />A/D Conversion<br />OTHER<br />Data<br />SUBSYSTEMS<br />SDR<br />Production<br />Cal.<br />Source<br />SDR Level<br />ENVIRONMENTAL<br />EDR<br />SOURCE<br />Production<br />EDR Level<br />COMPONENTS<br />
  4. 4. Interfaces<br />Air Force Weather Agency (AFWA)<br />NOAA Satellite and Information Service (NESDIS)<br />Fleet Numerical Meteorology and Oceanography Center (FNMOC)<br />Naval Oceanographic Office (NAVO)<br />NPOESS Preparatory Project (NPP) Science Data<br />Segment (SDS)<br />Comprehensive Large Array-data Stewardship System (CLASS)<br />NASA’s Science Data Segment will independently assess the quality of the science and environmental data records from the NPP mission for their ability to support climate research.<br />All data products will be provided to NOAA’s Comprehensive Large-Array data Stewardship System (CLASS) for distribution to the broader scientific user community.<br />The plan for the follow on mission is to add two more Centrals: FNMOC and NAVO.<br />NPP will provide data for processing at each of the two centrals: AFWA and NESDIS. Each Central will then disseminate the data to their user communities.<br />The data products generated on IDPS are delivered to the Centrals, CLASS and SDS based on their data subscriptions.<br />
  5. 5. IDPS Functional Overview<br />Infrastructure<br />Data Delivery<br />Ingest<br />Data Management<br />Processing<br />Data <br />Quality<br />Monitor<br />The Infrastructure subsystem manages IDPS by initiating tasks, monitoring processes, monitoring product generation, and maintaining log files of Status, Error, and Informational messages. It also provides common utilities, tools and a scheduler. It interfaces with NPOESS Enterprise Management (EM) as well as providing the main GUI for IDP Operator management, control and status.<br />The Ingest subsystem is the primary input path for data into IDPS. Stored Mission Data and Mission Support Data are ingested and used to create Raw Data Records (RDRs).<br />The Interface Data Processing Segment (IDPS) consists of the data processing elements (DPEs) located at each of the four Centrals to generate and deliver NPOESS and NPP products and associated metadata to the Centrals for additional application specific processing and dissemination. Each IDPS consists of six subsystems: Infrastructure, Ingest, Processing, Data Management, Data Delivery and Data Quality Monitoring. <br />The Data Delivery Subsystem is the primary mechanism for data delivery. Users have the capability to submit data requests via a GUI or use of an API. HDF5 formatting, packaging and aggregation of NPOESS Data products is performed. <br />The Processing (PRO) subsystem performs the data processing for product generation. PRO takes RDRs, ancillary (ANC) and auxiliary (AUX) data as inputs to generate Sensor Data Records (SDRs), Temperature Data Records (TDRs), geolocation information, Intermediate Products (IPs), and Environmental Data Records (EDRs). PRO assesses the data quality of the SDR, TDR, and EDRs and sends real-time quality notifications to the Data Quality Monitoring (DQM) subsystem to alert the operators of possible quality degradation.<br />The Data Management Subsystem manages the data within IDPS. Its primary function is sharing data between processes and the other subsystems. It provides on-line repository of data, inventory and metadata.<br />DQM performs quality monitoring of the data products. It allows automated and ad-hoc processing in support of data quality notifications from the PRO subsystem. It also provides the interface and tools for the data quality engineers to analyze the data and generate reports. This subsystem is implemented only at the NESDIS.<br />
  6. 6. I-P-O Construct<br /><ul><li>The current PRO design is based on an I-P-O model
  7. 7. Input (I) retrieves all needed input data
  8. 8. Processing (P) creates EDRs and IPs from the input data
  9. 9. Output (O) sends products and metadata to the DMS for storage, formatting & delivery
  10. 10. The use of modular software isolates impacts of changes to the basic architecture and provides for rapid, low impact recovery from hardware and software failures
  11. 11. Additionally, granule based processing allows the generation of high quality products within latency timelines
  12. 12. This construct allows the decoupling of algorithms from I/O</li></ul>Input<br />Output<br />Processing<br />
  13. 13. NPP EDRs<br />
  14. 14. NPP System Latency<br />
  15. 15. IDPS Data Latency<br />IDPS is optimized to reach data latency requirements<br />
  16. 16. IDPS IBM Architecture<br /><ul><li>Each Central will have an IDPS
  17. 17. High performance IBM computing hardware
  18. 18. POWER architecture
  19. 19. Consists of two hardware suites
  20. 20. Operational string
  21. 21. Integration and Test string</li></li></ul><li>IDPS Flexibility<br /><ul><li>The HW is scalable and expandable
  22. 22. Can add new capabilities without impacting the existing system
  23. 23. Combiningsoftware and hardware flexibility and robustness
  24. 24. Allows stringent performance requirements to be met
  25. 25. Fault tolerant hardware and software
  26. 26. Ensures high quality data products
  27. 27. Available to users within operational latency timelines</li></li></ul><li>Summary<br /><ul><li>IDPS generates the data products for end users.
  28. 28. Central Users will get data directly from IDPS
  29. 29. Science Users will get data from CLASS
  30. 30. SDS will get data directly from IDPS
  31. 31. 25 EDRs will be produced by IDPS
  32. 32. IDPS is meeting Latency requirements
  33. 33. IDPS is installed at AFWA and NESDIS and is currently undergoing system level testing in preparation for launch.</li></li></ul><li>Questions ?<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×