8.1 Project Planning, Work Breakdown Structures & CPM Scheduling

Project Planning, Work Breakdown Structures & CPM Scheduling

Quick Reference: Construction project success depends on rigorous scope decomposition and network-based logic scheduling. The Work Breakdown Structure (WBS) establishes the project baseline by decomposing scope into deliverable work packages governed by the 100% Rule. The Critical Path Method (CPM) applies mathematical forward and backward pass algorithms to determine early and late activity dates, identifying the Critical Path—the longest sequence of dependent tasks with zero Total Float ($TF = LS - ES = LF - EF$). Delays to critical path activities delay overall project completion day-for-day. Schedule acceleration requires deliberate trade-offs: fast-tracking overlaps sequential activities at high risk of rework, while crashing injects resources into critical activities based on the lowest crash cost per unit time.

---

1. Project Management Framework & Life Cycle Phases

Commercial and industrial construction projects progress through five distinct, sequential phases that comprise the project life cycle. Managing these phases systematically ensures that the contractual scope, budget, schedule, and quality benchmarks defined during preconstruction are realized during field execution.

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│   1. Initiation │ ──> │   2. Planning   │ ──> │  3. Execution   │
└─────────────────┘     └─────────────────┘     └────────┬────────┘
                                                         │
                        ┌─────────────────┐              │ Integrated
                        │   5. Closeout   │ <──┐         │ Oversight
                        └─────────────────┘    │         ▼
                                               │┌─────────────────┐
                                               └┤ 4. Monitoring   │
                                                │  & Controlling  │
                                                └─────────────────┘

The Five Project Life Cycle Phases

1. Initiation Phase:

   • Defines the initial project charter, business justification, and feasibility.
   • Identifies key stakeholders (owner, architect/engineers, general contractor, regulatory authorities, financial lenders).
   • Establishes broad project objectives, order-of-magnitude budget estimates, and macro milestone targets.

2. Planning Phase:

   • Establishes the total project scope baseline through architectural and engineering design documents.
   • Decomposes project scope into a hierarchical Work Breakdown Structure (WBS).
   • Develops the resource-loaded CPM baseline schedule, project budget, procurement schedule, and site logistics plan.
   • Drafts project management plans encompassing Quality Assurance/Quality Control (QA/QC), site safety, risk mitigation, and communication protocols.

3. Execution Phase:

   • Encompasses physical site mobilization, trade subcontract execution, material procurement, and field construction operations.
   • Allocates field personnel, construction plant, and heavy equipment to active work packages.
   • Directs and coordinates specialty subcontractors while implementing quality assurance standards and site safety programs.

4. Monitoring & Controlling Phase:

   • Operates concurrently with the Execution Phase.
   • Measures ongoing field performance against the approved baseline schedule and budget using tools such as Earned Value Management (EVM).
   • Administers the formal change management process, tracks Requests for Information (RFIs), reviews submittals, and oversees safety compliance.
   • Identifies schedule variances early to initiate corrective actions (re-sequencing, schedule compression) before critical milestones lapse.

5. Project Closeout Phase:

   • Manages punch list execution, regulatory agency inspections, life safety testing, and obtaining the Certificate of Occupancy (CO).
   • Formalizes Substantial Completion, transitioning operational control and risk of loss to the project owner.
   • Assembles and submits closeout deliverables: Operations and Maintenance (O&M) manuals, certified as-built drawings, warranties, attic stock, and final lien waivers.
   • Resolves outstanding subcontractor change orders, releases retainage, and conducts internal post-project cost audits.

---

2. Work Breakdown Structure (WBS) & The 100% Rule

The Work Breakdown Structure (WBS) is a hierarchical, deliverable-oriented breakdown of the total scope of work to be executed by the project team. It bridges the gap between high-level architectural drawings and the discrete operational activities that superintendents and project managers schedule and control.

                             Level 1: Total Project Scope
                           [ Commercial Office Building ]
                                         │
            ┌────────────────────────────┼────────────────────────────┐
     Level 2: Phase               Level 2: Phase               Level 2: Phase
   [ Substructure ]             [ Core & Shell ]              [ Interior TI ]
            │                            │                            │
     Level 3: Element             Level 3: Element             Level 3: Element
    [ Foundations ]            [ Structural Frame ]         [ Drywall & Finishes ]
            │                            │                            │
  Level 4: Work Package        Level 4: Work Package        Level 4: Work Package
  [ Cast-in-Place Grade       [ Structural Steel Erection   [ Metal Stud Framing &
       Beams (WP-03) ]             Grid A-D (WP-08) ]          Drywall Level 2 (WP-15) ]

