The 1,850-Activity Water Plant Schedule
Northgate Utilities is expanding a 40 ML/d water treatment plant over 14 months. The contractor's first draft schedule contains 1,850 activities, most at 8-hour task level, on a single 7-day calendar. The owner's project manager insists the schedule will not be accepted unless every pipe and valve is a separate activity, arguing that a lower-detail plan hides problems. The contractor's scheduler has only 0.6 FTE available for monthly updates. The project has 12 subcontractors, three long-lead package plants, and a 21-day commissioning window. The project controls lead must respond before the schedule review meeting.
1. How should the controls lead respond to the owner's demand for maximum detail, and what level of detail should the schedule actually carry?
Read the worked answer
Accept the transparency objective, not the 1,850-activity structure. Level of detail should be driven by update cycle, control need, risk, and available maintenance effort, not by a preference for granularity. With 0.6 FTE and 12 subcontractors, 1,850 activities cannot be statused credibly each month; the schedule will decay and the owner will get less transparency, not more.
Propose a control-level integrated schedule of roughly 400 to 600 activities, with every package plant, long-lead procurement, commissioning milestone, and interface represented, plus owner review and approval activities. Put pipe-and-valve detail into working schedules or fragnets used for look-aheads and dispute analysis, and add a drill-down coding structure so any summary activity can be traced to supporting detail. Set a documented activity-detail rule: control-level activities should be measurable within one update period, typically 2 to 4 weeks, and shorter only near commissioning. Offer monthly detail extracts for the commissioning window. This meets the owner's need to see substance while keeping the integrated model maintainable.
2. Which planning decisions and schedule architecture must be fixed before development starts, and why do they matter on this project?
Read the worked answer
Five decisions should be fixed and recorded in a schedule basis document. First, calendars: a 5-day office and engineering calendar, a 6-day construction calendar, and a 7-day commissioning calendar, with rules for converting float between them; otherwise weekend work is invisible and float is misstated. Second, WBS and coding: area, system, phase, responsible subcontractor, and work package, so reporting can cut the data by both parties' needs. Third, phasing and handover strategy: three package plants and a 21-day commissioning window drive the sequence, so commissioning and turnover activities must be planned now, not appended later. Fourth, long-lead procurement logic: enquiry, award, fabrication, factory acceptance test, delivery, and installation must be linked to installation with realistic lags. Fifth, the update and change-control regime: data date rules, progress measurement, and who approves logic changes. Without these, the activity-detail debate will recur because there is no agreed standard for what an activity represents.