Tips for Producing an Earned Value Management System Description

by Humphreys & Associates | June 1, 2023 5:02 am

Tips for Producing an EVM System Description Blog Post Banner Image.

There are a variety of ways a contractor can produce the documentation that describes their Earned Value Management System (EVMS), how it is implemented, used, and maintained. This is typically referred to as the EVM System Description (SD), though other names may be used. For example, it could be titled the Integrated Project Management System Description or Project Controls System Description to align with corporate or contractual naming conventions. EVM practices may be just one part of their overall project management system.

Regardless of the title, a contractor with an EVMS contractual requirement must be able to provide the necessary documentation to their customer to demonstrate their system complies with the EIA-748 Standard for EVMS guidelines. This includes any additional implementation guidance associated with the government agency responsible for conducting EVMS certification or validation reviews.

What is the purpose of an EVM System Description?

There are two purposes for an EVM SD; one is internal, the other is for the external customer.

The primary user of the EVM SD is project personnel such as project managers, project controls, schedulers, and control account managers (CAMs) responsible for implementing the EVMS on their project. It is essential they have a clear understanding of the required corporate EVM process and procedures as well as how to meet the intent of the EIA-748 guidelines using the applicable schedule, cost, analysis, risk, and other project control toolsets.

The government customer uses the EVM SD to gain an understanding of the contractor’s EVMS. The EVM SD must adequately document how the contractor’s system meets the intent of the EIA-748 guidelines. It should include a map of the EVM SD content to the EIA-748 guidelines or similar government customer checklist. The purpose of a government agency’s compliance review is to conduct a comprehensive assessment of a contractor’s EVMS. This includes the EVM SD as well as related processes and procedures. They also assess how the contractor has implemented the EVMS to verify the EVMS is providing timely, reliable, and auditable information.

Once the Cognizant Federal Agency (CFA) has determined the contractor’s EVMS complies with the EIA-748 guidelines, they conduct routine surveillance to ensure the contractor’s system as documented in the EVM SD and implemented on projects continues to comply with the EIA-748 guidelines. The contractor’s EVM SD is also a typical artifact required for an Integrated Baseline Review (IBR).

What needs to be included in the EVM SD?

An EVM SD should explain the methodology the contractor uses to comply with the EIA-748 guidelines as well as any government agency specific requirements. For example, DCMA uses the DoD EVMS Interpretation Guide (EVMSIG) and their Earned Value Management System Center Business Practice (BP) documents such as the BP 2 EVM System Description Review attachment EVMS Cross Reference Checklist (CRC). The DOE Office of Project Management (PM) uses their EVMS Compliance Review Standard Operating Procedure (ECRSOP) and related appendices including their Compliance Assessment Governance (CAG) document and EVMS Compliance Reference Crosswalk (CRC).

The EVM SD should provide an executive overview, reference the corporate EVMS policy, and address all of the subsystems that make up the EVMS. H&A earned value consultants have reviewed countless system descriptions over the years; contractors take a variety of approaches to discuss their subsystems.

Some contractors align with the EIA-748 five process areas (Organizing; Planning, Scheduling, and Budgeting; Accounting; Analysis and Management Reports; and Revisions and Data Maintenance). Others include additional sections covering indirect costs, material management, and subcontractor management. The planning, scheduling, and budgeting process area is often broken down into two sections – one for planning and scheduling and the other to cover work authorization and budgeting (a total of nine process groups). For more discussion, see the blog on the Benefits of Using Nine Process Groups.

A DOE contractor may align with the DOE CAG 10 subprocesses; this is similar to the nine progress group approach plus a section on risk and opportunity management. Other contractors use the project life cycle approach (initiation, planning, execution, monitor and control, and close out) to organize their content.

We recommend including a section on self-governance or self-surveillance (see Benefits of an EVMS Self-Governance Process). As noted in this blog, contractors with an approved EVMS are expected to establish and execute an annual EVMS self-governance plan.

The government customer expects contractors to map their EVM SD content to the applicable government agency EVMS compliance checklist. This is typically an appendix to the EVM SD. In most instances, this is the DCMA BP 2 EVMS Cross Reference Checklist or the DOE ECRSOP EVMS Compliance Reference Crosswalk. These checklists include attributes and/or questions that provide a more comprehensive guide to assess how a contractor meets the intent of the guidelines. The government customer also uses these checklists to identify and record the areas in the system documentation that meet the intent or note deficiencies the contractor needs to address.

The system description should include a concise description of what’s required, diagrams, illustrations, process flowcharts, as well as sample forms and reports with example data. In preparation for a compliance review, H&A earned value consultants often assist clients in creating an EVMS storyboard that visually depicts the entire system using the workflow diagrams along the inputs and outputs, and who is doing what using the applicable tool that demonstrates the system in operation.

Single or multiple documents?

A common question H&A earned value consultants are asked is whether the EVM SD should be a single document that includes the complete set of flowcharts, forms, and reports or a summary document with supporting procedures. Typically, the supporting procedures include the process flowcharts and sometimes the applicable artifacts (forms and reports). There are pros and cons to each approach.

Single Document Approach
Pros Cons
  • Provides an integrated view of the entire EVMS process.
  • Provides a complete discussion of a topic without having to reference multiple documents. Requirement discussion and process flowcharts with responsibility swim lanes along with example inputs/outputs provides a complete picture.
  • Configuration control is easier to manage, only need to make changes in one place.
  • Easier to search for a topic in a single document.
  • Easier to map the contents of a single document to the DCMA or DOE CRC.
  • Easier to create and maintain cross reference links between sections within a single document (See or See Also references).
  • For a company new to EVM, can appear to be an overwhelming task to produce a single, comprehensive document.
  • Can be a lengthy document.
  • More difficult to partition the content to different process owners to complete their section and to combine the content.
Summary Document with Supporting Procedures Approach
Pros Cons
  • Shorter summary document provides a general overview as a quick introduction to the EVMS. Can appear less daunting. Can be used as a strategy to introduce EVM concepts and incorporate into standard business practices.
  • Modular approach to creating and maintaining content. Can be easier to create the initial content.
  • Useful for targeted training using the individual procedures for a process area. For example, training focused on the steps required for developing the WBS and WBS dictionary with expected outputs.
  • Someone must review multiple documents to gain a complete understanding of the EVMS.
  • Fragmented and potentially siloed view of the system.
  • Potentially larger volume of content (over a single document), content is often repeated for context.
  • Configuration control. More difficult to maintain content to ensure consistency in multiple documents as well as maintain cross references between documents.
  • More difficult to map content in multiple documents to the DCMA or DOE CRC.

Regardless of which approach you take, keep in mind that the government customer will be approving the complete set of EVM SD documents (one or multiple documents). Any document referenced in the EVM SD is also subject to review. When you make changes to your EVM SD, the government customer will need to review and approve those changes to ensure continuing compliance with the EIA-748 guidelines. This is a formal process; changes must be processed through the contracting officer. 

Need help with your EVM System Description?

Whether you need to update your existing EVM SD or create one, H&A earned value consultants can help you to organize the content and artifacts in alignment with your business requirements. They also work with you to ensure your EVMS satisfies the EIA-748 guideline requirements as well as government agency specific requirements. H&A often assists with designing an EVMS and ensuring the project control software tools are configured to support the EVMS as well as verifying the quality of the data. For clients new to EVM, H&A offers a template that provides the basis to develop an EVM SD. This template is intended to assist clients with designing and implementing an EVMS that meets EIA-748 guideline requirements as well as the more rigorous requirements of specific government customers.

Call us today at (714) 685-1730 to get started.

Source URL: