Omnitracs OT Drive Fleet Management Software User Guide

Omnitracs OT Drive Fleet Management Software

Product Information

• Specifications:
  • Product Name: RN Mobile v7.0.0.14
  • Supported Platforms: Android 14 and higher
  • Release Date: May 30, 2024

Product Usage Instructions

• Upgrading OT1 Mobile:
  • Please be aware that upgrading OT1 Mobile using an MDM or the OT1 Installer application will result in logging the driver out of the XRS Mobile application. Drivers will need to re-login once the upgrade is complete.
• Support for Android 14:
  • To install or upgrade the application on Android 14 devices, the driver will be prompted for appropriate application permissions. If permissions are repeatedly denied, a permission explanation message will appear before the app closes.
• Adding Full Cycle ‘Recap’ Values:
  • A new option called ‘Cycle Recap’ has been introduced for drivers on XRS, allowing access to recap hours for the driver’s last duty cycle (7, 8, or 14 days). This feature helps drivers and dispatchers plan better.
• Work Time Extension Enhancements:
  • When a driver selects/declares a Big Day/Adverse Weather Exception, it will now be associated with the driver duty status and reflected in the ERODS transfer file automatically. This eliminates the need for manual intervention to add a remark.
• Refactoring ‘Off Duty in Passenger Seat of Moving Vehicle’ Implementation:
  • The XRS mobile log editor has been updated to prevent users from editing or deleting mobile-system-created Off Duty Passenger Seat Remarks.

FAQs

• Q: How do I access the Cycle Recap feature?
  • A: To access the Cycle Recap feature, long-click on the HOS option, and navigate to HOS -> options -> Cycle Recap on XRS.
• Q: What happens if I repeatedly deny permissions during installation?
  • A: If permissions are repeatedly denied during installation, a permission explanation message will be displayed to help you understand why they are required before the app closes.

Mobile Production

Omnitracs One v7.0 – Mobile Production Release Notes

• RN Mobile v7.0.0.14
• XRS Mobile v 7.0.0013
• OT Drive v7.0.0.0014
• OT Nav 1.0 v7.0.0.003
• OT Nav 2.0 v7.0.0.0005
• NavGE v6.27.1
• Omnitracs One Installer v6.9.0.13
• Release Notes
• Updated May 30, 2024

IMPORTANT NOTICE

Please be aware that upgrading OT1 Mobile using an MDM or the OT1 Installer application will result in logging the driver out of the XRS Mobile application. Drivers will need to re-login once the upgrade is complete.

Compliance – Hours of Service

New Enhancements

• Support for Android 14
  • To provide users with a safe and secure experience, and to meet the highest-level platform requirements, we have extended the app functionality to also support Android 14 devices.
  • The driver will be prompted for the appropriate application permissions to be accepted when installing the newly published application or while upgrading.
  • If the driver repeatedly denies providing the permissions, a permission explanation message has been added to help understand why they are required and the app closes.
• Adding full cycle ‘recap’ values
  • With this enhancement, we introduced a new option for the drivers called- Cycle Recap on XRS, similar to data on IVG which is accessible by a long click on the HOS option, and in HOS -> options -> Cycle Recap.
  • This would allow drivers and dispatchers to plan better.
  • It would display the recap hours on the mobile for the driver’s last duty cycle (7, 8, or 14 days)

Work Time Extension Enhancements

• Current Behavior:
  • When a driver selects/declares a Big Day/Adverse Weather Exception, it is not associated with the driver duty status and hence does not reflect in the ERODS transfer although the driver enters a remark.
  • Thus, it is still identified as a potential violation in the FMCSA ERODS site.
• New Behavior:
  • The ERODS transfer file shall reflect an automatically appended annotation. This will be associated to the driving duty segment for the Big Day/Adverse Weather Exception, past the 14 hour on-duty rule.
  • This would take out the need for driver’s manual intervention to add a remark.
  • If the driver declares a Big Day exception/Adverse Weather exception at any point in their shift on a particular day and goes ahead to utilize it without canceling, the system would now annotate that (the exception) against the duty status of the driver.
  • The annotation would read- “16-Hour Big Day Exception” or “Adverse Weather Exception”. This annotation would be against the driving duty status of the driver at the time of exceeding the 14-hour rule.
  • In the case where the driver takes multiple breaks during the extended two-hour period, then each driving segment will have an annotation.
  • This also applies to any manual driving or UVA accepted as driving that exceeds the 14-hour limit if the extension was declared.
  • The annotation shall reflect in the mobile logs in the Inspection mode and the mobile ERODS transfer.
