| NODIS Library | Program Formulation(7000s) | Search |

NASA Ball NASA
Procedural
Requirements
NPR 7123.1B
Effective Date: April 18, 2013
Expiration Date: April 18, 2018
COMPLIANCE IS MANDATORY
Printable Format (PDF)

(NASA Only)

Subject: NASA Systems Engineering Processes and Requirements

Responsible Office: Office of the Chief Engineer


| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | ALL |

Appendix G. Life-cycle and Technical Review Entrance and Success Criteria

This appendix describes the recommended best practices for entrance and success criteria for the life-cycle and technical reviews required in Chapter 5 regardless of whether the review is accomplished in a one-step or two-step process. Terms for maturity levels of technical products defined in the tables of this appendix are addressed in detail in Appendix F. The products indicated in the entrance criteria cover the technical products for each review. Additional programmatic products may also be required by the appropriate governing project/program management NPR.

G.1 System Requirements Review (SRR) for Program

The SRR for a program is used to ensure that the program's functional and performance requirements are properly formulated and correlated with the Agency and Mission Directorate strategic objectives. Uncoupled, loosely coupled, tightly coupled and AO programs should use the entrance and success criteria in Table G-1. For projects and single-project programs, refer to Table G-4.

Table G-1 - SRR Entrance and Success Criteria for a Program

System Requirements Review for a Program
Entrance Criteria Success Criteria
  1. The Program has successfully completed the MCR milestone review (if applicable) and responses have been made to all RFAs and RIDs, or a timely closure plan exists for those remaining open.
  2. A preliminary Program SRR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, the project manager, and the review chair prior to the Program SRR.
  3. All planned higher level SRRs and peer reviews have been successfully conducted and RID/RFA/Action Items have been addressed with the concurrence of the originators.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Top program risks with significant technical, health and safety, cost, and schedule impacts have been identified along with corresponding mitigation strategies.
  6. An approach for verifying compliance with program requirements has been defined.
  7. Procedures for controlling changes to program requirements have been defined and approved.
  8. The following primary products are ready for review:
    1. **Program requirements (including performance, health and safety, and defined interfaces to other programs) are ready to be baselined after review comments are incorporated.
    2. ** For one-step AO programs, SEMP is ready to be baselined after review comments are incorporated.
  9. Other Program SRR technical products have been made available to the cognizant participants prior to the review:
    1. *Preliminary traceability of program-level requirements on projects to the Agency strategic goals and Mission Directorate requirements and constraints.
    2. *Initial risk mitigation plans and resources for significant technical risks.
    3. *Preliminary cost and schedule for Uncoupled, Loosely Coupled, and Tightly Coupled Programs.
    4. *Preliminary documentation of Basis of Estimate (cost and schedule) for Uncoupled, Loosely Coupled, and Tightly Coupled Programs.
    5. * Review Plan ready to be baselined after review comments are incorporated.
    6. *Preliminary Configuration Management Plan.
    7. *Preliminary SEMP for uncoupled, loosely coupled, tightly coupled, and two-step AO programs.
  1. Program requirements have been defined and support Mission Directorate strategic objectives.
  2. The program requirements are adequately levied on either the single-program project or the multiple projects of the program.
  3. Traceability of program requirements to individual projects is documented in accordance with Agency needs, goals, and objectives, as described in the NASA Strategic Plan.
  4. Definition of interfaces with other programs is complete and approved.
  5. The program cost and schedule estimates are credible to meet program requirements.
  6. Top risk identification is complete and mitigation strategies appear reasonable.
  7. Evidence is provided that the program is compliant with NASA and implementing Center requirements, standards, processes, and procedures.
  8. To-be-determined (TBD) and to-be-resolved (TBR) items are clearly identified with acceptable plans and schedules for their disposition.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.2 System Definition Review for a Program

The SDR for a Program evaluates the credibility and responsiveness of the proposed program requirements/architecture to the Mission Directorate requirements, the allocation of program requirements to the projects, and the maturity of the program's mission/system definition. Uncoupled, loosely coupled, tightly coupled, and AO programs should use the entrance and success criteria in Table G-2. For project and single-project programs, refer to Table G-5.

Table G-2 - SDR Entrance and Success Criteria for a Program

System Definition Review for a Program
Entrance Criteria Success Criteria
  1. The Program has successfully completed the previous planned milestone reviews and responses have been made to all RFAs and RIDs, or a timely closure plan exists for those remaining open.
  2. An agenda for the Program SDR, success criteria, and instructions to the review board have been agreed to by the technical team, the project manager, and the review chair prior to the review.
  3. All planned higher level SDRs and peer reviews have been successfully conducted and RID/RFA/Action Items have been addressed with the concurrence of the originators.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. The following primary products are ready for review:
    1. **Approved definition of program TPMs.
    2. **Program architecture definition and a list of specific supporting projects that is ready to be baselined after review comments are incorporated.
    3. **Allocation of program requirements to the supporting projects that is ready to be baselined after review comments are incorporated.
    4. **Initial trending information on the mass margins (for projects involving hardware), power margins (for projects that are powered), and closure of review actions (RFA, RID, and/or Action Items).
    5. **SEMP ready to be baselined for uncoupled, tightly coupled, and loosely coupled programs and for two-step AO programs.
  6. Other SDR technical products (as applicable) for hardware, software, and human system elements have been made available to the cognizant participants prior to the review:
    1. *Updated Program requirements and constraints.
    2. *Traceability of program-level requirements on projects to the Agency strategic goals and Mission Directorate requirements and constraints that is ready to be baselined after review comments are incorporated.
    3. Preliminary interface definitions.
    4. Preliminary implementation plans.
    5. Preliminary integration plans.
    6. *Preliminary verification and validation plans.
    7. *Updated cost and schedule.
    8. *Updated SEMP for one-step AO programs.
    9. *Updated risk mitigation plans and resources for significant technical risks.
    10. *Updated cost and schedule.
    11. *Updated Documentation of Basis of Estimate (cost and schedule).
    12. *Preliminary plans for technical work to be accomplished during Implementation.
    13. *Updated Review Plan.
    14. * Configuration Management Plan that is ready to be baselined after review comments are incorporated.
    15. *Initial PDLM Plan.
  1. Evidence is provided that the program formulation activities are complete and implementation plans are credible to meet mission success.
  2. The program requirements address critical NASA needs as identified in the Mission Directorate strategic objectives.
  3. The program cost and schedule estimates are credible to meet program requirements within available resources.
  4. Program implementation plans are credible to achieve mission success.
  5. The program risks have been identified and mitigation strategies appear reasonable.
  6. Allocation of program requirements to projects has been completed and proposed projects are feasible within available resources.
  7. The maturity of the program's definition and associated plans are sufficient to begin preliminary design.
  8. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  9. TBD and TBR items are clearly identified with acceptable plans and schedules for their disposition.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.3 Mission Concept Review