The 100% Rule

The foundational standard governing WBS development is the 100% Rule. Formulated by the Project Management Institute (PMI) and adopted across construction management standards:

The 100% Rule: The Work Breakdown Structure must encompass 100% of the work defined by the project scope and account for all deliverables—including external subcontractor deliverables, internal project management, and temporary field installations. The rule applies hierarchically: the sum of the work at each subordinate level must roll up exactly to 100% of the work represented by the parent element, with zero omitted work and zero extraneous work (no scope creep).

Characteristics of the Work Package

The Work Package represents the lowest level of decomposition in the WBS. It is not an individual daily task, but rather a discrete, assignable package of work that exhibits five distinct operational criteria:

• Independent Unit: It can be assigned to a single responsible trade contractor or self-perform crew.
• Measurable Deliverable: It produces a tangible, verifiable physical product (e.g., "Cast-in-Place Grade Beams Level 1").
• Cost Estimation: Direct labor, equipment, and material costs can be reliably estimated and budgeted.
• Duration Estimation: Physical duration can be calculated using crew production rates (e.g., cubic yards per crew-day).
• Control Point: It serves as an accounting cost code and scheduling milestone for Earned Value tracking.

The WBS Dictionary

A graphical WBS chart alone is insufficient for construction procurement. It must be paired with a WBS Dictionary—a companion document providing detailed technical specifications for each work package:

• Scope Description: Detailed technical narrative of work included and explicitly excluded.
• Milestone & Schedule Dates: Target start and completion dates linked to the master schedule.
• Contractor / Organization: Assigned specialty trade subcontractor and license classification.
• Resource Requirements: Required equipment, specialized staging, and hoisting equipment.
• Quality & Acceptance Criteria: Code citations, ASTM material standards, and inspection checkpoints.

---

3. Scheduling Methodologies: Bar Charts vs. Network Diagrams

Construction schedules serve two critical functions: communication with field personnel and mathematical calculation of project duration. The two primary graphical techniques utilized are Bar (Gantt) Charts and Network Diagrams.

Evolution to the Precedence Diagramming Method (PDM)

Early network scheduling utilized Activity-on-Arrow (AOA) diagrams, where arrows represented tasks and nodes represented connecting events. Modern construction management relies almost exclusively on the Precedence Diagramming Method (PDM), also known as Activity-on-Node (AON):

• Nodes: Represent activities or work packages and contain metadata (Activity ID, Description, Duration, Early Start, Early Finish, Late Start, Late Finish, Total Float).
• Arrows: Represent logical dependencies and flow of work between activities.

---

4. Precedence Diagramming Method (PDM) & Logic Relationships

In PDM scheduling, the logical relationship between a preceding activity (predecessor) and a following activity (successor) is modeled using four dependency types. Understanding these relationships is critical for building valid construction logic networks.

1. Finish-to-Start (FS)       2. Start-to-Start (SS)
   [ Activity A ]                [ Activity A ]
         │                             │
         ▼                             ▼
   [ Activity B ]                [ Activity B ]

3. Finish-to-Finish (FF)      4. Start-to-Finish (SF)
   [ Activity A ]                [ Activity A ]
         │                             │
         ▼                             ▼
   [ Activity B ]                [ Activity B ]

The Four Dependency Types

1. Finish-to-Start (FS):

   • Definition: The predecessor must completely finish before the successor can initiate.
   • Frequency: Represents approximately 90–95% of all construction logic links.
   • Construction Example: Concrete footings must finish curing before structural steel baseplates can be set and bolted ($A \rightarrow B$).

2. Start-to-Start (SS):

   • Definition: The initiation of the successor depends upon the initiation of the predecessor.
   • Frequency: Used frequently with lags to model concurrent linear production work.
   • Construction Example: Interior wall framing initiates; after a 3-day lead, rough electrical conduit rough-in begins within the same zone ($A \xrightarrow{\text{SS}+3} B$).

3. Finish-to-Finish (FF):

   • Definition: The completion of the successor depends upon the completion of the predecessor.
   • Frequency: Used to coordinate simultaneous wrap-up of related trades.
   • Construction Example: Drywall taping and finishing must complete before interior final prime painting can complete ($A \rightarrow B$).

