11.1 ANSI/EIA-748 EVM Framework & Core Metrics (PV, EV, AC)

11.1 ANSI/EIA-748 EVM Framework & Core Metrics (PV, EV, AC)

Domain 4 of the May 2026 CCP blueprint — Conduct Performance Measurement/Analysis — is 17% of the exam, 20 questions, the third-largest domain. This section opens it with 4.B measure performance against the baseline and 4.C monitor performance against the baseline, and also carries Domain 1's 1.K monitor Budget-at-Completion (BAC). Note that the blueprint separates measure from monitor: measuring is the periodic calculation at the data date, monitoring is the continuing comparison of that series against the baseline over time.

In capital project management and project controls, traditional cost accounting compares only two variables: budgeted expenditures versus actual expenditures. While this comparison indicates whether money is being spent faster or slower than anticipated, it fails to reveal what was actually accomplished for the money spent. A project may appear "under budget" simply because planned work has not yet been performed, masking severe schedule delays and future cost overruns.

To overcome this fundamental blind spot, Earned Value Management (EVM) introduces a third critical dimension: Earned Value (EV)—the objective quantification of physical work accomplished. Under the AACE International Total Cost Management (TCM) Framework and standard industry practice, EVM serves as the premier project control methodology for integrating scope, schedule, and resource allocation into a unified baseline.

---

1. Genesis & Evolution of the ANSI/EIA-748 Standard

EVM originated in the 1960s within the United States Department of Defense (DoD) as the Cost/Schedule Control Systems Criteria (C/SCSC) during the Minuteman missile development program. C/SCSC established 35 rigorous procedural standards to ensure defense contractors utilized sound internal management systems.

In 1998, the aerospace and defense industries collaborated with the American National Standards Institute (ANSI) and the Electronic Industries Alliance (EIA) to modernize and streamline C/SCSC into a commercially adaptable standard: ANSI/EIA-748 (Standard for Earned Value Management Systems). Today, ANSI/EIA-748 (maintained by the National Defense Industrial Association - NDIA) defines 32 guidelines organized into five core functional categories.

+-----------------------------------------------------------------------------+
|                   THE 32 CRITERIA OF ANSI/EIA-748 (5 CATEGORIES)             |
|                                                                             |
|   1. ORGANIZATION (Guidelines 1 - 5)                                        |
|      • Define project Work Breakdown Structure (WBS) down to Work Packages. |
|      • Establish Organizational Breakdown Structure (OBS).                  |
|      • Integrate WBS and OBS into Control Accounts (CAs) with assigned CAMs.|
|                                                                             |
|   2. PLANNING, SCHEDULING & BUDGETING (Guidelines 6 - 15)                   |
|      • Establish integrated CPM schedule and identify physical milestones.  |
|      • Establish the Performance Measurement Baseline (PMB) = Σ PV.         |
|      • Identify Budget at Completion (BAC) and separate Management Reserve. |
|      • Assign objective work measurement methods to every Work Package.     |
|                                                                             |
|   3. ACCOUNTING CONSIDERATIONS (Guidelines 16 - 21)                         |
|      • Record direct and indirect actual costs (ACWP / AC) consistently.    |
|      • Ensure cost accruals synchronize with physical work performed.       |
|      • Summarize costs directly through the WBS without allocation bias.    |
|                                                                             |
|   4. ANALYSIS & MANAGEMENT REPORTS (Guidelines 22 - 27)                     |
|      • Compute Cost Variance (CV), Schedule Variance (SV), CPI, and SPI.    |
|      • Analyze variance thresholds to identify root causes and impacts.     |
|      • Calculate realistic Estimate at Completion (EAC) and ETC forecasts.  |
|                                                                             |
|   5. REVISIONS & DATA MAINTENANCE (Guidelines 28 - 32)                      |
|      • Implement formal baseline change control (prevent retroactivity).    |
|      • Manage Authorized Unpriced Work (AUW) and baseline replanning.       |
+-----------------------------------------------------------------------------+

The Control Account (CA) Architecture

