Skip to main content
Study NotesCELE · Construction Management & MethodsReal content

CELE Construction Management & MethodsProject Planning and Scheduling (CPM/PERT)Study Notes

Detailed study notes for CELE Construction Management & Methods — Project Planning and Scheduling (CPM/PERT). These are the kind of notes you would take if you were reviewing with someone who has already scored well on the CELE: organised by what Professional Regulation Commission (PRC) — Board of Civil Engineering tests first, followed by the nice-to-knows, and ending with the traps to avoid.

Exam context

On the CELE 2026, the Construction Management & Methods subtest carries a "Core" weight in Professional Regulation Commission (PRC) — Board of Civil Engineering's pattern. Project Planning and Scheduling (CPM/PERT) lands at position 2nd out of 5 in the standard review order. Target score is 70% weighted average, no sub-test below 50%, and roughly a meaningful share of items come from Construction Management & Methods on a typical CELE paper.

Project Planning and Scheduling (CPM/PERT) - Study Notes

Project Planning and Scheduling represents a critical competency area for civil engineers preparing for the PRC Licensure Examination. The Critical Path Method (CPM) and Program Evaluation and Review Technique (PERT) are fundamental project management tools that determine the minimum project duration, identify time-critical activities, and quantify schedule risk. This chapter covers network construction, the critical path determination through forward and backward pass analysis, float calculations, and probabilistic scheduling using PERT. Mastery of these concepts is essential for managing construction projects within the constraints of Philippine building codes (NSCP 2015) and standard construction practices. The techniques presented here allow engineers to optimize resource allocation, identify slack activities, and implement crashing strategies—all critical for cost-effective project delivery in the Philippine construction industry.

Summary

Project Planning and Scheduling using CPM and PERT is a cornerstone competency for PRC Civil Engineer licensure. The Critical Path Method provides a deterministic framework for identifying time-critical activities (those with zero float) and determining the minimum project duration. Through forward and backward pass analysis, engineers calculate early and late times for all activities, enabling precise identification of schedule flexibility (float). The longest path through the network—not the shortest—determines project completion time. When dealing with uncertain durations (typical in construction), PERT incorporates optimistic, most likely, and pessimistic estimates to calculate expected durations weighted toward the most likely scenario: t_e = (a + 4m + b) / 6. Variance measures uncertainty: σ² = ((b − a) / 6)². Project-level variance aggregates only critical path activities, allowing engineers to calculate the probability of meeting deadlines using the normal distribution and Z-scores. Project crashing—accelerating critical path activities through resource allocation—requires ranking activities by incremental cost (₱/day) and crashing lowest-cost options first. As the critical path shrinks, other paths may become critical, requiring simultaneous crashing of multiple paths to achieve further time reduction. Mastery of these techniques enables civil engineers to: 1. Develop realistic project schedules that account for activity sequences and dependencies 2. Identify schedule risk and quantify the probability of on-time completion 3. Make informed decisions about resource allocation and project acceleration 4. Balance cost and schedule trade-offs for optimal project delivery 5. Communicate schedule expectations to clients and stakeholders with quantified confidence levels In Philippine construction context, these methods accommodate: - Monsoon season weather impacts (June–November SW monsoon; November–April NE monsoon) - Supply chain uncertainties in an archipelagic environment - Labor availability and subcontractor coordination - Equipment mobilization constraints - Compliance with NSCP 2015 project management guidelines Common examination pitfalls include confusing float types, misapplying PERT weighting, summing variance from all activities (instead of critical path only), misinterpreting Z-scores, and selecting the shortest path as critical. Careful tabular organization, network drawing, and systematic verification prevent these errors. Success requires understanding not just the mechanics of calculations, but the underlying logic: why longest path is critical, why most-likely estimates are weighted 4×, why only critical activities contribute to project variance, and how cost-benefit analysis guides crashing decisions.

Sections

The foundation of CPM lies in representing a project as a directed network of activities and events. Each activity (represented as a node or arrow depending on notation) has an associated duration and dependencies. The network begins at a start node and terminates at an end node, with all paths representing different sequences through the project. The **Critical Path** is defined as the **longest** path through the network. This distinction is essential: while many paths exist in a typical project network, the critical path determines the minimum achievable project duration. Any delay in a critical activity directly delays the entire project; therefore, critical activities have zero flexibility or float. For a simple understanding, consider a two-path project: If Path A (A→C) takes 8 days and Path B (B→C) takes 9 days, the project cannot finish before 9 days. Activity A has 1 day of freedom; activity B (on the critical path) has none. The **forward pass** calculates earliest times (how soon each activity can start and finish), while the **backward pass** calculates latest allowable times (how late each activity can start or finish without delaying the project). Together, these passes identify which activities are critical. **Key Formula:** - Early Finish: EF = ES + duration - Early Start of successor: ES = maximum EF of all predecessors - Late Start: LS = LF − duration - Late Finish of predecessor: LF = minimum LS of all successors - Total Float: TF = LS − ES = LF − EF Critical activities satisfy: ES = LS and EF = LF (Total Float = 0).

Heading

1. Network Fundamentals and Critical Path Concept

Examples

Problem

Example 1.1 — Network with Two Parallel Paths Consider a small renovation project with the following structure: - Activity A (Foundation prep): 5 days, no predecessor - Activity B (Structural frame): 8 days, starts after A - Activity C (Electrical rough-in): 3 days, starts after A - Activity D (MEP finishes): 4 days, starts after both B and C Determine the critical path and project duration.

