User Manual
Help Center/User Manual/Run a WES demo: start a fresh round and walk the three storylines

Run a WES demo: start a fresh round and walk the three storylines

Last updated 2026-11-01

The WES-DEMO warehouse shows AMRs, a conveyor and a put wall working on the real orchestration chain. Start a fresh round in about five minutes, then run the three storylines in any order.

What you are showing#

WES-DEMO is a dedicated demo warehouse inside your Demo organization. Its equipment — two virtual AMRs, one virtual conveyor line and one 12-slot put wall — runs on the same task release, dispatch and device-job chain as real equipment. Nothing on screen is a special demo mode: tasks, step logs and KPIs are the real ones. The talking point to repeat: "same system, same contract — when real equipment arrives, only the adapter changes." You can open the device registry live and show simulated and real devices sharing one table and the same capability declarations.

Before the customer arrives: start a fresh round (about 5 minutes)#

  1. Run the reset tool (or ask your admin to): it opens a new round — fresh receiving into new LPNs and two new demo orders. Old rounds stay untouched and archived; nothing is deleted.
  2. Check the four devices read Idle on the device list. If one still shows a leftover fault injection from a previous session, the reset tool clears it — run it once more and confirm.
  3. Open the control tower for WES-DEMO and confirm it shows only the current round: new orders, new LPNs, devices idle. That is your starting screen.

Storyline 1 — AMR goods-to-person (the main act)#

Use the round’s GTP demo order. Release its pick task (the release gate lets tasks out in small batches — the "drip" rhythm you can point at), and the orchestrator sends a carry job to a virtual AMR. On the control tower you watch the AMR travel to the shelf, bring it to the GTP station and report "arrived". Pick at the station (or let the simulated operator confirm), complete the task, and finish on the KPI panel: the same numbers a real warehouse would produce. If a step feels slow, say it plainly: orchestration reacts in minutes, not seconds — that is the honest, designed pace.

Storyline 2 — Conveyor and put wall sorting#

Use the round’s SORT demo order. Parcels ride the virtual conveyor past the scan point and are diverted toward the put wall; the target slot lights up, the operator confirms, and the receipt comes back. Then show the full-slot moment: mark one slot full, send the next parcel to it, and the line reports blocked while the orchestrator suggests moving the parcel to a free slot. Send it to the suggested slot and the flow recovers — that suggestion is the system doing the thinking, not a person watching a screen.

Storyline 3 — A fault happens: rerouting and manual fallback#

While an AMR is working, inject a fault on it (device page → simulation parameters → set it offline). Jobs that have not started are moved to the second AMR; a job already under way is flagged for a person, an exception entry appears and supervisors are notified. Then flip the warehouse’s "pause automation" switch: orchestration stops handing out device jobs and work falls back to the normal manual flow — the warehouse never stops, it just goes manual. Turn the switch off to close the storyline. Keep the timing honest: rerouting is driven by a once-a-minute pump, so say "the orchestration reacts within a minute or so", and use the manual "advance now" action if you want it to happen on cue during the demo.

After every demo, run the reset tool once. The next audience gets a clean starting screen, and yesterday’s rounds stay archived for the record — nothing to clean up by hand.