8.1 Project Planning, Work Breakdown Structures & Critical Path Method (CPM) Scheduling

Project Planning Hierarchy and Strategic Scheduling

Effective construction project management begins long before ground is broken. In the commercial and residential construction sectors, project planning is the systematic process of defining scope, determining resource requirements, allocating trade responsibilities, and establishing temporal constraints. A disciplined planning framework prevents cost overruns, trade stacking, jurisdictional disputes, and project delays.

Project scheduling translates planning into an actionable, time-phased execution model. Within professional contracting operations, scheduling functions at four distinct hierarchical levels:

1. Executive Milestone Schedule (Level 1): High-level summary schedule prepared for owners, developers, lenders, and corporate executives. Highlights major project milestones such as site possession, groundbreaking, foundation completion, structural topping-out, building dry-in, substantial completion, and final occupancy.
2. Master Production Schedule (Level 2): Integrated baseline schedule incorporating all prime contract scopes, major procurement timelines, submittal approval cycles, and key jurisdictional inspection gates.
3. Look-Ahead Schedule (Level 3): Rolling operational schedule (typically spanning 3 to 6 weeks) managed by project managers and superintendents. Used in weekly subcontractor coordination meetings to manage trade handoffs, verify material deliveries, and resolve site access conflicts.
4. Short-Interval Production Schedule / Daily Work Plan (Level 4): 1- to 2-week daily task schedule managed by trade foremen and superintendents, assigning specific craft crews, equipment, and tasks to defined physical work areas.

---

Work Breakdown Structure (WBS) Decomposition

A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish project objectives and create the required deliverables. It organizes and defines the total scope of the project, dividing broad project deliverables into progressively smaller, more manageable components.

Level 1: Total Project Scope (e.g., Commercial Medical Office Building)
   │
   ├── Level 2: Subproject / Phase (e.g., Substructure & Core)
   │      │
   │      ├── Level 3: Work Package (e.g., Cast-in-Place Concrete Foundation)
   │      │      │
   │      │      └── Level 4: Activities / Tasks (e.g., Excavate Footings, Place Rebar, Pour Concrete)

The 100% Rule

The fundamental governing principle of WBS design is the 100% Rule. The WBS must encompass 100% of the work defined by the project scope and capture all deliverables—internal, external, and interim. The rule applies across all levels of the hierarchy:

• The sum of the work at the "child" level must equal 100% of the work represented by the "parent" level.
• The WBS must not include any work that falls outside the actual contract scope (0% scope creep).
• Elements must be mutually exclusive; no scope overlap or duplication can exist between sibling packages.

Defining the Work Package

A Work Package represents the lowest level of the WBS before decomposing into detailed scheduling activities. A properly formulated work package possesses specific operational attributes:

• Deliverable-Oriented: Results in a measurable, verifiable physical product or milestone.
• Single Accountability: Assigned to a single designated subcontractor, superintendent, or trade foreman.
• Resource and Cost Identifiable: Directly measurable in terms of labor hours, material costs, equipment usage, and subcontracts.
• Manageable Duration: Typically spans an 80-hour threshold or one to two weeks of field execution, preventing unmonitored scope drift.

The WBS Dictionary

Accompanying the WBS hierarchy is the WBS Dictionary, a formal document that provides detailed narrative descriptions of each component. It defines the technical boundaries, milestones, deliverable specifications, required materials, quality control standards, and contract references for every work package, ensuring that subcontractors and estimators possess identical interpretations of package scope.

---

Bar Charts (Gantt Charts) vs. Logic Network Schedules

Contractors utilize two primary visual mediums for scheduling construction work: Gantt bar charts and logic network diagrams. Understanding their operational distinctions and analytical limitations is essential for licensing examinations.

While a Gantt chart is effective for executive presentations and field notice boards, it is dangerous as a sole control tool on complex projects because it fails to reveal how an isolated delay in one activity affects downstream milestones.

---

Critical Path Method (CPM) Fundamentals: AON vs. AOA

The Critical Path Method (CPM) is a deterministic mathematical modeling technique developed in the late 1950s by the DuPont Corporation and Remington Rand. Unlike probabilistic methods such as Program Evaluation and Review Technique (PERT)—which uses three duration estimates (optimistic, most likely, pessimistic)—CPM relies on single, deterministic duration estimates derived from empirical labor production rates and quantity takeoffs.

Network Conventions: AON vs. AOA

Historically, CPM schedules were constructed using two distinct graphic conventions:

1. Activity-on-Arrow (AOA / Arrow Diagramming Method - ADM): Arrows represent activities requiring time and resources, while circular nodes represent milestone events (start or completion points). AOA networks cannot easily accommodate complex lead/lag logic and frequently require "dummy activities" (dashed arrows with zero duration and zero cost) simply to maintain logical integrity and unique node identification.
2. Activity-on-Node (AON / Precedence Diagramming Method - PDM): Rectangular nodes represent activities, while lines or arrows represent logical relationships (dependencies). AON has completely superseded AOA in modern construction project management software (such as Primavera P6 and Microsoft Project) due to its superior flexibility and ability to handle advanced dependency relationships.

