CELE Construction Management & Methods — Project Planning and Scheduling (CPM/PERT)Summary

CPM is a deterministic scheduling technique that identifies the longest sequence of dependent activities in a project network. The critical path determines the minimum project duration—no activity on this path has slack or float. Any delay in a critical activity directly delays the entire project. CPM uses activity durations based on historical data or expert judgment, assuming fixed (non-probabilistic) durations. The method involves constructing a network diagram, performing a forward pass to calculate early times (ES and EF), a backward pass to calculate late times (LS and LF), and identifying activities where ES = LS (indicating zero float). In Philippine construction projects, CPM is the standard scheduling approach mandated by most project delivery methods and contractual frameworks.

A network diagram represents project activities and their logical dependencies. There are two common formats: Activity-on-Node (AON), where activities are boxes connected by arrows showing dependencies, and Activity-on-Arrow (AOA), where activities are represented by arrows between nodes. AON diagrams are more intuitive and widely used in modern project management software. Activities are connected by precedence relationships: finish-to-start (FS, most common), start-to-start (SS), finish-to-finish (FF), and start-to-finish (SF). A dummy activity (zero duration) may be used in AOA diagrams to show logical dependencies without consuming time. In Philippine construction, most software (like Primavera P6 or Microsoft Project) uses AON format, making familiarity with this approach essential.

The forward pass calculates the earliest possible time each activity can start (ES) and finish (EF), beginning from the project start (time zero). The calculation uses: EF = ES + duration. For the first activity, ES = 0. For subsequent activities, ES equals the maximum EF of all predecessor activities—this ensures all predecessors are complete before the successor begins. The forward pass is performed sequentially from start to finish. Early Finish time for the last activity represents the minimum possible project duration if no delays occur. This calculation is deterministic and assumes predecessors finish at their earliest times.

The backward pass calculates the latest time each activity can start (LS) and finish (LF) without delaying the project beyond its minimum duration. Starting from the project end, the calculation uses: LS = LF - duration. The final activity's LF is set equal to its EF (the minimum project duration). For other activities, LF equals the minimum LS of all successor activities—this ensures the activity finishes early enough for all successors to start on time. The backward pass proceeds sequentially from finish to start. If an activity's LS is negative, it indicates a logic error or that the imposed finish date is unachievable.

Total Float (TF) is the amount of time an activity can be delayed without pushing the project finish date beyond the minimum duration. Calculated as: TF = LS - ES (or equivalently, TF = LF - EF). An activity with TF = 0 is on the critical path; any delay increases project duration. Activities with TF > 0 have scheduling flexibility. Free Float (FF) is the amount of time an activity can slip without delaying any successor activity. FF is always ≤ TF. Activities on the critical path have both TF = 0 and FF = 0. Non-critical activities may have free float even within total float, allowing local shifts in schedule. In Philippine construction contracts, understanding float is crucial for change order negotiations and delay analysis.

The critical path is the longest sequence of dependent activities from project start to finish. Its length equals the minimum project duration. All activities on the critical path have zero total float (ES = LS and EF = LF). If any critical activity is delayed, the entire project is delayed by the same amount. Typically, there is one critical path, but a project may have multiple critical paths of equal length. Non-critical activities have scheduling flexibility (positive float). To identify the critical path: (1) perform forward and backward passes, (2) find all activities where ES = LS (or EF = LF), (3) verify these activities form a continuous path from start to finish. Reducing project duration requires crashing activities on the critical path; crashing non-critical activities has no effect on project completion unless it creates a new critical path.

Crashing is the process of reducing activity duration to shorten the overall project duration, typically at increased cost. When an activity is crashed, its normal duration is reduced to a crash duration at a crash cost. The crash cost per day = (crash cost - normal cost) / (normal duration - crash duration). To compress the project schedule: (1) identify all critical activities, (2) crash the critical activity with the lowest cost per day, (3) recalculate the schedule to identify the new critical path, (4) repeat until the target duration is achieved or crashing becomes uneconomical. Important: crashing non-critical activities does not reduce project duration unless it makes them critical. Multiple paths may become critical simultaneously, requiring simultaneous crashing. Crashing continues until either the target date is met or all activities reach their crash durations.

