Home / Aerospace and defense program execution / Front-end planning for aerospace and defense programs
An earned value management system is supposed to answer one question with evidence: are we getting the work we paid for, on the schedule we planned? EIA-748 is the standard that defines what such a system must do. Setting it up correctly at the start of a program is far cheaper than defending a weak one later.
What EIA-748 actually requires
EIA-748 describes 32 guidelines, grouped into five areas. None of them names a tool or a report format. Each one describes a management outcome the system must produce, which is why two contractors can both comply while working very differently.
| Area | Guidelines | What it covers |
|---|---|---|
| Organization | 1 to 5 | Defining the work breakdown structure, the organizational structure, and who is responsible for each piece of work |
| Planning, scheduling and budgeting | 6 to 15 | Scheduling the work, setting budgets tied to it, establishing the performance measurement baseline and controlling reserves |
| Accounting considerations | 16 to 21 | Recording actual costs so they line up with the budgets and the work they were spent on |
| Analysis and management reports | 22 to 27 | Comparing planned, earned and actual values, explaining variances and forecasting the estimate at completion |
| Revisions and data maintenance | 28 to 32 | Controlling changes to the baseline so it stays honest and every change is traceable |
When a defense contract requires it
The Defense Federal Acquisition Regulation Supplement sets the thresholds. As a general rule, cost or incentive contracts above the applicable threshold require an earned value management system that complies with EIA-748. At a higher threshold, the system must also be validated by the government, which on most Department of Defense work means a formal review by DCMA. Firm fixed price contracts are usually outside these requirements, although a program office can still ask for earned value data. Thresholds and applicability do change, so the clauses in the actual contract are the final word.
Prime contractors also flow earned value requirements down to major subcontractors. A supplier that has never run an EVMS can find itself needing one because a prime's contract requires it.
The five places programs usually go wrong
A work breakdown structure that mirrors the org chart. The WBS should describe the product and the work to deliver it. When it is built around departments instead, costs and progress stop lining up with deliverables, and the reports describe the organization rather than the program.
A schedule that is not integrated with the budget. The integrated master schedule and the cost baseline must describe the same work at the same level. When they drift apart, earned value becomes a reconciliation exercise every month and nobody trusts either one.
Progress measured by opinion. Earning value by percent complete estimates invites optimism. Objective measures, such as discrete milestones within a work package, produce numbers that hold up under review.
Variances explained, but never acted on. A variance analysis that describes what happened without saying what will be done about it satisfies the report and helps no one. The analysis is only useful when it drives a decision.
Uncontrolled baseline changes. Rolling the baseline every time the program slips makes the performance numbers look fine and hides the real trend. Disciplined change control, with every change traceable to an authorized reason, is what keeps the system honest.
What is the performance measurement baseline?
The performance measurement baseline is the time-phased budget plan against which performance is measured. It is made up of the budgets distributed to control accounts, plus any undistributed budget that has not yet been assigned. Management reserve sits outside it, held for unforeseen work within the contract scope. Together, the performance measurement baseline and management reserve make up the contract budget base. Keeping these elements separate and traceable is what lets a program show honestly how much of its budget is committed to planned work and how much remains in reserve.
Which earned value techniques should be used?
| Technique | How value is earned | Best suited to |
|---|---|---|
| 0/100 | All value when the work is complete | Short tasks completed within one reporting period |
| 50/50 | Half at start, half at completion | Work spanning about two periods |
| Weighted milestones | Value assigned to objective milestones within the work package | Longer discrete work; the most defensible technique |
| Percent complete | Value based on an estimate of progress | Work that cannot be split into milestones; needs clear rules |
| Apportioned effort | Value tied to the progress of related discrete work | Inspection or support effort that scales with other work |
| Level of effort | Value earned with the passage of time | Genuine support activity; keep it to a small share of the budget |
The choice matters because level of effort earns value whether or not anything was accomplished. Programs with a large share of level of effort can report healthy indices while discrete work slips, so reviewers look closely at how much of the baseline uses it.
How are variances analyzed?
Each program sets variance thresholds, often a percentage combined with a dollar amount, beyond which a control account manager must explain the variance. A useful variance analysis states what happened, why, the impact on the estimate at completion and schedule, and the corrective action with a date. Analyses that only describe the past satisfy the requirement without helping the program. Reviewers and customers read them to judge whether the program understands its own performance.
What does a healthy earned value system feel like from the inside?
Control account managers use their own reports to run their work, not just to fill in a monthly template. Variances are discussed while they are small. The estimate at completion moves when the facts change, not only at year end. And the numbers the program manager sees, the numbers finance sees and the numbers the customer sees all come from the same source. When those things are true, the system is doing its job, and compliance reviews tend to follow naturally.
Which earned value numbers should a program manager watch?
Six of them, and every one is built from the same three inputs: planned value, the budget for the work scheduled to be done by now; earned value, the budget for the work actually done; and actual cost, what that work really cost. Once those three are honest, the measures below follow directly. If any of them is soft, every measure built on it is soft too.
| Measure | How it is calculated | What it tells you | What to watch for |
|---|---|---|---|
| Cost variance | Earned value minus actual cost | Whether the work completed cost more or less than its budget | A negative variance that grows every month, rather than one bad month |
| Schedule variance | Earned value minus planned value | Whether the planned volume of work is getting done | It is measured in budget dollars, not days, so it cannot tell you how late anything is |
| Cost performance index (CPI) | Earned value divided by actual cost | How much value the program earns for each dollar it spends | A cumulative CPI below 1.0 that keeps falling; the cumulative figure tends to change slowly once a meaningful share of the work is done, so an early decline deserves attention |
| Schedule performance index (SPI) | Earned value divided by planned value | The pace of work against the plan | It drifts back toward 1.0 near the end of a program because all the planned value is eventually earned, even when it is earned late |
| To-complete performance index (TCPI) | Remaining work (budget at completion minus earned value) divided by remaining funds (budget at completion minus actual cost) | The efficiency the rest of the work must achieve to finish on budget | A value well above the current CPI, which means the budget target is no longer realistic |
| Estimate at completion (EAC) | One common form is actual cost plus the remaining work divided by CPI | The forecast final cost of the program | An EAC that stays flat while CPI declines |
The schedule measures carry an important limit. They count the volume of work earned, not whether the right work is being done. A program can report an SPI close to 1.0 while its critical path slips, because work that is not critical is running ahead and offsetting it. That is why earned value data has to be read alongside the integrated master schedule, which shows what the slip does to the dates that matter. When both point the wrong way, a schedule recovery plan is usually the next step.
How should the estimate at completion be built?
From two directions, then compared. The first is a set of formula-based estimates that project past performance forward using the cost and schedule indices. The second is a bottom-up estimate in which each control account manager estimates the cost of the work that actually remains. The GAO Cost Estimating and Assessment Guide treats a range of independent estimates as a check on the contractor's own figure, and that comparison is where most of the insight sits. If the bottom-up estimate is much better than past performance suggests, the program should be able to say exactly what will change to make it true.
A credible estimate at completion usually has these qualities:
- Remaining work estimated by its owner. Each control account's estimate to complete comes from the person accountable for the work, not from a formula applied by finance.
- Risks and opportunities reflected or named. Known risks are either priced into the estimate or listed as exclusions, so leadership can see what the number does and does not cover.
- Current rates. Labor and overhead rates match what the business will actually charge over the remaining period, not the rates used at proposal.
- Agreement with the schedule forecast. A later finish usually costs more, because support and level of effort work continue for as long as the program runs.
- Management reserve kept separate. Reserve is not quietly spent inside the estimate, so the program can show what it needs and what it still holds.
Estimate at completion development is part of the project controls work we do, and it connects directly to risk and opportunity management, because the risks a program carries are what separate an optimistic estimate from a realistic one.
What does the customer see each month?
On Department of Defense contracts with earned value requirements, the data is typically delivered through the Integrated Program Management Data and Analysis Report, known as the IPMDAR. It replaced the older Contract Performance Report and the integrated master schedule data item. Instead of formatted forms, it delivers cost data and schedule data as structured files, along with a performance narrative that explains significant variances and the corrective action being taken.
That change has a practical consequence. Customer analysts receive the underlying data, so they can calculate their own indices, run their own schedule checks and compare the cost and schedule files against each other. Inconsistencies that a formatted report might once have smoothed over are now easy to see. The simplest protection is the one described above: the numbers the program manager uses, the numbers finance uses and the numbers the customer receives should all come from the same source. If you are not sure yours do, an independent program assessment will show where they diverge.
Related guides
- Building an integrated master schedule that works
- Preparing for an integrated baseline review
- Independent program assessment
- Agile and earned value on engineering programs
Setting it up at the front end
An earned value system is easiest to build before the program starts and hardest to retrofit once it is running. During front-end planning, Set Boundaries works with the program team to build the pieces in the order they depend on each other: a product-oriented work breakdown structure, the responsibility assignments, an integrated master schedule that passes the DCMA 14-point assessment, budgets loaded against that schedule, and the change control process that will protect the baseline once work begins.
The goal is not a binder that satisfies a review. It is a system the program manager actually uses to run the program, which is also the most reliable way to pass the review. The integrated baseline review goes far more smoothly when the baseline was built to be used.
If a new contract is bringing earned value requirements you have not had to meet before, or an existing system is not holding up, schedule a call to talk it through.
References
- SAE International and the Electronic Industries Alliance, EIA-748, Earned Value Management Systems.
- National Defense Industrial Association, Integrated Program Management Division, Earned Value Management Systems EIA-748 Intent Guide.
- US Department of Defense, Earned Value Management System Interpretation Guide.
- US Department of Defense, Earned Value Management Implementation Guide.
- Federal Acquisition Regulation, Subpart 34.2, Earned Value Management System.
- Defense Federal Acquisition Regulation Supplement, Subpart 234.2 and clauses 252.234-7001 and 252.234-7002.
- US Government Accountability Office, Cost Estimating and Assessment Guide, GAO-20-195G.
- US Government Accountability Office, Schedule Assessment Guide: Best Practices for Project Schedules, GAO-16-89G.
Questions
Common questions
What is EIA-748?
EIA-748 is the industry standard for earned value management systems. It sets out 32 guidelines that describe what a management system must do to plan work, control budgets, measure performance honestly and report it. It describes outcomes, not software, so a contractor can meet it with different tools and processes.
When does a defense contract require an EVMS?
Under the DFARS earned value clauses, cost or incentive contracts above the applicable threshold generally require a system that complies with EIA-748, and above a higher thresholdthe system must also be formally validated by the government, which for most Department of Defense work means DCMA. Thresholds and applicability can change, so confirm them against the clauses in your contract.
What is the difference between compliant and validated?
A compliant system meets the 32 guidelines and the contractor asserts that it does. A validated system has been reviewed and accepted by the government through a formal review. Validation is harder to earn and is required on the largest contracts.
Can a small company meet EIA-748?
Yes. The guidelines scale. A small business does not need an enterprise toolset to comply; it needs a clear work breakdown structure, an integrated schedule, budgets tied to the work, honest progress measurement and disciplined change control. The discipline matters far more than the software.
What is a performance measurement baseline?
The performance measurement baseline is the time-phased budget plan that a program measures its performance against. It includes the budgets assigned to control accounts and any undistributed budget not yet assigned. Management reserve is held separately for unforeseen work within scope. The baseline changes only through formal change control, which is what keeps performance reporting honest over the life of the program.
What is management reserve?
Management reserve is budget held outside the performance measurement baseline for unforeseen work that is within the scope of the contract but not yet identified. It is not a contingency for overruns on work already planned. When it is used, it moves into the baseline through controlled change. Comparing the remaining reserve with the program's assessed risk exposure is one of the quickest health checks available.
How many EIA-748 guidelines are there?
EIA-748 contains 32 guidelines, grouped into five categories: organization (guidelines 1 to 5), planning, scheduling and budgeting (6 to 15), accounting considerations (16 to 21), analysis and management reports (22 to 27), and revisions and data maintenance (28 to 32). The guidelines describe management outcomes rather than specific tools or report formats, so compliant systems can look quite different from one contractor to another. Set Boundaries helps contractors map their own processes to each guideline and document the evidence.
What are the 32 EVMS guidelines?
The 32 EVMS guidelines in EIA-748 define what an earned value management system must do. They require a defined work breakdown and organization, a schedule and time-phased budget tied to the work, a controlled performance measurement baseline and reserves, cost accounting that aligns actuals with budgets, regular comparison of planned, earned and actual values with variance analysis and estimates at completion, and disciplined control of baseline changes. Each guideline states an outcome, not a method. Set Boundaries builds system descriptions and procedures that show how each guideline is met.
Is EVM required on a FFP contract?
Generally no. DoD policy discourages applying earned value management to firm-fixed-price contracts because the contractor, not the government, carries the cost risk. Under DFARS, EVMS requirements normally apply to cost-reimbursement and incentive contracts above set dollar thresholds, and applying EVM to a firm-fixed-price effort typically requires a documented business case and approval. Thresholds and policy change over time, so always check the specific solicitation and clauses. Set Boundaries helps contractors confirm what a given contract actually requires before building a system.
Have a question that is not here? Ask Holly on a short call