• Re-factoring ‘Off Duty in Passenger Seat of Moving Vehicle’ implementation
  • With this enhancement, we have made changes to the way of handling the Off-Duty Passenger Seat Remark in XRS mobile.
  • The XRS mobile log editor will now prevent the user from editing or deleting mobile-system-created Off Duty Passenger Seat Remarks (In the Passenger Seat of a Moving Vehicle).

The remark would get auto-deleted in the following cases:

• a) if there is an edit that causes the duty status at that time to be something other than off-duty and a corresponding event would be relayed to the host.
• b) if the co-driver status is removed by host edit at the time of the remark event- In Passenger Seat of Moving Vehicle.
• c) if accepted UVA overlaps it.

Improvements

HOS Issues

• XRS-30206 – 2nd driver unable to log in app crash
  • We resolved an issue where the first driver logs out and post trips and then the second driver is unable to log in when the app settings are in Spanish.
• XRS-28142 – Erroneous Validation Sleeper Berth Message
  • We resolved an issue with the incorrect sleeper berth validation that was disallowing the driver from editing the logs. If the vehicle could not be identified when attempting to make edits during the driver log period, currently the application was applying a validation and returning an error assuming the vehicle did not have a sleeper berth. This has been corrected such that the application does not restrict the driver edits by returning a validation error where it does not correspond.
• XRS-23831 – Drive- OT1- Retroactive violation on current day
  • We resolved an issue where the Driver does not restore the 14-hour clock (Will Pair) and shows the driver in violation for the current day. When a driver begins a new shift, retroactive violations from the previous shift will now be cleared. This will prevent us from reporting that the driver is still in violation.
• XRS-29467- Accumulated Vehicle Miles and Elapsed Engine Hours incorrect on events edited by the driver
  • We resolved an issue wherein after the driver edits a terminating On Duty event, the Accumulated Vehicle Miles and Elapsed Engine Hours values for that Driving segment were no longer correct. They were being overwritten with whatever is the AVM/EEH at the time the edit was performed.
• XRS-30898- Increase in the number of Diagnostic Events reported in HOS
  • We resolved an issue where customers were noticing an increase in the number of diagnostic events in HOS which was due to the outdated SDK version of the Drivewyze causing Drive application and XRS to crash leading to the diagnostic events.
• XRS-20738- HOS Clock Not Computing Properly
  • We resolved an issue where the mobile HOS dashboard 11 and 14-hour clocks showed higher values than the 70-hour clock and did not sync with each other.
• XRS-23949- OT1/XRS: The driver was able to log out from the OT1 Drive app while in Drive status.
  • We resolved an issue where the driver was allowed to log in from Drive while still being in the Driving duty status in the HOS application.
• XRS-30826- OT1- The driver was able to change Canada Cycle when not legally allowed to
  • We resolved an issue where the Driver was able to change to the Canada 14/120 rule set when they should have not been able to without a cycle reset.
• XRS-30957- XRS doesn’t allow using Android’s default mapping/navigation settings in OS 11 or higher
  • We resolved an issue with navigation settings where the XRS application was not allowing us to use Android’s default mapping/navigation settings in OS 11 or higher. This has now been resolved by adding NavGE as a preferred navigation provider such that the workflow searches among the defined navigator providers and if found, it opens it directly according to the order defined on NavigatorProvider.

UVA Issues

• XRS-30321- Unable to Reject UVA when there is existing driving on logs
  • We resolved an issue where the driver was getting stuck on a screen when rejecting a UVA edit and was encountered an error stating that it overlaps with the existing driving on the logs wherein this error should appear when they try to accept but this is not the case here.
• XRS-26962- All Driver Logs set to Inactive Changed when UVA assumed/accepted
  • We resolved an issue where a UVA ‘session’ that contains multiple Drive/On-Duty pairs is assumed/accepted by the Driver, and all of the Duty Status changes from the start of the UVA ‘session’ to the end of the UVA ‘session’ are marked as ‘Inactive-Changed’ and the UVA terminating On-Duty is not processed into the Driver’s log

Compliance – OT Drive / DVIR New Enhancements

