Skip to main content
Omnitracs Knowledge Base

Omnitracs One 6.6 Release Notes

Overview

We are pleased to announce that the OT1 6.60 Host and Mobile release which includes XRS Mobile 6.40, 6.50, and 6.60 is available on Saturday 8/27/2022.

  • The XRS Host 6.6 release is available on Saturday 9/10/2022.
  • The XRS Mobile 6.6 release is available on Saturday 9/17/2022

This release includes new features, enhancements, and software corrections.

 

Important Changes

Changes to Limit Certain Edits on HOS Host Application

Please be advised of changes to Log Editing Functions.

Cannot Edit Automatically Recorded Drive time for ELD or AOBRD vehicles

In compliance with ELD requirements, users will no longer be permitted to edit automatically recorded driving time created on the ELD by switching to “AOBRD mode” on the host (this is also the case for driving records created in AOBRD/ERD equipped vehicles). Hours of Service (HOS) regulations in both the United States and Canada prevent the editing of automatically recorded drive time. This includes a prohibition against shortening or reassigning to anyone other than an authenticated co-driver in a team driving situation. Per the HOS regulations, drivers and motor carriers are limited to annotating the driving events recorded on a driver's log, if they are deemed incorrect or in error.

 Drive Time Swap requires Co-driver on Logs prior to initiating the swap

In compliance with ELD requirements, users in an ELD Mode company may reassign Driving to a co-driver via the Driver Log Editor. This reassignment of the Driving event is limited to the co-driver at the time of the selected Drive event.

Cannot Edit Uncertified Logs
In compliance with ELD requirements, users will not be able to edit a driver's Record of Duty Status (RODS) until the driver has certified it. To support this requirement, the Edit icon on the Driver Details page, for both U.S. and Canadian logs, will be grayed out and unavailable for editing driver's RODS that have not yet been certified.

 

New Features and Enhancements

The new features and enhancements section describes the changes included in the 6.6 release.

 

Active Alert/Mobile Manager

  • Users can now login to their existing account on the web app and manage their subscriptions by service location. From the Home page, users can modify contact information, authenticate through Google and request Forgot Password and a reset password link will be sent.
  • Mobile Manager now supports Android 12.
  • Users can now view past and future orders on the Order Summary tab within the Web Application.

  • Users now have the ability to search by keyword, order number and/or item description; sort by date and order number; and filter by status and date range.

  • When setting a Recipient type for the region, there is an option now to "Enable New Subscriptions" which controls the "Add Service Location" button appearance in the Web Applications. add a screenshot

 

Canadian ELD

Accept/Assign UVA as Yard Move or Personal Conveyance

In accordance with the provisions of the FMCSA FAQ included above, Unidentified Vehicle Activity (UVA) can now be classified as Yard Move or Personal Conveyance upon acceptance by the driver or assignment by an administrative user.

Note:  UVA will not be allowed to be shortened or removed even if it is assumed or assigned as Yard Move or Personal Conveyance.

When the driver is using Hours of service/ELD, they can undo any Unassigned Vehicle Activity they accepted as personal conveyance by mistake.

A driver using Hours of Service/ELD, can undo any Unassigned Vehicle Activity they accepted as yard move by mistake.

A driver editing their log on OT1/XRS Mobile, can either Undo Unassigned Vehicle Activity (UVA) or Reassign Drive Time during a single editing session. They cannot do both.

A driver using OT1/XRS Mobile in an ELD vehicle can reject an Unassigned Vehicle Activity (UVA) that is offered from the XRS Relay or AMG-C device. An automatic annotation will be included with each of the rejected events stating that the driver rejected the UVA in order for the rejection to be obvious to an enforcement officer.

Administrative Setup Changes

The "Allow Driver to Change Rule Set (USA)"

The "Allow Driver to Change Rule Set (USA)" setting has been updated to show that it only applies to drivers operating in the USA.

Users can still insert/edit/delete rule change events in the Driver Log Editor even when this setting is unchecked.

This applies to all users and drivers in all companies.

All Canadian Cycles must be selected

Administrative users must now select all four Canada cycles to be compliant with Canadian ELD. When the user selects one to three, but not all four a message will display the following message:

All the Canadian Federal HOS rules must be enabled together:

  • CAN 7/70 hrs.
  • CAN 14/120 hrs.
  • CAN 7/80 North hrs.
  • CAN 14/120 North hrs.

For existing customers who have at least one of the four Canadian rules enabled, a script will be run to enable all four rules.

U.S. Yard Move Termination and Personal Conveyance

The company, organization, and driver settings for Maximum Personal Conveyance Distance and Yard Move Termination only apply to vehicles/drivers operating in the USA. To clarify this, the settings have been renamed to “Maximum Personal Conveyance Distance (USA)” and “Yard Move Termination (USA).”

 

Bulk ELD Driver Log Report (Canada)

A new Manage ELD Driver Log (Canada) Jobs status page is available for bulk requests. To access this page, select the Admin tab, then select Manage Canada eRODS Bulk Request in the Background Processing section.

 

Canadian Cities – Official List

Canadian Council of Motor Transportation Administrators have provided a list of cities as part of the Canadian ELD mandate. This list will replace the current XRS database of Canadian cities.

 

Convert measurements to Metric in Canada only

In OT1/XRS Mobile, all drivers now have an option in the Settings menu called "HOS Unit of Distance". The driver can select Miles or Kilometers. Once selected, click on the Save or Cancel button.

 

CSV file updated for Data Transfer

OT1/XRS Mobile will include active and inactive Unassigned Vehicle Activity (UVA) events when generating a U.S. eRODS transfer or a Canadian CSV data transfer.

 

Cycle Change

A driver using XRS Mobile will have the following ruleset options after login in the following priority:

1. Historic ruleset for the current operating zone
2. Default ruleset for the federal jurisdiction

When a driver using OT1/XRS Mobile crosses into a new operating zone, the following rulesets can be selected in the following order:

1. Historic ruleset for the new operating zone.
2. Default for the federal jurisdiction if historic cannot be determined.

 

The Roadnet Anywhere (RNA) to XRS entity sync was updated to include sending Default HOS Rule (USA) and Default HOS Rule (Canada) for Regions & Drivers.

Roadnet Anywhere (RNA) Host for Drivers:

Entity Administration changes for Default Rule(s).

  • Remove Default HOS Rule from driver settings.
  • Add Default HOS Rule (USA) to driver settings.
  • Only active when US Ruleset(s) are enabled.
  • Required if USA Ruleset(s) are enabled.
  • Initially set to Enabled USA Federal Rule.

Add Default HOS Rule (Canada) to driver settings.

  • Only active when Canadian Ruleset(s) are enabled.
  • Required if Canadian Ruleset(s) are enabled.
  • Initially set to CAN 7/70.
  • Once Default HOS Rule (Canada) is set (saved), the dropdown list must only contain the North/South Rules in the same Cycle (e.g., Cycle 1 or Cycle 2).

 

Roadnet Anywhere (RNA) Host for Regions:

Entity Administration changes for Default Rule(s).

  • Remove the Default HOS Rule from region settings.
  • Add Default HOS Rule (USA) to region settings.
  • Only Active when US Ruleset(s) are enabled.
  • Required if USA Ruleset(s) are Enabled.
  • Initially set to Enabled USA Federal Rule.

Add Default HOS Rule (Canada) to region settings.

Only Active when Canadian Ruleset(s) are enabled.

  • Required if Canadian Ruleset(s) are enabled.
  • Initially set to CAN 7/70.
  • Once 'Default HOS Rule (Canada)' is set (saved), the dropdown list must only contain the North/South Rules in the same Cycle (e.g., Cycle 1 or Cycle 2).

 

Changing Rulesets

Drivers and co-drivers operating in a Canadian Operating Zone can change their ruleset or cycle on the Change Ruleset screen on XRS Mobile, even when the host setting “Allow Driver to Change Rule Set” is disabled for the driver’s organization. However, drivers operating in a USA operating zone may still only change their ruleset when “Allow Driver to Change Rule Set” is enabled for the driver’s organization.

 

Changing Cycles

A driver operating in a Canadian operating zone, can switch between Cycle 1 and Cycle 2, on either the North or South rules, and is required to take a reset before doing so.

  1. A driver operating on CAN 7/70 hrs. can select CAN 14/120 hrs. in the Change Ruleset option, and vice versa.
  2. A driver operating on CAN 7/80 North hrs. can select CAN 14/120 North hrs. in the Change Rules option, and vice versa.
  3. A driver may only change to a different cycle if a cycle reset has been taken. The option is only available after the driver has completed the cycle reset.
    • If the driver has already gone on duty after taking a cycle reset, the option is still available until the driver goes into Drive status. After the driver goes into Drive status, the option is no longer available until the next cycle reset is completed.
    • Upon successful selection of the new cycle, the driver is prompted with their new available hours and the limits of the new cycle.
  4. The driver will be asked to confirm the new cycle:
    • Please confirm the new cycle and new duty/driving hour limitations.
    • The driver must select the Confirm button and can provide an optional Annotation up to 60 characters.
      • When the driver taps Confirm, the view returns to the Home screen in OT1/XRS Mobile where the clocks are updated to the new available hours.
  5. The selected cycle is updated in the Header tab.
    • A "Change in Driver's Cycle" event is created.
    • The event will include the driver's Annotation if one was entered.

Note: There is no change to the behavior of drivers operating on US rules (USA Operating Zone).

 

Changing cycles requires reset

A driver operating in a Canadian operating zone may switch between cycle 1 and cycle 2 on either the North or South rules. By doing so the driver will be required to take a reset before doing so.

