NETWORK OPERATIONS / 01

Supply Chain
Network Control Tower.

Recover the network.
Not just the first bottleneck.

Loading experiment…

01 / EXPLORE THE NETWORK

One disruption. Five responses.

Operating scenario

Deterministic reference · same arrivals and original commitments · full nine-day horizon

DETERMINISTIC REFERENCE

Simulation day 5

FIFO processing. Port release and DC delivery may happen on the same day. Capacities are containers per day.

Port DC No-action total

End-of-day containers waiting · Day 2–4: reduced port capacity · Day 5–6: intervention window.

02 / COMPARE THE OPTIONS

500 PAIRED TRIALS

The same demand and capacity shocks are applied to every option. Values show P10 / median / P90 across simulations.

Response	Missed commitments containers	Peak DC backlog containers	Queue recovery simulation day

DECISION INSIGHT

03 / FOLLOW THE EVIDENCE

Due dates are fixed at arrival + 1 day; an intervention never rewrites the promise.

04 / KNOW THE LIMITS

EYESTERION is fictional. These are simulated operations, not live shipments or calibrated forecasts.

Model, uncertainty & assumptions

60 arrivals per day for six days; nine-day horizon.
Port and DC base capacity: 80/day. Disrupted port: 40/day on days 2–4.
Selected nodes receive 110/day capacity on days 5–6.
Independent uniform daily variations: arrivals ±10; each node capacity ±8. Scenarios share the same draws.
Recovery is the first permanently queue-free day from day 5; >9 means outside the horizon.
On-time delivery is measured per container, not order-level OTIF. No transport time, stock, partial deliveries or monetary optimization.
P10–P90 is an 80% simulation interval, not a guarantee. Parameters require real-world calibration.

Inspect daily flow and container delivery ledger

Day	Arrivals	Port released	Port waiting	DC delivered	DC waiting

Container	Arrived	Due	Port released	Delivered	Commitment