Robot operations platform
Robot operations platform
Run robots, site gateways, telemetry, commands, missions, operators, issues, and audit history as one supervisory operations platform.
The operating model
A robot operations platform is the control plane above individual machines. Dagmont Command connects robots, site gateways, telemetry, commands, missions, operators, issues, and audit history. That is the model searchers mean by robot operations software and a robot operations control plane.
Dagmont is robotics deployment infrastructure, not a generic robotics company. Command is the operational control layer. Deployment Intelligence is the investigation and acceptance record. The two products meet when a live failure needs a structured case.
Robots, gateways, and telemetry
Physical robots are enrolled at a site. The Site Gateway is the edge connection for that site. The Robot Agent, or a vendor adapter, sits with the robot controller. Commands go Command, gateway, agent, controller, robot. Results and telemetry return robot, agent, gateway, Command.
Remote robot operations depend on that return path. Operators away from the floor still need to know whether the gateway is up, whether the agent heartbeat is fresh, and whether telemetry matches the command that is supposed to be running. Physical robot monitoring is that view.
Commands and missions
Missions are the work operators dispatch. Commands are the supervisory actions around that work: pause, resume, cancel, controlled stop, return to charge, return to base, mode changes, and mission dispatch, where the robot integration supports them.
The command lifecycle is part of the platform, not a side log. Requested work stays visible through queueing, dispatch, acknowledgement, execution, and the final result. Mission supervision uses the same evidence: robot-reported state, not a transport success code.
Operators, issues, and audit history
Viewers observe. Operators send permitted commands when execution is enabled. Admins configure gateways, robots, and who may command. Those roles are the permission model for the operations platform.
Issues capture offline robots, disconnected agents, stale telemetry, faults, and failed commands. The audit trail records who acted, which state the command reached, and how it ended. That history is what a later shift, or a Deployment Intelligence investigation, can inspect.
Where fleet management fits
Robot fleet management is the multi-robot view of this platform: sites, health, capabilities, and history across machines. The operations platform is the broader model that also includes missions, operator permissions, and the escalation path.
Industrial and warehouse programs use the same model for AMR fleets and AGV fleets. The platform supervises. Vehicle motion and safety remain on the robot.