Standard AON Node Anatomy

CPM practice problems commonly use this Activity-on-Node box layout:

┌───────────────────┬────────────────────┬───────────────────┐
│ Early Start (ES)  │    Duration (D)    │ Early Finish (EF) │
├───────────────────┴────────────────────┴───────────────────┤
│                Activity ID & Description                   │
├───────────────────┬────────────────────┬───────────────────┤
│  Late Start (LS)  │  Total Float (TF)  │  Late Finish (LF) │
└───────────────────┴────────────────────┴───────────────────┘

• Early Start (ES): The earliest possible calendar point in time an activity can commence, based on network logic and completion of all predecessors.
• Duration (D): The estimated working time required to complete the activity using planned labor and equipment resources.
• Early Finish (EF): The earliest possible calendar point in time an activity can finish.
• Late Start (LS): The latest possible calendar point an activity can begin without delaying the overall contracted project completion date.
• Late Finish (LF): The latest possible calendar point an activity can finish without delaying the overall contracted project completion date.
• Total Float (TF): The amount of time an activity can be delayed without delaying the project completion date.

---

Forward Pass and Backward Pass Calculations

Determining activity early dates, late dates, float values, and the critical path requires two sequential mathematical passes through the network: the Forward Pass and the Backward Pass.

[START] ──► Forward Pass (Calculates ES and EF; drives left-to-right)
               │
               ▼
            Determines Minimum Project Duration
               │
[FINISH] ◄── Backward Pass (Calculates LF and LS; drives right-to-left)

The Forward Pass: Determining Early Dates

The forward pass proceeds chronologically from the initial project milestone to the final activity. Using the standard end-of-day convention (where Day 0 represents the start of work):

1. Initial Activity: For the starting activity, $ES = 0$.
2. Early Finish Formula: For any activity: $EF = ES + \text{Duration}$
3. Convergence (Merge Points): When an activity has multiple immediate predecessors, its Early Start is governed by the maximum Early Finish of those predecessors: $ES = \max(EF_{\text{predecessors}})$ Rule: A successor cannot begin until all of its required predecessors have finished.

The Backward Pass: Determining Late Dates

The backward pass proceeds in reverse chronological order from the final project activity back to the starting milestone:

1. Project Finish Activity: For the final activity, the Late Finish is set equal to its Early Finish (or the mandatory contract completion date): $LF_{\text{project}} = EF_{\text{project}}$
2. Late Start Formula: For any activity: $LS = LF - \text{Duration}$
3. Divergence (Burst Points): When an activity has multiple immediate successors, its Late Finish is governed by the minimum Late Start of those successors: $LF = \min(LS_{\text{successors}})$ Rule: An activity must finish in time to accommodate the most urgent successor's late start.

---

Float Analysis: Total Float vs. Free Float

Float (or slack) quantifies scheduling flexibility. In construction management, float is a critical asset that governs risk allocation, delay dispute negotiations, and resource leveling.

1. Total Float (TF)

Total Float is the total amount of time an activity can be delayed from its early start date without delaying the contracted project completion date (or violating a mandatory completion milestone).

$\text{Total Float} (TF) = LS - ES = LF - EF$

• Zero Float ($TF = 0$): The activity is critical. Any delay will immediately delay project completion.
• Positive Float ($TF > 0$): The activity has flexibility; it can absorb delays up to the float value without delaying completion.
• Negative Float ($TF < 0$): Occurs when an external contractual deadline or imposed milestone is earlier than the calculated early finish date. Indicates the project is currently trending behind schedule.

2. Free Float (FF)

Free Float is the amount of time an activity can be delayed without delaying the Early Start of any immediate successor activity.

$\text{Free Float} (FF) = \min(ES_{\text{successors}}) - EF$

• Free Float is "owned" exclusively by the activity; consuming free float has zero impact on downstream activities.
• Total Float is shared along an entire network path. Consuming total float on an early activity reduces the available float for all subsequent activities on that chain.
• Mathematically, Free Float can never exceed Total Float: $FF \le TF$.

3. Interfering Float

Interfering Float is the difference between Total Float and Free Float:

$\text{Interfering Float} = TF - FF$

It represents the portion of total float that, if consumed by delaying the activity, will delay the early start of downstream successors without delaying the overall project completion date.

---

Identifying the Critical Path

The Critical Path is defined by three interrelated rules:

1. It is the longest continuous sequence of activities from project start to project finish.
2. It represents the shortest possible time required to complete the total project.
3. It consists of activities that possess zero Total Float ($TF = 0$) (or the minimum float in a network with negative float).

Exam Key: A project network may have more than one critical path operating in parallel. When multiple critical paths exist, project management risk increases significantly because a delay on either path delays the overall project.

---

Activity Dependency Logic and Lead/Lag Durations

In modern Precedence Diagramming Method (PDM) scheduling, dependencies between activities are modeled using four primary relationship types:

1. Finish-to-Start (FS):  [ Activity A ] ──────────► [ Activity B ]
                                        (Most common)

2. Start-to-Start (SS):   [ Activity A ]
                               │ (SS + Lag)
                               ▼
                          [ Activity B ]

