Your Telematics Device is designed to collect and respond to status information in your vehicle. The port it is installed in is traditionally used for on-board diagnostics from the vehicle’s manufacturer.
Your Telematics Device responds to changes in your vehicle in the following areas:
Engine warning light on (MIL)
Seat belt usage
Engine hours (PTO)
Vehicle identification number (VIN)
Please be aware that due to differences in vehicle manufacturers, the actual engine information available in your vehicles may vary. We are constantly expanding the number of supported vehicles and features, and regularly distribute firmware updates as necessary.
Note: If when installing your Telematics Device you experience issues such as power loss, vehicle stalls, or engine lights turning on, you may have an incompatible vehicle. Please remove the Telematics Device and contact your authorized reseller.
View engine measurements by selecting Engine & Maintenance > Engine and Device… > Measurements.
Use the Options dialog to set diagnostic, vehicle, and date filters for the data. The filtered measurements will be displayed as a list.
Selecting a row from the list will display specific measurements and the date and time of when they were recorded. Clicking on the red sparkline graphic will take you to the engine data profile graph for the selected measurement.
Tip: Selecting multiple diagnostic types from the Options dialog on the graph page will overlay all selected measurements on the graph.
Authorized resellers have access to a proprietary tool that is used to automatically discover the available engine information for your vehicle. This is done by providing your vehicle identification number (VIN) to your reseller. The VIN is usually located on your dashboard.
In order to determine whether a vehicle is driving, stationary or turned off, the system uses patented technology to examine vehicle battery voltage, movement by use of accelerometer, GPS location and available engine status information. This allows the system to be used in vehicles that do not include an engine bus, in new electric or hybrid vehicles, commercial vans, and large trucks.
Use the following charts as a guide as the compatibility of your vehicles with certain features. For the most up to date information please contact your Authorized Reseller.
In most cases, your Telematics Device automatically records your odometer value.
The IFTA report relies on the odometer history.
For some vehicles, automatic recording of odometer reading may not be available because the manufacturer does not provide it, or it is not yet supported. If unsupported, you can update the odometer in your account by manually entering your vehicle’s current odometer reading.
The application retroactively corrects historical odometer readings based on the most recently entered value (whether manually or automatically recorded). This most recent value is always assumed to be correct and overrides all previous entries or corrections.
Incorrectly entered information can result in inaccurate reports:
Incorrectly copying of or entering of an odometer value might produce negative historical trip values.
When a Telematics Device firmware update introduces automated odometer tracking for a vehicle whose odometer values were previously manually — but incorrectly — entered, it could produce a jump in the value.
If a Telematics Device is moved from one vehicle to another, but the old vehicle was not marked as “historical”, then odometer readings for multiple vehicles are combined. This could result in sudden jumps or past negative trips.
Double check your manual odometer readings and entries.
When permanently transferring your Telematics Device to a new vehicle, set the previous vehicle to historical to preserve your location data, and then create a new vehicle.
An odometer offset reflects the absolute difference between the mileage displayed on a vehicle’s dashboard and the mileage provided by a vehicle’s on-board computer. An odometer factor is the multiplicative difference between the mileage displayed on a vehicle’s dashboard and the mileage provided by a vehicle’s on-board computer.
Both settings can be adjusted within the application to correct any inaccuracies experienced when engine data is collected.
To access these settings, navigate to the Vehicle Edit page and click the +More Details button. For an in-depth explanation regarding these setting, see this document.
The Fuel Usage Report provides a summary of the fuel economy, the travel distance, and the monthly fuel usage of selected vehicles. It can be accessed by navigating to Engine & Maintenance > Fuel Usage.
The Options dropdown allows you to filter the report by vehicle and time period. Additionally, the Sub-Periods option can be used to narrow down the report to daily or weekly results.
Once the report is generated, clicking on a row from the list will take you to a particular fill-up or the set of fill-ups associated with your chosen sort order. Alternatively, you can select the Fill-Ups button to view all fill-ups associated with the selected filters.
A fill-up event occurs every time fuel is added to the vehicle. The Fill-Ups Report displays all fill-up events for a selected time period.
When sorted by vehicle or driver, the heading of every vehicle row provides a brief summary of the average fuel economy, the total fuel added for that fill-up event, and the total cost of all fill-ups for the selected time period.
Selecting the graph icon to the right of the heading will display the fill-ups graph for the time period.
Clicking the icon to the right of each subsequent row will display the trip leading up to the stop where the fill-up occurred.
Telematics data is used to validate imported fuel transactions. A yellow warning icon will be displayed for any fill-up row that does not meet validation criteria. Hovering the cursor over the icon will display the reason why the system flagged the fill-up.
Selecting a row from the fill-ups report will show the details of that particular fill-up event. A matching fuel transaction will also be shown if available.
Rows are highlighted in yellow when the fuel transaction cannot be validated against telematics data.
The fill-ups graph can be used to validate a fill-up that has been flagged as suspicious.
The image above illustrates a fuel transaction event where the fuel level of the car (red line) does not increase together with the blue line. Generally, such an instance indicates suspicious activity associated with that particular fill-up.
The blue line is influenced by three factors: the fuel transaction import, the fuel tank level as reported by the vehicle, and the total fuel used as reported by the vehicle. Each dot on the blue line indicates a vehicle stop.
The red line is influenced only by the fuel tank level as reported by the vehicle. The accuracy of the red line will depend on the vehicle and manufacturer.
The two lines should follow a similar pattern under regular driving and refueling. However, because the blue line changes with imported transaction information, it is possible that the blue line may rise when the red line does not, indicating a scenario like the following:
There was an instance of card sharing — a driver forgot his fuel card and another driver let him use theirs.
The fuel card is associated with the wrong vehicle.
A driver has used the fuel card to fill a personal vehicle or a jerry can.
Fuel card importing is vendor agnostic. Most fuel card providers will supply fuel transaction data in .csv or .xls file formats. Each row of the transaction file represents a separate fuel card transaction, with the columns indicating values like cost, volume, location, vehicle, etc. Fuel transactions can be imported using any of the methods below:
An Add-In has been developed to assist in importing fuel card data from .csv/.xls files. Two formats are supported: the WEX master file and a generic format.
Integrate the Fuel Transaction Import Add-In into your database.
Select Engine & Maintenance > Fuel Transaction Import.
Click the Browse button and choose a .csv/.xls file of the appropriate format. Note: .xlsx files must be converted to .xls files before importing.
Select the Load File button.
The Add-In will begin parsing the file. When completed, the first ten records will be previewed and the Import button will be enabled.
Some files may contain information for multiple fuel card accounts. In these cases you can select the account whose data you wish to import from the dropdown menu. Only the data rows with the selected account name will be imported into the database.
Click the Import button to import the selected data. The Add-In will notify you when the process has completed or if an error has occurred.
The SDK documentation contains examples of adding, removing, setting, and searching for fuel transactions, along with information about the object structure. Potential use cases for using the API might be:
Developing a small application that monitors an FTP site for new files. Once new files appear, it processes and adds them to a database.
Fuel card system integration with the API.