The MCR affirms the mission/project need and evaluates the proposed mission's objectives and the ability of the concept to fulfill those objectives.

Table G-3 - MCR Entrance and Success Criteria

Mission Concept Review
Entrance Criteria Success Criteria
  1. An agenda for the MCR, success criteria, and instructions to the review board have been agreed to by the technical team, the project manager, and the review chair prior to the review.
  2. All planned higher level MCRs and peer reviews have been successfully conducted and RID/RFA/Action Items have been addressed with the concurrence of the originators.
  3. The following primary products are ready for review:
    1. **Stakeholders have been identified and stakeholder expectations have been defined and are ready to be baselined after review comments are incorporated.
    2. **The concept has been developed to a sufficient level of detail to demonstrate a technically feasible solution to the mission/project needs and is ready to be baselined after review comments are incorporated.
    3. **MOEs and any other mission success criteria have been defined and are ready to be approved.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Other technical products (as applicable) for hardware, software, and human system elements have been made available to the cognizant participants prior to the review:
    1. *Mission/project goals and objectives that are ready to be baselined after review comments are incorporated.
    2. Alternative concepts that have been analyzed and are ready to be reviewed.
    3. *Initial risk-informed cost and schedule estimates for implementation.
    4. Preliminary mission descope options.
    5. *A preliminary assessment performed by the team of top technical, cost, schedule, and safety risks with developed associated risk management and mitigation strategies and options.
    6. *Preliminary approach to verification and validation for the selected concept(s).
    7. *A preliminary SEMP, including technical plans.
    8. * Technology Development Plan that is ready to be baselined after review comments are incorporated.
    9. *Initial technology readiness that has been assessed and documented with technology assets, heritage products, and gaps identified.
    10. Preliminary engineering development assessment and technical plans to achieve what needs to be accomplished in the next phase.
    11. Conceptual life-cycle support strategies (logistics, manufacturing, and operation).
    12. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. Mission objectives are clearly defined and stated and are unambiguous and internally consistent.
  2. The selected concept(s) satisfactorily meets the stakeholder expectations.
  3. The mission is feasible. A concept has been identified that is technically feasible. A rough cost estimate is within an acceptable cost range.
  4. The concept evaluation criteria to be used in candidate systems evaluation have been identified and prioritized.
  5. The need for the mission has been clearly identified.
  6. The cost and schedule estimates are credible and sufficient resources are available for project formulation.
  7. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  8. TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.
  9. Alternative concepts have adequately considered the use of existing assets or products that could satisfy the mission or parts of the mission.
  10. Technical planning is sufficient to proceed to the next phase.
  11. Risk and mitigation strategies have been identified and are acceptable based on technical risk assessments.
  12. Software components meet the exit criteria defined in the NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.4 System Requirements Review

The SRR evaluates whether the functional and performance requirements defined for the system are responsive to the program's requirements and ensures the preliminary project plan and requirements will satisfy the mission. This table is used for projects and single-project programs. For uncoupled, loosely coupled, tightly coupled, and AO programs, refer to Table G-1.

Table G-4 - SRR Entrance and Success Criteria

System Requirements Review for Projects and Single-project Programs
Entrance Criteria Success Criteria
  1. The project has successfully completed the previously planned milestone reviews and responses have been made to all RFAs and RIDs, or a timely closure plan exists for those items remaining open.
  2. A preliminary SRR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, project manager, and review chair prior to the SRR.
  3. All planned higher level SRR and peer reviews have been successfully conducted and RID/RFA/Action Items have been addressed with the concurrence of the originators.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. The following primary technical products for hardware and software system elements are available to the cognizant participants prior to the review:
    1. **Requirements for system being reviewed are ready to be baselined after the review and preliminary allocation to the next lower level system has been performed.
    2. **For projects and single-project programs, the SEMP is ready to be baselined after review comments are incorporated.
  6. Other SRR work products (as applicable) for hardware, software, and human system elements have been made available to the cognizant participants.
    1. *Updated concept definition.
    2. * Updated concept of operations.
    3. Updated parent requirements.
    4. * Risk management plan ready to be baselined after review comments are incorporated.
    5. *Updated risk assessment and mitigations.
    6. * Configuration management plan ready to be baselined after review comments are incorporated.
    7. Initial document tree or model structure.
    8. Preliminary verification and validation method identified for each requirement.
    9. Preliminary system safety analysis.
    10. Preliminary MOPS and TPM and other key driving requirements.
    11. Other specialty discipline analyses, as required.
    12. *Updated cost and schedule estimates for the project implementation.
    13. *Updated documentation of Basis of Estimate (cost and schedule).
    14. *Updated Technology Development Plan.
    15. *Updated technology readiness that has been assessed and documented with technology assets, heritage products, and gaps identified.
    16. Logistics documentation (e.g., preliminary maintenance plan).
    17. *Initial Human Rating Certification Package.
    18. Human Systems Integration Plan (HSIP) ready to be baselined after review comments are incorporated.
    19. *System safety and mission assurance plan ready to be baselined after review comments are incorporated.
    20. *Preliminary operations concept.
    21. Preliminary engineering development assessment and technical plans to achieve what needs to be accomplished in the next phase.
    22. Software criteria and products, per the NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. The functional and performance requirements defined for the system are responsive to the parent requirements and represent achievable capabilities.
  2. The maturity of the requirements definition and associated plans is sufficient to begin Phase B.
  3. The project utilizes a sound process for the allocation and control of requirements throughout all levels, and a plan has been defined to complete the requirements definition at lower levels within schedule constraints.
  4. Interfaces with external entities and between major internal elements have been identified.
  5. Preliminary approaches have been determined for how requirements will be verified and validated.
  6. Major risks have been identified and technically assessed, and viable mitigation strategies have been defined.
  7. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  8. TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.
  9. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.5 Mission Definition Review/System Definition Review

