Start-up

This tool builds a full start-up timetable by working backward and forward from a single anchor point: your target Spinning start time. Every other milestone — DOW, AFT, DHYD, the TFE units, BSS, WWT, SCS ignition, FSO, and each utility — is calculated as a fixed offset from that anchor or from another milestone in the chain, using the durations set in Advanced settings.

Sequence offsets

Each offset (e.g. "AFT after DOW", "LS before DOW") is a duration, not a fixed clock time. Change Spinning start and the whole chain shifts with it. Change an offset in Advanced settings and every downstream step recalculates.

Include / exclude

Utilities, SCS ignition, and FSO start can each be left out of a plan using their own "Include" checkbox if they don't apply this time. Excluding an item only removes it from the timetable — it doesn't break the calculation chain, so anything that depends on its timing (for example, NG follows SCS ignition) still lines up correctly even when that item itself is hidden.

Custom start (override)

If the calculated time for a utility, SCS ignition, or FSO doesn't match what's actually planned or has already happened, tick "Custom start" next to it and enter the real date and time. The rest of the plan keeps using the calculated chain — only that one item is pinned. Overridden entries are marked "(custom)" in the timetable.

Custom blocks vs overrides

Overrides adjust an existing calculated event. Custom blocks (further down this page) add brand-new entries to the timetable that aren't part of the calculation at all — useful for site-specific steps this planner doesn't otherwise model.

Saving

"Save plan" writes everything on this page — inputs, advanced offsets, overrides, and custom blocks — to a JSON file you can reopen later with "Open plan".

This tool proposes exact process-stop timings around a target reference time. From your tank snapshot (V-217 latex, R-slurry, BSS) and the operating rates at that snapshot, it works out when each tank reaches its target, then finds the nearest exact stop before and after your reference — the closest points where the numbers land on a whole reactor batch — since latex is only produced in complete batches.

Drain to zero vs Hold and restart

Drain to zero runs tanks down to empty (or your target levels) for a full cold shutdown. Hold levels and restart stops Spinning while keeping inventory in the tanks, then restarts from AFT later without repeating the full cold start-up sequence — set the restart time and conditions in the "Hold and restart" section, which only appears when this plan type is selected.

Rate changes

Add step changes to the AFT, TFE, or Spinning consumption rate at any point after the snapshot. Each change applies from its own time onward, so you can model a planned rate reduction partway through the stop instead of assuming a constant rate throughout.

Reactor state

Each reactor's availability, state, next discharge time, and cycle duration feed into how much latex and R-slurry keep arriving after the snapshot, which shifts the tank balance and the proposed stop (or restart) times.

Tank balance

The "Tank balance at each process stop" table shows opening, added/generated, consumed, and closing volumes for every tank at each proposed stop, plus when a tank is projected to run empty or reach its target level.

Custom blocks

Add your own entries to the timetable for anything this planner doesn't calculate automatically.

Saving

"Save plan" writes everything on this page to a JSON file you can reopen later with "Open plan".