Skip to main content
Omnitracs Knowledge Base

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

The following new features have been implemented in support of Canadian ELD requirements.

Driver Swap Requirements

OHOS-4240

To meet Canadian ELD requirements and be in compliance with regulations, driver swaps are now limited to driving events that have a co-driver, and the swap will be restricted to the existing co-driver. To support this requirement, the following changes have been made to the existing swap functionality:

  • In the Driver Details window, the Swap button will be unavailable if the driver does not have a co-driver.
  • A driver swap defaults to the existing co-driver. The Co-driver field will be grayed out so it cannot be edited.
  • The host will fail a requested swap if the co-driver is not authenticated. 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 log. 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.
  • The swap will remain in a pending status until the co-driver accepts or rejects the changes.
  • Logs will be forwarded to Driver 2 (the co-driver who is receiving the swap) when the message from Driver 1 (the driver making the swap) is processed. Driver 2 will then receive a prompt to accept or reject the changes.

Electronic Records of Duty Status Updates

The Hours of Service application now supports electronic Records of Duty Status (ERODS) transfers in Canada. The Canadian ERODS output file will include a CSV file and a PDF generated by the system in accordance with the Canadian ELD technical standards.

Canadian ELD ERODS Requests

OHOS-4624

ERODS file requests are sent to the host, where they are processed and sent to the appropriate safety official, but ERODS output files can also be requested and sent directly from the host. To support this functionality for Canadian ELD ERODS, the ERODS (Request) tab includes a few new features.

Now when you select the ERODS (Request) tab from the Administration menu, you are first prompted to select US Safety Official or Canadian Safety Official as the recipient.

ERODS Request tab - prompt to select governing official

After you make your selection, the ERODS File Transfer Request window opens. 

Please note that the ERODS transfer process is different in Canada than in the U.S. If you select US Safety Official, all files are automatically sent to the FMCSA without any routing information. This process has not changed.

In Canada, however, there is no centralized process for receiving the ERODS output file being transferred. Instead, you must enter an email address, which will be provided by the safety official requesting the ERODS output file, so the file will be routed correctly. When you select Canadian Safety Official as the recipient, the ERODS File Transfer Request window includes a required field where you must enter the email address the safety official provides. In addition, "Email" is the only option available from the Transfer Method list. There is also an optional field where you can enter a comment if the safety official specifies that one should be included in the file.

ERODS Request window - Canadian ERODS

Select the Depot and Driver, then enter the Driver ID, select your date range, and enter the email address supplied by the safety official requesting the ERODS output file. When you select Send, the file is generated, formatted, and sent to the designated email address.

You can select a date range of up to 30 days and can go back as far as six months. If a user requests a Canadian ERODS output file and the file fails to generate, the Admin receives an alert saying, "Unable to generate the ERODS file, please use display or contact Omnitracs support."

U.S. ERODS output files have also been updated to include the following:

  • Unidentified Driver intermediate events that occurred during the specified time period
  • Elapsed Engine Hours of start and end events for Personal Conveyance and Yard Move

Note: When a driver requests the transfer of ERODS from the mobile, the correct routing (U.S. or Canada) is determined automatically based on the Operating Zone in which the driver is operating at the time of the roadside stop.

Driver Log Updates

Admin Users Cannot Edit Uncertified Logs

OHOS-5407

In compliance with U.S. and Canadian ELD requirements, admin users cannot edit a driver's duty status until the logs have been certified by the driver. To support this requirement, the Edit button on the Driver Details page will be grayed out and unavailable for any day that has not been certified by the driver.

Drivers Can Unassign UVA on Mobile

OHOS-5007

Drivers can now unassign UVA that was mistakenly accepted. When they do so, the request is sent to the host to be processed. When the host receives the request:

  • The driver is indicated as the originator of the request.
  • The forward logs are sent to the mobile after the host processes the unassignment request.
  • On the driver's log, the unassigned driving event is marked as inactive and is added back to the UVA list so it can be assigned to another driver. This scenario only occurs for 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.

Fixes

Work Item Number Issue
OHOS-5814 When a new exempt driver was created, portal driver records sometimes included duplicated data. This issue has been resolved.
  • Was this article helpful?