PR MEPS Map

MEP Contractor ISO 9001:2015


And ISO 14001:2015

PR MEP SERVICES

← Back to Academy

PR MEP Academy • Training Day 17

Progress Updating & Earned Value Management (EVM)

Mastering actual schedule status cycles, physical percent complete validation parameters, and cost/schedule efficiency metrics.

1. Theoretical Lecture: Progress Cycles & EVM Mathematical Formulations

The Schedule Progress Data Cycle

Updating a live project schedule requires strict, empirical data entry. Planners must freeze a fixed evaluation point called the **Data Date**, record explicit *Actual Start (AS)* and *Actual Finish (AF)* dates, and audit the *Physical Percent Complete* of in-progress tasks based on physical site units installed rather than visual estimates.

The Three Pillars of Earned Value Management

Teach the trainee the foundational math metrics required to verify project performance status objectively:

  • Planned Value (PV): The total budgeted cost or man-hours of work scheduled to be executed up to the current Data Date line (PV = Budgeted Cost of Work Scheduled).
  • Earned Value (EV): The true budgeted value or man-hours of work *actually completed* up to the Data Date line (EV = Budget at Completion × Physical % Complete).
  • Actual Cost (AC): The total actual costs or labor man-hours physically spent/logged on timesheets to complete the work up to the current Data Date line.

Performance Variances & Indices

Converting metrics into clear efficiency health flags:

  • Schedule Variance (SV): Measures schedule deviation in budgeted terms (SV = EV - PV). A negative value means the project is tracking behind schedule.
  • Cost Variance (CV): Measures financial or hour expenditure deviation (CV = EV - AC). A negative value indicates cost overruns.
  • Schedule Performance Index (SPI): Efficiency of time usage (SPI = EV / PV). An SPI below 1.0 means critical delays.
  • Cost Performance Index (CPI): Efficiency of money/labor hour expenditure (CPI = EV / AC). A CPI below 1.0 means over-budget.

2. Core Concepts: The Data Date Frontier & The "90% Complete" Trap

Enforcing rigorous auditing rules to protect reporting against subjective site claims:

  • The Data Date Boundary: The explicit line in time that separates historical completed progress facts from future planned forecasts. No incomplete work or future task segments are mathematically permitted to sit to the left of the Data Date.
  • The "90% Complete" Stagnation Trap: Site sub-contractors frequently report an activity as "90% complete" for weeks because they struggle to finish final terminal hookups, equipment terminations, or testing loops. Enforce a strict physical unit measurement rule (e.g., precise linear meters of pipe hung or cables pulled) to wipe out subjective bias.

3. Practical Activity: Processing Site Updates & Calculating EVM Data

Field Task Scenario: Evaluate a real-world weekly site progress report for a core Cable Pulling package, calculate full EVM performance metrics, and log diagnostic indicators into the system tracking sheet.

The trainee workbook log calculation entry must structure metrics exactly inside the code box below:

[Trainee Name: XYZ] — [Day 17: Earned Value Management & Progress Performance Report] 1. Quantitative EVM Database Inputs & Calculations: - Total Package Budget at Completion (BAC) = 1,000 Man-Hours - Progress Status at Current Data Date: * Target Planned Progress: 50% of work should be done ──> Planned Value (PV) = 500 Man-Hours * Actual Physical Progress Verified: 40% of cables pulled ──> Earned Value (EV) = 1,000 * 0.40 = 400 Man-Hours * Timesheet Data Logged: 450 hours physically spent ──> Actual Cost (AC) = 450 Man-Hours 2. Performance Diagnostics Dashboard Metrics: ┌───────────────────────────────┬────────────────────────┬────────────────────────┬────────────────┐ │ EVM METRIC RUN │ MATHEMATICAL FORMULA │ CALCULATED VALUE │ STATUS BLINK │ ├───────────────────────────────┼────────────────────────┼────────────────────────┼────────────────┤ │ Schedule Variance (SV) │ EV - PV │ -100 Man-Hours │ BEHIND SCHEDULE│ │ Cost Variance (CV) │ EV - AC │ -50 Man-Hours │ OVER BUDGET │ │ Schedule Performance Index(SPI│ EV / PV │ 0.80 │ CRITICAL DELAY │ │ Cost Performance Index (CPI) │ EV / AC │ 0.89 │ INEFFICIENT │ └───────────────────────────────┴────────────────────────┴────────────────────────┴────────────────┘ 3. Executive Analytical Interpretation Note: - Schedule Efficiency Analysis: The SPI of 0.80 means that for every 10 hours of planned work scheduled, the site team is only generating 8 hours of physical progress. The package is tracking 20% behind schedule. - Cost Efficiency Analysis: The CPI of 0.89 means the team is over-consuming labor hours relative to physical progress. We are spending more hours to install fewer units, indicating poor site productivity or excessive re-work.

4. Assessment & Knowledge Wrap-up

Question 1: You review a subcontractor's weekly progress log dashboard. The critical path activity 'Install Electrical Final DBs' displays a Cost Performance Index (CPI) of 1.25 and a concurrent Schedule Performance Index (SPI) of 0.70. What does this performance combination reveal about the field health of this activity?

Click to view Model Answer

Model Answer: This data combination reveals that the subcontractor activity is **under budget but significantly delayed behind the baseline schedule timeline**. The CPI of 1.25 indicates high cost efficiency (the field crew is spending 25% fewer man-hours than budgeted for the physical work accomplished). However, the SPI of 0.70 means they are only generating 70% of the planned volume speed. This signature typically identifies a severe **site under-staffing issue**. The workers on the floor are highly skilled and efficient, but there are simply not enough of them deployed to meet schedule velocity, threatening critical path completion milestones.

Question 2: What happens mathematically to the uncompleted segments of activities inside a scheduling database engine like Primavera P6 when you advance the project's Data Date forward during a monthly progress tracking update loop?

Click to view Model Answer

Model Answer: When the project Data Date line is advanced forward, the scheduling calculation engine automatically forces all uncompleted portions of work (represented by the activity's Remaining Duration) out to the right of the new Data Date boundary line. If a task was scheduled to complete in the past but remains physically un-executed, the software engine pushes that lingering work into the future, which instantly triggers a cascading recalculation that delays any logically dependent downstream activities, resource headcounts, and critical project milestones.

Professional & Specialized MEP Contractor in Gurgaon, Delhi NCR

Contact us