The Control Account is the primary management control point where scope, budget, schedule, and actual performance are integrated and managed. It sits at the intersection of the Work Breakdown Structure (WBS) (what work will be done) and the Organizational Breakdown Structure (OBS) (who will do it). Every Control Account is led by a single responsible Control Account Manager (CAM).

Control Accounts are further decomposed into:

• Work Packages (WPs): Short-duration, discrete work elements with assigned budgets, specific start/finish dates, and objective progress measurement techniques.
• Planning Packages (PPs): Future work within a control account that is not yet detailed enough for work package conversion. Planning packages contain scope, budget, and tentative schedule but no active progress measurement techniques.

---

2. The Three Fundamental EVM Metrics

EVM relies on three core data elements evaluated at any given point in time (the Data Date):

+-----------------------------------------------------------------------------+
|                     THE THREE CORE EVM FOUNDATION METRICS                   |
|                                                                             |
|   1. PLANNED VALUE (PV) / BCWS                                              |
|      • Budgeted Cost for Work Scheduled                                     |
|      • PV = Authorized budget assigned to scheduled work up to the Data Date|
|      • Cumulative PV curve forms the Performance Measurement Baseline (PMB) |
|                                                                             |
|   2. EARNED VALUE (EV) / BCWP                                               |
|      • Budgeted Cost for Work Performed                                     |
|      • EV = % Physical Complete × Budget at Completion (BAC_task)           |
|      • The true objective metric of physical progress accomplished          |
|                                                                             |
|   3. ACTUAL COST (AC) / ACWP                                                |
|      • Actual Cost of Work Performed                                        |
|      • AC = Total direct and indirect expenditures incurred in executing    |
|        the work that yielded the Earned Value (including accruals)          |
+-----------------------------------------------------------------------------+

Mathematical Definitions & Units

All three core metrics must be expressed in identical, common units of measurement—typically monetary currency ($) or direct labor hours (work-hours):

1. Planned Value ($PV$): $PV = \sum_{i=1}^{n} (\text{Planned } \% \text{ Complete}_i \times BAC_i)$
2. Earned Value ($EV$): $EV = \sum_{i=1}^{n} (\text{Actual Physical } \% \text{ Complete}_i \times BAC_i)$
3. Actual Cost ($AC$): $AC = \text{Direct Labor Costs} + \text{Direct Material Costs} + \text{Subcontract Costs} + \text{Allocated Indirects} + \text{Uninvoiced Accruals}$

[!IMPORTANT] Earned Value is Valued at Baseline Rates: Earned Value ($EV$) is always calculated using the original budgeted unit rates or baseline budget ($BAC$), never actual cost rates. This ensures that variances in productivity (schedule accomplishment) are completely decoupled from variances in labor wages or material unit prices.

---

3. Project Budget Architecture & Budget at Completion (BAC)

A fundamental requirement of ANSI/EIA-748 is establishing a clear, hierarchically structured budget architecture. Total project funding must be rigorously partitioned to maintain baseline integrity:

+-----------------------------------------------------------------------------+
|                        TOTAL ALLOCATED BUDGET (TAB)                         |
|                                                                             |
|   +----------------------------------------------------+----------------+   |
|   |    PERFORMANCE MEASUREMENT BASELINE (PMB = BAC)    |   MANAGEMENT   |   |
|   |                                                    |  RESERVE (MR)  |   |
|   |  +-------------------------+--------------------+  |  (Held by PM   |   |
|   |  |     CONTROL ACCOUNTS    |   UNDISTRIBUTED    |  |  for unknown/  |   |
|   |  |  +---------+---------+  |    BUDGET (UB)     |  |  unforeseen    |   |
|   |  |  | Work    | Planning|  |   (Authorized,     |  |  in-scope      |   |
|   |  |  | Packages| Packages|  |    unallocated     |  |  risks)        |   |
|   |  |  | (WPs)   | (PPs)   |  |    to CAs)         |  |                |   |
|   +--+--+---------+---------+--+--------------------+--+----------------+   |
+-----------------------------------------------------------------------------+

