Compact requirements checklist

BALYO RFQ Data Sheet

Capture the minimum evidence needed to compare warehouse robotics concepts without hiding route, traffic, interface or acceptance assumptions.

Warehouse robotics RFQ worksheet beside an autonomous forklift route map
Input register

Mark each field measured, assumed or open

A blank field is not automatically a blocker. It is an action with an owner and a date, which is more useful than filling the RFQ with an unverified number.

GroupRequired inputUnit / evidenceStatus
LoadMass, dimensions and load centerkg and mm; representative load drawingMeasured / assumed / open
Pickup and drop tolerancemm; pallet or carrier conditionMeasured / assumed / open
Load exceptionsDamaged, shifted, absent or rejected loadProcedure owner
FlowBaseline movement rateLoads/hour by routeObserved period
Peak caseLoads/hour and peak durationOrder or production profile
Buffer occupancyUsable positions and release logicNormal and blocked states
RouteClear width, turns and slopesmm, degrees and floor surveyDrawing revision
Shared trafficCrossings, manual trucks, pedestriansTraffic plan
ChargingLocation, access and operating ruleDuty-cycle assumption
InterfacesTask source and acknowledgementWMS/WCS/WES message contractSystem owner
Field devicesPLC, doors, conveyors and signalsI/O and state diagram
Exception recoveryTimeout, retry, cancel and restartAuthority matrix
Evidence checklist

Close the RFQ around verification and ownership

This checklist does not assert certification. It identifies documents and review boundaries that may be required for the selected model, market and site.

□

Responsibility matrix

WMS, WCS/WES, PLC, fleet management, vehicle, infrastructure and site operations owners are named for normal and fault states.

□

Safety evidence boundary

Applicable ISO 3691-4 and ISO 13849-1 considerations, risk reduction, scanner zones and validation responsibilities are reviewed for the actual configuration.

□

FAT protocol

Emulated systems, representative loads, test preconditions, expected results, logs, exclusions and issue closure are documented.

□

SAT protocol

Site routes, traffic, interfaces, loads, peak case, degraded behavior and restart authority are observed in the installed environment.

□

Brownfield release plan

Work zones, available routes, fallback movement, commissioning windows, training and authorization protect the live warehouse during rollout.

□

Handover package

Open items, as-built records, diagnostics, maintenance, critical spares, recovery procedures and support boundaries have named recipients.

Performance boundary

Fleet quantity, throughput, availability and charging demand cannot be confirmed from a generic checklist. They require a bounded model using route length, load profile, speeds and waits, traffic interaction, task logic, battery strategy, buffer occupancy and exception frequency. Compare both ideal flow and a defined disturbed case.

Selection dimensions without naming vendors

When comparing concepts, score the same dimensions: rated load with load center; aisle / clear width in mm; design and peak loads/hour with SKU or order profile; interface cycle time and exception timeout ownership; system availability assumptions at vehicle, fleet and end-to-end levels; and whether the path is greenfield optimization or brownfield phasing. Prefer the concept that closes the highest-risk dimension with measurable evidence, not the one with the broadest marketing claim.

Verification path available on request: representative load trial on a mapped route segment, controls-message emulation for timeout and duplicate-call cases, and joint review of the FAT/SAT exclusion list with the site operations owner.

Send the completed RFQ basis

Identify confidential attachments before transmission and request an agreed secure channel when needed.