> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperwisor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fleet Manager

> One widget. Any device. Any industry. A general-purpose operational layer for monitoring devices at scale.

Most fleet tools are built for one vertical — buses, trucks, drones — and hardcode
the data model. The Hyperwisor **Fleet Manager** widget makes zero assumptions
about what your devices are. A bus operator, a soil-sensor network, a drone fleet,
and a solar farm all use the same widget. The only difference is the
[field mapping](/fleet/field-mapping) they configure.

Drop it onto a [custom dashboard](/custom-dashboard/overview) and it becomes your
operational layer for many devices at once.

## The six views

Enable any combination per dashboard:

| View          | What it does                                                                           |
| ------------- | -------------------------------------------------------------------------------------- |
| **Map**       | Live map — every device as a direction-aware marker. Trails, routes, click-to-inspect. |
| **Devices**   | Searchable, filterable device table with status, last-seen, and firmware.              |
| **Groups**    | Organize devices into named groups with per-group health.                              |
| **Commands**  | Send a command to a device, a group, or the whole fleet.                               |
| **Firmware**  | Version distribution across the fleet; flags outdated devices.                         |
| **Analytics** | Uptime %, online/offline counts, category breakdown, custom metrics.                   |

Each view toggles independently — a dispatcher might show only **Map + Commands**;
a maintenance engineer only **Firmware + Analytics**.

## The data contract

A device needs to satisfy one rule: **emit a message with a device identifier and
at least one piece of data.** Everything else is optional and unlocks more:

```
REQUIRED:  device identifier      (any key — you map it)
OPTIONAL:  lat / lng              → enables the Map view
OPTIONAL:  speed / heading        → enriches the map marker
OPTIONAL:  firmware_version       → enables the Firmware view
OPTIONAL:  status                 → drives marker / row color
OPTIONAL:  __meta: { any: ... }   → surfaces in Analytics + detail rows
```

## Progressive enhancement

A device emitting only `{ id, lat, lng }` gets a working Map. Add `speed` → markers
rotate. Add `__meta` → popups enrich. Add `firmware_version` → the Firmware view
activates. Each field you add unlocks more, automatically — no redeploy.

<Card title="Next: Field Mapping" icon="diagram-project" href="/fleet/field-mapping">
  Map any payload shape to Fleet's concepts.
</Card>