New Features and Enhancements
Note: Some of the options described below are purchasable and may not appear. Contact your Omnitracs sales representative for more information about acquiring additional features.
- You can have Google Maps direct the worker to a service location's street address instead of the service location's geocode.
- You can receive a notification and an audible alert when you are at risk of grounding your vehicle, when you are near a railway crossing that has barriers and signals, and when you are near a railway crossing that does not have barriers and signals.
- Enhancements to the usability of Omnitracs Navigation include that you must confirm that you want to cancel a trip, when a route is unable to be calculated due to vehicle settings, Omnitracs Navigation will automatically try to re-calculate a path, and when arriving at a stop, the address of the stop will now display in the Arrived area of the "You have arrived at your stop" screen.
- The region filter in Omnitracs Web has been updated to make it faster and improve searching.
- The Performance Alert report now includes alerts for additional Black Box events.
- In the Scorecard report, the Driver ID is now displayed in a separate column rather than included parenthetically next to the driver name.
- Vehicle inspection forms now include an item to prove drivers in some areas have checked for Spotted Lanternfly.
- The Driver Log Editor will now better handle Daylight Savings Time.
For drivers in ELD Mode companies, or for those in Mixed Mode companies who are associated to an ELD vehicle, Inspection Mode is now turned on by default in the HOS Log screen. When Inspection Mode is turned on, violations are not displayed on the grid.
The ERODS File Transfer option on the HOS Options menu is now always available. If the file cannot be sent, the driver receives a message explaining why it cannot be sent.
In order to prevent a driver from being put in violation when the driver’s duty status is being backdated after a drive segment, the mobile now implements a “blackout period”—a period when the automatic On Duty timer is enabled. During this blackout period, the HOS calculations continue and the HOS clocks are updated, but events and violations (for example, shift reset, Canadian deferral, or no rest break) are ignored. When the On Duty timer is disabled (due to manual or automatic duty status change, or because the driver starts driving again), an HOS calculation will be performed and any resulting events and/or violations will be processed.
The new Canadian Fertilizer Exemption rule has been implemented.
Previously, drivers could not select the Big Day exemption until they had 30 minutes or less of duty time remaining. Now drivers who are eligible to use the Big Day option can select it up to six hours before they reach their 14 hours of duty time for the duty tour. Once Big Day has been selected, it cannot be removed.
On many screens in HOS Mobile, previously untranslated text has been translated into French, and corrections have been made to other translated text (both French and Spanish).
To make it easier for drivers to add a manifest number, an Enter Shipping Info component has been added to the driver dashboard. To make it easier for drivers to add a manifest number, an Enter Shipping Info component has been added to the driver dashboard.
Drivers using Personal Conveyance can now access the Fuel Purchase menu option in order to enter fuel purchases.
Previously, when a driver used HOS Mobile in offline mode, only log data was synchronized with the host after the connection was re-established. Now additional data and settings, such as fleet and company details, vehicle type, messages, and forms, will be synchronized as well.
If a company is set up to carry inspection defects over from previous DVIR inspections, any defects from previous inspections that have not been repaired yet will be automatically checked on the inspection form when the driver inspects the vehicle or trailer.
The trailer inspection process now allows drivers to enter the odometer value of the trailer they are inspecting (pre- or post-trip). After they have confirmed the inspection and certified that the trailer is safe to operate, the Driver Certification screen appears, displaying the trailer’s ID and condition and allowing the driver to enter the odometer value. The value must be numeric and consist of no more than 7 digits. The odometer value is sent to the host along with the corresponding inspection form. This field can be left blank.
When a driver enters comments for a defect during an inspection, the comments now carry over to all subsequent inspections until the driver unchecks the defect or until it is certified as repaired on the host. Drivers can edit comments that have been carried over.
Drivers using mobile devices with a fixed display are now prompted to update the Omnitracs Relay at login and logout if pre- and post-trip inspections are not required. Inspection requirements are company settings configured in the host. If pre-trip inspections are not required, the Relay update prompt appears at login. If post-trip inspections are not required, the Relay update prompt appears at logout.
Using the Street Address in Google Maps
If your workers use Google Maps to navigate to a service location, and they make their deliveries to the front door, workers might find that the directions provided by Google Maps are not always accurate.
To provide directions to a worker, Google Maps manipulates the geocode information sent from Omnitracs. This can result in Google Maps providing inaccurate directions. Now, you can choose to send the street address to Google Maps instead of the geocode. This prevents Google Maps from manipulating the information and the worker is directed to the front door of the service location with more accuracy.
To have Omnitracs send street addresses to Google Maps rather than geocodes, you must turn on the Use Address for Google Maps Navigation region setting.
Administration > Regions > Add/Edit Region > Phone Settings > Smart Phone - Allowed Worker Actions
Note: If your workers deliver to a loading dock or back door, Omnitracs recommends you do not use this setting.
New Alerts for Grounding and Railway Crossings
Letting your workers know when an unsafe event is about to occur can deter mishaps and accidents. For instance, being alerted to the risk of grounding their vehicle can certainly change the way a worker drives down a hilly road or if the worker knows a railway crossing is less than a mile away, they can prepare to stop for a train. New alerts have been added to Omnitracs Navigation to help your workers identify possible risks on their trips.
The Risk of Grounding alert lets your worker know when there is a risk nearby of the vehicle grinding on the road surface and getting stuck. The Protected Railway Crossing alerts the worker to a nearby railway crossing with automatic barriers and signals, so it can be approached with caution. The Unprotected Railway Crossing alerts the worker to a nearby railway crossing that does not have barriers or signals. By default , each alert is enabled. Your workers must turn it off if they do not want to receive notifications. For each alert, the worker can change the Alert Distance and if wanted, turn on an alert sound.
The Risk of Grounding, Protected Railway Crossing, and Unprotected Railway Crossing alerts are managed under Menu > Settings > Alerts.
Tap the appropriate alert and toggle it to On or Off. Use the + and - icons to set the Alert Distance to a minimum distance of .1 mile up to a maximum distance of 1.0 mile. Omnitracs Navigation will send a notification to the mobile device when the alert distance is met. If the worker wants an audible alert, toggle Alert Sound to On. The worker will receive an audible alert in addition to the notification, when the Alert Distance is met.
Usability Enhancements to Omnitracs Navigation
Enhancements have been made to Omnitracs Navigation so that your workers get a more user friendly experience.
So that a worker doesn't cancel a trip accidentally, a confirmation screen now displays when Cancel is chosen. This gives the worker the opportunity to abort the action before the trip is canceled.
Previously, when a route path was not able to be recalculated, due to one or more vehicle settings, the worker had to press the retry button after each attempt. Now, Omnitracs Navigation will automatically try to re-calculate a path.
So the worker knows exactly which stop is being arrived, the address of the stop now displays in the Arrived area of the "You have arrived at your stop" screen.
Changes to the Region Filter
Larger organizations may have many regions to help organize and structure their data. However, because of the large amount of data involved, it can take a long time to load all the information. To help increase performance, some changes were made to how the list of regions is presented throughout Omnitracs Web, including the Shared By Regions page on Maintenance items and in FleetView.
- When you search for a region, regions that do not match the search criteria disappear from the list.
- If you are using hierarchy management, when you select a lower level region the box for the higher level region now turns green instead of black, indicating a sub-region is selected. Checking and unchecking the box for the higher level region will still select/deselect the sub-regions under that region.
New Black Box Events in the Performance Alert Report
The Performance Alert report helps you track potentially unsafe behaviors that a driver may engage in. Now, there are additional behaviors that the report can alert you to:
- Hard Brake
- ABS Brake
- Forward Collision Warning
- Forward Collision CMS Warning
- Forward Collision Haptic Warning
- Stability Control Warning
- Following Time Warning
- Lane Departure Active
- Lane Departure Imminent
- Lane Departure Disable
Vehicle Inspection Forms Include an Item for Spotted Lanternfly
The Spotted Lanternfly is an invasive insect that poses a threat to agriculture in some states (primarily in Pennsylvania at this time). In order to be in compliance with state regulations, drivers in affected states must be able to prove that they have checked their trailers or tractors for the presence of this insect. To meet this need, the following pre-, post-, and midday inspection forms now include a Spotted Lanternfly item:
- U.S. Tractor inspection forms
- U.S. Trailer inspection forms
- Canada Tractor inspection forms
- Canada Trailer inspection forms
This item appears on inspection forms in both the mobile and the host website.
Changes for Daylight Savings Time
To accommodate Daylight Saving Time changes, the graph in the Driver Log/UVA editor can now switch to a 25-hour day (end of DST) or 23-hour day (beginning of DST).
When Daylight Saving Time ends (when we “fall behind” in autumn), there are essentially two occurrences of 1:00 a.m., creating a 25-hour log day. If you insert an event in the log on this day, you will be asked to select either the first or second instance of the selected time.
When Daylight Saving Time begins (when we “spring ahead”), there is no 2:00 a.m.—we skip right over it, creating a 23-hour log day. If you insert an event in the log on that day with a time between 2:00 a.m. and 3:00 a.m., you will get a message saying “Invalid time” and you will need to select a new time.
The graphs in the Driver Log Report and the ELD Driver Log Report also accommodate a 25-hour or 23-hour day to reflect DST changes.
New Canadian Fertilizer Exemption Rule
A new Canadian Fertilizer Exemption rule (CAN 14/180 Fertilizer hrs) is now available for drivers who haul fertilizer in Canada. Under this rule, drivers who haul fertilizer are exempt from Canadian cycle reset requirements if they have the appropriate permit.
Drivers who are eligible for this rule can select it from the Change Rules screen.
Under the CAN 14/180 Fertilizer hrs. rule:
- Drivers must take at least 36 consecutive hours of off-duty time within any 14-day period. This means they cannot accumulate more than 12.5 consecutive on-duty days and the minimum 36 consecutive hours of off-duty time must be taken in any 14-day period.
- Drivers must take nine consecutive hours of daily off-duty time for the duration of the 14-day cycle until the 36-hour reset is taken.
- When drivers take nine consecutive hours off duty, they must still take one hour separately to make up the 10 hours for the day. The hour can be split into 30-minute segments. After this reset is taken, the driver may switch to a different rule set.
- Drivers do not need to take a 36-hour reset before using the exemption, but when this rule is selected, all hours accumulated since the last 36-hour consecutive off-duty period apply towards the 14-day period calculation.
- Drivers are exempt from parts 24-29 of the Canadian regulations and are therefore not required to take 24 hours off in the preceding 14 days.
- Drivers cannot use off-duty deferral while they are on this permit.
|Issue key||Release Notes||Component|
|RPE-940||There was an issue that was preventing some Telematics data from processing properly. This has been corrected.||Telematics|
|RPE-1743||There was an issue that was preventing the Telematics Diagnostics report from running as a scheduled report. This has been corrected and the report now runs when scheduled.||Telematics|
|RPE-1213||The RA Bridge Wizard successfully uploads Mobilecast Routes from the Roadnet Transportation Suite to Insight.||Data Transfer|
|RPE-1197||There was an issue causing the icons in FleetView to be displayed very faintly. This has been corrected.||Dispatch|
|RPE-1479||There was an issue that was causing an error to occur when the dispatcher tried to Cease Dispatch on some routes. This has been resolved.||Dispatch|
|RPE-1325||There was an issue preventing the links for signatures and route notes from appearing in Order Status. This has been corrected.||Order Status|
|RPE-963||There was an issue where changes to stops could prevent the route from unloading on the device. This has been corrected.||Roadnet Mobile|
|RPE-1050||There was an issue causing the incorrect options to appear when the driver added a delay to a route. This has been corrected.||Roadet Mobile|
|RPE-1215||There was an issue where some options were not appears in the Quick Task menu in Roadnet Mobile. This has been corrected.||Roadnet Mobile|
|RPE-1326||There was an issue where the route could not be unloaded from the device if the driver added a delay after the last stop. This has been corrected.||Roadnet Mobile|
|RPE-1482||An Unload error message and a reset note from the dispatcher no longer display when a Tracking route day is ended.||Roadnet Mobile|
|RPE-1490||There was an issue causing the incorrect options to appear when the driver added a delay to a route. This has been corrected.||Roadnet Mobile|
|RPE-1488||There was an issue preventing routes from being unloaded on the mobile device if stops on the route had active alerts. This has been corrected.||Roadnet Mobile|
|RPE-1596||The Roadnet Mobile app now successfully saves pictures.||Roadnet Mobile|
|RA-44384||In previous versions, the Uncancel Order option on a canceled stop was inadvertently left enabled when the entire stop was canceled. This has been corrected. The option is not disabled in this scenario.||Roadnet Mobile|
|RACS-3682||An issue causing Roadnet Mobile to stop sending GPS has been resolved.||Roadnet Mobile|
|RA-44163||Previously, some reports continued to display the priority assigned to the service location even though there was a priority override on the order. This has been corrected.||Reporting|
|RA-44374||During the Save Session As operation there is an option to change the session date for the newly created copy. If the date is changed the route start dates are also automatically adjusted. However, this causes some calculated values to be stale, like stop arrival dates. To update these values the routes had to be manually recalculated after the copy operation is finished. This change does the calculation automatically after the Save Session As operation so all calculated values are up to date right after the new copy is created.||Routing|
|RA-44304||An issue existed that resulted in imported orders having blank values for urgency increases. This issue has been resolved.||Routing|
|RA-44414||The ignore constraint parameter on the routing rules dialog has been changed to "Priority" (previously "Service Location Priority").||Routing|
|RPE-1512||There was an issue preventing admin users from moving equipment from one region to another. This has been resolved.||Maintenance|
|RPE-1327||There was an issue where the depots list on the Workers window would be empty. This has been resolved.||Maintenance|
|RPE-1511||A problem was identified and fixed that ignored the weekly stop assignment when dragging orders to a new territory and the option, 'Maintain Current Assignment', is enabled.||Strategic Planner|
|RPE-1517||There was an issue where users were able to uncheck a map region on the Map Dataset Regions page, but the device would not allow the deselected region to be removed from the device. Users can no longer deselect regions on the Map Dataset Regions page.||Admin|
|RPE-1214||There was an issue that was causing Mobile Device Diagnostics to time out if there was a large number of devices to be retrieved. This has been corrected.||Miscellaneous|
|RA-44670||There was an issue preventing users from being able to scroll to the bottom of the Region - Map Dataset Region page. This has been corrected.||Navigation|
|RA-44151||There was an issue that was preventing Wisconsin and District of Columbia map datasets from being sent to the device. This has been corrected.||Navigation|
|OTNAV-11605||The driver will now see a confirmation dialog when a trip is cancelled.||Navigation|
|OTNAV-11603||The destination address will now appear in a confirmation dialog when the driver arrives at a stop.||Navigation|
|OTNAV-11597||The driver will no longer be required to enter an activation code when activating Omnitracs Navigation. Activation will be based on the device ID.||Navigation|
|OTNAV-11542||The driver will only hear the GPS Signal Lost message when in a route or the route is recalculating, not when opening the application.||Navigation|
|OTNAV-11539||When Omnitracs Navigation is installed, the permission message was not asking for permission to access the device's phone number. The message has been updated and now asks for permissions for storage, location, and phone number.||Navigation|
|OTNAV-11509||There were instances where the Location Preview dialog did not properly display all the options. This has been corrected.||Navigation|
|OTNAV-11481||There was an issue that was causing the Navigation application to improperly arrive at a destination. This has been corrected.||Navigation|
|OTNAV-11480||There was an issue that was causing the location name to partially cover the mileage in when searching for POIs. This has been corrected.||Navigation|
|OTNAV-11475||The user now has the option to choose whether to use the system's volume setting or a max volume setting for spoken messages.||Navigation|
|OTNAV-11471||When a route was started to a POI, the destination was not always providing the same level of detail. This has been corrected, and the POI only displays the store name and street.||Navigation|
|OTNAV-11470||The turn by turn list did not always display the destination name and address properly. This has been resolved.||Navigation|
|OTNAV-11386||There was an issue where portions of an address were cleared when changing a search on the Search screen. This has been corrected.||Navigation|
|OTNAV-11349||There was an issue where portions of the address were being deleted when changing a search on the Search screen. This has been corrected.||Navigation|
|OTNAV-11319||There was an issue where if music was playing when an audible alert was announced, the music did not stop. This has been corrected, and the music is stopped when the message is read.||Navigation|
|XRS-10461||When a pre-trip inspection and drive event occurred within the same minute, the Driver Log Report showed the events out of order, with the drive event displayed before the inspection. This issue has been resolved.||Compliance|
|XRS-12415||This release resolves an issue that sometimes caused erroneous edits to be made on the Driver Log when drive time was reassigned.||Compliance|
|XRS-14203||Some UVA events were not appearing on the Driver Log when users selected the vehicle ID in the UVA window, but they were appearing when users selected the Reclassify button. This issue has been resolved.||Compliance|
|XRS-15565||An issue that caused the wrong vehicle ID to be assigned to manually entered fuel receipts has been resolved.||Compliance|
|XRS-15752||The numbers indicating hours on the Driver Log Editor graph are now correctly aligned over the vertical lines they correspond to.||Compliance|
|XRS-16173||A missing driver attribute was resulting in some inaccurate data in the ELD Log Report. This issue has been resolved.||Compliance|
|XRS-16282||When users searched for UVA for a specific date range, they sometimes received UVA outside of that date range. This issue has been resolved||Compliance|
|XRS-16511||In the Canadian Vehicle Inspection Form, the Windshield Wiper/Washer item is no longer duplicated.||Compliance|
|XRS-2135||The Driver Log graph was showing incorrect hours for some drivers. This issue has been resolved.||Compliance|
|XRS-12902||In the Driver Log Editor, some driver comments were being displayed as pre-defined messages when they were supposed to be free-form text. This issue has been resolved.||Compliance|
|XRS-15579||When segments of a UVA event were reclassified as a group, some short segments did not get reclassified, causing them to appear in the driver’s log as “orphan” segments. This issue has been resolved.||Compliance|
|XRS-16903||On rare occasions, a UVA event consisted of only a single segment and could not be reclassified. This issue has been resolved.||Compliance|
|XRS-17136||When the UVA list was exported as a .CSV file, the Site ID column was missing from the export file. This issue has been resolved.||Compliance|
|XRS-10291||Drivers were able to return to the dashboard during the certification of logs at logout. This issue has been resolved.||HOS Mobile|
|XRS-10413||Drivers who logged in to ELD vehicles were prompted to login twice—during the initial login and again during the pre-trip inspection. This issue has been resolved.||HOS Mobile|
|XRS-10418||If a driver declares a 16-hour Big Day again before the daily reset, the warning message now correctly reads “Big Day is already on.”||HOS Mobile|
|XRS-10813||On the Schedule screen > Future tab, the French label now correctly says “Avenir.”||HOS Mobile|
|XRS-11301||Spanish translations of text on several screens have been corrected.||HOS Mobile|
|XRS-12140||Drivers using the French language setting received a non-translated message when they logged out of the app while they were still associated with a vehicle. This issue has been resolved.||HOS Mobile|
|XRS-12736||In the menu, the Change Drivers option has been corrected to Switch Drivers.||HOS Mobile|
|XRS-12903||When the latest version of HOS Mobile was downloaded on the mobile, drivers did not receive a version update message when they first logged out. This issue has been resolved.||HOS Mobile|
|XRS-12916||Previously untranslated labels have been translated into Spanish.||HOS Mobile|
|XRS-13367||When drivers were prompted to confirm carrier edits, pending vehicle associations were being presented as unknown group edits. This issue has been resolved.||HOS Mobile|
|XRS-13846||Several French translations of text have been corrected||HOS Mobile|
|XRS-13952||When users register a new mobile device using HOS Mobile, the list of device types is now displayed in alphabetical order to make it easier for users to find the correct device type.||HOS Mobile|
|XRS-14644||When drivers replied to a form, the violation date showed the current date rather than the date of the violation. This issue has been resolved.||HOS Mobile|
|XRS-14869||If there were no pending entries to send to the host, the mobile erroneously logged this as an error, which then showed up as such in customers’ logs. This issue has been resolved.||HOS Mobile|
|XRS-14917||The blue dashboard indicating Paper Log Mode remained blue after Bluetooth was reconnected. This issue has been resolved.||HOS Mobile|
|XRS-14958||Pressing and holding the HOS option from the main menu allowed users to select the eRODS File Transfer option when it was not available from the Options menu on the HOS Log screen. This issue has been resolved.||HOS Mobile|
|XRS-15346||If driving occurred between the time the app was forcibly closed or crashed and then resumed, the app now correctly assigns that driving time to the driver instead of treating it as UVA.||HOS Mobile|
|XRS-15923||When a rule change occurred 24 days earlier and the driver remained logged in over midnight, the rule change was trimmed, resulting in the mobile calculating the HOS based on the default rule. This issue has been resolved.||HOS Mobile|
|XRS-16247||Selecting Clear Device Registration (Settings > Setup) after a first login now correctly returns the user to the Privacy screen instead of the login screen.||HOS Mobile|
|XRS-16292||Driver sometimes had a pre-trip inspection on their log but no Drive time following it. When the driver performed a post-trip inspection and then performed a pre-trip inspection again, the Drive time appeared on the log. This issue has been resolved.||HOS Mobile|
|XRS-16463||An issue that caused the mobile to sometimes use the incorrect state code when it was geo-tagging has been resolved.||HOS Mobile|
|XRS-16478||Some users experienced problems when they tried to make calls from the Scheduled Stop screen using the phone icon. This issue has been resolved.||HOS Mobile|
|XRS-16684||When a driver made a duty status change but had not yet associated to a Relay, the mobile prompted the driver to enter a location if one was not available from the mobile device GPS. The driver, however, was able to select OK without entering a location. The OK button is now unavailable until a location value of at least five characters is entered.||HOS Mobile|
|XRS-17052||After a driver departs from a site, the departure notification message now appears as expected.||HOS Mobile|
|XRS-17055||If drivers had to certify their logs within the first few hours of their day, they received prompts to certify the logs for the wrong days. This issue has been resolved; now drivers are prompted to certify their logs on the correct days regardless of when they certify them.||HOS Mobile|
|XRS-4124||Previous inspections are now processed based on the vehicle, not the current driver. This is the expected behavior.||HOS Mobile|
|XRS-5104||The driver ID and vehicle ID are now appearing as expected on the Stop Detail screen.||HOS Mobile|
|XRS-5248||If HOS Mobile crashed or was forced to close after the driver entered the manifest number during the pre-trip inspection, the driver was prompted to enter the manifest number again after the first drive segment was completed. This issue has been resolved.||HOS Mobile|
|XRS-7147||Drivers using mobiles devices with Fixed Display were being prompted twice to select the Short Haul exemption. This issue has been resolved.||HOS Mobile|
|XRS-15884||Engine Power On events that occurred outside of an ELD driver’s login period were not being listed in the driver’s HOS log. This issue has been resolved.||HOS Mobile|
|XRS-16999||An issue that caused mobile eRODS file transfers to fail if they were missing a value for CMV Order Number has been resolved.||HOS Mobile|