NivaarExam PrepOfficial exam papers ↗

16-Civ-B8 Management of Construction · December 2019

Question 1 of 6: Scheduling — PERT expected duration, critical path and total floats

Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)

Notes on this paper

Paper format. National Exams, December 2019 — 16-Civ-B8, Management of Construction. Three hours, closed book, one of two approved calculators (Casio or Sharp). Six questions of equal value; any five constitute a complete paper and only the first five appearing in the answer book are marked. All six are worked here, because the set is a study resource rather than a sitting.

Reference texts. Hendrickson, Project Management for Construction, 2nd ed. (network scheduling, PERT, project control); Halpin & Senior, Construction Management, 4th ed. (precedence networks with lags, estimating, tendering, safety); RSMeans, Building Construction Cost Data (crew composition, daily output, masonry lines); Fraser et al., Global Engineering Economics, 5th Canadian ed. (present worth, annual worth, benefit–cost analysis of public projects); CCDC 2 (2020) Stipulated Price Contract with the CCDC 220/221 bond forms, and CCDC 23 A Guide to Calling Bids and Awarding Contracts (tendering practice); the Society of Construction Law Delay and Disruption Protocol, 2nd ed., and AACE International RP 29R-03 (forensic schedule analysis); Hinze, Construction Safety, 2nd ed., with the WorkSafeBC Occupational Health and Safety Regulation Part 20 (Construction) and Ontario O. Reg. 213/91.

Question 1: Scheduling — PERT expected duration, critical path and total floats (20 marks)

Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.

(a) PERT expected completion time

Given. Six tasks whose expected durations and duration variances are already computed and tabulated, with the predecessor list defining the logic.

Given data — PERT task list
TaskPredecessorsExpected duration $t_e$ (days)Variance $\sigma^2$ (days2)
Anone3025
BA4064
CA6081
DB259
EB, C4536
FD, E209

Find. The expected completion time of the whole project, that is the earliest finish of the terminal task F.

A30 dvar 25B40 dvar 64C60 dvar 81D25 dvar 9E45 dvar 36F20 dvar 9Critical path A–C–E–F, expected duration 155 days
Figure 1.1 — PERT network for the six tasks, drawn in activity-on-node form from the predecessor column. The critical chain A–C–E–F is shown in red.

Approach. Draw the logic implied by the predecessor column, run a forward pass to obtain each task's earliest start and earliest finish, and read the project's expected duration off the terminal task; then confirm the answer by enumerating the three complete chains and use the variances on the governing chain to attach a confidence statement to the date.

  1. Establish the logic from the predecessor column. A is the only task with no predecessor, so it starts the project. B and C both wait on A; D waits on B alone; E is a merge point waiting on both B and C; F is a second merge point waiting on both D and E. Nothing succeeds F, so F terminates the project. This is the network drawn in Figure 1.1.
  2. Run the forward pass. For every task the earliest start is the latest earliest-finish among its predecessors, and the earliest finish follows by adding the expected duration:

    $$ES_j=\max_{i\,\in\,\text{pred}(j)}\left(EF_i\right),\qquad EF_j=ES_j+t_{e,j}$$

    Working left to right, A runs 0–30. B and C both start at day 30 and finish at days 70 and 90 respectively. D follows B alone and runs 70–95. E is held by the later of its two predecessors, and since C finishes at 90 against B's 70, E starts at day 90 and runs to day 135. F is held by the later of D (day 95) and E (day 135), so it starts at day 135 and finishes at day 155.

    Forward pass
    Task$t_e$ (d)ES (d)EF (d)Governing predecessor
    A30030—
    B403070A
    C603090A
    D257095B
    E4590135C (90 > 70)
    F20135155E (135 > 95)
  3. Read the expected completion time. The project ends when its terminal task ends, so

    $$T_e=EF_F=\boxed{155\ \text{days}}$$

  4. Confirm by enumerating the complete chains. Three chains run from A to F. Their lengths are $30+40+25+20=115$ days for A–B–D–F, $30+40+45+20=135$ days for A–B–E–F, and $30+60+45+20=155$ days for A–C–E–F. The longest is A–C–E–F at 155 days, which agrees with the forward pass and identifies the critical chain. Because every link here is a plain finish-to-start with no lag, this sum check is valid; it would not be on the lagged network of part (b).
  5. Attach the variance the question supplies. The paper gives duration variances as well as expected durations, which is what makes this a PERT problem rather than a plain CPM one. Variances add along a chain of independent tasks, so on the critical chain

    $$\sigma_T^2=\sum_{\text{critical}}\sigma_i^2=25+81+36+9=151\ \text{days}^2,\qquad \sigma_T=\sqrt{151}=12.29\ \text{days}$$

    The expected duration is therefore a 50 % date, not a promise. Treating the sum of four independent durations as approximately normal by the central limit theorem, the probability of finishing by any date $T$ is $\Phi\!\left[(T-T_e)/\sigma_T\right]$, which gives 65.8 % by day 160, 88.8 % by day 170 and 97.9 % by day 180. Conversely a date the planner could commit to with 90 % confidence is

    $$T_{90}=T_e+z_{0.90}\,\sigma_T=155+1.2816\times12.29=170.7\approx 171\ \text{days}$$

