1. An Enterprise Approach for Meeting Satellite Data and Product Distribution and Access Requirements
Reginald Lawrence, NOAA/NESDIS/OSD
NOAA Direct Readout Conference
April 2011

2. Presentation Outline What is GAS?
Operational Distribution & Access Systems to Satellite Data and Products – Current Subsystems
Operational Distribution & Access Systems to Satellite Data and Products – Future Subsystems
Evolutionary Path
Impacts
Schedule

3. What is GAS?
GAS, by definition, is the GOES R-Series Ground Segment Access Subsystem
GAS will become a part of the consolidated enterprise solution for the Environmental Satellite Processing Center (ESPC) future operational Product Distribution and Access (PDA) subsystem

4. NESDIS Operations - CURRENT
ESPC
GOES - Geostationary Observational
Environmental Satellite
POES - Polar-orbiting Observational

5. Environmental Satellite Processing Center (ESPC) Segments

6. Current/Planned Distribution and Access
Current GOES and POES (both NOAA and non-NOAA assets) distribution and access of data and products are provided via several legacy operational ESPC subsystems including SATEPSDIST systems and the Data Distribution System (DDS)
GOES data to the NWS is primarily through the GOES Ingest and NOAAPORT Interface (GINI)
SATEPDIST subsystems are Man Computer Interactive Data Access System (McIDAS) based, allowing users to pull data via McIDAS Abstract Data Distribution Environment (ADDE) commands
DDS subsystems provide primary access and distribution of POES data and products
DDS is primarily built with Perl scripts and tables, requiring operator action to support new subscription and ad hoc requests.
McIDAS is not simply a satellite data format, it is rather a suite of applications for analyzing and displaying meteorological data for research and education. McIDAS has been in use and under continual development by the University of Wisconsin-Madison Space Science and Engineering Center (SSEC) since The Unidata McIDAS software (a superset of SSEC McIDAS) has been under development since 1985 and in distribution since The software can be used with conventional observational, satellite, and grid-point data. Unidata distributes a version of McIDAS (McIDAS-X) for a variety of platforms running Unix, Linux, and MacOS-X.

7. Current/Planned Distribution and Access
Previous plans called for the new GOES R-Series (GOES-R) and Joint Polar Satellite System (JPSS) missions to provide their own separate distribution and access systems: GOES-R Access Subsystem (GAS) and NPOESS Data Exploitation (NDE), respectively
Plans are now to consolidate legacy and future mission distribution subsystems into an enterprise solution for ESPC operations
DDS is primarily built with Perl scripts and tables, requiring operator action to support new subscription and ad hoc requests.
McIDAS is not simply a satellite data format, it is rather a suite of applications for analyzing and displaying meteorological data for research and education. McIDAS has been in use and under continual development by the University of Wisconsin-Madison Space Science and Engineering Center (SSEC) since The Unidata McIDAS software (a superset of SSEC McIDAS) has been under development since 1985 and in distribution since The software can be used with conventional observational, satellite, and grid-point data. Unidata distributes a version of McIDAS (McIDAS-X) for a variety of platforms running Unix, Linux, and MacOS-X.

8. Issues
NESDIS understood that uncoordinated project development activities conducted without consideration of legacy operations leads to operational ‘stove pipes’
Parallel development of an enterprise solution creates risks for the Project Manager because project success is dependent on the success of the enterprise effort
User
Ingest
Product
Generation
Impact of ‘Stove Pipes’
Increased operational cost for training and sparing
Increased sustainment costs

9. Moving to an Enterprise Solution
Decision made to incorporate all required distribution and access functionality within an enterprise solution: Product Distribution and Access (PDA)
Identify PDA enterprise and project-unique requirements from the comprehensive set of the legacy, GOES-R, and NDE requirements
Capture project schedule needs and constraints (e.g., reviews, integration and test, operational capability)
Derived enterprise PDA services
Receive Data (push and pull)
Route Data (to users and storage)
Subscription Services
Distribute Data (includes user interface)
Store Data (internal short term and interface to CLASS)
Support Future Data and Product Enhancements (additional external data processing)
Identify any functional, performance, constraint, and interface requirements substantially different between the legacy requirements, NDE Specifications, and the functional and performance specification requirements levied on GAS.
Requirements traceability facilitated through use of the IBM Rational Dynamic Object-Oriented Requirements System (DOORS) software.

10. Moving to an Enterprise Solution
System acquisition planned through the NESDIS Office of System Development (OSD) Environmental Satellite Processing and Distribution System (ESPDS) Development contract
Acquisition approach focused on ensuring planned project schedule needs are met
Phased enterprise evolution
Incremental development and delivery
Service oriented architecture planned to accommodate new missions or new mission needs

11. PDA Evolution Plan Notes:
The first operational PDA will be delivered in Phase II. The Phase 1 PDA prototype will be used operationally for NDE. Components of the Phase 1 NDE PDA prototype are planned to be used in the Phase II PDA design.
NDE (NPP) and Legacy operations will transition to the Phase II PDA after GOES-R check out and operations.

12. NESDIS & NWS Satellite Product Data Flow – As Is

13. NESDIS & NWS Satellite Product Data Flow – Planned 2013

14. NESDIS & NWS Satellite Product Data Flow – Planned 2015

15. GOES-R Notional Architecture

16. Backup Slides

17. ESPDS Program Milestones As of April 1, 2011

18. Functional Analysis & Decomposition Process to Develop Legacy Requirements
PDA Functional Model
Capture all functions for data product access & distribution
Identify missing functions and requirements