V15 7 Apr SPSRB Project Plan Template Instructions / Guidance A SPSRB goal is for “every funded product development effort responding to a user request be documented in a SPSRB Project Plan. After the SPSRB approves the proposal for product development, the initial project plan will be drafted and used when seeking funding at the Annual Product Review Every summer OSD leads a polar-orbiting and geostationary “Annual Product Review” where funding for existing and new projects are determined. All projects for funding consideration will develop a project plan using this template. Routine modifications to an existing product or service that is handled through the NESDIS OSPO change management process does not have to develop a project plan, unless directed by OSPO management or requested by the SPSRB. STAR/OSPO/OSD will develop a process to update the plans annually. In addition, projects will be periodically reviewed by management. These reviews will include assessment of all issues impacting the execution of the project. This template will be used by NESDIS project leads to outline their plan to implement a new or enhanced product or service into operations. 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 document plans to develop a new or enhanced product/service where the effort will end at the pre-operational development phase (i.e., we have reached our end- state for this capability). The template is a guide and may require tailoring. However, adherence to the briefing outline is recommended because it ensures the SPSRB and Office management is presented with the information needed to make decisions. Additional guidance is contained on the note pages. You can access the notes page by selecting “View” and “Notes Page” from the main menu. You can also print the slide with notes by selecting “File”, “Print” and select “Notes Pages” under the Print What option. Prior to submitting final version of a project plan to NESDIS Satellite Product Manager (Tom Schott), ensure it is coordinated at the IPT level and ensure your office division chief approves the plan. If you are tasked to do a project plan briefing at a SPSRB, the briefings are due 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 and info copy and Delete this slide before you send your brief to funds manager or the SPSRB secretaries

V15 7 Apr SPSRB Project Plan “title” Presenter: Name and office * IPT Lead: Name and office * IPT Backup Lead: Name and office Month day, year * If project is funded, leads will be responsible for management reporting on the secure SPSRB web site

V15 7 Apr Outline Integrated Product Team (IPT) Requirements Capabilities Assessment IT System Architecture Plan of Operations Project Milestones Funding Spending Plan and Tasks

V15 7 Apr 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:

5 Requirement(s) ─ SPSRB requirement number, title and summary of requirement ─ Others User community Benefit to user NOAA Mission Goal supported: Mission priority: V15 7 Apr 2014

6 Capabilities Assessment Current Operational Capabilities Requested CapabilitiesProposed Operational Capabilities Satellite Source (s) Environmental Observational Parameter Accuracy Latency Timeliness Coverage Resolution Other attributes V15 7 Apr 2014

7 Capabilities Assessment (Continued) Current Operational Shortfalls ─ Timeliness ─ Accuracy of Product Define how product development addresses shortfalls Impact if project is not funded V15 7 Apr 2014

8 Algorithm Status and Approach Current status of algorithms being considered in your project ─ Include some details on peer reviews ─ Include expected performance Overview of technical approach of the algorithm and its implementation ─ Include brief technical description ─ Ancillary data requirements ─ Concept of operations (e.g. for each orbit level 1b radiances are read, ancillary data is read, algorithm is applied to level1b using ancillary data for initial guess, generated output is converted to several formats, output sent to server for distribution) Briefly describe the validation concept ─ Include ground truth data used in validation ─ Metrics for assessing performance ─ Independent user assessments V15 7 Apr 2014

9 IT System Architecture Ancillary Data from ? ESPC h/w? Operational ESPC h/w ? Backup ORA or OSPO h/w? Development ESPC h/w, ftp? Dissemination h/w? User System Input Data Includes: ???? Ancillary Data Satellite Data from ? V15 7 Apr 2014

