Presented by Robert Rank, NOAA/NESDIS/OSD/GSD Co Authors: Scott - - PowerPoint PPT Presentation

Presented by Robert Rank, NOAA/NESDIS/OSD/GSD Co‐Authors: Scott McCormick, Global Science & Technology Constantino Cremidis, CSC

1

Topics

Methodology

Collaborative Teams Approach CLASS Experience with New Campaigns Opportunities for Improvement

Central Conclusions

2

NOAA’s IT Enterprise Solution

Comprehensive Large Array‐data Stewardship System

CLASS has been designated as NOAA’s enterprise‐wide

information technology system designed to support long‐ term, secure preservation, and standards‐based access to environmental data collections and information.

This system, owned and operated by the NOAA National

Data Centers, supports the ingest, quality control, archival storage of and public access to data and science information.

3

CLASS Team Formation

The Requirements Definition Team (RDT) and the

System Engineering Team have a pool of requirements engineers and system engineers from which we form a dedicated team to coordinate the initial phases of each new campaign

This team works with the NOAA National Data

Centers and with the data provider to build integrated teams for each major campaign

4

Team Formation and Interactions

5

CLASS Team Data Centers Data Provider Working Groups Integrated Product Teams Tiger Teams

Roles and Responsibilities

CLASS RDT

serves as the technical liaison between the CLASS team and

the NOAA data centers and external stakeholder

• rganizations during the process of negotiating and defining

data management requirements.

performs gap analysis and requirements management for

campaigns and works with system engineers, the software development team, and the hardware engineering team to conduct impact assessments.

Data center personnel, including Subject Matter Experts

(SMEs), provide information stewardship expertise.

Data provider personnel provide expertise related to the

data and products being generated and on the technical interface being developed with CLASS.

6

Experience with New Campaigns

Current/new campaigns

NPP/NPOESS – now JPSS

Requirements, ICDs, Submission Agreement – all complete

GOES‐R

IRD baselined, IRS drafted Functional Requirements document developed in conjunction with

the NOAA data centers

System Definition and Requirements Reviews complete

Previous campaigns

Jason‐2

Operational – June 2008

MetOp‐A

Operational – May 2007

7

GOES‐R Campaign Teams

Integrated Product Teams (IPTs)

Archive Facilities

Working Groups

Data Engineering Integration, Test & Validation

Tiger Teams

Product Distribution‐CLASS Interface Metadata Search & Access Functional Requirements

8

GOES‐R Documents

Interface Documents

Interface Requirements Document Interface Specifications Document Interface Control Document

Functional Requirements

Submission Agreement – not considered a requirements

document, but will be a living document

Functional Requirements for Search & Access

Future Documents

Interconnectivity Security Agreement Operational Agreement

9

GOES‐R High‐level Schedule

10

I R D d r a f t e d I R D b a s e l i n e d I R S d r a f t e d I C D d r a f t e d F u n c t i

• n

a l R e q u i r e m e n t s d r a f t e d F u n c t i

• n

a l R e q u i r e m e n t s b a s e l i n e d L a u n c h 2015 2008 S R R / S D R 2009 2010 D e l t a S R R / S D R P D R 2011 C D R 2012

GOES‐R Schedule Coordination

Extensive and ongoing coordination is needed with all

stakeholders (CLASS, data centers, and data providers) to ensure success

This is a joint effort!

Interdependencies must be identified Milestones must be negotiated Testing coordination is especially important

Develop use cases early Examine resources (facilities, network connections, hardware

implementation schedules, software release schedules)

Work together to develop test strategies

11

Opportunities for Improvement

Documents needed in addition to a Submission

Agreement

Interface Control Documents Operations Agreements

Standard metadata Standard data formats

12

Interface Control Documents

Documents the technical aspects of the electronic

data transfer including

network channels file and data formats processing workflow acknowledgment protocol

13

Operations Agreements

Documents operational aspects of data transfers

IP addresses Routine and emergency point of contacts

14

Standard Metadata

Needed by the archive for independent

understandability

Independent understandability so that the

information in the archive is sufficiently complete to allow it to be interpreted, understood, and used by consumers for many years to come

Documentation to enable continued usage of the data

even after the ‘experts’ have moved to new projects

15

Standard Data Formats

Directly usable by the user community, therefore not

requiring the Archive to make data format conversions before distributing the data

Facilitate data preservation by not relying on specific

software for processing it

Facilitate archival storage by being compact

Easier to receive, copy, archive, and distribute

HDF5 will be used for GOES‐R data and products

Standard HDF5 libraries can be used by consumers

16

GOES‐R Status and Next Steps

Interface requirements

Engaged in a number of integrated product teams and

working groups leading up to an ICD

Search, access, and dissemination requirements

Working closely with the three NOAA National Data Centers Separate requirements document will provide the data

centers and CLASS teams with a more structured set of requirements that can be baselined much earlier in the satellite campaign than the submission agreement

Test strategies

Jointly developing these in a new tiger team

17

Conclusions

Collaborative teams with representation from CLASS,

the NOAA data centers, and the data provider are essential to the success of the mission

Effective systems must be in place to support the

scientific and research community to address data management issues

Data management / information stewardship Data volumes Standard data formats Metadata Documentation

18

References

CLASS Project Team, CLASS Target System

Architecture Overview, March 2009

CLASS Project Team, CLASS Level 1 Requirements

Document and Mission Success Criteria, Version 1.16, November 2008

Consultative Committee for Space Data Systems

(CCSDS), Open Archival Information System – Reference Model (OAIS‐RM), Issue 1.1, August 2009

National Oceanic and Atmospheric Administration,

NOAA Enterprise Architecture, Version 4, March 2009

19

Questions

Check out the CLASS Web Site:

http://www.class.noaa.gov

20