The MDR/SDR evaluates whether the proposed mission/system architecture is responsive to the program mission/system functional and performance requirements and requirements have been allocated to all functional elements of the mission/system. This table is to be used for projects and single-project programs. For uncoupled, loosely coupled, tightly coupled, and AO programs, refer to Table G-2.

Table G-5 - MDR/SDR Entrance and Success Criteria

Mission Definition Review/System Definition Review for Projects and Single-project Programs
Entrance Criteria Success Criteria
  1. The project has successfully completed the previously planned milestone reviews and responses have been made to all RFAs and RIDs, or a timely closure plan exists for those items remaining open.
  2. A preliminary MDR/SDR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, project manager, and review chair prior to the MDR/SDR.
  3. All planned higher level MDR/SDR and peer reviews have been successfully conducted and RID/RFA/Action Items have been addressed with the concurrence of the originators.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. The following primary technical products for hardware, software, and human system elements are available to the cognizant participants prior to the review:
    1. ** Defined architecture, including major tradeoffs and options ready to be baselined after review comments are incorporated.
    2. ** Allocation of requirements to next lower level ready to be baselined after review comments is incorporated.
    3. ** MOPs, TPM, and other key driving requirement ready to be approved.
    4. **Initial trending information on the mass margins (for projects involving hardware), power margins (for projects that are powered) and closure of review actions (RFA, RID, and/or Action Items).
  6. Other MDR/SDR technical products listed below for both hardware and software system elements have been made available to the cognizant participants prior to the review:
    1. Supporting analyses, functional/timing descriptions, and allocations of functions to architecture elements.
    2. *Updated SEMP.
    3. *Updated risk management plan.
    4. *Updated risk assessment and mitigations (if required by the governing PM NPR, including PRA).
    5. *Updated Technology Development Plan.
    6. *Updated technology readiness that has been assessed and documented with technology assets, heritage products, and gaps identified.
    7. *Updated cost and schedule data with ranges and a basis of the estimates.
    8. *Preliminary Integrated Logistics Support Plan (ILSP).
    9. *Updated Human Rating Certification Package.
    10. Preliminary interface definitions.
    11. Initial technical resource utilization estimates and margins.
    12. *Updated safety and mission assurance (SandMA) plan.
    13. Updated HSIP.
    14. *Preliminary operations concept.
    15. Preliminary system safety analysis.
    16. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. The proposed mission/system architecture is credible and responsive to program requirements and constraints, including resources.
  2. The mission can likely be achieved within available resources with acceptable risk.
  3. The project's mission/system definition and associated plans are sufficiently mature to begin Phase B.
  4. All technical requirements are allocated to the architectural elements.
  5. The architecture tradeoffs are completed, and those planned for Phase B adequately address the option space.
  6. Significant development, mission, and health and safety risks are identified and technically assessed, and a process and resources exist to manage the risks.
  7. Adequate planning exists for the development of any enabling new technology.
  8. The operations concept is consistent with proposed design concept(s) and is in alignment with the mission requirements.
  9. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  10. TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.
  11. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.6 Preliminary Design Review

The PDR demonstrates that the preliminary design meets all system requirements with acceptable risk and within the cost and schedule constraints and establishes the basis for proceeding with detailed design.

Table G-6 - PDR Entrance and Success Criteria

Preliminary Design Review
Entrance Criteria Success Criteria
  1. The Project has successfully completed the previous planned milestone reviews, and responses have been made to all RFAs and RIDs, or a timely closure plan exists for those remaining open.
  2. A preliminary PDR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, project manager, and review chair prior to the PDR.
  3. All planned lower level PDRs and peer reviews have been successfully conducted and RID/RFA/Action Items have been addressed with the concurrence of the originators.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. The following primary products are ready for review:
    1. **A preliminary design that can be shown to meet requirements and key technical performance measures.
    2. Updated trending information on the mass margins (for projects involving hardware), power margins (for projects that are powered), and closure of review actions (RFA, RID, and/or Action Items).
  6. Other PDR technical products (as applicable) for hardware, software, and human system elements have been made available to the cognizant participants prior to the review:
    1. Subsystem design specifications (hardware and software), with supporting trade-off analyses and data, as required, that are ready to be baselined after review comments are incorporated.
    2. *Updated technology readiness assessment.
    3. *Updated Technology Development Plan.
    4. *Updated risk assessment and mitigation.
    5. *Life-Cycle Cost and Integrated Master Schedule (IMS) that are ready to be baselined after review comments are incorporated. When required, the Joint Confidence Level (JCL) analysis.
    6. *Baseline ILSP.
    7. Applicable technical plans that are ready to be baselined after review comments are incorporated (e.g., technical performance measurement plan, contamination control plan, parts management plan, environments control plan, Electromagnetic Interference/ Electromagnetic Compatibility (EMI/EMC) control plan, payload-to-carrier integration plan, producibility/manufacturability program plan, reliability program plan, quality assurance plan).
    8. Applicable standards that have been identified and incorporated.
    9. *Updated safety analyses and plans.
    10. Preliminary engineering drawing tree.
    11. Interface control documents that are ready to be baselined after review comments are incorporated.
    12. * Verification/validation plan that is ready to be baselined after review comments are incorporated.
    13. Plans to respond to regulatory requirements (e.g., Environmental Impact Statement), as required, that are ready to be baselined after review comments are incorporated.
    14. Preliminary Disposal Plan.
    15. Updated technical resource utilization estimates and margins.
    16. *Baseline operations concept.
    17. Updated Human Systems Integration Plan.
    18. *Updated Human Rating Certification Package.
    19. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. The top-level requirementsâ?"including mission success criteria, TPMs, and any sponsor-imposed constraintsâ?"are agreed upon, finalized, stated clearly, and consistent with the preliminary design.
  2. The flow down of verifiable requirements is complete and proper or, if not, an adequate plan exists for timely resolution of open items. Requirements are traceable to mission goals and objectives.
  3. The program cost, schedule, and JCL analysis (when required) are credible and within program constraints and ready for NASA commitment.
  4. The preliminary design is expected to meet the requirements at an acceptable level of risk.
  5. Definition of the technical interfaces (both external entities and between internal elements) is consistent with the overall technical maturity and provides an acceptable level of risk.
  6. Any required new technology has been developed to an adequate state of readiness, or backup options exist and are supported to make them viable alternatives.
  7. The project risks are understood and have been credibly assessed, and plans, a process, and resources exist to effectively manage them.
  8. Safety and mission assurance (e.g., safety, reliability, maintainability, quality, and Electrical, Electronic, and Electromechanical (EEE) parts) have been adequately addressed in preliminary designs and any applicable SandMA products (e.g., PRA, system safety analysis, and failure modes and effects analysis) meet requirements, are at the appropriate maturity level for this phase of the program's life cycle, and indicate that the program safety/reliability residual risks will be at an acceptable level.
  9. Adequate technical and programmatic margins (e.g., mass, power, memory) and resources exist to complete the development within budget, schedule, and known risks.
  10. The operational concept is technically sound, includes (where appropriate) human systems, and includes the flow down of requirements for its execution.
  11. Technical trade studies are mostly complete to sufficient detail and remaining trade studies are identified, plans exist for their closure, and potential impacts are understood.
  12. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  13. TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.
  14. Preliminary analysis of the primary subsystems has been completed and summarized, highlighting performance and design margin challenges.
  15. Appropriate modeling and analytical results are available and have been considered in the design.
  16. Heritage designs have been suitably assessed for applicability and appropriateness.
  17. Manufacturability has been adequately included in design.
  18. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.7 Critical Design Review

