Run the Traffic Test

An autonomous mobile robot navigates dynamically rather than following a fixed path, which is what distinguishes it from a traditional guided vehicle running on wire or tape. That flexibility is the selling point and the source of the difficulty.

The Bot Scout traffic test evaluates the fleet rather than the robot: what happens when two AMRs meet in a full aisle, when a pallet blocks a route, when three units queue for one charger, and when a person stops to talk in a doorway. A single unit in an empty building tells you nothing about any of it.

Throughput in practice is set by waiting, not by speed. Utilisation collapses well before reliability does, and utilisation is usually what the business case was built on.

SituationSingle robot behaviourFleet behaviourWhat to test
Two units meet in a narrow aisleNot applicableDeadlock or negotiated passRun both units on crossing routes
Blocked routeStops or reroutesQueue forms behind itBlock a route during a live run
ChargingPredictableContention for chargersRun to low battery at peak
Priority conflictNot applicableNeeds an arbitration ruleSend two urgent jobs at once
Human interactionStops politelyCascading delaysTest at shift change

The Software Is the Purchase

Fleet management assigns jobs, routes units, resolves conflicts, and reports on the whole system. Its integration with the existing warehouse or manufacturing execution system is routinely scoped late and routinely sets the schedule, a pattern also described in the warehouse automation guide.

Ask who arbitrates when two jobs claim the same unit, how priorities are configured, and whether operations staff can change them without a vendor visit. A fleet nobody on site can reconfigure becomes a fixed installation.

For inspection and data collection rather than transport, a different class of mobile robot applies; Boston Dynamics Spot illustrates that distinction, and it should not be compared with transport AMRs as if they were interchangeable.

  • Test with the full fleet, not a single unit.
  • Block a route deliberately and time the recovery.
  • Check charger contention at peak, not at shift start.
  • Confirm who can change priorities without a vendor visit.
  • Scope the WMS or MES interface before signing for hardware.

Floors, Networks, and People

AMRs need floor conditions, network coverage, and defined traffic rules. Ramps, dock plates, thresholds, and reflective surfaces all affect navigation, and network dead zones produce stoppages that look like robot faults.

Shared space is the operating environment, not an exception. OSHA notes that many robot incidents occur during non-routine work such as setup, testing, and maintenance, which in a live building happens alongside pedestrians and forklifts.

Staffing changes shape rather than disappearing. Fleet recovery, exception handling, and someone who owns the data are new roles, and a plan that omits them will find them anyway.

Bottom Line

Autonomous mobile robots are a fleet purchase. Test traffic, blocking, and charger contention at peak, and scope the fleet software integration before comparing vehicles.

Run two units on crossing routes and block one deliberately before comparing vendor throughput claims.

FAQs

What is the difference between an AMR and an AGV?

An AMR navigates dynamically and can reroute around obstacles. A traditional guided vehicle follows a fixed path defined by wire, tape, or markers, which is more predictable and less flexible.

What limits AMR throughput in practice?

Waiting rather than speed. Blocked aisles, traffic conflicts, and charger contention reduce utilisation well before reliability becomes an issue.

What should an AMR pilot include?

The full fleet on crossing routes, a deliberately blocked aisle, charger contention at peak, and a shift-change period with normal pedestrian and forklift traffic.

Is fleet software part of the AMR purchase?

It is the most important part. Job assignment, routing, conflict resolution, and integration with the existing WMS or MES usually set the project schedule.

Primary Sources