Study guide
7.2 Traditional EV Performance Indices & Late-Project Quirks
AACE Planning and Scheduling Professional PSP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Introduction & AACE PSP Exam Structure
0.1 Current AACE PSP Exam, Eligibility, and Certification Facts 0.2 Planning and Scheduling Professional Roles and Competencies 0.3 Cost Engineering and Scheduling Terminology per RP 10S-90
2 Chapter 1: Scope Definition & Planning Fundamentals
1.1 Work Breakdown Structure (WBS) Architecture & RP 33R-15 1.2 Organization & Resource Breakdown Structures (OBS, RBS, RAM) 1.3 Project Planning and Activity-Logic Development 1.4 Contract Requirements and Delivery Constraints 1.5 Stakeholder Identification, Needs, and Plan Review 1.6 Constructability Methods and Value Engineering 1.7 Resource Identification and Project Variables 1.8 Scope, Goals, Project Plan, and Phase Definition 1.9 Cost Breakdown Structure and Cost Estimate Development 1.10 Phase Relationships, Baseline Plan, Forecasts, and Risk/Recovery Planning
3 Chapter 2: Critical Path Method Mechanics & Network Logic
2.1 Activity Definition and Logic Relationships 2.2 Activity Durations, Productivity, and Work Calendars 2.3 Forward and Backward Pass Mathematical Mechanics 2.4 Float Calculations and Critical-Path Identification
4 Chapter 3: Advanced Network Techniques & Schedule Constraints
3.1 Schedule Constraints and Their Impact on Dates and Float 3.2 Advanced Logic Modeling: Ladders and Fragnets 3.3 Schedule Levels of Detail and Schedule Basis Documentation 3.4 Schedule Scope and Schedule Specification 3.5 Breakdown-Structure Relationships and the Cost Estimate Model 3.6 Stakeholder Feedback and Types of Schedules 3.7 Activities, Milestones, Schedule Quality, and Basis Documentation
5 Chapter 4: Resource Management & Leveling
4.1 Resource Planning, Allocation, and Histograms 4.2 Resource Leveling vs. Resource Smoothing 4.3 Cumulative Resource S-Curves & Productivity Tracking
6 Chapter 5: Baseline Management & Schedule Updating
5.1 Baseline Establishment, Forecasts, and Controlled Revision 5.2 Progress Measurement and Data Date Mechanics 5.3 Out-of-Sequence Logic: Progress Override vs. Retained Logic 5.4 Schedule Update Review and Quality Verification per RP 53R-06 5.5 Cost/Resource Management, Schedule Change, and Feedback 5.6 Acceleration and Recovery Scheduling per RP 54R-07 5.7 Control Schedules, Variance Analysis, Forecasts, and Management Summaries
7 Chapter 6: Schedule Risk Analysis & Monte Carlo Simulation
6.1 Schedule Risk Principles, Risk Drivers, and Three-Point Estimates 6.2 Monte Carlo Simulation, Criticality, Correlation, and Merge Effects 6.3 Risk Outputs, Confidence Dates, Sensitivity, and Contingency
8 Chapter 7: Earned Value & Earned Schedule Management
7.1 Earned Value Foundations: PV, EV, AC, and Variances 7.2 Traditional EV Performance Indices & Late-Project Quirks 7.3 Earned Schedule (ES) Theory, SV(t), and SPI(t) 7.4 Independent Schedule Forecasting & IEAC(t)
9 Chapter 8: Forensic Schedule Analysis & Delay Claims
8.1 Delay Classification, Criticality, and Contract Questions 8.2 RP 29R-03 Taxonomy, Data Validation, and Method Selection 8.3 TIA, Windowed Analysis, and Subtractive Models 8.4 Concurrency, Pacing, and Float: Technical Analysis Before Entitlement
10 Chapter 9: Executive Communication & Practical Scenario Applications
9.1 Official PSP Memo Writing Framework 9.2 Structured Technical Problem-Solving for PSP Scenarios 9.3 Current Exam Strategy and Core Calculation Review
7.2 Traditional EV Performance Indices & Late-Project Quirks
Key Takeaways Explain This Topic AI
Traditional EV efficiency indices comprise the Schedule Performance Index ( S P I = E V / P V SPI = EV / PV SP I = E V / P V ) and Cost Performance Index ( C P I = E V / A C CPI = EV / AC CP I = E V / A C ).
The Critical Ratio / Composite Index ( C R = C P I × S P I CR = CPI \times SPI CR = CP I × SP I ) provides an integrated multi-dimensional snapshot of project operational health.
The traditional Schedule Performance Index exhibits a fatal mathematical flaw late in a project: as E V EV E V approaches B A C BAC B A C and P V PV P V reaches B A C BAC B A C , S P I SPI SP I is mathematically forced to converge to 1.00 and S V SV S V to $0, regardless of how delayed the project actually is.
Schedule Variance ( S V SV S V ) is denominated in dollars or work hours, not units of calendar time; a project with S V SV S V = -$500,000 cannot be directly interpreted as being 50 days late.
Traditional EVM lacks network topology awareness: earning massive EV on non-critical activities can artificially create S P I ≥ 1.00 SPI \ge 1.00 SP I ≥ 1.00 , completely masking severe slippage on the CPM critical path.
Last updated: October 2026
7.2 Traditional EV Performance Indices & Late-Project Quirks
AACE Professional Context: Earned Value Management is a widely used integrated performance method, but its traditional schedule metrics—specifically Schedule Variance ( S V = E V − P V SV = EV - PV S V = E V − P V ) and the Schedule Performance Index ( S P I = E V / P V SPI = EV / PV SP I = E V / P V )—harbor profound mathematical and structural limitations. On the PSP examination, planning professionals must not only know how to calculate traditional performance indices, but also possess the advanced analytical capability to identify when and why traditional EV metrics fail, recognize the 'convergence trap' near project completion, and explain why earned value must never be evaluated in isolation from CPM network critical path float.
Traditional Performance Indices: SPI, CPI, and the Critical Ratio
Performance indices convert absolute dollar variances into dimensionless ratios representing operational efficiency. These metrics allow cross-project benchmarking and serve as the mathematical foundation for statistical forecasting.
- 1. Schedule Performance Index ( S P I SPI SP I )
- S P I = E V P V \mathbf{SPI = \frac{EV}{PV}} SPI = PV EV
Measures the efficiency of work accomplished relative to the baseline schedule plan.
S P I > 1.00 SPI > 1.00 SP I > 1.00 : Favorable. Work is being earned at a faster rate than planned.
S P I = 1.00 SPI = 1.00 SP I = 1.00 : On plan. Work earned exactly equals scheduled work.
S P I < 1.00 SPI < 1.00 SP I < 1.00 : Unfavorable. Work is being earned at a slower rate than planned (e.g., S P I = 0.80 SPI = 0.80 SP I = 0.80 implies earning $0.80 of work for every $1.00 scheduled).
- 2. Cost Performance Index ( C P I CPI CP I )
- C P I = E V A C \mathbf{CPI = \frac{EV}{AC}} CPI = AC EV
Measures the financial efficiency of work accomplished relative to actual expenditures.
C P I > 1.00 CPI > 1.00 CP I > 1.00 : Favorable. Project is experiencing cost underrun efficiency (e.g., C P I = 1.25 CPI = 1.25 CP I = 1.25 indicates $1.25 of work earned for every $1.00 spent).
C P I = 1.00 CPI = 1.00 CP I = 1.00 : On budget.
C P I < 1.00 CPI < 1.00 CP I < 1.00 : Unfavorable. Project is burning money faster than earning work (e.g., C P I = 0.80 CPI = 0.80 CP I = 0.80 indicates $0.80 of work earned per $1.00 spent).
Durable Rule of Thumb: Empirical research across defense and infrastructure megaprojects demonstrates that cumulative C P I CPI CP I stabilizes once a project reaches approximately 20% completion; it rarely improves by more than 0.10 from that point forward without formal re-baselining.
- 3. Critical Ratio / Composite Index ( C R CR CR )
- C R = C P I × S P I \mathbf{CR = CPI \times SPI} CR = CPI × SPI
Provides a composite health indicator balancing cost and schedule efficiency.
If a project is behind schedule ( S P I = 0.85 SPI = 0.85 SP I = 0.85 ) but significantly under budget ( C P I = 1.20 CPI = 1.20 CP I = 1.20 ), its composite index is C R = 1.20 × 0.85 = 1.02 CR = 1.20 \times 0.85 = 1.02 CR = 1.20 × 0.85 = 1.02 , indicating overall manageable project stability.
If both indices lag ( S P I = 0.80 , C P I = 0.80 SPI = 0.80, CPI = 0.80 SP I = 0.80 , CP I = 0.80 ), C R = 0.64 CR = 0.64 CR = 0.64 , indicating critical project distress.
The Fatal Flaw: The Late-Project SPI Convergence Quirk
The most dangerous limitation of traditional EVM is the behavior of S V SV S V and S P I SPI SP I as a project approaches and passes its planned completion date. This phenomenon is frequently tested on the AACE PSP exam. THE LATE-PROJECT SPI CONVERGENCE TRAP
- SPI Value
- ▲
- 1.20│
1.00│───────Planned Performance (1.00)───────────────────────► CONVERGES TO 1.00!
- │ ▲
- 0.80│ Actual SPI Drops │
- │ \ │ False Recovery
- 0.60│ \ / (EVM Blind Spot)
- │ \ /
- 0.40│ └─── Late Project ┘
- └───────────────────────────────────┬──────────────────┬──────────────► Time
- Target Finish Actual Finish
- (PD) (Late)
- Mathematical Origin of the Quirk
By definition, the Planned Value curve terminates at project completion when P V = B A C PV = BAC P V = B A C . Once the planned duration ( P D PD P D ) elapses, Planned Value stops growing ; it remains fixed at P V = B A C PV = BAC P V = B A C .
Even if a project is catastrophically delayed by months or years, physical work continues until all scope is finally completed. Therefore, Earned Value continues to rise toward B A C BAC B A C .
As physical completion nears 100%: E V → B A C EV \to BAC E V → B A C P V = B A C PV = BAC P V = B A C
Look at what happens to the mathematical formulas: lim E V → B A C S V = E V − P V = B A C − B A C = $ 0 \lim_{EV \to BAC} SV = EV - PV = BAC - BAC = \mathbf{\text{\textdollar}0} lim E V → B A C S V = E V − P V = B A C − B A C = $ 0 lim E V → B A C S P I = E V P V = B A C B A C = 1.00 \lim_{EV \to BAC} SPI = \frac{EV}{PV} = \frac{BAC}{BAC} = \mathbf{1.00} lim E V → B A C SP I = P V E V = B A C B A C = 1.00
The Real-World Danger of SPI Convergence
Consider a $10 million hospital construction project planned for 12 months. At Month 12, the contractor has achieved only $7 million of work ( E V EV E V = $7M, P V PV P V = $10M, S P I = 0.70 SPI = 0.70 SP I = 0.70 ). The project is severely delayed.
During Months 13 through 18, the contractor finishes the remaining $3 million of work.
At Month 15: E V EV E V = $9M, P V PV P V = $10M ⟹ S P I = 0.90 \implies SPI = 0.90 ⟹ SP I = 0.90 , S V SV S V = -$1M.
At Month 18: E V EV E V = $10M, P V PV P V = $10M ⟹ S P I = 1.00 \implies SPI = 1.00 ⟹ SP I = 1.00 , S V SV S V = $0!
The Absurd Reality: An executive reviewing the monthly EV dashboard sees S P I SPI SP I rise from 0.70 to 0.90 to 1.00, giving the illusion of a heroic schedule recovery. In reality, the project finished 6 months late (50% schedule overrun) ! Traditional S P I SPI SP I and S V SV S V completely lost their ability to signal schedule performance.
Dollar-Denominated Schedule Variance Confusion
Another fundamental defect of traditional EVM is that Schedule Variance is denominated in currency units (dollars, euros) or labor hours, NOT calendar time .
Why Dollars Cannot Measure Time
If a project controls report states: S V SV S V = -$250,000, what does this mean to the site superintendent?
Does it mean the project is 2 days late? 2 weeks late? 2 months late?
It is impossible to know without looking at the rate of expenditure (the slope of the PV curve) at that specific period.
Furthermore, the magnitude of S V SV S V is heavily skewed by the capital intensity of the work packages active during that window:
A delay on an activity involving the delivery of a $2,000,000 gas compressor generates an immediate negative S V SV S V of -$2,000,000.
A delay on a $15,000 software integration logic activity on the critical path generates an S V SV S V of only -$15,000.
Traditional EVM flags the $2,000,000 compressor as an existential schedule disaster, even if it has 90 days of float, while ignoring the $15,000 critical path activity that is actively delaying total project commissioning!
Critical Path vs. Non-Critical Path Earned Value Distortion
Traditional EVM treats every dollar of budget identically. It possesses zero network topology awareness . It cannot differentiate between a dollar earned on the zero-float critical path and a dollar earned on a low-priority task with 200 days of float. CRITICAL PATH vs. NON-CRITICAL PATH EV DISTORTION
- Baseline Plan (Month 4): Target PV = \$500,000
- ┌───────────────────────────────────────────────┬───────────────────────────────┐
- │ Critical Path Foundation Work: \$250,000 │ Non-Critical Landscaping: │
- │ (Zero Float - Drives Completion Date) │ \$250,000 (120 Days Float) │
- └───────────────────────────────────────────────┴───────────────────────────────┘
Actual Field Execution at Month 4:
- ┌───────────────────────────────────────────────┬───────────────────────────────┐
- │ Critical Foundations: 0% Earned (EV = \$0) │ Non-Critical Landscaping: │
- │ STALLED DUE TO PERMIT DELAY │ Accelerated! 100% Earned │
- │ Critical path delayed by 60 days! │ EV = \$500,000 (Scope advance)│
- └───────────────────────────────────────────────┴───────────────────────────────┘
Consolidated EVM Project Report:
- Total Planned Value (PV): \$250,000 + \$250,000 = \$500,000
- Total Earned Value (EV): \$0 + \$500,000 = \$500,000
- Schedule Variance (SV): EV - PV = \$500,000 - \$500,000 = \$0
- Schedule Index (SPI): EV / PV = \$500,000 / \$500,000 = 1.00
STATUS REPORT: "Project is exactly on schedule (SPI = 1.00)!"
FIELD REALITY: Project completion date has slipped 2 months on the critical path!
The "Cherry-Picking" / "Front-Loading" Vulnerability
Because contractors are often evaluated or paid based on S P I SPI SP I and progress billing, unprincipled project managers can artificially inflate S P I SPI SP I by deploying crews to execute non-critical, easy-to-earn work packages (such as bulk excavation or procurement deliveries with high float), while critical path engineering or permitting languishes.
The AACE Professional Mandate
earned-value management practice and AACE scheduling principles mandate that Earned Value must never be interpreted without cross-referencing the CPM schedule critical path and total float distributions :
Supplement aggregate SPI with CPM milestone and path analysis; a critical-path-only index may be useful if its scope and weighting are defined.
Never assume that S P I ≥ 1.00 SPI \ge 1.00 SP I ≥ 1.00 implies the project will finish on or ahead of the contract completion date.
Worked Calculation: The SPI Convergence & Distortion Demonstration
A $1,200,000 data center expansion project has a Planned Duration of 10 months ( P D = 10 PD = 10 P D = 10 ).
Monthly planned value is linear at $120,000 per month ( B A C BAC B A C = $1,200,000).
By Month 8, execution difficulties occur. At Month 10 ( A T = 10 AT = 10 A T = 10 ), the project has only earned $840,000 ( E V EV E V = $840,000).
Work continues for 4 additional months until Month 14, when all scope is finished.
Table of Progression Across Months 10 through 14:
Actual Month ( A T AT A T ) Cumulative P V PV P V Cumulative E V EV E V Cumulative A C AC A C S V SV S V ( E V − P V EV - PV E V − P V ) Traditional S P I SPI SP I True Project Status
- Month 8 $960,000 $720,000 $800,000 -$240,000 0.75 Delayed 2.0 months
- Month 10 $1,200,000 $840,000 $1,050,000 -$360,000 0.70 Baseline target missed; 30% scope remains
Month 11 $1,200,000 $930,000 $1,180,000 -$270,000 0.78 SPI falsely improves by 0.08!
Month 12 $1,200,000 $1,020,000 $1,320,000 -$180,000 0.85 SPI falsely improves by 0.15!
Month 13 $1,200,000 $1,110,000 $1,450,000 -$90,000 0.93 SPI falsely improves to 0.93!
Month 14 $1,200,000 $1,200,000 $1,600,000 $0 1.00 Project finishes 4 months late, yet SPI = 1.00!
Observations for Exam Review:
Look at Months 11 through 14: Although the project is in deep contractual breach (operating past the contract completion date), S V SV S V becomes less negative each month (from -$360k to -$90k to $0) and S P I SPI SP I marches relentlessly upward toward 1.00 1.00 1.00 .
A project controls manager who relies solely on traditional EVM would report 'improving schedule performance' during the very period the project was suffering an uncontrolled schedule overrun.