Solution

Step 1: Identify all paths from start to finish. Path 1: A → B → D = 5 + 8 + 4 = 17 days Path 2: A → C → D = 5 + 3 + 4 = 12 days Step 2: The critical path is the longest: A → B → D = 17 days. Step 3: Project duration = 17 days. Step 4: Activity C has float = 17 − 12 = 5 days (can be delayed up to 5 days without affecting project). Answer: Critical path is A → B → D with duration 17 days. Activity C has 5 days of float.

Problem

Example 1.2 — Forward and Backward Pass (ES, EF, LS, LF) Given a sequence of activities: - Activity A: 4 days, starts at day 0 - Activity B: 6 days, starts after A - Activity C: 3 days, starts after B - Activity D: 2 days, starts after B (parallel with C) Project deadline: 13 days Calculate ES, EF, LS, LF for each activity.

Solution

FORWARD PASS (calculating ES and EF): Activity A: ES = 0, EF = 0 + 4 = 4 Activity B: ES = EF(A) = 4, EF = 4 + 6 = 10 Activity C: ES = EF(B) = 10, EF = 10 + 3 = 13 Activity D: ES = EF(B) = 10, EF = 10 + 2 = 12 Project finishes at max(EF of C, EF of D) = max(13, 12) = 13 days BACKWARD PASS (calculating LF and LS, working backward from day 13): Project LF = 13 Activity C: LF = 13, LS = 13 − 3 = 10 Activity D: LF = 13, LS = 13 − 2 = 11 Activity B: LF = minimum(LS of C, LS of D) = min(10, 11) = 10, LS = 10 − 6 = 4 Activity A: LF = LS(B) = 4, LS = 4 − 4 = 0 FLOAT CALCULATIONS (TF = LS − ES): Activity A: TF = 0 − 0 = 0 (critical) Activity B: TF = 4 − 4 = 0 (critical) Activity C: TF = 10 − 10 = 0 (critical) Activity D: TF = 11 − 10 = 1 day (can slip 1 day) Answer: Critical path is A → B → C = 13 days. Activity D has 1 day of float.

Key Points

  • The critical path is the LONGEST path through the network, not the shortest
  • Critical path length equals the minimum project duration
  • Activities on the critical path have zero total float and cannot be delayed
  • Forward pass: EF = ES + d, with ES being the maximum EF of predecessors
  • Backward pass: LS = LF − d, with LF being the minimum LS of successors
  • Total float represents how much slack an activity has before delaying the project
  • Multiple critical paths can exist, meaning multiple activities are time-critical simultaneously

Float (or slack) represents the amount of time an activity can be delayed without impacting the overall project duration. Understanding float is crucial for project managers in prioritizing resources and managing risk. There are two primary types of float: total float and free float. **Total Float (TF)** is the amount an activity can slip without delaying the project finish date. It is calculated as: TF = LS − ES = LF − EF Total float belongs to the project—if an activity with float is delayed by the full amount of its float, the float of subsequent activities is consumed. This is critical in scheduling decisions. **Free Float (FF)** is the amount an activity can slip without delaying any successor activity. Free float is a property of the individual activity and its immediate successors. An activity can use its free float without impacting dependent activities. FF = ES(successor) − EF(activity) **Interfering Float** represents the portion of total float that would delay successors if used. It is calculated as TF − FF. This distinction helps avoid cascading delays in the schedule. Activities are classified based on float: - **Critical activities**: TF = 0; no slack; any delay affects the project - **Subcritical activities**: TF > 0; have slack and some scheduling flexibility - **Independent activities**: FF = TF (can slip fully without affecting any successor) In Philippine construction practice, identifying float is essential for daily labor scheduling, equipment allocation (per NSCP 2015 guidelines on resource management), and managing the sequence of trades. Activities with substantial float should be scheduled to accommodate weather delays, material deliveries, and workforce availability in tropical climates. **Key Distinctions:** - Total float affects the PROJECT completion date - Free float affects only SUCCESSOR activities - Float diminishes as activities use their slack

Heading

2. Float Analysis and Schedule Slack

Examples

Problem

Example 2.1 — Total and Free Float Calculation A foundation activity has the following schedule parameters: - Early Start (ES) = 5 days - Early Finish (EF) = 12 days - Late Start (LS) = 8 days - Late Finish (LF) = 15 days Its successor activity (structural concrete) has ES = 15 days. Calculate total float, free float, and interfering float.

Solution

Step 1: Calculate Total Float. TF = LS − ES = 8 − 5 = 3 days Verification: TF = LF − EF = 15 − 12 = 3 days ✓ Step 2: Calculate Free Float. FF = ES(successor) − EF(activity) = 15 − 12 = 3 days Step 3: Calculate Interfering Float. Interfering Float = TF − FF = 3 − 3 = 0 days Interpretation: This activity has 3 days of total float. All 3 days can be used as free float (delaying the start by 3 days will not affect the successor). There is no interfering float, meaning the successor is not dependent on other activities, or the successor has identical slack. Answer: TF = 3 days, FF = 3 days, Interfering Float = 0 days.

Problem