4. Start-to-Finish (SF):

   • Definition: The successor cannot finish until the predecessor has started.
   • Frequency: Extremely rare in construction scheduling; often discouraged by public agency specifications because it creates confusing network logic loops.
   • Construction Example: A temporary diesel generator system cannot be shut down and decommissioned (finished) until the permanent building electrical service has been energized (started).

Leads and Lags

Logic relationships can be modified using time adjustments:

• Lag (Positive Lag): An enforced waiting duration between activities. Concrete curing is the classic construction lag: after stripping forms (Activity A), an enforced lag of 7 days (7-day cure time) must elapse before structural backfilling or heavy vertical loading (Activity B) can commence ($FS + 7\text{d}$). Lags consume calendar time but require no direct labor or equipment resources.
• Lead (Negative Lag): An acceleration overlap where the successor begins prior to the completion of the predecessor ($FS - 3\text{d}$). Schedulers generally discourage excessive negative leads because they obscure physical logic and make schedule updates prone to logic corruption.

---

5. Critical Path Method (CPM) Mathematical Mechanics

The Critical Path Method executes two computational sweeps across the network: the Forward Pass (which establishes the earliest possible project completion date) and the Backward Pass (which calculates the latest permissible start and finish dates that preserve that completion target).

Standard CPM Activity Node Layout:
┌───────────────────────────────────────────────┐
│ Early Start (ES)    │        Duration (D)     │ Early Finish (EF) │
├─────────────────────┴─────────────────────────┴───────────────────┤
│                 Activity Description / ID                         │
├───────────────────────────────────────────────────────────────────┤
│ Late Start (LS)     │      Total Float (TF)   │ Late Finish (LF)  │
└───────────────────────────────────────────────┘

Mathematical Formulation (End-of-Day Calendar Convention)

In standard construction management calculations, using integer day counts (where day 1 is the start of the project):

$\text{Early Finish (EF)} = \text{Early Start (ES)} + \text{Duration (D)} - 1$

$\text{Successor Early Start (ES)} = \max(\text{EF of all immediate predecessors}) + 1$

(Note: When using standard continuous 0-based calculus, $\text{EF} = \text{ES} + \text{D}$ and $\text{Successor ES} = \max(\text{EF of predecessors})$. Both conventions yield identical durations and float calculations. The formulas below illustrate the continuous calculus standard ubiquitous in computer algorithms).

$\mathbf{EF} = \mathbf{ES} + \mathbf{Duration}$

$\mathbf{ES}_{\text{successor}} = \max(\mathbf{EF}_{\text{predecessors}})$

The Backward Pass (Late Dates)

Beginning at the project end date (where $\text{Late Finish of terminal activity} = \text{Early Finish of terminal activity}$):

$\mathbf{LS} = \mathbf{LF} - \mathbf{Duration}$

$\mathbf{LF}_{\text{predecessor}} = \min(\mathbf{LS}_{\text{successors}})$

Float (Slack) Calculations

Float represents schedule flexibility. Construction contracts distinguish between Total Float and Free Float:

1. Total Float (TF): $\mathbf{TF} = \mathbf{LS} - \mathbf{ES} = \mathbf{LF} - \mathbf{EF}$

   • The total amount of time that an activity can be delayed from its early start without delaying the overall project completion date or violating a contractual completion milestone.
   • Total Float is a shared project resource. If an early non-critical trade consumes all total float on a path, subsequent trades on that path lose all float and become critical.

2. Free Float (FF): $\mathbf{FF} = \min(\mathbf{ES}_{\text{successors}}) - \mathbf{EF}$

   • The amount of time an activity can be delayed without delaying the Early Start of any immediately following successor activity.
   • Free Float belongs exclusively to that specific activity and does not impact downstream operations.
   • Mathematical Rule: Free Float can never exceed Total Float ($FF \le TF$).

Defining the Critical Path

• The Critical Path is the longest continuous chain of activities through the network diagram from project inception to completion.
• Activities on the critical path have zero Total Float ($TF = 0$).
• A project has at least one critical path, but can have multiple parallel critical paths.
• Any delay to any critical path activity will result in a direct, day-for-day delay to the final project completion date.
• Near-Critical Paths: Paths with low total float (typically 1 to 5 days). Schedulers must track near-critical paths closely, as modest delays can convert them into the primary critical path.
• Negative Float ($TF < 0$): Occurs when a contractually mandated completion date or owner milestone is earlier than the mathematically calculated Early Finish date. Negative float signifies that the project is already trending behind schedule.

