RFQ clarity for loads, flows, interfaces and acceptance evidence. Open RFQ Data Sheet
Compact requirements checklist

Daifuku RFQ Data Sheet

A useful warehouse automation RFQ states what moves, how often each route is demanded, where constraints occur, which control layer owns each decision and how performance will be accepted.

Requirements ledger

Capture facts, assumptions and open questions separately

Use one row per operating case when loads or routes differ materially. Attach source files, timestamps and owners so changes can be traced during design review.

Input group Minimum information Why it changes the concept Preferred evidence
Load unit Length, width, height, mass, underside, orientation and stability Controls carrier interface, payload margin, pickup tolerance and safe transfer Dimensioned drawing, weight range, representative samples
Material flow Origins, destinations, moves by interval, SKU/order profile, replenishment, peak duration and cutoff Determines mission demand, travel, queueing, buffer occupancy and equipment quantity Timestamped transaction extract and route matrix
Site geometry Clear aisle width, turns, doors, crossings, safety zones, fire routes and maintenance areas Defines feasible paths, speed restrictions, traffic rules and intervention access Current CAD, measured survey, marked photographs
Control interfaces WMS/WCS/WES/PLC/FMS ownership, messages, acknowledgements, timeouts, alarms and network policy Prevents duplicated decisions, silent failures and unresolved exception states Responsibility matrix, interface specification, sequence diagrams
Acceptance Design and peak rates, transaction definition, availability boundary, test duration, fault cases and evidence owner Turns commercial expectations into repeatable FAT and SAT decisions Approved protocol, scenario data, result and deviation template

Do not compress uncertainty into one capacity number

Where input is unknown, record a range and name the validation action. A 30-minute peak has a different effect from a full-shift peak. A nominal tote size does not represent damaged, overfilled or mixed containers. A map without pedestrian activity and temporary staging does not represent the live route. Making uncertainty explicit protects both selection and later acceptance.

Submission check

Before issuing the RFQ

01

Transaction is defined

The rate states exactly what completes a move or order line, including pickup and drop confirmation.

02

Peak has a window

Demand identifies duration, recurrence, replenishment overlap and whether backlog is allowed.

03

Buffers are located

Every station and lane has a capacity, blocking rule and response when full or unavailable.

04

Interfaces have owners

Commands, data state, retries, alarms and manual decisions belong to named systems and teams.

05

Safety paths are visible

Pedestrian crossings, restricted areas, maintenance access and intervention points appear on the layout.

06

Failures are test cases

Blocked routes, host silence, network loss, lost load and disabled stations have expected outcomes.

Reference and certification boundaries

If the project cites ISO 12100, ISO 13849-1 or a regional machinery regulation, specify whether each item is a design reference, product requirement, site integration obligation or requested third-party certificate. Do not use a framework name as a substitute for model-specific documentation. This site does not claim product certifications that are not evidenced for a specific model.

For brownfield deployments, include cutover zones, allowed downtime, rollback steps, inventory reconciliation and temporary manual flow. For expansion, include the next expected destinations, workload range and network growth so the initial phase does not create avoidable constraints.

Reproducible acceptance example

Freeze the route map, equipment configuration, interface version and test dataset before a run. Execute a named transaction mix for a stated duration, record completed and failed moves, queue time, buffer occupancy, mean time to repair and system availability percentage, then repeat the same scenario after each material change. A useful example protocol might require a 120-minute nominal run at a stated order-lines-per-hour mix, followed by blocked-path, host-timeout and unavailable-station scenarios with measured recovery in minutes; the numbers are test conditions to approve, not Daifuku performance claims.

Send a compact, traceable requirements pack

Attach the route matrix, load evidence, site drawing, interface responsibility and draft acceptance scenarios. Mark unknowns clearly; they are inputs to resolve, not gaps to hide.

Submit project requirements