PERT is a probabilistic scheduling technique used when activity durations are uncertain. Instead of a single duration, three time estimates are provided: optimistic time (a, best-case scenario with minimal obstacles), most likely time (m, most probable duration based on experience), and pessimistic time (b, worst-case scenario including unexpected delays). The expected duration is calculated as: t_e = (a + 4m + b) / 6. This formula weights the most likely time (m) by a factor of 4, reflecting its higher probability. The variance is: σ² = ((b - a) / 6)². PERT assumes a beta distribution for activity durations. For the overall project, variances along the critical path are summed, and the project standard deviation is: σ_project = √(Σσ² along critical path). This allows probabilistic analysis of completion dates.

Using PERT, the probability of completing a project by a target date can be calculated. First, calculate the project standard deviation (σ_project) from critical path activity variances. Then, compute the Z-score: Z = (target date - t_e,project) / σ_project, where t_e,project is the expected project duration. The Z-score indicates how many standard deviations the target date is from the expected duration. Using the standard normal distribution table, the Z-score corresponds to a probability. For example, Z = 0 means 50% probability of on-time completion; Z = 1 means approximately 84%; Z = -1 means approximately 16%. A typical target is Z ≥ 1.65 (95% confidence). This analysis helps set realistic schedules and identify the risk of missing deadlines given schedule uncertainties.

Float (slack) represents scheduling flexibility. Understanding how float is distributed across the project network is crucial for effective schedule management. Total float belongs to the project as a whole—consuming float on one activity reduces available float for other activities sharing that path. Free float belongs to an activity and can be consumed without affecting successors. In multi-path networks, activities may share float; reducing one activity's float can affect others downstream. Best practice: never fully consume float on critical path activities; maintain schedule buffers. In Philippine construction, contractual provisions often address float consumption, especially regarding who benefits from schedule delays that consume float. Modern project controls track float consumption as a schedule health indicator.

Construction schedules face numerous risks: weather delays, material shortages, labor availability, design changes, and unforeseen site conditions. CPM provides the deterministic minimum duration; PERT quantifies uncertainty. Schedule buffers (contingencies) should be added to critical path activities to absorb probable delays. The buffer magnitude depends on the project's risk profile: low-risk projects (30% contingency), medium-risk projects (50% contingency), high-risk projects (100%+ contingency). Rather than distributing buffer throughout activities, best practice concentrates buffers on critical path and high-uncertainty activities. This approach, called Critical Chain Project Management (CCPM), protects the finish date while minimizing resource contention. In Philippine construction, especially for projects prone to weather delays (typhoon season) or regulatory delays, adequate buffering is essential.

A 30-story residential tower with 24-month schedule requires CPM to coordinate structural work, MEP rough-in, and finishing trades across multiple floors. PERT accounts for weather delays during the Philippine typhoon season (June–November). Critical path activities: pile foundation, core wall construction, and structural completion. Non-critical activities: facade installation and interior fit-out can be scheduled with float. Crashing decisions focus on critical activities (additional formwork crews, extended shifts) versus schedule acceleration (premium payments to suppliers). Probability analysis targets 95% confidence of on-time turnover, essential for pre-selling units.

A 15-km expressway extension with 36-month duration involves land acquisition, design, utility relocation, earthworks, pavement, and tolling system installation. CPM manages parallel activities (preliminary engineering, ROW acquisition, detailed design) and sequential phases (construction bid, mobilization, construction). PERT estimates account for uncertain permitting timelines, material delivery delays, and weather impacts on earthwork. Critical chain includes design completion → bid approval → contract award → mobilization → main construction. Buffer management protects against regulatory delays and contractor mobilization periods common in Philippine infrastructure projects. Schedule risk mitigation includes maintaining float on critical activities and scheduling contingencies for utility relocations (typically delays cause overruns). Cost-schedule tradeoffs: accelerating design or expanding crews affects project budget. Delay analysis (documented in monthly progress reports) tracks float consumption to support claims if delays occur.