• Command – “Inspect trailer assets only” configuration added for all DVIR tasks
  • A new configuration for all Drive DVIR tasks has been added to Command. When enabled, “Inspect trailer assets only” will only display the trailer(s) associated with the driver’s current assets in the DVIR form. This feature is especially useful for DVIR tasks that may occur during stops where drop & hook events are common – where only trailer inspections must take place, not a tractor inspection. This saves the driver time by enabling them to skip an unnecessary re-inspection of their tractor if they intend to continue to use the same vehicle for the duration of their trip.
  • This configuration is disabled by default for each respective DVIR task within the Command Task Library – including DVIR, Pre-Trip, Post-Trip, and any other DVIR task “clones” that may have been created within each Workflow
  • Template. As a best practice, it is recommended that users clone the base DVIR task and rename the clone “Trailer Inspection” or something similar, and subsequently enable this new configuration only for the clone, or tasks designated specifically for trailer inspections. DVIR tasks that are used commonly to perform inspections on tractor assets (ex: base DVIR task, Pre-Trip, Post-Trip) should NOT have this configuration enabled.
• Canadian Vehicles & Trailers – DVIR Tasks and “Previous DVIR” display Odometer values in KMs
  • Canadian customers who have vehicles and trailers registered in Canada or Quebec will now see the Odometer values reflected in Drive DVIR tasks and the “View Previous” task represented in Kilometers, no longer Miles. Vehicle and trailer assets that are maintained in the Omnitracs One Portal “Equipment” list which has a Canadian province as the registered location will see the Odometer value reflected in KMs automatically.
• Unknown Assets – Country and State / Province dropdown lists
  • If a Drive user enters an “unknown asset” into the DVIR form, they will be presented with 2 new dropdown fields, Country and State / Province. This data will be used to determine the asset’s registration location.
  • Additionally, upon entering the registration location data, the Odometer value reflected will be in Miles for US locations or KMs for Canadian registration.
• Improvements
  • DVIR-1721 – DVIR Task Clones are “Adhoc” enabled by default
  • We resolved an issue where DVIR task “clones” were automatically added to the Drive Adhoc tasks list in the previous release, 6.9. Unless explicitly enabled by the customer within the Command Task Library, DVIR task clones will no longer be visible in the Adhoc task list. Only the base DVIR task will be visible in Adhoc tasks.

Roadnet Mobile

New Enhancements

• Roadnet Mobile – Support Android 14
  • This version supports Android 14 (API – Application Programming Interface 34). This update maintains all the functionalities from the previous version, ensuring a seamless transition and consistent user experience.
• Roadnet Mobile – Support iOS17
  • This version supports iOS17, this update maintains all the functionalities from the previous version, ensuring a seamless transition and consistent user experience.
• Roadnet Mobile – Supports the integration of Active Alert messages
  • This capability is a limited-release feature that will not be visible by default to users. Please contact your Account Manager if this use case applies to you.
  • We’re thrilled to share that Roadnet Mobile is getting a new capability with the release of version 7.0.
  • When Active Alerts for Roadnet Mobile are configured in the host, and the recipient worker is set as a Frontline worker, the subsequent route assigned to the recipient worker will receive the Active Alerts.
• Roadnet Mobile left, and the Active Alert URL, right, opened using web view
  • Roadnet Mobile – Inbox now supports opening URL links inside the application using web view Now, you can effortlessly open links in Route Note messages directly within the app, without the hassle of switching to a separate application. Enjoy a smoother and more integrated user experience with this convenient enhancement!
• Roadnet Mobile for iOS – Supports a new integration with Omnitracs Mobile Manager
  • We are thrilled to announce a significant improvement to Roadnet Mobile for iOS that will streamline the workflow and provide a seamless experience for Omnitracs Mobile Manager (OMM) users.
  • Now, workers configured in the RNA host to launch Omnitracs Mobile Manager can conveniently overview critical details and insights regarding their fleet’s operations, enhancing visibility and control over their assets on the road.
  • This enhancement will not only improve efficiency but also contribute to a more streamlined and productive experience for team members using OMM in conjunction with Roadnet Mobile in iOS.
  • Edit the Worker Type form, left, and the Omnitracs Mobile Manager shortcut, right.

Improvements

• RPE-107271 – Quantities Header is Properly Displayed for RTL Languages on Roadnet Mobile iOS
  • Previously, the quantities header was displayed in LTR (left to right) orientation. With the implementation of a fix in version 7.0, the header is now correctly displayed in RTL (right to left) orientation for improved readability.
• RPE-114654 – Support negative values with decimals in the Numeric Response Type Mobile Form
  • Now, users can seamlessly input negative values with decimals in the Numeric Response Type Mobile Form for Roadnet Mobile.
