AMR integration guide
AMR Integration Guide: From Site Survey to Pilot Acceptance Without Rework
Turn the facility, workflow and system assumptions into a testable integration scope before the first robot arrives.
An AMR integration succeeds when the site survey, map, traffic rules, load handoff, business-system messages, training and acceptance tests describe the same operating scenario. Start with evidence from the facility, not a robot count or a generic integration promise.
Step 1 · facility evidence
Start with a site survey that another team can verify
Walk the complete route with operations, safety, maintenance and the integrator. Measure the floor, slopes, doors, lifts, crossings, lighting, network coverage, charging space, recovery points and emergency access. Photograph the awkward areas that a clean plan view hides.
| Control area | Evidence before design freeze |
|---|---|
| Site and route | Floor, slopes, doors, lifts, crossings, congestion, lighting and emergency access are measured. |
| Load and handoff | Payload, carrier, pickup/drop-off geometry, confirmation signals and failed-handoff recovery are defined. |
| Traffic and safety | Right-of-way, speed, pedestrian interaction, restricted zones and safe-stop behavior are agreed. |
| Systems and data | WMS/MES/ERP messages, map ownership, network coverage, task states and error handling are documented. |
| Pilot and training | Success metrics, test scenarios, operator roles, maintenance ownership and exception closure are assigned. |
Step 2 · operating design
Map the complete task, including the handoff and the exception
Define the load, carrier, pickup point, drop-off point, due time, confirmation signal and person or system that releases the next task. Record normal traffic and the conditions that force a wait: a blocked aisle, a full station, a door that stays closed or a manual recovery.
Keep the map version, route rules, speed limits, restricted zones and charging locations under change control. The AMR safety checklist adds the safety evidence; the fleet-sizing guide helps test whether the resulting cycle time and availability support the demand.
Step 3 · interfaces
Freeze the message and recovery contract before the pilot
Write the task fields and states in plain language: create, accept, start, arrive, load confirmed, unload confirmed, complete, pause, cancel and recover. For each state, define the source, timestamp, retry rule, owner and visible operator action. This prevents a map demo from being mistaken for a production integration.
Interface acceptance rule
Every system message must have a testable response and a safe recovery path. “The API is connected” is not an acceptance criterion.
- 01Document the WMS, MES, ERP or PLC owner for each task and status field.
- 02Test duplicate, delayed, missing and rejected messages before live traffic.
- 03Show operators how to pause, isolate, recover and resume a task without losing state.
- 04Record map, software, interface and configuration versions with every result.
Step 4 · pilot gate
Accept the pilot against normal, peak and degraded scenarios
A pilot acceptance test should prove the work under representative demand, not only an empty route. Include the highest intended payload, the real carrier, normal pedestrian interaction, a blocked route, a missed handoff, low battery, network or interface loss, safe stop/restart, manual recovery and the agreed service target.
- 01Prepare: freeze the route, load, map, software, test observer and expected result.
- 02Run: capture cycle time, queueing, handoff, charging, exception and on-time completion.
- 03Close: classify pass, correction or open exception and assign an owner and due date.
- 04Handover: deliver the approved map, rules, training, maintenance and change-control record.
If the site, load, interface or route changes, reopen the affected test rather than assuming the original result still applies. Use the AMR cost guide to keep commissioning, integration and support scope visible in the proposal.
Buyer questions
FAQs
What should an AMR site survey include?
Capture floors, slopes, doors, lifts, crossings, people flow, load handoffs, network coverage, charging, recovery space, fire and emergency access, and the interfaces the AMR must use.
When should WMS or MES integration be tested?
Test the real task message, acknowledgement, exception and retry path before the pilot is accepted. A robot moving on a map is not proof that the operational interface is ready.
How do we avoid rework during an AMR pilot?
Freeze the site assumptions, map version, load, traffic rules, interface fields, acceptance tests, training owner and change-control process before equipment is commissioned.
Does an AMR pilot need a formal acceptance checklist?
Yes. Define normal, peak and degraded scenarios, expected results, evidence owners and exception closure. Reuse the checklist when the route, load, software or interface changes.
Sources and related guidance
- AMR safety standards site checklist - apply the route and handoff evidence to a safety review.
- AGV vs AMR comparison - compare navigation and infrastructure assumptions.
- ISO 3691-4:2023 - confirm the applicable driverless industrial-truck safety requirements with the project team.
Ready to scope an AMR pilot?
Share your facility, load, routes, handoffs, interfaces and acceptance target so the first proposal includes the evidence your team needs.
Submit your pilot brief