For Example:

  1. A driver operating on CAN 7/70 hrs. can select CAN 14/120 hrs. in the Change Ruleset option, and vice versa.
  2. A driver operating on CAN 7/80 North hrs. can select CAN 14/120 North hrs. in the Change Rules option, and vice versa.
  3. A driver may only change to a different cycle if a cycle reset has been taken. The option will not be available after the driver has completed the cycle reset.
    • Upon successful selection of the new cycle, the driver's new available hours and the limits of the new cycle are displayed, with a message to confirm:
    • Please confirm the new cycle and new duty/driving hour limitations.
    • The driver can enter Annotation of 4 to 60 characters. (optional)
      • A Confirm and Cancel button are displayed.
    • When the driver taps Confirm, the view returns to the Home screen where the clocks are updated to the new available hours, and the selected cycle is updated in the Header tab. A "Change in Driver's Cycle" event is created.
    • The event will include the driver's Annotation if one was entered.

Note: There is no change to the behavior of drivers operating on U.S. rules (USA Operating Zone).

 

Diagnostics & Malfunctions

When using OT1/XRS Mobile, the malfunction status indicator and code will display on the Driver Log Header tab when either the vehicle or driver have a current malfunction.

OT1/XRS Mobile will create a missing data diagnostic event when required values are missing for Canadian ELD events, including operating zone changes, off duty deferral, and cycle changes.

clipboard_e0f0ceb05939751f6fc20aa7579f9be22.png

 

Drive Time Reassignment

A driver using OT1/XRS Mobile who is operating on any rule set in a mixed mode or ELD mode company can reassign automatically recorded drive time to their co-driver if the co-driver is still logged into the same mobile device.

 

ELD Data Transfer (Canada)

Administrative users in a mixed mode or ELD mode company need to send drivers logs to enforcement when requested in case of an HOS audit in Canada. In the Reports menu, in the HOS section there is a new Log Audit item called ELD Data Transfer (Canada).

The only Transfer Method is email (selected by default) and there is a required Recipient Email Address. The user must enter a valid email address to send the files.

The user must select the following items:

  • Organization
  • Start date
  • End date
  • Select at least one Driver
  • Add a comment (optional)

Click on the Send ELD Data Transfer button to make the transfer.

A new radio button allows a OT1/XRS Host user of Canadian HOS/ELD to select either drivers or vehicles.

When the user selects vehicle, they now have the ability select one or more vehicles for ELD Data Transfer.

 

Enhanced Driver Log Editor Changes

Operating Zone Events

Under Canadian ELD when a driver/vehicle moves from one Operating Zone to another, an Operating Zone Event must be recorded. Operating Zones are USA, Canada South (below the 60th parallel), and Canada North (above the 60th parallel).

Administrative users can insert/edit operating zone events for drivers via the Driver Log Editor.

Operating Zone Events cannot be deleted.

All Operating Zone Events are sent as a pending edit to the driver and can be accepted or rejected by the driver.

All edits are tracked in the Driver Log Edit Summary/Detail report.

Restrict Edit/Insert Off Duty Deferral events in Mixed or ELD mode companies

An administrative user in a mixed or ELD mode company is not allowed to insert or edit Off Duty Deferral events.

Restrict Insert HOS Rule Change

An administrative user in a mixed or ELD mode company will not be allowed to insert an Hour of Service rule change event that could result in a cycle change for the selected period.

Log Activity Reporting Changes

ELD Driver Log Report (USA)

The current ELD Driver Log report has been renamed to ELD Driver Log Report (USA) to help the administrative user differentiate between the ELD Driver Log Report in FMSCA format and the same report in CCMTA format.

  • The name ELD Driver Log Report (USA) has been updated in:
  • The Reports menu, and at the top of the Report when it is run
  • The exported version of the report
  • The Report Scheduler
  • The Driver Portal

Engine Hours and Vehicle Miles will be blank when the data is unavailable.


Driver Log Report (Non-ELD)

The AOBRD Driver Log report’s new name is Driver Log Report (Non-ELD).

The new name, Driver Log Report (Non-ELD), has been updated in the following locations:

  • The Reports menu, and at the top of the Report when it is run
  • The exported version of the report
  • The Report Scheduler
  • The Driver Portal
  • In FleetView 


ELD Driver Log Report (Canada)

The ELD Driver Log Report (Canada) has been added. It is available to administrative users in the OT1/XRS Host UI and to drivers in the Driver Portal.

The ELD Driver Log Report (Canada) has a new menu and filter selector.

Click on the ELD Driver Log Report (Canada) to view the selection criteria for the report.

  • Select Organizations (required)
  • Select Resource Groups
  • Set the Start and End Date. The date range is limited to 31 days (required).
  • Select one or multiple drivers

Click on the Generate Report button to create the report.

The ELD Driver Log Report (Canada) conforms to the Canadian ELD required format and is what an enforcement officer will see in the generated Canadian ELD Output file.

An error message displays, "There is no Driver Log activity for the selected date range", when is no driver log activity found within the selected date range.

 

New Report Page View Mode for ELD Driver Log (Canada)

When an administrative user generates a report for multiple drivers, they can view one driver log at a time, with the currently selected driver displayed.

 

Hours of Service and ELD

When a back-end user switches a Driver’s HOS-Use Region Settings to No in using Hours of Service (HOS)/ELD in OT1 Host, the user will see the Driver’s HOS Settings pre-populated with the Region’s HOS Settings.

To prevent issues in the FMCSA ERODS System, OT1/XRS Mobile will include all engine power-ups and power-downs for all vehicles that a driver was in during the selected date range for an ERODS transfer.

A OT1 Host user can now set an Odometer gap limit value to avoid false positives. When a change is made, the value is sent to OT1/XRS Mobile.

In OT1/XRS Mobile, the ELD Exempt driver is prompted to Certify their logs in the same manner as non-Exempt drivers to stay compliant with HOS regulations.

A driver or co-driver using OT1/XRS Mobile while operating on Canadian Federal rules will see a warning, when going back on duty after being off duty or in sleeper, to notify them if they need more time off to achieve the required daily off duty time.

  1. The warning will appear after the driver selects on duty after being in Off Duty or Sleeper Berth, but before the On Duty status change is committed.
    • The warning will also be given if the driver is prompted to go On Duty upon login, and the driver selects Yes to go On Duty.
  2. For the daily off duty time requirement, the warning will appear if the driver/co-driver has an hour or less remaining before reaching their required daily Off Duty time.
    • Warning text: The required daily off duty time will be complete at HH:MM:SS PM/AM. Are you sure you want to change your duty status?
  3. If the required daily Off Duty time is being taken as split sleeper berth periods (single or team drivers), the following warning will appear any time the driver or co-driver tries to go on duty while in sleeper berth. "If you would like to use the current Sleeper Berth time as part of a split sleeper reset, you need to stay in your current status until [time when reset will be completed. Are you sure you want to change your duty status?"
  4. The driver will have the ability to tap OK to continue with the On Duty status change, or Cancel to stay in their current duty status.
    • If the driver Cancels, and then attempts to change their duty status again before the driver has reached their required time off, the warning will appear again.
  5. If multiple messages are shown in the same prompt, the shift message will be shown first, then the daily time off warning, then 24 hours in 7-day warning, then the cycle reset message.

 

Misc. Items

If a driver initiates a mobile logout and then moves the vehicle prior to the logout being completed, the logout will be canceled.

Validate the U.S. Intermediate Event recording based on the requirements in the U.S. ELD Technical Specification.

4.5.1.2. Event: Intermediate Logs

(a) When a CMV is in motion, as described in section 4.3.1.2 of this appendix, and there has not been a duty status change event or another intermediate log event recorded in the previous 1-hour period, the ELD must record a new intermediate log event.

(b) The ELD must associate the record to the driver, the vehicle, the motor carrier, and the shipping document number, and must include the same data elements outlined in section 4.5.1.1 of this appendix except for item (p) in section 4.5.1.1.

 

Operating Zone

A driver using OT1/XRS Mobile and is using the US Intrastate Rule can switch to a Canada Operating Zone and an associated Canada rule set, as required by the Canada ELD mandate.

In cases where there are no operating zone change events within the drivers logs on OT1/XRS Mobile to populate the HOS Log Header, OT1/XRS Mobile will use the current operating zone value provided from the host or prompt the driver to identify the operating zone.

 

Personal Conveyance

An ELD Driver who is on Personal Conveyance and they select to logout or “Disconnect from Vehicle” are given the option to go Off-Duty to terminate Personal Conveyance prior to completing the Logout or Disconnect from Vehicle.

When a Host user edits a driver's log and inserts personal conveyance into the current day, OT1/XRS Mobile will incorporate the change into the 75 km distance limit for Canada. The edited distance will be combined with any personal conveyance distance accumulated on the mobile in the current day to calculate 75kms and update the driver status.

 

Sending ELD output files to roadside inspection

Driver can now send log without being connected to the vehicle

A driver in a Canadian Operating Zone can email their logs to CCMTA, even when not connected to a vehicle, and in any duty status (other than Drive).

 

Mobile Duty Status Changes

Automatically recorded Driving duty status change

A driver using OT1/XRS Mobile who manually selected Drive status and then reaches the configured speed for transitioning to Drive Status, will have an automatically recorded Driving duty status change added to their logs.

In this scenario, the US/Canada driver's log on mobile and host shows a manual drive event and then an auto drive event with the appropriate time stamps.

If a driver/host user attempts to edit the driver’s log, they can only edit the manual portion. The auto drive event is not editable and but can assigned to another driver if co-driver was present.

Manual Drive Status Behavior in USA Operating Zone

When the driver is in a USA Operating Zone switches to On Duty after a manual driving, the On Duty event timestamp will be at the time the On Duty change occurred, not when the vehicle stopped moving.

When the driver is in a USA Operating Zone and an automatic On Duty status change is recorded after manual driving, the On Duty event timestamp will be at the time the On Duty change occurred, not when the vehicle stopped moving.

On Duty Events begin/end when switched to On Duty

A driver using OT1/XRS Mobile in a Canadian Operating Zone, with AOBRD and ELD vehicles, will have on duty events that reflect the exact time that they switched to On Duty, and not the time the vehicle stopped moving.

