AGV fleet management
AGV fleet management
Supervise AGV fleets with site context, commands, telemetry, and execution history while motion and safety control stay on the vehicle.
How to monitor and supervise AGVs
Automated guided vehicles follow site guidance and a vehicle controller. AGV fleet management in Dagmont is the supervisory record around that vehicle: which AGV is at which site, whether it is connected, which command is active, and how the last command ended. Dagmont Command does not become the AGV’s guidance system.
People comparing AGVs with AMRs should keep the same split. Both are mobile robots. Command supervises operations for either type. The difference on the vehicle — guided path versus onboard autonomy — stays on the vehicle.
Supervisory control versus onboard motion and safety
AGV motion, path following, braking, and safety-rated stops remain on the vehicle and the site safety system. Command can send a supported supervisory command, including a controlled stop where the integration allows it. That command is not a physical emergency stop and it does not replace the safety PLC.
Robot fleet control here means authorized operators directing work and recording the result. It does not mean Dagmont closing the motor loop. The controller on the AGV remains the real-time system.
Gateways, telemetry, and execution history
Each AGV site enrolls a Site Gateway. The Robot Agent or adapter reports telemetry and command progress. Operators watch battery, faults, and freshness in robot telemetry and see gateway health separately from the vehicle.
Execution history shows requested, queued, dispatched, gateway acknowledged, robot acknowledged, executing, completed, or failed. A gateway acknowledgement is not proof the AGV finished the move. Physical evidence and the vehicle’s reported state decide the result, as described in robot command software.
Multi-vendor AGV sites
Sites often keep an installed AGV vendor for guidance and traffic. Dagmont is the operations layer above that vendor when an adapter is implemented. HTTP/JSON and vendor Python integrations are the production connection styles. Simulated AGVs stay labeled simulated.
When an AGV failure needs more than a live retry, Command opens an operational issue and can escalate into Deployment Intelligence with command history attached. Monitoring details live on the physical robot monitoring page.