Skip to main content
Domain 02 · Logistics & fulfilment

Two Vendors Blame Each Other for Every Corridor Deadlock.

Logistics is not a routing problem. It is a political problem at fleet scale — one the warehouse runs on, between vendors who don’t share intent and a clock that does not negotiate. The runtime is what stops the floor lead from being the arbitrator.

01 — Environment

Throughput Collapses at the Edges, Not the Centre.

Steady state is solved. Edge events are not: a lane closes, a pick face empties, a cross-dock window shortens, a priority shipment lands ninety minutes before cut-off. Local optimisation accumulates into global congestion.

FloorWarehouse · yard · hubMixed fleets. Humans, AMRs, AGVs, forklifts in the same lanes.
OperatorsPickers · dispatch · floor leadsConstantly shifting priority. Tolerant of slowness, intolerant of confusion.
TempoCut-off windows · minutesTruck departures dictate the clock; everything else follows.
MemoryCorridor history · congestion heatWhere deadlocks form, when, and why. Inherited by every new shift.
02 — Fleet coordination

Intent Broadcast. Conflict Arbitration. Hand-Off.

Multi-platform fleets share a corridor only if their plans are negotiable. The runtime gives every unit a fleet-aware planning surface — and a coordinator that resolves conflicts before they become deadlocks.

14Active units
03Vendor platforms
+22%Cycle-time vs vendor only
0Deadlocks last 24h
03 — Operational signals

Anomalies the Runtime Watches For.

Vendor-A Logs Blame Vendor-B. Vendor-B Logs Blame Vendor-A.

Six weeks of contract renegotiation. Six weeks of floor leads walking corridor 14 every shift.

Corridor · 14

Cut-Off Window Shortened by 12 Min.

Re-rank, hand off, reserve dock-door — before the floor lead walks the aisle. After is too late.

Wave · 02 · 14:38

WMS Says Bay 14. Bay 14 Is Empty.

Picker re-shelved at bay 17 last shift. The robot picks nothing, times out, and the order misses its wave.

Bay · 14

Dock Door 4 Closed for 18 Min — Not on Schedule.

Truck reversed in early. Three units are pre-staged for a dock that’s blocked. Nobody told the fleet.

14:52
“We added the second vendor to ease congestion. We got more deadlocks. Now the floor leads spend the shift refereeing.”
Operations director3PL · UK
“We’re hitting cut-off on labour, not on the fleet. The platform doesn’t know which orders matter to the truck schedule.”
Dispatch leadDistribution · NL
03b — Economics

What the Dock Clock Actually Costs.

Missed cut-off · per wave €400–€2,500 Plus contractual penalty plus retailer-side perception cost.
Corridor deadlock · resolution 14–42 min Until a human walks the lane and physically untangles intent.
Vendor blame loop 6–12 wk Average contractual standoff before a shared coordinator is forced in.
Floor-lead supervision 25–40% Of supervisor time on shift, spent arbitrating across vendor platforms.
04 — Operational scenario

A Priority Shipment Is Added Mid-Shift.

Scenario

Late High-Priority Order.

A high-priority order enters the queue ninety minutes before cut-off. Half its SKUs are at the far aisle. Two of the closest units are mid-pick on lower-priority work.

STEP 01Re-rank tasks across the fleet against the new deadline and dependency graph.
STEP 02Hand off in-flight work to nearby units without idling the line.
STEP 03Reserve corridor and dock-door capacity ahead of arrival.
STEP 04Surface the trade-off to the floor manager with alternatives ranked.
05 — Capabilities

What the Layer Adds to a Logistics Fleet.

/ 01

Fleet Awareness

Continuous picture of every unit, its task, its load, its intent — across the floor.

/ 02

Priority Arbitration

Live arbitration of conflicting priorities — orders, exceptions, hand-offs, deadlines.

/ 03

Congestion Resolution

Resolve corridor and intersection congestion before it queues, not after.

/ 04

WMS Integration

Bidirectional reasoning with the WMS — fleet feedback influences the order plan.

Logistics · Outcome

A fleet that reasons, not a swarm that moves.