For example:

  1. When the driver is in a Canadian Operating Zone, and the driver switches to On Duty after driving, the On Duty event timestamp will be at the time the On Duty change occurred, not when the vehicle stopped moving.
  2. When the driver is in a Canadian Operating Zone, and an automatic on duty status change is recorded after driving, the On Duty event timestamp will be at the time the On Duty change occurred, not when the vehicle stopped moving.

Note: The current behavior when a driver is in a US operating zone is unchanged.

Driver can manually select drive

A driver operating in any Operating Zone and connected to an ELD vehicle can manually select Drive status if they are connected to an ELD vehicle.

If the driver is not connected to an ELD vehicle, the App will display the following message:

Drive status cannot be selected manually when there is not an ELD vehicle connected.

Once drive status is selected it will go On Duty after 5 minutes or when the vehicle is moving 5 mph, whichever comes first.

If the driver responds No to going On Duty after 5 minutes, OT1/XRS will prompt the driver again after 5 minutes if there is no motion.

Note: ELD Exempt drivers and co-drivers may not manually select Drive status.

Driver can manually select drive

A driver operating in any Operating Zone and connected to an ELD vehicle can manually select Drive status if they are connected to an ELD vehicle.

If the driver is not connected to an ELD vehicle, the App will display the following message:

Drive status cannot be selected manually when there is not an ELD vehicle connected.

Once drive status is selected it will go On Duty after 5 minutes or when the vehicle is moving 5 mph, whichever comes first.

If the driver responds No to going On Duty after 5 minutes, OT1/XRS will prompt the driver again after 5 minutes if there is no motion.

Note: ELD Exempt drivers and co-drivers may not manually select Drive status.

 

Off Duty Deferral Changes

Driver notification to adjust deferral hours

A driver in a Canadian Operating Zone may select Off Duty Deferral. OT1/XRS Mobile will prompt the driver when additional time off duty occurs after selecting the deferral. This allows the driver to adjust the hours to defer.

When a driver takes additional qualifying Off Duty time on Day 1 after selecting the deferral, upon going back on duty during Day 1 XRS Mobile prompts the driver to adjust the new deferral hours.

Message:

Remaining off duty time to be deferred (HH:MM)

The driver may adjust the displayed new deferral hours.

Work Time Extension

A driver in a mixed mode or ELD mode company that is in a Canadian Operating Zone can select Declare Canadian Off Duty Deferral Day 1 in the Hours of Service (HOS) Options menu, select Enter Work Time Extension.

The driver will be prompted with the following message to confirm how much time to defer and enter an optional comment.

The optional comment has no minimum characters requirement but does have a maximum of 60 characters.

Message:

"Please review and confirm the Off-duty time to be deferred (HH:MM): [number of hours and minutes to be deferred]"

The driver can reduce the number of hours and minutes down to 1 minute minimum.

The modified value cannot be greater than the value that was originally displayed or less than 1 minute.

The driver can select Confirm or Cancel.

When the driver taps Confirm, the existing confirmation message "The Canadian Off Duty Deferral is now active" is displayed, with an OK button. A deferral event is created.

If the driver modified the number of minutes/seconds to defer, the confirmation message will be "The Canadian Off Duty Deferral is now active. Based on the deferral time entered, you must take an additional [HH:MM] of Off Duty Time today."

The time value in the message accounts for the remaining Off Duty Time the driver needs to take today to make up 2 hours when you add the time deferred.

Example: The driver already took off 30 minutes today separate from the 8-hour shift break, and chose to defer an hour, the message would show 00:30. 

Upon confirmation, the Off-Duty Time Deferral Status value will be set to 1 (day one).

If the driver has already selected the Off Duty Deferral on Day 1, and attempts to select the option again, a message will display.

"Remaining Off Duty Time to be deferred (HH:MM): [number of hours and minutes to be deferred, as calculated by OT1/XRS.

Driver warning: Canadian Split Sleeper Berth rules when selecting Off Duty Deferral option

A driver in Sleeper Berth of at least 2 hours but less than 8 hours is allowed to select Off-Duty Deferral when the driver is not in a current Split Sleeper Pairing Cycle.

When the driver selects Declare Canadian Off-Duty Deferral Day 1 from the Work Time Extensions menu there is a Confirmation Message:

Are you attempting to split SB time for a shift reset?

If yes, you cannot use Off Duty Deferral.

The driver can select either the Yes or No button.

If the driver selects Yes, the deferral selection is canceled, and the driver returns to the Work Time Extensions menu with Declare Canadian Off-Duty Deferral Day 1 temporarily disabled.

If the driver selects No, the deferral is selected, and the driver is allowed to confirm hours to defer and enter a comment.

If the driver leaves and then returns to the Work Time Extension menu while still in Sleeper Berth in less than 8 hrs. Declare Canadian Off-Duty Deferral Day is enabled.

Off-Duty Deferral is not available when:
  • Any portion of a Sleeper Berth Pairing Cycle is present in a day.
  • When the 8+ hr. reset is still in progress.
Remaining Off Duty Time

The driver's deferral time will be between zero and 2 hours and will indicate the remaining OFF Duty time that could be deferred to Day 2 based on the time already taken off by the driver in Day 1.

Day 2 confirm hours

When a driver or a co-driver in a mixed mode or ELD mode company selected Off Duty Deferral on the previous log day, the driver will be prompted on Day 2 to confirm the hours being deferred. This occurs when the driver goes on duty for the first time on Day 2 of the deferral.

Logging Devel (ELD) Event

When the driver confirms the prompt for hours being deferred on Day 1, an Electronic Logging Device (ELD) event is created on the driver's Hours of Service (HOS) Log when Inspection Mode is on and in the Driver log report Canada ELD in OT1/XRS Host.

 

Operating Zone Events (Jurisdiction Change)

 

Changing Operating Zones when in Personal Conveyance

A driver using OT1/XRS Mobile in a Mixed Mode or ELD Mode company, will be prompted when a change in my Operating Zone is detected. If the driver is in Personal Conveyance when an Operating Zone is detected, the prompt will occur when Personal Conveyance in ended.

Editing an Operating Zone Event

Drivers can edit operating zone events via the mobile Log Editor within the Hours of Service (HOS) cycle. However, the Operating Zone event cannot be deleted.

All edits are tracked like other Electronic Logging Device (ELD) events, where the original event becomes inactive, and the new version of the event is active.

All edits are tracked in the Driver Log Edit Summary/Detail report on the OT1 host, indicating that the driver made the edit.

Only the Date, Time and Location may be edited, and an Edit Reason is required

  • Minimum 4 characters
  • Maximum 60 characters
Operating Zone Change

Using OT1/XRS Mobile in a Mixed Mode or ELD Mode company, a change of the Operating Zone is detected due to a border crossing or when the driver manually changes their Operating Zone. When this occurs a message is displayed to confirm the new available hours for the selected Operating Zone ruleset.

Please confirm the new operating zone and new duty/driving hour limitations for the day, work shift, cycle and operating zone".

The driver may enter up to 60 characters in an Annotation field. (Optional)

When the driver taps on the Confirm button, the view returns to the Home screen where the clocks are updated. New available hours and the updated Operating Zone is displayed in the Header tab. When complete, an Operating Zone event is created.

Operating Zone detection

A driver using OT1/XRS Mobile in a Mixed Mode or ELD Mode company will be prompted when a change in Operating Zone is detected. A Change in Operating Zone is triggered when the driver crosses between:

  • United States/Alaska (OZ 3) and Canada South (OZ 1) - either direction
  • United States/Alaska (OZ 3) and Canada North (OZ 2) - either direction
  • Canada South (OZ 1) and Canada North (OZ 2) - either direction
Manually change Operating Zone

A driver using OT1/XRS Mobile in a Mixed Mode or ELD Mode company, can manually change their Operating Zone.

The Change Ruleset option has been renamed to Change Ruleset/Cycle/Operating Zone.

There is a new row on the screen, above the Current Ruleset and below the driver name, labeled Current Operating Zone. The Current Operating Zone is one of the following values:

  • 1 (South of latitude 60°N in Canada)
  • 2 (North of latitude 60°N in Canada)
  • 3 (United States)

The driver can select the Change button in the row below it to select a different Operating Zone.

After the selection is made, a message is displayed to confirm the new available hours to the driver for the selected Operating Zone/ruleset.

If a Co-Driver logged in, the Co-Driver's ruleset/cycle will be based on their default for the current Operating Zone and NOT set according to main driver’s default ruleset/cycle.

Note: This new option is disabled for ELD Exempt drivers.

Event when changing Operating Zones

When a driver operating on any rule set, in a Mixed Mode or ELD Mode company, changes operating zones an event is created to record the change.

 

Personal Conveyance changes

Personal Conveyance Total Time

The driver operating on Personal Conveyance on any ruleset and with AOBRD and ELD vehicles, can now see the total amount of Personal Conveyance time for the current log day.

End personal Conveyance

OT1/XRS Mobile: A driver operating in a Canadian Operating Zone and connected to an ELD vehicle, when operating on PC can only select Off Duty which ends Personal Conveyance.

View Personal Conveyance distance/time

A driver operating on Personal Conveyance on any ruleset and with AOBRD and ELD vehicles, can view their total Personal Conveyance distance/time for the current log day in addition to the current Personal Conveyance period to see how close they are to the 75 KM limit in Canada.

75 km rule

Duty Status for Drivers in a CAN zone and connected to an ELD vehicle, are changed to Driving when reaching the 75 km in Persona Conveyance.

The 75 km is also honored when drivers are connected to an AOBRD vehicle in a CAN zone, this while doing Personal Conveyance.

There’s no change for drivers operating in the US zone.

A Maximum Personal Conveyance Distance established in Host settings is ignored for drivers in a CAN zone. When the established Maximum Personal Conveyance Distance is set higher or lower than the 75 km. The Duty status will be changed automatically to driving when the 75 km limit is reached.

Personal Conveyance is disabled when drivers reach the 75 km limit whether it is Midnight to Midnight or Noon to Noon and it will be enabled again until the next log day starts.