The CDR demonstrates that the maturity of the design is appropriate to support proceeding with full-scale fabrication, assembly, integration, and test. CDR determines that the technical effort is on track to complete the system development, meeting performance requirements within the identified cost and schedule constraints.

Table G-7 - CDR Entrance and Success Criteria

Critical Design Review
Entrance Criteria Success Criteria
  1. The project has successfully completed the previous planned milestone reviews, and responses have been made to all RFAs and RIDs or a timely closure plan exists for those remaining open.
  2. A preliminary CDR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, project manager, and review chair prior to the CDR.
  3. All planned lower level CDRs and peer reviews have been successfully conducted, and RID/RFA/Action Items have been addressed with the concurrence of the originators.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. The following primary products are ready for review:
    1. **A baselined detailed design that can be shown to meet requirements and key technical performance measures.
    2. Updated trending information on the mass margins (for projects involving hardware), power margins (for projects that are powered), and closure of review actions (RFA, RID and/or Action Items).
  6. Other CDR technical work products (as applicable) for hardware, software, and human system elements have been made available to the cognizant participants prior to the review:
    1. Product build-to specifications along with supporting trade-off analyses and data that are ready to be baselined after review comments are incorporated.
    2. Fabrication, assembly, integration, and test plans and procedures are being developed and are ready to be baselined after review comments are incorporated.
    3. Technical data package (e.g., integrated schematics, spares provisioning list, interface control documents, engineering analyses, and specifications).
    4. Defined operational limits and constraints.
    5. Updated technical resource utilization estimates and margins.
    6. Acceptance plans that are ready to be baselined after review comments are incorporated.
    7. Command and telemetry list.
    8. *Updated verification plan.
    9. *Updated validation plan.
    10. Preliminary launch site operations plan.
    11. Preliminary checkout and activation plan.
    12. Preliminary disposal plan (including decommissioning or termination).
    13. *Updated technology readiness assessment.
    14. *Updated Technology Development Plan.
    15. *Updated risk assessment and mitigation.
    16. Updated Human Systems Integration Plan (HSIP).
    17. *Updated Human Rating Certification Package.
    18. Updated reliability analyses and assessments.
    19. * Updated Life-Cycle Costs and IMS.
    20. *Updated ILSP.
    21. Subsystem-level and preliminary operations safety analyses that are ready to be baselined after review comments are incorporated.
    22. Systems and subsystem certification plans and requirements (as needed) that are ready to be baselined after review comments are incorporated.
    23. *System safety analysis with associated verifications that is ready to be baselined after review comments are incorporated.
    24. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. The detailed design is expected to meet the requirements with adequate margins.
  2. Interface control documents are sufficiently mature to proceed with fabrication, assembly, integration, and test, and plans are in place to manage any open items.
  3. The program cost and schedule estimates are credible and within program constraints.
  4. High confidence exists in the product baseline, and adequate documentation exists or will exist in a timely manner to allow proceeding with fabrication, assembly, integration, and test.
  5. The product verification and product validation requirements and plans are complete.
  6. The testing approach is comprehensive, and the planning for system assembly, integration, test, and launch site and mission operations is sufficient to progress into the next phase.
  7. Adequate technical and programmatic margins (e.g., mass, power, memory) and resources exist to complete the development within budget, schedule, and known risks.
  8. Risks to mission success are understood and credibly assessed, and plans and resources exist to effectively manage them.
  9. Safety and mission assurance (e.g., safety, reliability, maintainability, quality, and EEE parts) have been adequately addressed in system and operational designs, and any applicable SandMA products (e.g., PRA, system safety analysis, and failure modes and effects analysis) meet requirements, are at the appropriate maturity level for this phase of the program's life cycle, and indicate that the program safety/reliability residual risks will be at an acceptable level.
  10. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  11. TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.
  12. Engineering test units, life test units, and/or modeling and simulations have been developed and tested per plan.
  13. Material properties tests are completed along with analyses of loads, stress, fracture control, contamination generation, etc.
  14. EEE parts have been selected, and planned testing and delivery will support build schedules.
  15. The operational concept has matured, is at a CDR level of detail, and has been considered in test planning.
  16. Manufacturability has been adequately included in design.
  17. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.8 Production Readiness Review (PRR)

