Negative Float in a 21-Day Substation Outage
During development of a 21-day substation outage schedule, the scheduler links 'Replace breaker' (10 days) to 'Energize and test' (3 days) with a start-to-start lag of 10 days. 'Energize and test' also carries a start-no-earlier-than constraint of Day 15. All activities use a 5-day, 8-hour calendar, but the utility's outage window is 21 consecutive calendar days and the testing crew works six days a week. The schedule calculates 9 days of negative float on energization, and the contractor proposes deleting the constraint to fix the float. The owner's engineer must decide how to correct the model before the outage window is finalized.
1. Diagnose the causes of the nine days of negative float and identify the modelling errors.
Read the worked answer
Negative float means the forward pass cannot satisfy a constraint or deadline. Here three causes compound. The start-no-earlier-than Day 15 is a date constraint on an activity whose predecessor logic and calendar already place it later; the schedule is being asked to satisfy both a date and a relationship, and the constraint consumes float rather than creating logic.
The start-to-start lag of 10 days is also suspect. It lets energization start 10 days after breaker replacement starts, not after replacement finishes, so if the breaker work extends, testing can begin before the physical handover. That can create a false early start and hide the real sequence. The calendar is the largest distortion: a 21-calendar-day outage contains about 15 working days on a 5-day calendar, while the testing crew actually works six days a week. Using a 5-day calendar for testing overstates testing duration and understates available window. The float is therefore largely an artefact of constraint plus calendar mismatch, not a genuine nine-day problem.
2. What corrections should the owner's engineer require, and what is the likely effect on the forecast completion?
Read the worked answer
Require the constraint to be removed unless it represents a genuine external commitment. If it does, document it and show its effect separately. Replace the start-to-start lag with a relationship that reflects when energization can physically begin; if pre-testing can overlap, use a lag tied to a defined portion of the breaker work and justify it. Correct the calendars: model the outage window as a 6-day or 7-day calendar for testing and energization, and keep the 5-day calendar only for office activities. Then rerun the schedule and compare the longest path with the outage window.
The correction may remove the negative float by extending the forecast, or reveal that the 21-day window is still feasible with weekend testing. Deleting the constraint alone is not a fix; it may simply hide the conflict. The engineer should require a time-scaled logic diagram and a calendar-day float report before accepting the window.