Skip to main content
Omnitracs Knowledge Base

Hours of Service 5.15 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 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.
  • Users who would change the driver's rule set in the driver admin page to determine available hours, will no longer have this functionality. This will now create a Canadian ELD Event on the drivers log for operating zone change which is not permitted by an Admin user under Canadian ELD Technical standards.

DriverAdmin_NewAccount.png
 

Note: Changes on the host have been made to record Canadian ELD Cycle Change events in preparation for the upcoming 11xx IVG release where drivers will have the ability to change their Canadian cycle after satisfying the reset requirements.

Additional changes will be released in June, prior to Canadian ELD, which will disable Canadian Cycle change for the driver after initial setup. At that time, web services will be updated to prevent changes to the drivers Canadian Cycle.

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 DA11xx is released.

Notes:

  • 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.

DriverAdmin_AccountSaved.png

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).

Edit_DriverDetails.png

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

EditOperatingZone.png

To split the time period, select the scissors icon.

EditOperatingZone2.png

Additional HOS Updates

  • Admin 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.
  • To comply with Canadian ELD Technical Standards, Off-Duty deferral is now available for all drivers. To that end, the Fleet option for Off-Duty deferral has been removed from the HOS Setup tab and all drivers are allowed Off-Duty deferral by default. 
  • Unidentified Driver Intermediate Events are now included in the Canadian and U.S. ELD generated eRODS and output files. 
  • The Canada North rules engine has been updated so that it limits drivers to 15 hours of driving per shift, not 15 hours of driving per day.

FMCSA Sleeper Berth Fixes on Host and Mobile

The following firmware versions are affected:

  • Host 5.16
  • IVG DA1011R
  • MCP 50 CA1398R
  • MCP 200/110 AA1837R
Sleeper Berth Pairing

In prior versions, the host and mobile didn't grant the split sleeper berth if the driver was in violation before the second portion of the split. However, the split sleeper pairing should be granted even if the driver is in violation.

If the driver has a valid split—for example, 7 hours in SB and 3 hours off duty or 8 hours in SB and 2 hours off duty, amounting to at least 10 hours—the system will allow the driver to utilize the split and recalculate with optimistic hours once the second split is satisfied. 

Rules Engine Updates

When the driver has paired more than 8 hours in Sleeper Berth with a shorter 2 hours sleeper and a 3 hours off-duty period, the rules engine will allow the pairing of the two larger periods and calculate clocks using the most optimal pairing, while preventing violations.

Additional 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-3559 Some users received an ELD confirmation request when they selected the Vehicles tab. This issue has been resolved.
OHOS-4935 Hours of Service was incorrectly retaining some drivers who had been inactive for an extended period of time. This issue has been resolved.
OHOS-4665 The "No CoDriver” option was missing from the Vehicles tab when users tried to assign UVA. This issue has been resolved.
OHOS-4597 Some customers reported that when they tried to unassign driving time, nothing happened when they selected the Continue button on the confirmation window; they could not complete the process of unassigning the drive time and did not receive a warning message. This issue has been resolved.
OHOS-4334 Users were able to delete depots even when there were users associated with the depot. This issue has been resolved.
OHOS-4094 Some customers reported receiving HOS violations alert emails for drivers who were not in violation. To avoid sending false alerts, email alerts have been updated to use optimistic clocks.
OHOS-2445 To resolve an issue with dropped return messages from the mobile device, the Tractor ID is now randomly generated by the system when users create a new vehicle. In addition, users will need to change the Tractor ID before they can remove a unit.
OHOS-969 In some cases, when there was an error in the time zone conversion, not all duty statuses were included in the Driver Log Export report. This issue has been corrected.
OHOS-93 Some customers reported that vehicles that had been inactive for more than six months were still showing up in HOS reports. This issue has been resolved.
OHOS-51 Users were not able to generate an ERODS file during a Communication Sensor Failure (that is, when the mobile has not communicated with the host over an extended period of time). Now the host will block an ERODS file transfer if it includes a day when the driver's current status was CSF, but the file can be sent after the CSF status clears, whether or not the status is removed from the driver's logs.
OHOS-38 An issue that caused the ERODS Status Report to be blank for some customers has been resolved.
  • Was this article helpful?