1 / 15

Earth Science Level 1 Requirements Overview Eric Ianson Feb 27, 2012

Earth Science Level 1 Requirements Overview Eric Ianson Feb 27, 2012. Introduction. Program Level Requirements (PLRA or Level 1 Requirements) are a required gate product in NPR 7120.5 KDP-A: Draft KDP-B: “Baseline” (typically signed by Project, Program, and Division)

braith
Download Presentation

Earth Science Level 1 Requirements Overview Eric Ianson Feb 27, 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Earth ScienceLevel 1 Requirements OverviewEric IansonFeb 27, 2012

  2. Introduction • Program Level Requirements (PLRA or Level 1 Requirements) are a required gate product in NPR 7120.5 • KDP-A: Draft • KDP-B:“Baseline” (typically signed by Project, Program, and Division) • KDP-C: Update (all signatures, including Center Director and SMD AA) • The Level 1s are essentially the “contract” between HQ and the project • Program Executive and Program Scientist are the primary authors of the Level 1s • Draft input from the project are usually required for many sections • Program Office should have a significant role in development of the Level 1s • PE should maintain configuration control of the Level 1s • Review of Level 1s with ESD should be conducted at least 2 months before the next KDP • Always a good idea to provide a draft to Ken Ledbetter and Mike Luther before formal routing • A good L1requirement is a verifiable requirement • Wherever possible should be clear to a non-expert what you looking to achieve • Avoid using descriptive language outside of section 2

  3. 1.0 Scope Very Boilerplate section. Avoid editorializing.

  4. 2.0 Science Definition If you want to be descriptive or provide explanatory information, this is the section to do it.

  5. 3.0 Project Definition (1 of 2) Important to be clear who has project responsibilities

  6. 3.0 Project Definition (2 of 2)

  7. 4.1 Science Requirements (1 of 2) Most important section in L1s. BE CLEAR.

  8. 4.1 Science Requirements (2 of 2)

  9. 4.2-4.4 More Program Requirements Only be as specific as you need to be.

  10. 4.5 Data Requirements (1 of 3) Often the most challenging section to reach agreement on; work with ESD Data folks

  11. 4.5 Data Requirements (2 of 3)

  12. 4.5 Data Requirements (3 of 3)

  13. 4.6 Mission Success Criteria What constitutes mission success EXTERNAL to the Agency; rules always seem to be changing for MSC

  14. 5.0 Cost Requirements Keep this as simple as possible

  15. 6.0-10.0 Requirements

More Related