When drivers are connected to an ELD vehicle and operating in the US zone go over the 75km and then change to a CAN zone, the Personal Conveyance option will be unavailable. On the other hand, drivers who reach 75km on the CAN zone are able to start PC again when in the US zone.

The Personal Conveyance distance and time are accumulated and all the Personal Conveyance periods are included from the driver during their log day and it counts until 75 km is reached.

 

Prompt driver when ELD is 30 minutes of duty limitation

Low Drive or Low Duty

Low Drive or Low Duty Time warning message on OT1/XRS Mobile will now include which limit the driver is about to reach for the day: work shift, cycle and operating zone being used. This applies to both U.S. and Canada.

Example:

You are 30 minutes from violating the 13-hour driving shift limit of regulation part 13(1) of CAN 7/70 hrs. in the South of latitude 60° in Canada operating zone. 

 

Prompt driver when events are missing data

VIN number not available

When the VIN is not available, the value will be blank for any ELD related view.

The following views and reports will have a blank VIN value when it is not available from the ECM, or from the host vehicle entity.

  • Mobile HOS Log Header (Canada and US)
  • US eRODS (Host and Mobile)
  • Canada Driver Log PDF report and Canada CSV Data Transfer
  • ELD Driver Log Report (USA)

When required data is missing such as the VIN, a data diagnostic event is created.

ECM data not available

A driver in a Canadian Operating Zone will be notified that required data is missing. This occurs when the driver is not associated to a vehicle, or has lost connectivity to the vehicle, resulting in some data elements being left blank for some ELD events.

The driver will see the following message:

There is no link to the engine ECM. Please acknowledge and confirm that required data elements were omitted in the event record [event name].

Driver should press the Confirm button.

There will be a separate prompt for each event where values were omitted.

This only applies to driver in either Canadian Operating Zone.

ECM Connection is not linked

When a driver who is operating on a Canadian rule set logs into XRS Mobile or Omnitracs One Drive, the driver is presented with a message that the device is not associated with the vehicle. The following message is displayed:

The ELD is not linked to the Engine Control Module (ECM). The ELD cannot capture required data from the engine ECM and monitor the engine's power and vehicle motion statuses. Please acknowledge that without a link to the engine ECM, there may be an impact on data recording and compliance to the current HOS regulations.

The driver must click on the Confirm button after reading the message.

 

Unassigned Activity

Reject recorded driving

A driver in a Mixed or ELD Mode company, can edit their log and remove recorded Driving that was erroneously assumed from the Unidentified Driver Profile. When the driver removes the events, the events will reappear in the UVA tool as a UVA event that must be reclassified or assigned to another driver.

Accept or reject UVA

A driver reviewing pending edits that include Unassigned Vehicle Activity (UVA) that has been assigned/removed via an edit in OT1/XRS Host, the driver can Accept or Reject them and they must apply to the drive event and the associated terminating event.

When the carrier proposed edit includes a UVA being assigned/deleted from the driver’s log, the pending edit includes the drive event to be assigned/removed, and the associated terminating event which will also be assigned/removed if the edit is accepted.

The driver can only accept/reject the driving event. The terminating event will automatically be accepted/rejected along with the drive event when the driver makes their selection. The driver cannot accept/reject the terminating event separately.

When there are multiple drive events being assigned/deleted (UVA), the driver does not need to accept all or reject all. The driver can accept some and reject others, but the terminating event for each drive events is handled the exact same way as the associated drive event.

 

Unidentified Driver Profile

Hours of Service (HOS) Power On/Off events for unidentified driver.

When the Mobile connects, events that match the driver's assigned period will be automatically assigned to the driver and create driver log entries. These event will not appear on the Unidentified profile.

Events with timestamps outside of the driver’s assigned period will be assigned to the Unidentified driver and appear on the Unidentified Profile.

Unidentified Profile Tab Improvements

When the Mobile connects, events that match the driver's assigned period will be automatically assigned to the driver and create driver log entries. These event will not appear on the Unidentified profile.

  • Events will be shown in chronological order, oldest at the top.
  • The fields for Unidentified events are the same as HOS log screen events.

 

Vehicle ID Correction

Indicate Vehicle ID was modified

When a driver makes a correction to the vehicle ID, OT1/XRS Mobile will record an annotation on the driver's and co-driver's current duty status indicating that the vehicle ID was modified.

Annotations for vehicle ID modifications format:

[Old vehicle name] modified by driver to [new vehicle name].

Fixing a Vehicle ID in Canada

A driver operating on in a Canadian operating zone associated to an ELD vehicle, has the ability to fix the Vehicle ID of their associated vehicle. This option is available in the Hours of Service (HOS) Options menu labeled Modify Vehicle Name.

The option is only available to driver's operating in a Canadian operating zone, when in network coverage, and only when associated to an ELD vehicle.

If the driver attempts to select the option when it's not available (greyed), the reasons why it is not available are shown:

This option is unavailable due to the following:

  • You must be in an On Duty status to access this feature
  • You must be in a Canadian Operating Zone to access this feature
  • You must be connected to an ELD vehicle to access this feature.
  • A network connection is required to access this feature” 

Note: (Only the applicable reason(s) are displayed)

When the driver selects the option, the associated Vehicle ID is displayed and can be modified by the driver.

  • The value cannot contain spaces and must be between 3 and 20 characters
  • The driver can select Save or Cancel. When the driver taps the Save button, this message is shown:

Are you sure? The vehicle name will be changed for all users and in all reports.

  • If the driver taps Yes, the Vehicle ID is modified for the current day and subsequent days. Previous days are not affected.
  • If the driver taps No, the changes are not saved and view returns to the HOS Options menu.
  • If the driver taps Cancel, the changes are not saved and view returns to the HOS Options menu.

When the driver saves the change, the modified vehicle ID is communicated to the OT1 Host

  • If the modified vehicle ID already exists, notify the driver that the update failed due to a duplicate Vehicle ID.
  • If there is no network connection when attempting to update the vehicle ID, notify the driver that the update failed due to lack of network connection. 
  • After the mobile received confirmation of a successful update, the mobile requests a fleet list update to get the new vehicle ID updated locally.

If the driver is in an OT1 account, the change is also communicated to the OT1 host to update the equipment name.

Note: Vehicle ID cannot be edited by the co-driver. Only the primary driver.

 

Yard Move

Yard move status

A driver who's duty status is Yard Move can only change their status to On Duty.

Auto termination of Yard Move

A driver operating in a Canadian Operating Zone, connected to an ELD vehicle, and has selected Yard Move needs OT1/XRS Mobile to terminate the Yard Move when one of the following conditions are met.

Yard Move will terminate when:

  • Driver reaches 32 km/h
  • A vehicle is powered down and powered on again

Upon Yard Move termination due to reaching 32km/h, Yard Move is cleared and status is changed to Drive status.

Note: Canadian Operating Zone is not based on the OT1 host setting for yard move termination.

Note: This change does not affect a driver operating in a US Operating Zone or is connected to an AOBRD vehicle.

 

Continue Yard Move

A driver operating in a Canadian Operating Zone, connected to an ELD vehicle, and has selected Yard Move needs OT1/XRS Mobile to ask the driver if they want to continue in Yard Move after the vehicle is powered down and back on again. This may include a loss of Bluetooth connectivity.

Before the vehicle is in motion, one of the following messages will be displayed:

  1. Power down detected. Stay in Yard Move?
  2. Bluetooth connection lost. Stay in Yard Move?

The driver is shown a Yes and a No button.

If the driver selects Yes, continue Yard Move status.

If the driver selects No, end Yard Move status and leave the driver on duty.

If motion is detected before the driver responds, end Yard Move status and switch to Drive status at the configured speed trigger (8kph or less).

If the Bluetooth disconnection/reconnection occurs while the vehicle is in motion, the driver is not prompted to continue Yard Move when Bluetooth reconnects. The driver remains in Yard Move.

If the Bluetooth recovers after the vehicle has stopped moving, the driver is prompted with the continue Yard Move message at that point.

Note: While operating in the US operating zone, or connected to an AOBRD vehicle, the behavior is unchanged.

 

Update Mobile Log display and header

Canadian Operating Zone includes all data

A driver using OT1/XRS Mobile in a Canadian OZ, the Unidentified Tab includes all data required by the Canadian ELD Mandate.

When a driver is in a Canadian OZ, in the Unidentified tab under the graph, there is an Event Details section that includes drive events, an On Duty terminating event for each drive event, and intermediate log events recorded by the unidentified driver.

  1. In the Event Details section, there is an Engine Power Up and Shut Down section.
    • Power up and shut down events recorded during unidentified driving activity for the connected vehicle always appear as active events in this section, even after the unidentified driving activity has been accepted by a driver.
  2. In the Engine Power Up and Shut Down section, there is Diagnostic and Malfunction section
    • Diagnostic and Malfunction events recorded during unidentified driving activity for the connected vehicle will always appear as active events in this section, even after the unidentified driving activity has been accepted by a driver.
  3. The Unidentified tab displays the above events for the current vehicle being used by the logged in driver, for the current day and previous 14 days.
  4. The columns for each event are listed as vertical field labels, similar to Inspection Mode view in the Hours of Service (HOS) Log screen.
  5. The unit of measure in this screen is available to select between kilometers and miles selected by the driver.

Note: If the driver is in the US Operating Zone, there is no change to the current display.

Note: The driver can still only view the last 7 days plus current day of UVA in this tab.

Canadian Operating Zone Events

A driver operating in a Canadian Operating Zone, their events in my HOS Log screen are separated into sections based on the Canadian ELD mandate.

The events will still be listed with the field labels vertically on the left of the screen.

