How does the Vehicle Service Odometers Report work?
Vehicle Service Odometers Report
What each column in the transaction report means, how the protected odometer is calculated, and which odometer to send to your maintenance system.
Report columns, left to right
1 Vehicle Number 2 Service Date/Time 3 Protected Odometer 4 Expected On-Board Odometer 5 Actual Odometer Input 6 Actual Odometer Source 7 Previous Input Odometer 8 Protected Miles Run 9 Odom Calc? 10 Mile Run Flag 11 Engine Hours Input 12 Drift Correction 13 Initial Calc MPG 14 Avg MPG 15 Total Fuel 16 From RIH? 17 RIH Unit
| Import to EAM / maintenance Protected Odometer | Don't import Expected On-Board Odometer, Actual Odometer Input |
1 Vehicle Number
The vehicle's unique ID in the system. Links each transaction's fuel, odometer and maintenance data to the right vehicle.
2 Service Date/Time
Date and time of the transaction, captured automatically by the system.
3 Protected Odometer Import this one
Also called the Current LTD odometer. Filters out bad raw odometer data, so it's the odometer Fleetwatch recommends for importing into vehicle maintenance or EAM systems.
4 Expected On-Board Odometer Don't import
The system's estimate of what the vehicle's odometer (or other meter) should read. Used for odometer syncing (see Odometer Syncing.pdf in the Help section).
5 Actual Odometer Input Don't import
The raw odometer value received during the transaction.
6 Actual Odometer Source
Where the Actual Odometer Input came from: trip recorder, data logger or RIH keypad.
7 Previous Input Odometer
The Actual Odometer Input from the vehicle's previous transaction.
8 Protected Miles Run
Miles added to the Protected Odometer in this transaction, including any Drift Correction. Before drift correction, it's calculated one of two ways depending on Odom Calc?:
No: Actual Odometer Input − Previous Input Odometer
Yes: Total Fuel × Avg MPG, capped at Max Jump
9 Odom Calc?
"Yes" means the system calculated miles run instead of using the odometer input. This happens when Initial Calc MPG falls outside the vehicle's MPG limits and the input looks unreliable, for example from a faulty trip recorder, keypad error, short-fueling or topping off, or no odometer input (zero entered). "No" means the odometer input was used as-is.
When "Yes," calculated miles are capped at the Max Jump value to prevent inflated mileage, such as from several fuelings in a row. Max Jump (Max Trip Distance Without Fuel Bounding) is set in the vehicle's Fuel/Fluid properties and should be a reasonable distance between transactions. The default for revenue coaches is 400. If Max Jump is 0, every transaction records 0 miles, so set it high enough not to restrict mileage.
10 Mile Run Flag
How miles run was determined:
| Unaltered / blank | Odometer input used as-is. |
| No odometer provided | No input received; miles = Total Fuel × Avg MPG. |
| Upper / Lower Bound Failure | Initial Calc MPG was above or below the vehicle's MPG limit. Miles are calculated if the distance exceeds Max Jump or an RF equipment problem is detected. |
| Odom Syncing Up / Down | Miles are being added to or subtracted from Protected Miles Run to bring the Protected Odometer in line with the input odometer (see Drift Correction). |
11 Engine Hours Input
Engine hours from a data logger or keypad entry.
12 Drift Correction
Miles added (Syncing Up) or subtracted (Syncing Down) from Protected Miles Run to keep the Protected Odometer in sync with the input odometer. Limited by the Maximum Additional Miles setting in System Monitor Options > Mileage Options.
13 Initial Calc MPG
(Actual Odometer Input − Previous Input Odometer) ÷ Total Fuel
If there's no odometer input, Avg MPG is used.
14 Avg MPG
Rolling average of recent Initial Calc MPGs that were within limits; out-of-bounds values are excluded. The number of transactions averaged is set by MPG Weight in System Monitor Options > Mileage Options.
15 Total Fuel
Total fuel dispensed in the transaction.
16 From RIH?
"Yes" if the transaction came from the RIH in real time; "No" if it was loaded later from storage, such as an M30 memory card, the manual update utility or another external source.
17 RIH Unit
ID of the RIH where the transaction occurred (fuel lane, maintenance bay, gate FR, etc.).