V8 20 Jan 20121

SPSRB Decision Brief on Declaring a Product OperationalInstructions / Guidance

• This template will be used by NESDIS personnel to recommend to the SPSRB that a new satellite product be declared operational. A decision briefing should be given to the SPSRB 1 to 45 days prior to declaring a product/service operational. Slides are due on the last Friday of the month. The presentation will be at the SPSRB which meets on the 3rd Wednesday of every month.─ Send briefing to Marco.Vargas@noaa.gov and info copy John.Paquette@noaa.gov and Eileen.Maturi@noaa.gov

• Occasionally, NOAA will stop a capability at a pre-operational phase. For example, a product from a research satellite may not go all the way to a full 24/7 operational phase. In such cases, this template will also be used to declare a new product is ready to be declared fully pre-operational (i.e., we have reached our end-state for this capability).

• Every new product that is ready for transition into operations will be briefed to the SPSRB. • Routine modifications to an existing product that is handled through the NESDIS OSPO change

management process does not have to be briefed to the SPSRB, unless directed by OSPO management or requested by the SPSRB.

• Updates or enhancements to existing satellite products do not have to be briefed to the SPSRB. The decision to declare these products as operational will be made by OSPO’s SPSD Division Chief or his Representative.

• The template is a guide and may require tailoring. However, adherence to the briefing outline is recommended because it ensures the SPSRB is presented the information needed to make decisions.

• Guidance is contained in the notes page. You can access the notes page by selecting “View” and “Notes Page” from the main menu.

• Delete this slide before you send your brief to the SPSRB secretaries

2

SPSRB Decision Briefon Declaring

“title” Operational

Presenter: name and office

Month day, year

V8 20 Jan 2012

V8 20 Jan 20123

Integrated Product Team (IPT)

• IPT Lead:• IPT Backup Lead:• NESDIS Team:

─ STAR:─ OSPO:─ OSD:─ Data Center:─ Others:

• User Team─ Lead:─ Others:

• Oversight Panel (OP) lead:• Other OPs involved:

V8 20 Jan 20124

Requirement(s)

• Requirement(s)─ SPSRB requirement number, title and summary of requirement

Date of Initial Technical Assessment and SPSRB decision Date of Proposal for Product Development and SPSRB decision

─ Others

• User community• Benefit to user• NOAA Mission Goal supported:• Mission priority:

V8 20 Jan 20125

Capabilities AssessmentCurrent Operational Capabilities

Requested Capabilities Proposed Operational Capabilities

Satellite Source (s)

Product Name

Accuracy

Latency

Timeliness

Coverage

Resolution

Other attributes

V8 20 Jan 20126

Proposed Product Deliverable Details

N=New E=Enhanced R=Replacement T=Tailored O=Other

Product Type and Number

Fiscal Year (FY)

Product Delivery/Tracking Name

Environmental Observational Parameters

Satellites Sensors N

#

E

#

R

#

T

#

O

#

Tailoring Options or Comments

Formats:

Coverage areas:

Resolutions:

Update cycle:

Other:

Formats:

Coverage areas:

Resolutions:

Update cycle:

Other:

Formats:

Coverage areas:

Resolutions:

Update cycle:

Other:

Formats:

Coverage areas:

Resolutions:

Update cycle:

Formats:

Coverage areas:

Resolutions:

Update cycle:

Other:

V8 20 Jan 20127

Project Milestones and Key Tasks(New Product Example)

Product Delivery/Tracking Name: xxxxxxx• MMM YY (mmm yy): Development Phase Begins

─ MMM YY: IPT Lead informed to begin product development─ MMM YY: Initial Archive Requirements identified─ MMM YY: Quality Monitoring Concept Defined─ MMM YY: Long-term Maintenance Concept Defined ─ MMM YY: Preliminary Design Review─ MMM YY: Development processing system defined─ MMM YY: Initial Information Technology (IT) Security concept defined─ MMM YY: Test case processed─ MMM YY: Critical Design Review─ MMM YY: Code is prepared for implementation─ MMM YY: Software Code Review─ MMM YY: Final Archive requirements identified─ MMM YY: Operational and backup processing defined