When a driver is in a Canadian Operating Zone:

  1. When the driver was in personal conveyance, only a subset of ELD events are included in the event list for the driver.
    • The Canada data transfer CSV file only includes PC start and PC end events, and any ELD diagnostic and malfunction events
    • No intermediate events or engine power up or shutdown events are included while the driver is in Personal Conveyance.
  2. The date and time of the certification event will be the date and time the event was created and appear in chronological order on the day that it is being certified. The entry will include the date and time the certification was recorded.
  3. When a driver is in a USA Operating Zone, there is no change to the existing display.
  4. The graph annotations (line identifiers shown in the Remarks section of the graph) should continue to function the way they do today with the following exception. Since the display lines will no longer be in chronological order, the annotations in the graph Remarks should appear in alphabetic order but the annotations on the line items will be interspersed and out of order.
  5. Annotations and Comments section:
    • For each ELD event that contains a comment with more than 4 characters a new line is created.
    • When there is a comment, each of the listed functions will appear on a separate line, in the order that appears in the table.

For edit comments (getComment()), there will be corresponding edit date/time (getEditedTime()) and edit user (getEditedBySid() used to lookup in the Editors list of the Driver Log (108) request)

Canadian Operating Zone ELD Version

When a Driver or Co-Driver is in a Canadian operating zone, using a Canadian Ruleset, OT1/XRS Mobile will display the Canadian ELD version of the header tab.

 

Will Pair and Split Sleeper Enhancements

Selecting the Will Pair feature indicates that the driver intends to split their sleeper berth time to obtain restorative rest in accordance with the current HOS regulations in the USA or Canada.

  • If Will Pair is selected, the HOS duty and driving limitation clocks will assume the driver is going to take the second half of a spilt sleeper pair and exclude the first qualifying segment from the appropriate duty and driving limitation clocks. The driver will see an “optimistic” view of available hours.
  • If Will Pair has not been selected, the HOS duty and driving limitation clocks will be calculated as if the driver will not be utilizing the split sleeper berth option and all hours in the day will be considered when calculating available duty and driving limitations. The driver will see a “pessimistic” view of available hours.

To use the Will Pair selection, Allow Split OFF/SB Pairing must be enabled. Allow Split OFF/SB Pairing can be enabled for the Region and overridden on a per Driver basis if desired.

Note: Will Pair has been added to the XRS Import Driver template (CSV). A new column is available. Select Yes or No to set the Will pair selection on the driver level.

If Allow Split OFF/SB Pairing is Disabled, the HOS duty and driving limitation clocks will be calculated as if the driver will not be utilizing the split sleeper berth option and all hours in the day will be considered when calculating available duty and driving limitations. The driver will see a "pessimistic" view of available hours.

OT1/XRS Mobile: When a driver is using HOS/ELD in Canada and using the ‘Will Pair’ feature to show optimistic clocks, the driver will be warned when approaching a violation of the pessimistic clock in order to remain compliant if they are not going to be able to use the split sleeper provisions.

When a driver using XRS Mobile with an AMG-C or XRS Relay device while in Sleeper Berth status and loses Bluetooth connectivity, XRS will not automatically trigger paper log mode. Instead, Sleeper Berth status will prompt the driver to ask if they would like to switch to paper log mode.

 

CoPilot - Omnitracs Navigation 2.0

CoPilot is officially upgrading to Omnitracs Navigation 2.0, and we will provide you with a better experience.

  • Starting with a brand-new look and feel that improves the Navigation product usability and learnability.
  • By standardizing Omnitracs Navigation 2.0 across all platforms (OT1, XRS, and Roadnet), customers will benefit from visual consistency, streamlined documentation, knowledge base, and ongoing innovation.
  • By white labeling to align with Solera’s latest brand standards, Omnitracs Navigation 2.0 will benefit from increased investment.
  • Enriched development and support between Omnitracs and Trimble

More than a new User Interface, the 6.6 version includes new features and improvements!

  • Omnitracs Navigation 2.0 (CoPilot) supports the integration with the Roadnet Mobile app.
  • Omnitracs One vehicle entities (equipment and equipment type) now integrate with Trimble Fleet Portal.
  • From the back office, you can now enable or disable the configuration to allow the use of cellular data to download and upgrade maps.
  • Introduce various behind-the-scenes improvements and bug fixes to enhance the experience.

 Before upgrading, please look at these important considerations:

  • The dispatcher app (Drive or RN Mobile) and Omnitracs Navigation 2.0 (CoPilot) apps should upgrade to the latest 6.6 release version together.
  • To use the Omnitracs Navigation 2.0 (CoPilot) app, the Mobile Device ID must have a license assigned in both portals Omnitracs One and Trimble Fleet.
  • The driver must open the dispatcher app (Drive or RN Mobile) and navigate to a stop to enable the Omnitracs Navigation 2.0 (CoPilot) license.

Omnitracs One vehicle entities, integrate with Trimble Fleet Portal

  • Now, the equipment and equipment type entities are integrated into Trimble Fleet Portal.
  • The Roadnet Admin portal can be configured with the Account ID to enable the integration of the vehicle entities (equipment and equipment type).
  • From the Roadnet Admin portal, equipment integration can be enabled.
  • When the Trimble integration is enabled, the Account ID becomes a required field needed to complete the setup for an Omnitracs Navigation 2.0 (CoPilot) Customer.
  • When the integration is enabled, the equipment data is automatically synchronized to accept the changes made in Omnitracs One portal to add, delete, or update entities.
  • When the integration is enabled, the import method of the Omnitracs One portal can be used to add, delete, or update equipment data.
  • The equipment types are integrated into Trimble Fleet Portal as vehicle groups.
  • This means that when using equipment type "A" for equipment 1, 2, and 3, the vehicle group in Trimble Fleet Portal will be "A" and contain 1, 2, and 3 vehicle IDs.
  • The last sync time is recorded when adding or updating an equipment entity.
  • When facing server issues or crashes, the system can recover by re-enabling the integration, then the pending equipment data is synchronized.
  • The system records the logs of the integration, and when facing issues, it alerts the Solera-Omnitracs team.

Configuration to allow the use of cellular data to get maps

  • The Fleet Admin can configure each Omnitracs One region to allow the usage of the cellular network to download or upgrade map sets in Omnitracs Navigation 2.0 app.
  • Omnitracs Navigation 2.0 (CoPilot) app will use the primary region set for the mobile device ID to retrieve the configuration for the usage of the cellular data key.
  • Omnitracs Navigation 2.0 (CoPilot) app will save the configuration to allow downloads of maps through the cellular network when initializing the app with the Drive app.
  • Omnitracs Navigation 2.0 (CoPilot) app will display a prompt when the cellular network is disabled for the Device Region in Omnitracs One portal and there is no Wi-Fi connection.
  • When the application is not enabled in the Omnitracs One portal, the UI will display a prompt asking to contact the administrator.
  • The Omnitracs Navigation 2.0 (CoPilot) app will always open in a separate instance, which will allow the driver to have only one task running at the same time; this will help to improve the experience and performance.

Omnitracs Navigation 2.0 supports the integration with the Roadnet Mobile app

  • The Roadnet Mobile customers must do a clean installation of Omnitracs Navigation 2.0 (CoPilot) v6.6 and install new maps. This means that the prior CoPilot 10 cannot be upgraded to the new 6.6 version.
  • For new Mobile Device IDs, the user must add the item in the Omnitracs One portal and mark the Enable Copilot checkbox. Then please follow the “Steps to add a Mobile Device ID in Trimble Fleet Portal.” 
  • The Equipment IDs added to the Omnitracs One portal automatically synchronize to Trimble Fleet Portal as Vehicle IDs.
  • The Equipment type IDs added to the Omnitracs One portal automatically synchronize to Trimble Fleet Portal as Vehicle Groups.
  • After the clean install, the driver must open the Roadnet Mobile app and navigate to a stop to enable the Omnitracs Navigation 2.0 (CoPilot) license.
  • Android mobile devices need connectivity at least once a week for Omnitracs Navigation 2.0 (CoPilot) app licensing to work.

 

Dispatch

  • If a stop has multiple orders, you can now scroll through the orders and edit the actuals.

 

Hours of Service/ELD Changes

Enhanced Driver Log Editor

The Driver Log Editor (DLE) has been upgraded to improve the user experience.

New Date Range Selection Options

clipboard_eba84bb896ce433b428f7128d71e7cb5f.png

Common timeframes for selection

When selecting a date range to load, the enhanced editor includes a dropdown menu to quickly select a few common timeframes (today, past 7 days, etc.)

clipboard_ee0773a1749575ee84ffd76d5463c73c7.png

Initial display of most current day in range

When multiple days are loaded in the editor, the enhanced editor starts out by displaying the last day in this timeframe; the standard editor starts out on the first day.


Easy to jump to different days in range

The enhanced editor includes an additional date selector to quickly jump to a different day in the range selected.

clipboard_e101f65fee63a230f8f876c31d4006d6e.png

New Current DOT Clock Section

Canadian Driver

clipboard_eb6c5873f5338e4c598170e5d620662d8.png

Current Clocks

This section always displays the driver’s current clocks, regardless of the date range selected for viewing.

8-Day Recap

A new view is available on the Enhanced Driver Log Editor that provides a quick view of the time a driver will get back at midnight for each of the upcoming days based on the roll off of days in their current cycle.

Select 8-Day Recap to view driver's recap hours for the cycle.

clipboard_e5bf66de1b1ac6bbb60c928ec659ef1ae.png

Extend logs using last known status

There is a checkbox "Extend logs using last known status" with description: "The DOT clocks and driver log will reflect the last-known driver status up to the current time regardless of the data gaps. Clocks will auto-reset when a driver is presumed off-duty for a compliant amount of time. When using this feature, the current duty status is assumed and may not be accurate."

Driver Chart

A new view is available on the Enhanced Driver Log Editor that displays multiple Grid Graphs for the selected Driver. The number of grid graphs is dependent on the week/cycle setting for the Driver:

  • US 7/60 – 8 grid graphs
  • US 8/70 – 9 grid graphs
  • Canadian Cycle 1 or 2 – 15 grid graphs

