Service workstreams are specified as reviewable boundaries: what is modeled for inventory cube utilization and selectivity, what is tested for peak order lines per hour, 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 selective rack, shuttle systems and AS/RS controls.
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 for a named legal entity.
| Service package | Primary engineering question | Minimum inputs | Evidence class |
|---|---|---|---|
| Density engineering | Can inventory cube utilization rise without erasing fire, maintenance and recovery access? | SKU velocity, rack load rating, aisle widths, expansion intent | Concept boundary report |
| 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 |
| Controls responsibility matrix | Who owns command, confirmation, timeout, alarm and restart for each handshake? | WMS/WCS/WES/PLC message list | Responsibility matrix + FAT script |
| 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 agreed exposure? | Asset list, duty cycle, local skill model | Serviceability and spares matrix |
The sequence keeps density slogans and peak-rate slogans from being debated without owners, buffers and recovery paths.
Capture load units, SKU velocity, order-line distribution, peak window, temperature zones and the longest tolerable interruption for each critical storage path. Mark unknowns as assumptions with owners before Steel King freezes bay geometry or interface definitions.
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 and residual capacity.
Document WMS, WCS, WES, PLC and crane or shuttle controller responsibilities for release, routing, confirmations, alarms and restart authorization. Centralized orchestration and modular aisle controls can coexist if handshake boundaries are explicit.
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, including OPC UA or fieldbus bridge behavior where applicable.
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 that erase system availability metrics.
Peak throughput view: Maximize order lines per hour under a defined design condition with tight buffers.
Resilient flow view: Preserve recovery paths, redundancy and stable output when divert accuracy, host timeouts or door cycles disturb the wave.
Steel King service packages require both numbers: the design rate and the degradation path. Choosing only the headline rate without buffer occupancy and exception ownership is treated as incomplete intake.
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.