9.4 Project Scheduling, Critical Path Method (CPM/PERT) & Control

9.4 Project Scheduling, Critical Path Method (CPM/PERT) & Control

Executing complex supply management initiatives on schedule and within budget requires rigorous mathematical modeling of task dependencies, probabilistic duration estimation, and quantitative performance tracking. Project managers rely on the Critical Path Method (CPM), Program Evaluation and Review Technique (PERT), and Earned Value Management (EVM) to optimize project schedules, compress timelines, and forecast financial outcomes with precision.

1. Network Diagramming & Precedence Diagramming Method (PDM)

The Precedence Diagramming Method (PDM), also known as Activity-on-Node (AON), is the standard graphical technique used to construct project schedule network diagrams. Activities are represented by rectangular nodes, and logical relationships (dependencies) are depicted by connecting arrows.

+-----------------------------------------------------------------------------+
|                   THE FOUR PDM DEPENDENCY RELATIONSHIPS                     |
|                                                                             |
|   1. FINISH-TO-START (FS) - [Most Common]                                   |
|      Activity B cannot start until Activity A finishes.                     |
|      [Draft RFP (A)] ──────────────────────────────► [Issue RFP to Bidders (B
|                                                                             |
|   2. START-TO-START (SS)                                                    |
|      Activity B cannot start until Activity A starts.                       |
|      [Begin Data Cleansing (A)] ───────────────────► [Begin Spend Analytics (B
|                                                                             |
|   3. FINISH-TO-FINISH (FF)                                                  |
|      Activity B cannot finish until Activity A finishes.                    |
|      [Complete Supplier Tooling (A)] ──────────────► [Complete PPAP Doc (B)]
|                                                                             |
|   4. START-TO-FINISH (SF) - [Extremely Rare]                                |
|      Activity B cannot finish until Activity A starts.                      |
|      [New Warehouse System Live (A)] ──────────────► [Decommission Old Sys (B
+-----------------------------------------------------------------------------+

Dependency Origins

• Mandatory Dependencies (Hard Logic): Inherent physical or contractual limitations (e.g., a physical prototype must be machined before destructive stress testing can occur).
• Discretionary Dependencies (Soft / Preferential Logic): Preferred best-practice sequencing defined by the project team (e.g., choosing to complete supplier financial audits before conducting technical site tours).
• External Dependencies: Relationships between project activities and external third-party events outside the project team's direct control (e.g., waiting for government customs import clearance or third-party ISO registrar audit availability).
• Internal Dependencies: Precedence relationships strictly within the project team's direct control.

Leads and Lags

• Lead (Acceleration): A modification of a logical relationship that allows an acceleration of the successor activity (a negative delay). Example: In an FS relationship with a 3-day lead (FS - 3 days), drafting the user manual begins 3 days before software coding is fully completed.
• Lag (Mandatory Waiting Delay): A modification that inserts a mandatory waiting period between activities. Example: In an FS relationship with a 5-day lag (FS + 5 days), painting a new warehouse floor requires a 5-day curing lag before heavy racking installation can begin.

2. The Critical Path Method (CPM) & Float Calculations

The Critical Path Method (CPM) is a deterministic scheduling algorithm that calculates the earliest and latest dates each activity can start and finish, determines project duration, and identifies which activities have scheduling flexibility (float).

+-----------------------------------------------------------------------------+
|                           STANDARD CPM ACTIVITY NODE                        |
|                                                                             |
|                   +-------------------+-------------------+                 |
|                   | Early Start (ES)  | Duration (D)      |                 |
|                   +-------------------+-------------------+                 |
|                   | Activity Name / ID & Description      |                 |
|                   +-------------------+-------------------+                 |
|                   | Late Start (LS)   | Total Float (TF)  |                 |
|                   +-------------------+-------------------+                 |
|                   | Early Finish (EF) | Late Finish (LF)  |                 |
|                   +-------------------+-------------------+                 |
+-----------------------------------------------------------------------------+

Core CPM Definitions

• Early Start (ES): The earliest possible point in time an activity can begin based on network logic.
• Early Finish (EF): The earliest possible point in time an activity can complete: EF = ES + Duration.
• Late Finish (LF): The latest point in time an activity can finish without delaying overall project completion.
• Late Start (LS): The latest point in time an activity can begin without delaying project completion: LS = LF - Duration.
• Total Float / Total Slack (TF): The total amount of time an activity can be delayed from its Early Start without delaying the project finish date: Total Float = LS - ES = LF - EF
• Free Float (FF): The amount of time an activity can be delayed without delaying the Early Start (ES) of any immediate successor activity: Free Float = min(ES_successors) - EF
• The Critical Path: The sequence of dependent activities that has Zero Total Float (TF = 0). The critical path is the longest continuous duration path through the network and dictates the shortest possible time in which the project can be completed.

[!IMPORTANT] Critical Path Delay Penalty: Any delay to an activity on the critical path causes an immediate, day-for-day delay to final project completion unless schedule compression interventions are executed.

Forward Pass & Backward Pass Algorithms

1. Forward Pass (Calculates Early Dates: ES and EF):
   • Begin at project start: ES_initial = 0.
   • For each node: EF = ES + Duration.
   • For nodes with multiple predecessors: ES = max(EF_all_immediate_predecessors).
2. Backward Pass (Calculates Late Dates: LF and LS):
   • Begin at project finish: LF_end = EF_end.
   • For each node: LS = LF - Duration.
   • For nodes with multiple successors: LF = min(LS_all_immediate_successors).

Fully Worked Numerical CPM Problem

Scenario: A global supply chain team is executing a strategic category sourcing initiative consisting of 6 activities:

• Activity A (SOW & Baseline): Duration = 4 days; Predecessors: None
• Activity B (Market Research): Duration = 6 days; Predecessor: A
• Activity C (Technical Specs): Duration = 8 days; Predecessor: A
• Activity D (RFP Bidding): Duration = 10 days; Predecessor: B
• Activity E (Supplier Selection): Duration = 6 days; Predecessors: C, D
• Activity F (Contract Execution): Duration = 4 days; Predecessor: E

+-----------------------------------------------------------------------------+
|                        CPM NETWORK DIAGRAM FLOW                             |
|                                                                             |
|                        ┌────────────────┐     ┌────────────────┐            |
|                        │  Activity B    │────►│  Activity D    │            |
|                   ┌───►│ (Market Res:6) │     │  (RFP Bid: 10) │───┐        |
|  ┌─────────────┐  │    └────────────────┘     └────────────────┘   │   ┌─────────────┐   ┌─────────────┐
|  │ Activity A  │──┤                                                ├──►│ Activity E  │──►│ Activity F  │
|  │ (SOW Dev: 4)│  │    ┌────────────────┐                          │   │(Selection:6)│   │ (Contract:4)│
|  └─────────────┘  └───►│  Activity C    │──────────────────────────┘   └─────────────┘   └─────────────┘
|                        │ (Tech Specs:8) │                                   |
|                        └────────────────┘                                   |
|                                                                             |
|   Path 1: A ──► B ──► D ──► E ──► F = 4 + 6 + 10 + 6 + 4 = 30 Days (CRITICAL)
|   Path 2: A ──► C ──► E ──► F       = 4 + 8 + 6 + 4      = 22 Days          |
+-----------------------------------------------------------------------------+

Step 1: Forward Pass Calculations

• Activity A: ES = 0; EF = 0 + 4 = 4
• Activity B: ES = 4; EF = 4 + 6 = 10
• Activity C: ES = 4; EF = 4 + 8 = 12
• Activity D: ES = 10; EF = 10 + 10 = 20
• Activity E: ES = max(EF_C, EF_D) = max(12, 20) = 20; EF = 20 + 6 = 26
• Activity F: ES = 26; EF = 26 + 4 = 30
• Total Project Duration = 30 Days.

Step 2: Backward Pass Calculations

• Activity F: LF = 30; LS = 30 - 4 = 26
• Activity E: LF = 26; LS = 26 - 6 = 20
• Activity D: LF = 20; LS = 20 - 10 = 10
• Activity C: LF = 20 (since successor E has LS = 20); LS = 20 - 8 = 12
• Activity B: LF = 10; LS = 10 - 6 = 4
• Activity A: LF = min(LS_B, LS_C) = min(4, 12) = 4; LS = 4 - 4 = 0

Step 3: Total Float & Critical Path Summary Table

• Critical Path: A -> B -> D -> E -> F (30 Days).
• Float Analysis on Activity C: Total Float = 12 - 4 = 8 days. Free Float = ES_E - EF_C = 20 - 12 = 8 days. Activity C can be delayed by up to 8 days without impacting project finish date or delaying the start of Activity E.

3. Three-Point PERT Estimation (Beta Distribution)

When activity durations are uncertain, the Program Evaluation and Review Technique (PERT) uses a three-point weighting model based on a Beta Distribution:

+-----------------------------------------------------------------------------+
|                        THREE-POINT PERT FORMULAS                            |
|                                                                             |
|   1. Optimistic Duration (O): Best-case scenario duration.                  |
|   2. Most Likely Duration (M): Realistic, normal conditions duration.       |
|   3. Pessimistic Duration (P): Worst-case scenario duration.                |
|                                                                             |
|   EXPECTED DURATION (Te):                   TASK VARIANCE (σ²):             |
|                                                                             |
|             O + 4M + P                                  ⎛ P - O ⎞²          |
|       Te = ────────────                           σ² =  │───────│           |
|                 6                                       ⎝   6   ⎠           |
+-----------------------------------------------------------------------------+

Total Project PERT Calculations

• Project Expected Duration (Te): Sum of expected durations of all critical path activities: Sum(Te_critical).
• Project Variance (sigma^2_project): Sum of variances of all critical path activities: Sum(sigma^2_critical).
• Project Standard Deviation (sigma_project): sqrt(Sum(sigma^2_critical)).
• Probability of Completion by Target Date (Ts): Calculated via standard normal Z-score: Z = (Ts - Te) / sigma_project

4. Schedule Compression: Crashing vs. Fast-Tracking

When a project falls behind schedule or executive management mandates an expedited completion date, project managers execute Schedule Compression techniques:

+-----------------------------------------------------------------------------+
|                     SCHEDULE COMPRESSION COMPARISON                         |
|                                                                             |
|   TECHNIQUE        MECHANISM                    COST IMPACT    RISK IMPACT  |
|   ---------------  ---------------------------  -------------  ------------ |
|   CRASHING         Adding resources / overtime  INCREASES      Low to Mod   |
|                    to critical path tasks       direct budget  (burnout)    |
|                                                                             |
|   FAST-TRACKING    Performing sequential        Zero direct    INCREASES    |
|                    critical tasks in parallel   budget add     rework & error
+-----------------------------------------------------------------------------+

Crashing Mechanics & Crash Cost Slope

Crashing compresses schedule duration by adding financial or labor resources (overtime, subcontracting, premium freight) to critical path tasks. To crash efficiently:

1. Crash ONLY activities on the Critical Path. (Crashing non-critical tasks increases cost without shortening project duration!)
2. Select the critical activity with the lowest Crash Cost per Unit Time (Crash Cost Slope): Crash Cost Slope = (Crash Cost - Normal Cost) / (Normal Duration - Crash Duration)
3. Crash that activity up to its maximum crash limit or until a new parallel path becomes critical.

Fast-Tracking Mechanics

Fast-Tracking executes critical activities concurrently that were originally planned in sequence (e.g., starting tooling fabrication before final CAD drawings receive sign-off). While Fast-Tracking adds no immediate budget cost, it introduces substantial risk of rework, engineering scrap, and communication breakdowns.

5. Earned Value Management (EVM) Quantitative Performance Control

Earned Value Management (EVM) is an industry-standard quantitative methodology that integrates scope, schedule, and cost performance baselines to assess project health and forecast final budget and completion timelines.

+-----------------------------------------------------------------------------+
|                        EARNED VALUE MANAGEMENT (EVM)                        |
|                                                                             |
|   BASE METRICS:                                                             |
|   • Planned Value (PV): Budget authorized for scheduled work.               |
|   • Earned Value (EV):  Budget authorized for work ACTUALLY COMPLETED.      |
|   • Actual Cost (AC):   Actual funds spent on work completed to date.       |
|   • Budget at Completion (BAC): Total baseline project budget.              |
|                                                                             |
|   VARIANCES:                                PERFORMANCE INDICES:            |
|   • Cost Variance:     CV = EV - AC         • Cost Index:     CPI = EV / AC |
|   • Schedule Variance: SV = EV - PV         • Schedule Index: SPI = EV / PV |
|                                                                             |
|   FORECASTING:                                                              |
|   • Estimate at Completion: EAC = BAC / CPI                                 |
|   • Variance at Completion: VAC = BAC - EAC                                 |
|   • To-Complete Index:      TCPI = (BAC - EV) / (BAC - AC)                  |
+-----------------------------------------------------------------------------+

EVM Metrics & Interpretations

Fully Worked Numerical EVM Problem

Scenario: A multinational enterprise is deploying an integrated global SCM and Supplier Portal system across 20 facilities.

• Total Approved Baseline Budget (BAC) = $2,000,000
• Planned Schedule Duration = 10 Months (Planned linear spend = $200,000 per month)

At the Month 5 status review, an operational and financial audit reveals:

• Planned Progress: 50% of the project should be completed.
• Actual Physical Progress: 40% of the work is objectively completed.
• Accounting Incurred Costs: Total money spent to date (AC) = $1,000,000.

Step 1: Calculate Base Metrics (PV, EV, AC)

• Planned Value (PV): 50% * BAC = 0.50 * $2,000,000 = $1,000,000
• Earned Value (EV): 40% * BAC = 0.40 * $2,000,000 = $800,000
• Actual Cost (AC): $1,000,000

Step 2: Calculate Variances (CV, SV)

• Cost Variance (CV): CV = EV - AC = $800,000 - $1,000,000 = -$200,000 Interpretation: The project is $200,000 over budget for the work performed.
• Schedule Variance (SV): SV = EV - PV = $800,000 - $1,000,000 = -$200,000 Interpretation: The project is behind schedule by $200,000 worth of planned work.

Step 3: Calculate Performance Indices (CPI, SPI)

• Cost Performance Index (CPI): CPI = EV / AC = $800,000 / $1,000,000 = 0.80 Interpretation: For every $1.00 spent, the project is realizing only $0.80 of earned value (20% cost inefficiency).
• Schedule Performance Index (SPI): SPI = EV / PV = $800,000 / $1,000,000 = 0.80 Interpretation: The project is progressing at only 80% of its planned schedule velocity.

Step 4: Calculate Forecasting Metrics (EAC, VAC, TCPI)

• Estimate at Completion (EAC): EAC = BAC / CPI = $2,000,000 / 0.80 = $2,500,000 Interpretation: If current cost efficiency continues, the project will cost $2,500,000 at completion instead of the budgeted $2,000,000.
• Variance at Completion (VAC): VAC = BAC - EAC = $2,000,000 - $2,500,000 = -$500,000 Interpretation: Projected project budget deficit is $500,000.
• To-Complete Performance Index (TCPI to target BAC): TCPI = (BAC - EV) / (BAC - AC) = ($2,000,000 - $800,000) / ($2,000,000 - $1,000,000) = $1,200,000 / $1,000,000 = 1.20 Interpretation: To finish within the original $2,000,000 budget, the project team must achieve a CPI of 1.20 (120% efficiency) on all remaining work.