Example 2.2 — Float Impact on Sequential Activities Consider an electrical installation sequence: - Activity E (conduit installation): ES = 10, EF = 18, LS = 12, LF = 20 - Activity F (wire pulling): ES = 18, EF = 25, LS = 20, LF = 27 - Activity G (breaker installation): ES = 25, EF = 28, LS = 27, LF = 30 Calculate the float for each activity and identify the impact of using E's float on activity F.

Solution

Step 1: Calculate Total Float for each activity. Activity E: TF = LS − ES = 12 − 10 = 2 days Activity F: TF = LS − ES = 20 − 18 = 2 days Activity G: TF = LS − ES = 27 − 25 = 2 days Step 2: Calculate Free Float for each activity. Activity E: FF = ES(F) − EF(E) = 18 − 18 = 0 days Activity F: FF = ES(G) − EF(F) = 25 − 25 = 0 days Activity G: FF = Project end − EF(G) (assume no successor) Step 3: Calculate Interfering Float. Activity E: Interfering = TF − FF = 2 − 0 = 2 days Activity F: Interfering = TF − FF = 2 − 0 = 2 days Step 4: Analyze the impact. If Activity E uses its 2 days of float (delaying from day 10 to day 12), its Early Finish becomes 20 days. This equals the Late Start of Activity F, consuming all of F's float. Activity F would then have zero free float. Answer: All activities have 2 days total float. Activity E has zero free float; using its float fully consumes F's free float. This is a case of sequential interfering float.

Key Points

  • Total Float (TF) = LS − ES = LF − EF; measures project-level slack
  • Free Float (FF) = ES(successor) − EF(activity); measures successor-level slack
  • Interfering Float = TF − FF; portion that would delay successors if consumed
  • Critical activities have TF = 0; any delay extends the project
  • Subcritical activities have TF > 0 and offer scheduling flexibility
  • Free float can be used without affecting dependent tasks
  • Activities with high float are lower priority for expediting efforts
  • In multi-path networks, float reductions on one path may shift criticality to another

While CPM assumes deterministic (fixed) activity durations, real construction projects involve uncertainty. PERT incorporates this uncertainty using three time estimates: optimistic (a), most likely (m), and pessimistic (b). This approach is particularly relevant in Philippine construction, where weather variability, supply chain uncertainties, and material sourcing (including importation) introduce schedule risk. **PERT Expected Duration and Variance:** The expected duration of an activity is calculated as a weighted average: t_e = (a + 4m + b) / 6 This formula weights the most likely estimate (m) four times relative to the optimistic and pessimistic estimates. This reflects the statistical principle that the most likely outcome (modal value) has greater influence than extreme values. The variance (measure of uncertainty) is calculated as: σ² = ((b − a) / 6)² The standard deviation is σ = √σ². This measures the spread of uncertainty; a larger variance indicates greater schedule risk. **Project Duration and Probability:** For the entire project, the expected duration is the sum of expected durations along the critical path: T_p = Σ t_e (for critical path activities) The project variance is the sum of variances of critical path activities: σ_p² = Σ σ² (for critical path activities) Project standard deviation: σ_p = √σ_p² Assuming the project duration follows a normal distribution (valid for projects with many activities), we can estimate the probability of completing by a target date using the Z-score: Z = (T_target − T_p) / σ_p Where T_target is the desired completion date. Using standard normal distribution tables, Z converts to a probability (typically between 0.5 and 0.99 for practical projects). **Practical Application in Philippine Construction:** In tropical climates, pessimistic estimates should account for: - Monsoon season delays (June to November for southwest monsoon; November to April for northeast monsoon) - Labor availability during harvest seasons in agricultural regions - Material delivery delays due to port congestion in archipelagic supply chains - Utility interruptions (water, power) during peak dry seasons Most likely durations should reflect normal Philippine construction productivity rates as established in historical project data. A probability of 0.85 to 0.90 is typically acceptable for milestone dates (per best practices in construction scheduling); critical deadlines may require 0.95 confidence.

Heading

3. PERT (Program Evaluation and Review Technique) — Probabilistic Scheduling

Examples

Problem

Example 3.1 — PERT Expected Duration and Variance A reinforced concrete floor pour has the following time estimates (in days): - Optimistic (a) = 3 days (ideal conditions, full crew, materials on-site) - Most Likely (m) = 5 days (normal weather, typical productivity) - Pessimistic (b) = 11 days (heavy rain, crew absences, supply delays) Calculate the expected duration and variance for this activity.

Solution

Step 1: Calculate Expected Duration. t_e = (a + 4m + b) / 6 t_e = (3 + 4(5) + 11) / 6 t_e = (3 + 20 + 11) / 6 t_e = 34 / 6 t_e = 5.67 days Step 2: Calculate Variance. σ² = ((b − a) / 6)² σ² = ((11 − 3) / 6)² σ² = (8 / 6)² σ² = (1.333)² σ² = 1.78 (day²) Step 3: Calculate Standard Deviation. σ = √σ² = √1.78 = 1.33 days Interpretation: The concrete floor pour is expected to take 5.67 days, with a standard deviation of 1.33 days. The range (±1σ) spans approximately 4.34 to 7.00 days, covering roughly 68% of possible outcomes (one standard deviation from mean in normal distribution). Answer: t_e = 5.67 days, σ² = 1.78 day², σ = 1.33 days.

Problem

