Skip to content
Octopus Twin
Logistics & WarehousingGen 3 · Digital Twin

Warehouse Twin

A multi-customer high-bay warehouse sized from a client site sketch: 75 m wide, 26 rack rows × 39 bays × 6 levels, 13 reach-truck aisles, eight docks and six customers across lithium batteries, food and light industry. A discrete-event simulation runs a naive and an optimised WMS twin in lockstep — slotting, dispatch, vision counts, audit and safety.

Warehouse Twin
usable pallet positions
11,550
reach-truck aisles
13
virtual cameras for vision tracking
112
tests + browser checks
53 + 48

The challenge

Warehouse operators change slotting rules and truck dispatch on intuition. Nobody can show the effect on lead time and empty travel — or prove where a missing pallet went.

What we built

  1. Every coordinate modelled: rack rows, aisles, docks, staging lanes, swept paths without in-place pivots
  2. Two DES twins share the same demand: first-feasible vs scored slotting, FIFO vs Hungarian dispatch
  3. Segregated lithium zone with hard rules for levels, capacity and food buffer
  4. Vision counts, discrepancy workflow and a SHA-256 hash-chained audit log
  5. Patrol robot rounds, UWB proximity stops and a safety rule engine

Outcome in the twin

Strategy effects show up as measured fleet KPIs — lead time, cycles per busy hour, empty travel, aisle changes — and every pallet has a reconstructable journey from dock to slot to truck.

Technology

Discrete-event simulationA* with time-window reservationsHungarian assignmentReact Three FiberEN + 中文

About this build

Fictional warehouse and customers; every page carries a simulated-data badge.

Have a system you want to see, question or rehearse?

Tell us about the site, the process and the decision. We will come back with what a twin could answer, which data it needs, and how fast a prototype can be in front of your team.