New Features

Providing Aliases for Assets and Operators

We added Alias as an asset and operator property you can use as a secondary identifier for information about vehicles, drivers, equipment, and trailers. You’ll see Alias as a new field in the Add/Edit Asset and Operator dialog boxes, as a new filterable column on the Admin - Assets and Admin - Operators screens, and in the import templates. You’ll also be able to search for aliases on the Tracking screen and in reports and use them as alert triggers. One requested use for this was to store whether an asset was owned or leased, which can help you manage when leased assets are due to come off lease and prepare for a new deployment (to prevent underutilization).

Creating Asset and Operator Types

We added the ability for you to create your own asset and operator types via the Add/Edit Group dialog box, using a similar procedure to adding asset and operator categories. After you’ve created new types, you can apply them in the Add/Edit Asset and Operator dialog boxes via the Asset/Operator Type drop-down list (which will display the types belonging to the group the asset or operator is assigned to, plus a None option). This will allow you to use asset and operator types to further categorize these entities, and you’ll be able to search for types on the Tracking screen and in reports and use them as alert triggers.

Note that the default asset types of Vehicle, Machine, Powered, Unpowered, Tool, and Equipment will still be available.

Using Device Input Alerts and Reports

We added the ability to set up alerts based on device input state and state changes, which will enable you to monitor when inputs are used. In the Add/Edit Alert dialog box, you’ll select the alert type by input number (as indicated by the choices iOn Device Input1 Alert, iOn Device Input2 Alert, and so on in the Alert Type drop-down list) and provide the input value as the trigger.

We also added a related Device Input report (in the Exception Reports list), which provides details of specific input events, including descriptions and when, how long, and where they occurred.

WEX Fuel Card Integration

We added WEX fuel card integration, including new Fuel Purchase Detail, Fuel Purchase Summary, and Fuel Purchase Unmatched Records reports (in the Trip, Stop, Location Reports list), which will provide details on when fuel was purchased, which operator/asset used the card, fuel efficiency, fuel costs, and location. The third of these reports (Unmatched Records) will list each fuel purchase instance without a valid iOn asset ID.