Select Driver Chart to view driver's current cycle of logs.

Use the scroll on the right side for additional logs.

 

Daily Event List Changes

End of Day (or most recent event) at top

The enhanced editor lists log events from newest to oldest; the standard editor lists them oldest to newest.

Ability to change sort, descending vs ascending time
Note: When using the sort feature, you must have a driver selected.

Users can now sort events on the Enhanced Drive Log Editor in either ascending or descending order by Date/Time. Clicking on the name of the column will sort in the Ascending or descending depending on the current sort order.


Ability to filter to event list

Users can now filter the events listed.

clipboard_e01a2a296ec1a28bbd9aafbfa2d35cb77.png

Two new columns

The enhanced editor includes two additional columns that aren’t present in the standard editor: Vehicle ID, Co-Driver.

 

Enhancements to the UVA Tool

Host

The Reclassification Editor Screen now optionally includes Distance Traveled and Location for each of the individual UVA segments

Export UVA has been expanded to include more dataset options

Select the date range and status, then select Load List. Select Export.

Select one of the four options, the click on Export.

The export is a CSV file.

clipboard_ec0b99ac2f950c6af4d61a8c114404fff.png

Unassigned – This includes all UVA that is currently not Assigned/Accepted or Reclassified and includes the following fields:

  • Organization
  • Vehicle ID
  • Previous Association Date
  • Previous Known Driver
  • First Drive Time
  • Next Association Date
  • Next Known Driver
  • Driver Association Gap
  • Rejected By
  • Motion Distance
  • Reclassify
  • Notes
  • Site ID

 

Reclassified – This includes all UVA that has been Reclassified and includes the following fields:

  • Organization
  • Vehicle ID
  • Date
  • Start Time
  • Duration
  • Distance
  • Location
  • Site ID
  • Reclassification
  • Assigned By

 

Assigned to Driver – This includes all UVA that is on a Driver’s Log, both those assumed by the driver on the mobile and those assigned by an administrative user and accepted by the driver, and includes the following fields:

  • Organization
  • Vehicle ID
  • Date
  • Start Time
  • Duration
  • Distance
  • Location
  • Site ID
  • Assigned To
  • Assigned By

 

Rejected – This includes all UVA that was Rejected by a Driver on the mobile and includes the following fields:

  • Organization
  • Vehicle ID
  • Date
  • Start Time
  • Duration
  • Distance
  • Location
  • Site ID
  • Rejected By
  • Rejected Date/Time
  • Rejected Reason

 

Force Logout

When a driver forgets to logout of a Mobile and then logs into a different Mobile, it is possible that the Driver could get ELD Events from two vehicles at the same time. This makes a mess of his RODS and some items, like automatically recorded Driving, cannot be edited out. Using the new Force Logout feature will minimize the risk of having incorrect logs, particularly for operations where the Mobile stays with the vehicle and the Driver moves from vehicle to vehicle.

 

Omnitracs Navigation (OTNav)

To enrich your experience with the application, this version includes:

  • A new set of maps v12 HERE 2021.4 CAN-USA.
  • The WEX integration for FedEx Fuel locations.
  • We also introduced various behind-the-scenes improvements and bug fixes.

Before upgrading, please look at these important considerations:
Maps v12 HERE 2021.4 CAN-USA

  • Now, a new set of maps is available, which includes updates and improvements to the accuracy of the map data.
  • This set of maps is supported from the 6.6 version of the OTNav application; please do not use this map set in prior app versions.

WEX integration for FedEx Fuel Locations

  • Now, we support the WEX file format to sync the Fuel Locations.
  • The integration frequency is set to be every hour but past 30 minutes from 4 to 10 am CST.
  • The functionality is enabled by setting these values as TRUE in the Device Manager portal:
    • IsNavSyncLocationsEnabled = TRUE
    • IsCategoryRetrievalInfoEnabled = TRUE
    • IsFuelLocationRetrievalInfoEnabled = TRUE
    • IsLocationRetrievalInfoEnabled = TRUE
  • Fleet POIs (points of interest) sync frequency can be configured in Device Manager using this key NavLocRequestFreqInMins.
  • The Fleet Fuel Locations downloaded to the app correspond to the Primary Region set for the Mobile Device.
  • The Device will take 10 minutes to 1 hour to retrieve the Fleet Fuel locations. The time will depend on the size of the Mobile Device Primary Region set in the RNA/Omnitracs One portal and the network speed.
  • When disabling the functionality through the Device Manager portal, the Fleet POI (points of interest) data is cleaned after closing and relaunching the app.
  • It will take some minutes to clean all the files from the Device.
  • The process to integrate the WEX file is completed when the upload success rate is greater or equal to the percentage set in "successRateForDeletingRemoteFile" (80% is the default value).
  • We improved the verbiage to set the path settings of a region for the OTNav application.

 

NavGE integration to 6.6 Drive app

To enrich your experience with the application, this version includes:

  • Single sign-on integration
  • Vehicle dimension integration
  • HOS (Hours of Services) clock integration

Before upgrading, please look at these important considerations:

  • Use the NavGE v6.24.5 application to integrate with the 6.6 Drive and XRS app 
  • The Drive app integrates the mobile device ID and worker ID to enable the single sign-on functionality.
  • The Drive app integrates the vehicle settings configured in Omnitracs One portal with the NavGE app when using a telematic device.
  • When the app does not have a telematic device paired and/or configured with vehicle settings, the Drive app sends the trip with the default vehicle dimensions: Length: 65 ft - Width: 8 ft 6 in - Height: 13 ft 6 in - Weight: 80000 lb.
  • When the vehicle settings in Omnitracs One portal are configured with zeros instead of real values, the Drive app sends the trip with the default vehicle dimensions: Length: 65 ft - Width: 8 ft 6 in - Height: 13 ft 6 in - Weight: 80000 lb.
  • The HOS clock is integrated into the NavGE app when using the integration with Drive and XRS.
  • The HOS clock will be displayed in the Follow me View and Guidance View.


 

Drive/Command

Post GPS from Drive App
A new position Updated int event handler has been added to device integrator.

A new setting was added to Command --> Universal Config --> Location called "Enable Position Updates". When selected, the mobile device will store and sync location data. The location data will sync based on the existing sync interval defined in the core app settings. This should only be used if the vehicles in use do not have telematics devices installed (AMGC or Relay). Otherwise, this setting should remain off.

An update was made to the Drive app to allow the tablet or smartphone being used by the driver to be the "source" of GPS location data. This is only for scenarios where a telematics device such as an AMGC or a Relay will not be installed.

For integrators, a time zone offset field has been added for all integration events so that the datetime field is properly translated before updates to the TMS system.
The truck icon in Drive now shows the correct connectivity state when used with an AMG-C or a Relay. The icon will be green when Bluetooth is turned on and the connection is established. It will be orange with an exclamation point when Bluetooth is turned off or is lost.

For integrators, Drive now reports the currently connected trailers in the intEvent payload data when a driver has hooked to a trailer.
Drive users have the ability to delete individual messages contained in the Messaging tab.  Clicking on the 3 dots for each message will display the Delete option.

Add the ability to display additional information in MyDayPlanner for both the L1 (trip) and L2 (stop) data
An update was made to Drive / My Day Planner where integrators or customers with direct web services integration to the MilesAhead API can provide additional pieces of data (custom properties) that get displayed in line with the Trip Header and the Stop Headers. Customers who have not built their own integrations will not be able to use this feature.
showInPlanner true/false/default is added in source code and documentation


Misc. Items
An additional property, copilotPathSettings has been added to the Data API /asset-search/attributes API call.
A new checkbox setting has been added to Command --> Universal Config --> Documents to disable Auto Capture for Documents scans. This will require users to manually capture a document by pushing the capture button to help eliminate blurry images. This setting is disabled by default.

Add the ability for the driver to delete a message in OT Drive messaging on the tablet
When using the Pickup or Delivery task in Drive, and using the Document Scanning feature, which is accessed by clicking the "scanning icon" within the task itself, the Drive user will now be prompted to select the type of document in alignment with the Supporting Data list found in Command --> Supporting Data --> Document Types.


Mobile Device Diagnostics - App Version Tracking
When the Handler compares installed apps with apps configured for the customer in the Customer Client Application table, the apps are reported and displayed in Mobile Device Diagnostics in Latitude. 

 

Mobile

RNM - Android 12 Support
RNM has been enhanced to function correctly on Android 12.

 

New Map Service

Omnitracs now uses mapping services provided by HERE maps for FleetView, Site Management, and Trip Monitor.
clipboard_e57b1b91eed8868dbcc2f3559d1eb88e2.png

Only the source of the maps is changing; there are no changes to the way the maps function in XRS, and you will notice only minor differences in some of the tools and controls. For instance, the zoom in and zoom out buttons are in the lower right corner of the map rather than at the top.

The way you change views in site and trip management also differs slightly from previous maps services.

To choose a new view, select the Choose view icon below the zoom buttons.

clipboard_e0967b07bbc99210ba2d28a4bb8e7b1ab.png

Choose View menu opens with options for Map view, Satellite, Traffic conditions, or Show traffic incidents.

clipboard_ec5a2f1046d2ae502ea6864da334c7d80.png

  • Map view: The standard default map view.
  • Satellite: A photographic aerial view.
  • Traffic conditions: Shows current traffic conditions. Red lines indicate heavy congestion; yellow lines indicate mild congestion.
  • Show traffic incidents: Indicates accidents, construction work, and other events that can cause traffic slowdowns or detours.

In both map view and satellite view, you can switch to street view by holding down the Alt key on your keyboard and moving your mouse until you get the angle you want.

clipboard_ed9ba79ddfec141d573aaf757146f606b.png

Note: These options only apply to maps in site and trip management. FleetView has its own controls for changing views, which have not changed.

 

Other Map Features 

Show Labels Option

Show an information box of each driver, site, and vehicle on the map when the Show Labels option is checked.

Feet/Miles or Meters/Kilometers

