Benefits

Know where you stand and what it takes

Assess your current project management capabilities against EVMS requirements through an analysis led by experts who have implemented compliant systems for decades.

  • Gap analysis
  • Corrective action plan development
  • Corrective action plan implementation

Choose the right system

Take a tech-agnostic, business-first approach to selecting and implementing EVMS tools that align with your existing systems and operational needs.

  • Tech ecosystem assessment
  • EVMS tool selection
  • EVMS tool implementation

Shift from reporting system to management system

Integrate cost, schedule, and scope into a unified system that meets compliance requirements while improving forecasting, visibility, and program-level decision-making.

  • Cost, schedule, and scope alignment
  • Enhanced decision making

Add EVMS expertise, on-demand

Augment your team with experienced EVMS professionals to accelerate implementation, support ongoing operations, and perform health checks aligned to DCMA expectations.

  • Outsourced staffing
  • DECM or IMS health checks

Related
success stories

Take a deeper dive and discover how we’ve helped clients with EVMS Compliance.

FAQs

Can’t find what you’re looking for?

Contact us

What is an EVMS?

An EVMS is a project management methodology that integrates cost, schedule, and scope to provide an objective measure of program performance. By comparing budgeted cost of work scheduled (BCWS) against budgeted cost of work performed (BCWP) and actual cost of work performed (ACWP), an EVMS produces actionable metrics including cost variance (CV), schedule variance (SV), and estimate at completion (EAC). For government contractors, a compliant EVMS transforms a regulatory requirement into a genuine management tool that improves forecasting accuracy and supports program-level decision-making.

When is a contractor required to implement an EVMS?

DFARS 252.234-7002 requires contractors to implement an EVMS compliant with the ANSI/EIA-748 standard when performing on contracts that meet specific thresholds. Generally, cost or incentive contracts valued at $20 million or more require an EVMS that is accepted by the cognizant DCMA Contracting Officer. Contracts valued at $50 million or more require formal DCMA EVMS system acceptance prior to contract performance. Contractors should also note that individual agency supplements and contract terms may impose EVMS requirements below these thresholds.

What is the ANSI/EIA-748 standard and why does it matter?

The ANSI/EIA-748 standard establishes 32 guidelines organized across five process areas: organization, planning and budgeting, accounting, analysis, and revisions and data maintenance. Compliance with these guidelines is the foundation of any government-accepted EVMS. DCMA evaluates contractor systems against these 32 guidelines during formal Integrated Baseline Reviews (IBRs) and ongoing surveillance. A system that substantively satisfies the guidelines, and can demonstrate that through documented policies and procedures, is far better positioned to withstand DCMA scrutiny and avoid findings that trigger corrective action plans.

What is the role of DCMA in EVMS oversight?

DCMA serves as the primary government oversight authority for contractor EVMS compliance. For contracts meeting applicable thresholds, DCMA conducts an EVMS system acceptance review to validate that the contractor’s system conforms to ANSI/EIA-748. Following acceptance, DCMA performs ongoing surveillance through IBRs, compliance reviews, and performance analysis using contractor-submitted Contract Performance Reports (CPRs). A finding of system non-compliance can result in a formal corrective action request (CAR), increased government oversight, and potential impact to contract payments. Maintaining a surveillance-ready system is a continuous obligation, not a one-time milestone.

What is an IBR and what should contractors expect?

An IBR is a joint government and contractor review conducted to verify that the performance measurement baseline (PMB) is realistic, comprehensive, and traceable to contract scope. During an IBR, DCMA evaluates whether the contractor has adequately defined work scope, assigned budget, and established a credible schedule at the control account level. Contractors should expect government reviewers to examine the Work Breakdown Structure (WBS), Organizational Breakdown Structure (OBS), and supporting basis of estimate (BOE) documentation. A well-prepared IBR demonstrates that the EVMS functions as a management tool, not merely a compliance reporting mechanism.

How does EVMS interact with other government business systems?

An EVMS does not operate in isolation. For contractors subject to CAS-covered contracts, the EVMS must be consistent with the contractor’s disclosed accounting practices, ensuring that costs flowed into the system align with how costs are accumulated and allocated under FAR Part 31 and applicable Cost Accounting Standards. Additionally, the Integrated Master Schedule (IMS) that underpins the EVMS is subject to its own DCMA review. Contractors with interconnected business systems, including purchasing, estimating, and accounting, should treat EVMS implementation as an enterprise-level integration effort, not a standalone program office function.

What are the most common EVMS deficiencies identified during DCMA reviews?

DCMA surveillance and compliance reviews most frequently cite deficiencies in baseline integrity, including unauthorized or undocumented changes to the performance measurement baseline (PMB). Other common findings include inadequate management reserve (MR) controls, inconsistencies between the IMS and budget, failure to maintain a traceable work authorization process, and insufficient variance analysis at the control account level. Contractors with decentralized program offices or inconsistent application of EVMS policies and procedures across contracts are particularly vulnerable. Proactive health checks aligned to DCMA’s surveillance methodology are the most effective way to identify and remediate these issues before a formal review.

Can a small or mid-sized contractor realistically implement a compliant EVMS?

Yes, though the implementation pathway must be scaled appropriately. The ANSI/EIA-748 standard does not prescribe specific tools or system architectures, which gives contractors meaningful flexibility in how they satisfy the 32 guidelines. Smaller contractors can achieve compliance using commercially available scheduling and cost tools, provided those tools are configured to support proper earned value techniques (EVTs), control account structures, and reporting outputs required by contract. The most significant risk for smaller organizations is underestimating the procedural and documentation requirements. A compliant EVMS requires not only the right tools but formally documented policies, desk procedures, and trained personnel who apply them consistently.

Drive mission speed with EVMS

Build an EVMS that meets requirements and accelerates program execution — without adding burden to your business.

Let’s talk