Example 3.2 — Project Duration Probability A structural framing project has three critical path activities: - Activity A (Rebar placement): a = 6, m = 8, b = 16 days - Activity B (Concrete pour): a = 4, m = 6, b = 12 days - Activity C (Formwork removal): a = 2, m = 3, b = 8 days The client requires project completion within 18 days. Calculate: (1) Expected project duration (2) Project standard deviation (3) Probability of finishing within 18 days

Solution

Step 1: Calculate expected duration for each activity. Activity A: t_e = (6 + 4(8) + 16) / 6 = (6 + 32 + 16) / 6 = 54 / 6 = 9 days Activity B: t_e = (4 + 4(6) + 12) / 6 = (4 + 24 + 12) / 6 = 40 / 6 = 6.67 days Activity C: t_e = (2 + 4(3) + 8) / 6 = (2 + 12 + 8) / 6 = 22 / 6 = 3.67 days Step 2: Calculate project expected duration. T_p = Σ t_e = 9 + 6.67 + 3.67 = 19.34 days Step 3: Calculate variance for each activity. Activity A: σ_A² = ((16 − 6) / 6)² = (10/6)² = (1.667)² = 2.78 day² Activity B: σ_B² = ((12 − 4) / 6)² = (8/6)² = (1.333)² = 1.78 day² Activity C: σ_C² = ((8 − 2) / 6)² = (6/6)² = 1² = 1.00 day² Step 4: Calculate project variance and standard deviation. σ_p² = Σ σ² = 2.78 + 1.78 + 1.00 = 5.56 day² σ_p = √5.56 = 2.36 days Step 5: Calculate Z-score for T_target = 18 days. Z = (T_target − T_p) / σ_p Z = (18 − 19.34) / 2.36 Z = −1.34 / 2.36 Z = −0.568 Step 6: Determine probability from Z-score. From standard normal distribution table: Z = −0.568 corresponds to approximately 0.285 or 28.5% Interpretation: The expected project duration is 19.34 days with a standard deviation of 2.36 days. Completing within 18 days (below the expected duration) has a probability of only 28.5%, which is very risky. The client should either: - Extend the deadline to 19.34 days (50% confidence) or 21.70 days (84% confidence, i.e., T_p + 1σ_p) - Allocate resources for crashing critical activities Answer: (1) T_p = 19.34 days; (2) σ_p = 2.36 days; (3) P(finish ≤ 18 days) ≈ 28.5%

Problem

Example 3.3 — Confidence Level for Schedule Target Using the same project from Example 3.2 (T_p = 19.34 days, σ_p = 2.36 days), the project manager wants to plan a 90% confidence schedule (i.e., 90% probability of on-time completion). What target date should be communicated to the client?

Solution

Step 1: Identify Z-score for 90% confidence. From standard normal distribution table, P(Z ≤ z) = 0.90 corresponds to Z ≈ 1.28 Step 2: Rearrange the Z-score equation to solve for T_target. Z = (T_target − T_p) / σ_p T_target = T_p + Z × σ_p T_target = 19.34 + 1.28 × 2.36 T_target = 19.34 + 3.02 T_target = 22.36 days ≈ 22.4 days or 23 days (rounded to next workday) Interpretation: To achieve 90% confidence of on-time completion, the project should be scheduled for 23 days. This adds approximately 3.6 days (22.4 − 19.34) of buffer to the expected duration, representing reasonable risk mitigation in construction scheduling. Answer: Target date for 90% confidence = 22.4 days (or 23 days when rounded to workdays).

Key Points

  • PERT uses three estimates: optimistic (a), most likely (m), pessimistic (b)
  • Expected duration: t_e = (a + 4m + b) / 6; the coefficient 4 weights most likely value
  • Variance: σ² = ((b − a) / 6)²; larger variance = greater uncertainty
  • Project expected duration: T_p = Σ t_e along critical path activities
  • Project variance: σ_p² = Σ σ² for critical path activities only (non-critical paths do not contribute due to float)
  • Project standard deviation: σ_p = √σ_p²
  • Z-score: Z = (T_target − T_p) / σ_p for probability calculation
  • Normal distribution assumption requires multiple activities; valid for typical construction projects
  • Typical confidence levels: 0.85–0.90 for milestone dates; 0.95 for critical deadlines
  • In Philippine context, include seasonal weather, material sourcing delays, and regional labor availability in estimates