Check: the PERT date is optimistic, and by a knowable amount. The near-critical chain A–B–E–F is 135 days long with a variance of 134 days2 ($\sigma=11.58$ days), so it has only twenty days of slack against a standard deviation of nearly twelve. The probability that it stays inside 155 days is about 95.8 %, so the probability that both chains do is lower than the 50 % the critical chain alone suggests. This is the classical PERT merge-event bias: the calculation ignores the parallel chains that can overtake the critical one. Where a defensible completion probability matters, a Monte Carlo simulation over the whole network should replace the single-chain normal approximation. The 155-day answer above is the one the question asks for and is boxed accordingly.

Final results — Question 1(a)
QuantityResult
Expected completion time155 days
Critical chainA → C → E → F (30 + 60 + 45 + 20 = 155 d)
Variance / standard deviation of that chain151 days2 / 12.29 days
Next-longest chainA → B → E → F, 135 days (20 days of slack)
90 % confidence completion date171 days

(b) Critical path, total floats and the effect of delaying H

Given. The precedence network printed on page 2, comprising twelve activities with the durations shown in brackets and two lagged links.

Given data — precedence network read from the printed diagram
ActivityDuration (days)Predecessor link(s)
A2— (start)
B4A, FS 0
C3A, FS 0
D5B, SS 2
E4C, FS 0
F8C, FS 0
G2D, FS 0
H4E, FS 0
I4G, FS 0
J7G, FS 0
K4H FS 0; F FS 3
L2I, J, K, all FS 0

Find. The critical path and the project duration, the total float of every activity, and the change in project duration caused by a six-day delay to activity H.