10 Research and Operational System Environments Project Name: IT ItemResearchOperations Agency Platform(s) and need dates Operating Systems Programming languages/compilers * Scripting languages Graphical/Imaging programs, COTS S/W, other tools, libraries, etc Helpdesk Monitoring Tool (standardized tool or customized tool?) Other platforms needed for monitoring/imaging/graphics (specify platform & operating system) Other (tools, shareware, libraries, critical non-static ancillary data, etc) * ESPC Target Architecture is either IBM P-series or X86 with virtualization ** ESPC target OS is either AIX, AIX with a Red Hat Linux LPAR (64-bit), or Red Hat Linux for X86 (64-bit) *** IDL and MATLAB are not supported in ESPC for science algorithm processing, only for post-processing tasks Red font indicates new IT resource requirements for this project Blue font indicates existing IT resources will be used for this project V15 7 Apr 2014

11 Operational Agency System Requirements Project Name: Back-up Operations IT Item DevelopmentOperationsOn-SiteOff-Site Agency Platform(s) and need dates (include secondary platforms for monitoring, imagery or graphics, if necessary) Storage required on systems How often does system run (granule time, orbital, daily); event or schedule driven? Memory used at run time Input data volume and input data sources Data volume for distribution; planned distribution server; specific push users & volumes N/A Communication Requirements/Protocol Days to retain input and output data Red font indicates new IT resource requirements for this project Blue font indicates existing IT resources will be used for this project V15 7 Apr 2014

12 Research and Operational System Environments Project Name:PROJECT NAME GOES HERE IT ItemResearchOperations Agency STAROSPO (ESPC) Platform(s) * and need dates 3 Dell Blade Servers w/ 8 Gigs of RAM Jun 2008 IBM P Nodes Aug 2010 Operating Systems ** Red Hat LinuxAIX Programming languages/compilers *** FORTRAN, C, C++, IDL, C-shell, Oracle Database C/C++, PGI FORTRAN Scripting languages PERLJAVASCRIPT Graphical/Imaging programs, COTS S/W, other tools, libraries, etc IDLGIMP,GDL Helpdesk Monitoring Tool (standardized tool or customized tool?) TBDALTERIS BMS 2008 Other platforms needed for monitoring/imaging/graphics (specify platform & operating system) NoneGNOME Other (tools, shareware, libraries, critical non-static ancillary data, etc) GRIB/GRIB2/NetCDFUSER EPHEMERIS DATA * ESPC Target Architecture is either IBM P-series or X86 with virtualization ** ESPC target OS is either AIX, AIX with a Red Hat Linux LPAR (64-bit), or Red Hat Linux for X86 (64-bit) *** IDL and MATLAB are not supported in ESPC for science algorithm processing, only for post-processing tasks Red font indicates new IT resource requirements for this project Blue font indicates existing IT resources will be used for this project Example V15 7 Apr 2014

13 Operational Agency System Requirements Project Name: PROJECT NAME GOES HERE Back-up Operations IT Item DevelopmentOperationsOn-SiteOff-Site Agency STAROSPO (ESPC) CIP Platform(s) and need dates (include secondary platforms for monitoring, imagery or graphics, if necessary) 3 Dell Blade Servers w/ 8 Gigs of RAM Jun 2008 IBM P Nodes Aug 2010 IBM P Nodes Need date TBD Storage required on systems 3 TB (1 TB per server) SAN 10 TBSAN is mirrored and redundant How often does system run (granule time, orbital, daily); event or schedule driven? HourlyOrbitally (16 per day) Memory used at run time 24 GB75 GB Input data volume and input data sources 4 GB per day12 GB per day Data volume for distribution; planned distribution server; specific push users & volumes N/A 4 GB per day Communication Requirements/Protocol InternetESPC Data Distribution Server, FTP Days to retain input and output data 322 Red font indicates new IT resource requirements for this project Blue font indicates existing IT resources will be used for this project Example V15 7 Apr 2014

14 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.) ─ Define funding cost requirements 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 developed/used ─ Define who will use the QC tools ─ Describe how the QC tools will be used Documentation/Metadata Plan ─ Describe who will do documentation and metadata and what will be done User Involvement Plan ─ Describe how you intend to get the user involved in project and how you will baseline their requirements for this capability (e.g., describe how you will collect user requirements and baseline requirements at PDR or a requirements review meeting) V15 7 Apr 2014

