NASA Procedural Requirements

NPR 7120.8A Effective Date: September 14, 2018 Expiration Date: September 14, 2028

Subject: NASA Research and Technology Program and Project Management Requirements (Revalidated w/change 5)

Responsible Office: Associate Administrator

Appendix D. R&T Program Commitment Agreement (PCA) Template

D.1 R&T PCA Title Page

Figure D-1 R&T Program Commitment Agreement Title Page

RESEARCH AND TECHNOLOGY

PROGRAM COMMITMENT AGREEMENT
(PROGRAM TITLE)

1.0 R&T PROGRAM OBJECTIVES

Identify the broad program objectives. Describe the program's relationship to the Agency's vision and mission, as defined by NPD 1001.0, NASA Strategic Plan. Convey the public good of the program to the taxpayer, stated in a way that can be understood by the average citizen.

2.0 R&T PROGRAM OVERVIEW

Describe the strategy to achieve the above-mentioned objectives. Relationships with external organizations, other Government agencies, or international partners should be addressed if achievement of the program objectives is dependent on their performance. Identify the associated projects governed by the program.

3.0 R&T PROGRAM AUTHORITY

Describe the NASA organizational structure for managing the program and projects from the MDAA to the project managers. Include any NASA Center involvement. Include lines of authority and reporting, Center(s) responsibilities, the governing PMC for the oversight of the program and its projects, and the management responsibilities for approving new projects. Identify the program manager in charge of the program.

4.0 TECHNICAL PERFORMANCE COMMITMENT

Summarize the performance metrics with goals and minimum thresholds needed to achieve the program objectives. If the objectives include a technical performance target (goal) in addition to a threshold requirement, the commitment could be stated as a range.

5.0 SCHEDULE COMMITMENT

Identify the key target schedule milestones for the program and for each project in the program. Identify key target milestones such as:

a. Start of Formulation.

b. Target date or time frame for the Program Approval for approval to transition from Formulation to Implementation.

c. Start of Implementation.

d. Start of operations, if applicable.

e. End of prime operations and/or disposal requirements, if applicable.

f. Other milestones or time periods, as appropriate for a specific program/project.

6.0 COST COMMITMENT

Provide the estimated cost range for the program for the five-year period beginning in the current fiscal year at a level of detail that identifies the approved individual projects. Identify the constraints and assumptions used to develop this estimated cost range and specifically identify those assumptions that drive the range. This cost range should contain all costs necessary to perform the program, including, but not limited to, standard project activities, required technology developments, facilities costs, infrastructure costs, operations and sustainment, data analysis, and disposal. Reference the annual budget contained in the Integrated Budget and Performance Document (IBPD) for cost phasing. The cost range (and this PCA) should be updated when program content changes, such as the addition of new projects entering implementation.

7.0 ACQUISITION STRATEGY

Provide a brief statement of the proposed acquisition strategy for major program elements.

8.0 HIGH-RISK AREAS

Identify the areas of highest risk for the program (covering safety, technical, institutional, cost, or schedule issues) in which failure may result in changes to the program/project baseline cost, schedule, or technical performance requirements. This section should identify, where possible, the specific risk drivers, such as high-risk technologies upon which the program is dependent.

9.0 INTERNAL AGREEMENTS

If the program is dependent on other NASA activities outside of the MDAA's control to meet program objectives, identify the required support and list any formal agreements required.

10.0 EXTERNAL AGREEMENTS

Explain the involvement of external organizations, other Government agencies, or international support necessary to meet the program objectives. Include a brief overview of the program/project relationships with such external organizations. Include an identification of the commitments being made by the external organizations, other Government agencies, or international partners and a listing of the specific agreements to be concluded. Any unique considerations affecting implementation of required NASA policies and processes necessitated by the external involvement should be clearly identified.

11.0 REVIEWS

Key Decision Points are required at Authority to Proceed, Program Approval, and Closeout. IAs are required, but timing and frequency are determined by the MDAA with approval of the DA. PARs are required, but timing, frequency, and format are planned by the program manager and approved by the DA. PSRs are required, but timing and frequency are determined by the program manager in coordination with the DA. Include reviews required by this NPR and any additional reviews required by the program manager, DA, MDAA or governing PMC. Identify gate products required prior to the PARs and the type of IAs that will be performed.

12.0 OUTCOMES

Identify the discrete set of expected deliverables (outcomes) that flow from the Agency's goals and objectives, as defined in the Agency's strategic roadmaps, architecture, and plan.

13.0 WAIVERS

Identify known waivers that will be sought for the program. Provide rationale consistent with program characteristics such as scope, complexity, visibility, cost, safety, and acceptable risk.

14.0 R&T PCA CHANGE LOG

Document changes to the PCA.

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.