DevShift Labs · Operational digital twin
DevShift RelayDisruption control room for a multi-site fulfillment network
Relay mirrors a nine-facility fulfillment network as a live twin. Pick an incident, read the damage across facilities, lanes, inventory and orders, then generate recovery plans that are built from real allocations and real routes — never from a stored answer.
Fixture6c1835cb5c4437aa
Interactive twin
The WebGL control deck loads in the browser. The network snapshot below stays readable without it.
What the deck does
Diagnose
Every incident is replayed from one immutable fixture, so the facilities, lanes, inventory and order book you inspect are the same ones the planner solves against.
Compare
Four recovery postures are solved independently — deadline sprint, weighted fair-share, clean corridor and headroom guard — and ranked against your service, cost and carbon weights.
Commit
Preview runs against a cloned state and never touches the canonical record. Commit moves inventory, books shipments and shifts the twin. Reset restores the exact starting state.
Incident library
Four independent scenarios. State never leaks between them: selecting one rebuilds the twin from the fixture.
INC-01Fulfillment hub outage
Central Hub drops out of the network for the whole planning horizon. Every unit it was holding for the north-west corridor has to be re-sourced from the remaining hubs before the critical batches breach their deadlines.
INC-02Directed transport-lane closure
The West Transfer to Northwest Demand lane is closed in one direction. The corridor has to be rebuilt through East Transfer, which is slower, dearer and capped at a lower per-tick capacity.
INC-03Regional demand spike and kit shortage
South-east vision-kit demand rises sharply at the same moment as hub stock of that family is capped. Demand now exceeds the units physically held in the network, so recovery becomes an allocation decision rather than a routing one.
SBXSeeded sandbox
A reproducible synthetic disruption derived from a seed string. The same seed always closes the same lane and inflates the same regional demand, so a plan can be replayed, copied and handed to another operator unchanged.
Static network snapshot
Server-rendered from the immutable fixture, so the network is readable with JavaScript switched off.
| Facility | Role | Region | Throughput | Stock |
|---|---|---|---|---|
| North Hub | Fulfillment hub | north | 32 u | 238 u |
| Central Hub | Fulfillment hub | central | 40 u | 335 u |
| South Hub | Fulfillment hub | south | 34 u | 295 u |
| West Transfer | Transfer | west | 48 u | — |
| East Transfer | Transfer | east | 44 u | — |
| Northwest Demand | Demand region | northwest | — | — |
| Northeast Demand | Demand region | northeast | — | — |
| Southwest Demand | Demand region | southwest | — | — |
| Southeast Demand | Demand region | southeast | — | — |
| Lane | Capacity | Transit | Unit cost | Unit carbon |
|---|---|---|---|---|
| North HubtoWest Transfer | 26 u | 45 min | $1.40 | 0.42 kg |
| North HubtoEast Transfer | 22 u | 60 min | $1.70 | 0.48 kg |
| Central HubtoWest Transfer | 30 u | 30 min | $1.10 | 0.31 kg |
| Central HubtoEast Transfer | 30 u | 30 min | $1.10 | 0.31 kg |
| South HubtoWest Transfer | 20 u | 60 min | $1.80 | 0.52 kg |
| South HubtoEast Transfer | 28 u | 45 min | $1.50 | 0.44 kg |
| West TransfertoNorthwest Demand | 24 u | 30 min | $0.90 | 0.22 kg |
| West TransfertoNortheast Demand | 18 u | 75 min | $1.90 | 0.57 kg |
| West TransfertoSouthwest Demand | 25 u | 30 min | $0.80 | 0.20 kg |
| West TransfertoSoutheast Demand | 19 u | 75 min | $2.00 | 0.59 kg |
| East TransfertoNorthwest Demand | 18 u | 75 min | $2.00 | 0.60 kg |
| East TransfertoNortheast Demand | 25 u | 30 min | $0.80 | 0.20 kg |
| East TransfertoSouthwest Demand | 19 u | 75 min | $1.90 | 0.56 kg |
| East TransfertoSoutheast Demand | 24 u | 30 min | $0.90 | 0.23 kg |