Skip to main content
Omnitracs Knowledge Base

Hours of Service 5.14 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 host 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 MCPs.

New Features

Updates to Driver Rule Setup

The Current Rule Set section of the Driver Administration page has been updated and renamed to comply with the new Current Operating Zone requirements for Canadian ELD. Previously, admin users could modify the Current Rule Set for the driver between Canadian, USA, and intrastate rule sets as applicable; now admin users can only configure the Operating Zone during the initial setup of a driver. Drivers are the only users who can move between a Canadian or U.S. operating zone after the driver setup is completed.

Transitions to and from intrastate and federal U.S. regulations are still controlled only by admin users and only for drivers who need to move between intrastate regulations and U.S. federal rules.

  • To configure the Operating Zone, select the driver's operating zone—USA, Canada South, or Canada North—in the Current Operating Zone section.
  • To change a driver's rule set from U.S. federal rules to intrastate rules, select the appropriate state under Intrastate. To switch back to federal rules, select the Return to Federal Rules button.
    The intrastate option is only available for drivers who are currently in the USA operating zone and who are enabled for intrastate rules.

    Driver Admin window - Current Operating Zone section highlighted

Editing Operating Zones

Admin users will be able to edit Operating Zone changes on the host, but this will only be required for Canadian ELD drivers when necessary.

This functionality will be supported on the IVG when version DA1013R is released.

Note: U.S. and Canadian settings can only be configured in this window when you first set up a new driver. After the account is created and saved, you are not able to select a different operating zone from this window.

Driver Administration window - existing account, operating zone fields unavailable

If you need to make changes later, you can edit a previous Operating Zone from the Driver Details window in the same way you edit duty status changes. Note that you can only edit previous Operating Zones, not the current one (as is the case with editing duty statuses).

Driver Details window

You can edit the entire period during which the driver was using that operating zone.

Edit Operating Zone

To split the time period, select the scissors icon.

Edit Operating Zone - split time period

Additional HOS Updates

  • Host users can now edit Yard Move and Personal Conveyance from the Driver Details window.
  • The License Number field is now required in the Driver Administration window.
  • The Canadian city database has been updated.

Fixes

Work Item Number Issue
OHOS-55 Text referring to pending clock-in and clock-out activities has been removed from the driver portal.
OHOS-65 An issue that occasionally resulted in incorrect values in the Odometer Jumps report has been resolved.
OHOS-1067 If the mobile unit was unplugged from the vehicles, the Odometer Jumps report did not always record the event. This issue has been resolved.
  • Was this article helpful?