Effective Date: August 14, 2012
Expiration Date: December 14, 2020
|| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | ALL ||
Figure D-1 Program Commitment Agreement Title Page
PROGRAM COMMITMENT AGREEMENT
1.0 PROGRAM OBJECTIVES
Identify the broad program objectives. Describe the program's relationship to Mission Directorate goals and objectives as documented in the Directorate's 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 PROGRAM OVERVIEW
Describe the strategy to achieve the above-mentioned objectives. Relationships with external organizations, other agencies, or international partners should be addressed if achievement of the program objectives is dependent on their performance. Identify the associated projects to be included in the program as of the writing date. Specify the type of program (i.e., single-project, uncoupled, loosely coupled, or tightly coupled) and the basis for that classification.
3.0 PROGRAM AUTHORITY
Describe the NASA organizational structure for managing the program and projects from the MDAA to the NASA Center project managers. Include lines of authority and reporting, Center(s) responsibilities, the governing Program Management Councils (PMCs) for the oversight of the program and its known projects, and the approving official for new projects. Identify any delegated Decision Authority, per Section 2.3 of this NPR.
4.0 TECHNICAL PERFORMANCE COMMITMENT
Summarize the technical performance requirements, identifying baselines and thresholds needed to achieve the program objectives, as applicable. If the objectives include a technical performance target (goal) in addition to a threshold requirement, the commitment could be stated as a range. Demonstrate traceability to Agency strategic goals and outcomes and Agency requirements.
5.0 SCHEDULE COMMITMENT
Identify the following key target milestones for each project in the program, such as:
1. Start of Formulation.
2. Target date or timeframe for the SDR or MDR.
3. Target date or timeframe for the PDR or the start of implementation.
4. Start of operations.
5. End of prime operations and/or disposal, if applicable.
6. 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 ten-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, customary project activities, required technology developments, facilities costs, launch vehicles, tracking, operations and sustainment, data analysis, and disposal. Either reference the most recent Agency budget to provide the first five years of the estimated program cost or provide the budget required for the next five years. The cost range should be updated when program content changes, such as the addition of new projects entering Implementation or when the estimated cost changes. Reference the annual budget contained in the Integrated Budget and Performance Document (IBPD) for cost phasing. The cost range should be updated when program content changes, such as the addition of new projects entering Implementation.
7.0 ACQUISITION STRATEGY
Provide a high-level summary of the Acquisition Plan (described in Appendix G, Section 3.4) to reflect the results of the process for acquisition process and the Acquisition Strategy Meeting (ASM).
8.0 HIGH-RISK AREAS
Identify the areas of highest risk for the program (covering safety, technical, institutional, cost, and schedule issues) in which failure may result in changes to the program/project baseline cost, schedule, safety, 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, and mitigation options.
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 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 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.
Specify the program and project life-cycle reviews (per figures 2-2, 2-3, 2-4, and 2-5 in Chapter 2) that are required to be conducted during the Implementation Phase. Include any other requirements, e.g., the ASM, and any known unique considerations, e.g., international participation. Specify the considerations that will be used to trigger a discussion on the need for a PIR with the NASA AA (see Section 184.108.40.206 and Considerations for a PIR in Appendix A.)
Identify the discrete set of expected deliverables (outcomes) that flow from the Agency goals and objectives, as defined in the Agency Strategic Plan.
13.0 WAIVERS AND DEVIATIONS
Identify known waivers or deviations that will be sought for the program. Provide a rationale consistent with program characteristics such as scope, complexity, visibility, cost, safety, and acceptable risk.
14.0 PCA ACTIVITIES LOG
Provide and maintain a log of all PCA activities, including revisions that reflect all waivers to the original PCA. This log includes the information shown in Table D-1 and may be supplemented with an attached addendum for each change, describing the change. The PCA should be updated to add approved projects or whenever substantial change makes it necessary.
Table D-1 Sample Program Commitment Agreement Activities Log
|dd/mm/yy||Approval of new project||Addition of Project N||Ref. #1||No|
| TOC | ChangeLog | Preface | Chapter1 | Chapter2 | Chapter3 | AppendixA | AppendixB | AppendixC | AppendixD | AppendixE | AppendixF | AppendixG | AppendixH | AppendixI | AppendixJ | ALL |
|| NODIS Library | Program Formulation(7000s) | Search ||
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.