SPSRB Project Plan Template Instructions Guidance

1
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.

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
3
Outline

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

4
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

5
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

6
Capabilities Assessment
7
Capabilities Assessment (Continued)

• Current Operational Shortfalls
• Timeliness
• Accuracy of Product
• Define how product development addresses
  shortfalls
• Define algorithm maturity
• Impact if project is not funded

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

9
IT System Architecture
Ancillary Data
Ancillary Data
Input Data Includes ????
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.)
• 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)

11
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.

12
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

13
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

14
Current and Next Fiscal Year (FY) Product
Deliverable Details
NNew EEnhanced RReplacement
TTailored OOther
15
Current and Next Fiscal Year (FY) Product
Deliverable Details
Example
NNew EEnhanced RReplacement
TTailored OOther
16
Funding (K)Project Name
17
Previous Fiscal Year Efforts

• FY??
• (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
• FY??
• (xK of source) zz STAR Grant for person at y
  time from MMM YY to MMM YY
• Xxx
• Xxx
• Xxx
• (xK of source) STAR Software Contractor for
  person at y time from MMM YY to MMM YY

18
Current Fiscal Year Efforts

• FY??
• (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

19
Next Fiscal Year Efforts

• FY??
• (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

20
Future Fiscal Year Efforts

• FY??
• (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
• Xxx
• (xK of source) OSDPD Hardware purchase on MMM YY
• xxx