For projects developing or acquiring multiple or similar systems greater than three or as determined by the project. The PRR determines the readiness of the system developers to efficiently produce the required number of systems. It ensures that the production plans, fabrication, assembly, integration enabling products, operational support, and personnel are in place and ready to begin production.

Table G-8 - PRR Entrance and Success Criteria

Production Readiness Review
Entrance Criteria Success Criteria
  1. The significant production engineering problems and nonconformances encountered during development are resolved.
  2. The design documentation needed to support production is available.
  3. The production plans and preparation to begin fabrication are developed.
  4. The production-enabling products are ready.
  5. Resources are available, have been allocated, and are ready to support end product production.
  6. Updated costs and schedules.
  7. Risks have been identified, credibly assessed, and characterized, and mitigation efforts have been defined.
  8. The bill of materials is available and critical parts identified.
  9. Delivery schedules are available.
  10. In-process inspections have been identified and planned.
  11. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. High confidence exists that the system requirements will be met in the final production configuration.
  2. Adequate resources are in place to support production.
  3. The program cost and schedule estimates are credible and within program constraints.
  4. Design-for-manufacturing considerations have been incorporated to ensure ease and efficiency of production and assembly.
  5. The product is deemed manufacturable. Evidence is provided that the program/project is compliant with NASA and Implementing Center requirements, standards, processes, and procedures.
  6. TBD and TBR items are clearly identified, with acceptable plans and schedule for their disposition. Alternate sources for resources have been identified for key items.
  7. Adequate spares have been planned and budgeted.
  8. Required facilities and tools are sufficient for end product production.
  9. Specified special tools and test equipment are available in proper quantities.
  10. Production and support staff are qualified.
  11. Drawings and/or production models are approved/certified.
  12. Production engineering and planning are sufficiently mature for cost-effective production.
  13. Production processes and methods are consistent with quality requirements and compliant with occupational health and safety, environmental, and energy conservation regulations.
  14. Qualified suppliers are available for materials that are to be procured.
  15. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

G.9 System Integration Review (SIR)

An SIR ensures segments, components, and subsystems are on schedule to be integrated into the system, and integration facilities, support personnel, and integration plans and procedures are on schedule to support integration.

Table G-9 - SIR Entrance and Success Criteria

System Integration Review
Entrance Criteria Success Criteria
  1. The project has successfully completed the previous planned milestone reviews, and responses have been made to all RFAs and RIDs or a timely closure plan exists for those remaining open.
  2. A preliminary SIR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, project manager, and review chair prior to the SIR.
  3. The following primary products are ready for review:
    1. **Integration plans baselined at PDR that have been updated and approved.
    2. Updated trending information on the mass margins (for projects involving hardware), power margins (for projects that are powered), and closure of review actions (RFA, RID, and/or Action Items).
    3. **Preliminary VandV results from any lower tier products that have been verified.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Integration procedures have been identified and are scheduled for completion prior to their need dates.
  6. Segments and/or components are on schedule to be available for integration.
  7. Mechanical and electrical interfaces for hardware necessary to start system integration have been verified against the interface control documentation and plans for verification of remaining hardware exist.
  8. All functional, unit-level, subsystem, and qualification testing has been conducted successfully or is on track to be conducted prior to scheduled integration.
  9. Integration facilities, including clean rooms, ground support equipment, handling fixtures, overhead cranes, and electrical test equipment, are ready or will be available when required.
  10. Support personnel have been trained.
  11. Handling and safety requirements have been documented.
  12. All known system discrepancies have been identified, dispositioned, and are on schedule for closure.
  13. The quality control organization is ready to support the integration effort.
  14. Other SIR technical products (as applicable) for hardware, software, and human system elements have been made available to the cognizant participants prior to the review:
    1. * Updated Life-Cycle Costs and IMS.
    2. * Updated design solution definition.
    3. Updated interface definition(s).
    4. * Updated verification and validation plans.
    5. Final transportation criteria and instructions.
    6. *Preliminary mission operations plans.
    7. Preliminary decommissioning plans.
    8. Preliminary disposal plans.
    9. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. Integration plans and procedures are on track for completion and approval to support system integration.
  2. Previous component, subsystem, and system test results form a satisfactory basis for proceeding to integration.
  3. The program cost and schedule estimates are credible and within program constraints.
  4. Risks are identified and accepted by program/project leadership, as required.
  5. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  6. TBD and TBR items are clearly identified with acceptable plans and schedule for their dispositions.
  7. The integration procedures and work flow have been clearly defined and documented or are on schedule to be clearly defined and documented prior to their need date.
  8. The review of the integration plans, as well as the procedures, environment, and configuration of the items to be integrated, provides a reasonable expectation that the integration will proceed successfully.
  9. Integration personnel have received appropriate training in the integration and health and safety procedures.
  10. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.10 Test Readiness Review (TRR)

A TRR for each planned test or series of tests ensures that the test article (hardware/software), test facility, support personnel, and test procedures are ready for testing and data acquisition, reduction, and control.

Table G-10 - TRR Entrance and Success Criteria

