How to monitor fleet fuel use and idling
Fleet fuel monitoring combines available vehicle fuel data, mileage, engine state, journeys and stops to create comparable trends by vehicle. Its purpose is to identify deviations and idling that need review; an anomaly alone does not prove theft, a fault or driver misconduct.
- Published
- Updated
Five rules for interpreting fuel data correctly
The value is not an isolated number but the context needed to interpret it.
Key takeaways
- Compare vehicles in the same class and with similar duties.
- Normalise fuel use by mileage, engine hours or another unit that matches the work.
- Separate idling, operational stops and driving.
- Review a trend across periods before classifying a deviation.
- Confirm signal compatibility and quality before building financial controls.
What can a fleet fuel monitoring system measure?
The answer varies by vehicle: CAN bus and other connections expose only compatible, available signals.
Fuel use and mileage
Fuel use becomes interpretable when it is read alongside mileage and a time period. Litres per 100 km can suit road vehicles; engine hours or work-related units may describe equipment that performs much of its work while stationary.
Engine on while stationary
Engine state and movement distinguish a stop with the engine off from idling. The record indicates where to investigate; operating context shows whether the engine was avoidably running or was needed for the service.
Trends and deviations
Comparing the same vehicle over time and comparable vehicles can reveal persistent changes. Load, route, traffic, weather, maintenance and driving style may all contribute, so no single factor should be declared the cause without investigation.
How to move from invoices to vehicle-level fuel control
The monthly total shows what was spent; vehicle-level data helps explain where and why to investigate.
1. Define a consistent baseline
Group vehicles by class and duty. A long-haul tractor, an urban van and a machine should not share one threshold because they perform different work.
2. Connect fuel use, work and context
Read available fuel consumption, mileage, engine hours where present, journeys, stops and idling together. Every comparison should refer to the same time interval.
3. Look for persistent deviations
A single change may result from the data or the duty. A continuing trend merits checks on the vehicle, route, maintenance and operational behaviour.
4. Record the action
Record whether a deviation led to a technical check, process review or no action. Without an outcome, the same alert is investigated from scratch each time.
How to monitor idling without creating false positives
Not all idling is waste: the comparison must consider vehicle type, duty and location.
Distinguish stop types
| Event | Observable data | Operational question |
|---|---|---|
| Engine-off stop | Vehicle stationary, engine inactive | Is the duration consistent with the service? |
| Idling | Vehicle stationary, engine active | Was the engine needed to power equipment or a service? |
| Stop inside a geofence | Dwell time in a defined area | Is it a depot, customer, jobsite or unexpected area? |
| Recurring event | The same pattern across several days | Is a process, coaching or technical check needed? |
CAN bus, tank level and fuel probes: what must be verified first
CAN bus does not mean universal fuel-level availability, and a probe should not be assumed unless it is documented in the project.
CAN bus exposes what the vehicle makes available
The model, body configuration, protocol and connection determine which signals can be read. It is therefore incorrect to publish one accuracy figure or promise identical data for every vehicle.
Consumption is not tank level
A fuel-use trend can expose a deviation, but it does not automatically quantify a sudden tank-level drop. Monitoring tank level, dual tanks or possible removal requires a specific technical configuration that must be verified.
An anomaly starts an investigation
Journey, location, time, documented refuelling, engine state and maintenance help reconstruct context. The platform supports analysis; the cause must be confirmed with appropriate evidence and checks.
Detection is not prevention
| Action | Outcome | Limit |
|---|---|---|
| Detect | Observe a change in available data | Depends on signal and resolution |
| Alert | Send a notification from a configured rule | The alert does not prove the cause |
| Analyse | Connect the change, refuelling, location and history | Requires human verification |
| Prevent | Physically stop removal | Not a promise of the platform |
Technical sources for CAN
ISO 11898-1 describes the CAN data-link layer, while SAE J1939 describes a communications family used in heavy-duty vehicles. The standards do not determine which fuel signals every vehicle exposes.
Which actions can a fuel report support?
A report is useful when every deviation leads to a proportionate check and a recorded outcome.
Possible actions
- Check a vehicle whose fuel use rises against its own history
- Review recurring idling at a location or during a time window
- Compare like-for-like vehicles before reassigning work or scheduling maintenance
- Read vehicle-allocated invoices alongside available mileage and consumption
- Measure the next period after an intervention without promising a generic percentage
Questions to resolve before using fuel data
Compatibility, accuracy and limitations explained without absolute promises.
Which data is needed to monitor fleet fuel consumption?
At minimum, you need fuel use available from the vehicle, mileage, a time period and operating context. Engine state, idle time, journey and vehicle class help distinguish explainable consumption from a deviation that needs review. Actual coverage depends on the vehicle, device and configuration.
How accurate is fuel consumption read from CAN bus?
There is no single accuracy figure that applies to every vehicle. The data depends on what the control unit exposes, the protocol, model, device and configuration. Data quality should be verified for each vehicle class before it is used for financial control or a formal challenge.
Does fuel consumption data prove fuel theft?
No. Abnormal consumption or a deviation is a signal to investigate, not conclusive evidence of theft. Detecting a level drop or quantifying removed fuel may require specific signals or sensors whose availability must be verified for the vehicle and project.
What is idle time and why should it be separated from stops?
Idle time is the period when the engine remains on while the vehicle is not moving. A stop can happen with the engine off and may be required by the service. Separating the two helps investigate waste or operational needs without treating every stop as a problem.
Can fuel invoices be connected with vehicle data?
Zenit documents fuel-invoice ingestion and allocation by vehicle, which can be read alongside available mileage and fuel-use data. This does not automatically mean matching every fuel-card transaction to the litres entering a tank; that capability needs a separate technical check.
Start with the vehicles, not a promised accuracy figure
During a demo, the Zenit team can review vehicle classes, available signals, control objectives and required modules before reports or alerts are defined.
- No generic percentageThe baseline and outcome are measured on the configured fleet and technical setup.