Robot command center
Robot command center software
Give operators one robot command center to dispatch missions, watch the command lifecycle, and record who acted when a robot fails.
What operators do in a command center
A robot command center is the place operators supervise a fleet and issue the next command. In Dagmont Command that screen shows site, robot, connectivity, capabilities, the active command, and recent failures. It is robot command center software for supervisory control, not a pendant for jogging motors.
Remote robot operations use the same center. The operator does not need to stand at the controller to see whether the gateway, the Robot Agent, and the robot agree about state. They do need an enrolled integration before a command can reach that robot.
Mission management and fleet control
Mission management means dispatching supported work and watching it through execution. Fleet control means choosing the robot, confirming it is allowed to receive commands, and sending a high-level action its capabilities include. Both are operator actions with an identity and a timestamp.
The center follows the lifecycle used across robot command software: requested, queued, dispatched, gateway acknowledged, robot acknowledged, executing, completed, or failed. Operators can see that a command left the center and whether the robot reported it done.
Who can act
Viewers may use the center to observe robots, telemetry, and history. The command controls are not available to them. Operators send permitted commands when execution is enabled. Admins configure the gateway, the robot, the adapter, and command access before the center can reach a physical machine.
Simulated robots remain labeled simulated in the same center, including simulator fleets such as CleanBot. A simulated acknowledgement is not presented as physical execution. Fleet management uses that label so mixed programs do not blur the two.
When the center hands off to investigation
Failed commands, offline robots, and stale telemetry become operational issues the center can show. Routine supervision stays in Command. When the event needs evidence, corrective action, retesting, and acceptance, Command creates a Deployment Intelligence case with the operational snapshot and command history.
That handoff keeps the command center focused on live operations. The investigation record lives in the other Dagmont product, linked by the failure rather than copied into a second unofficial log.