• RPE-112064 – The Planned Quantities values are preserved for orders with Line Items when suspending stops or routes
  • Previously, there was an issue where suspending a stop or route would result in planned quantities being reset to zero on both the host and Roadnet Mobile. With the latest update, this issue has been resolved. Now, when using orders with line items, the code in Mobile Communicator checks if the stop is a redelivered stop with a null planned sequence number. In such scenarios, instead of relying on the quantities columns (which are reset upon suspension), the system now checks the Planned Quantities tables, ensuring data integrity.
• RPE-94869 – Roadnet Mobile properly sends the destination address to Navigation apps when using the manual location search
  • Previously, an issue occurred during a manual location search, causing the application to send the current location point as the destination address. With the 7.0 update, the application now employs a method to pass the searched location string. If a match is found, it returns the location and sends the coordinates to the navigation app. This ensures that the route is directed to the destination that was entered manually.
• RPE-111658 – Roadnet Mobile allows updates to the Equipment
  • Previously, users were unable to update the Equipment Type due to a drop-down issue. However, this issue has been resolved and users can now easily update their equipment by selecting the Equipment Type from the drop down menu within the mobile app.

Workflow (OT Drive / Command)
New Enhancements Drive updated to fully support Android 14 devices

• The Drive app has been updated to fully support compatible Android 14 devices.
• For device compatibility, please refer to the Omnitracs One “Compatible Devices” page found here: Compatible Devices

Barcode scan input control for Smart Forms

• Smart Form text entry fields can now be configured to support barcode input. This feature uses the mobile device camera to scan and interpret barcodes into raw data, which populates the text field of the form.
• Additionally, barcode scanning-enabled fields can be configured to “auto scan”, which automatically launches the barcode scanner when the field is selected – otherwise, the user will need to click on the “barcode icon” next to the field within the form to launch the scanner, which is the default functionality.
• Also, a configuration is available to “move to next”, which is useful for customers who may have multiple barcode scan fields in a row. This attribute can be added to the field and automatically move to the next field of the form once a scan has occurred / the field is populated with data from the scan.

PLEASE NOTE:

• Only standard 1D barcodes are supported, not QR codes, 2D or 3D barcodes.
• This feature is only designed to use the mobile device camera for scanning. Customers who use devices with integrated hardware scanners (ex: Zebra, Honeywell) should use a supported “data wedge” application from their device manufacturer in conjunction with Drive to support hardware-based scanning.
• The barcode scanning input control can only be enabled via a JSON smart form upload to Command. Customers who use the Omnitracs One Portal / RNA “Mobile Forms Designer” will not have this option available when building forms. Please refer to the most current Smart Forms Documentation or contact a support representative for more information.

Pickup & Delivery Tasks “Enhanced” Document Scanning feeds details to Order Status report

Drive customers who have the “enhanced” document scanning option enabled for the Pickup and Delivery tasks will now see the details captured along with the scanned image itself added to the Order Status report in the Omnitracs One portal / RNA. This includes the Document Type, Number (aka document number), and Comments associated with each scan instance.

PLEASE NOTE:

• If not previously enabled for your account, you must have the Mobile Productivity “Picture Notes” feature enabled for your Omnitracs One account for the Order Status Report to populate with these details. Please contact a support representative if you wish to add the Picture Notes feature to your account.
• This feature is only supported within the standard Drive Pickup and Delivery tasks. Customers who use separate tasks like “Documents” or “Photos” will not see the data from these tasks populate within the Order Status report.

Improvements

• DCMD-8370 – Smart Forms “Groups” – Removing a group clears data entered in previous groups
  • We resolved an issue encountered when using the “groups” feature within a Smart Form when clicking the “ – “ symbol to remove a group that would clear the data entered previously completed groups (if present).
• DCMD-8634 – HOS Clocks UI exhibiting strange behavior when changing Duty Statuses
  • We resolved an issue that was causing the visual elements of the HOS clocks displayed in the Drive HOS tab and the HOS Clock banner to “tear” and flicker, especially when multiple Duty Status changes were made within the Drive app in a short time.

Navigation New Enhancements

• Omnitracs Navigation 2.0 (CoPilot) – Support Android 14
  • This version supports Android 14 (API – Application Programming Interface 34). This update maintains all the functionalities from the previous version, ensuring a seamless transition and consistent user experience.
