Dashboards and anomalies
The analytics module gives you an operational read on the fleet in one place: a KPI dashboard tailored to your role, and a ranked anomaly feed — signals that stand out from the fleet's norm and deserve attention. Both views are computed automatically in the background, so you open ready data instead of waiting for a live calculation.
Who it's for
Visible to the fleet manager, dispatcher, safety manager, finance controller, executive (read-only) and organization administrator. Drivers and technicians have no analytics access — their work is scoped to their own assignments and inspections.
Key concepts
- Benchmark — for three metrics (fleet utilization, uptime/availability, PM compliance) the dashboard shows the actual value alongside two reference points: a typical industry value and a "world-class" target for top-performing fleets, so a number has context instead of standing alone.
- Anomaly score — every signal in the anomaly feed carries a score from 0 to 1; the higher it is, the more urgently it warrants attention. The feed sorts signals by score, descending.
The role-tailored KPI dashboard
The dashboard defaults to the widget set that matches your role in the organization, but you can switch to any of five views: manager (utilization, uptime, PM compliance, work-order backlog, incident count), dispatcher (utilization, active/available vehicles, distance driven), safety (incidents, uptime, PM compliance), finance (total operating cost, cost per km, PM compliance) and executive (utilization, uptime, cost per km, total cost, incidents). Switching the view doesn't change your permissions — it's just a different selection of cards over the same underlying data. Every card shows when it was last computed, and the three benchmarked metrics also show a progress bar against the target.
The anomaly feed
Below the dashboard sits a list of signals that deviate from the fleet's norm, sorted from most significant: fuel fraud caught by reconciliation, work orders costing far more than the fleet average, available vehicles with no telematics activity at all in the analysis window, telematics devices that have gone quiet for too long, and vehicles with an elevated predicted-maintenance score. Each entry carries a short description and links back to the vehicle or device it concerns — the feed is a starting point for further diagnosis, not a separate module to manage.
In the background
The KPI snapshot is computed once a day per organization (one snapshot per day, never repeated) from the last 30 days of data across the assets, telematics, maintenance, fuel and inspections modules. Right after it, anomaly aggregation runs and replaces the organization's entire feed with freshly computed signals. Some of the same events — a device gone quiet for too long, a new fuel-fraud flag — also reach the notification center for the relevant roles, independently of the dashboard.