Compact requirements checklist

Hikrobot RFQ Data Sheet for warehouse automation evaluations

A useful warehouse robotics RFQ states what the equipment carries, how often each route is demanded, where constraints occur, which control layer owns each decision and how performance will be accepted. This page reuses a compact compliance-style structure to capture those engineering facts—not sustainability slogans.

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 with Hikrobot.

Input groupMinimum informationWhy it changes the conceptPreferred evidence
Load unitLength, width, height, mass, underside, overhang, orientation and stabilityControls adapter interface, pickup tolerance, braking and safe transferDimensioned drawing, weight range, representative samples
Material flowOrigins, destinations, moves by interval, SKU/order profile, replenishment, peak duration and cutoffDetermines mission demand, travel, queueing, buffer occupancy and fleet quantityTimestamped transaction extract and route matrix
Site geometryClear aisle width, turns, gradients, floor joints, doors, lifts, crossings, safety zones and charging areasDefines feasible paths, speed restrictions, traffic rules and intervention accessCurrent CAD, measured survey, marked photographs
Control interfacesWMS/WCS/WES/PLC/FMS ownership, messages, acknowledgements, timeouts, alarms and network policyPrevents duplicated decisions, silent failures and unresolved exception statesResponsibility matrix, interface specification, sequence diagrams
AcceptanceDesign and peak rates, transaction definition, availability boundary, test duration, fault cases and evidence ownerTurns commercial expectations into repeatable FAT and SAT decisionsApproved protocol, scenario data, result and deviation template
Submission check

Before issuing the RFQ to Hikrobot

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, low energy, lost load and disabled stations have expected outcomes.

Reference and certification boundaries

If the project cites ISO 3691-4, 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. Hikrobot will not treat a logo row as acceptance evidence.

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, charging capacity and network growth so the initial phase does not create avoidable constraints.

Reproducible acceptance example

Freeze the route map, robot 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, energy state and recovery time, then repeat the same scenario after each material change. An example protocol (planning-range test conditions, not Hikrobot performance claims) requires: (1) SKU/order profile with lines-per-order mix and peak-window minutes; (2) rated load in kg with mm dimensions; (3) aisle clear width in mm at the tightest turn; (4) WMS/WCS/PLC/FMS ownership matrix with interface cycle time in seconds; (5) 120-minute nominal run followed by blocked-path, host-timeout and unavailable-station scenarios with measured recovery minutes and system availability % at the named FMS boundary.

Dispute note: fixed path vs flexible fleet phasing

When a site debates fixed AGV loops against flexible AMR fleets, keep the RFQ honest about duty cycle stability. If pallet move patterns are stable for years, deterministic dock-to-reserve paths may support higher design rates with simpler PLC handshakes. If SKU velocity and dock schedules change each season, document phased cutover, modular charging capacity and WCS ownership so a flexible fleet can expand without rewriting mission assumptions after SAT.

Dispute note: peak rate vs operational resilience

A headline missions-per-hour figure can conflict with buffer occupancy, charger redundancy and graceful degradation. Hikrobot RFQs ask teams to state whether the design objective is maximum peak rate for a short window, or a resilient rate that still holds when one aisle, one charger bank or one host path is unavailable. Both choices are valid; mixing them without writing the priority creates SAT ambiguity.

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