V14.3 11 Arp 20111
SPSRB Project Plan TemplateInstructions / 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 OSDPD change management process does not have to develop a project plan, unless directed by OSDPD management or requested by the SPSRB.
• STAR/OSDPD/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 [email protected] and info copy [email protected] and [email protected]
• Delete this slide before you send your brief to funds manager or the SPSRB secretaries
V14.3 11 Arp 2011
2
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
V14.3 11 Arp 20113
Outline
• Integrated Product Team (IPT)• Requirements• Capabilities Assessment• IT System Architecture• Plan of Operations• Project Milestones • Funding • Spending Plan and Tasks
V14.3 11 Arp 20114
Integrated Product Team (IPT)
• IPT Lead:• IPT Backup Lead:• NESDIS Team:
─ STAR:─ OSDPD:─ OSD:─ Data Center:─ Others:
• User Team─ Lead:─ Others:
• Oversight Panel (OP) lead:• Other OPs involved:
V14.3 11 Arp 20115
Requirement(s)
• Requirement(s)─ SPSRB requirement number, title and summary of requirement─ Others
• User community• Benefit to user• NOAA Mission Goal supported:• Mission priority:
V14.3 11 Arp 20116
Capabilities Assessment
Current Operational Capabilities
Requested Capabilities Proposed Operational Capabilities
Satellite Source (s)
Product Name
Accuracy
Latency
Timeliness
Coverage
Resolution
Other attributes
V14.3 11 Arp 20117
Capabilities Assessment (Continued)
• Current Operational Shortfalls─ Timeliness─ Accuracy of Product
• Define how product development addresses shortfalls• Impact if project is not funded
V14.3 11 Arp 20118
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
V14.3 11 Arp 20119
IT System Architecture
Ancillary Data from ?
ESPC h/w?
Operational
ESPC h/w ?
Backup
ORA or OSDPDh/w?
Development
ESPCh/w, ftp?
Dissemination
h/w?
User System
Input Data Includes: ????
Ancillary Data
Satellite Data from ?
V14.3 11 Arp 20111010
Research and Operational System Environments
Project Name:
IT Item Research Operations
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 projectBlue font indicates existing IT resources will be used for this project
V14.3 11 Arp 20111111
Operational Agency System Requirements
Project Name:
Back-up Operations
IT Item Development Operations On-Site Off-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 projectBlue font indicates existing IT resources will be used for this project
V14.3 11 Arp 20111212
Research and Operational System Environments
Project Name: PROJECT NAME GOES HERE
IT Item Research Operations
Agency STAR OSDPD(ESPC)
Platform(s) * and need dates3 Dell Blade Servers w/ 8 Gigs of RAM Jun 2008
IBM P6-570 2 NodesAug 2010
Operating Systems ** Red Hat Linux AIX
Programming languages/compilers ***FORTRAN, C, C++, IDL, C-shell, Oracle Database
C/C++, PGI FORTRAN
Scripting languagesPERL JAVASCRIPT
Graphical/Imaging programs, COTS S/W, other tools, libraries, etc
IDL GIMP,GDL
Helpdesk Monitoring Tool (standardized tool or customized tool?)
TBD ALTERIS BMS 2008
Other platforms needed for monitoring/imaging/graphics (specify platform & operating system)
None GNOME
Other (tools, shareware, libraries, critical non-static ancillary data, etc)
GRIB/GRIB2/NetCDF USER 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 projectBlue font indicates existing IT resources will be used for this project
Example
V14.3 11 Arp 20111313
Operational Agency System Requirements
Project Name: PROJECT NAME GOES HERE
Back-up Operations
IT Item Development Operations On-Site Off-Site
Agency STAR OSDPD(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 P6-570 2 NodesAug 2010
IBM P6-570 2 NodesNeed date TBD
Storage required on systems3 TB (1 TB per server)
SAN 10 TB SAN is mirrored and redundant
How often does system run (granule time, orbital, daily); event or schedule driven?
Hourly Orbitally (16 per day) Orbitally (16 per day)
Memory used at run time 24 GB 75 GB 75 GB
Input data volume and input data sources
4 GB per day 12 GB per day 12 GB per day
Data volume for distribution; planned distribution server; specific push users & volumes
N/A 4 GB per day 4 GB per day
Communication Requirements/Protocol
Internet ESPC Data Distribution Server, FTP
ESPC Data Distribution Server, FTP
Days to retain input and output data
3 2 2
Red font indicates new IT resource requirements for this projectBlue font indicates existing IT resources will be used for this project
Example
V14.3 11 Arp 201114
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 OSDPD 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)
V14.3 11 Arp 201115
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.
V14.3 11 Arp 201116
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
V14.3 11 Arp 201117
Project Milestones and Key Tasks(Update/Upgrade 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 Security (IT) 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: Archive process updated─ 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: Update SPSRB Oversight Panel(s) on product status─ MMM YY: Brief OSDPD 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
V14.3 11 Arp 201118
Product Deliverable Details
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:
N=New E=Enhanced R=Replacement T=Tailored O=Other
V14.3 11 Arp 201119
Product Deliverable Details
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
FY10 Sea Surface Temperatures from AMSR-E
Sea Surface Temperatures
Aqua AMSR-E 1 9 Formats: PNG, NetCDF4
Coverage areas: 5 regions
Resolutions: 40 km
Update cycle: daily
Other: N/A
FY11 Sea Surface Temperatures from AMSR-E Update
Sea Surface Temperatures
Aqua AMSR-E 1 9 Formats: 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 #resolutionsTotal products = 10 = 2 x 5 x 1FY10 get credit for 1 new and 9 tailoredFY11 get credit for 1 enhanced and 9 tailored
V14.3 11 Arp 201120
Funding (K)Project Name
Funding SourceProcurement Office
Purchase Items FY09 FY10 FY11 FY12 FY13
xxx -- Totals => 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
STAR 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
STAR 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
STAR 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
xxx -- Totals => 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
OSDPD 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
OSDPD 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
OSDPD 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
OSDPD Base -- Totals => 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
OSDPD S/W Licenses 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
OSDPD H/W Maintenance 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
OSDPD Sys Admin 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
STAR Base -- Totals => 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
STAR 0 (0) 0 (0) 0 (0) 0 (0) 0 (0)
V14.3 11 Arp 201121
FYxx Purchases and Tasks
• (xK of source): zz STAR Grant for # person at y% time from MMM YY to MMM YY─ Xxx─ Xxx
• (xK of source): STAR Software Contractor for # person at y% time from MMM YY to MMM YY─ Xxx─ Xxx
• (xK of source): OSDPD Software Contractor for # person at y% time from MMM YY to MMM YY─ Xxx─ Xxx
• (xK of source): OSDPD Hardware purchase on MMM YY─ xxx