Skip to content

Robotair Fleets⿻

Estimated time to read: 2 minutes

Concept Overview⿻

In Robotair, a Fleet is a logical grouping of robots that enables scalable software deployment and monitoring operations. Fleets provide a hierarchical structure that can represent operational boundaries such as geographic zones, deployment waves, or application types.

Robotair supports nested groupings through subfleets, giving teams fine-grained control over deployment granularity, observability, and rollout safety.

Role in the Platform⿻

Fleets are essential for managing large-scale robotics deployments. Instead of handling robots one by one, Robotair users can target entire fleets or subfleets for software updates, health diagnostics, telemetry collection, or phased rollouts.

Each fleet functions as a deployable unit. You can:

  • Monitor the overall health of a group
  • Apply version-controlled deployments
  • Schedule staged rollouts (e.g., canary deployments)
  • Rollback changes selectively
  • Filter diagnostics and telemetry by fleet structure

Functional Capabilities⿻

  • Organize robots into fleets and nested subfleets
  • Deploy software to a fleet or individual subfleets
  • Monitor performance across defined groups
  • Control update granularity from entire operations down to individual roles or regions

Fleet Hierarchy and Control Model⿻

The diagram below illustrates a structured Robotair deployment with multiple levels of fleet organization:

flowchart TD
    subgraph Robotair[Robotair Fleets]
    end

    subgraph Fleet_A["Fleet: WarehouseBots"]
        Sub1[Subfleet: Region-East] --> R1[Robot 001]
        Sub2[Subfleet: Region-West] --> R2[Robot 002]
        Sub2 --> R3[Robot 003]
    end

    subgraph Fleet_B["Fleet: OutdoorBots"]
        Sub3[Subfleet: Region-North] --> R4[Robot 004]
        Sub4[Subfleet: Region-South] --> R5[Robot 005]
    end

    Robotair --> Fleet_A
    Robotair --> Fleet_B
    Robotair --> Fleet_A
    Robotair --> Fleet_B

This model enables Robotair to broadcast a deployment to an entire fleet, or to precisely target a smaller subfleet for validation before a full rollout. Telemetry and health metrics can likewise be filtered at any level of the hierarchy.