Hour Meter and Odometer Tracking: Telemetry, QR and Bulk Entry
Keep meters current so services are never missed
Maintenance triggers, fuel consumption and the availability calculation all rest on an accurate meter reading. Reper Ops collects meter data from three sources: telemetry, QR code entry in the field, and fast bulk entry from the office. Every value is stored in a single history with a source label.
QR entry in the field
The operator scans the QR code on the machine and enters the current meter reading. The meter is also captured on the same screen during refuelling or an inspection.
Automatic feed from telemetry
On connected machines the engine hours are pulled from the provider on a regular basis. The manual entry burden disappears.
Fast bulk entry
Values for several machines can be entered one after another from a single screen. The weekly round is recorded in minutes.
Source labelling
Every reading is tagged as telemetry, mobile entry or bulk entry. Where an inconsistent value came from is always clear.
Missing meter alerts
Notifications are raised for machines with no reading entered for a long time. Meter gaps are closed before they disrupt the maintenance plan.
How hour meter and odometer tracking works
The meter type is set by machine group: engine hours on heavy equipment, kilometres on trucks. Values arrive from three sources. On machines with a telemetry connection, engine hours are pulled from the provider on a regular basis and no manual entry is needed. In the field, the operator scans the QR code on the machine and enters the current value; a meter reading entered during refuelling is also added to the same history as a reading. In the office, the machine is selected on the Meter Entry page, the last value is shown on screen, the new value is entered and the record appears on the machine card immediately.
For bulk entry, the import button on the Meter Entry page is used; an Excel file matching the template is selected, the matched machines and values are checked in the preview, and the records are processed in bulk once confirmed.
Data quality and control
Meter values cannot run backwards; if a value lower than the last reading is entered, the system raises an error, and the server message is also shown on a record sitting in the offline queue. An authorised user can correct a faulty record, and the change is written to the audit trail with who did it and when. Every reading is tagged with a telemetry, mobile entry or bulk entry source. The Engine Hours page under Checklists lists machines with no meter reading at all, machines showing zero and machines not updated for a long time; a scan that runs every morning raises a notification for stale meters. The Tracking page shows the last position, engine hours and data source for machines with telemetry, and the Engine Hours button downloads the latest values for every machine as Excel.
How it connects to the other modules
The meter is the most fundamental data in the system. Maintenance program targets are calculated from the current reading; as the meter updates, the hours remaining and the work order triggers are refreshed. The fuel-per-hour report derives litres per engine hour from the meter, and the warranty hours check looks at the meter when a fault is raised. The difference in meter readings between fitting and removal gives a tire's service life. The faults per 100 hours figure in operator performance is divided by the engine hours in the assignment period. A closing meter reading is requested on the work order because the next service target depends on it.
Who it is for
It was designed for fleets running a mix of machines with and without telemetry. The operator enters the value with a QR code at the end of the shift, the site supervisor makes a bulk entry after the weekly round, and the maintenance manager closes data gaps by working through the missing meter list. A weekly checklist routine keeps data quality high and stops service timing from drifting.
- 1
Define the meter type
Engine hours or an odometer is selected according to the machine group.
- 2
Values are collected
Telemetry, QR field entry and bulk entry all write to the same history.
- 3
The triggers run
Service thresholds, consumption figures and reports use the current value.
FAQ
What happens on a machine with no telemetry
The meter is recorded from the field with a QR code or from the fast bulk entry screen in the office. Both methods feed the same meter history.
Can a value entered incorrectly be corrected
An authorised user can correct the record, and the change is written to the audit trail with who did it and when. Past readings are never deleted, they stay traceable.