Earned Value Management is built on a hierarchical structure that connects the full scope of a program to the people responsible for executing it. Before any performance metric can be calculated, before any variance can be analyzed, the program must be decomposed into discrete, manageable, and measurable units of work. The architecture that makes this possible is built from three fundamental components: control accounts, work packages, and planning packages.
Understanding how these elements work — and how they fail — is prerequisite to understanding why EVMS compliance problems manifest the way they do.
The Work Breakdown Structure and the Organizational Breakdown Structure
Every EVMS begins with two decomposition structures. The Work Breakdown Structure (WBS) decomposes the total program scope into progressively smaller deliverables and components. The Organizational Breakdown Structure (OBS) decomposes the performing organization into responsible entities — divisions, departments, subcontractors. The WBS answers the question "what is being built?" The OBS answers "who is responsible for building it?"
The intersection of these two structures produces the control account. Every element of work scope from the WBS is assigned to exactly one element of the OBS. The point where they meet is the control account — the basic unit of EVMS performance measurement.
The Control Account
A control account is a management control point where scope, schedule, and budget are integrated and actual performance is measured against the plan. Each control account has a Control Account Manager (CAM) — the individual accountable for its technical performance, schedule, and cost.
This is not an administrative designation. The CAM owns the budget for the control account, authorizes the work packages within it, tracks performance, and is responsible for preparing the Estimates at Completion (EACs) that roll up to the program level. In a well-run EVMS, the control account is the lowest level at which meaningful management decisions are made.
Control accounts are sized based on risk and complexity. A high-risk deliverable with significant technical uncertainty warrants a more granular control account structure — smaller in scope, shorter in duration, more frequently measured. A routine, well-understood deliverable can be managed at a higher level without sacrificing oversight quality.
Work Packages
Within each control account, the near-term work is planned as work packages. A work package is a discrete, short-duration element of work with:
- A defined scope of work
- A scheduled start and finish date
- A budget (expressed as a time-phased plan)
- An objective method for measuring physical completion
The objective measurement method is critical. EVMS requires that earned value credits be earned based on objective evidence of physical accomplishment — not on the subjective opinion of a project team that says work is "about 60% done." Approved measurement methods include: 0/100 (no credit until fully complete), 50/50 (50% credit at start, 50% at completion), milestones with weighted values, and percent complete with weighted milestones.
Work packages are intended to be short-duration — DCMA surveillance guidelines consider durations greater than 44 working days to be a schedule health concern. This is not arbitrary. Long work packages are harder to status accurately, more susceptible to percent-complete padding, and less useful as early warning indicators of slippage.
Planning Packages
Not all work can be planned at the work package level from the outset of a program. Work scheduled in the far future — often a year or more away — may not yet be defined at sufficient detail to support meaningful work package planning. For this work, EVMS provides the planning package.
A planning package is a budget holder for far-term work within a control account. It represents a known cost and schedule commitment without the detailed task-level definition of a work package. Planning packages must be converted to work packages before their scheduled work begins — this process, called "rolling wave planning," is a formal EVMS requirement.
The conversion of planning packages to work packages is a surveillance target. A program that never converts its planning packages, or that converts them at the last possible moment without adequate definition, has failed to plan its work. A program that shows a large proportion of budget still in planning packages as near-term work approaches is a program that does not have a credible path to execution.
Where the Architecture Fails
Most EVMS compliance problems can be traced back to one of three structural failures in this architecture.
Scope is not fully decomposed. Work that is not in the WBS is not in the baseline. Undistributed budget — work that is acknowledged but not yet assigned to a control account — is a legitimate temporary condition. Chronic undistributed budget is a sign that the program scope is not under control.
Control accounts are too large. When control accounts span multiple years, contain hundreds of work packages, or cover multiple responsible organizations, the measurement resolution needed for effective management is lost. Performance problems can hide inside a large control account for months before they are visible at the reporting level.
Earned value is not measured objectively. This is the most common and most consequential failure. When percent-complete is estimated subjectively — when a CAM says work is "80% done" because it feels that way — the earned value figure is unreliable. The schedule variance and cost variance derived from that figure are unreliable. The EAC built on that performance data is unreliable. The entire purpose of the EVMS is defeated.
The architecture of control accounts, work packages, and planning packages is only as strong as the discipline with which it is maintained.
The Forensic Intelligence Engine validates control account structure, work package completeness, and earned value measurement methods against EVMS compliance requirements — and cross-references findings against the governing contract to identify where structural failures carry contractual consequences.