Skip to main content

Analytics, Workshop and the Dashboard

Three read-only surfaces answer "what needs attention?", all computed live from the same mileage and lifing engine — nothing is stored, so they can never drift out of sync.

Dashboard

The home page shows KPI tiles (cars, components, critical mileage, total mileage) and the "Operational alerts" panel:

  • "Blocker" — a part already over a limit (km, hours, events or expiry), or projected to pass one during the next event; also expired car documents. The detail line says "do not run this part".
  • "At risk" — projected to cross a limit within the horizon, or expiring soon.
  • "Inspect" — parts with an open incident flag from a session.
  • "Chassis" — unresolved major/structural chassis findings.

The Horizon control (1–3 events) sets how far ahead projections look, and is shared with each car's Alarms tab. Low-confidence forecasts carry a "low data" tag. Alerts aren't dismissed — they clear when you fix the cause (rebuild the part, acknowledge the incident in the part drawer, renew the document).

Analytics

The Analytics page (current project scope):

  • "EOL Forecast — next replacements" — up to 12 parts due within 6 events, soonest first, with "NEXT EVENT" badges.
  • "Replacement plan" — how many components hit EOL at each upcoming event; budget your rebuild programme from it.
  • "Utilization by Category" — total km per category with average life-used %.

Workshop

The Workshop page lists every part currently in service (sent from the part drawer), grouped by category, with lifetime km and rebuild counts, and a "Mark rebuilt" shortcut per part — the between-events service queue.

Was this page helpful?