ANSI/A3 R15.08-3-2026 addresses users of industrial mobile robot applications, including management of changes to the application and its current operating environment. For a US warehouse fleet, that means keeping the accepted operating arrangement identifiable after commissioning. Connect changes in routes, maps, zones, traffic, tasks and operator procedures to affected requirements, evidence and an authorised disposition. A successful original site test does not establish that every later fleet or warehouse change is covered. (ANSI R15.08-3-2026 public scope)
This guide is for operations engineering, AMR deployment and safety owners deciding whether an existing fleet may operate under a changed arrangement. Its practical output is a current-operating-environment change register with vehicle and zone effectivity. The question is narrower than initial site acceptance: which accepted assumptions are still true today, and what changes need reassessment?
What does R15.08 Part 3 cover for AMR users?
The ANSI catalogue calls the document Industrial Mobile Robots, Safety Requirements, Part 3: Use of IMR Applications. Its public scope describes maintaining acceptable workplace risk, safe use, risk assessment and management of changes to both the IMR application and the current operating environment, or COE, throughout the machinery lifecycle. The scope supports an ongoing user review, rather than a one-time vehicle approval. (ANSI, title and public scope)
A3's current catalogue distinguishes the other parts. ANSI/A3 R15.08-1-2020 (R2026) concerns the individual IMR and is a reaffirmation with no technical differences from the 2020 text. ANSI/A3 R15.08-2-2023 concerns IMR systems and applications, while the separate 2026 Part 3 concerns use. Keep those identities in the source register instead of treating “R15.08-2026” as a single revised requirement set. (A3 industrial robot standards, R15.08 listings)
The public catalogue does not provide all normative duties, numerical limits or change procedures. Obtain the applicable licensed text for that assessment. The registers and rollout decisions below are editorial engineering methods. They do not reproduce clauses or establish a universal speed, separation distance or mandatory rollout percentage.
OSHA identifies national consensus standards as distinct from its regulations. A US workplace still needs the relevant federal or state duty assessment, alongside the national standard or contractual basis selected for the application. (OSHA robotics standards, State Plan Standards and National Consensus Standards)
What is the current operating environment of an AMR fleet?
For this worksheet, the COE is the identifiable operating arrangement on which the fleet's accepted use depends. It includes physical conditions and operational rules as well as software representations. Define it for the application rather than assuming a map file contains the entire environment.
In a fictional US distribution warehouse, the arrangement might include transfer station positions, pedestrian access, powered-truck traffic, load families, floor conditions, permitted routes and the procedures used to release tasks. A map revision can represent only some of those facts. A painted crossing can move without an AMR software release, and an operating shift can change access patterns without moving any equipment.
Give consequential assumptions an owner. Facilities may establish equipment locations, operations may maintain the traffic procedure and the deployment team may control map distribution. The reviewer needs to know how the physical arrangement and each vehicle's effective configuration remain aligned.
The existing ISO 3691-4 site-acceptance guide explains how installation assumptions enter commissioning. This Part 3 workflow starts from that accepted arrangement and follows routine changes after handover. It should use the existing acceptance records as inputs rather than rebuilding an unrelated site checklist.
How should the fleet change register connect maps and site reality?
Record the accepted arrangement, proposed change, affected vehicles or zones, dependencies, required reassessment and decision. Preserve both physical and software identities. A map checksum can identify a file, but it cannot prove that the warehouse still matches its assumptions.
The table describes a fictional, unexecuted change in a US distribution warehouse. Fleet baseline FW-12 would use map MP-6 and transfer-zone plan ZP-4. No warehouse, fleet or accepted safety result is represented. The proposed records show the questions that a real team would need to answer.
| Change record | Accepted assumption and proposed change | Affected application and owner | Evidence and operating disposition needed |
|---|---|---|---|
| COE-31, crossing relocation | The proposed pedestrian crossing moves beside transfer station TS-2 | Facilities controls the physical crossing, operations controls access rules, deployment controls affected routes | Compare visibility, traffic and protection assumptions, identify affected requirements and assess the changed arrangement |
| COE-32, map revision | MP-7 would represent the revised crossing and route | Deployment owns distribution to the declared vehicle cohort | Confirm file identity and actual vehicle activation, then retain the installed configuration used for evaluation |
| COE-33, temporary overflow stock | A new stock position may alter visibility near TS-2 | Operations owns the temporary placement and its removal conditions | Review whether the accepted environment still holds, with a restriction or changed arrangement decided by the responsible authority |
| COE-34, operator procedure | A new shift procedure changes when manual transfer is requested | Operations and integration owners assess the task interface | Exercise the agreed sequence and interruption cases, review training and unresolved dependencies |
| COE-35, offline vehicle | One vehicle may retain MP-6 while the affected route uses MP-7 | Fleet deployment owns vehicle-specific effectivity | Decide whether the vehicle may remain in a separately assessed zone or must be excluded until the change is verified |
The table's last column is the important output. It should explain the operation being permitted or held, the evidence supporting that decision and the authority that made it. “Map published” and “all affected vehicles operating on the assessed map” are different states.
Keep temporary changes visible. A pallet placed for one shift can invalidate a visibility assumption even if nobody plans to edit the controlled drawing. Define how operations reports such a change, who can impose an interim restriction and what establishes that the previous arrangement has been restored.
Which warehouse changes should trigger reassessment?
Select triggers from the actual application and accepted conditions. Consider physical layout, traffic and pedestrian arrangements, loads, docking interfaces, tasks, maintenance practices, operator roles, fleet software and effective map or zone configuration. This list is a prompt for engineering review, not a universal clause extract.
A change request should state what remains unchanged as well as what changed when that helps determine evidence applicability. A moved charging station may affect one travel route and one service activity. It need not reopen every unrelated claim, but the team needs an argument for the bounded reassessment.
Distinguish a planned change from a detected discrepancy. A planned new route can enter a controlled proposal before deployment. A vehicle discovering an unexpected obstacle or operations finding a moved barrier is an operational event. Its immediate response must come from the established operating and safety arrangements, followed by a recorded assessment. Creating a paperwork record is not an adequate immediate protective measure.
Use the robotics change-impact guide to trace the changed assumption to requirements, interfaces, verification and owners. This fleet register adds installed vehicle identity, zone scope and the physical operating arrangement on which that trace depends.
How do staged changes affect evidence and vehicle effectivity?
A staged rollout can limit an evaluation to a declared cohort or operating zone, if the responsible authorities assess the resulting mixed arrangement. It does not establish safety merely because fewer vehicles receive the change. Define the stage's entry conditions, permitted interactions, evidence questions, stop conditions and exit decision.
Record the configuration each vehicle actually activates. A fleet-server update, successful download and active map state may occur at different times. Where that distinction matters to behaviour, define the acknowledgments and evidence that establish effective use. Give failed or missing acknowledgments an explicit disposition.
Also consider interaction between changed and unchanged vehicles. A shared transfer station or traffic rule can connect the cohorts even when their software deployments are separate. The stage's scope must include those interactions or exclude them through an assessed arrangement. Do not use a green rollout dashboard as evidence that the physical operating assumptions remain valid.
Preserve the exact setup of any later evaluation. The robotics configuration-evidence guide explains the underlying result record. A fleet review also needs the effective vehicle cohort, site arrangement, map and zone identities that delimit the result's applicability.
What failure would hold the warehouse change?
Return to the fictional FW-12 fleet. The proposal combines a moved pedestrian crossing and map MP-7. One vehicle is offline when MP-7 is distributed. The change board has a server deployment record, but no acknowledgment that the offline vehicle activated the new map or was excluded from the affected route.
The problem is an unresolved operating configuration. Testing another vehicle on MP-7 would not establish the offline vehicle's active state, and a software deployment receipt would not establish the relocated crossing's physical conditions. These are separate evidence gaps and should have separate owners.
A proposed disposition would hold the affected vehicle and changed route from the new arrangement until the required configuration and environment evidence are established and reviewed. If operations proposes a restricted alternative, assess that alternative explicitly. This fictional example reports no executed checks and grants no operating permission.
The resulting record should preserve the old baseline, the proposed change, missing acknowledgments, physical-condition work and the scope of the final decision. A future reviewer could then explain why a particular vehicle or route was included, excluded or still awaiting action.
How can Arc support a post-commissioning fleet review?
Arc's configuration capability represents variants, applicability and configuration-specific records. A team can configure vehicle, site, map, zone and change records within its connected programme model, then link the affected assumptions to requirements and evidence.
Controlled engineering changes preserve proposals and receiving baselines. The customer defines authority and effectivity rules. Arc organises those records and review decisions. It does not distribute AMR maps, sense warehouse conditions or independently decide that a changed application is safe.
Sources and method
Prepared on 2 November 2026 using ANSI's public R15.08-3-2026 scope, A3's current part and reaffirmation listings, OSHA's distinction between consensus standards and regulations, and Arc's canonical capability-page source. The paid standards were not reviewed. The COE definition used for the worksheet, register fields and fictional FW-12 scenario are editorial methods. No normative threshold, mandatory rollout stage or executed result is claimed. This adapts roadmap topic R37 to the current US user-part scope. Arc sells requirements management and systems engineering software.
Frequently asked questions
What does ANSI/A3 R15.08-3-2026 add to a fleet review?
Its public scope addresses users maintaining acceptable risk during use of IMR applications, including change management for the application and its current operating environment. It supports an ongoing operating review. Assess the licensed text for the detailed requirements applicable to the project. (ANSI R15.08-3-2026 scope)
Is R15.08-1-2020 (R2026) a technically new robot standard?
A3 identifies the R2026 record as a reaffirmation with no technical differences from the original 2020 text. Keep that designation distinct from the separate R15.08-3-2026 user part and R15.08-2-2023 integration part. (A3 R15.08 catalogue entries)
Does an AMR map define the complete operating environment?
A map identifies a software representation of some operating conditions. The actual environment also includes physical layout, access, traffic, tasks and site procedures relevant to the application. Keep their identities and owners connected so a map update cannot obscure a changed physical assumption.
Can a partially updated fleet use the new route?
That needs an explicit application and interaction assessment. Establish which vehicles have activated the assessed configuration and what unchanged vehicles may do. Missing acknowledgments, mixed traffic and shared-station dependencies should have a defined operating disposition before the new arrangement is permitted.
Does a successful original site test cover later warehouse changes?
It supports the installation and conditions within its recorded scope. Reassess affected claims when the application or accepted environment changes. Preserve the original result and record whether it remains applicable, needs supplementary evidence or cannot support the proposed operation.