Hours of Service 5.12 Release Notes

This page documents the January 2020 5.12 Hours of Service host application release.

For previous release notes, click here.

Features and Enhancements

Administrators can now unassign previously assigned unknown driving events on the portal and with Web services.
The Hours of Service Violation report is now available in Excel and CSV format.
The nightly purge has been updated to include older vehicles that have never communicated with a device.
A new feature allows customers to control the 16-hour exemption by driver. Please note that this feature requires firmware that is not yet available on the telematic devices. The firmware is expected to be released as follows:
- IVG DA0964R: End of January 2020
- MCP 50 and MCP 110/200: Spring 2020
The Driver Admin window now includes an Allow 16 Hour Exemption radio button that lets administrators enable the 16-hour exemption at the driver level. This option prevents drivers who do not qualify for the exemption from trying to use it.
When the Edit Audit report is run by driver group, it now includes the driver ID in a separate column.
A one-time update has been made to enable the 16-hour exemption for all drivers in a fleet that has already been enabled for 16-hour exemption use.
The Unassigned Driving Report now includes Rejected Unassigned driving. Please note that some columns will not populate with data until the telematic devices receive the firmware required. The firmware is not yet available but is expected to be released as follows:
- IVG DA0964R: End of January 2020
- MCP 50 and MCP 110/200: Spring 2020
A new Rejected Unassigned Driving Events report provides the driver ID and a reason for the rejection. Please note that some columns will not populate with data until the telematic devices receive the firmware required. The firmware is not yet available but is expected to be released as follows:
- IVG DA0964R: End of January 2020
- MCP 50 and MCP 110/200: Spring 2020
Administrators who assign or accept UVA can now edit the location of a status that occurred after an unassigned driving event was assigned. This allows users to accurately reflect the driver’s location in the log.
Updates have been made to improve the speed with which logs are delivered to mobile devices.
In order to fix some issues in the Events Report, all events are now grouped by driver, and each driver's name and ID are displayed only once at the top of the driver's block of events.

Fixes

The system has been updated to automatically correct corrupt log files when a driver logs in to the driver portal.
The system no longer removes the primary driver from an assigned UVA event if the co-driver assignment has been rejected.
Spelling errors in the Diagnostic and Malfunction report have been corrected.
The Web Services error message has been updated to provide more detailed information about the reason for the failure.
A fix has been made to correct an issue that occasionally caused the location displayed on the driver chart to differ from the location displayed in the driver details window.
A blank column in the Excel version of the Driver Log Export report has been removed.
If a driver claims an unassigned driving event that overlaps with a non-driving event that has a manually entered tractor ID, the assigned driving event no longer displays the manually entered tractor ID.
On rare occasions, using the driver portal to clock out caused a status to be uneditable from the host after the driver had certified. This issue has been resolved.

Previous Releases

Omnitracs endeavors to ensure that the information in this document is correct and fairly stated, but Omnitracs is not liable for any errors or omissions. Published information may not be up to date, and it is important to confirm current status with Omnitracs. Specifications subject to change without notice.

This technical data may be subject to U.S. and international export, re-export or transfer (export) laws. Diversion contrary to U.S. and international law is strictly prohibited.