Effective Date: February 05, 2008
Expiration Date: February 05, 2018
|| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | AppendixL | ALL ||
2.1.1 A program is a strategic investment by a Mission Directorate (MD) or Mission Support Office (MSO) that has a defined architecture and/or technical approach, requirements, funding level, and management structure that initiates and directs one or more Agency projects. A program defines a strategic direction that the Agency has identified as critical. Only R&T programs adhere to this NPR. The following are types of programs used in this NPR:
a. Agency Program - A program confirmed to be on the current list of programs within the "Program and Project List" at https://nen.nasa.gov/web/pm/ and/or the Meta-Data Manager (MdM) https://nsminfo.nasa.gov/nsminfo/home/Home.aspx. Programs on these lists are particular, because they are issued four-digit alpha numeric designators by the Office of the Chief Financial Officer (OCFO) for organizing funding within NASA and explaining NASA's funding to external groups. Also, Agency-level organizations such as the Office of the Administrator, Program Analysis and Evaluation (PA&E), the Office of the Chief Engineer (OCE), the OCFO, and the Office of Safety and Mission Assurance (OSMA) track, monitor, and assess the health and success of Agency programs. While most programs are Agency programs, there are special cases such as in Cross-Program Research or Center discretionary funding where the Agency or personnel within the Agency may refer to an investment as a program when it is not on these lists. Projects that are part of an Agency program may include space flight projects, TD projects, R&T portfolio projects, and institutional projects. Only R&T programs and projects adhere to this NPR.
Agency programs are usually long-term commitments by the Agency with a common focus. Agency programs follow a specific life cycle with periodic program reviews and the cyclical starts and stops of projects.
b. R&T program - An Agency program that is strictly comprises R&T projects. The R&T Program life cycle is depicted in Figure 2.1. The life cycle includes the minimum set of reviews and gate products. R&T program management requirements are defined in Chapters 2 and 3 of this document.
Figure 2.1 R&T Program Life Cycle (Chapter 3)
c. Cross-Program Research - collective management of R&T portfolio projects taken from various Agency programs within the MD or MSO. Cross program research is controlled by a Research director (typically at NASA HQ rather than a program lead. The cross program research management requirements are defined in Chapter 3, Section 3.5.
2.2.1 A project is a specific investment identified in a Program Plan having defined requirements, a life-cycle cost, a beginning, and an end. A project yields new or revised products that directly address NASA's strategic needs. Only R&T projects adhere to this NPR. The following are types of projects in this NPR:
a. Agency Project - a project confirmed to be on the current list of projects within the "Program and Project List" on the Meta-Data Manager (MdM) database. Projects on these lists are particular, because they are issued six digit alpha numeric designators by the Office of the Chief Financial Officer (OCFO) for organizing funding within NASA and explaining NASA's funding to external groups. Also, Agency-level organizations such as the Office of the Administrator, Program Analysis and Evaluation (PA&E), the OCE, the OCFO, and the OSMA track, monitor, and assess the health and success of Agency projects. While most projects are Agency projects, there are cases where lower level projects (e.g., project elements) are confused with Agency projects or personnel within the Agency refer to specific Center investments as projects when they are not on these lists. Only R&T Agency projects adhere to this NPR.
b. R&T Project - an Agency project that is comprises strictly of R&T investments. Compared to other projects, R&T projects tend to define a cost/schedule structure rather than a life-cycle cost (LCC) and end date. R&T projects are managed as TD projects (as defined in Chapter 4 of this NPR) or as R&T portfolio projects (as defined in Chapter 5 of this NPR).
c. Technology Development Project - a specific R&T project identified in an Agency Program Plan as a Technology Development (TD) project. The TD project is managed by a project lead who reports to a program lead. The TD Project life cycle is depicted in Figure 1. The TD Project management requirements are defined in Chapter 4 of this document. A TD Project may be referenced elsewhere in Agency documentation as Advanced Technology Development (ATD).
d. R&T Portfolio Project - a specific R&T project identified in an Agency Program Plan as an R&T portfolio project. An R&T portfolio project may be made up of one or more groups of R&T investigations that address the goals and objectives of the R&T portfolio project. An R&T portfolio project is managed by a project lead who reports to a program lead or Research director. The R&T portfolio project life cycle is depicted in Figure 2-2. The R&T portfolio project management requirements are defined in Chapter 5 of this document. An R&T portfolio project may be referenced elsewhere in Agency documentation as Basic and Applied Research (BAR).
Figure 2-2 Technolody Development Project Life Cycle (Chapter 4)
Figure 2-3 R&T Portfolio Life Project Cycle (Chapter 5)
2.2.2 Meta-Data Manager
22.214.171.124 The OCFO with assistance from the OCE maintains the official database of NASA programs and projects known as the Meta-data Manager (MdM). This database is the basis for the Agency's WBS and forms the structure for program and project status reporting across all MDs and MSOs.
2.2.3 Strategic Acquisition Planning
126.96.36.199 NASA's strategic acquisition planning and authorization is a continuous process requiring the earliest possible informed decisions to ensure programs and projects have the proper budget authorization and Agency commitment.
188.8.131.52 An acquisition events facilities this decision process:
a. The Acquisition Strategy Meeting (ASM) examines the Agency's acquisition approach (e.g., internal make-or-buy, Center assignments). The ASM follows up from Agency-level acquisition decision down to program- or project-specific. The ASM occurs during the program and project formulation and approval processes.
b. The PSM, approves the procurement approach for each procurement. The PSM is project- or contract-specific and is developed by the project lead, supported by the Contracting Officer, and approved as prescribed in NPR 5100.4, Federal Acquisition Regulation Supplement (NASA/FAR Supplement) [48 CFR 1800-1899].
184.108.40.206 R&T Programs, TD Projects, and R&T portfolio projects are subject to each of these three strategic acquisition events.
a. Applicability of the ASP and the ASM is dependent on multiple factors, including associated resources and workforce parameters. To determine ASP and/or ASM applicability, and to obtain additional guidance regarding these meetings, the cognizant MD or MSO will consult with NASA Headquarters, Office of Program and Institutional Integration.
b. To determine PSM applicability, the cognizant MD or MSO, supported by the project lead and the Contracting Officer, will consult with NASA Headquarters, Office of Procurement, Office of Program and Institutional Integrations.
c. When determined applicable, these three strategic acquisition events are part of the normal program and project formulation and implementation activities described in the following paragraphs and chapters.
2.3.1 This section describes NASA's oversight approach for R&T programs, TD projects, and R&T portfolio projects. This section also defines KDPs and the Decision Authority (DA) responsible for approval of each KDP.
2.3.2 To ensure the appropriate level of management oversight, NASA has established a hierarchy of Program Management Councils (PMCs)--the Agency PMC and MD PMCs (or MSO equivalent). Each council has the responsibility of periodically evaluating the cost, schedule, risk, and performance of Agency programs or Agency projects under its purview. The evaluation focuses on whether the Agency program or Agency project is meeting its commitments to the Agency and is following appropriate management processes. Each Agency program and Agency project has a governing PMC that provides management oversight. For R&T Programs, TD projects, and R&T portfolio projects, the governing PMC and the DA for each KDP are defined in Table 2-1 and Table 2-2 (see Table 5.1 for more detail on R&T portfolio projects).
Table 2-1 Summary of Authorities for R&T programs
|R&T Program |
|Approving Official |
for Start and
|Program Decision |
(KDP I, II, III, ... n)
|NASA Associate Administrator (AA)||While the R&T Program KDP I is the NASA AA's signature on the R&T program Commitment Agreement (PCA), the MDAA or MSOD concurrently signs the R&T Program Plan for an R&T program to continue into implementation.
The NASA AA can delegate responsibility to the MDAA or MSOD (see section 220.127.116.11.d).
Optional KDPs (KDP II, III, IV, ...) may be added per DA discretion during implementation. The DA may also determine these optional KDPs are not needed.
|Selecting Official |
|NASA AA||The NASA AA can delegate responsibility to the MDAA or MSOD for selection of the Formulation Review team.
This refers to the Formulation Review in section 18.104.22.168.
|Selecting Official |
|MDAA or MSOD||This refers to the independent assessments specific to section 3.4.1. The MDAA or MSOD can delegate responsibility for selection of independent assessment team(s). The Associate Administrator for PA&E will ensure that the team(s) and process is independent and objective. The MDAA or MSOD must obtain approval from the AA for PA&E and the Chief Engineer per section 3.4.1.
Other independent assessments may occur per section 3.4.
|Governing PMC||Agency PMC||The Agency PMC can delegate oversight responsibility to the MD PMC or MSO equivalent.|
|Governing Document||R&T Program Plan||The R&T Program Plan is approved by the MDAA or MSOD.|
R&T Program and Project Plans will reflect modifications due to the comments above and document the attendant rationale for the change.
Table 2-2 Summary of Authorities for R&T Programs
Official for Start
|The MDAA or MSOD can delegate responsibility to the program lead or Research director.|
|Project Decision |
|The MDAA or MSOD can delegate responsibility to the program lead or Research director.|
|The MDAA or MSOD can delegate responsibility to the program lead or Research director.
This refers to the Formulation Review in section 22.214.171.124 and 126.96.36.199.
This refers to the independent assessments in section 188.8.131.52 and 184.108.40.206.a.
The MDAA or MSOD shall obtain approval from the Chief Engineer and the AA for PA&E per section 220.127.116.11.a and 18.104.22.168.
|MD PMCor |
|MD PMC or |
|TD Project Plan||R&T
|The TD and R&T Portfolio Project Plans are approved by the Project DA with concurrence by the Program Lead/Research director and applicable Center Director(s) (CD).|
The R&T Program and Project Plans must reflect modifications due to the comments above and document the attendant rationale for the change.
2.3.3 Oversight of Agency programs and Agency projects is also performed by a Center Management Council (CMC), which may evaluate all R&T work executed at that Center. The CMC evaluation is an independent assessment that focuses on whether Center engineering and management practices (e.g., resources, contracting, institutional, and technical authority) are being followed by the R&T work under review, and whether Center resources can support R&T work requirements. The evaluation should also focus on the technical authority role of the Center to ensure technical and scientific integrity of work conducted at that Center. A CMC provides its findings and recommendations to the governing PMC.
2.3.4 A KDP occurs when the DA determines the readiness of a program or project to progress to the next phase of its life cycle. As such, KDPs serve as gates through which programs and projects will pass. To support the decision process, a KDP is typically preceded by one or more reviews. KDPs enable a disciplined approach to assessing programs and projects. The potential outcomes at a KDP include:
a. Approval to enter the next phase of the life cycle.
b. Approval to enter the next phase of the life cycle, pending resolution of actions.
c. Disapproval to enter the next phase of the life cycle, with a decision to terminate.
d. Disapproval to enter the next phase of the life cycle, with follow-up actions required. In such cases, follow-up actions are documented and the KDP is redone after the follow-up actions are completed.
2.3.5 To support the decision process, the DA will designate the required supporting materials (gate products) that will be submitted in support of the KDP. These materials may include: the governing PMC review recommendation; the Independent Assessment (IA) report; the Program Lead's recommendation; the Project Lead's recommendation; Cost Estimation reports; the CMC's recommendation; relevant lessons learned; any documents requiring the DA signature (e.g., R&T Program FAD, R&T Program Plan, and R&T PCA); and any other documentation the DA deems appropriate.
2.3.6 The DA's decision is based on consideration of a number of factors, including but not limited to:
a. Continued relevance to the Agency's vision and mission, as defined by NPD 1001.0, NASA Strategic Plan.
b. Technical quality of effort.
c. Continued cost affordability with respect to the Agency's resources.
d. Remaining risks (cost, schedule, technical, management, programmatic, safety).
e. Infrastructure resource readiness.
f. The viability and the readiness to proceed to the next phase.
2.3.7 At each KDP, the DA reviews the program or project to ensure that it is currently in line with the Agency's vision and mission, as defined by NPD 1001.0, NASA Strategic Plan. At each KDP, the DA ensures that the criteria defined in the Preface P.2 are currently applicable to continue use of this NPR in lieu of NPR 7120.5, NASA Space Flight Program and Project Management Requirements.
2.3.8 To complete formal actions at a KDP, the DA makes and documents the decision and its basis (including materials presented, major issues, options, and open action items) and archives the documents, as appropriate. Following the decision, the DA signs the applicable documents, if no changes are required. If changes are required, the documents are revised, all parties-to signatures obtained, and resubmitted to the DA for final signature. Dissenting opinions are resolved in accordance with the process described in section 3.6.
2.4.1 The program and project reviews identified in the life cycles are essential elements of conducting, managing, evaluating, and approving R&T programs/projects. R&T programs and projects will conduct the appropriate independent reviews or assessments that assure the relevance, quality, and performance of the program or project per the requirements in the White House guidance. See the Quality Assessment Process and Performance Measurement Metrics in NPR 1080.1, NASA Science Management for additional guidance on assessments. In preparation for these reviews, programs and projects may conduct internal reviews to establish and manage the program/project baseline. Programs and projects are required to document in their Program and Project Plans their approach to conducting both program/project independent external and internal reviews.
2.4.2 At a minimum, Independent Assessments (IA) occur during the life cycle as shown in Figure 2.1.1, 2.2.1, 2.2.2, and 2.2.3. Programs and projects are required to document in their Program and Project Plans their approach to supporting the IAs. The Terms of Reference (ToR) for each program and project IA is a document specifying the nature, scope, schedule, and ground rules for these types of independent reviews or independent assessments.
2.4.3 When practical, other Agency and Center reviews should be coordinated with planned program and project reviews.
Figure 2-4 Portfolio Project Cycle (Chapter 5)
| TOC | ChangeHistory | Preface | Chapter1 | Chapter2 | Chapter3 | Chapter4 | Chapter5 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | AppendixK | AppendixL | ALL |
|| NODIS Library | Program Formulation(7000s) | Search ||