Maps now display in either Feet/Miles or Meters/Kilometers based on the company’s settings.

Here Lookup City Center button

The Lookup City Center button becomes active when the city, state, and country fields are entered.       

clipboard_ee841027104c7eced6445c4a03d54d36c.png

Lookup Address Button

The Lookup Address button is enabled when the user provides the address, city, country, state. When the button is pushed, the Lat/Long is generated specific to the location.

Breadcrumb heading arrow adjust when map is rotated

When a FleetView user rotates the map, the breadcrumbs heading adjusts properly with the rotation.

A user can apply driver, site, and route filters in FleetView.

Filters:

  • Search box and button
  • Pushpins (Drivers/Vehicles, Domiciles, and Sites):
  • Last Known, Last *** Hours, and Historical
  • Grid view (Map Only, List Only, Map & list)
  • Type view (road and Aerial)
  • Traffic view

 

Mobile Changes - Miscellaneous

Editable “Driving” when Engine Power Down 

 NOTE: This requires upgrade to XRS Mobile 6.50.2. 

In accordance with the provisions of the FMCSA FAQ included above, we have added functionality to edit or correct driving time erroneously recorded due to failing to change duty status before powering off the CMV. When the driver is in an automatically recorded Driving status and powers down the vehicle, the driver’s duty status will be transitioned to Driving (Manual) at the point the power down event is recorded.


Although the drive segment has been transitioned to Driving (Manual), the timer that started following no-motion detection is not interrupted. The driver will still be prompted to go On-Duty 5 minutes after the vehicle stopped and will be automatically switched to On-Duty one minute later if they do not respond to the prompt. The Driving (Manual) segment will be editable by the driver or administrative user.


As an important note, drivers should always manage their duty status by manually putting themselves On-Duty at the conclusion of a driving segment, maximizing the drive time available to the driver.

Allow Driver “Work” on HOS logs while in non-working status

NOTE: This feature requires an upgrade to XRS Mobile 6.50.2 to be fully functional.

Removed the “On-Duty” restriction on Editing Logs or Switching Primary & Co-Driver. Drivers can now Edit their logs or switch Primary & Co-Driver while in Off-Duty or Sleeper Berth status.


Prompt Driver to certify logs when logging into mobile after going On-Duty from Kiosk or Driver Portal

NOTE: This feature requires an upgrade to XRS Mobile 6.50.2 to be fully functional.

Drivers will now be prompted to Certify historical logs, logs on days prior to the current day, when they log into the Mobile even if they have previously used the Kiosk or Driver Portal to go On-Duty before going out to the vehicle.

 

Special Driving Conditions Report Change

Adverse Weather Conditions

When a driver uses the Adverse Weather Conditions option in a selected period, the entry will display in the Special Driving Conditions Report.

Time Clock Report

Driver Id

The Driver ID was added to the Time Clock Report

 

Log Audit Updates

When the OT1 Host is generating an eRODS Extract or ELD Data Transfer (Canada) for multiple drivers and the process fails for a driver in the selection, the system will now skip the impacted driver and continue with the request. XRS Host will communicate to the administrative user which driver(s) failed to the process.

When the OT1 Host is generating an eRODS Extract or ELD Data Transfer (Canada) engine hours and vehicle miles will be blank when the data is unavailable.

When the OT1 Host is generating an eRODS Extract or ELD Data Transfer (Canada) the Unidentified Driver Profile events will include unidentified Engine On-Off, Intermediate, and Diagnostic events.

When the OT1 Host is generating an eRODS Extract or ELD Data Transfer (Canada)

inactive events corresponding to duty status events created by OT1/XRS Mobile when a driver assumes UVA on the Mobile will be included in the Unidentified Driver Profile section.

To prevent issues with the FMCSA eRODS site, the driver's current time zone offset, standard time or daylight time, will be used for the entire eRODS Extract file.

 

Misc

Overspeed Alert Events

Performance Improvements were made for Overspeed Alert Events.

 

Platform

Password Changes

Note: Driver passwords are not affected by this policy.

Password Requirements

A user password will now require a minimum of eight characters. This change will be required when creating new users or editing a current user.

Password Length: At least 8 characters in length

Password Complexity: Should contain at least one character from each of the following groups:

  • Lower case letters
  • Upper case letters
  • Numbers
  • Special Characters

Password Lockout Process

A new lockout mechanism for Password Reset lockouts has been enabled. After five failed attempts, the user is locked out. This lockout is controlled by Omnitracs One and XRS systems and is not adjustable by the customer.

 

RNA Platform (Integrations)

Region Management

For Single Region customers a Region Hierarchy and a Single Root Region has been added. 

A new feature has been added that allows CreateCustomer with isRoot in place to override Region Hierarchy correctly. 

 

Route Modeling
Route modeling has been enabled for selection within the Purchasable Options under Routing. 

 

Misc. Items
The Driver portal now has a log-out button to allow drivers to exit the app safely.
NOTE: Can someone provide me with a clean screenshot of where the logout button is on the app? Pending Screenshot

When logging into Ominitracs has failed, you will be redirected to the Login screen and a message will appear telling you that the login was not successful.  
NOTE: Can I get a screenshot of a failed login with the new message letting them know the login was not successful? Added Image 

A user in OT1 Host using Hours of Service (HOS)/ELD has the Driver’s HOS Settings pre-populated with the Region’s HOS Settings when they switch a Driver to HOS-Use Region Settings = No.

Roadnet Anywhere (RNA) Host for Regions: Entity Administration changes for Default Rule(s).

Remove the Default HOS Rule from region settings.

  • Add Default HOS Rule (USA) to region settings.
  • Only Active when US Ruleset(s) are enabled.
  • Required if USA Ruleset(s) are Enabled.
  • Initially set to Enabled USA Federal Rule.

Add Default HOS Rule (Canada) to region settings.

  • Only Active when Canadian Ruleset(s) are enabled.
  • Required if Canadian Ruleset(s) are enabled.
  • Initially set to CAN 7/70.
  • Once 'Default HOS Rule (Canada)' is set (saved), the dropdown list must only contain the North/South Rules in the same Cycle (e.g. Cycle 1 or Cycle 2)."
  • Roadnet Anywhere (RNA) Host for Drivers: Entity Administration changes for Default Rule(s).

Remove Default HOS Rule from driver settings.

  • Add Default HOS Rule (USA) to driver settings.
  • Only active when US Ruleset(s) are enabled.
  • Required if USA Ruleset(s) are enabled.
  • Initially set to Enabled USA Federal Rule.

Add Default HOS Rule (Canada) to driver settings.

  • Only active when Canadian Ruleset(s) are enabled.
  • Required if Canadian Ruleset(s) are enabled.
  • Initially set to CAN 7/70.
  • Once Default HOS Rule (Canada) is set (saved), the dropdown list must only contain the North/South Rules in the same Cycle (e.g. Cycle 1 or Cycle 2)."

The Roadnet Anywhere (RNA) to XRS entity sync was updated to include sending Default HOS Rule (USA) and Default HOS Rule (Canada) for Regions & Drivers.


 

Routing

  • The existing REST – Route Template web service now includes stop details. sp
  • There is a new REST method for Get, Post, Put, Patch and Delete Route Template Set. sp
  • You can import the Category Size fields as part of the Import Routed Solution. sp
  • You can execute a single Import Routed Solution and add routes to multiple routing sessions. sp
  • You can see the Template Stop Sequence in the Stops grid window, Plot Info and Pick List. sp
  • The Worker's attribute, 'Adjust Service Time Percent', has an improved service time calculation formula. 
  • You can enable an option in the regional settings to round the stop quantity automatically to a whole number. sp
  • You can restrict users with the ability to adjust service time and/or service windows. sp
  • You can adjust the service time factor by worker using a new service time calculation.

 

Strategic Planning

  • You can click the clipboard_ebcc672c07f9bdbd73b46c26c489b8aed.png Options icon in the Map window to select the detail that you want to display on the map. sp
  • Software performance improvements were made in the following areas: deleting routes, creating strategic routes, dragging recurring orders to a new territory, importing the  planning solution, and exporting the planning solution. sp

 

Telematics

 

“Undo” UVA assumed incorrectly by driver

In accordance with the provisions of the FMCSA FAQ included above, a user in a Mixed Mode or ELD Mode company can remove an accepted UVA from the driver who assumed it from the Unidentified Drive Profile on the Mobile. 

Note: This will only be available for UVA accepted by the driver after the upgrade to XRS Mobile 6.50.2.

When the carrier edits or removes accepted UVAs, the driver must confirm or reject the edit.

When the driver accepts the edit, the removed event appears in the XRS Host UVA tool as a UVA that can be reclassified or assigned to a driver.

 

Web Services and Integrations

Omnitracs One REST Web Services

OT1 REST - Modification to Events Endpoint 
The OT1 REST events endpoint will contain co-driver ID and Name for any worker log events that have a co-driver associated with the logs

OT1 REST events endpoint for worker status now includes new properties that are related to 'completed' events such as "Duration" and "Distance" for the particular event.  

The OT1 REST events endpoint for worker status events now includes HOS violations that occurred during the requested begin and end date.

Misc. Items
The OT1 REST workercompliance endpoint now contains a new query parameter for specifying active or inactive workers.

The OT1 REST webservice now includes a parameter to exclude equipment restrictions in the change locations endpoint.

In the OT1 Drive API, the "all" parameter has been removed from the findLevel1Docs endpoint.

New property "totalPlannedServiceTime" is now returned as part of "serviceableStopInfo" object when retrieving a route .


API Documentation
The OT1 REST documentation page now has the option to download the “OpenAPI” spec file.  

Omnitracs One Drive Integration API

 

TMW Total Mail

 

XRS

API command CreateInspectionDriverLogEntry.
New mobile only log entry for inspection events so that the driver's log is correct for current inspection events.

 

User Interface Details

 

Route Template

Routing 
Desktop Client

 

 

Map Options

Strategic Planning
Client Only