Project crashing is the process of reducing the project duration by allocating additional resources (typically labor and equipment) to critical path activities. This strategy is employed when: 1. **Contractual penalties** exist for late completion (liquidated damages per construction contracts) 2. **Opportunity costs** from delayed revenue or resource release exceed crashing costs 3. **External deadlines** are immovable (e.g., facility opening date, regulatory compliance deadline) 4. **Resource conflicts** require freeing equipment or labor for subsequent projects In Philippine construction context (aligned with NSCP 2015 project management guidelines), crashing decisions must consider: - Increased labor costs (overtime premiums: typically 25–50% of base rate) - Equipment mobilization and extended equipment rental costs - Subcontractor availability (particularly for specialized trades) - Weather windows in monsoon season (June–November Southwest; November–April Northeast) - Material availability and import lead times **Crashing Cost and Duration Trade-off:** Each activity has a normal (uncrashed) duration with normal cost, and a crash (minimum) duration with crash cost. The crashing cost per unit time is: Crash Cost Rate = (Crash Cost − Normal Cost) / (Normal Duration − Crash Duration) For example, if an activity normally takes 10 days at ₱100,000 but can be crashed to 7 days for ₱125,000: Crash Rate = (125,000 − 100,000) / (10 − 7) = 25,000 / 3 = ₱8,333.33 per day **Crashing Strategy:** 1. **Calculate crash rates** for all activities on the critical path 2. **Sort by crash rate** (lowest cost first) 3. **Crash activities one at a time**, starting with the lowest-cost option 4. **Recalculate the critical path** after each crash (sometimes non-critical paths become critical) 5. **Stop** when the target date is reached or when crashing becomes uneconomical **Multi-Path Crashing Consideration:** When multiple paths approach criticality, crashing must consider all simultaneous paths. Crashing an activity not on all critical paths provides no benefit if another path remains longer. **Practical Constraints:** - **Minimum duration limit**: Each activity has a physical minimum (cannot pour concrete instantaneously) - **Resource availability**: Additional labor/equipment may not be available - **Diminishing returns**: Beyond a certain point, more resources provide minimal productivity gain (e.g., more workers in a small space create congestion) - **Quality impact**: Excessive crashing may compromise workmanship and safety - **Weather dependency**: Weather-sensitive activities (excavation, formwork, exterior finishes) cannot be meaningfully crashed in monsoon season In Philippine practice, NSCP 2015 emphasizes safety and quality; crashing decisions should not compromise worker safety, environmental compliance, or final product quality. **Cost-Duration Optimization:** The optimal project duration balances: - **Direct costs** (materials, labor, equipment)—typically increase with crashing - **Indirect costs** (site management, supervision, utilities, insurance)—decrease with shorter duration - **Penalty costs** (liquidated damages)—decrease with earlier completion - **Premium costs** (incentives for early finish)—may justify crashing The optimal duration is where Total Cost = Direct + Indirect + Penalty is minimized.

Heading

4. Project Crashing and Schedule Optimization

Examples

Problem

Example 4.1 — Calculating Crash Cost Rate A structural steel erection activity has the following parameters: - Normal duration: 15 days - Normal cost: ₱450,000 - Crash (minimum) duration: 10 days - Crash cost: ₱600,000 Calculate the incremental cost per day of crashing this activity.

Solution

Step 1: Identify cost and duration parameters. Normal: 15 days, ₱450,000 Crash: 10 days, ₱600,000 Duration reduction possible: 15 − 10 = 5 days Step 2: Calculate crash cost rate. Crash Cost Rate = (Crash Cost − Normal Cost) / (Normal Duration − Crash Duration) Crash Cost Rate = (600,000 − 450,000) / (15 − 10) Crash Cost Rate = 150,000 / 5 Crash Cost Rate = ₱30,000 per day Interpretation: To accelerate this activity by 1 day, the project incurs an additional ₱30,000 in cost. Answer: Crash rate = ₱30,000 per day.

Problem

Example 4.2 — Multi-Activity Crashing Decision A project's critical path consists of three activities with the following crash rates and maximum crash days: Activity A: ₱15,000/day, can crash 4 days Activity B: ₱22,000/day, can crash 3 days Activity C: ₱18,000/day, can crash 5 days The current project duration is 30 days. The client offers a ₱50,000 bonus for each day completed early (up to 5 days early). Determine the optimal crashing strategy (how many days to crash and which activities).

Solution

Step 1: Organize activities by crash cost rate. 1st choice: Activity A at ₱15,000/day (lowest cost) 2nd choice: Activity C at ₱18,000/day 3rd choice: Activity B at ₱22,000/day Step 2: Analyze cost-benefit for each day of crashing. Bonus per day early = ₱50,000 Crash Day 1: Use Activity A at ₱15,000 Net benefit = ₱50,000 − ₱15,000 = ₱35,000 ✓ (beneficial) Crash Day 2: Use Activity A at ₱15,000 Net benefit = ₱50,000 − ₱15,000 = ₱35,000 ✓ Crash Day 3: Use Activity A at ₱15,000 Net benefit = ₱50,000 − ₱15,000 = ₱35,000 ✓ Crash Day 4: Use Activity A at ₱15,000 (last day for A) Net benefit = ₱50,000 − ₱15,000 = ₱35,000 ✓ Crash Day 5: Activity A is fully crashed (4 days). Next choice is Activity C at ₱18,000 Net benefit = ₱50,000 − ₱18,000 = ₱32,000 ✓ Crash Day 6 (if considered): Activity C at ₱18,000 Net benefit = ₱50,000 − ₱18,000 = ₱32,000; but bonus is limited to 5 days No 6th day bonus applies, so: Net benefit = ₱0 − ₱18,000 = −₱18,000 ✗ (not beneficial) Step 3: Determine optimal crashing. Crash Activity A fully (4 days): Cost = 4 × ₱15,000 = ₱60,000 Crash Activity C by 1 day: Cost = 1 × ₱18,000 = ₱18,000 Total crash days = 5 (maximum bonus eligibility) Total crashing cost = ₱78,000 Total bonus earned = 5 × ₱50,000 = ₱250,000 Net benefit = ₱250,000 − ₱78,000 = ₱172,000 Step 4: Final schedule. New project duration = 30 − 5 = 25 days Answer: Crash Activity A by 4 days (to minimum) and Activity C by 1 day. New duration = 25 days. Net project benefit = ₱172,000. This assumes Activity A can actually crash 4 days without becoming infeasible or compromising quality.

