Decision guide · decision

Write AMR pilot acceptance measures before the demo

Precommit scope, measures, evidence, stop conditions and decision rules for a warehouse mobile-robot pilot.

DecisionWhat evidence will support an accept, revise or stop decision?

Freeze the boundary

Name the vehicle, load interface, software, map, route, endpoints, traffic window and facility integrations in the pilot baseline. A result is not reusable when the configured system that produced it is unclear.

Measure distributions and exceptions

Retain every mission, not only completed examples. Report cycle-time distributions, blocked work, human interventions, retries and recovery duration so the buyer can see normal work and failure handling together.

Precommit the decision

State who will accept, revise or stop the pilot and what happens when a measure misses its threshold. Open questions should remain visible; a successful demonstration does not need to be relabelled as a production commitment.

Structured requirement

What the buyer brief must carry.

Task: Run a bounded set of representative material-movement missions under agreed site conditions.

Industry: Warehousing and industrial material movement

Environment

  • Named pilot route and endpoints
  • Representative traffic windows
  • Controlled load set
  • Witnessed exception and recovery tests

Constraints

  • No production-scale inference from a staged demo
  • Explicit excluded loads and conditions
  • Safety and operating stop authority
  • Evidence retention and system version
  • Decision owner and date

Robot approaches

  • Single-vehicle route trial
  • Small-fleet flow trial
  • Endpoint integration trial
  • Simulation followed by physical validation

Provider evidence to request

  • Instrumented mission and event logs
  • Configuration and software version record
  • Supported exception and recovery procedure
  • Evidence export without marketing-only summaries

Integration boundary

  • Timestamp alignment across robot and facility systems
  • Mission, endpoint and traffic event identifiers
  • Evidence retention and access
  • Versioned configuration baseline

Evidence to retain

  • Every planned mission and its outcome
  • Raw timestamps and classified delays
  • Intervention and recovery record
  • Deviations from the agreed route, load or configuration
  • Customer witness notes and unresolved questions

Installed-cost inputs

  • Pilot equipment and engineering
  • Site preparation and supervision
  • Integration and evidence collection
  • Training, travel and restoration
  • Production estimate kept separate from pilot price

Pilot measures

  • Mission completion by representative window
  • Load integrity and correct destination
  • P50 and P90 cycle time
  • Interventions and recoveries per 100 missions
  • Availability with an agreed denominator
  • All stop conditions and deviations

Geography boundary: Acceptance measures must sit beside, not replace, applicable safety, legal and site approvals.

Sources and boundaries

ISO 3691-4:2023 — Driverless industrial trucks and their systems

The public ISO abstract identifies the standard's scope and the importance of the operating zone. It is not a compliance assessment, and the full standard must be obtained and applied by competent parties where relevant.

Source date 2023-06-01 · Reviewed 2026-08-24

VDA 5050 Version 3.0.0

The specification defines an interface boundary between mobile robots and a master control. Stated support is not proof of feature coverage, peripheral integration, traffic strategy, safety or cybersecurity.

Source date 2026-03-01 · Reviewed 2026-08-24

Page boundary: These measures are a project-contracting aid. They do not certify safety, compliance, reliability or production performance.

Continue with your task

Turn the route and load into a reviewable requirement.

Describe one material-movement problem. RobotAtom will structure the constraints, possible approaches, provider-comparison criteria and pilot measures before any provider shortlist.

Build a Robot Fit brief