10.3 Schedule Baseline Maintenance & Change Control

10.3 Schedule Baseline Maintenance & Change Control

Quick Summary: Maintaining schedule baseline integrity is a primary duty of the project controls technician. Project performance is measured against the Performance Measurement Baseline (PMB)—the frozen, time-phased master plan established at contract award. During periodic schedule updates, the Data Date (Time-Now) serves as the strict boundary dividing historical actuals from forecasted remaining work. Schedulers must resolve out-of-sequence progress using Retained Logic (which respects predecessor dependencies) rather than Progress Override (which dangerously ignores remaining logic). A fundamental governance rule under AACE standards is that formal re-baselining is permitted ONLY for approved customer scope changes or force majeure—never to erase contractor delays or clear negative float. Furthermore, technicians must remember that Earned Value Schedule Variance ($SV = EV - PV$) measures monetary volume, not calendar time, necessitating rigorous Critical Path Method (CPM) float tracking alongside Time Impact Analysis (TIA).

---

1. The Performance Measurement Baseline (PMB) & Baseline Freeze

In Total Cost Management, project control cannot occur in a vacuum; it requires a stable benchmark. The Performance Measurement Baseline (PMB) represents the approved, integrated time-phased baseline plan against which project execution is measured, assessed, and controlled.

+-----------------------------------------------------------------------------------+
|              THE THREE PILLARS OF THE PERFORMANCE MEASUREMENT BASELINE             |
|                                                                                   |
|        SCOPE BASELINE          SCHEDULE BASELINE             COST BASELINE        |
|     +-------------------+     +-------------------+     +-------------------+     |
|     | - WBS Hierarchy   |     | - CPM Network     |     | - Time-Phased CBS |     |
|     | - WBS Dictionary  | <-> | - Logic & Float   | <-> | - Control Accounts|     |
|     | - Scope Statement |     | - Calendar & Dates|     | - Budget (BAC)    |     |
|     +-------------------+     +-------------------+     +-------------------+     |
|               \                         |                         /               |
|                +------------------------+------------------------+                |
|                                         |                                         |
|                                         v                                         |
|                       +-----------------------------------+                       |
|                       | PERFORMANCE MEASUREMENT BASELINE  |                       |
|                       |               (PMB)               |                       |
|                       +-----------------------------------+                       |
+-----------------------------------------------------------------------------------+

The Baseline Freeze

Once the project scope is defined, estimates are finalized, and the CPM schedule is optimized, the baseline undergoes a formal Baseline Freeze:

• Contractual Commitment: Approved formally by the project sponsor, client, and contractor leadership.
• Locked Parameters: Target early start dates, early finish dates, late dates, baseline durations, logic ties, and allocated budgets are locked in the scheduling software database as the Target 1 Baseline (B1).
• Permanent Yardstick: Even as field conditions evolve, the frozen baseline remains unchanged throughout project execution unless a formal contractual change order is authorized.

---

2. The Schedule Status Updating Cycle & The Data Date

Schedule control operates through a disciplined periodic reporting cadence (weekly, bi-weekly, or monthly). The core mechanism of every update is the Data Date.

The Data Date (DD) / "Time-Now" / "Status Date"

Per AACE Recommended Practice 10S-90, the Data Date is defined as:

"The calendar date up to which actual historical progress has been recorded and from which remaining schedule durations and forecast dates are calculated."

                         THE DATA DATE (TIME-NOW) DIVIDER
                                         |
     HISTORICAL ACTUALS (PAST)           |        FORECASTED REMAINING WORK (FUTURE)
                                         |
  Activity A: [=== ACTUAL DURATION ===]  |
                                         |
  Activity B: [=== Actual ===]           |  [== REMAINING DURATION ==>
                                         |
  Activity C:                            |          [== PLANNED DURATION ==>
                                         |
-----------------------------------------+------------------------------------------->
                                     DATA DATE

CARDINAL SCHEDULING RULES:
1. NO Actual Start or Actual Finish dates can exist to the RIGHT of the Data Date.
2. NO Remaining Duration can exist to the LEFT of the Data Date.
3. All uncompleted work is scheduled to execute from the Data Date forward.

Schedule Status Update Protocol (Step-by-Step)

During each reporting cycle, the cost technician executes four sequential actions:

1. Advance the Data Date: Move the software status date forward to the close of the current accounting period (e.g., advancing from May 31 to June 30).
2. Record Historical Actuals: Enter verified Actual Start (AS) dates and Actual Finish (AF) dates for activities that commenced or completed during the period.
3. Enter Physical Progress & Remaining Duration: Record the physical percent complete and enter the Remaining Duration (RD) for all ongoing (in-progress) activities. Crucial: Do not allow the software to auto-calculate remaining duration based on elapsed time; obtain an updated physical estimate of remaining work from field superintendents.
4. Run CPM Scheduling Engine: Recalculate early dates, late dates, total float, and the critical path from the Data Date into the future.

---

3. Out-of-Sequence Progress: Retained Logic vs. Progress Override

In dynamic construction environments, field crews frequently adapt to site constraints by executing work out of order. Out-of-Sequence (OOS) Progress occurs when an activity begins before its predecessor activity has finished, violating the planned Finish-to-Start (FS) logic dependency.

PLANNED BASELINE LOGIC:
[Activity 10: Erect Formwork] ------------(FS)------------> [Activity 20: Pour Concrete]

FIELD REALITY (Out-of-Sequence Progress):
Due to a late lumber delivery, the crew completed only 50% of the formwork, but began
pouring concrete in the completed section. Activity 20 has an Actual Start before
Activity 10 has an Actual Finish!

When calculating the updated schedule, scheduling software (e.g., Primavera P6) requires the scheduler to choose between two mathematical calculation modes:

+-----------------------------------------------------------------------------------+
|                    RETAINED LOGIC VS. PROGRESS OVERRIDE                           |
+-------------------+--------------------------------+------------------------------+
| ATTRIBUTE         | RETAINED LOGIC (AACE STANDARD) | PROGRESS OVERRIDE            |
+-------------------+--------------------------------+------------------------------+
| Logic Treatment   | **Respects network logic.**    | **Ignores network logic.**   |
|                   | Remaining duration cannot start| Remaining duration proceeds  |
|                   | until predecessor finishes.    | immediately from Data Date.  |
+-------------------+--------------------------------+------------------------------+
| Operational       | Realistic; recognizes that     | Unrealistic; assumes broken  |
| Realism           | unfinished predecessor work    | predecessor logic has zero   |
|                   | restrains final completion.    | further constraint on task.  |
+-------------------+--------------------------------+------------------------------+
| Schedule Impact   | Conservative; reveals potential| Highly optimistic; creates   |
|                   | delays and critical path slips.| artificial negative float    |
|                   |                                | or false early completions.  |
+-------------------+--------------------------------+------------------------------+
| Exam Status       | **Industry best practice.**    | Generally unacceptable       |
|                   | Mandated on formal claims.     | without logic revision.      |
+-------------------+--------------------------------+------------------------------+

The Retained Logic Calculation

Under Retained Logic, the software accepts the Actual Start date for Activity 20, but halts the remaining duration of Activity 20 until Activity 10 reaches 100% completion. This reflects physical construction reality: you cannot finish pouring concrete until the remaining formwork is fully erected and inspected.

The Progress Override Danger

Under Progress Override, the software assumes that because Activity 20 has started, the logic link is permanently satisfied or invalidated. It schedules the remaining duration of Activity 20 to proceed immediately from the Data Date, running completely in parallel with the unfinished predecessor. This artificially shortens the critical path and masks significant delays.

[!IMPORTANT] AACE Best Practice: When out-of-sequence progress occurs, schedulers must investigate the physical cause. If the sequence has genuinely and permanently changed, the network logic must be formally revised (e.g., replacing the FS link with an SS link and lag). If the out-of-sequence work was an interim workaround, Retained Logic must be enforced.

---

4. Schedule Maintenance Taxonomy: Update vs. Revision vs. Re-baselining

A critical area tested on the CCT exam is distinguishing between three levels of schedule maintenance:

+-----------------------------------------------------------------------------------+
|                         SCHEDULE MAINTENANCE TAXONOMY                             |
+-------------------+--------------------+-------------------+----------------------+
| ACTION LEVEL      | WHAT IS MODIFIED?  | BASELINE STATUS   | APPROVAL AUTHORITY   |
+-------------------+--------------------+-------------------+----------------------+
| 1. Routine Status | Data Date, actual  | **UNTOUCHED**     | Project Controls     |
|    Update         | dates, % complete, | Baseline remains  | Lead / Scheduler     |
|                   | remaining duration | frozen yardstick  |                      |
+-------------------+--------------------+-------------------+----------------------+
| 2. Schedule       | Forecast logic,    | **UNTOUCHED**     | Project Manager /    |
|    Revision /     | activity durations,| Current schedule  | Construction Manager |
|    Recovery Plan  | added crews, shifts| adjusted to recover|                      |
+-------------------+--------------------+-------------------+----------------------+
| 3. Formal         | Target dates,      | **MODIFIED**      | Client / Executive   |
|    Re-baselining  | contract baseline, | Target baseline is| Change Board / Owner |
|                   | scope, total budget| formally replaced | Contract Officer     |
+-------------------+--------------------+-------------------+----------------------+

Strict AACE Governance Rules for Re-baselining

Formal Re-baselining resets the Performance Measurement Baseline (PMB), wiping out prior variances and establishing a new baseline of record ($B2$). Because re-baselining alters contractual accountability, AACE International enforces strict governance:

1. Authorized Reasons for Re-baselining:
   • Approved Scope Changes: Client authorizes a major contract change order adding or removing significant physical scope.
   • Client-Directed Suspensions: Owner issues a formal suspension of work or changes project phasing.
   • Catastrophic Force Majeure: Unforeseen events (e.g., regional disasters, environmental halts) that fundamentally invalidate the original execution plan.
2. PROHIBITED Reasons for Re-baselining:
   • Masking Poor Contractor Performance: Re-baselining to hide contractor-caused delays, poor productivity, or staffing shortages is strictly prohibited.
   • Erasing Negative Float: Moving target baseline dates simply to bring negative float back to zero ($TF = 0$) destroys schedule controls integrity.
   • Resetting Deteriorating EVM Metrics: Re-baselining to reset a failing $CPI = 0.75$ or $SPI = 0.80$ back to $1.0$ conceals financial reality from executive stakeholders.

---

5. Critical Path Evolution & Float Migration

The Critical Path is not static; it is a dynamic chain that evolves with every periodic update:

• Float Consumption: As non-critical activities slip, their Total Float ($TF$) is consumed ($TF = LS - ES$).
• Critical Path Migration: When an activity's delay exceeds its available float, it enters Negative Float ($TF < 0$), and the critical path shifts away from the original baseline path onto this newly delayed path.
• Near-Critical Path Monitoring: Schedulers must actively monitor secondary and tertiary paths with low float (e.g., $0 < TF \le 10$ days). A minor field disruption on a near-critical path can instantly propel it to primary critical status, catching project management off guard.

---

6. Schedule Variance: CPM Network Variance vs. EVM Schedule Variance

One of the most heavily tested conceptual paradoxes on the CCT exam is the difference between CPM Schedule Variance and EVM Schedule Variance.

+-----------------------------------------------------------------------------------+
|                         CPM VARIANCE VS. EVM VARIANCE                             |
+-------------------+--------------------------------+------------------------------+
| ATTRIBUTE         | CPM SCHEDULE VARIANCE          | EVM SCHEDULE VARIANCE (SV)   |
+-------------------+--------------------------------+------------------------------+
| Measurement Unit  | **Calendar Time**              | **Monetary Currency**        |
|                   | (Working Days, Weeks, Months)  | (Dollars, Euros, or Hours)   |
+-------------------+--------------------------------+------------------------------+
| Core Formula      | Variance = Target Milestone -  | SV = EV - PV                 |
|                   | Forecast Completion Date       | SPI = EV / PV                |
+-------------------+--------------------------------+------------------------------+
| Critical Path     | **Directly measured.**         | **Completely blind.**        |
| Sensitivity       | Focuses entirely on float      | Treats all earned dollars    |
|                   | along the critical path.       | equally, regardless of float.|
+-------------------+--------------------------------+------------------------------+
| Behavior at       | Accurately shows total days    | **Fatal Flaw: Returns to $0**|
| Project Finish    | late (e.g., 90 days late).     | EV = PV = BAC; SV = $0;      |
|                   |                                | SPI = 1.0 (Shows "on time"!) |
+-------------------+--------------------------------+------------------------------+

The Fundamental Flaw of EVM Schedule Variance

Consider a project that is 12 months behind schedule:

• During execution, the contractor spent funds accelerating high-dollar non-critical activities (e.g., early equipment purchases) while the critical path foundation work was completely stalled.
• Because massive Earned Value was generated on non-critical tasks, $EV > PV$, producing a favorable Schedule Performance Index ($SPI = 1.15$). The project manager falsely reported that the project was "ahead of schedule" while the critical path was actually 3 months late!
• At Project Completion: By definition, all scope is eventually completed, so $EV$ reaches $BAC$, and $PV$ reaches $BAC$. Therefore: $SV = EV - PV = BAC - BAC = \mathbf{\$0}$ $SPI = \frac{EV}{PV} = \frac{BAC}{BAC} = \mathbf{1.0}$

Even if a project finishes two years late, EVM metrics conclude with $SV = $0$ and $SPI = 1.0$! To eliminate this distortion, cost engineers must:

1. Always evaluate CPM Total Float alongside EVM metrics.
2. Utilize Earned Schedule ($ES$), an advanced technique that maps Earned Value back to the planned baseline time axis to express schedule variance in time units ($SV_t = ES - AT$).

---

7. Management of Change (MOC) & Schedule Integration

A schedule baseline cannot remain relevant without rigorous integration with the project Management of Change (MOC) system. Every design deviation, site condition change, or client request must flow through a structured change protocol:

+-----------------------------------------------------------------------------------+
|                         SCHEDULE CHANGE CONTROL WORKFLOW                          |
|                                                                                   |
|  1. IDENTIFY        Project team identifies field deviation, owner scope change,  |
|     & LOG           or differing site condition. Logged in Change Register.       |
|                                   |                                               |
|                                   v                                               |
|  2. TIME IMPACT     Scheduler constructs a FRAGNET (mini-network) modeling the     |
|     ANALYSIS (TIA)  specific delay tasks and inserts it into current schedule.    |
|                                   |                                               |
|                                   v                                               |
|  3. COMMERICAL      Quantify critical path delay (excusable vs non-excusable).    |
|     PRICING         Calculate direct acceleration costs & time-related overhead.  |
|                                   |                                               |
|                                   v                                               |
|  4. GOVERNANCE      Change Review Board (CRB) and Client approve or reject change.|
|     APPROVAL        If approved: Issue formal Contract Change Order (CO).         |
|                                   |                                               |
|                                   v                                               |
|  5. BASELINE        Incorporate change order fragnet into official CPM schedule.  |
|     ADJUSTMENT      Adjust target milestone dates if authorized by contract.      |
+-----------------------------------------------------------------------------------+

---

8. Time Impact Analysis (TIA) Basics (AACE RP 29R-03)

Under AACE Recommended Practice 29R-03 (Forensic Schedule Analysis), Time Impact Analysis (TIA) is the preferred prospective and contemporaneous method for quantifying schedule delay claims and time extension requests.

The Four Steps of Time Impact Analysis

1. Select the Un-Impacted Schedule Update: Retrieve the most recently accepted CPM schedule update immediately prior to the occurrence of the delay event.
2. Develop the Fragnet (Fragmentary Network): Create a discrete sub-network of new activities representing the delay event. Estimate durations based on physical scope and assign logical predecessor/successor links.
3. Insert Fragnet & Recalculate Schedule: Insert the fragnet into the un-impacted schedule and run the CPM forward and backward pass.
4. Measure Net Critical Path Impact: Compare the project completion date before and after fragnet insertion: $\Delta \text{Project Duration} = \text{Impacted Completion Date} - \text{Un-Impacted Completion Date}$

If the project completion date slips, the contractor is entitled to an excusable time extension. If the delay lies entirely on a path with positive float, zero time extension is granted.

---

9. Monthly Schedule Narrative Reporting Requirements

Per AACE Recommended Practice 38R-06, a raw CPM Gantt chart is insufficient for executive communication. Every monthly schedule submittal must be accompanied by a comprehensive Schedule Narrative Report containing:

1. Executive Summary: High-level narrative of physical accomplishment and contract milestone status.
2. Critical Path Analysis: Detailed review of the primary critical path and secondary near-critical paths, explaining why changes occurred.
3. Milestone Variance Table: Comparison of baseline target dates, previous forecast dates, current forecast dates, and net variances in calendar days.
4. Out-of-Sequence Log: Complete listing of all out-of-sequence activities and their justification under Retained Logic.
5. Logic & Calendar Modifications: Explicit documentation of all added, deleted, or revised activity dependencies, leads/lags, and working calendars.
6. Corrective Action & Recovery Plan: Clear mitigation strategies (crashing, re-sequencing, shift work) to recover accumulated negative float.

---

10. Step-by-Step Worked Problem: Schedule Variance & Baseline Governance

Scenario: An offshore fabrication project ($BAC = $12,000,000$, Baseline Duration = 18 Months) is undergoing its Month 6 schedule update. The project controls technician must reconcile conflicting performance data and evaluate a contractor re-baselining request.

Performance Data at Data Date (Month 6)

• Planned Value ($PV$): $$4,200,000$
• Earned Value ($EV$): $$4,100,000$
• Actual Cost ($AC$): $$4,600,000$
• Baseline Contract Completion: Day 540
• Current CPM Forecasted Completion: Day 562
• Critical Path Total Float: -22 Days
• Out-of-Sequence Event: Activity ACT-320 (Deck Piping Prefabrication, Remaining Duration = 30 days) was started out-of-sequence before its predecessor Activity ACT-300 (Approved P&IDs) finished. Activity ACT-300 is currently delayed and has 15 days of remaining duration.

---

Step 1: Reconcile EVM Metrics vs. CPM Network Metrics

1. EVM Schedule Variance ($SV$): $SV = EV - PV = \$4,100,000 - \$4,200,000 = -\$100,000$ $SPI = \frac{EV}{PV} = \frac{\$4,100,000}{\$4,200,000} = 0.976$
   • Looking solely at EVM, $SPI = 0.976$ suggests the project is experiencing only a 2.4% minor volume lag.
2. CPM Network Status:
   • Critical Path Total Float = -22 Days.
   • The project is trending 22 calendar days late against the contractual delivery date!
3. Technical Explanation: The contractor earned substantial value on non-critical steel staging, masking a severe critical path delay in main deck piping tie-ins. CPM float analysis reveals the true critical delay that EVM monetary metrics failed to expose.

---

Step 2: Resolve Out-of-Sequence Progress on Activity ACT-320

• If calculated under Progress Override: The software ignores the remaining 15 days of predecessor Activity ACT-300 and schedules the 30 remaining days of ACT-320 to execute immediately from the Data Date. Forecasted finish = Day 30.
• If calculated under Retained Logic (AACE Standard): The software enforces the Finish-to-Start dependency. The remaining 30 days of ACT-320 cannot begin until Activity ACT-300 finishes (15 days from Data Date). Forecasted finish = $15 + 30 = \mathbf{\text{Day 45}}$.
• Governance Decision: Enforce Retained Logic. Prefabricating piping spools without approved P&IDs creates extreme rework risk. Retained Logic correctly reflects the physical constraint, preventing false optimistic forecasts.

---

Step 3: Evaluate Contractor's Re-baselining Request

The contractor formally requests to re-baseline the project by extending the contract baseline finish date from Day 540 to Day 562, which would reset Total Float to 0 and reset $SPI$ to 1.0. The contractor cites unexpected vendor manufacturing delays on piping flanges.

• Evaluation under AACE Standards:
  • Vendor manufacturing delays are an ordinary contractor supply chain risk, NOT an owner-directed scope change or force majeure.
  • Re-baselining to eliminate negative float or hide poor execution is STRICTLY PROHIBITED.
• Final Ruling: REJECT THE RE-BASELINING REQUEST.
  • The Performance Measurement Baseline remains locked at Day 540.
  • The contractor must submit a Schedule Revision / Recovery Plan demonstrating how they will crash critical path activities or add labor shifts to recover the 22 days of negative float at their own expense.

---

11. CCT Exam Watch: High-Yield Schedule Control Traps

1. Re-baselining as a Delay Fix: Any multiple-choice option suggesting that a project should be re-baselined to "eliminate negative float", "align with current reality after a delay", or "restore SPI to 1.0" is incorrect. Re-baselining requires formal contractual change orders.
2. The $SPI = 1.0$ at Completion Fallacy: Always remember that at project completion, $EV = PV = BAC$, meaning $SV = $0$ and $SPI = 1.0$. If a question describes a project that finished 6 months late and asks for its final $SV$, the answer is $0, not a negative dollar amount.
3. Progress Override Distortions: Progress Override allows out-of-sequence remaining duration to start immediately, creating an artificially optimistic schedule. Retained Logic holds remaining duration until predecessors complete.
4. Data Date Temporal Violations: Actual dates cannot occur after the Data Date. Remaining durations cannot occur before the Data Date. Any schedule showing actual progress in the future violates basic project controls principles.