• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
MO3.L10 - NATIONAL POLAR-ORBITING OPERATIONAL ENVIRONMENTAL SATELLITE SYSTEM PREPARATORY PROJECT (NPP) INTERFACE DATA PROCESSING SEGMENT (IDPS)
 

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

on

  • 910 views

 

Statistics

Views

Total Views
910
Views on SlideShare
910
Embed Views
0

Actions

Likes
0
Downloads
10
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

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

    • NPPNational Polar-orbiting Operational Environmental Satellite System Preparatory Project
      Interface Data Processing Segment (IDPS)
      Joe Mulligan, IPO Ground Systems Division Deputy Chief
      Marge Ripley, IPO IDPS IPT Lead
    • IDP
      @
      Science
      Centrals
      Users
      Field
      Terminal
      Software
      NPP Mission Data Flow
      C3S
      C3S
      IDP
      IDP
      Centrals
      @
      @
      C3S
      C3S
      CONUS
      CONUS
      NPP Spacecraft
      Space Vehicle 1
      Svalbard
      Ground
      Centrals
      Centrals
      SMD
      SMD
      DHN &
      DHN &
      Gateways
      Gateways
      SMD
      Ground
      FEP
      FEP
      (4x)
      (2x)
      Receptor
      CLASS
      (@ IDPS)
      (@ IDPS)
      Bus
      Sensors
      Sensors
      Bus
      Mission
      Mission
      SDS
      Ground
      Management
      Management
      Station
      Center
      Center
      IDPS
      IDPS
      Stored Mission Data flow for
      Centrals and Science Data Users
      Deliver Data
      Products
      HRD
      Field
      Users
      Field
      Field
      Terminal
      Terminal
      Software
      Software
      Field Terminals (LRD, HRD)
      Field Terminals (HRD)
      Deliver Data
      Products
      HRD Data flow for
      Field Users
      Timely, Accurate, Reliable Data from Sensors to Users
    • NPP Data Product Definitions
      S
      3
      Comm
      Comm
      Comm

      Data
      Store
      C
      Receiver
      Processing
      Xmitter
      CCSDS Level
      SPACE SEGMENT
      CCSDS (mux, code, frame)
      Packetization
      IDPS
      RDR
      Production
      RDR Level
      Compression
      SENSORS
      Anc.
      Sensor
      A/D Conversion
      OTHER
      Data
      SUBSYSTEMS
      SDR
      Production
      Cal.
      Source
      SDR Level
      ENVIRONMENTAL
      EDR
      SOURCE
      Production
      EDR Level
      COMPONENTS
    • Interfaces
      Air Force Weather Agency (AFWA)
      NOAA Satellite and Information Service (NESDIS)
      Fleet Numerical Meteorology and Oceanography Center (FNMOC)
      Naval Oceanographic Office (NAVO)
      NPOESS Preparatory Project (NPP) Science Data
      Segment (SDS)
      Comprehensive Large Array-data Stewardship System (CLASS)
      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.
      All data products will be provided to NOAA’s Comprehensive Large-Array data Stewardship System (CLASS) for distribution to the broader scientific user community.
      The plan for the follow on mission is to add two more Centrals: FNMOC and NAVO.
      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.
      The data products generated on IDPS are delivered to the Centrals, CLASS and SDS based on their data subscriptions.
    • IDPS Functional Overview
      Infrastructure
      Data Delivery
      Ingest
      Data Management
      Processing
      Data
      Quality
      Monitor
      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.
      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).
      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.
      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.
      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.
      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.
      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.
    • I-P-O Construct
      • 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 recovery from hardware and software failures
      • Additionally, granule based processing allows the generation of high quality products within latency timelines
      • This construct allows the decoupling of algorithms from I/O
      Input
      Output
      Processing
    • NPP EDRs
    • NPP System Latency
    • IDPS Data Latency
      IDPS is optimized to reach data latency requirements
    • IDPS IBM Architecture
      • Each Central will have an IDPS
      • High performance IBM computing hardware
      • POWER architecture
      • Consists of two hardware suites
      • Operational string
      • Integration and Test string
    • IDPS Flexibility
      • The HW is scalable and expandable
      • Can add new capabilities without impacting the existing system
      • Combiningsoftware and hardware flexibility and robustness
      • Allows stringent performance requirements to be met
      • Fault tolerant hardware and software
      • Ensures high quality data products
      • Available to users within operational latency timelines
    • Summary
      • IDPS generates the data products for end users.
      • Central Users will get data directly from IDPS
      • Science Users will get data from CLASS
      • SDS will get data directly from IDPS
      • 25 EDRs will be produced by IDPS
      • IDPS is meeting Latency requirements
      • IDPS is installed at AFWA and NESDIS and is currently undergoing system level testing in preparation for launch.
    • Questions ?