1. 1 SPSRB Decision Brief on Declaring a Product Operational Instructions / 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 Priyanka.Roy@noaa.gov and cc: David.R.Donahue@noaa.gov and Eileen.Maturi@noaa.govPriyanka.Roy@noaa.govDavid.R.Donahue@noaa.govEileen.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 V9 15 Jan 2015

2. 2 SPSRB Decision Brief on Declaring “title” Operational Presenter: name and office Month day, year V9 15 Jan 2015

3. 3 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: V9 15 Jan 2015

4. 4 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: V9 15 Jan 2015

5. 5 Capabilities Assessment Current Operational Capabilities Requested CapabilitiesProposed Operational Capabilities Satellite Source (s) Product Name Accuracy Latency Timeliness Coverage Resolution Other attributes V9 15 Jan 2015

6. 6 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 SatellitesSensorsN#N# E#E# R#R# T#T# O#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: V9 15 Jan 2015

7. 7 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 V9 15 Jan 2015

8. 8 Data Flow Diagram V9 15 Jan 2015

9. 9 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 V9 15 Jan 2015

10. 10 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 V9 15 Jan 2015

11. PATRON Application Name Short Name Status Support Level User Impact Notification Tier Approval Level Escalation Tier Application Type Description * Satellites Instrument * Channels System CIP 11 * Items in green are needed to update SPEEDS V9 15 Jan 2015

12. PATRON Product Name Short Name Application Short Name Status Support Level Format Primary Use Description Output Filenames * Projected date to go operational * Horizontal resolution * Vertical resolution * Frequency * Coverage * Accuracy * Product Oversight Panel * Users * Web page * Archive 12 * Items in green are needed to update SPEEDS V9 15 Jan 2015

13. 13 SPSRB User Request Status Has the SPSRB user request been fully satisfied? V9 15 Jan 2015

14. 14 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 V9 15 Jan 2015