Problem

Example 4.3 — Crashing with Critical Path Shift A project has two paths: - Path 1 (critical): A(8) → B(6) → D(5) = 19 days - Path 2: C(7) → D(5) = 12 days Crash rates: - Activity A: ₱12,000/day, can crash 3 days - Activity B: ₱10,000/day, can crash 2 days - Activity C: ₱8,000/day, can crash 3 days The project deadline is 15 days. Determine the minimum cost to meet the deadline.

Solution

Step 1: Current critical path. Path 1: A(8) + B(6) + D(5) = 19 days (critical) Path 2: C(7) + D(5) = 12 days Project duration = 19 days; need to reduce by 19 − 15 = 4 days. Step 2: Plan initial crashes (Path 1 activities only). Since Path 2 has 7 days of float (19 − 12), we can ignore C for now and focus on Path 1. Sort Path 1 activities by crash rate: 1. Activity B: ₱10,000/day (can crash 2 days) 2. Activity A: ₱12,000/day (can crash 3 days) Step 3: Crash sequentially. Crash B by 2 days: Cost = 2 × ₱10,000 = ₱20,000 New Path 1 duration: 8 + 4 + 5 = 17 days Still need to reduce by 17 − 15 = 2 more days Crash A by 2 days: Cost = 2 × ₱12,000 = ₱24,000 New Path 1 duration: 6 + 4 + 5 = 15 days ✓ New Path 2 duration: 7 + 5 = 12 days Step 4: Check for new critical path. Path 1: 15 days Path 2: 12 days Path 1 remains critical at 15 days (matches deadline). Step 5: Verify float on Path 2. Path 2 still has float = 15 − 12 = 3 days (no further crashing needed on Path 2). Step 6: Total cost. Crashing cost = ₱20,000 + ₱24,000 = ₱44,000 Answer: Crash Activity B by 2 days and Activity A by 2 days. Total minimum cost = ₱44,000. New project duration = 15 days. Path 1 remains critical; Path 2 has 3 days of remaining float.

Key Points

  • Crashing is accelerating critical path activities by adding resources (labor, equipment)
  • Crash cost rate = (Crash cost − Normal cost) / (Normal duration − Crash duration)
  • Crash the lowest-cost activities first to minimize total project cost increase
  • Recalculate critical path after each crash; non-critical paths may become critical
  • Multiple critical paths require simultaneous crashing; crashing only one path provides no benefit
  • Each activity has a minimum (crash) duration limit
  • Indirect costs (supervision, site overhead) decrease with shorter schedules; direct costs increase
  • Optimal duration balances direct, indirect, and penalty/incentive costs
  • Weather-dependent activities in Philippine climate cannot be meaningfully crashed during monsoon season
  • Safety and quality must not be compromised; crashing decisions must comply with NSCP 2015 requirements
  • Resource availability (labor, equipment, subcontractor capacity) limits crashing potential

