Example deliverable

Sample data

Fleet time model / loss analysis

W37 / 2026

Availability

87.4%

Agreed denominator

Utilisation

76.2%

Current week

Operating time

128 hrs

Sample fleet

Weekly performance

Actual Target

W31W32W33W34W35W36W37

Contributors & exceptions

Mechanical downtime
Operational delay
Standby
Uncoded events

Illustrative time-model dashboard using sample data. Category rules and denominators are confirmed before development.

Objective, scope & delivery

The problem to solve

A clear objective before any work starts.

Nobody agrees where the hours went, so availability and utilisation numbers change by who asks.

The starting point is how your team works, not a list of features in Power BI. We establish what needs to change, who relies on the result and how you will judge whether the work has solved the problem.

The scope below sets the boundary for mining time model reporting. Before work starts, we check the current process, available information and practical constraints with you. Gaps and assumptions are made visible so that the quote reflects the work actually required.

What the work needs to address

  • Use one agreed set of time categories across fleet reporting.
  • Distinguish equipment downtime from operational delays and standby.
  • Trace availability and utilisation back to the coded events.