Hours of Service 5.16 Release Notes
Canadian ELD Compliance
The introduction of changes to the Hours of Service host application in preparation for compliance with the Canadian ELD mandate provides for functionality in compliance with the Canadian ELD Technical Standards.
Over the next several releases, Hours of Service will introduce additional Canadian ELD functionality that will culminate in the complete Canadian ELD application.
It is possible that Admin users will have complete Canadian ELD functionality before Omnitracs receives third-party certification.
Please note that the Canadian ELD mandate effectively replaces paper logs and requires federally regulated motor carriers to equip their vehicles with compliant, third-party-certified ELDs on or before June 12, 2021. Once the device is certified, the certification body will provide Omnitracs with a certification number. Omnitracs will embed this number in the ELD software in the appropriate data field.
Note: Canadian ELD Certification only applies to the IVG, not MCP devices.
Please refer to the CCMTA website for details about the Canadian ELD Mandate.
New Features
Driver Swap Updates
OHOS-4240
In Hours of Service 5.16, the swap icon in the Driver Details window is now only available if the driving event has a co-driver. If a co-driver does not exist, the icon does not appear:
Co-Driver
No Co-Driver
In addition, the Transfer Driving Record window only allows you to swap the event to the existing co-driver. The This event will be swapped to codriver field is pre-populated with the co-driver's name and ID and the field is grayed out and cannot be edited.
ELD HOS regulation 4.3.2.8.2 for the U.S. and Canada has always restricted the swapping of erroneously recorded drive time to an authenticated co-driver in a team driver operation. This new functionality simply enforces the restriction.
As was the case prior to this release, when an admin user requests a swap, logs are forwarded to both drivers, who are notified of an edit request for their logs. Both drivers are then prompted to accept or reject the changes. The swap will remain in a pending status until both drivers accept the changes.
In the event of a failed swap, the host will send an alert to the mobile telling the driver the swap has failed due to pre-existing driving on the co-driver's log or due to attempting to edit a current duty status. The alert provides the Driver ID of the driver who requested the swap, a list of the driving statuses that failed to swap, and a reason for each failure. The message to the mobile will then cause locked events to be unlocked.
Driver Swaps on the IVG (Upcoming Feature)
In an upcoming release of the IVG, drivers will have the ability to swap automatically recorded drive time to an authenticated co-driver in a team driving situation. Like the swap icon on the host, the Swap button (on the Certify tab) will only be available for driving events that have a co-driver associated with them. When the driver requests a swap, a message will go from the mobile to the host. The swap will remain in a pending status on the logs until both drivers confirm or reject the changes.
The broadcast of this IVG upgrade will begin in April 2021. Until that time, driver swaps will function as they currently do. Release notes with more information about this feature will be available in the Knowledge Base shortly before the upgrade is available for customers.
Driver Log Changes
Drivers Unassign UVA on Mobile
OHOS-5007
In support of U.S. and Canadian ELD requirements and in preparation for Canadian ELD certification, an upcoming IVG release will give drivers the ability to unassign UVA that was mistakenly accepted. When they do so, the request will be sent to the host to be processed. When the host receives the request:
- The driver will be indicated as the originator of the request.
- The forward logs will be sent to the mobile after the host processes the unassignment request.
- On the driver's log, the unassigned driving event will be marked as inactive and will be added back to the UVA list so it can be assigned to another driver. This will only apply to events that occurred up to 15 days prior to the current day in Canada and 8 days prior to the current day in the U.S.
Historical Record of Vehicle ID Updates
OHOS-4609
In compliance with the requirements of the Canadian ELD technical standards, drivers are now able to update the Tractor ID on the mobile; when they do so, the ID is also updated on the host.
To track ID updates, the system now maintains a historical record of the Vehicle ID and when it changed. When the host receives a message to update the Vehicle ID, the record will be inserted into the vehicle history. The new record's start time is the end time for the most current record; the end time is the time the change occurred on the mobile.
The Vehicle ID change will carry over to any duty statuses that occur after the change is made.
In addition, the Truck ID will be added to power events so the mobile has the complete Vehicle ID history.