• MMM YY (mmm yy): Pre-operational Phase Begins─ MMM YY: Operational and backup processing capabilities in place─ MMM YY: Final IT Security Concept Defined─ MMM YY: Pre-operational product output evaluated & tested─ MMM YY: Code transitions to operations; all documentation is complete─ MMM YY: Operational and backup capabilities reach ops status─ MMM YY: Brief SPSRB Oversight Panel(s) on product status─ MMM YY: Brief SPSRB capability is ready to go operational

• MMM YY (mmm yy): Operational Phase Begins─ MMM YY: SPSRB declares product operational

SPSRB Secretaries/manager update the SPSRB product metrics web pages OSD updates Satellite Products database

V8 20 Jan 20128

Data Flow DiagramGINI Ingest/Remap System

SATEPS/NSOF

Fairmont, WV

GOES Ingestand NOAA Port

Interface(GINI)

SDI3_3/SDI3_4SDI4_3/SDI4_4

NPORT3/NPORT4/NPORT6

Send mail

Raw GOES Satellite Data

ADDE Pull

SDIIngest System

AWIPSVSFTP Push

SATEPS Security at ESPC/NSOF

NSOF

SDI5_1/SDI5_2 NPORT5

Send mail

Raw GOES Satellite Data

ADDE Pull

GOES Ingestand NOAAPort

Interface(GINI)

SDIIngest

System

NWS Test NCF

AWIPSVSFTP Push

NWS (For NOAAPORT

Feed) ANCFNWB BackupSBN BNCF

McLean, VA

AWIPSVSFTP Push

Product Server

GP05/GP13 SATEPSDIST 4/SATEPSDITb4

AWIPSComposite

PolarMicrowave

Five DPIProducts

BlendedTPW

Low CloudBase

Data Flow Diagram Legend

AWIPSSFTP Push

AWIPSSFTP Push

GP67/GP68

GP75/GP78

Silver Spring, MD

Fairmont, WV

SATEPSDIST 1

SATEPSDIST4/SATEPSDISTb4

AWIPSSFTP Push

AWIPSSFTP Push

Arrow indicates direction of connection

Send mail/SMTP – Port 25

SSH – Port 22

ADDE – Port 112

http – Port 80

VSFTP – Port 21

OSDPD/ESPC-GINI-ESDA31-0001-V1.2Baseline Date: January 12, 2011

External User Zone

Development Zone

Distribution Zone (DMZ)

Private NSOF Network

Production Zone

Staging Zone

WWB Zone

AWIPSVSFTP Push

AWIPSSFTP Pull

AWIPSSFTP Push

V8 20 Jan 20129

Guidance

Insert a few slides that clearly show the following

• Quality of the product─ Technical performance ─ Strengths and weaknesses─ Peer reviews conducted

Recommend appropriate Oversight Panel review performance prior to SPSRB briefing

─ For new NPP products include a short quality assessment from the STAR cal/val lead. If you do not know the STAR person, contact Laurie Rokke

• User readiness and acceptance of product─ Is user ready to use product? If user not using product operationally, please explain

when this will happen─ Has user received training on how to use the product?

Delete this guidance slide when submitting your briefing

V8 20 Jan 201210

Plan of Operations

• Product Retirement Plan─ Define if we will pursue the retirement of a product as a result of

implementing a new or enhanced product under this project

• Archive Plan─ Define need for archive, archive location and duration of archive─ Define deliverables to archive (e.g., software, documentation, etc.)

• Long Term Maintenance Plan─ Define STAR science maintenance plan and funding source─ Define OSPO maintenance plan and funding source

• Quality Monitoring Plan─ Define Quality Control (QC) tools to be used─ Define who will use the QC tools ─ Describe how the QC tools will be used (e.g., what thresholds trigger action)

• Documentation/Metadata Plan─ Describe who will do documentation and metadata and what will be done

V8 20 Jan 201211

Satellite Product End-to-End Documentation System (SPEEDS)

• Product Name:• Projected Date to Go Operational:• Product Description:• Product System:• Platform:• Satellite(s):• Instrument(s) used:• Channels:• Horizontal Resolution:• Vertical Resolution:• Frequency:• Coverage:• Accuracy:• Formats:• Web Page:• Product Oversight Panel:• Users:• Archive:

V8 20 Jan 201212

SPSRB User Request Status

• Has the SPSRB user request been fully satisfied?

V8 20 Jan 201213

SPSRB Decision

• General comments• User input• STAR senior representative input• OSPO senior representative input• OSD senior representative input

• Consensus decision reached?─ Yes: summarize decision─ No: summarize direction