Test Readiness Review
Entrance Criteria Success Criteria
  1. A preliminary TRR agenda, success criteria, and instructions to the review team have been agreed to by the technical team, project manager, and review chair prior to the TRR.
  2. The objectives of the testing have been clearly defined and documented.
  3. Approved test plans, test procedures, test environment, and configuration of the test item(s) that support test objectives are available.
  4. All test interfaces have been placed under configuration control or have been defined in accordance with an agreed to plan, and version description document(s) for both test and support systems have been made available to TRR participants prior to the review.
  5. All known system discrepancies have been identified and dispositioned in accordance with an agreed-upon plan.
  6. All required test resourcesâ?"people (including a designated test director), facilities, test articles, test instrumentation, and other test-enabling productsâ?"have been identified and are available to support required tests.
  7. Roles and responsibilities of all test participants are defined and agreed to.
  8. Test safety planning has been accomplished, and all personnel have been trained.
  1. Adequate test plans are completed and approved for the system under test.
  2. Adequate identification and coordination of required test resources are completed.
  3. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  4. TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.
  5. Risks have been identified, credibly assessed, and appropriately mitigated.
  6. Residual risk is accepted by program/project leadership as required.
  7. Plans to capture any lessons learned from the test program are documented.
  8. The objectives of the testing have been clearly defined and documented, and the review of all the test plans, as well as the procedures, environment, and configuration of the test item, provides a reasonable expectation that the objectives will be met.
  9. 9. The test cases have been analyzed and are consistent with the test plans and objectives.
  10. 10. Test personnel have received appropriate training in test operation and health and safety procedures.

G.11 System Acceptance Review (SAR)

The SAR verifies the completeness of the specific end products in relation to their expected maturity level, assesses compliance to stakeholder expectations, and ensures that the system has sufficient technical maturity to authorize its shipment to the designated operational facility or launch site.

Table G-11 - SAR Entrance and Success Criteria

System Acceptance Review
Entrance Criteria Success Criteria
  1. The project has successfully completed the previous planned milestone reviews, RFA/RIDs have been closed, and plans to complete open work are defined.
  2. A preliminary SAR agenda, success criteria, and instructions to the review team have been agreed to by the technical team, project manager, and review chair prior to the review.
  3. The following SAR technical products have been made available to the cognizant participants prior to the review:
    1. Results of the SARs conducted at the major suppliers.
    2. Product verification results.
    3. Product validation results.
    4. Documentation that the delivered system complies with the established acceptance criteria.
    5. Documentation that the system will perform properly in the expected operational environment.
    6. Technical data package that has been updated to include all test results.
    7. Final Certification Package.
    8. Baselined as-built hardware and software documentation.
    9. Updated risk assessment and mitigation.
    10. Required safe shipping, handling, checkout, and operational plans and procedures.
    11. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. Required tests and analyses are complete and indicate that the system will perform properly in the expected operational environment.
  2. Risks are known and manageable.
  3. System meets the established acceptance criteria.
  4. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  5. TBD and TBR items are resolved.
  6. Technical data package is complete and reflects the delivered system.
  7. All applicable lessons learned for organizational improvement and system operations are captured.
  8. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

G.12 Operational Readiness Review (ORR)

The ORR ensures that all system and support (flight and ground) hardware, software, personnel, procedures, and user documentation accurately reflect the deployed state of the system and are operationally ready.

Table G-12 - ORR Entrance and Success Criteria

Operational Readiness Review
Entrance Criteria Success Criteria
  1. All planned ground-based testing has been completed.
  2. Test failures and anomalies from verification and validation testing have been resolved, and the results/mitigations/work-arounds have been incorporated into supporting and enabling operational products.
  3. All operational supporting and enabling products (e.g., facilities, equipment, documents, software tools, databases) that are necessary for nominal and contingency operations have been tested and delivered/installed at the site(s) necessary to support operations.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Operations documentation (handbook, procedures, etc.) has been written, verified, and approved.
  6. Users/operators have been trained on the correct operation of the system.
  7. Operational contingency planning has been completed, and operations personnel have been trained on their use.
  8. The following primary products are ready for review:
    1. **Updated operations plans.
    2. **Updated operational procedures.
    3. **Preliminary decommissioning plan.
  9. Other ORR technical products have been made available to the cognizant participants prior to the review:
    1. *Updated cost and schedule.
    2. Updated as-built hardware and software documentation.
    3. *Preliminary VandV results.
    4. Preliminary disposal plan.
    5. Preliminary certification for flight/use.
    6. *Updated Human Rating Certification Package.
    7. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. The system, including all enabling products, is determined to be ready to be placed in an operational status.
  2. All applicable lessons learned for organizational improvement and systems operations have been captured.
  3. All waivers and anomalies have been closed.
  4. Systems hardware, software, personnel, and procedures are in place to support operations.
  5. Operations plans and schedules are consistent with mission objectives.
  6. Mission risks have been identified, planned mitigations are adequate, and residual risks are accepted by the program/project manager.
  7. Testing is consistent with the expected operational environment.
  8. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  9. TBD and TBR items are resolved.
  10. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.13 Flight Readiness Review (FRR)

The FRR examines tests, demonstrations, analyses, and audits that determine the system's readiness for a safe and successful flight or launch and for subsequent flight operations. The FRR also ensures that all flight and ground hardware, software, personnel, and procedures are operationally ready.

Table G-13 - FRR Entrance and Success Criteria

Flight Readiness Review
Entrance Criteria Success Criteria
  1. The system and support elements are ready and have been properly configured for flight.
  2. System and support element interfaces have been demonstrated to function as expected.
  3. The system state supports a launch "go" decision based on the established go/no-go criteria.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Flight failures and anomalies from previously completed flights and reviews have been resolved, and the results/mitigations/work-arounds have been incorporated into supporting and enabling operational products.
  6. The following primary products are ready for review:
    1. **Final certification for flight/use.
    2. *Baselined VandV results.
    3. **Disposal plan that is ready to be baselined after review comments are incorporated.
    4. Other FRR technical products have been made available to the cognizant participants prior to the review:
    5. *Updated cost.
    6. Updated schedule.
    7. Updated as-built hardware and software documentation.
    8. Updated operations procedures.
    9. Preliminary decommissioning plan.
    10. Software criteria and products, per NASA-HDBK-2203, NASA Software Engineering Handbook.
  1. The flight vehicle is ready for flight.
  2. The hardware is deemed acceptably safe for flight.
  3. Certification that flight operations can safely proceed with acceptable risk has been achieved.
  4. Flight and ground software elements are ready to support flight and flight operations.
  5. Interfaces have been checked and demonstrated to be functional.
  6. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  7. TBD and TBR items are resolved.
  8. Open items and waivers have been examined and residual risk from these is deemed to be acceptable.
  9. The flight and recovery environmental factors are within constraints.
  10. All open safety and mission risk items have been addressed, and the residual risk is deemed acceptable.
  11. Supporting organizations are ready to support flight.
  12. Software components meet the exit criteria defined in NASA-HDBK-2203, NASA Software Engineering Handbook.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

