AMR fleet management
AMR fleet management
Supervise autonomous mobile robot operations—sites, missions, commands, and telemetry—while navigation and safety stay on the robot.
How to supervise AMRs
Autonomous mobile robots move through warehouses and plants on their own navigation stack. Supervising them is a different job: which AMR is assigned to which site, which mission was dispatched, whether the vehicle is connected, and whether the last command completed. Dagmont Command is that supervisory layer for AMR fleet management.
Dagmont does not provide robot-local navigation or SLAM. Path planning, localization, and onboard obstacle avoidance stay on the AMR. Command does not drive the wheels.
Operational layer versus onboard autonomy
An AMR already has a controller that decides how to move. Command sits above that controller through a Site Gateway and a Robot Agent or vendor adapter. Operators issue supported high-level commands and mission dispatch. The AMR reports state, battery, faults, and execution results back.
That boundary is the same one used for the wider robot operations platform. Fleet software that owns motion and traffic can keep doing that work. Dagmont records supervisory commands and the evidence of what the AMR reported.
Missions, connectivity, and warehouse operations
Warehouse robot operations often mix AMRs with other vehicles. Command groups them by site and fleet so an operator can see connectivity and capabilities per robot. A mission is supervised as work with a lifecycle, not as a map edit.
If an AMR disconnects, Command distinguishes a down gateway from a disconnected Robot Agent and from a robot that reports itself offline. Stale telemetry is flagged when snapshots stop, so a warehouse lead does not treat an old battery reading as live. See physical robot monitoring for that model.
Failures without replacing the AMR vendor
Command is designed to work above different AMR manufacturers through adapters: HTTP/JSON, vendor Python integrations, serial or controller links, and a simulator for non-physical fleets. A VDA 5050 translation layer can map messages. Production control uses the HTTP/JSON path, not VDA 5050 MQTT.
An AMR is available for command when its adapter is enrolled and command execution is enabled. Completion still depends on what that robot reports. Failed missions and commands can escalate into Deployment Intelligence when the site needs an investigation record rather than another live retry.