The PRC Civil Engineer Licensure Examination typically includes 3–5 questions on CPM/PERT, often combined with cost estimation, resource management, or risk assessment. Questions follow predictable patterns and test specific competencies. Understanding common pitfalls and examination strategy significantly improves performance. **Typical Question Formats:** 1. **Critical Path Identification**: Given a network (text, table, or diagram), identify activities, calculate ES/EF/LS/LF, determine critical path and project duration. This is the most frequent question type (60% of CPM questions). 2. **Float Calculation**: Calculate total float, free float, or interfering float for specific activities. Often combined with criticality questions. 3. **PERT Probability**: Given three time estimates, calculate expected duration, variance, project duration, and probability of meeting a deadline. Requires familiarity with normal distribution and Z-scores. 4. **Crashing/Optimization**: Given normal and crash parameters, determine which activities to crash and calculate new project cost/duration. May include cost-benefit analysis. 5. **Schedule Compression**: Identify which activities can be executed in parallel (concurrency) to reduce duration without adding crashing costs. Tests logical sequencing understanding. **Common Mistakes to Avoid:** 1. **Critical Path = Shortest Path**: The longest path is critical, not shortest. Candidates sometimes calculate all paths and select the minimum—incorrect. Verify: "Longest path determines minimum completion time." 2. **Confusing Float Types**: - Total Float = Project level (affects deadline) - Free Float = Activity level (affects successors only) - Candidates often interchange these, leading to wrong conclusions about activity flexibility. 3. **PERT Weighting Errors**: - Formula: t_e = (a + 4m + b) / 6, not (a + m + b) / 3 (which is simple average) - The most likely (m) is weighted 4× for a reason: statistical beta distribution - Common error: Using simple average (a + m + b) / 3 instead of weighted formula 4. **Variance Only from Critical Path**: - Project variance = Σσ² for ONLY critical path activities - Non-critical activities do NOT contribute to project duration variance (they have float) - Candidates sometimes sum variance of all activities—incorrect 5. **Z-Score Misinterpretation**: - Positive Z means target is AFTER expected completion (high confidence) - Negative Z means target is BEFORE expected completion (low confidence) - Z = +1.28 gives 90% probability; Z = +1.96 gives 97.5%; Z = +2.33 gives 99% 6. **Crashing Cost-Benefit Backward**: - Crash rate is incremental cost per day - Benefit per day crashed = (Penalty avoided + Bonus earned) − (Crash cost) - Candidates often subtract crash cost from project cost (static), not from benefit 7. **Missing Network Logic**: - Finish-to-Start (FS) is standard but lag/lead times change calculations - If "Activity C starts 2 days after B finishes," adjust ES(C) = EF(B) + 2 - Some exams include these; ensure you account for lags 8. **Rounding Errors**: - PERT variance: [(b − a) / 6]² must be squared correctly - Project SD: √(Σσ²) not Σ√σ² - Many candidates drop the square root or misapply it 9. **Forgetting Network Boundary Conditions**: - Project ES = 0 (unless stated otherwise) - Project LF = max(EF) of all ending activities (for unconstrained projects) - Some problems specify an external deadline; LF becomes that deadline 10. **Duplicate Paths Logic**: - If two activities merge (e.g., A→D, B→D), D's ES = max(EF of A, EF of B) - Backward: D's LF predecessors: LF(A) and LF(B) are both = LS(D) + 0 (for immediate predecessor) - Missing the "maximum" or "minimum" operator causes cascading errors **Time Management in Exam:** - **First read**: 2 minutes—understand the network structure, identify nodes/activities, note which are critical (sometimes highlighted) - **Forward pass**: 3–4 minutes—calculate ES and EF systematically; write neatly in table format - **Backward pass**: 3–4 minutes—start from project end, work backward; double-check against EF values - **Float/Path identification**: 1–2 minutes—identify critical path (TF = 0) and note float values - **If PERT**: 3–5 minutes—calculate t_e and σ² per activity; sum for project; calculate Z and probability - **Verification**: 1–2 minutes—spot-check calculations; verify TF = LS − ES = LF − EF **Effective Study Techniques:** 1. **Tabular Method**: Organize all calculations in a clear table with columns: Activity | Duration | ES | EF | LS | LF | TF. This prevents errors and aids quick reference. 2. **Draw the Network**: Even if provided, redraw it to ensure you understand the logic. Hand-drawn networks reveal sequencing errors that are invisible in printed form. 3. **Work Backward from End**: Some candidates find backward pass confusing; always start from the project end and systematically move backward. Use a second color for clarity. 4. **Use Normal Distribution Tables**: Memorize key Z-scores: Z = 1.00 (84%), Z = 1.28 (90%), Z = 1.645 (95%), Z = 1.96 (97.5%), Z = 2.33 (99%). This accelerates probability questions. 5. **Check Multiple Paths**: In complex networks, always identify and calculate ALL paths, not just the obvious one. Some exams include trick paths that are longer than expected. 6. **Practice Crashing Multiple Times**: Crashing is the hardest CPM topic. Practice the sort-by-cost method repeatedly; it becomes intuitive with repetition. **Exam-Day Tips:** - **Show all work**: Partial credit is awarded for correct methodology, even if final answer is wrong due to arithmetic - **Label units**: Write "days" or "₱" clearly; ambiguity costs points - **State assumptions**: If the problem is ambiguous (e.g., "finish by Day 20"), state your interpretation clearly - **Cross-check**: After completing, verify that Project Duration = max(EF of all ending activities) and that at least one path exists with TF = 0 - **If stuck on one question**: Move on, attempt other questions, and return if time permits

Heading

5. Board Examination Strategy and Common Pitfalls

Examples

Problem

Example 5.1 — Complete CPM Exam-Style Problem A residential building project has the following activities and relationships: - A (Site prep): 5 days, no predecessor - B (Foundation): 8 days, after A - C (Structural frame): 12 days, after B - D (Roof): 6 days, after C - E (MEP rough-in): 7 days, after C - F (MEP inspection): 2 days, after E - G (Interior finishes): 10 days, after D and E - H (Final inspection): 1 day, after F and G Calculate ES, EF, LS, LF, and TF for all activities. Identify the critical path and project duration. Calculate float for Activity E.

Solution

