SmartFill can allow the entry of Odometers and meters when a Vehicle or plant is detected at the system.

This article will use Odometers and Vehicles as the asset type. The process is the same if you want an Hourmeter or Plants; just swap the names around when you search for them.

If you're unsure how to add columns to your Asset pages, you can learn how to add columns via this article.

Before we get started, we recommend that you add the below columns to your desired asset page;

• Enable Odometer - Allow/disallow an asset to enter an odometer.
• Odometer - The last reported odometer from the asset.
• Odometer Limit - The maximum distance allowed between transactions. More about that feature here.

There are more columns that you can add that may benefit your odometer reconciliation;

• Last Service Odometer - The last odometer reading when the asset was last serviced.
• Service Interval - The interval that the vehicle should be serviced at.

Once you have added the above columns, your assets page should contain the columns previously mentioned, as shown below.

You can then edit these columns to reflect what your vehicles are currently set to. When a driver uses this tag and enters an odometer, the odometer will be updated on the FMTData web portal.

Odometer/Hourmeter Limit

Odometer/Hourmeter limits restrict an odometer/hourmeter to authorise a value only in a specific range.

Let's assume we have a Vehicle with an Odometer of 15,000 and an Odometer Limit of 1000. This means the driver can only enter an odometer reading of 16,000 or 14,000. If the driver enters a value higher or lower than the expected range, SmartFill will throw an error stating that the odometer reading is incorrect.

If the odometer limit is set to 0, no limit will be forced, and the driver can enter whatever value they like.

It's recommended that the Odometer/Hourmeter Limit remains at 0 until the odometer reading is confirmed and reported correctly on FMTData