• Omnitracs Navigation 2.0 (CoPilot) – Fleet Portal settings are now available in the Account Manager
  • To help you better manage Omnitracs Navigation advanced settings, FleetPortal settings are now available under the Account Manager web tool too.
  • The Account Manager tool will provide the same features as FleetPortal. Only the look and location of the application are changing.
  • Create or update vehicle routing profiles and assign custom location content (from ContentTools) to new or existing groups.
  • FleetPortal, left, and the new Configure Fleet Settings, right, in Account Manager
• OTNav 1.0 – Support Android 14
  • This version supports Android 14 (API – Application Programming Interface 34). This update maintains all the functionalities from the previous version, ensuring a seamless transition and consistent user experience.

Improvements

• DCMD-6907 – The OT1 Driver ID is displayed in the Trimble Route Reporter for Omnitracs Navigation 2.0
  • Previously, the Driver ID was not displayed, even though the value was correctly assigned to the trip. This issue has been resolved, and now when a trip is triggered from the Omnitracs dispatcher application, the Driver ID is properly displayed in the Trimble Route Reporter tool. This enhancement ensures that users have access to accurate and reliable information, making it easier for them to manage their trips and track their drivers’ activities.
• RPE-83265 – In Omnitracs Navigation 2.0, now a routing profile remains properly selected when switching from the Company Profile tab to My Profiles and back
  • Earlier, an edge scenario existed where transitioning between tabs could lead to the application unchecking the routing profile, inadvertently enabling users to start a route without a selected profile. This issue has been resolved in the 7.0 release, ensuring that a routing profile remains selected even when navigating between tabs.
• RPE-83265 – Omnitracs Navigation 2.0, improve the way of handling waypoints
  • Previously, the first waypoint listed on the plan screen was not being properly handled, causing the application to set up as the starting point. Now, when a trip includes waypoints, they are handled correctly, and the plan screen displays the details accurately. This improvement ensures that Navigation provides accurate and reliable information to users, making it easier for them to plan their trips and navigate to their destinations.
• RPE-109656 – When active mobile devices are de-activated through the import method, the Omnitracs Navigation 2.0 and NavGE license is automatically unassigned
  • Previously, when using the import method to deactivate mobile devices, the Navigation license remained assigned, resulting in having assigned licenses to inactive devices that drivers cannot use.
  • In the 7.0 release, we implemented new logic within the Mobile Device Event Listener. This logic checks the active flag, and if set to false, automatically deactivates the associated licenses. Please note that customers who imported mobile devices previously marked as “inactive” with assigned licenses will need to re-import these inactive devices and edit another field, such as the description, to trigger the removal of licenses.
• RPE-112658 – Route Navigator now supports the activation of NavGE
  • Previously, NavGE activation was only available through the RNA site, but now it can be managed directly from the Route Navigator under Dispatching -> Mobile Devices. The support in Route Navigator also allows for the export of data in an Excel file, which includes details of all devices that have Verizon NavGE enabled. This enhancement will make it easier for users to activate NavGE and manage their devices more efficiently.
• RPE-96108 – The NavGE app now seamlessly syncs Ferries, and Historic Traffic values from the Verizon portal
  • Previously, these keys were not supported for back-office configuration. However, the latest updates have resolved this issue, ensuring that the NavGE app synchronizes not only Ferries and Historic Traffic, but continues supporting U-Turns and Toll Road data flawlessly. This enhancement grants greater control over the fleet and delivers a more reliable and efficient routing experience.
• RPE-110036 – For Omnitracs Navigation 1.0, now Navigation Change Events are properly delivered
  • Previously, an issue prevented Navigation Change Events from being properly delivered to Fleetview. We’re pleased to inform you that this issue has been resolved. Navigation Change Events are accurately transmitted to Fleetview, and you will see them displayed in Notifications when OT Nav 1.0 initiates a recalculation or issues a speeding alert.

Compatibility Requirements

Please refer to our minimum requirements for system components that are used with these solutions:

• Compatibility requirements for devices, operating systems, and browsers
• Certified mobile devices
• RNA routing and dispatch client specifications

Copyright © 2024 Omnitracs, LLC. All rights reserved. This document contains confidential, trade secret, and/or privileged material of Solera and Omnitracs, a Solera company, and may not be shared with anyone outside the intended audience without written approval from Solera. Rev 1.4 – 05.30.2024

References

• Account Manager - Trimble Maps
• ContentTools
• Omnitracs One
• Requirements
• FleetPortal

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>