Project close-out reveals what in-flight monitoring should have flagged six months earlier: a 30% budget overrun, an undetected delay, a project margin that has collapsed. In engineering firms, design offices and contract-based industries, this scenario is not an anomaly. It is the direct consequence of tracking only actual costs incurred, without ever measuring the value of work actually completed.
Earned Value Management (EVM) solves precisely this problem. Combined with a fit-for-purpose ERP, it enables cost and schedule variances to be detected during execution — not at project close-out. This guide explains how EVM works, which metrics to watch, and how your ERP can become the engine driving that control.
What EVM Fundamentally Changes About Project Control
Most organisations track project progress by comparing two curves: the planned budget and actual costs incurred. If actual costs stay below budget, the conclusion is that the project is “on track.”
That reading is misleading. A project may have spent less than planned simply because it has also accomplished less than planned. Spending 60% of the budget at the halfway point while completing only 40% of deliverables is not good news — it is the early signature of a certain future overrun.
EVM corrects this illusion by introducing a third dimension: the budgetary value of work actually completed. This value, called Earned Value (EV), allows you to compare simultaneously what was planned, what was delivered, and what was spent.
EVM is today governed by two international standards. The ANSI/EIA-748, an American standard published by the Electronic Industries Alliance, defines 32 criteria for a compliant earned value management system (AcqNotes, ANSI/EIA-748). Internationally, ISO published in February 2026 the second edition of ISO 21508:2026, which provides the reference framework for implementing EVM across project, programme and portfolio management (DIN Media, ISO 21508:2026).
The Five Core EVM Metrics
Before discussing ERP integration, you need to master the vocabulary. EVM rests on three base values from which two variances are derived.
Planned Value (PV)
PV represents the budget allocated to the work that should have been completed by a given date. Expressed in monetary units, it is read from the project’s performance measurement baseline. If you have planned £500,000 of work over 12 months, PV at the end of month six should be £250,000 on a linear schedule.
Earned Value (EV)
EV represents the budgetary value of work actually completed at the same date. If your teams have delivered 40% of the project scope, and the total budget is £500,000, EV equals £200,000 — regardless of what you have spent.
Actual Cost (AC)
AC is the expenditure actually incurred to accomplish the work measured by EV. It is the only figure most organisations track today. EVM’s contribution is placing it in context alongside the other two.
Cost Variance (CV) and Schedule Variance (SV)
Cost variance (CV = EV − AC) shows whether you are spending more or less than the value of work completed. A negative CV means cost overrun. Schedule variance (SV = EV − PV) measures whether progress matches the plan. A negative SV signals execution delay.
Performance Indices: CPI and SPI
Variances are useful for point-in-time monitoring, but performance indices enable trend analysis over time and comparison across projects.
Cost Performance Index (CPI)
CPI is calculated by dividing earned value by actual cost: CPI = EV / AC. A CPI of 1.0 means you are spending exactly the value of the work completed. A CPI of 0.8 means that for every pound of work accomplished, you have spent £1.25. Any CPI below 1.0 is a budget overrun signal (Deltek, Cost Performance Index).
Schedule Performance Index (SPI)
SPI measures schedule efficiency: SPI = EV / PV. An SPI of 0.9 indicates that your teams are progressing at 90% of the planned rate. An SPI below 0.85 sustained across multiple consecutive periods is typically a sign of a structural resource or complexity problem.
Combined Reading: The CPI/SPI Matrix
Reading both indices together gives a clear picture of project health:
- CPI > 1 and SPI > 1: under budget and ahead of schedule. Verify your baseline is realistic.
- CPI > 1 and SPI < 1: slow but economical progress. Late-delivery risk.
- CPI < 1 and SPI > 1: fast but expensive progress. Final-overrun risk.
- CPI < 1 and SPI < 1: degraded on both dimensions. Management intervention required.
Forecasting Final Cost: EAC, VAC and TCPI
The major benefit of EVM for a CFO or programme director is the ability to forecast total project cost well before close-out.
Estimate at Completion (EAC)
EAC is the projected total cost at project end, recalculated from observed performance. The most common formula: EAC = Budget at Completion (BAC) / CPI. If your project has a £1,000,000 budget and a current CPI of 0.85, your projected EAC is £1,176,470 — a £176,470 overrun.
Variance at Completion (VAC)
VAC is simply the difference between the original budget and EAC: VAC = BAC − EAC. A negative VAC means the project will exceed its budget at completion.
To-Complete Performance Index (TCPI)
TCPI answers the question: what performance level must be sustained for the remainder of the project to meet budget? TCPI = (BAC − EV) / (BAC − AC). A TCPI above 1.1 indicates that the required future performance is materially higher than historical performance — making the budget target unrealistic without significant corrective action.
ERP and EVM: How the Two Systems Connect
EVM is only as good as the data feeding it — data that must be reliable, current and structured. This is where ERP plays a central role.
An ERP designed for engineering organisations centralises the information EVM requires:
- Work Breakdown Structure (WBS): each work package with its budget and percentage complete
- Time and cost entry: hours logged by engineers, supplier invoices, subcontract costs, overhead allocated to the project
- Schedule: milestones, planned start and finish dates, resource assignments
From this data, the ERP’s EVM module (or its connector to a specialist tool) computes metrics continuously. The programme director no longer consolidates an Excel file on Friday evening — they access a dashboard updated with every transaction.
Typical data flow
Engineers enter their hours in the ERP’s time-management module. Those hours are valued at the budgeted rate for the work package to compute EV. Supplier invoices entered in the procurement module feed AC. PV comes from the performance measurement baseline locked at project kick-off. The ERP updates all metrics with every transaction, with no manual consolidation.
The trap to avoid: EV based on costs incurred
The most frequent mistake in early EVM implementations is calculating EV from actual costs rather than from physical progress. If you treat £500,000 spent as automatically equal to £500,000 of earned value, your metrics are worthless — they will detect no overrun at all. Physical progress must be entered independently by project managers or work package owners.
Which ERPs Support EVM for Engineering Organisations
The project-oriented ERP market has structured its EVM offering around several main players.
Deltek: The EVM Reference in Defence and Engineering
Deltek Vantagepoint and Deltek Costpoint are the reference ERPs for engineering firms and government contractors. Deltek Cobra, connected to these ERPs, is the most widely used EVM tool in the US defence sector — deployed by nine of the top ten Department of Defense contractors (Deltek Cobra). It pulls cost data from the ERP, schedule data from Open Plan or Microsoft Project, and generates ANSI/EIA-748-compliant EVM reports.
SAP: EVM in Large Industrial Organisations
SAP offers a project management module (SAP PS, Project System) and a portfolio management layer (SAP PPM) that enable EVM implementation within the core ERP. For organisations already standardised on SAP S/4HANA, this is the most integrated option: project costs flow directly from SAP controlling, with no external interface.
Oracle: Primavera P6 and Large-Scale Project Management
Oracle Primavera P6 is a reference scheduling tool in construction, industrial engineering and energy projects. Its integration with Oracle ERP Cloud enables cost and progress data to flow within a unified architecture. Oracle also offers a dedicated EVM solution for large infrastructure programmes.
Microsoft Dynamics 365 and Project Operations
For mid-market engineering firms that do not wish to invest in Deltek or SAP, Microsoft Project Operations (a Dynamics 365 module) provides integrated project management with a foundational EVM logic. Metrics are less advanced than Deltek or Oracle, but the solution is sufficient for organisations whose projects do not require formal ANSI/EIA-748 compliance.
Access Group and Sage UK for the Mid-Market
In the UK and European mid-market, Access Group (particularly Access Financials and Access People) and Sage X3 offer project accounting capabilities suited to engineering consultancies. Native billing-by-progress, margin tracking and job costing are included. Full EVM with automated CPI and SPI calculation requires specific configuration, but the underlying data structure is compatible.
Implementing EVM in Your ERP: Four Steps
Step 1: Define the Work Breakdown Structure
Before measuring anything, structure your projects into homogeneous work packages, each with an owner and a budget. The WBS is EVM’s backbone: the more granular it is, the more precise the metrics. For an 18-month project, a three-level WBS (phase, work package, task) is generally sufficient.
Step 2: Establish the Baseline and Lock PV
Planned Value is meaningful only when grounded in a validated, frozen baseline. Before project start, work package owners must sign off on their budgets and schedules. Once the baseline is locked in the ERP, it should only be modified through a formal Change Control decision. Without this discipline, your metrics have no reference and therefore no value.
Step 3: Enter Physical Progress Separately from Costs
Project managers or work package owners must regularly update physical progress — at least bi-monthly — for each work package, expressed as a percentage complete. This figure is independent of costs incurred: it represents the share of work actually accomplished against an objective criterion (deliverable submitted, milestone reached, quantity installed). The ERP then calculates EV by multiplying that percentage by the work package budget.
Step 4: Configure the Dashboard and Alerts
Set threshold alerts in the ERP for CPI and SPI. A CPI below 0.9 or an SPI below 0.85 on any work package should trigger an automatic notification to the project manager and CFO. These alerts enable corrective action before drift becomes irreversible.
What the CFO and CIO See on Their EVM Dashboard
An operational EVM dashboard contains at minimum six indicators, readable in under two minutes:
- Project-level CPI: trend over the last three periods
- Project-level SPI: physical progress vs. baseline schedule
- EAC: projected final cost, compared against initial BAC
- VAC: projected overrun in absolute value
- CPI by work package: to identify the packages dragging the overall CPI down
- TCPI: performance effort required to stay within budget
This cockpit replaces lengthy review meetings and fragile summary spreadsheets. It demands disciplined data entry — but it delivers visibility that organisations without EVM simply never have during project execution.
What This Means for Your Organisation
Earned Value Management is not a technique reserved for defence contractors or large consultancies. Any engineering firm managing several concurrent projects, billing on progress and committing resources for six months or more has a direct interest in implementing EVM.
The primary condition is not company size — it is rigour: rigour in baseline definition, rigour in physical progress entry, rigour in metric interpretation. A properly configured ERP automates the calculations. It cannot substitute the project manager’s judgement on actual progress.
ISO 21508:2026 and ANSI/EIA-748 provide the frameworks to structure this approach. Your next decision is to choose the ERP that enables you to implement it in your specific context.
To go further, read our ERP guide for engineering and consulting firms, our article on ERP and management control: analytical accounting and budget management and our weekly ERP steering committee template.