---

6. Comprehensive Worked CPM Calculation Example

Consider a commercial building foundations and core package with six activities (A through F). The activities, immediate predecessors, and durations in working days are summarized below:

Step 1: Forward Pass (Early Dates)

• Activity A: No predecessors. $\text{ES} = 0$. $\text{EF} = 0 + 4 = 4$.
• Activity B: Predecessor A (EF = 4). $\text{ES} = 4$. $\text{EF} = 4 + 6 = 10$.
• Activity C: Predecessor A (EF = 4). $\text{ES} = 4$. $\text{EF} = 4 + 8 = 12$.
• Activity D: Predecessor B (EF = 10). $\text{ES} = 10$. $\text{EF} = 10 + 10 = 20$.
• Activity E: Predecessor C (EF = 12). $\text{ES} = 12$. $\text{EF} = 12 + 5 = 17$.
• Activity F: Predecessors D (EF = 20) and E (EF = 17). $\text{ES} = \max(20, 17) = 20$. $\text{EF} = 20 + 6 = 26$.

Total Project Duration = 26 working days.

Step 2: Backward Pass (Late Dates)

• Terminal Activity F: Set $\text{LF} = 26$. $\text{LS} = 26 - 6 = 20$.
• Activity D: Successor F (LS = 20). $\text{LF} = 20$. $\text{LS} = 20 - 10 = 10$.
• Activity E: Successor F (LS = 20). $\text{LF} = 20$. $\text{LS} = 20 - 5 = 15$.
• Activity B: Successor D (LS = 10). $\text{LF} = 10$. $\text{LS} = 10 - 6 = 4$.
• Activity C: Successor E (LS = 15). $\text{LF} = 15$. $\text{LS} = 15 - 8 = 7$.
• Activity A: Successors B (LS = 4) and C (LS = 7). $\text{LF} = \min(4, 7) = 4$. $\text{LS} = 4 - 4 = 0$.

Step 3: Float Calculation & Critical Path Table

                                  [ C: Utilities ]
                                  ES=4  EF=12 Dur=8
                                  LS=7  LF=15 TF=3
                                    /          \
                                   /            \   [ E: Slab Prep ]
                                  /              \  ES=12 EF=17 Dur=5
                                 /                \ LS=15 LF=20 TF=3
[ A: Mobilize ]    [ B: Excavate ]                   \    /
ES=0  EF=4  Dur=4  ES=4  EF=10 Dur=6                  \  /
LS=0  LF=4  TF=0   LS=4  LF=10 TF=0                    \/
  ═══════════════════════════════════> [ D: Footings ] ═══> [ F: Slab Concrete ]
          (CRITICAL PATH)              ES=10 EF=20 Dur=10   ES=20 EF=26 Dur=6
                                       LS=10 LF=20 TF=0     LS=20 LF=26 TF=0
                                        (CRITICAL PATH)      (CRITICAL PATH)

• Critical Path: A $\rightarrow$ B $\rightarrow$ D $\rightarrow$ F (Total duration = $4 + 6 + 10 + 6 = 26$ days).
• Float Analysis on Path A $\rightarrow$ C $\rightarrow$ E $\rightarrow$ F: Activity C has 3 days of Total Float but 0 days of Free Float, because delaying Activity C by 1 day forces Activity E's early start to move from day 12 to day 13. Activity E has 3 days of Total Float and 3 days of Free Float, meaning Activity E can be delayed up to 3 days without impacting Activity F's early start date of 20.

---

7. Schedule Compression: Fast-Tracking vs. Crashing

When a project falls behind schedule or an owner demands an earlier completion milestone, project managers compress the schedule using two primary techniques: Fast-Tracking and Crashing.

┌────────────────────────────────────────────────────────────────────────┐
│                     SCHEDULE COMPRESSION STRATEGIES                    │
├─────────────────────────────┬──────────────────────────────────────────┤
│ Fast-Tracking               │ Crashing                                 │
├─────────────────────────────┼──────────────────────────────────────────┤
│ • Overlaps sequential tasks │ • Adds resources to critical activities  │
│ • Concurrency-focused       │ • Cost-time tradeoff optimization        │
│ • Zero direct labor premium │ • Direct increase in project labor cost  │
│ • High risk of rework       │ • Low risk of design logic failure       │
│ • Increases spatial clashes │ • Diminishing returns from overtime      │
└─────────────────────────────┴──────────────────────────────────────────┘

