Risk and safety basis
Applicable risk assessment, operating modes, hazard controls, validation plan and residual-risk communication.
Possible references: ISO 12100, ISO 3691-4 and ISO 13849-1 where relevant.Prepare the facts that allow a warehouse robotics concept to be evaluated consistently. Every target should name its unit, input source, revision, owner, operating condition and acceptance method.
The table is an RFQ preparation aid, not a specification for a particular model. Unknown values can be entered as ranges and marked for confirmation.
| Input group | Required field | Unit or format | Why it changes the design |
|---|---|---|---|
| Load and geometry | Load envelope and carrier | L × W × H in mm | Shapes pickup approach, station interface, turning and clearance. |
| Rated load and center | kg + center-of-gravity range | Changes traction, stability, duty cycle and safe handling conditions. | |
| Aisle and crossings | Clear width in mm + scaled plan | Determines route feasibility, passing rules and human interaction. | |
| Floor and environment | Slope, joints, temperature, contaminants | Defines equipment limits, sensing conditions and maintenance exposure. | |
| Demand and flow | Order or mission sample | Timestamped source file | Reveals SKU depth, release pattern, travel and station demand. |
| Normal and peak target | Units/hour or order lines/hour | Needs duration, mix, buffers, replenishment and backlog definition. | |
| Operating calendar | Shifts/day, hours/shift, breaks | Influences duty cycle, charging opportunity and maintenance access. | |
| Disruption scenarios | Trigger, affected boundary, recovery objective | Tests resilience beyond a clean peak-throughput run. | |
| Controls and acceptance | System responsibility | WMS / WCS / WES / fleet / PLC matrix | Prevents overlapping ownership and unhandled state transitions. |
| Interface cycle | Command, acknowledgment and timeout in s | Connects message behavior to physical material-flow timing. | |
| Availability definition | % + measurement window + exclusions | Separates robot, zone, subsystem and end-to-end performance. | |
| FAT / SAT evidence | Script, data revision, expected result, sign-off | Makes acceptance repeatable and issues traceable into handover. |
A standard name alone does not demonstrate conformity. Identify which requirement applies, which party owns the evidence and which product configuration the record covers. Company management-system certificates, machinery-design standards, regulatory conformity and third-party product certificates are different evidence classes.
The checklist below avoids assuming that Ambi Robotics or a particular model holds a certificate. Applicable documents must be reviewed for legal entity, issuing body, certificate or report number, scope, geography, revision and validity.
Applicable risk assessment, operating modes, hazard controls, validation plan and residual-risk communication.
Possible references: ISO 12100, ISO 3691-4 and ISO 13849-1 where relevant.Versioned message list, state model, timeout behavior, network assumptions and responsibility matrix.
Evidence: approved interface control document and emulation or integration record.Dataset, load mix, test duration, instrumentation, buffer state, exclusions and pass criteria.
Evidence: FAT/SAT script with observed result and traceable issue disposition.Maintenance access, backup and restore, compatible spares, alarm triage, manual fallback and restart authority.
Evidence: handover index, training record and controlled recovery procedure.These boundaries keep Ambi Robotics concept work honest. They are engineering limits for evaluation, not product claims for a named model series.
Use the same five axes for every option under review. Do not insert competitor names; score only the operating trade-offs that change capital, labor or recovery risk.
| Axis | Example unit | Typical review question |
|---|---|---|
| System throughput | order lines/hour across a 4-hour peak | What mix, backlog and replenishment assumptions sit behind the number? |
| Rated load | kg with load-center range | Does the carrier, tote or pallet change stability or duty cycle? |
| Aisle / clear width | mm on a scaled plan | Where do robots, people and maintenance carts share space? |
| Controls boundary | WMS / WCS / WES / fleet / PLC matrix | Who owns timeout, restart and inventory reconciliation? |
| Acceptance evidence | FAT script + 8-hour SAT window | Which disruption cases must pass before handover? |
Attach or summarize the load table, representative demand, scaled layout, interface list and the acceptance questions procurement and operations need answered. Mark forecasts and estimates so they are not mistaken for confirmed site facts.