15 Additional Guidance Delete this slide before submission of your project plan The next few slides show milestone templates. It is extremely difficult to capture a standard set of milestones because there are so many different types of development efforts. For example, ─ Standard development for a new product ─ Update/Upgrade to an existing product ─ Develop multiple new products within a project  This is where you might consider development/operational builds Milestones should consider the standard SPSRB task for the various phases and delete ones that are not applicable. Projects should add project unique milestones to these templates. V15 7 Apr 2014

16 Project Milestones and Key Tasks (Complex 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: Requirement Allocation document Review ─ 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: Final Archive requirements identified ─ MMM YY: Operational and backup processing defined ─ MMM YY: Unit Test Readiness Review MMM YY (mmm yy): Pre-operational Phase Begins ─ MMM YY: Software Code Review ─ 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: System/Algorithm Readiness Review ─ MMM YY: Code transitions to operations; all documentation is complete ─ MMM YY: Operational and backup capabilities reach ops status ─ MMM YY: Operational Readiness Review ─ 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 V15 7 Apr 2014

17 Project Milestones and Key Tasks (Simple 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: Requirements Allocation Document Review ─ MMM YY: Development processing system defined ─ MMM YY: Initial Information Security (IT) concept defined ─ MMM YY: Test case processed ─ MMM YY: Critical Design Review ─ MMM YY: Code is prepared for implementation ─ MMM YY: Archive process updated ─ MMM YY: Operational and backup processing defined MMM YY (mmm yy): Pre-operational Phase Begins ─ MMM YY: Software Code Review ─ 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: System/Algorithm Readiness Review ─ MMM YY: Code transitions to operations; all documentation is complete ─ MMM YY: Operational and backup capabilities reach ops status ─ MMM YY: Operational Readiness Review ─ MMM YY: Update SPSRB Oversight Panel(s) on product status ─ MMM YY: Brief OSPO capability is ready to operational MMM YY (mmm yy): Operational Phase Begins ─ MMM YY: SPSRB manager and secretaries notified update/upgrade went into operations.  SPSRB Secretaries/manager update the SPSRB product metrics web pages ─ MMM YY: OSD updates Satellite Products database V15 7 Apr 2014

18 Product Deliverable Details 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: N=New E=Enhanced R=Replacement T=Tailored O=Other V15 7 Apr 2014

19 Product Deliverable Details 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 FY10Sea Surface Temperatures from AMSR-E Sea Surface Temperatures AquaAMSR-E19Formats: PNG, NetCDF4 Coverage areas: 5 regions Resolutions: 40 km Update cycle: daily Other: N/A FY11Sea Surface Temperatures from AMSR-E Update Sea Surface Temperatures AquaAMSR-E19Formats: PNG, NetCDF4 Coverage areas: 5 regions Resolutions: 40 km Update cycle: daily Other: N/A N=New E=Enhanced R=Replacement T=Tailored O=Other Example Total products = #formats x #coverage areas x #resolutions Total products = 10 = 2 x 5 x 1 FY10 get credit for 1 new and 9 tailored FY11 get credit for 1 enhanced and 9 tailored V15 7 Apr 2014

20 Funding (K) Project Name Funding Source Procurement Office Purchase Items FY15FY16FY17FY18FY19 xxx-- Totals =>0 (0) STAR 0 (0) STAR 0 (0) STAR 0 (0) xxx--Totals =>0 (0) OSPO 0 (0) OSPO 0 (0) OSPO 0 (0) OSPO Base--Totals =>0 (0) OSPO S/W Licenses 0 (0) OSPO H/W Maintenance 0 (0) OSPO Sys Admin 0 (0) STAR Base--Totals =>0 (0) STAR 0 (0) V15 7 Apr 2014

21 FYxx Purchases and Tasks (xK of source): zz STAR Grant for # person at y% time from MMM YY to MMM YY ─ Xxx (xK of source): STAR Software Contractor for # person at y% time from MMM YY to MMM YY ─ Xxx (xK of source): OSPO Software Contractor for # person at y% time from MMM YY to MMM YY ─ Xxx (xK of source): OSPO Hardware purchase on MMM YY ─ xxx V15 7 Apr 2014