3. Finish-to-Finish (FF):                [ Activity A ]
                                                │ (FF + Lag)
                                                ▼
                                         [ Activity B ]

4. Start-to-Finish (SF):  [ Activity A ] ──(SF)──► [ Activity B ] (Rare)

1. Finish-to-Start (FS)

The standard, most common relationship in construction (>90% of all network ties). Activity B cannot commence until Activity A has completely finished.

• Example: Activity A: "Erect Structural Steel" $\rightarrow$ (FS) $\rightarrow$ Activity B: "Install Metal Roof Decking".

2. Start-to-Start (SS)

Activity B cannot start until Activity A has started. Commonly used to model phased or staggered operations where successive trades work concurrently.

• Example: Activity A: "Trench Utility Line" $\rightarrow$ (SS with 2-day Lag) $\rightarrow$ Activity B: "Lay Pipe in Trench". Pipe laying can commence two days after trenching begins.

3. Finish-to-Finish (FF)

Activity B cannot finish until Activity A has finished. Frequently used when two concurrent tasks must conclude simultaneously or in close sequence.

• Example: Activity A: "Rough Electrical Installation" $\rightarrow$ (FF with 1-day Lag) $\rightarrow$ Activity B: "In-Wall Inspection". The inspection cannot conclude until the rough wiring is 100% finished.

4. Start-to-Finish (SF)

Activity B cannot finish until Activity A has started. This is rare in physical construction and typically restricted to just-in-time material supply or security shift handovers.

Lags and Leads

• Lag: A mandatory delay inserted between a predecessor and successor. A positive lag shifts the successor forward in time. For example, a FS + 7-day Lag between pouring concrete footings and structural steel erection represents mandatory concrete curing time.
• Lead (Negative Lag): An acceleration where a successor begins before its predecessor is completely finished. For instance, FS - 2-day Lead allows the successor to start two days prior to predecessor completion.

---

Schedule Compression Methods: Crashing vs. Fast-Tracking

When a project falls behind schedule or the owner demands an accelerated completion date, project managers must compress the schedule. The two recognized compression techniques are Crashing and Fast-Tracking.

Crashing Mechanics and the Cost Slope Formula

When crashing a schedule, you must only crash activities on the critical path. Crashing a non-critical activity incurs additional cost without shortening the overall project duration by a single day.

When multiple critical activities exist, the scheduler must select the activity that provides the maximum time reduction at the lowest financial expense. This is evaluated using the Cost Slope:

$\text{Cost Slope} = \frac{\text{Crash Cost} - \text{Normal Cost}}{\text{Normal Duration} - \text{Crash Duration}} = \frac{\Delta \text{Cost}}{\Delta \text{Time}}$

The Law of Diminishing Returns in Crashing

Project managers must be cautious of over-crashing. Adding excessive labor or working continuous 60-hour weeks leads to trade stacking (spatial congestion), increased safety incidents, fatigue, and diminishing marginal productivity, where adding 20% more labor may yield only a 5% increase in production output.

---

Worked Numerical CPM Example

Consider a commercial sitework and foundation scope consisting of seven sequential activities:

Step 1: Forward Pass Calculations

• Activity A: $ES = 0$; $EF = 0 + 4 = 4$.
• Activity B: Predecessor A ($EF = 4$). $ES = 4$; $EF = 4 + 6 = 10$.
• Activity C: Predecessor A ($EF = 4$). $ES = 4$; $EF = 4 + 5 = 9$.
• Activity D: Predecessor B ($EF = 10$). $ES = 10$; $EF = 10 + 7 = 17$.
• Activity E: Predecessor B ($EF = 10$). $ES = 10$; $EF = 10 + 3 = 13$.
• Activity F: Predecessor C ($EF = 9$). $ES = 9$; $EF = 9 + 6 = 15$.
• Activity G: Predecessors D ($EF = 17$) and F ($EF = 15$). Convergence rule applies: $ES = \max(17, 15) = 17$; $EF = 17 + 4 = 21$.

Total Project Duration = 21 Working Days.

Step 2: Backward Pass Calculations

• Activity G: $LF = 21$; $LS = 21 - 4 = 17$.
• Activity E: Terminal activity (no successors). $LF = 21$; $LS = 21 - 3 = 18$.
• Activity D: Successor G ($LS = 17$). $LF = 17$; $LS = 17 - 7 = 10$.
• Activity F: Successor G ($LS = 17$). $LF = 17$; $LS = 17 - 6 = 11$.
• Activity B: Successors D ($LS = 10$) and E ($LS = 18$). Divergence rule applies: $LF = \min(10, 18) = 10$; $LS = 10 - 6 = 4$.
• Activity C: Successor F ($LS = 11$). $LF = 11$; $LS = 11 - 5 = 6$.
• Activity A: Successors B ($LS = 4$) and C ($LS = 6$). Divergence rule applies: $LF = \min(4, 6) = 4$; $LS = 4 - 4 = 0$.

Step 3: Float and Critical Path Determination

The Critical Path is: A $\rightarrow$ B $\rightarrow$ D $\rightarrow$ G (Duration: 21 Days).