Step 1: FORWARD PASS (Calculate ES and EF) Activity A: ES = 0, EF = 0 + 5 = 5 Activity B: ES = 5, EF = 5 + 8 = 13 Activity C: ES = 13, EF = 13 + 12 = 25 Activity D: ES = 25, EF = 25 + 6 = 31 Activity E: ES = 25, EF = 25 + 7 = 32 Activity F: ES = 32, EF = 32 + 2 = 34 Activity G: ES = max(31, 32) = 32, EF = 32 + 10 = 42 Activity H: ES = max(34, 42) = 42, EF = 42 + 1 = 43 Project Duration = 43 days Step 2: BACKWARD PASS (Calculate LF and LS) Start from the end: Activity H: LF = 43, LS = 43 − 1 = 42 Activity G: LF = 42, LS = 42 − 10 = 32 Activity F: LF = min(LS of H) = 42, LS = 42 − 2 = 40 Activity E: LF = min(LS of F, LS of G) = min(40, 32) = 32, LS = 32 − 7 = 25 Activity D: LF = min(LS of G) = 32, LS = 32 − 6 = 26 Activity C: LF = min(LS of D, LS of E) = min(26, 25) = 25, LS = 25 − 12 = 13 Activity B: LF = min(LS of C) = 13, LS = 13 − 8 = 5 Activity A: LF = min(LS of B) = 5, LS = 5 − 5 = 0 Step 3: TOTAL FLOAT CALCULATION (TF = LS − ES) Activity A: TF = 0 − 0 = 0 (CRITICAL) Activity B: TF = 5 − 5 = 0 (CRITICAL) Activity C: TF = 13 − 13 = 0 (CRITICAL) Activity D: TF = 26 − 25 = 1 day Activity E: TF = 25 − 25 = 0 (CRITICAL) Activity F: TF = 40 − 32 = 8 days Activity G: TF = 32 − 32 = 0 (CRITICAL) Activity H: TF = 42 − 42 = 0 (CRITICAL) Step 4: IDENTIFY CRITICAL PATH Critical path (all TF = 0): A → B → C → E → G → H = 5 + 8 + 12 + 7 + 10 + 1 = 43 days (Note: Activity F is not on critical path; Activity D has 1 day float) Answer: Project Duration = 43 days Critical Path: A → B → C → E → G → H Activity E: TF = 0 (on critical path) Non-critical activities: D (1 day), F (8 days) Summary Table: Activity | Duration | ES | EF | LS | LF | TF | Critical A | 5 | 0 | 5 | 0 | 5 | 0 | Yes B | 8 | 5 | 13 | 5 | 13 | 0 | Yes C | 12 | 13 | 25 | 13 | 25 | 0 | Yes D | 6 | 25 | 31 | 26 | 32 | 1 | No E | 7 | 25 | 32 | 25 | 32 | 0 | Yes F | 2 | 32 | 34 | 40 | 42 | 8 | No G | 10 | 32 | 42 | 32 | 42 | 0 | Yes H | 1 | 42 | 43 | 42 | 43 | 0 | Yes

Problem

Example 5.2 — PERT with Probability (Exam Question) A concrete finish activity on a high-rise building has three time estimates (in days): - Optimistic: 8 days (perfect conditions) - Most Likely: 12 days (normal operations) - Pessimistic: 22 days (severe delays) This activity is on the critical path. The critical path, excluding this activity, has a total variance of 6 (day²). The client deadline is Day 50, and the project's expected duration (excluding this activity) is 38 days. (a) Calculate the expected duration and variance of the concrete finish activity. (b) Calculate the project's expected duration and standard deviation. (c) What is the probability of meeting the Day 50 deadline?

Solution

Step 1: Calculate expected duration of concrete finish activity. t_e = (a + 4m + b) / 6 t_e = (8 + 4(12) + 22) / 6 t_e = (8 + 48 + 22) / 6 t_e = 78 / 6 t_e = 13 days Step 2: Calculate variance of concrete finish activity. σ² = ((b − a) / 6)² σ² = ((22 − 8) / 6)² σ² = (14 / 6)² σ² = (2.333)² σ² = 5.44 day² Step 3: Calculate project expected duration. T_p = (Rest of critical path) + (Concrete finish) T_p = 38 + 13 T_p = 51 days Step 4: Calculate project variance. σ_p² = (Variance of rest) + (Variance of concrete finish) σ_p² = 6 + 5.44 σ_p² = 11.44 day² Step 5: Calculate project standard deviation. σ_p = √11.44 σ_p = 3.38 days Step 6: Calculate Z-score for deadline of Day 50. Z = (T_target − T_p) / σ_p Z = (50 − 51) / 3.38 Z = −1 / 3.38 Z = −0.296 Step 7: Determine probability from Z-score. From standard normal distribution table: Z = −0.296 corresponds to P ≈ 0.383 or 38.3% Interpretation: The expected project duration is 51 days, but the deadline is Day 50 (1 day early). The probability of meeting this deadline is only 38.3%, which is less than 50%. This is a risky schedule; the project is more likely to be late than early. Answer: (a) Concrete finish: t_e = 13 days, σ² = 5.44 day² (b) Project: T_p = 51 days, σ_p = 3.38 days (c) P(finish by Day 50) ≈ 38.3% Recommendation: Either extend the deadline to 51 days (50% confidence) or 54.4 days (84% confidence = T_p + 1σ_p), or allocate resources to crash the critical path to save at least 1 day.

Key Points

  • Critical path = LONGEST path (not shortest); its length = minimum project duration
  • Forward pass: EF = ES + d, with ES = max(EF of predecessors)
  • Backward pass: LS = LF − d, with LF = min(LS of successors)
  • Total float (TF) affects PROJECT; free float (FF) affects SUCCESSORS
  • PERT: t_e = (a + 4m + b) / 6 (weighted average, not simple mean)
  • PERT variance: σ² = ((b − a) / 6)²; project variance = Σσ² for critical path only
  • Z-score: Z = (T_target − T_project) / σ_project for probability of on-time completion
  • Crash rate = (Crash cost − Normal cost) / (Normal − Crash duration)
  • Crash lowest-cost activities first; recalculate critical path after each crash
  • Multiple critical paths may exist; crashing must address all simultaneous paths
  • Common error: confusing float types, PERT weighting, variance summation, Z-interpretation
  • Exam strategy: tabular layout, draw network, check all paths, show all work
  • Verify: TF = LS − ES = LF − EF; Project duration = max(EF) and min path TF = 0
Loading diagram…
Loading diagram…
Loading diagram…
Loading diagram…

Ready to practise for the CELE 2026?

Super Tutor's AI review plan adapts to your weak areas and builds a weekly practice schedule around your target CELE exam date.