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

NASA Ball NASA
Procedural
Requirements
NPR 7120.8A
Effective Date: September 14, 2018
Expiration Date: September 14, 2023
COMPLIANCE IS MANDATORY FOR NASA EMPLOYEES
Printable Format (PDF)

Subject: NASA Research and Technology Program and Project Management Requirements (Updated w/Chage 2)

Responsible Office: Office of the Chief Engineer


| TOC | Change Log | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixF | AppendixG | AppendixE | AppendixH | AppendixI | AppendixJ | AppendixK | AppendixL | AppendixM | ALL |

Appendix J. Requirement Reference Table

The following table is provided as a reference to each of the requirements in this NPR. This table is for information and not intended to be a formal compliance matrix.

Section Requirement
2.6.1.2 The DA shall approve decisions made at KDPs which are summarized and recorded in the decision documentation (e.g., memorandum or other appropriate format) that will become part of the retrievable program or project documentation.
2.6.1.4 The appointed IA team shall conduct Independent Assessments during the program and project life cycles. (From "NASA Independent Assessment Principles and Approach" white paper approved at the Agency Program Management Council (APMC) held May 18, 2016.)
3.2.1.1 For an R&T program, the MDAA or their delegated representative shall assign a program manager to manage the effort.
3.2.2.1.1 The MDAA or their delegated representative shall provide the purpose, scope, and constraints of the potential R&T program to the program manager.
3.2.3.1 The DA shall conduct the Authority to Proceed KDP to determine approval for a proposed program to enter the Formulation Phase.
3.2.4.2.2 The MDAA, or designee, shall develop an R&T PCA during program Formulation.
3.2.4.3.2 The program manager shall develop a Program Plan that provides the goals and objectives, management approach, program requirements, schedule/key milestones and cost estimate, the budget and acquisition strategy or the project selection approach, and the approach for reviewing and assessing projects.
3.2.5.1 The DA shall conduct the Program Approval KDP to determine the program's readiness to proceed to Implementation.
3.2.6.2 The program manager shall provide to the project managers, in writing, the purpose, scope, and constraints for each specific R&T project that is an official element of the program.
3.2.6.3 New technologies arising from technology programs shall be reported to the appropriate Center Technology Transfer Offices in a timely manner in accordance with NPR 7500.2 to be considered for intellectual property protection and transfer for secondary applications.
3.2.7.1.1 The program manager shall conduct PSRs to evaluate the status of the program.
3.2.7.2.1 The DA shall conduct decisional PARs during the Implementation Phase.
3.2.8.1 When the program achieves its goals and objectives and completes the planned mission, the DA shall conduct the Closeout KDP.
3.2.8.6 The program manager shall develop a final program report at the conclusion of the program, capturing recommendations/actions and results from the closeout activity, including any issues.
4.2.3.1 The R&T program manager, in coordination with the DA, shall assign a project manager to lead the project effort.
4.2.5.1 The project manager shall provide to the DA documentation that establishes the technical and acquisition work that needs to be performed during the life cycle or at least during the Formulation Phase, including the management process, deliverables, preliminary schedule, and funding requirements.
4.2.6.1 The DA shall conduct the ATP KDP to determine approval for a proposed project to enter the Formulation Phase and begin developing more detailed plans.
4.2.7.1 The project manager shall develop a Project Plan that contains, as a minimum:
  1. A description of the project and its objectives.
  2. How the project will be managed.
  3. How the project will be monitored and controlled, including reviews.
  4. The expected cost and schedule.
  5. Deliverables.
4.2.8.1 Before the project can enter the Implementation Phase, the DA shall conduct the Project Approval KDP to determine the project's readiness to proceed to Implementation and document the decision.
4.2.9.2 For projects with an LCC of $250 million or greater, if the project exceeds the LCC costs by 30 percent or more, the project shall notify the DA and program manager.
4.2.10.2.1 The project manager shall conduct PPRs to evaluate the status of the project.
4.2.10.3.1 The DA shall conduct decisional CAs.
4.2.11.1 When a project achieves its goals and objectives and completes the planned mission, or if a project is terminated early, the DA shall conduct the Closeout KDP.
4.2.11.4.1 The project manager shall provide a Closeout report at the conclusion of each project.
4.2.11.5 New technologies derived from NASA R&T projects shall be reported to the appropriate Center Technology Transfer Office in a timely manner in accordance with NPR 7500.2 to be considered for intellectual property protection and transfer for secondary applications.
4.2.11.6 At the conclusion of the project, the project manager shall archive data so that future users can assess the research results, technology maturity (e.g., TRL) and incorporate the research or technology into system designs or perform further investigations. (From NPR 1441.1 and NPD 7120.6.)
5.3.1 MDAAs and program and project managers shall ensure dissenting opinions are elevated through the Formal Dissent process described in this section in accordance with the following principles.
5.6.4 The person requesting a permanent change to a prescribed requirement in an Agency or Center document that is applicable to all programs and projects shall submit a "change request" to the office responsible for the requirement policy document unless formally delegated elsewhere.
5.6.6.1 The person requesting a waiver to a requirement in this directive shall document the request, obtain the required signature from the OCE or the organization responsible for the requirement, and submit a copy to the OCE. The request should include the rationale, a risk evaluation, and reference to all material that provides the justification supporting acceptance.


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

DISTRIBUTION:
NODIS


This document does not bind the public, except as authorized by law or as incorporated into a contract. 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: https://nodis3.gsfc.nasa.gov.