Skip to main content
Omnitracs Knowledge Base

Analytics Manager 1.2 Release Notes


Version 1.2 of the Omnitracs Analytics Manager software reports time data for the State Miles feature using local time zones. In previous releases, State Miles reports listed times in GMT only.

Note: Previous release notes for Analytics Manager referred to releases 4.0–7.0. With this release, the release notes version is revised to match a different system. Therefore, these notes pertain to Analytics Manager version 1.2, even though the previous release notes referred to version 7.0.

User Interface Changes

State Miles Time Values Now Expressed in Local Time

In previous releases, time values for State Miles were expressed in Greenwich Mean Time (GMT). In Analytics Manager 1.2, times are expressed in the local time zone as follows:

  • If the vehicle is assigned to an HOS depot, the local time zone is defined by the location of that HOS depot.
  • If the vehicle is not assigned to an HOS depot, the local time zone is defined by the location of the company headquarters.

Day-level State Miles Reports Include Further Information

In State Miles reports that show vehicle mileage by day, two columns have been added:

  • The local time zone used for each row in the report
  • The source of the local time zone for that row (either HOS depot or company, as outlined above)

How the Upgrade Affects Data Retention

The switch from GMT to local times affects retained data for State Miles in the following manner:

  • Historic State Miles data, gathered before the switch to version 1.2, retains the GMT values associated with it.
  • In reports of this data, the local time is calculated from the GMT value and displayed.
  • The location used for the local time zone is the one assigned to the vehicle at the time of the upgrade to version 1.2.

    Example: A vehicle is assigned to HOS depot A in San Diego when the upgrade occurs. After the upgrade, all historic times for that vehicle will show the local time for San Diego. This is true even if the vehicle was assigned to a depot on the east coast when some of the data was gathered.
  • Before the upgrade, you can see up to a year of historic data, even if your company’s data retention period is smaller.
  • Immediately after the upgrade, you can only see historic data that falls within your retention period.
  • From the upgrade forward, historic data will accumulate until a full year’s data is saved.
  • After a year of data has accumulated, you will again be able to see up to a year of historic data.
  • If you deleted a vehicle at some time during the 12 months prior to the upgrade, when the upgrade occurs, you will no longer have access to that vehicle’s data.


Improved Handling of Bad Odometer Readings

Because of how the vehicle passes odometer readings to the application, erroneous readings occasionally occur. In some cases, the erroneous value is zero and other times it is an extremely high value. The application logic has been changed to replace these values with the previously known good value. In this way, the occasional bad value does not distort the data reporting.

  • Was this article helpful?