An AMR operating zone needs change control

A mobile robot is qualified for an environment, not an empty floor plan

A drawing of the proposed route is useful, but it is not the operating requirement. A mobile robot also encounters people, forklifts, doors, intersections, changing loads, floor damage, spills, temporary storage, charging stations and workstations. Those conditions can change the space available, the robot's speed, its stopping behaviour and the way work is recovered.

ISO 3691-4:2023 says the condition of the operating zone has a significant effect on the safe operation of driverless industrial trucks, a term that its public scope includes autonomous mobile robots and AGVs. RobotAtom therefore treats the operating zone as part of the configured solution and as a hard gate, not as background information that a fleet-size or price score can offset.

Record the route as operating conditions

• Measure usable aisle, doorway, turn and passing widths in the conditions that will actually exist, including fixtures, stored material and the robot's loaded envelope.
• Record slopes, transitions, gaps, thresholds, floor condition, traction risks and any limits on water, oil, dirt, temperature or other environmental exposure.
• Map crossings, blind corners, pedestrian access, manual vehicles, queues, doors, lifts, conveyors, workstations, chargers and places where people load, unload or recover the robot.
• Define permitted routes, directions, speeds, passing rules, waiting points and restricted areas for each relevant robot and load state.
• Name the owner and source of every material value, mark unknowns, and version the approved layout and operating assumptions.

Keep manufacturer limits attached to their conditions

Mobile Industrial Robots currently publishes different MiR250 corridor and doorway widths for its default setup and for a minimized footprint with muted protective fields. It also states a gap tolerance, incline at a stated speed, indoor environmental limits and dry, clean floor conditions, while warning that specifications can vary with local conditions and application setup. These are MiR's claims for its own product, not independent verification of another AMR or a customer site.

OTTO by Rockwell Automation's selection guidance says its qualification process considers manual traffic, ramps or slopes, pickup and drop-off points, Wi-Fi coverage and whether forklifts share an endpoint. That is manufacturer guidance about OTTO's process, not proof that an OTTO system or any competitor will meet a site's throughput or safety requirements. Use supplier material to identify conditions to verify; use site measurements, engineering review and acceptance evidence to establish project fit.

Assign the environment across the lifecycle

A3's public descriptions of the ANSI/A3 R15.08 series separate responsibilities across the mobile-robot lifecycle. Part 1, reaffirmed in 2026, addresses the manufacturer's specified operating environment and information passed onward. Part 2 addresses integration, facility adaptations, workstations, chargers and the deployed operating environment. The new Part 3 addresses user operation, the current operating environment and management of change.

That public scope supports a practical ownership chain: the manufacturer documents operating limits, the integrator shows how the configured application and facility meet them, and the user controls ongoing conditions and changes. The full paid standards were not reviewed for this article, and their applicability depends on the deployment jurisdiction and use. Their public descriptions do not establish that a named robot, integration or site conforms to the standards.

Update every affected route record together

VDMA's Layout Interchange Format 1.0.0 provides one industry-body example of a versioned track layout exchanged between a vehicle integrator and a third-party master control system. Its process calls for physical verification before transfer and coordinated processing and confirmation when the layout or vehicle behaviour changes.

The same guideline leaves traffic rules, congestion, battery management, doors, lifts and some higher-level behaviour outside the layout file. The practical inference is that a route change may require several synchronized records: the measured site baseline, robot and load restrictions, fleet or master-control configuration, peripheral interfaces and operating rules. LIF is one optional data format, not a complete operating-zone or safety assessment.

Test the busy and degraded route

• Run the exact proposed robot, payload, safety configuration, software and fleet-control versions.
• Test representative shifts, including expected pedestrian and vehicle traffic, queues, crossings and blocked routes—not only a cleared demonstration route.
• Exercise the narrowest turn, doorway, threshold, slope, load-transfer point, charger and shared resource under the relevant loaded and unloaded states.
• Measure travel and wait time, task completion, interventions and recovery against the agreed operational acceptance criteria.
• Test stale maps, unavailable doors or lifts, temporary obstructions, network loss, manual recovery and restart without bypassing agreed safeguards.
• Retain the approved route version, observations, exceptions and owners so later changes can be compared with the accepted baseline.

Make change a review trigger

Define which changes reopen engineering, risk and operational review: a new robot or load, altered protective fields, route or speed changes, layout and racking moves, new doors or workstations, changed traffic, floor repairs, software updates or a new recovery process. Also define who can approve the change, what evidence must be repeated and how operators are told.

A successful trial only supports the configuration and conditions that were tested. ISO 3691-4 remains published but is due to be revised, and its public scope excludes public zones, public roads and several special or severe environments. ISO, A3 and VDMA describe standards or industry guidance, while MiR and OTTO describe their own products and processes; none independently certifies the proposed deployment. RobotAtom records the operating-zone requirement, evidence and change state. It does not certify safety or compliance.