Decision guide · implementation
Map the AMR operating zone before inviting a demonstration
Turn floors, crossings, people, vehicles, doors, lifts, storage and change control into a route evidence pack.
Treat the zone as part of the system
The ISO public abstract notes that operating-zone condition materially affects safe operation. Record the route, crossings, surfaces, endpoints and access rules as controlled project inputs rather than background scenery.
Walk the exceptions
A clean demonstration route is weak evidence. Review peak traffic, replenishment, cleaning, damaged floors, temporary pallets, open doors and unusual shift conditions. Mark conditions the pilot will include, exclude or stop on.
Assign change ownership
Racking, traffic, doors and floor conditions change after commissioning. Name who can alter the zone, how the change is recorded, which tests must be repeated and who returns the route to service.
Structured requirement
What the buyer brief must carry.
Task: Operate a driverless industrial vehicle along a bounded route with named endpoints and interaction rules.
Industry: Warehousing and industrial sites
Environment
- Floors, ramps and transitions
- Crossings and shared traffic
- Doors, lifts and controlled access
- Temporary obstructions and changing storage
Constraints
- Floor damage, debris, water and reflectivity
- Blind corners and stopping visibility
- Pedestrian, forklift and truck interaction
- Emergency routes and fire controls
- Who approves and records route changes
Robot approaches
- Separated automated route
- Shared route with engineered controls
- Time-separated operation
- No-go decision until the site changes
Provider evidence to request
- Documented environmental operating limits
- Mapping and remapping controls
- Detection and protective-field evidence for the configured system
- Change-management and revalidation process
Integration boundary
- Automatic door and lift states
- Traffic lights, gates and access controls
- Facility change notifications
- Map, zone and configuration versioning
Evidence to retain
- Versioned route map and photo record
- Crossing and obstruction test results
- Defined degraded and stop states
- Change log linked to retest decisions
Installed-cost inputs
- Floor and aisle remediation
- Barriers, gates, signs and crossings
- Door, lift and traffic controls
- Mapping, commissioning and future revalidation
Pilot measures
- Route coverage under agreed conditions
- Blocked or abandoned missions by location
- Protective stops and traffic waits
- Human interventions and rule violations
- Time to review and release a route change
Geography boundary: The checklist is not jurisdiction-specific and must be reconciled with local requirements and site rules.
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-24Warehousing — Hazards and Solutions
OSHA guidance establishes US warehouse hazard context. It does not replace the law, standards, risk assessment or competent safety advice applicable at the deployment location.
Source date undated · Reviewed 2026-08-24Mobile Robotics Systems Research and Standard Test Methods
NIST describes measurement methods and environmental factors for mobile-robot performance. It does not validate a particular commercial product or RobotAtom estimate.
Source date 2024-08-16 · Reviewed 2026-08-24Page boundary: This is a discovery checklist, not a risk assessment, traffic design, compliance statement or permission to operate.
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.