A truck, a bus and a generator can belong to the same fleet without doing comparable work. Kilometres help describe transport activity, but say little about a generator powering a site. A single utilisation percentage can hide those differences and make a necessary asset look idle simply because the wrong measure was chosen.
Start by defining the service each asset provides and the capacity you expect it to make available. Transport vehicles may be assessed by distance, completed work or service reliability. Equipment may need engine hours, productive hours or output. Shared reporting is useful, but it should retain the distinctions that make the numbers meaningful.
Define the work each asset is meant to do
For trucks, consider total and loaded distance, completed trips, payload context and time spent waiting. For buses, consider scheduled services completed and punctuality alongside distance, where those fit the operation. For site equipment, examine hours and the work delivered. These are candidate measures, not universal targets. Select them according to the contract and the decisions you need to make.
Define the measurement period and denominator. Hours used divided by hours available differs from hours used divided by all calendar hours. State whether planned maintenance, standby requirements or closed-site periods are excluded. Two asset groups can show the same percentage while using different definitions. A useful report makes those definitions visible before asking managers to compare performance.
Use kilometres, hours and jobs appropriately
Check the underlying data source. Engine hours, ignition time and productive operating time are not interchangeable. An engine running while equipment waits can increase hours without producing work. Verify what the installed device actually reports and supplement it with job records where needed. Keep missing readings visible instead of assigning a precise utilisation score to an incomplete record.
Use kilometres for road-based exposure and hours where operating duration drives service needs, following the manufacturer’s relevant maintenance guidance. Some assets require attention to more than one measure or to calendar time. Do not let a low-distance vehicle skip a service that is due on another basis. Record the applicable maintenance rule for the asset rather than applying a fleet average interval.
Separate availability from productive use
Availability asks whether an asset could perform its assigned role. Productive use asks whether it did so. Keep these separate. A vehicle awaiting repair and a serviceable standby vehicle may both record no completed jobs, but need different decisions. Record downtime reasons such as repair, parts wait, inspection or lack of assigned demand.
In an illustrative construction fleet, a generator may run daily while a truck supports only scheduled material deliveries. More truck kilometres would not automatically improve the project. Check whether its capacity is required for peaks, whether hired capacity is an alternative and what the contract expects. Assets should be evaluated against the service needed, not against an incentive to keep everything moving.
Make allocation and replacement decisions
When low use persists, review scheduling, sharing between sites, rental alternatives and standby obligations. Include the cost and risk of moving an asset before deciding to reassign it. Equipment that is rarely used may still protect a critical service. Document that rationale so low use is understood rather than dismissed or concealed by an adjusted target.
For replacement decisions, combine utilisation with maintenance history, downtime, condition and foreseeable demand. Avoid replacing an asset solely because its current month looks expensive or retaining it solely because it has few kilometres. Compare options on consistent assumptions, including transition costs. Record the decision and revisit it when workload changes.
When evaluating mixed-fleet reporting in AlphaFleet, bring examples from each important asset class and ask what measurements are actually available. A good reporting view lets managers see common responsibilities while keeping distinct service measures. That is how a mixed fleet becomes manageable without pretending every asset earns its keep in the same way.