Note: Some of the options described are purchasable and may not appear. Contact your Omnitracs sales representative for more information about acquiring additional features.
The Map - Options window allows you to decide how various routing items appear on the map, including whether to display the depots, how the stop markers appear on the map, route colors, and how rush hour and restricted areas and paths appear.
Note: The options on this page generally do not apply to the Map Editor. However, the colors selected for Rush Hour and Restricted Areas/Paths will be used in the Map Editor.

clipboard_ece7517fb34681b8b44b5a90470e05ad8.png

clipboard_e8d77170b17b39e0643eb1b325c501e6d.png

Software Corrections

Work Item Number

Issue

Component

RPE-86240 Fixed an issue where Active Alerts were sent out multiple times for the same stop. Active Alert
RPE-87881 Fixed an issue in Active Alert where the authentication link is not sent during the sign-up process when the Enable Verification option is switched disabled. Active Alert
RPE-84587 Fixed an issue where customer was not able to install Omnitracs Navigation because they are limited to the Install Unknown Packages requirement that sends an MDM locked device to Settings. Android IVG Skins
RPE-88748 Fixed an issue when upgrading from OT1 6.2 to 6.4 with a Navigation folder in the root, the app would get stuck on the Migration loader page. Android IVG Skins
RPE-79704 Fixed an issue whereby you are always prompted to change the Primary Region when editing a piece of equipment. Dispatching
RPE-83625 Fixed an issue whereby attempting to add 'Location Comments' to the Mobile Workflow resulted in a 'Server is Busy' error. Dispatching
RPE-84370 Fixed an issue whereby attempting to insert a 'Reload' on a route did not save the reload to the route. Dispatching
RPE-84891 Fixed an issue in Fleetview where the GPS data is not up to date. Dispatching
RPE-87531 The Maintenance context menu was updated to display the menu option, Stop Cancel Reason Codes. Dispatching
RPE-87532 The Maintenance context menu was updated to display the menu option, Order Cancel Reason Codes. Dispatching
RPE-87603 Fixed an issue whereby device running RN Mobile displayed Server Error 500 when attempting to unload a route. Dispatching
RPE-87645 Fixed an issue whereby the Assign Resource window displayed deleted and active drivers.  The window now only shows 'Active' resources. Dispatching
RPE-88345 Fixed an issue whereby device running Roadnet Mobile were displaying 'Error 500' and stops were not showing 'Completed' in Fleetview. Dispatching
RPE-89420 Fixed an issue whereby multiple routes in Fleetview stopped displaying GPS data from the XRS relays. The arrivals/departures are working, but the GPS data was not available. Dispatching
RPE-83309 Fixed an issue in the Interactive Geocoder whereby the HERE Candidates window located in the bottom-right margin was missing. Geocoding
RPE-85133 Service Locations with a Geocode Method,  "None", are now visible on the 'Not-Geocoded' view. Geocoding
RPE-85599 Addressed an issue where GPS geocoded locations were showing up as "Needs Review." Going forward, Service Locations that have been GPS Geocoded will have their "Geocode Attention Reason" set to "None" and will not appear under the "Needs Review" or "Not Geocoded" view.  Geocoding
RPE-83618 Fixed an issue whereby Import Service Locations did not update service window overrides correctly. Import
RPE-83799 Fixed an issue whereby the Import Depots File Layout did not show the correct field names when the option, Use Line Items, was disabled on the Business Unit. Import
RPE-84938 Fixed an issue where the state drop-down menu was blank when using the Maintenance - Equipment page. Integrations
RPE-88059 Fixed an issue where the Rest API WorkerLogs were not working. Integrations
RPE-88167 When a customer does not have compliance enabled, the user is unable to save a worker due to empty compliance fields. When the worker is in the host, we deactivated that flag to allow the worker to be edited. Integrations
RPE-88682 We improved the GetDriversStatus endpoint that receives a list of driver IDs and returns their status in a single operation vs. one driver at a time. Integrations
RPE-85085 Fixed an issue where the system was unable to successfully update travel speeds due to underlying map data errors. Misc
RPE-87405 Fixed an issue where the CellComm App was missing from Omnitracs Navigation Quick Menu in version 6.4.0.007. Misc
XRS-11841 Fixed an issue where the driver was forced to logout of OT1/XRS Mobile after receiving the Sleeper Berth/volume warning. Mobile
XRS-14704 Fixed an issue where the drivers ELD login is missing the odometer value. Mobile
XRS-15057 There was an issue where the trailer did not disappear from the App after dropping the trailer. This issue has been resolved. Mobile
XRS-15395 There was an issue where an ELD exempt driver was not required to complete a pre-trip inspection (DVIR) despite the fact that the organization requires it. This issue has been resolved. Mobile
XRS-16199 Fixed an issues when drivers cross from the U.S. to Canada and the rule set changes to the wrong Canadian rule set. Now the CAN 7/70 hrs. rule set which is the Default HOS Rule set enabled for the drivers organization. Mobile
RPE-83868 Fixed an issue where the Mobile Device Diagnostics export did not populate the Last Contact field. Mobile Manager
RPE-86453 Fixed an issue where exporting from the Mobile Device Diagnostic Screen is limited to 1000. Device diagnostics export will request and accumulate all devices in batches of 1000 and export them as a csv file. The Mobile Device Diagnostic Screen is unchanged and will only show the first 1000 statuses. Mobile Manager
RPE-88346 Fixed an issue where messages were sent to drivers who are no longer active, but are still with the company and have no depot assigned to them. Mobile Manager
RPE-89588 Fixed an issue whereby the application returns a 'Server is busy' error when retrieving Service Locations in the Desktop Client or Web for the first time. Performance
RPE-83558 Fixed an issue where a feature was available to customers who did not purchase the feature. Only customers who purchase Enterprise Routing or Dispatching, are presented with the menu item, "Update Routing or Dispatching". Planning
RPE-86903 Fixed an issue whereby the Export Planning Solution process did not execute a Post Processor when a post process is specified.  A post processor will now execute. Planning
RPE-87040 Fixed an error running Save Session As when reload depots are assigned to routes. Planning
RPE-87647 Fixed an issue whereby the Transfer Session process returned an unexpected error when Service Locations have Service Time Overrides. Planning
RPE-87822 A Shift Days bug was resolved whereby the application attempted to shift days for Recurring Orders assigned a service pattern set, Days Between service, even though such recurring orders did not exist. Planning
RPE-84183 Fixed an issue whereby the Route Query for a date range did not return expected routes after the user change regions.  Routing
RPE-84310 Fixed an issue whereby the user was unable to delete a route or move stops from the route.  An order on the route contained data in an order custom property that prevented the delete or move.  Routing
RPE-85072 Fixed an issue whereby the Stops grid window did not display the order's service window overrides. Routing
RPE-85379 Fixed an issue whereby the 'Export' orders grid window feature in the Desktop Client generates a blank file. Routing
RPE-85461 Fixed an issue whereby the 'Force Sequence by Cost' feature was changing the route's start time. The routes' start times do not change. Routing
RPE-86129 Performance improvements were made to the Create Routes process to fix an issue whereby the Routing pass was taking to long to run. Routing
RPE-86451 Fixed an issue with Create Strategic Routes where the process returned an 'unknown error' when a recurring order contained an invalid service pattern. Routing
RPE-86917 Fixed an issue where some Roadnet Mobile devices loading a route would receive an unexpected error. Routing
RPE-86979 Fixed an issue in Centralized Messaging that displayed a message read by a inactive driver. In addition, logic was created to ensure that inactive drivers do not receive messages. Routing
RPE-87338 Improvements have been made to the application's responsiveness during user login. Routing
RPE-87651 Fixed an issue whereby the Total Distance value displayed on the Driver Directions did not match the summed distance value of the route. Routing
RPE-87762 Fixed an issue where a route's equipment assignment was randomly changing after the driver loads his route in Roadnet Mobile. Routing
RPE-87773 Fixed an issue when saving changes to the Pass Template resulting in a Duplicate Data Error. Routing
RPE-87821 Fixed an issue in Roadnet Anywhere, where a user with the Managers role could not save an edited driver log. When clicking on Save, the system did not save the change and displayed the Compliance Dashboard screen. Routing
RPE-88294 Fixed an issue whereby the Account value added on the Service Location was not syncing between the Desktop Client and the web applications. Routing
RPE-88704 Fixed an issue whereby the routing process is using preferred route IDs and the routing pass option, "Only Create Routes From Templates", is enabled, that dynamic routes are not created. Routing
TM-3068 Fixed an issue when performing an IFTA Filing and the Manitoba filing was missing the tax rates. Tax Manager
TM-3255 Fixed an issue when performing an IFTA Filing, Pennsylvania was not filling the totals fields. Tax Manager
TM-4142 Fixed an issue the hut rate for Oregon was not being properly calculated when the vehicle is over 80,001 lbs. Registered Laden Gross Vehicle Weight and has more than 5 axles. Tax Manager
TM-4157 Fixed an issue in Tax Manager in the Reconciliation report where he surcharge column is rounded to two decimal places instead of the four that are needed for the rate. Tax Manager
TM-4159 Fixed an issue where the Oregon HUT rates were out-of-date. Tax Manager
TM-4160 Fixed an issue in Tax Manager Vehicle maintenance where some vehicles in the vehicles tab could not be edited. Tax Manager
RPE-84824 Fixed an issue in Daily Plan where pickup orders quantities were not returned correctly. WebServices
RPE-85726 Fixed an issue when populating the Order entity in the SOAP SaveOrders service. WebServices
RPE-86662 The server was configured to have character limit for the total URL that can be passed in a GET request for identifiers in a query parameter. If a caller exceeds that limit they will get an message about the limit. WebServices
RPE-87340 Fixed a specific data error when adding a planning session through the REST API. WebServices
RPE-87341 Fixed an issue where an error occurred when creating a territory through the REST API using the territories endpoint. WebServices
  • Was this article helpful?