Technical service specifications

Swisslog services structured around throughput, interfaces and cutover evidence

Service workstreams are specified as reviewable boundaries: what is modeled, what is tested, what is accepted on site and what remains owned by operations after handover. Response objectives stay project-specific because travel, spare access and isolation rules change the achievable recovery path across automated storage, shuttle systems and control layers.

Capability matrix

Service packages mapped to operating questions

Each package names the primary deliverable, the minimum input set and the evidence class it can support. Planning values are not published as certified performance claims.

Service package Primary engineering question Minimum inputs Evidence class
Controls responsibility matrix Who owns command, confirmation, timeout, alarm and restart for each handshake? WMS/WCS/WES/PLC/fleet message list Responsibility matrix + FAT script
Throughput validation Does design rate hold across the sustained peak with stated mix and buffers? Order profile, replenishment, peak duration, divert/merge logic Scenario and sensitivity record
Density & selectivity review Can inventory cube utilization rise without erasing fire, maintenance and recovery access? SKU velocity, load rating, aisle widths, expansion intent Concept boundary report
Phased project delivery How does live fulfillment stay protected during staged release? Zone map, fallback states, commissioning windows Cutover and rollback plan
Lifecycle serviceability What spares, access and diagnostics keep mean time to repair within the agreed exposure? Asset list, duty cycle, local skill model Serviceability and spares matrix
Methodology

Five steps from operating data to acceptance gates

  1. Frame the operating profile

    Capture load units, SKU velocity, order-line distribution, peak window, temperature zones and the longest tolerable interruption for each critical flow path. Mark unknowns as assumptions with owners before Swisslog freezes interface definitions.

  2. Bound storage and automation concepts

    Relate inventory cube utilization to selectivity, rack or shuttle geometry, fire routes and recovery access. Separate greenfield freedom from brownfield aisle, floor and column constraints that limit staged cutover.

  3. Map controls ownership

    Document WMS, WCS, WES, PLC and fleet or AS/RS controller responsibilities for release, routing, confirmations, alarms and restart authorization. Swisslog treats missing owners as open engineering risks, not schedule footnotes.

  4. Run scenario and FAT evidence

    Exercise baseline, peak and disturbance cases against the agreed message list. Record expected versus observed states for FAT-relevant interfaces before equipment leaves the controlled test environment.

  5. Close SAT and service handover

    Repeat applicable checks with installed geometry and real loads. Transfer diagnostics, critical spares guidance and recovery procedures with clear ownership after go-live so operations can quarantine a failed zone without improvised workarounds.

Service boundaries Swisslog will state up front

  • Emulation or digital twin results are planning evidence; they do not replace installed-site SAT with real loads.
  • Mean time to repair targets require spare staging, access paths and isolation authority—travel time alone is not a recovery plan.
  • OPC UA, fieldbus or host message coverage is limited to the agreed interface list; undocumented handshakes stay open risks.
  • Greenfield sequencing assumptions do not automatically apply to brownfield cutover windows that protect live fulfillment.
Request a scoped service review

Send the data that defines available and accepted

Include the operating calendar, storage concept, interface list and the acceptance questions that must be closed before cutover. Assumptions can remain provisional if they are labeled.

Open the service brief