Earned Value Management Systems
- Aerospace Standard
Plan all work scope for the program to completion.
Break down the program work scope into finite pieces that are assigned to a responsible person or organization for control of technical, schedule and cost objectives.
Integrate program work scope, schedule, and cost objectives into a performance measurement baseline plan against which accomplishments are measured. Control changes to the baseline.
Use actual costs incurred and recorded in accomplishing the work performed.
Objectively assess accomplishments at the work performance level.
Analyze significant variances from the plan, forecast impacts, and prepare an estimate at completion based on performance to date and the remaining work to be performed.
Use the EVMS information in the organization’s management processes.
In the context of this standard, a program is a group of related projects supporting a mission that are managed in a coordinated way to obtain benefits not obtained from managing them individually. As the management principles are the same to achieve success, the two terms, program and project, are used interchangeably in this standard.
An objective of this standard is the planning and performance measurement of program work scope in a manner that enables efficient integrated program management. As the management principles of planning and performance measurement are detailed throughout this standard, the terms “effort”, “scope”, “work,” “work scope,” and “program work scope” are used interchangeably.
In the context of this standard, “organization” is used as a generic term and may include but is not limited to: public and private corporations and companies, Federal government agencies, departments and activities, state and local government entities, Federally Funded Research and Development Centers (FFRDC) and similar organizations, educational institutions, and non-profit entities that are likely to be owners of earned value management systems.
There are occasions where it is beneficial for complementary systems or methodologies (e.g., Enterprise/Manufacturing Resource Planning, Agile Software Development, Theory of Constraints) to interface with the EVM System. These complimentary systems or methodologies can be used to deliver functionality and value to the customer while EVM provides a standardized method for measuring progress and reporting across the contract. The EVMS documentation should describe the interface content as well as the recurring control process to maintain data conformance and system compliance.
Data Sets - Support Documents
The G-47 Committee serves as an industry focal point for systems engineering by developing and maintaining standards, coalescing industry positions, preparing and coordinating positions on government policies & practices, and promoting sharing of best practices on the engineering of systems.