Fast-Tracking

• Mechanism: Modifies schedule logic by executing activities in parallel or overlapping them (e.g., changing a Finish-to-Start link to a Start-to-Start with a lag) that are normally performed sequentially.
• Practical Example: Commencing footing excavation before 100% of the structural engineering drawings are stamped, or starting drywall framing on lower floors while upper floor structural steel erection is ongoing.
• Risks: Fast-tracking dramatically increases the risk of rework, coordination errors, and subsequent change orders if preliminary work must be altered to fit emerging upstream conditions.

Crashing

• Mechanism: Injects additional resources (overtime, second shifts, supplemental craft labor, specialized heavy machinery) into critical path activities to compress their duration for the least incremental cost.
• Cost Slope Calculation: To crash a schedule cost-effectively, calculate the Crash Cost Slope (cost per unit time saved) for each candidate critical path activity:

$\mathbf{\text{Crash Cost per Day}} = \frac{\text{Crash Cost} - \text{Normal Cost}}{\text{Normal Duration} - \text{Crash Duration}}$

Rules for Crashing a Project Schedule

1. Crash Only the Critical Path: Crashing a non-critical activity spends capital without shortening the project duration, merely increasing that activity's float.
2. Select the Lowest Crash Cost Slope: Always crash the critical path activity that possesses the lowest incremental cost per unit time saved.
3. Monitor Parallel Critical Paths: As the primary critical path compresses, near-critical paths will lose float and become critical. Once multiple critical paths emerge, you must crash activities on all concurrent critical paths simultaneously to achieve further overall schedule compression.
4. Beware Diminishing Returns: Excessive overtime causes labor fatigue, reduced production rates, and heightened safety incidents (the law of diminishing returns).

Worked Crashing Example

Suppose the 26-day project above must be compressed by 2 days. The critical activities are A, B, D, and F. Schedulers evaluate the crash costs:

• Activity A: Can crash 1 day at $800/day.
• Activity B: Can crash 2 days at $500/day.
• Activity D: Can crash 3 days at $1,200/day.
• Activity F: Can crash 1 day at $1,500/day.

Action Plan:

1. The critical activity with the lowest crash cost per day is Activity B ($500/day).
2. Crash Activity B by 2 days (reducing duration from 6 to 4 days).
3. Project duration decreases from 26 to 24 days at a total additional direct cost of $1,000 ($2 \times $500$).
4. Verify that non-critical path C-E (duration = $4 + 8 + 5 = 17$ days) has not become critical (17 days remains well below 24 days).

---

8. Realistic Exam Scenario Analyses

Scenario 1: The Imposed Contract Completion Date (Negative Float)

• Case: A general contractor enters into a contract for a Utah school district building with an agreed substantial completion milestone of August 15. The CPM schedule baseline calculation indicates that the early finish date for final life safety commissioning is August 27. The project manager identifies -12 working days of Total Float across the critical path.
• Analysis: When an imposed contractual completion date is earlier than the calculated early finish date, the backward pass produces Late Finish dates that precede Early Finish dates, generating negative float. The project is contractually in default before construction even begins. The general contractor cannot simply ignore the negative float. The management team must immediately execute schedule compression (crashing the lowest-cost critical path activities or negotiating logic revisions through fast-tracking) during the preconstruction phase to bring Total Float to zero or greater prior to baseline acceptance.

Scenario 2: Uncritical Delay Consumption & The Shared Float Rule

• Case: On a commercial warehouse project, the underground electrical conduit subcontractor experiences an unexcused 5-day material delay on an activity that possessed 6 days of Total Float and 0 days of Free Float. The electrical contractor claims the general contractor cannot assess delay damages because the activity had float. Meanwhile, the concrete slab subcontractor is delayed by 5 days and demands a time extension.
• Analysis: Under standard construction law, Total Float is a shared project resource owned by the project, not by any individual subcontractor. However, because the electrical activity had 0 days of Free Float, delaying it by 5 days directly delayed the early start of its immediate successor (the concrete slab prep). The slab contractor suffered an operational impact because its planned early start was pushed back. While the final completion date was not compromised (since 1 day of Total Float remained), the electrical subcontractor breached its coordination commitment. Schedulers must evaluate both Free Float (inter-trade handoff) and Total Float (project completion) when adjudicating delay responsibilities.