Vehicle Service Odometers Report
Vehicle number – refers to the unique identifier assigned to each vehicle within the system. This number is essential for tracking and managing vehicle transactions effectively. During any transaction, the vehicle number is used to associate the recorded data with the specific vehicle involved, ensuring accurate maintenance records, fuel consumption tracking, and odometer readings.
Service Date/Time – the date and time of the transaction, The service date and time are automatically captured within the system at the moment of the transaction, providing a reliable and consistent reference point for all subsequent analyses and reporting activities.
Protected odometer – commonly referred to as the Current LTD odometer, this odometer is safeguarded against inaccuracies in raw data entry. FLEETWATCH strongly advises using this odometer for importing data into vehicle maintenance software or Enterprise Asset Management (EAM) systems.
Expected on-board odometer – The expected on-board odometer represents the system's estimation of what the vehicle's odometer or other measurement should read. It serves a crucial role in synchronizing odometer readings within the system (refer to Odometer Syncing.pdf in the Help Section for more details). However, it is important to note that this odometer should generally not be utilized for importing data into the vehicle maintenance system.
Actual Odometer Input – The Actual Odometer Input refers to the odometer value recorded in the system during the transaction. This value can be obtained from various sources, including a trip recorder, a data logger, or manual entry via the RIH keypad. The Actual Odometer Source identifies the origin of this odometer reading. It is essential to note that this odometer value should not be used for importing data into the vehicle maintenance system.
Actual Odometer Source – the origin of the actual odometer input for this transaction, which may include a trip recorder, keypad entry, or data logger.
Previous Input Odometer – the odometer reading recorded during the transaction that occurred before the current actual odometer input. This value can originate from a trip recorder, data logger, or manual entry via the keypad, and serves as the last recorded odometer input in the system..
Protected Miles Run – the miles run added to the Protected Odometer (Current LTD odometer) during this transaction. See the next column, “Odom Calc?”. If “Yes”, the protected miles run will be equal to the Total Fuel * Avg MPG. If “No”, protected miles run will be the difference between the Actual Odometer Input and the Previous Odometer Input.
Odom Calc? – If the response is "Yes," it indicates that the Initial Calc MPG has failed to meet the upper or lower MPG limits established in the vehicle's fuel/fluid properties. This failure may occur due to several factors, such as an inaccurate odometer reading caused by a malfunctioning trip recorder, human error, instances of short-fueling a bus, topping off fuel, or situations where no odometer input was provided (e.g., a zero entry for the Actual Odometer Input). Conversely, if the answer is "No," it signifies that the Initial Calc MPG is within the acceptable bounds. Even if the MPG falls outside these limits, the vehicle must have traveled a reasonable distance, and no issues with RF equipment have been detected, thereby leaving the data unmodified. In cases where the Odom Calc is marked "Yes," and the calculated miles run exceed the Max Jump threshold—potentially due to excessive fuel consumption—the system will default to using the Max Jump value for miles run instead of calculating it based on fuel multiplied by MPG. This precaution helps avoid significant discrepancies in mileage caused by multiple fueling events for a single vehicle. The Max Jump mileage, or Max Trip Distance Without Fuel Bounding setting, can be found in the Fuel/Fluid properties of the vehicle. This number should be a reasonable distance a vehicle travels between transactions. Default is 400 for revenue coaches. If the Max Jump is 0, it will record 0 miles per transaction. Use a high enough number to avoid restricting mileage too much.
Mile Run Flag – The status "Unaltered" or a blank entry signifies that the data displayed is accurate and unmodified. Conversely, the label "No odometer provided" indicates that there was no Actual Odometer Input recorded in the system, necessitating the calculation of miles run for that transaction based on the Total Fuel consumed multiplied by the Average Miles Per Gallon (Avg MPG).
An "Upper Bound Failure" occurs when the Initial Calculated Miles Per Gallon (Calc MPG) exceeds the upper limit, which may result in a calculated odometer reading if the mileage surpasses the Max Jump threshold or if a malfunctioning RF device is detected. Similarly, a "Lower Bound Failure" indicates that the Initial Calc MPG falls below the lower limit, leading to the same consequences in terms of odometer calculation.
The term "Odom Syncing Up" relates to the Drift Correction column and indicates that the system is adding miles to the Protected Miles Run figure to ensure that the Input Odometer aligns with the Protected Odometer. In contrast, "Odom Syncing Down" denotes a subtraction of miles run to achieve this synchronization between the two odometers.
Engine Hours Input – the engine hours input from a data logger or keypad entry.
Drift Correction – The miles that are either added to or subtracted from the Protected Miles Run during a transaction are determined by the processes known as "Odom Syncing Up" and "Odom Syncing Down." This adjustment is subject to the limitations set by the "Maximum Additional Miles" parameter found in the Mileage Options of the System Monitor Options utility.
Initial Calc MPG – The Initial Calculated Miles Per Gallon (Calc MPG) is determined by taking the difference between the Actual Odometer Input and the Previous Odometer Input, and then dividing that value by the Total Fuel consumed. In cases where no odometer reading is available, the system defaults to using the Average Miles Per Gallon (Avg MPG) instead.
Avg MPG – The Average Miles Per Gallon (Avg MPG) is calculated based on the running average of the most recent transactions where the Initial Calculated Miles Per Gallon (Calc MPG) fell within acceptable limits. It is important to note that Avg MPG does not include any Initial Calc MPGs that fall outside these bounds. You can find the number of transactions considered in this moving average within the Mileage Options section of the System Monitor Options utility, specifically under the MPG Weight setting.
Total Fuel – represents the total volume of fuel used during the transaction.
From RIH? – Indicates whether the transaction was processed directly from the RIH in real-time or was retrieved later from storage, such as an M30 memory card, a manual update utility, or another external source.
RIH Unit – represents the unique identifier of the RIH location where the transaction occurred, which may correspond to a fuel lane, maintenance bay, gate FR, or another external source.