Earned Value Management (EVM): Tracking Cost and Schedule Performance

Earned Value Management (EVM) is a project management technique that measures performance by comparing planned work (budget) against work completed (earned value) and actual costs incurred.

Why EVM exists:

Traditional metrics are misleading. You can be on budget but behind schedule, or on schedule but over budget. EVM integrates both dimensions to show true project health.

The three key values:

• Planned Value (PV) — Budgeted cost of work scheduled to be completed by a certain date
• Earned Value (EV) — Budgeted cost of work actually completed by that date
• Actual Cost (AC) — Actual cost incurred for work completed by that date

Simple example:

You planned to spend $100K by end of month to complete 10 tasks (PV = $100K). You actually completed 8 tasks, which were budgeted at $80K (EV = $80K). But you spent $90K to complete them (AC = $90K).

• You're behind schedule (only 8 of 10 tasks done)
• You're over budget ($90K spent for $80K of work)

EVM vs. EVMS:

• EVM — The methodology/technique
• EVMS — Earned Value Management System: the processes, tools, and organization to implement EVM, certified to meet 32 guidelines in ANSI/EIA-748

DoD contracts:

• $20M+ — EVM required
• $50M+ — EVMS compliance required (DoDI 5000.91)
• Applies to development, modernization, major modifications

Other federal agencies:

• Varies by agency (NASA, DOE, DHS have their own thresholds)
• Typically $20M+ for major programs
• Check agency-specific acquisition regulations

EVMS compliance requirement:

If your contract requires EVMS compliance, your system must be certified. This involves:

• Integrated Baseline Review (IBR)
• EVMS compliance review by DCMA or customer
• Meeting all 32 ANSI/EIA-748 guidelines
• Ongoing surveillance to maintain certification

Subcontractor flowdown:

If you're a prime with EVMS requirement, you must flow it down to major subs (typically subs with $50M+ effort or critical path work).

Voluntary EVM:

Some contractors use EVM on smaller contracts for better visibility, even when not required. Good practice for complex programs.

Variance metrics:

Schedule Variance (SV):

• Formula: SV = EV - PV
• Meaning: Difference between work completed and work planned
• Positive SV: Ahead of schedule
• Negative SV: Behind schedule

Cost Variance (CV):

• Formula: CV = EV - AC
• Meaning: Difference between value earned and actual cost
• Positive CV: Under budget
• Negative CV: Over budget

Performance indices:

Schedule Performance Index (SPI):

• Formula: SPI = EV / PV
• Interpretation:
• SPI > 1.0: Ahead of schedule
• SPI = 1.0: On schedule
• SPI < 1.0: Behind schedule
• Example: SPI = 0.85 means you're completing work at 85% of planned rate

Cost Performance Index (CPI):

• Formula: CPI = EV / AC
• Interpretation:
• CPI > 1.0: Under budget (good efficiency)
• CPI = 1.0: On budget
• CPI < 1.0: Over budget
• Example: CPI = 0.90 means you're getting $0.90 of value for every $1.00 spent

Forecasting metrics:

Estimate at Completion (EAC):

• Formula: EAC = BAC / CPI (most common)
• Meaning: Projected final cost based on current performance
• BAC: Budget at Completion (original budget)
• Example: $10M contract, CPI = 0.85 → EAC = $11.76M (overrun)

Estimate to Complete (ETC):

• Formula: ETC = EAC - AC
• Meaning: How much more money is needed to finish

Variance at Completion (VAC):

• Formula: VAC = BAC - EAC
• Meaning: Projected final overrun or underrun
• Negative VAC: Overrun expected

To-Complete Performance Index (TCPI):

• Formula: TCPI = (BAC - EV) / (BAC - AC)
• Meaning: CPI needed on remaining work to stay on budget
• Example: TCPI = 1.15 means you need 15% better efficiency than original plan to finish on budget

The 32 ANSI/EIA-748 guidelines:

Organized into 5 categories:

1. Organization (5 guidelines):

• Define work scope
• Identify organization responsible for work
• Integrate planning, budgeting, scheduling, and cost accumulation

2. Planning, Scheduling, and Budgeting (10 guidelines):

• Schedule work with defined start/finish dates
• Identify products, milestones, technical performance
• Establish time-phased budgets
• Establish overhead budgets
• Identify management reserves

3. Accounting Considerations (6 guidelines):

• Record direct costs at lowest WBS level
• Summarize costs to WBS and organizational elements
• Record overhead on consistent basis
• Identify unit costs/equivalent units

4. Analysis and Management Reports (7 guidelines):

• Use data for internal management
• Provide data to customer at WBS/organizational levels
• Implement managerial actions based on data
• Reconcile original and current budgets

5. Revisions and Data Maintenance (4 guidelines):

• Incorporate authorized changes promptly
• Reconcile budgets to authorized changes
• Control retroactive changes
• Prevent unauthorized revisions to records

Getting certified:

1. Integrated Baseline Review (IBR):

• Joint government-contractor review of performance measurement baseline
• Typically within 6 months of contract award
• Validates baseline is realistic and complete

2. Compliance review:

• DCMA or customer evaluates your EVMS
• Reviews policies, procedures, tools, data
• Interviews staff to verify implementation
• Issues compliance determination

3. Ongoing surveillance:

• Periodic DCMA reviews to maintain certification
• Typically annual or biennial
• Can lose certification if system degrades

Cost of EVMS:

Implementing compliant EVMS costs $500K-$2M+ for initial setup (software, training, staff, processes). Annual operating cost: 1-3% of contract value. Only worthwhile on large programs.

Contract Performance Report (CPR):

Standard DoD EVM report format, submitted monthly or as specified in contract.

CPR Formats:

• Format 1: Work Breakdown Structure (WBS) summary
• Format 2: Organizational category summary
• Format 3: Baseline information
• Format 4: Staffing information
• Format 5: Narrative analysis

Integrated Program Management Report (IPMR):

Replaced CPR in 2012. Similar content, different format. More integrated view of cost/schedule/technical performance.

IPMR formats:

• Format 1: WBS summary
• Format 2: Organizational category summary
• Format 3: Baseline summary
• Format 4: Staffing summary
• Format 5: Narrative
• Format 6: Subcontractor summary (if applicable)
• Format 7: Supplemental info (optional)

Submission frequency:

• Typically monthly, due 15-20 days after month-end
• Some contracts require quarterly
• Check CDRL (Contract Data Requirements List) for specifics

Common EVM reporting challenges:

• Data collection from multiple systems (accounting, project management, timekeeping)
• Ensuring consistency across formats
• Meeting tight deadlines after month close
• Explaining variances in Format 5 narrative
• Reconciling subcontractor data

Healthy project indicators:

• CPI > 0.95 (preferably > 1.0)
• SPI > 0.95 (preferably > 1.0)
• Variances are small and explained
• Trends are stable or improving
• EAC is at or below BAC

Warning signs:

• CPI < 0.90: Significant cost inefficiency, unlikely to recover
• SPI < 0.90: Seriously behind schedule
• Declining trend: CPI/SPI getting worse each month
• TCPI > 1.10: Need unrealistic efficiency improvement to finish on budget

The "CPI is king" rule:

Industry data shows CPI stabilizes early (around 20% complete) and rarely improves. If your CPI is 0.85 at 20% complete, you'll likely finish at 0.85. Don't assume you'll "make it up later."

Schedule vs. cost tradeoffs:

• High SPI, low CPI: Accelerating schedule at cost of efficiency (throwing money at problem)
• Low SPI, high CPI: Going slow but efficiently (may miss deadlines to save money)

Common misinterpretations:

• Mistake: "We're 50% through the timeline, so 50% done."
• Reality: Check SPI. You might be 40% done (SPI = 0.80) or 60% done (SPI = 1.20).

• Mistake: "We've spent $5M of $10M, so we're on budget."
• Reality: Check CPI. If CPI = 0.85, you got $4.25M of work for $5M spent (overrunning).

Step 1: Define the Work Breakdown Structure (WBS):

• Decompose program into manageable pieces
• Align with contract SOW and deliverables
• Typical levels: Program → System → Subsystem → Work Package

Step 2: Create the schedule:

• Integrated Master Schedule (IMS) with all tasks
• Define dependencies and critical path
• Schedule must be resource-loaded

Step 3: Develop the budget:

• Allocate budget to WBS elements (Performance Measurement Baseline)
• Time-phase budget based on schedule
• Establish management reserve (unallocated budget for unknowns)

Step 4: Set up accounting:

• Collect actual costs by WBS element
• Typically requires project accounting system or ERP integration
• Must track direct labor, materials, ODCs, overhead

Step 5: Measure earned value:

• Determine what work was completed
• Apply earned value technique (% complete, milestones, units, etc.)
• Calculate EV based on completed work

Earned value techniques:

• Discrete effort: Specific tasks with measurable output (use % complete, milestones, or units)
• Apportioned effort: Work tied to discrete effort (e.g., QA is 10% of development)
• Level of effort (LOE): Work without measurable output (EV = PV by definition, e.g., program management)

Step 6: Analyze and report:

• Calculate variances and indices
• Identify unfavorable trends
• Develop corrective action plans
• Submit required reports (CPR/IPMR)

Tools:

• Dedicated EVMS software: Deltek Cobra, Winsight, Acumen Fuse
• ERP integration: Costpoint, Deltek, SAP
• Project management tools: MS Project, Primavera can do basic EVM

Best practices:

• Realistic baseline: Don't lowball or pad excessively. Use historical data.
• Objective earned value: Use measurable completion criteria, not subjective estimates
• Timely data: Close financial books quickly to meet reporting deadlines
• Root cause analysis: Don't just report variances, explain them and fix them
• Forward focus: EVM shows problems early — act on them, don't just report
• Training: Ensure all project staff understand EVM basics

Common pitfalls:

1. Subjective progress assessment:

• "I'm 70% done" (based on gut feel)
• Leads to inaccurate EV and false confidence

Fix: Use objective measures — lines of code, drawings completed, tests passed.

2. Rear-loading the schedule:

• Putting most budget late in schedule
• SPI looks good early, then crashes at the end

Fix: Load budget based on realistic work flow, not desired cash flow.

3. Ignoring LOE creep:

• Too much Level of Effort work (EV = PV always, masks problems)
• Should be <20% of total work

Fix: Minimize LOE. Make work measurable wherever possible.

4. Not updating the baseline:

• Baseline becomes obsolete after changes
• Variances reflect outdated plan, not real performance

Fix: Incorporate authorized changes promptly (with government approval).

5. Gaming the metrics:

• Claiming more progress than earned
• Moving budget between tasks to hide overruns
• Government sees through this quickly

Fix: Be honest. Bad news early is better than disaster late.