Throughput stated with SKU mix, order lines, replenishment, accumulation and peak window length.
Translate throughput, storage density, WMS/WCS/PLC handshakes and acceptance criteria into reviewable engineering requirements before capital commits. Swisslog keeps evaluation tied to the material-flow map your distribution center actually runs—not brochure rates detached from SKU mix and peak windows.
Throughput stated with SKU mix, order lines, replenishment, accumulation and peak window length.
WMS, WCS, WES, PLC and fleet ownership for commands, timeouts, alarms and recovery.
Factory and site acceptance cases tied to installed geometry and live load assumptions.
Diagnostics, critical spares and maintenance access visible before operational handover.
Keep load profile, controls boundary and site constraints in one review record instead of scattered slide decks.
| Load unit | Pallet, tote, carton or shuttle-compatible dimensions, weight bands and overhang rules |
|---|---|
| SKU / order mix | Active SKU depth, lines per order, multi-line share and velocity classes |
| Peak window | Design rate, peak factor, duration and recovery time after backlog |
| Host interfaces | WMS, WCS, WES, PLC and fleet-management handshake states, including OPC UA or fieldbus paths where the site already uses them |
|---|---|
| Interface cycle time | Target handshake and exception timeout bands stated in seconds for each critical confirmation; open timeouts remain engineering risks |
| Exception ownership | Retries, alarm routing and who may authorize restart after a protective stop or blocked destination |
| Orchestration scope | Wave release, buffer occupancy and divert confirmation responsibilities across material flow controller layers |
| Site constraints | Floor quality, aisle / clear width in mm, power, fire zones and brownfield cutover windows |
|---|---|
| Availability basis | System availability measured at subsystem and end-to-end levels; mean time to repair tied to spare staging and isolation rules |
| Acceptance evidence | FAT/SAT cases, alarm ownership, spare parts and maintenance access |
| Fallback states | Manual bypass, zone isolation and rollback triggers during staged go-live |
Product conversations stay attached to storage density, shuttle or crane duty cycles, robotics paths and the control layer that must own each handshake.
Responsibility matrices define who owns commands, confirmations, retries, buffers and exception recovery across host and PLC layers. Swisslog treats orchestration as an engineering boundary with FAT/SAT evidence—not a standalone software brochure.

Selectivity, fire access, replenishment and crane or shuttle duty cycle reviewed against SKU velocity bands.
Review catalog →
Cube utilization gains stay paired with maintenance aisles, recovery paths and expansion sequencing.
Review catalog →
Fleet traffic rules, charging and blocked-destination logic stay attached to the same interface matrix.
Review catalog →High SKU depth and short cutoffs stress induction balance, sorter recirculation and WCS release logic during peak hours.
Store-order sequencing, mixed tote and pallet flows and temperature zones change buffer sizing and exception routing.
Line-side deliveries need takt alignment, load identity and a defined response when a workcell cannot receive material.
Traceability and controlled access must stay attached to physical handoffs, quarantine locations and recovery records.
Sensor behavior, maintenance access and duty cycles are reviewed at the stated temperature band before SAT.
Brownfield conveyors, shared docks and phased cutover windows define which automation layers can go live first.
Generic brochure rates stall decisions. Share the operating boundary so controls, mechanical and site teams can review the same record.
Contact engineering