G.14 Post-Launch Assessment Review (PLAR)

A PLAR evaluates the readiness of the spacecraft systems to proceed with full, routine operations after post-launch deployment. The review also evaluates the status of the project plans and the capability to conduct the mission with emphasis on near-term operations and mission-critical events.

Table G-14 - PLAR Entrance and Success Criteria

Post-Launch Assessment Review
Entrance Criteria Success Criteria
  1. The launch and early operations performance, including (when appropriate) the early propulsive maneuver results, are available.
  2. The observed spacecraft and science instrument performance, including instrument calibration plans and status, are available.
  3. The launch vehicle performance assessment and mission implications, including launch sequence assessment and launch operations experience with lessons learned, are completed.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. The mission operations and ground data system experience, including tracking and data acquisition support and spacecraft telemetry data analysis is available.
  6. The mission operations organization, including status of staffing, facilities, tools, and mission software (e.g., spacecraft analysis and sequencing), is available.
  7. In-flight anomalies and the responsive actions taken, including any autonomous fault protection actions taken by the spacecraft or any unexplained spacecraft telemetry, including alarms, are documented.
  8. The need for significant changes to procedures, interface agreements, software, and staffing has been documented.
  9. Documentation is updated, including any updates originating from the early operations experience.
  10. Plans for post-launch development have been addressed.
  1. The observed spacecraft and science payload performance agrees with prediction, or if not, is adequately understood so that future behavior can be predicted with confidence.
  2. All anomalies have been adequately documented and their impact on operations assessed. Further, anomalies impacting spacecraft health and safety or critical flight operations have been properly dispositioned.
  3. The mission operations capabilities, including staffing and plans, are adequate to accommodate the actual flight performance.
  4. The program/project has demonstrated compliance with applicable NASA and implementing Center requirements, standards, processes, and procedures.
  5. Open items, if any, on operations identified as part of the ORR have been satisfactorily dispositioned.

G.15 Critical Event Readiness Review (CERR)

A CERR evaluates the readiness of the project and the flight system to execute the critical event during flight operation.

Table G-15 - CERR Entrance and Success Criteria

Critical Event Readiness Review
Entrance Criteria Success Criteria
  1. Critical event/activity requirements and constraints have been identified.
  2. Critical event/activity design and implementation are complete.
  3. Critical event/activity testing is complete.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Critical event/activity operations planning, including contingencies, is complete.
  6. Operations personnel training for the critical event/activity has been conducted.
  7. Critical event/activity sequence verification and validation is complete.
  8. Flight system is healthy and capable of performing the critical event/activity.
  9. Flight failures and anomalies from critical event/activity testing have been resolved, and the results/mitigations/work-arounds have been incorporated into supporting and enabling operational products.
  10. The following technical products have been made available to the cognizant participants prior to the review:
    1. Final certification for critical event readiness.
    2. Updated operations procedures.
  1. The critical activity design complies with requirements. The preparation for the critical activity, including the verification and validation, is thorough.
  2. The project (including all the systems, supporting services, and documentation) is ready to support the activity.
  3. The requirements for the successful execution of the critical event(s) are complete and understood and have flowed down to the appropriate levels for implementation.
  4. The program/project is compliant with NASA and Implementing Center requirements, standards, processes, and procedures.
  5. Any TBD and TBR items have been resolved.
  6. All open risk items have been addressed and the residual risk is deemed acceptable.

G.16 Post-Flight Assessment Review (PFAR)

The PFAR evaluates how well mission objectives were met during a mission and identifies all flight and ground system anomalies that occurred during the flight and determines the actions necessary to mitigate or resolve the anomalies for future flights of the same spacecraft design.

Table G-16 - PFAR Entrance and Success Criteria

Post-Flight Assessment Review
Entrance Criteria Success Criteria
  1. All anomalies that occurred during the mission, as well as during preflight testing, countdown, and ascent, are dispositioned.
  2. All flight and post-flight documentation applicable to future flights of the spacecraft or the design is available.
  3. All planned activities to be performed post-flight have been completed.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Problem reports, corrective action requests, and post-flight anomaly records are completed.
  6. All post-flight hardware and flight performance data evaluation reports are completed.
  7. Plans for retaining assessment documentation and imaging have been made.
  1. Formal final report documenting flight performance and recommendations for future missions is complete and adequate.
  2. All anomalies have been adequately documented and dispositioned.
  3. The impact of anomalies on future flight operations has been assessed and documented.
  4. Reports and other documentation have been retained for performance comparison and trending.

G.17 Decommissioning Review (DR)

A DR confirms the decision to terminate or decommission the system and assesses the readiness of the system for the safe decommissioning and disposal of system assets.

Table G-17 - DR Entrance and Success Criteria

Decommissioning Review
Entrance Criteria
  1. The requirements associated with decommissioning are defined.
  2. Plans are in place for decommissioning and any other removal from service activities.
  3. Resources are in place to support and implement decommissioning.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Health and safety, environmental, and any other constraints have been identified.
  6. Current system capabilities relating to decommissioning are understood.
  7. Off-nominal operations, all contributing events, conditions, and changes to the originally expected baseline have been considered and assessed.
  8. The following primary product is ready for review:
    1. **Decommissioning plan that is ready to be baselined after review comments are incorporated.
  9. Other DR technical products have been made available to the cognizant participants prior to the review:
    1. *Updated cost
    2. Updated schedule.
    3. *Updated disposal plan.
  1. The rationale for decommissioning is documented.
  2. The decommissioning plan is complete, meets requirements, is approved by appropriate management, and is compliant with applicable Agency safety, environmental, and health regulations.
  3. Operations plans for decommissioning, including contingencies, are complete and approved.
  4. Adequate resources (schedule, budget, and staffing) have been identified and are available to successfully complete all decommissioning activities.
  5. All required support systems for decommissioning are available.
  6. All personnel have been properly trained for the nominal and contingency decommissioning procedures.
  7. Safety, health, and environmental hazards have been identified, and controls have been verified.
  8. Risks associated with the decommissioning have been identified, and adequately mitigated.
  9. Residual risks have been accepted by the required management.
  10. The program/project is compliant with NASA and Implementing Center requirements, standards, processes, and procedures.
  11. Any TBD and TBR items are clearly identified with acceptable plans and schedule for their disposition.
  12. Plans for archival and subsequent analysis of mission data have been defined and approved, and arrangements have been finalized for the execution of such plans.
  13. Plans for the capture and dissemination of appropriate lessons learned during the project life cycle have been defined and approved.
  14. Plans for transition of personnel have been defined and approved.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence.

