Requirements checklist

System Logistics RFQ Data Sheet for warehouse automation evaluation

A compact checklist for teams that already know their loads, flows, interfaces and acceptance targets. Use it to structure System Logistics RFQs without empty rate claims. The sheet exists so Warehouse Operations, capital procurement, IT/OT integration and maintenance can review one evidence record before comparing conveyor, AS/RS, AGV/AMR or WCS options.

System Logistics expects unknowns to be labeled as unknowns. A missing peak-window duration or an unnamed PLC owner is more useful than a polished slide that hides the operating boundary. When brownfield cutover limits apply, capture the protected outbound waves and the hours available for commissioning so design rate discussions stay attached to real site constraints.

Structured RFQ data

Capture the operating boundary before vendor comparisons

System Logistics treats missing fields as blockers for meaningful throughput or interface discussion. Complete what you know; mark unknowns explicitly rather than inventing placeholder rates.

Load and flow
Load unitDimensions, weight bands, overhang, pallet/tote/carton/pouch type
SKU profileActive SKU count, velocity classes, seasonal SKUs, slotting constraints
Order profileOrders/hour, lines/order, multi-line share, wave or waveless release
Peak windowDesign rate, peak factor, duration, recovery objective after backlog
Interfaces and site
Host systemsWMS, WCS, WES, PLC, fleet manager owners and protocols
Site constraintsFloor quality, clear heights, fire zones, power, brownfield cutover limits
Acceptance evidenceFAT/SAT cases, alarm ownership, spares, maintenance access routes
Evidence checklist

Documents System Logistics expects alongside the RFQ sheet

Checklist items are planning aids. They do not certify compliance and should be adapted to local regulations and corporate standards. Framework names used elsewhere on the site identify review topics; they are not product certificates for a specific System Logistics model.

How System Logistics uses the completed sheet

Completed fields become the baseline for throughput validation, interface FAT scripts and SAT exception cases. If the SKU velocity mix or dock availability changes after design freeze, update the sheet before reopening rate claims. System Logistics will not treat a brochure carton-per-hour figure as acceptance evidence when the RFQ omits replenishment, accumulation or recovery assumptions.

For multi-building networks, complete one sheet per operating profile rather than averaging e-commerce and grocery constraints into a single generic request. That keeps shuttle selectivity, sorter recirculation and WMS allocation rules from being evaluated against the wrong peak factor. Buffer occupancy targets and goods-to-person presentation rates should also be stated per profile so WES wave release logic is not sized for an imaginary average day.

Send your System Logistics RFQ Data Sheet inputs

Share the completed fields or schedule a boundary review with engineering so evaluation starts from operating data.

Submit RFQ inputs