Reports and analytics
Five analytics screens answer "who, how much and how well" for each area. Links to them appear in the sidebar under Reports while the dashboard is open.
How the analytics screens are built
All five share one layout — learn one and you know the rest.
Header — the report name and the count of selected objects, for example "24 of 120 vehicles". On the right sit Export CSV and Back to dashboard.
Filter bar
- Search — by object name.
- Object selector — All vehicles, All zones, All cameras, All cargo. Narrows the report to a subset.
- All statuses — a status filter.
- Period — a set of buttons, or From / To fields, depending on the report.
The label Sorted by distance shows the current sort.
Table — the main block. Clicking a column header sorts by it; clicking again flips the direction (asc / desc). With nothing matching: "No results match your filters."
Two charts — a breakdown by category, and each selected object's share of the total.
Export downloads the whole current selection, with every filter applied.
Vehicle analytics
Reports → Vehicle analytics, at /analytics/vehicles.
Purpose: "Distance, trips & driving events".
The "By vehicle" table
Subtitle: "Per-vehicle movement & events · click a column to sort".
| Column | Meaning |
|---|---|
| Vehicle | The vehicle name |
| Plate | Registration plate |
| Status | Current state |
| Distance | Distance in the period |
| Trips | Trip count |
| Time moving | Total time in motion |
| Avg trip | Average trip length |
| Events | Event count |
Search: "Search vehicle or plate…". Empty: "No vehicles match your filters."
Charts
- By event type — what the selection's events consist of ("412 events across selection").
- Utilisation — each vehicle's share of fleet distance ("Share of fleet distance · selected vehicles"). It exposes imbalance: a few vehicles carrying a large share while the rest sit idle.
Reading it
High Time moving with low Distance means dense traffic or long waits in congestion. Many Trips with a short Avg trip means distribution work; the reverse means long-haul runs.
Geofence analytics
Reports → Geofence analytics, at /analytics/geofences.
Purpose: "Crossings, dwell & zone alerts".
The "By geofence" table
| Column | Meaning |
|---|---|
| Zone | Name |
| Area | Area in km² |
| Type | Operational, speed zone, restricted |
| Crossings | Total boundary crossings |
| Entries | Entry count |
| Exits | Exit count |
| Avg dwell | Average time inside |
| Alerts | How many times the zone raised an alert |
Search: "Search zone or type…". Empty: "No zones match your filters."
Charts
- By alert type — what the triggers consist of.
- Busiest zones — each zone's share of crossings.
- Crossings by hour — entries and exits by hour of day, with Peak entries at, Peak exits at and Quietest window markers. The bar tooltip reads "08:00 — 14 in · 9 out".
- Speed compliance — for zones with a limit: the share of crossings within it ("within limit" / "violations") summarised as "avg 52 · p95 71".
- Overspeed severity — by how much the limit was exceeded (km/h over) plus Top speeding vehicles in the selected zones.
Reading it
A gap between Entries and Exits means some vehicles were still inside at the end of the period. The p95 figure in speed compliance is more informative than the average: it filters out one-off spikes and shows the speed the fast end of the traffic actually travels at.
Camera analytics
Reports → Camera analytics, at /analytics/cameras.
Purpose: "Fixations, detections & confidence".
The "By camera" table
| Column | Meaning |
|---|---|
| Camera | Name |
| Status | Online / offline |
| Fixations | Vehicle fixation count |
| Detections | Detected object count |
| Avg conf | Average recognition confidence |
| Uptime | Share of time the camera was reachable |
Search: "Search camera…". Empty: "No cameras match your filters."
Charts and lists
- Detections by class — what is actually being recognised: vehicles, people, other ("1,204 detections · avg confidence 91%").
- Fixation share — each camera's contribution to the total fixation count.
- All fixations — a table of the most recent fixations with Time, Camera, Class, Plate / object and Conf. columns. The subtitle spells out the selection: "100 recent · of 3,482 this range (51,200 total) · newest first".
Reading it
Low Uptime with normal Fixations means the camera drops out often but works while it is up; look at the network or power. Many Detections with few Fixations means the camera sees movement but cannot read plates: check the angle, lighting and focus.
Cargo analytics
Reports → Cargo analytics, at /analytics/cargo.
Purpose: "Volume, delivery & on-time SLA".
The "By shipment" table
| Column | Meaning |
|---|---|
| Shipment | Cargo name |
| Status | Planned, in transit, delivered, damaged |
| Volume | Shipment volume |
| Deliveries | Delivery count |
| On-time | Share delivered on time |
| Avg transit | Average delivery time |
Search: "Search shipment…". Empty: "No shipments match your filters."
Charts
- Status breakdown — how many shipments sit in each status ("37 shipments in selection").
- Volume share — each shipment's contribution to the volume moved.
Reading it
A drop in On-time while Avg transit holds steady usually means the planned deadlines were too optimistic, not that transport got worse. Both moving together points to a genuine problem on the route.
Transit on-time
Reports → Transit on-time, at /analytics/transit.
Purpose: "Schedule adherence across routes".
Periods: 7 days, 30 days, 90 days.
Key figures
| Figure | Meaning |
|---|---|
| On-time rate | Percentage of arrivals that met the schedule |
| Arrivals | How many arrivals were recorded |
| Late | Arrivals behind schedule |
| Early | Arrivals ahead of schedule |
| Routes | How many routes have recorded arrivals |
Tables and charts
- By route ("On-time performance per route") with Route, Arrivals, On-time and Late columns.
- Daily on-time ("Share on time per day") — how adherence moves over time.
With no data: "No arrivals recorded yet."
Reading it
A large Early count is not necessarily good news: in public transport, leaving a stop early means passengers missed it. A steady dip on the Daily on-time chart on particular weekdays usually points to recurring congestion rather than driver discipline.
Exporting reports
On every screen Export CSV downloads the selection with all filters and the
current sort applied. The events log and the
fixations page additionally offer .xlsx export.