** Product is required per NPR 7123.1.

G.18 Disposal Readiness Review (DRR)

A DRR confirms the readiness for the final disposal of the system assets.

Table G-18 - Disposal Readiness Review Entrance and Success Criteria

Disposal Readiness Review
Entrance Criteria Success Criteria
  1. Requirements associated with disposal are defined.
  2. Plans are in place for disposal and any other removal from service activities.
  3. Resources are in place to support disposal.
  4. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  5. Safety, environmental, health, and any other constraints are described.
  6. Current system capabilities related to disposal are described and understood.
  7. Off-nominal operations, all contributing events, conditions, and changes to the originally expected baseline have been considered and assessed.
  8. *Updated cost.
  9. Updated schedule.
  10. The following primary product is ready for review:
    1. **Updated disposal plan.
  1. The rationale for disposal is documented.
  2. The disposal plan is complete, meets requirements, is approved by appropriate management, and is compliant with applicable Agency safety, environmental, and health regulations.
  3. Operations plans for disposal, including contingencies, are complete and approved.
  4. All required support systems for disposal are available.
  5. All personnel have been properly trained for the nominal and contingency disposal procedures.
  6. Safety, health, and environmental hazards have been identified, and controls have been verified.
  7. Risks associated with the disposal have been identified and adequately mitigated.
  8. Residual risks have been accepted by the required management.
  9. If hardware is to be recovered from orbit:
    1. Return site activity plans have been defined and approved.
    2. Required facilities are available and meet requirements, including those for contamination control, if needed.
    3. Transportation plans are defined and approved.
    4. Shipping containers and handling equipment, as well as contamination and environmental control and monitoring devices, are available.
  10. Plans for disposition of mission-owned assets (i.e., hardware, software, and facilities) have been defined and approved.
  11. Adequate resources (schedule, budget, and staffing) have been identified and are available to successfully complete all disposal activities.
  12. All mission and project data and documentation has been archived per disposal plan.
  13. The program/project is compliant with NASA and Implementing Center requirements, standards, processes, and procedures.
  14. TBD and TBR items have all been dispositioned.

* Product is required for programs/projects covered by NPR 7120.5. If there is disagreement between this table and NPR 7120.5, NPR 7120.5 takes precedence

** Product is required per NPR 7123.1.

G.19 Peer Reviews

Peer reviews provide the technical insight essential to ensure product and process quality. Peer reviews are focused, in-depth technical reviews that support the evolving design and development of a product, including critical documentation or data packages. The participants in a peer review are the technical experts and key stakeholders for the scope of the review. Another purpose of the peer review is to add value and reduce risk through expert knowledge infusion, confirmation of approach, identification of defects, and specific suggestions for product improvements.

Table G-19 - Peer Review Entrance and Success Criteria

Peer Review
Entrance Criteria Success Criteria
  1. 1. The product to be reviewed (document, process, model, design details, etc.) has been identified and made available to the review team.
  2. 2. Peer reviewers independent from the project have been selected for their technical background related to the product being reviewed.
  3. 3. A preliminary agenda, success criteria, and instructions to the review team have been agreed to by the technical team and project manager.
  4. 4. Rules have been established to ensure consistency among the team members involved in the peer review process.
  1. 1. Peer review has thoroughly evaluated the technical integrity and quality of the product.
  2. 2. Any defects have been identified and characterized.
  3. 3. Results of the Peer Review are communicated to the appropriate project personnel.

G.20 Program Implementation Reviews (PIR) and Program Status Reviews (PSR)

PIRs or PSRs are periodically conducted, as required by the Decision Authority and documented in the program plan, during the Implementation phase to evaluate the program's continuing relevance to the Agency's Strategic Plan. These reviews assess the program performance with respect to expectations and determine the program's ability to execute the implementation plan with acceptable risk within cost and schedule constraints.

Table G-20 - PIR/PSR Entrance and Success Criteria

Program Implementation and Program Status Reviews
Entrance Criteria Success Criteria
  1. A preliminary PIR agenda, success criteria, and instructions to the review team have been agreed to by the technical team, project manager, and review chair prior to the review.
  2. The current status of the overall technical effort is available and ready to be reviewed.
  3. Programmatic products are ready for review at the maturity levels stated in the governing program/project management NPR.
  4. Current actual and estimated costs, including any Earned Value and JCL information, if applicable, are available and compared to the expected plan.
  5. Current schedule is available showing remaining work planned.
  6. Trending of the selected Technical Performance Parameters relevant to the current Program phase is available.
  7. Updated technical plans are available.
  1. Program still meets Agency needs and should continue.
  2. The program cost and schedule estimates are credible and within program constraints.
  3. Risks are identified and accepted by program/project leadership, as required.
  4. Technical trends are within acceptable bounds.
  5. Adequate progress has been made relative to plans, including the technology readiness levels.
  6. Technologies have been identified that are ready to be transitioned to another project or to an organization outside the Agency.


| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | Chapter6 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | ALL |
 
| NODIS Library | Program Formulation(7000s) | Search |

DISTRIBUTION:
NODIS


This Document Is Uncontrolled When Printed.
Check the NASA Online Directives Information System (NODIS) Library
to Verify that this is the correct version before use: http://nodis3.gsfc.nasa.gov