NASA EVM Implementation Handbook Page F-1
APPENDIX F. EVM IMPLEMENTATION DESCRIPTION IN PROJECT PLANS
1. Purpose: The purpose of this template is to provide guidance and instruction on a suggested
format and information to be included in the Project Plan when EVM is required.
2. Background: In accordance with NPR 7120.5, NASA Space Flight Program and Project
Management Requirements, NPR 7120.7, NASA Information Technology and Institutional
Infrastructure Program and Project Management Requirements, and NPR 7120.8, NASA
Research and Technology Program and Project Management Requirements, major projects
prepare a Project Plan that provides an agreement between the Project Manager, Program
Manager, and Center Director, etc., on the scope, implementation approach, project operational
environment, and the baseline commitments of the project. The Project Plan is updated over
the project life cycle in response to changes in program requirements on the project or the
baseline commitments. Execution of the Project Plan is the responsibility of the Project
Manager. The Plan includes accompanying stand-alone plans such as Safety and Mission
Assurance, Risk Management, System Engineering Management, Software Management,
Security Plans, Technical/Cost/Schedule and Control Plan, etc., summarized in section 3,
which collectively provide the guidance and control for the project.
3. Project Plan Requirements: The Project Plan Template is included as an appendix in each of
the NPRs cited above. For example, in NPR 7120.5, Appendix H, Project Plan Template,
section 3.1, Technical, Schedule, and Cost Control Plan, projects are required to describe how
it plans to control project requirements, technical design, schedule, and cost to achieve the
program requirements on the project to include EVM. The EVM implementation approach can
be included in this section or described in a separate control plan and referenced in this section.
This control plan describes the project’s implementation of EVM including:
a. How the PMB will be developed and maintained for the project and how UFE will be
established and controlled;
b. The methods the project will use to authorize the work (e.g. work agreements) and to
communicate changes for the scope, schedule, and budget of all suppliers; how the plan
is updated as make-buy decisions and agreements are made;
c. The process to be used by the project to communicate the time-phased levels of funding
that have been forecasted to be made available to each supplier;
d. For the class of suppliers not required to use EVM, the schedule and resource
information required of the suppliers to establish and maintain a baseline and to
quantify schedule and cost variances; how contractor performance reports will be
required; and
e. How the cost and schedule data from all partners/suppliers will be integrated to form a
total project-level assessment of cost and schedule performance.
f. How the project plans to report technical, schedule, and cost status to the program
manager, including the frequency
g. A description of any additional tools necessary to implement the project’s control
processes (e.g., the requirements management system, project scheduling system,