Key Budget Definitions:

1. Budget at Completion ($BAC$): The total authorized budget for all work scheduled across the entire project life cycle. $BAC = \sum PV_{\text{terminal}} = \text{Total PMB Budget}$.
2. Management Reserve ($MR$): An amount of the total contract budget held separately by the Project Manager for unforeseen, in-scope uncertainties and risk events. $MR$ is NOT part of the Performance Measurement Baseline ($PMB$), has no schedule, and has no planned value ($PV$). Once an approved risk event occurs, budget is formally transferred from $MR$ into specific Control Accounts.
3. Undistributed Budget ($UB$): A temporary holding account for authorized scope changes that have been contractually approved but have not yet been distributed to specific Control Accounts.
4. Total Allocated Budget ($TAB$): $TAB = PMB + MR = BAC + MR$

---

4. The S-Curve Performance Tracking Framework

When time-phased planned value, earned value, and actual cost are plotted cumulatively against project calendar time, they form characteristic S-Curves.

+-----------------------------------------------------------------------------+
|                      THE CUMULATIVE EVM S-CURVE MODEL                       |
|                                                                             |
|   Cumulative Cost ($)                                                       |
|          ^                                                    BAC           |
|          |                                                  .-----[*]       |
|          |                                             .---'       |        |
|          |                                        .---'            |        |
|          |                                   .---'  AC             |        |
|          |                              .---'   .- - - -           |        |
|          |                         .---'     .-' (Actual Cost)     |        |
|          |                    .---'       .-'                      |        |
|          |               .---'         .-'                         |        |
|          |          .---'           .-'  PV (Planned Baseline)     |        |
|          |     .---'             .-'                               |        |
|          |.---'               .-'     EV (Earned Accomplishment)   |        |
|          |                 .-'                                     |        |
|          |              .-'                                        |        |
|          +---------------+-----------------------------------------+----->  |
|                          |                                                  |
|                      Data Date                                    Finish    |
|                     (Time-Now)                                     Date     |
+-----------------------------------------------------------------------------+

Anatomy of the S-Curve:

• Startup / Ramp-Up Phase (Concave Up): Slow initial expenditures during mobilization, engineering setup, and procurement submittals.
• Peak Execution Phase (Linear Steep Slope): Maximum resource mobilization, mass craft labor deployment, major equipment deliveries, and peak installation velocity.
• Closeout / Commissioning Phase (Concave Down): Tapering expenditures during punch list resolution, pre-commissioning, testing, and handover.

The Three Curves at the Data Date:

At the Data Date, plotting $PV$, $EV$, and $AC$ allows instant visual diagnostics:

• Vertical Gap Between $EV$ and $PV$: Schedule Variance ($SV$). If $EV$ is below $PV$, work is behind schedule.
• Vertical Gap Between $EV$ and $AC$: Cost Variance ($CV$). If $AC$ is above $EV$, work is over budget.
• Horizontal Distance Between $EV$ and $PV$: Earned Schedule ($ES$). Shows the time difference between when the work was accomplished and when it was planned.

---

5. The Data Date Protocol & Accounting Synchronization

The Data Date (also termed Status Date, Time-Now, or As-Of Date) is the defined calendar date up to which all historical project data (actual costs, actual progress, schedule completions) is reported, and from which all future forecasts and remaining baseline activities are projected.

The Golden Rule of EVMS Data Integrity:

[!CAUTION] Strict Accounting and Schedule Cutoff Synchronization: Actual costs ($AC$) and physical progress ($EV$) must be recorded up to the exact same calendar cutoff date. If progress is recorded through Day 30 but the accounting ledger only includes invoices approved through Day 15, the project will display a false favorable cost variance because work completed in the second half of the month has zero associated cost in the ledger.

To prevent accounting distortions, cost engineers must implement Accrual Accounting—estimating and booking unvouchered physical work performed, unpaid subcontractor invoices, and delivered materials into $AC$ at the status date.