Skip to content
Honeywick Consulting

Metrics

The Metrics panel gives dispatch a live measure of the operation: how the active fleet is being used, the rate work is completing, and whether service commitments are being met. It floats over the map (drag its header to reposition), can be toggled from the panel menu (☰ → Metrics), and opens automatically when a scenario starts.

All figures are computed over the desks currently in view (watched + owned) — the panel is a view of your scope, not a global report. Nothing here is stored in the database: history builds in the browser, one sample per simulated minute, and resets on reload.

The measures

Section titled “The measures”

Utilisation — a stacked bar splitting the active resources (Working, Standby or Called; resting and off-shift resources are excluded) across:

  • Busy — currently servicing project work,
  • Idle — on shift with no active work,
  • Break / Unprod — on a break or other unproductive activity (break stops are identified by the domain’s isBreak property, so all break types group together),
  • STBY / CALL — on standby, or called out from standby.

Each segment takes the same colour the resource list shows for that group, with the count and share in the legend.

Stops / hr — the number of resourced stops forecast to complete in the next hour, divided by the number of working resources not on unproductive activity: a per-productive-resource completion rate.

Drive Time — the average travel time (minutes) across resourced stops’ current legs.

Unresourced — unresourced stops awaiting action now. Future-dated appointments are excluded; this is the backlog that needs attention, not the forward book.

SLA — the percentage of appointments arriving within their earliest–latest window.

Unresourced and SLA are RAG-coloured; a scenario can supply the thresholds used.

Delivery (to) legs are excluded from the stop counts throughout, so multi-leg jobs are not double-counted.

History and charts

Section titled “History and charts”

Expanding the panel (▼ Charts) shows each measure as a time-series, one point per simulated minute, with two kinds of marker:

  • Injection markers — dashed lines where a scenario event fired, so the operational response can be read against its cause.
  • Desk-scope markers — labelled lines wherever the set of desks in view changed. Because the figures are an amalgam of the viewed desks, a step change in a chart often just means the scope changed; the marker makes that explicit, by desk name.
Section titled “Related”