[Figure not reproduced: Figure 1.2 — the printed precedence network redrawn, with each activity's total float shown beneath its box and the critical path A–C–F–K–L in red. Note that only two links carry lags: SS = 2 from B to D and FS = 3 from F to K. See the official exam paper.]

Approach. Run a forward pass in which a finish-to-start link drives the successor from its predecessor's earliest finish while the start-to-start link drives it from the predecessor's earliest start; run the matching backward pass on latest starts; take total float as the difference; then re-run the forward pass with the delay imposed to measure its effect rather than assuming it.

  1. Set the driving rule for each link type. With $L$ the lag, a finish-to-start and a start-to-start link impose respectively

    $$ES_j\ \ge\ EF_i+L_{ij}\quad\text{(FS)},\qquad ES_j\ \ge\ ES_i+L_{ij}\quad\text{(SS)}$$

    and each activity takes the largest of the demands made on it, $ES_j=\max(\cdot)$, with $EF_j=ES_j+D_j$. The single SS link is what makes this network more than an exercise in addition: D does not wait for B to finish, only for B to have been under way two days.

  2. Forward pass. A starts at day 0 and finishes at 2. B and C both follow A finish-to-start and so start at day 2, finishing at days 6 and 5. D is released by the start-to-start link at $ES_B+2=4$ and runs 4–9 — two days before B has finished, which is the whole point of the lag. E and F both follow C and start at day 5, finishing at 9 and 13. G follows D and runs 9–11; H follows E and runs 9–13; I and J both follow G, running 11–15 and 11–18. K is the interesting merge: H offers $EF_H=13$ while F offers $EF_F+3=16$, so the lagged link governs and K runs 16–20. L is held by the latest of I (15), J (18) and K (20), so it runs 20–22.

    $$T=EF_L=\boxed{22\ \text{days}}$$

  3. Backward pass. Fixing $LF_L=T=22$ and working right to left, each activity's latest start is the smallest demand its successors make. A finish-to-start successor requires $LS_i\le LS_j-L_{ij}-D_i$, whereas a start-to-start successor constrains only the predecessor's start, $LS_i\le LS_j-L_{ij}$. Applying these gives the schedule below, and the pass closes correctly with $LS_A=0$ — the standard self-check that the two passes are consistent.
  4. Compute total and free float. Total float is the slack an activity has against the project completion date, $TF=LS-ES=LF-EF$; free float is the slack it can use without disturbing any successor's earliest start, $FF=\min_j\left(ES_j-L_{ij}\right)-EF_i$ over its finish-to-start successors.
    Complete schedule — forward pass, backward pass and floats (days)
    ActivityDurationESEFLSLFTotal floatFree float
    A2020200
    B4264820
    C3252500
    D54961120
    E45981230
    F851351300
    G2911111320
    H4913121633
    I41115162055
    J71118132022
    K41620162000
    L22022202200
  5. Identify the critical path. The activities with zero total float are A, C, F, K and L, and they form a connected chain from the start to the finish, so

    $$\text{critical path}=\boxed{\text{A}\rightarrow\text{C}\rightarrow\text{F}\rightarrow\text{K}\rightarrow\text{L},\ \ T=22\ \text{days}}$$

    Walk it link by link rather than adding durations: the five critical durations sum to $2+3+8+4+2=19$ days, three days short of the answer, and the missing three days are exactly the FS = 3 lag on F → K. On any network carrying lags the familiar “critical durations must sum to the project duration” check is invalid, and a candidate who applies it here will conclude, wrongly, that the pass contains an error.

  6. Measure the effect of delaying H by six days. H carries three days of total float, so the general rule

    $$\Delta T=\max\left(0,\ \text{delay}-TF\right)=\max(0,\ 6-3)=3\ \text{days}$$

    predicts a three-day extension. Re-running the forward pass confirms it: pushing H out to 15–19 makes H, not the lagged F link, the governing predecessor of K at day 19, so K runs 19–23 and L runs 23–25.

    $$T'=\boxed{25\ \text{days}\quad(\text{a 3-day extension})}$$

    The critical path swings away from F and now runs A → C → E → H → K → L, whose durations under the delay sum to 25 days with no lag left on the path.

  7. Show that the usual ambiguity collapses here. “Delaying activity H by 6 days” can mean that H starts six days late or that H takes six days longer. Because H's only successor link is a plain finish-to-start to K, both readings push $EF_H$ from day 13 to day 19 and both give 25 days. The two readings would diverge only if H fed its successor through a start-to-start link, in which case a duration extension would be absorbed entirely. It is worth saying so explicitly rather than quietly picking one meaning.
SS = 2FS = 3A2 dTF = 0B4 dTF = 5D5 dTF = 5G2 dTF = 5I4 dTF = 8J7 dTF = 5C3 dTF = 0E4 dTF = 0H10 dTF = 0F8 dTF = 3K4 dTF = 0L2 dTF = 0With H delayed 6 days the critical path swings to A–C–E–H–K–L and the project runs 25 days
Figure 1.3 — the same network with H extended to ten days. The critical path has moved to A–C–E–H–K–L, F now carries three days of float, and the project runs 25 days.
Final results — Question 1(b)
QuantityResult
Project duration22 days
Critical pathA → C → F → K → L (19 days of work plus the 3-day FS lag)
Activities with zero total floatA, C, F, K, L
Total floats (days)A 0, B 2, C 0, D 2, E 3, F 0, G 2, H 3, I 5, J 2, K 0, L 0
Free floats (days)H 3, I 5, J 2; zero for every other activity
Effect of delaying H by 6 daysProject extends by 3 days, 22 → 25 days
Critical path after that delayA → C → E → H → K → L
← Paper overview