Shutdown Window Planner

Sequence the steps of a planned shutdown or tie-in, track the running clock, add a contingency buffer, and see whether it fits inside the maximum allowable out-of-service window. Runs entirely offline; everything persists in this browser via localStorage.

Use limits: The window is a hard constraint set by whatever actually governs — customers' tolerable outage, hours of storage in the tanks, a boil-water threshold, a permitted lane-closure or night-work window, a contractual milestone. Name it, and be honest about the durations: the unknown condition of the existing valve or pipe is the classic overrun, which is what the buffer is for. This plans a serial sequence; you can't backfill before you test.
Window

The overrun reserve. 15–25% is common; more for an old valve of unknown condition.

Shutdown Steps (in sequence)
StepDurationUnitHold pointStartsEnds

Mark inspection, sample-result, or pressure-test steps as hold points — their clock can't be compressed by adding manpower.

How the Numbers Are Derived

The clock and the go/no-go

Steps run in sequence, so the planned duration is just their sum, and each step's start and end clock times accumulate from the planned start. The committed duration is planned × (1 + buffer%). Slack is window − committed: positive is go, negative is the amount you'd blow the window by. The timeline draws the steps end to end with the buffer appended and the window line marked — if the bars cross into the shaded zone past the line, the plan doesn't fit.

Field notes

References

  1. The utility's / owner's shutdown and outage procedures, and the customer-notification or boil-water policy that sets the allowable duration (governing).
  2. Companion field tools: pipe flushing and chlorine dosing for the return-to-service steps.