A water treatment plant (BOT model) has 24-month construction schedule to meet concession agreement milestone deadlines. Critical activities: site preparation, equipment procurement, civil works, mechanical installation, and commissioning. Equipment long-lead times (12-16 months for specialized filters and pumps) drive early crashing decisions. Network logic includes finish-to-finish relationships (equipment arrival must precede final installation). PERT accounts for weather delays, supply chain uncertainties, and commissioning test repeat cycles. Delay penalties in the concession agreement (loss of revenue for each day late) justify spending on schedule compression for critical activities. Float management: protective buffers on procurement and delivery dates prevent cascading delays. Schedule monitoring: monthly updates track actual progress, recalculate critical path, and trigger mitigation plans if critical activities slip.

A phased renovation of an operational shopping mall requires concurrent site operations and construction. CPM sequences demolition, structural work, MEP installation, and tenant fit-out in staggered phases to minimize business disruption. Constraints include partial operational status (some tenants remain), limited working hours (no night construction), and coordination with tenant vacations and leaseholder approvals. PERT accommodates tenant coordination delays and design changes common in renovation. Critical path: structural completion → MEP rough-in → testing → tenant handover. Non-critical activities: minor structural repairs and temporary facilities have float, allowing flexible scheduling around operational needs. Crashing decisions: priority activities receive funding for extended shifts or concurrent operations; low-priority activities defer to available float. The schedule directly affects revenue loss and tenant satisfaction, making accurate CPM/PERT analysis critical to project success.

A petrochemical plant shutdown for 60 days of maintenance and equipment replacement requires precise CPM to minimize production loss. Activities are highly constrained: equipment removal → inspection → refurbishment/replacement → installation → testing → restart. Logic is strictly sequential with minimal float. PERT accounts for unexpected equipment damage discoveries during inspection (extending duration) and testing failures requiring rework. Critical path is the equipment removal → replacement cycle; any delay extends plant downtime and costs millions daily. Crashing is limited by equipment availability and workforce size; parallel crews may expedite some parallel activities (e.g., piping and electrical work). Float is managed tightly: any non-critical activity consuming float reduces buffer for contingencies. Contingency time (typically 10–20% of critical path) protects against test failures and rework cycles common in major maintenance.

A 2,000-unit residential subdivision with 48-month development schedule requires CPM to coordinate site infrastructure (roads, utilities, drainage), individual lot development, and common facilities. Activities are partially parallel: infrastructure and lot development can overlap; common facilities follow. PERT accounts for soil conditions uncertainties (soil investigation may reveal unexpected fill requirements), weather delays in earthworks, and utility agency approval timelines (unpredictable in the Philippines). Critical path likely includes: detailed design → site infrastructure → lot development completion. Non-critical activities: landscaping, recreation facilities, and amenities have float. Crashing: accelerating site infrastructure allows earlier lot releases, accelerating sales and cash flow. Schedule compression focuses on activities affecting marketable units (grading, utilities to lots) while non-critical amenities may be deferred if schedule pressure exists. Float management: maintaining schedules on infrastructure prevents cascading delays to lot developers.

When schedule delays occur, CPM/PERT analysis supports change order claims and delay assessments. Baseline schedule (approved at project start) documents original critical path and float. As delays occur (weather, design changes, material shortages), the current schedule is updated, and the impact analyzed: which activities delayed? Did they delay the critical path? How much float was consumed? Was the delay compensable (client-caused) or non-compensable (contractor fault or force majeure)? Timeline analysis compares as-planned vs. as-built schedules to identify delay causes. Cost of delay includes prolongation costs (extended site overhead, labor escalation, equipment rental). In Philippine construction disputes, well-documented schedule analysis often determines claim validity. Courts increasingly expect professional CPM analysis to support delay claims, making proper schedule documentation from project inception essential.