Robot fleet management with operational context

Create group or site cohorts and add building, floor, or zone context where useful. Static membership works for a known deployment; rules can organize units by model, firmware, advertised capabilities, or tags. Filter the fleet board by these boundaries to focus on the units an operator actually manages.

For a mobile robot fleet across two sites, keep site membership separate from a maintenance tag. The same unit can belong to its operating site while also appearing in the maintenance selection. This makes fleet views useful for both local operators and the team responsible for a shared hardware model.

Pre-register serial numbers through CSV and create an enrollment token with an appropriate claim limit and serial allowlist. A robot uses the claim flow on first connection and receives its own credential. The runtime then authenticates as that unit when sending heartbeats or telemetry.

Individual credentials give operators a clearer lifecycle for access. A unit can be tracked, moved into maintenance, or decommissioned without sharing one long-lived credential across the whole fleet. Confirm that the device software implements claim and reporting before planning an unattended enrollment.

Robots send telemetry batches with an idempotency identifier, allowing a client to retry an uncertain submission without counting the same batch twice. Minute and hour rollups support trends by robot and cohort. Check the documented backlog window and retention rules when designing store-and-forward reporting for intermittent connectivity.

Use a filtered selection for audited bulk operations such as updating tags or cohorts, dispatching commands, or acknowledging alerts. Follow per-target results and retry failed targets where appropriate. Mission records and command status support coordination, while the robot's own runtime remains responsible for navigation and physical execution.