Roadnet Anywhere 5.6 - New Features and Enhancements

 

Note: Some of the options described are purchasable and may not appear. Contact your Omnitracs sales representative for more information about acquiring additional features.

Roadnet Anywhere version 5.6 contains several new features that make it easier for you to plan and monitor your routes throughout the day, as well as analyze your overall transportation operation.

Maintenance

Dispatching

Active Alert

Routing

Strategic Planner

  • Omnitracs introduces Strategic Planner, a cloud-based tool that will analyze and optimize your distribution network.

Roadnet Mobile

Roadnet Mobile Manager

Centralized Messaging

Telematics

Insight

Navigation

  • Drivers can now limit the list of possible points of interest (POIs) instead of seeing all POIs.
  • There were several updates to the user interface, making it easier for drivers to use the application.
  • To provide more accurate vehicle information, the default vehicle is now determined in the following order:
    • - If Roadnet Mobile or another application with a vehicle is used, that vehicle will be default vehicle
    • - If there is not another application to get a vehicle from, the default equipment type from Roadnet Anywhere will be used.
  • User can now configure when trips are purged, previously they were purged after one day

Compliance Mobile

  • There are changes to how drive time reassignment is handled in the Compliance mobile application.
  • There are changes to how drivers handle drive time reassignments that are made in the Driver Log Editor.
  • Canadian drivers can now email their logs.
  • The Compliance app now alerts drivers of the amount of break time remaining.
  • There are changes to how drivers can make comments in the log editor.
  • There are new screens when drivers change their rule set.
  • You can now clear a mobile device's registration so that it can be used for another company.
  • The Hours of Service mobile application will now require users to install upgrades when they are made available.
  • There is a new data privacy agreement for drivers.
  • The trailer's license plate number, state or province, and license issuing jurisdiction will now be included in the trailer inspection form.
  • If the Drive License Number or Driver License Issuing State are left blank in a driver's log, the eRODS file will fill those fields with default values to prevent the eRODS file transfer from failing.
    • If the Driver License Number field is blank, the corresponding field in the eRODS file will display as "NA".
    • If the Driver License Issuing State is blank, the eRODS field will display "OT" (for "Other").
  • Drivers are no longer required to be associated to a vehicle in order to edit their logs, depending on the company’s default host mode and whether or not the company settings allow AOBRD log edits:
    • In AOBRD Mode companies, if AOBRD edits are allowed in the host (that is, if Allow AOBRD Log Editing is selected in the General Information tab of the Edit Company Settings window), drivers can edit their logs at any time without being associated to a vehicle.
    • n Mixed Mode companies, if AOBRD edits are allowed in the host, drivers can edit their logs at any time without being associated to a vehicle. If AOBRD edits are not allowed, drivers can only edit their logs when they are associated to an ELD vehicle.
    • Drivers in ELD Mode companies can edit their logs at any time without being associated to a vehicle.
  • Drivers in ELD Mode companies can edit their logs at any time without being associated to a vehicle.
    • In Mixed Mode companies, if the driver is not associated to a vehicle, carrier edits will be presented as they are in AOBRD Mode companies—when drivers go on duty after logging in they will be alerted to any edits that were made, but the changes will be automatically added to the log. Drivers who are associated to an ELD vehicle will be able to accept or reject the edits. 
    •  In ELD Mode companies, drivers will be presented with carrier edits and will be able to accept or reject them whether or not they are associated to a vehicle.
  • The Stop Detail screen now includes a Cancel button, which allows drivers to cancel a scheduled stop after they have arrived the stop either by entering the geofence or manually. When drivers can cancel stops themselves they can more efficiently manage unpredictable situations that prevent them from executing the stop. When a driver cancels a stop this way, the stop is sent back to the driver’s schedule as not having been started. In addition, an inbound form message can be sent to the host if that form is triggered by a cancelation.
  • Previously, when users performed a Relay swap (moving a Relay from one vehicle to another), they received a message saying, “Relay data cleared. You can now unplug the relay.” This message could be misleading, however; the data is not actually cleared until the green LED light blinks every three seconds, and the previous message sometimes led drivers to unplug the Relay prematurely. To ensure that the Relay is not unplugged before the data-clearing process is complete, the message now says, “Do not unplug the Relay until the Relay reboot has completed! When the green LED blinks once every 3 seconds, you may unplug the Relay.”
  • When a driver performs a Relay swap—that is, moves a Relay from one vehicle to another—an alert is now sent to the Omnitracs XRS host. The alert message includes the name of the driver, the vehicle ID, and the date and time of the swap.
  • When drivers send eRODS file transfers from the mobile, they now receive more detailed information about the status of the file transfer:
    • The eRODS File Transfer screen now includes a View History button that drivers can select to view their historical eRODS transfers. When they send the transfer, th confirmation message also reminds them that they can view their history by selecting this button.
    • After drivers send a file transfer, they receive a brief message telling them the date and time of the transfer, the driver's name, the method of the transfer (email or web service) and whether the transfer has succeeded or failed.
    • After the eRODS transfer process is complete (whether the transfer succeeded or failed), an HOS remark will be added to the driver's log. This remark will not be editable.
  • The pre-trip and post-trip Inspection Summary screens now include the carrier name and statements of compliance specific to where the carrier is based (Canada or the U.S.).

Maintenance

Managing Maintenance Items Across Multiple Regions

Found in Roadnet Anywhere Web

Working across multiple regions can make if difficult to manage maintenance items like equipment and workers; especially if you are only able to edit, add, and view items from the region you are currently working in. To save you the time and effort of clicking back and forth between regions, Roadnet Anywhere has made it much simpler to manage items if you are responsible for more than one region. For example, If you are working in one region adding new pieces of equipment, and you come across a trailer that doesn’t belong in the region that you are currently working in, you can add that trailer to the other region without having to change your current one.

Once that trailer is added, you can use Filter Regions to view it and equipment from other regions on the grid, where there is a new column that will indicate which regions the equipment is shared to. You can also search for that trailer and other pieces of equipment across multiple regions.

You can now view and manage the following maintenance items across multiple regions:

  • Compliance Alerts
  • Depots
  • Equipment
  • Equipment types
  • Equipment profiles
  • Fuel locations
  • Mobile devices
  • Restricted locations
  • Service locations
  • Service location categories
  • Telematics devices
  • Workers
  • Worker types

Adding, Editing and Viewing Maintenance Items for other Regions

In the Edit or Add item window, click the Shared by Regions tab.

Check Assigned Regions. A list will open with all Regions that you have been assigned, even regions that you are not currently working in.

If necessary, deselect the current region and select another from the list

OR

select any additional regions that you want to share the item to.

Viewing Maintenance Items that Have Been Shared Across Multiple Regions

Each grid will have a new Shared by Regions Column that will display the regions that the entity is shared to

If the item is shared to more than one region, you can hover over the listed number and a tool tip will list the specific regions that the item is shared to.

To filter the list, click on the [Filter Regions] button. Select the regions that you want to view. You will be able to select every region that you have been assigned to.

To search for an item across multiple regions, type the item's ID or Description into the Search box. Roadnet Anywhere will search for that item across all visible regions.

 

Dispatching

Managing Exception Rules Across Multiple Regions

Found in Roadnet Anywhere Web and Roadnet Anywhere Client

Exception rules allow you monitor issues that may occur on your routes. When a rule is broken, Omnitracs Roadnet Anywhere can alert you to the problem so that it can be solved quickly and efficiently. Exception rules are intended to simplify fleet management, but when your business is spread out over many regions, creating and managing exception rules can be difficult. For instance, you may have a manager that is responsible for monitoring exceptions in three regions. One region may be an urban area, with specific rules for idling time and posted road speed violations. The other two may be rural areas made up of highways that would require very different rules for idling and speeding. The best way for that manager to really utilize exception rules is to have the ability to quickly share rules to multiple regions when applicable. Instead of creating the same rule in both of the rural regions, they will simply need to create it once and then share it. When assigning a recipient to an exception rule, you can even chose which regions that recipient will receive alerts for. This will ensure that employees only receive alerts that are relevant to their jobs.

Previously, you were able to create exception rules that were customized as well as use system defined exception rules. Now each rule that is created will be considered customized. System defined exception rules have become exception rule types. Every time you add a rule you will be able select a system defined exception rule type like Device Low Battery or Idling. These exception rule types will include specific parameters based on their type. If none of the system defined exception rule types are applicable, you have the ability to select a user defined exception rule type and create your own parameters.

Note: You will need to add all new exception rules, no rules will created by default. However; all of your existing exception rules will be migrated to the new format.

Exception rules management has now been enhanced to ensure that exception rules can be utilized efficiently by every user, no matter how many regions they work with. You now have the ability to:

  • Assign a Rule Type to an exception rule or create a user defined rule type.
  • Select particular regions recipients will receive alerts from.
  • Share exception rules over multiple regions.
  • View all exceptions or filter exceptions by rule
  • Identify an exception rule's rule type and region with two new columns in the exception rules grid.

Creating an Exception Rule

In Roadnet Anywhere Web

Go to Maintenance and select Exception Rules

To add an exception rule, click the [Add] button. The Add Exception Rule window will open.

To edit an existing rule, click the edit icon. The Edit Exception Rule window will open.

On the General tab, enter an ID for the exception rule.

Use the arrow to select the Rule Type. You can chose from a list of existing exception rule types or create a user defined rule type. There are no limitations to the number of rules you can create of a certain rule type.

Depending on the rule type you select, you may be prompted to enter additional information, for instance a Device Low Battery rule will require you to enter a Low Battery Threshold percentage. Other fields, like the display color and description, may also be pre-populated depending on the rule type you select. If you select a User defined rule type, a wizard will prompt you to define the rule.

Notes: You will only be able to change a rule type when adding an exception rule. Once an exception rule has been created, you will not be able to change the rule type.

If you have not purchased Custom Route Exception Rules, you will not be able to add or edit a user defined rule.

Assigning Regions to Recipients

If you have a manager that is only responsible for two regions, it is probably difficult for that manager to work efficiently if his or her inbox is flooded with notifications from every region in your organization that the company has created. To ensure that each employee is seeing only what they need to see to perform their job, you now have the ability to define which regions each employee receives alerts for.

To assign a region to a recipient:

Click the Recipient tab.

To add a new recipient, enter their information in the Enter a new item field.

To edit an existing recipient, click the edit icon.

Use the arrows to select whether the recipient will receive notifications for all regions or specific regions.

Select which depots the recipient will receive notifications for.

To Share an Exception Rule to other Regions

Previously, rules could only apply to one region. Now, you can create a single rule that can be easily shared to multiple regions, saving you the time and effort of having to create the same rule one by one for each region.

To share an exception rule to other regions:

Click the Shared By Regions tab.

If you want the rule to apply to all regions, check Share To All Regions.

If you want to specify the regions that the rules will apply to, select which region you wish to apply it to from the list.

Click the [Save] button.

After you have created exception rules, you will be able to view and manage exception rules for all regions in Maintenance. Each exception rule will display the Rule Type and Shared by Regions in the grid.

Creating an Exception Rule

In Roadnet Anywhere Client

Go to Dispatching and select Resource Exception Rules.

To add an exception rule, click the add icon. The Add Exception Rule window will open.

To edit an existing rule, click the edit icon. The Edit Exception Rule window will open.

On the Standard Properties tab, enter an ID and Description for the exception rule.

Use the arrow to select the Rule Type. You can chose from a list of existing exception rules or create a user defined rule. There are no limitations to the number of rules you can create of a certain rule type.

Depending on the rule type you select, you may be prompted to enter additional information, for instance a Device Low Battery rule will require you to enter a Low Battery Threshold percentage. Other fields, like the display color and description may also be pre-populated depending on the rule type you select. If you select a user defined rule type, a wizard will prompt you to enter resource exceptions for the rule.

Notes: You will only be able to change a rule type when adding an exception rule. Once an exception rule has been created, you will not be able to change a rule type.

If you have not purchased Custom Route Exception Rules, you will not be able to add or edit a user defined rule.

To Share an Exception Rule to other Regions

Previously, rules could only apply to one region. Now, you can create a single rule that can be easily shared to multiple regions, saving you the time an effort of having to create the same rule one by one for each region.

To share an exception rule to other regions:

Click the Shared By Regions tab.

If you want the rule to apply to all regions, check Share To All Regions.

If you want to specify the regions that the rules will apply to, select which region you wish to apply it to from the list.

Click the [Save] button.

You will be able to view and manage exception rules for all regions in Maintenance. Each exception rule will display the Rule Type and Shared by Regions in the grid.

 

Changing The Way Depots Filter Information

Found in Roadnet Anywhere Web

Currently, when you filter your routes by a specific depot, Roadnet Anywhere shows the routes associated with the depot that is assigned to the routing session. But, many users prefer to see the routes that originate from the selected depot. Now, when you filter on depots in FleetView, you are choosing to see information about routes that started at that depot.

In addition, the depot field on the Change Region Context window is no longer available.

Note: If you want to continue seeing information for routes where the depots are connected to routing sessions, contact Customer Service and ask to turn on the Enable Depot in Region Context setting.

Sending Exception Notifications Based on A Depot

Found in Roadnet Anywhere Web

When an exception rule is triggered, you can send a notification to a specific recipient to alert them of the event. Previously, if you assigned a depot to the recipient, notifications were sent if the recipient's selected depot matched the depot for the route's routing session. Now, if you prefer, you can have a notification sent to the recipient if the assigned depot matches the route's depot of origin.

If you want your depots to be independent of your routing sessions, so that you can send exception notifications based on the depot where the route originated, contact Customer Service and ask to turn off the Enable Depot in Region Context setting.

Note: When you make this change, you will also change the routes that display in Fleetview when you select a depot on the region filter.

 

Roadnet Active Alert

Configuring Roadnet Active Alert in Roadnet Anywhere Web

Found in Roadnet Anywhere Web

Roadnet Active Alert allows your customers to easily view order information stored in Roadnet Anywhere so they know when to expect their service to occur. Previously you could only setup and update Active Alert in Roadnet Anywhere Client. It has been added to Roadnet Anywhere Web, so that those users can also take advantage of the features of Active Alert.

Once Active Alert is enabled, you will need to define the necessary settings for the Business Unit, as well as add email senders, recipient types, and recipient type templates. You will also need to assign recipient and event types and a recipient email or mobile number to each service location that will receive an alert.

Creating an Email Sender

First you will want to enter the email address that will be used as the From or Reply to address when an email alert is sent to your customer. To enter your Email Sender, click Administration and then click the green button and scroll to Email Senders. Add a new email sender and then enter an email address and a description for your email sender.

When you save your email sender, a verification message from Amazon Web Services is sent to the email address. The person receiving the verification message must click on the link included in the message to verify the email address. You will assign this email sender when you set up Active Alert settings for the business unit.

Entering Active Alert Business Unit Settings

Next, you need to define the Active Alert settings for the business unit. Click Administration and if necessary, click the green button and scroll to Business Unit. Add a new business unit or edit an existing one. Click the Active Alert tab.

On the Active Alert - General Settings page, the Display Settings define how the quantity and date/time information is displayed to your customer in Active Alert. The ETA Window Buffer determines how wide the ETA window is that is given to the customer and Missed Service Window Settings determine at what point a customer will be alerted if the driver is projected to miss a service window.

On the Active Alert - Email Settings page, select the email sender address that will be used for sending alerts. You can also upload up to two images to display in the alert, such as a company logo.

Creating Recipient Types

After defining settings for the business unit, you will need to create recipient types. Active Alert recipient types are a way to create and manage alerts that inform customers about their service. For instance, you may have one recipient type for customers that receive deliveries and want to know the expected arrival of their package or when a package has been delivered, while another recipient type may be for vendors from who you will pick items up and want to only know if an order has been canceled.

To add a recipient type, click on Maintenance and then click the green button and scroll to Active Alert Recipient Types. Add a new Recipient Type and enter an ID and description for the recipient type.

On the General tab, you will define the number of days that orders should be displayed for the customer, if worker information will show, and the amount of time prior to the worker’s projected arrival that alerts can be sent. You can choose to display up to three pieces of additional stop information.

On the Template tab, you will define how you want to contact your customer, text or email, and what to include in the message. Add a new template and then choose the Event Type. Event types tell what type of alert is being sent, ETA, time until service, if the service is completed, canceled, or marked unserviceable, or if a service window is going to be missed and how early or late it will be. You can then choose the Notification Method and enter the Subject and Body of the message.

Notes: The online help provides information on customizing a message so that your customer's specific information is included in the Subject and Body of the message.

If you select SMS as the Notification Method, any text you enter in the Subject field is ignored.

Only one message template can be created for each notification method and alert type pair. For example, you can create only one message template for initial ETA alerts sent by email.

You can create as many recipient types as necessary. When you have completed these set ups, you must then add recipient and event types and a recipient email or mobile number to the service location.

Setting Up Active Alert for Service Locations

When setting up a Service Location, the Active Alert page lets you define who will receive service alerts and what type of alerts they will receive.

Note: Active Alert users can also add recipients using the Active Alert web application.

On the Active Alert page of the Service Location, add a new subscription. You will select a Recipient Type that you previously created and the notification method that will be used. After you choose the Event Type, you will enter any email addresses or mobile numbers to which you want notifications sent. You can add as many subscriptions to the service location as necessary.

Notes: If the selected recipient type doesn't contain a template for an event type, then you will not be able to choose that event type.

When you have completed all the steps, your users can begin getting notifications about their deliveries and pickups.

Importing Active Alert Service Location Information

If you prefer, you can import your active alert information for service locations into Roadnet Anywhere Web. The Service Location import template has been updated to reflect the active alert fields that have been added. From the Service Locations list, simply press Import and then Download Import Template File to save the updated import template. The following fields have been added.

Field Name Required Max Length Description
Active Alert - Method No N/A The method of communication for the recipient. The choices are Email (0) or SMS (1) (text message to mobile phone).
Active Alert - Recipient Address No N/A The e-mail addresses or phone numbers (depending on Active Alert -Method) where service alerts should be sent. When entering phone numbers, you must enter the 10 digit phone number without dashes or other punctuation. Recipients should be separated by semicolon.
Active Alert - Recipient Type No 32 The recipient type (Active Alert Recipient Type Identifier) for the subscription. The recipient type determines the types of notifications available to send to the recipient as well as the information that will be contained in the messages that are sent.
Active Alert - Send Initial ETA Message No N/A When the flag is set to T, True, Y, Yes, or 1 the recipient(s) will receive an alert when the estimated time of arrival is calculated based on when the driver leaves the depot. Otherwise set the flag to F, False, N, No, 0, or leave the field blank or leave it blank.
Active Alert - Send Missed Service Window Message No N/A When the flag is set to T, True, Y, Yes, or 1 the recipient(s) will receive an alert if the driver's arrival time is projected to miss a service window, such as when a route is running early or late. When setting the active alert options for the business unit, you can specify the number of minutes a driver must be projected to miss the service window by for this the alert to be sent. Otherwise set the flag to F, False, N, No, 0, or leave the field blank or leave it blank.
Active Alert - Send Serviced Message No N/A When the flag is set to T, True, Y, Yes, or 1 the recipient(s) will receive an alert once service is completed. Otherwise set the flag to F, False, N, No, 0, OR don't include it for the import.
Active Alert - Send Updated ETA Message No N/A When the flag is set to T, True, Y, Yes, or 1 the recipient(s) will receive an alert when the estimated time of arrival changes. Otherwise set the flag to F, False, N, No, 0, OR don't include it for the import.
Active Alert - Send X Minutes Before Arrival No N/A Format: hh:mm. If the value is provided the recipient(s) receive an alert a specified number of minutes before receiving service. Enter the number of minutes before service that you would like the recipient to receive a notification. Minimum is 00:01, Max - 01:00. If the field is not specified, the corresponding alert would not be sent.

Routing

Using Order Urgency

On any given day, you are going to have some orders that it is more important to deliver than others. For instance, if a customer calls because they have run out of your product, you probably want to make sure that order is delivered as soon as possible. Now, you can indicate the urgency for an order, and Roadnet Anywhere will place orders with a higher urgency on routes before the orders with a lower urgency.

Some features of order urgency are:

  • You can specify an urgency between 0 and 100 on an order, with 100 being the most urgent.
  • You can specify that orders can only be combined if the urgency is the same.
  • You can choose to have the order urgency ignored when routes are created.
  • You can have the stop markers on the map colored by urgency.
  • When you run Create Routes, Roadnet Anywhere will route orders with a higher urgency first.

Adding Urgency to Orders

In order to use urgency when creating routes, you need to indicate how urgent the orders are. You can manually add the urgency information to your orders, or import it.

In Roadnet Anywhere Client

On the Unassigned list in the Route Planning workspace, click the Add icon to add an unassigned order. The Unassigned Order window opens.

Note: You can add or edit the urgency on unassigneds or orders opened from other places.

On the General page, enter use the arrows to enter the urgency for the unassigned. You can enter an urgency between 0 and 100; an order with an urgency of 100 should be delivered in the current session. Click the Save button.

You can also import the order urgency when importing orders or a routed solution.

Field Required Range Description
Urgency No 0-100 A number between 0 and 100 indicating how important it is that the order is routed in the current routing session.

Note: If you are importing a routed solution, the field name is Order - Urgency.

 

In Roadnet Anywhere Web

Click on the FleetView icon to open FleetView.

On any of the routes screens, click the Add icon on the Unassigned Orders tab. The Unassigned Orders window opens.

Click the Advanced tab to open the Advanced page. Enter an urgency between 0 and 100; an order with an urgency of 100 should be delivered in the current session. Click the Save button.

 

Ignoring Urgency when Combining Orders

In Roadnet Anywhere Client

Combine orders is an option that lets you indicate that orders going to the same location are considered together when creating routes. You can specify other parameters that must match for the orders to be combined, including the urgency. If you say that the order urgency must match, and there are two orders for a location, one with an urgency of 100 and one with an urgency of 30, these orders will not be combined and may not be routed together.

Click on the Administration menu and scroll to Regions; the Regions list opens. To add a new region, click the Add icon. To change an existing region, click the Edit icon. The Region window opens. Click on the Routing Options tab. In the Combine Orders box, check Urgency. Now, orders for the same service location will only be combined if they have the same order urgency.

Ignoring Urgency when Creating Routes

In Roadnet Anywhere Client

Normally, when you run the Create Routes process, orders with a higher urgency are more likely to be routed than orders with a lower urgency. However, there may be times when you don't want the urgency considered when you are creating routes. In those cases, you can tell Create Routes to ignore the urgency set on the orders - they will be all be treated as if urgency did not exist.

Click on the Routing menu and scroll to Create Routes. The Create Routes tab opens. In the Ignore box, check Order Urgency.

Seeing Urgency on the Map

In Roadnet Anywhere Client

There may be times when you want to be able to easily identify the most urgent orders when you are looking at a map. For instance, you may want to see that all no urgent orders are unassigned, or even use the order urgency when evaluating or editing your routes. Now, you can have the stop markers colored by urgency. The color code is:

Low urgency orders - green

Medium urgency orders - yellow

High urgency orders - red

Note: If a stop has more than one order, the color indicates the order with the highest urgency.

Click on the Tools menu and scroll to Options. The Options notebook opens. Click on the Map to open the Map page. In the Route Markers area, click the Marker Color By arrow and choose Order Urgency. Click the [Save] button.

Running Create Routes with Order Urgency

You do not need to enable order urgency for Roadnet Anywhere to consider it when creating routes; if there is an urgency value entered for an order Roadnet Anywhere will automatically consider it when creating the routes. There are some important things to remember about using urgency when running create routes: 

  • If the routing session is for more than one day, the order urgency is ignored.
  • If you are creating multi-day routes and select to Maximize Early Days, orders with a higher urgency will be routed on the earlier days.
  • If an order has an end date that is the same as the route date, that order takes precedence over an order with a high urgency.
  • Order urgency is only used when routes are created; it is not used for Suggest Route.
  • If putting an order on a route breaks a route constraint, the order will not be routed, even if it has a high urgency. For instance, if adding the order to the route would cause the route to exceed the allowed Max Time, the order will not be placed on the route.
  • If you are using Combine Orders, Roadnet Anywhere will use the highest urgency value when routing those orders.

 

Starting a Route on the Previous Day

Found in Roadnet Anywhere Client

You may have routes where the driver needs to leave the day before the first stop is delivered. For instance, the first stop's planned arrival time might be 1:30 AM, but in order to meet that arrival time the driver needs to leave at 11:50 PM the prior day. Now, when you set up the route template, you can indicate that the driver will need to start the route on the previous day.

Click the Routing menu and scroll to Route Templates. The Route Templates screen opens. To add a template route, click the Add icon in the Route Template list; the Add Route Template window opens. Check Starts on Previous Day.

 

Viewing the Priority for Unassigned Orders

Found in Roadnet Anywhere Client

Priority indicates the importance of servicing a service location early in the day - a service location with a priority of 9 should be serviced before a service location with a priority of 2. This information can be important, particularly if you are dragging and dropping orders onto routes, so you can meet customer expectations. Now, you can see the service location's priority in the Unassigned Orders list.

Note: If the order is a transfer order, only the pickup is shown in the Unassigned list.

 

Updating the Service Locations' Preferred Route IDs

Found in Roadnet Anywhere Client

If you use preferred route IDs to ensure that service locations are placed on specific routes, it is important that the proper preferred route ID is specified on the service location. As you create your routes, you may find that you want a service location to be part of a specific route, or you may have created a route where you want all the stops to always be placed on that route. Now, you can right click on a route, or a stop, and update the service location(s) preferred route ID with the ID of the route.

In a routes or stops list, select the routes/stops whose service locations you want to update. Right-click on a selected route or stop and choose Update Preferred Route IDs from the menu that pops up. The Updated Preferred Route IDs window opens, listing the service locations that will be updated, their current preferred route ID and the updated preferred route ID. If a service location already has a preferred route ID, it will not be updated unless you check Overwrite Preferred Route IDs. Click [Update]. The service locations' preferred route ID is updated with the route's current ID.

 

Strategic Planner

Introducing Strategic Planner

Omnitracs Strategic Planner is a new cloud-based tool that enables you to analyze, modify, and optimize your service and distribution network. After you import your historical data and business requirements, Strategic Planner quickly analyzes that data to generate geographic territories and optimal route weeks and days in the business cycle. You can customize the rules and goals used during route creation to meet your business goals and constraints.

With Strategic Planner, you can explore strategic options that lead to enhanced customer service and greater cost efficiencies across the board. By creating ‘what-if’ projections, Strategic Planner lets you take immediate control of every aspect of your operation, to assess the best use of resources in meeting operational goals.

To analyze optimized routes immediately, Strategic Planner creates a territory scorecard to display important ‘before’ and ‘after’ statistics to show potential savings of the strategy you are analyzing. You can also quickly drill down with a territory to modify each route and stop sequence to adhere to specific customer needs.

 

Contact your Omnitracs sales representative for more information.

 

Roadnet Mobile

Entering Freeform Quantity Reason Codes

Found in Roadnet Mobile for Android

When you create quantity reason codes, even when you think you have covered all the possible reasons why an actual quantity doesn't match a planned quantity, inevitably workers will encounter a more outrageous reason why they have an over, short, or damaged situation. So that workers can provide a relevant reason why an actual quantity doesn't match a planned quantity, they can now enter freeform text for a quantity reason code.

Before a worker can enter freeform reason codes, you must enable the Add Freeform Reason Code region setting.

In Roadnet Anywhere Web, check the Add Freeform Reason Codes region setting box on the Smart Phone - Allowed Worker Actions page.

In Roadnet Anywhere Client, check the Add Freeform Reason Codes region setting box on the Smart Phone tab of the Dispatch Settings page.

On the mobile device, when the worker enters an over, short, or damaged quantity, you can require them to enter a reason code before they can depart the route. When they press Select a Reason Code, if there is no appropriate code in the list that is provided, the worker can press Add Other Reason Code and enter a reason that is more accurate. When the worker presses OK, the reason displays with the over, short, or damaged quantity.

Note: The worker's entry is limited to 256 characters.

Quantity reason codes entered by the worker can be seen in Order Status. Search for the route and expand the information. Notice that the Short Reason Code reflects what the worker entered on the mobile device.

 

Including the Order Signature on a Receipt

Found in Roadnet Mobile for Android

Previously, you could only see the stop signature on a receipt. Now, if the worker collects a separate signature for an order, that signature can display on the receipt when it is viewed, printed, or emailed.

To see the order signature on the receipt, you must add it to your print template. The signature collected for an order is a sub property of the OrderWithLineItems class called OrderSignature. You can edit your print template using a third party XSLT editor or contact Omnitracs Professional Services to discuss purchasing a customized print template.

Notes: Basic information on changing your template can be found in the Viewing, Printing, and Emailing Receipts on Android Mobile Devices document.
The default print template is delivery_receipt_report.xslt.

Limiting Items on the Verified Orders List

Found in Roadnet Mobile for Android

The Verified Orders screen in Roadnet Mobile for Android can become overwhelming when the worker is looking for an order or line item in a long list of orders and line items. There are already a few ways the worker can manage the list. It can be sorted numerous ways and can be filtered by items that have been verified or cancelled. Now, so that the worker can review reconciled items that do not meet the planned quantities, two new filter options have been added. The option the worker sees depends on if Enable Over, Short, and Damaged Quantities box is checked on the Region's Smart Phone - General page under Phone Settings.

If your organization lets workers mark over, short, and damaged quantities, the workers can now filter the Verified Orders screen to hide orders and line items that do not have an over, short, or damaged quantity. For a worker to see only those orders and line items with over, short, or damaged quantities, from the Verified Orders screen, press Menu and check the Hide Items w/o OS&D box. The list shows only orders and line items that have over, short, or damaged quantities. To show all the items, the worker simply removes the check from the Hide Items w/o OS&D box.

If your organization uses Delivery and Pickup Quantity Reason Codes so that your workers can explain why an order or line item's planned quantity does not match an actual quantity, your workers can use the new filter that hides items that do not have a reason code assigned. Workers can now limit the Verified Orders list to only orders and line items that have been assigned a reason code.

For a worker to see only those orders and line items with a reason code assigned, from the Verified Orders screen, press Menu and check the Hide Items w/o Reason Code box. The list shows only orders and line items that have an assigned reason code. To show all the items, the worker simply removes the check from the Hide Items w/o Reason Code box.

Note: The worker will see only one of these new filter options. Either Hide Items w/o OS&D or Hide Items w/o Reason Codes displays, depending on if you use over, short, and damaged quantities.

 

Roadnet Mobile Manager

In a continuing effort to provide a useful and user friendly mobile application, enhancements have been made to Roadnet Mobile Manager.

Navigating to An Equipment's Current Position

Found in Roadnet Mobile Manager

Breakdowns happen. If you are in a very rural area and your workers find themselves on long stretches of roadway, they may not be able to tell you their exact location, so that you can send a mechanic out to fix the equipment. You can now find your equipment using Roadnet Mobile Manager. Using the equipment's current GPS position and Google Maps on your mobile device, you can get driving directions to the equipment.

From the Route Details and Equipment Details screens, press Navigate to Vehicle. Google Maps opens in Navigation mode. You can then get turn-by-turn driving directions to the equipment's location. You can also access the map from the Fleet Overview screen. Press the individual piece of equipment on the overview map to access turn-by-turn directions.

Note: If Google Maps is not installed on the device, you will see the location, but you will not get turn-by-turn directions.

 

Limiting the Workers List

Found in Roadnet Mobile Manager

The workers list in Roadnet Mobile Manager can get lengthy. Filtering the list helps to show you only those workers you want to see. Previously you could show all workers or show only workers on active routes. The filter has been enhanced to eliminate workers from the list in two ways, eliminate workers from the list that are on active routes or eliminate workers that are not on active routes. To filter the list, toggle the appropriate Exclude Workers option on or off, depending on what you want to see. Leave both options off to show all workers. Press Apply to save the filter and return to the Workers list with your filter applied.

 

Viewing And Assigning Unassigned Orders

Found in Roadnet Mobile Manager

Roadnet Mobile Manager lets you easily see how your routes are progressing, where your equipment is, and which orders have been cancelled. Now, you can also keep up with orders that have not been assigned to a route.

The new Unassigned Orders screen shows you information about the orders that are not assigned to a route. You can see information such as the Order ID, the order begin date, if the order is a delivery and/or pickup, and information about the stop associated with the order.

Note: You may need to scroll across up or down the screen to see all the available information categories.

You can filter the unassigned orders list by the Begin and End Date as well as the type of order: Pickup, Delivery, Delivery and Pickup, or Transfer.

You can also assign unassigned orders to a route. This can be done manually or you can use a route that is suggested by Roadnet Mobile Manager. To see details about the unassigned order, have Roadnet Mobile Manager suggest a route, or to manually assign a route, press the unassigned order with which you want to work. The unassigned order details screen displays.

To have Roadnet Mobile Manager provide suggestions as to which route this order should be placed on, press Suggest Route. The Select Route screen displays with suggestions. You can see the Additional Cost, Time, and Distance that is added to the route if you place the order on that suggested route. Press the route you want to place the order on. From the menu that pops up, choose View Route Details or Assign Order. View Route Details displays the Route Details screen. Press the Back icon to return to the list of suggested routes. Assign Order places that order on the chosen route and returns you to the Unassigned Orders screen.

To manually assign the order to a specific route, press Assign Order. A list of available routes displays. Press the route you want to place the order on. From the menu that pops up, select how you want the order placed on the route: First, Last, by Cost, by Time Windows, or by Routing Goals. The order is placed on the chosen route and returns you to the Unassigned Orders screen.

 

Using the Roadnet Mobile Manager Dashboard

Found in Roadnet Mobile Manager

Accessing your information just got easier. You can now see a quick summary of your information on the Roadnet Mobile Manager Overview dashboard. The Overview dashboard gives you a quick glance at each category of information: Routes, Exceptions, Cancelled Orders, Unassigned Orders, Workers, and Equipment. You can see how many routes are in what status of completion and how many routes are meeting their time windows, the number of acknowledged vs. unacknowledged exceptions and a count for each type of unacknowledged exception, the order type and cancelled source for cancelled orders, the order type for unassigned orders, the number of workers on a route vs. not on a route, which duty status your workers are currently in, and the number of equipment that are in use vs. available and their motion state.

Press the arrow next to the category for which you want to see more information and the associated information screen displays.

If you want to see everything that Roadnet Mobile Manager has to offer on the front screen, you can leave it as it is or, you can easily remove the unnecessary information.

To make changes to the Overview dashboard, press the overview settings icon.

The Overview Settings screen displays. The Overview screen default setting is that all the information is enabled. If you want to remove a category or specific information, toggle the appropriate category or piece of information off.

If you want to turn it back on, change the toggle to on. If you decide you want to see all the information again, toggle Enable All to on. After you make your changes, press Apply and the Overview dashboard displays your selections.

 

Finding A Truck's Current Location On The Route

Found in Roadnet Mobile Manager

When looking at the route details map, it can be hard to locate the equipment on the route. You have to manually zoom in to the route and find the equipment icon. With this new feature, you can now quickly see where on the route map the equipment is currently located. From the Route screen, view the route details of the equipment you want to see. Press Show on Map and then press the crosshairs icon. The map zooms into the current location of the equipment.

 

Resetting Filters to the Default

Found in Roadnet Mobile Manager

Previously, when you used filters in Roadnet Mobile Manager, to clear them and go back to the original list, you had to manually clear or undo any filters that you set. Now, to reset filters to the defaults on the Filters screen, simply press Reset to Defaults and then press Apply to update the list.

 

Centralized Messaging

In a continuing effort to provide a useful and user friendly messaging application, enhancements have been made to Centralized Messaging.

Including Web Links in Messages

Found in Roadnet Anywhere Web and Roadnet Mobile for Android

Currently when you use Centralized Messaging and a web address is included in a message, you must copy and paste it into your internet browser. Now, if a web address is received in the body of a message, when the recipient clicks on the link, an internet browser opens showing the page associated with the link that was included in the message.

Note: The web address does not appear as a link to the sender until the message is sent.

Links in Centralized Messaging have been added to both Roadnet Anywhere Web and Roadnet Mobile for Android.

Viewing Thumbnails in a Message

Found in Roadnet Anywhere Web and Roadnet Mobile for Android

When a picture is received as an attachment in Centralized Messaging, the file name displays and you must click on it to open the picture. Now, when you receive a picture, a thumbnail of the picture displays with the message. If you want to see the picture in more detail, simply click or press the thumbnail and the picture is downloaded to the computer or mobile device. You may need to click on the downloaded file to open it to full view.

A thumbnail of the picture also shows when you are creating a message. In Roadnet Anywhere Web, when you send a message with a picture, the thumbnail displays after you send the message. In Roadnet Mobile for Android, the thumbnail displays when you return to Roadnet Mobile after taking the photo or picking an existing photo.

This enhancement has been made in Centralized Messaging for both Roadnet Anywhere Web and Roadnet Mobile for Android.

Inactive Workers Removed from the Recipient Search

Found in Roadnet Anywhere Web

Previously when you created a message and you searched for a worker in the To: field, the list that displayed included all workers that exist in Maintenance. Now, so that you do not see workers that are no longer with the company, the worker list is filtered to exclude workers that are not marked as an active employee in Maintenance.

Creating and Managing Mailing Lists

Found in Roadnet Anywhere Web

If you find yourself sending messages to the same group of workers, routes, depots, and/or regions, over and over again, then the mailing list enhancement in Centralized Messaging will be a time saver for you. If you have the proper permission, mailing lists can be created that contain all the workers, routes, depots, and regions that receive the same messages. You will no longer need to waste time searching for and choosing each individual worker, route, depot, or region when sending messages to a group.

Mailing lists are shared across the organization. Anyone can use an existing mailing list to send a message. But, only people with the proper permission can create and remove mailing lists. Those that you want to manage mailing lists must have the Can Save and Can Delete permissions assigned to their role.

In Roadnet Anywhere Web, in Administration, click the green button and choose Role from the list that pops up. Add a new role or edit an exiting one. On the Entity Permissions tab, check the appropriate boxes for Correspondence Mailing List. Can Save allows mailing lists to be saved. Can Delete allows mailing lists to be removed from Centralized Messaging.

In Roadnet Anywhere Client, from the Administration menu, choose Role. Add a new role or edit an existing one. In the Record Permissions area, check the appropriate boxes for Mailing List. Can Save allows mailing lists to be saved. Can Delete allows mailing lists to be removed from Centralized Messaging.

To manage mailing lists in Centralized Messaging, click on the Mailing Lists folder.

To add a mailing list, click the [Create] button. Enter a Name for your mailing list and then click in the Members field. Start to enter the worker, route, depot, and/or region you want to add. A list pops up that contains choices that meet your criteria. Click on the worker, route, depot, or region you want added. Continue to type and click on workers, routes, depots, and regions until you have include all that you want to add to your list. Click the [Save] button. The list is added to the center column in the Mailing Lists folder.

Existing lists display in the center column. When you click on a list, you see which workers, routes, depots, and regions are included in the mailing list in the right panel. Add to the list by clicking in the To field and starting to enter the worker, route, depot, and/or region you want to add. A list pops up that contains choices that meet your criteria. Click on the worker, route, depot, or region you want to add. Remove workers, routes, depots, and regions from the list by clicking the X next to the one you want to delete. Click the [Save] button.

Once a mailing list is saved, it can be used by anyone in the organization to send a message to the group. To use a mailing list, when creating the message simply place your cursor in the To: field and begin typing the name of the list. A list pops up that contains choices that meet your criteria. Choose the list you want to use. You can add other workers, routes, depots, regions, and mailing lists to the To: field. Complete the message and send it as you would any other message.

Note: Hover over the mailing list that you have chosen in order to see the workers, routes, depots, and regions that are included in it.

Identifying Who Has Received A Message

Found in Roadnet Anywhere Web

When you send a message, currently you do not know if it was received or read. Some workers may be out for the day, others may be servicing a stop and unable to read the message right away. You can now see who has seen the message and who has not. For messages that have been sent, show the recipient details. Names of the workers that have not read the message display in bold. Hover over the worker name and you see if the message was delivered or read, and if so, what time.

 

Telematics

Clearing Active Trouble Codes

Found in Roadnet Anywhere Web

Trouble codes are sent from the Telematics device to Roadnet Anywhere Web to alert you to potential problems with the equipment. You can review the list of the active trouble codes sent by each Telematics device in Telematics Diagnostics. Normally, when the issue clears on the equipment, the Telematics device sends a message and the active trouble code is removed from the list in Telematics Diagnostics. However, there may be times when the clear message is not sent, but you know that the situation no longer exists. Now, you can manually clear the active trouble code so it is removed from the list of active trouble codes.

In Telematics Diagnostics, find the device that has the trouble code you want to clear. Scroll across the list to the Active Trouble Codes column and click on the number in the column, the Active Trouble Codes window opens. For the code you want to clear, click the [Clear] button. The code is removed from the list.

 

Telematics Diagnostics Report

Found In Roadnet Anywhere Web

Telematics Diagnostics in Roadnet Anywhere Web provides information about your Telematics devices, which can not only help troubleshoot problems in the field, but can help you simply check the status of all your devices. However, if you have a large number of devices, you may not be able to see them all in Telematics Diagnostics. Now, there is a Telematics Diagnostics report that lets you view information for all your Telematics devices in selected regions. The Telematics Diagnostics report is a csv file, so you can filter and manipulate the data as needed for your purposes.

To run the Telematics Diagnostics report: 

Click on the Reporting icon to open Reporting. Scroll to the Telematics Diagnostics report; the Telematics Diagnostics report options are shown. Click the Select Region arrow and choose the region(s) that you want to include in the report. If you can't quickly find a region, you can search for it. Click the [Run] button; the report is run and appears as a download on the computer.

Note: The Telematics Diagnostics report is only available as a .csv file.

 

Completing Maintenance on Equipment that is not part of the Equipment Maintenance Plan

When maintenance workers are working on equipment, they may discover additional necessary work that was not part of the scheduled equipment maintenance plan for the equipment. For instance, while performing an oil change the worker may discover that the timing belt is worn and needs to be replaced. Now, the maintenance worker can easily indicate this maintenance was done while completing maintenance on the equipment. When the maintenance worker opens the list of possible tasks to complete on the Enter Performed Service window, the list includes items that were not originally included in the equipment's maintenance plan, so they can be selected and added to the Maintenance Performed list.

 

Insight

In a continuing effort to provide a useful and user friendly analytic application, enhancements have been made to Insight.

Route Costs from Roadnet Transportation Suite Available in Insight

Found in Insight

Insight users that receive data directly from the Roadnet Transportation Suite can now see route cost information in Insight.

Analyzing Net Revenue

Found in Insight

You can now use Insight to see the net revenue of your routes. You can sort net revenue by route, service location, organization, and time. There is also a new template, Net Revenue, that displays the information in a KPI.

Comparing Net Revenue against Actual Route Cost is a simple way to see if your routes are profitable. One way you might use net revenue is to find out which of your routes cost more to run than the profit they return. First you would create a custom measure that finds the percentage of net revenue to actual route cost. Then, using your custom measure, create a rule that shows only routes where your custom measure value is less than 1. Drill into the net revenue information and view which routes are causing the issue.

 

Navigation

Limiting POIs

When drivers need to find a gas station, truck stop, or other point of interest, they can search for one. Previously, they had the option to search for POIs that were near their route, or for all POIs. However, this could still provide the driver with a long list of POIs that needed to be scrolled through to find the best option. Now, drivers can fine tune the search, limiting the search results to those that are near the current location (Nearby), (along the route) In Route, or (near the destination) At Destination.

Note: This option is only available if the driver has a route loaded.

Updates to the User Interface

To make it easier for drivers to find information, several updates have been made to the user interface.

  • All menu options have been consolidated under a hamburger menu. In addition, the Quick Menu option has been replaced with a kabob menu; the driver can choose to place the most commonly used actions in this menu. To configure click the hamburger menu and choose Quick Menu Settings from the main menu, then choose the options you want to see on the Quick Menu.

  • To see more information about a waypoint or stop, simply click on it and a tooltip with more information, such as the name and address of the location, appears.
  • It is now easier for a driver to start searching for a waypoint, POI, or destination.
    • To search for a city, address or POI, click in the Search field; a window opens where you can search for city center and full address under those OR select from map, history, POI.
    • To use the map to find a location, click the green Drag map to select icon. Move around the map to find the proper location, then press on it. Choose Start, Add to Trip. or Favorite.

Compliance Mobile

Reassigning Drive Time in the Mobile Log Editor

Several changes have been made to the way Omnitracs XRS Mobile handles drive time reassignments:

• If drive time has been reassigned from a primary driver to a co-driver and the co-driver has not yet accepted the changes, the primary driver cannot modify any of the events that have not yet been accepted. The app will display a massage that says “Reassigned events are awaiting approval from the other driver and cannot be edited.”

• Log events that have not yet been confirmed by the second driver will not be included in HOS calculations.

• Events still awaiting confirmation by the second driver will not be included in the driver log when Inspection Mode is turned off. When Inspection Mode is turned on, those events will appear as pending events.

Note: The drive time reassignment feature is only available for ELD Mode companies. It is not available for Mixed Mode or AOBRD Mode companies.

Carrier Edits Review Process for Drive Time Reassignment

When drive time is reassigned from one driver to another in the host, the mobile behavior will be as follows:

• Drivers will have to accept or reject all edits associated with the reassignment at the same time, even though they are displayed as individual events. When the driver selects Confirm or Reject for any event, a message appears: “Drive time is being reassigned. All associated events must be accepted or rejected as a group.” When the driver selects OK, the associated events are all updated as either confirmed or rejected, depending on the driver’s selection. Carrier edits that are not part of the drive time reassignment can be confirmed or rejected separately.

• When one driver accepts the reassigned events, the edits remain as pending edits in that driver’s log until the other driver accepts the reassignment.

Canadian Drivers Can Now Email Logs

A new feature in Compliance Mobile allows Canadian drivers to email their driver logs to a recipient. This feature is also available to U.S. drivers in AOBRD or Mixed Mode companies; it is not available for U.S. drivers in ELD companies.

Drivers can email their logs as long as they are On Duty, the mobile is connected to a vehicle, the vehicle is stopped, and there are no pending log edits or UVA events.

To email logs:

1. Select the three-dot menu in the top-right corner of the HOS Log screen and select Email Driver Log. The Request to Email Driver Log screen opens.

2. Type the email address in the Enter an Email Address field. You can enter only one address with a maximum of 256 characters.

3. If you want to enter a comment, type it in the Enter a Comment field. You can enter up to 60 characters. Comments are optional.

4. Select Send. You receive a confirmation notice that the request has been sent and is being processed.

The request is then sent to the host, which assembles the driver’s logs and sends them to the requested email address.

Note: If any pending edits or UVA events exist, the Carrier edits exist for Driver screen opens before the request is sent to the host. After you confirm or reject the edits, the email log request will be sent.

Drivers are Alerted of Time Remaining to Complete Break

Drivers following U.S. HOS rules now receive a warning if they need more time off to complete their break time before a cycle reset. The warning is tied to the driver’s rule set. It appears when the driver selects On Duty after having been in Off Duty or Sleeper Berth status.

• For cycle/weekly resets or shift resets, the warning appears if the driver has one hour or less remaining before reaching the required reset time.

• For the eight-hour rest break on U.S. rules, the warning appears if the driver has 10 minutes or less remaining before reaching the required rest time.

In all cases, the message indicates when the reset will be complete and asks the drivers if they’re sure they want to change their duty status. If the driver selects OK, the duty status changes. If the driver selects Cancel, the duty status does not change and the driver returns to the Change Duty Status screen.

Changes to Comment Fields in Mobile Log Editor

Several updates have been made to the comment fields in the mobile log editor.to support changes made in the host.

Host users can configure company settings to give drivers a wider variety of comment options when they change duty status using the mobile log editor. Host users can enable free-form comments, pre-defined comments, both, or neither. They can also specify whether drivers can enter one or two comments. The comment fields in the edit screens have been updated to reflect these settings.

Comments can be required or optional. If a comment is required, it must contain between 4–60 characters.

To enter a free-form comment, select the field and type your comment.

When you select a pre-defined comment field, a pop-up window opens that lists all the comments that are pre-defined in the host. As many as 15 comments can be pre-defined.

Choose the appropriate comment and then select OK.

In addition, the name of the comment field that drivers fill out when they change duty status has been changed from Comment to Edit Reason.

Note: Duty status changes to Yard Move and Personal Conveyance still require a comment of between 4–60 characters, no matter how comments are configured in the host.

New Screen Shows Available Hours in Each Rule Set

When drivers change their rule set on the mobile, they now see a screen that shows them the remaining drive and duty time for each of the rule sets available to them based on their carrier’s settings.

From the HOS Log screen, select the three-dot menu and then select Change Ruleset. The Change Ruleset screen opens, showing the rulesets available to the driver and the remaining drive and duty time available for each one.

To change the ruleset, select the Change button, choose your new ruleset, and then select OK.

Clear Device Registration

Mobile users can now clear the device registration in order to move the device to another company.

To clear the registration:

1. Select the three-dot menu in the top right corner of any screen and select Settings, then Setup. The Setup screen opens.

2. Select Clear Device Registration from the menu. You receive a message asking you to confirm that you want to unregister from the device and reminding you that the device will need to be re-registered before Compliance Mobile can be used on it again.

3. Select Yes to continue clearing the registration. Select No to cancel the action.

If you select Yes, a notification message appears telling you that the registration information will be cleared when you log out of the app.

Updates to the Mobile Upgrade Process

Some new features in Compliance Mobile and RDC require that customers use the most recent version of Compliance Mobile rather than an older version. Using the most recent mobile version also ensures that you are ELD-compliant.

Compliance Mobile will now require users to install upgrades when they are made available. When drivers are prompted to upgrade the app, they can decline the upgrade by selecting No. They can do this three times (that is, for three logouts). The third time the Update Confirmation message appears, drivers will see an additional message telling them this is the last time they can select No and that the upgrade will be completed the next time they log out.

If the driver logs out a fourth time without updating, the update will begin automatically.

If you need your company’s devices to be excluded from these mandatory upgrades—for instance, if you use device management software—please contact your customer service representative.

Note: If Allow Automatic Software Updates is not selected for your organization, the mandatory mobile upgrades do not apply.

New User Data Privacy Notice

Due to Google’s data privacy requirements, users must now consent to allow the device’s phone number to be sent to Omnitracs for registration. In support of this requirement, when users first launch the app after installing it, they will be presented with a User Data Privacy screen that explains how the data is used. To continue using the app, users must select Accept.

Software Corrections

The following software corrections were made in Roadnet Anywhere 5.6.

Key Read Me Notes
  Admin
RA-41811 Users can now select "Not assigned" as the Default Telematics I/O Configuration option when editing a region.
RACS-3608 There was an issue where users could log in using a temporary password, even after they were forced to change their password. This has been corrected, and the temporary password will no longer work.
RACS-3773 Users were receiving an error when attempting to clone a canned role. This has been corrected.
RA-41569 Drivers are now able to enter free form Over, Short and Damaged reason codes on Android devices.
  Maintenance
RA-40880 The "Deleted Time" field that is displayed when viewing deleted maintenance items no longer uses the GMT timezone. This field now displays in the current region's timezone.
RA-40724 The entity grids in Maintenance have been widened to take advantage of the space. This should reduce the amount of data that gets truncated.
RA-34190 When editing an unassigned order directly from the search results view in Roadnet Anywhere Client, changes were not immediately reflected in the results. This issue has been resolved.
RACS-3767 There was an issue when cloning the same Service Window Type over again, from the 3rd clone the previously cloned entity was overwritten instead of creating a new entity. This has been corrected.
RACS-3626 The search functionality for maintenance items was not working properly if the user only entered two characters for the search. This has been corrected, and you can now search using only two characters.
RACS-3638 Some users were experiencing an error when trying to manually add an unassigned order. This has been corrected.
RACS-3592 Users creating a custom Restricted Hours exception rule were not able to choose Use Depot Open/Close Times or Use Region Restricted Operating Hours as the Mode. This has been corrected.
RACS-3730 There was an issue that was causing a service location to be geocoded to the incorrect street arc. This has been corrected.
RA-40880 The "Deleted Time" field that is displayed when viewing maintenance items no longer uses the GMT timezone; the times now display in the current region's timezone.
  Routing
RA-42465 When Equipment Type Restrictions are the reason an Order is Unrouted the word 'Location' has been removed from the "Reason Not Placed on New Route".
RA-41692 A new right click menu option, "Update Preferred Route IDs" has been added for routes and serviceable stops.
RACS-3747 Deleting a route in Roadnet Anywhere Client no longer results in an unexpected error.
RACS-3774 There was an issue that was causing some users to receive an error when running Create Routes. This has been corrected.
RA-42465 When Equipment Type Restrictions are the reason an Order is Unrouted, the word "Location" has been removed from the Reason Not Placed on a New Route.
RA-41692 A new right click menu options, Updated Preferred Route IDs, has been added for routes and serviceable stops. If selected, the service locations' preferred route ID will be updated with the route's route ID.
RA-43189 There was an issue that was causing the times and distances to be inflated when Create Routes was run, causing orders to be unassigned. This has been corrected.
  Data Transfer
RACS-3632 There was an issue that was causing importing service locations and importing routed solution to fail in specific situations. This has been corrected.
RACS-3418 The Import Routed Solution data transfer layout did not include the route custom properties. This has been corrected, and the route, order, and line item custom properties are now listed.
  Dispatching
RACS-3600 There was an issue that was causing the incorrect time zone to be displayed in the Quantity Input Date Time column for line items in FleetView. This has been corrected.
RACS-3734 There was an issue that was preventing the depot dropdown from appearing as part of the filter in FleetView for users that did not use region hierarchy. This has been corrected and the depot dropdown in now available when only one region is selected in the filter.
RACS-3635 There was an issue that prevented the planned path of a route from being plotted correctly if it did not originate from a Depot. This has been corrected.
  Insight
RACS-3645 In certain situations Insight was not properly retrieving the user or business unit measurement options when calculating values in Insight. This has been corrected.
RACS-3711 There was an issue that was preventing scheduled reports from sending in Insight. This has been corrected.
RACS-3738 There was an issue that was causing every depot to have an asterisk next to it on the Route Summary View. This has been corrected.
  Roadnet Mobile iOS
RACS-3537 The defect preventing Roadnet Mobile for iOS users from using "First Stop is Origin" flag has been identified and resolved.
RACS-3717 There was an issue that would cause stops to be added to routes when Roadnet Mobile iOS was used, depending on the configuration. This has been corrected.
RACS-3736 There was an issue that was causing Mobile Device Diagnostics to show the wrong mobile version for iOS devices. This has been corrected.
RACS-3764 There was an issue preventing drivers from unloading routes from the mobile device if the same piece of equipment was assigned to multiple routes. This has been corrected.
RA-43108 There was an issue where the consignee was disappearing once a signature was captured on iOS devices. This has been corrected.
  Miscellaneous
RACS-3679 There was an issue that was preventing the proper stop from being highlighted in Order Status. This has been corrected.
RACS-3453 There was an issue that was preventing service location custom properties from displaying on the Plot Information window. This has been corrected.
  Roadnet Mobile
RACS-3646 There was an issue that could cause the second driver to be unassigned from the route when the route was loaded on the mobile device. This has been corrected.
RACS-3639 There was an issue where Roadnet Mobile would crash when attaching images to forms. This has been corrected.
RA-41569 Drivers are now able to enter free form Over, Short, and Da,aged reason codes on Android devices.
RACS-3704 There was an issue where if an emoji was entered as part of the Consignee name, the route stopped updating. This has been corrected.
RA-43162 There was an issue preventing drivers from receiving route notes sent by the dispatcher. This has been corrected.
  Reporting
RACS-3580 There was an issue where the Off Day Delivery report was including locations with planned data, even though actual data was selected. This has been corrected.
  Telematics
RACS-3594 There was an issue with the Telematics Diagnostics component taking an excessive amount of time to load if there was a large number of Telematics devices. There is now a limit on the number of devices that can be loaded. In addition a new Telematics Diagnostics report was added that will allow the user to print a csv file that includes all the devices.
RACS-3748 There was an issue that was preventing firmware upgrade scripts from being available for some Telematics devices. This has been corrected.
  Web Services
RACS-3589 Creating routes using web services that contain fixed service times for stops, and no orders, now correctly display the stops total fixed service time.
RACS-3602 There was an issue preventing web services users from being able to log into Roadnet Anywhere due to the WSDL showing the wrong protocol. The WSDL has been updated to reflect the correct protocol and URL.
RA-42992 There was an issue that was causing SaveOrders to fail with an unexpected error if the order does not exist. The error message has been updated to be more specific.
 Compliance Mobile Application
XRS-10191 Drivers performing a Canadian pre-trip inspection sometimes lost changes they made in the Pre-Defects screen after they scrolled through the list and then scrolled back. This occurred primarily when a defect was changed from Minor to Major or vice versa. This issue has been resolved.
XRS-10333 The primary driver was being logged out of the mobile when the co-driver exceeded the offline cached login time. This issue has been resolved.
XRS-10602 The red circle on the hamburger menu that indicates the number of unread messages was truncating the number if the driver had more than ten unread messages. For instance, if the driver had 11 unread messages, the badge displayed the number 1. This occurred because there was not enough space on the red badge to display larger numbers. The issue has been resolved; now if the driver has more than ten unread messages, the badge displays “9+” to indicate that there are additional messages.
XRS-11962 Vehicle-based malfunctions were not triggering Paper Log Mode when the device was reconnected to the same vehicle. This issue has been resolved.
XRS-12048 An issue that prevented drivers from being prompted to certify their driver logs for the previous day has been resolved.
XRS-12319 Some drivers were receiving a 16-hour violation even though they had not taken a 16-hour exemption and had driven less than 16 hours. This issue has been resolved.
XRS-13735 The UVA window only retrieved 4–5 days’ worth of data if the Organization filter was set to “All.” If only a few organizations were selected, the date range increased. This issue has been resolved.
XRS-13036 Duty statuses were sometimes duplicated from one driver's log to another if both drivers had used the same mobile device. This has been corrected.
XRS-12659 An issue that caused some drivers to receive rest break violations even though they were operating under Short Haul rules has been resolved.
XRS-12761 For some drivers, the Hours of Service mobile application was crashing after they performed a pre-trip inspection and tried to accept carrier edits. This issue has been resolved.
XRS-13223 When drive time was reassigned from Driver A to Driver B and both drivers accepted the reassignment, the driving event did not appear in Driver B’s mobile log when Inspection Mode was turned off. This issue has been resolved.
XRS-13279 An issue that caused the Hours of Service application to report drive time incorrectly has been resolved.
XRS-13317 When drive time was reassigned from Driver A to Driver B and only Driver A accepted the edits, meaning the change was still pending, the Inspection Mode view in the log showed the event as both active and inactive. This issue has been resolved.
XRS-13361 Reply forms with a “Cancel” trigger were erroneously being displayed in the Activities screen for stops. This issue has been resolved: forms with a “Cancel” trigger are no longer displayed in the Activities screen and will not be included in the list of forms drivers can choose from when they are sending a new form message from the host.
XRS-13499 If drive time was reassigned from Driver A to Driver B and both drivers accepted the reassignment, Driver A’s mobile logs were not being updated, although the changes appeared correctly in the driver log in the host. This issue has been resolved.
XRS-13512 If drive time was reassigned from Driver A to Driver B, Driver A accepted the changes but Driver B rejected them, and the drive time was then reassigned to Driver C, the Inspection Mode view in the HOS Log screen displayed more than the expected status events. This issue has been resolved.
XRS-13551 AOBRD drivers wre able to edit their logs on the mobile even though the Allow AOBRD Log Editing setting was turned off. This issue has been resolved.
XRS-13819 If a driver drove a vehicle that was then deleted or moved to a different region, the vehicle would not show up on the eRODS vehicle list, causing the file transfer to fail. This issue has been resolved.
XRS-4316 When an AOBRD driver accepted carrier edits, events for the previous day were not appearing in the driver's log. This issue has been resolved.
XRS-4402 When a primary driver indicated defects during the pre-trip inspection and then the co-driver took over and did a pre-trip inspection on the same vehicle, the defects did not carry over from the initial inspection. This issue has been resolved.
XRS-4485 Drivers on state rules were being prompted for Short Haul, but if they accepted on the prompt they were not switched to the Short Haul rule. This issue has been resolved.
XRS-4873 If a driver's tablet was turned off in the middle of a trip for any reason, UVA was being created in error. This only affected vehicles in AOBRD companies. This issue has been resolved.
XRS-5088 The Hours of Service application was restarting the HOS counter if a rule change occurred, but the rule set change did not actually change. This issue has been resolved.
XRS-5361 If a user selected "Deny" for any of the permission questions that arise when the Hours of Service application is installed, the app crashed. This issue has been resolved.
XRS-5839 An issue that caused the Gap in Mile alert to be triggered incorrectly has been resolved.
XRS-6352 An issue that caused the sound on the mobile to be at maximum volume regardless of the device's volume setting has been resolved
XRS-6733 Several cosmetic issues (such as text alignment) on the Carrier Edits screen have been resolved.
XRS-6852 When a driver was on Short Haul up to and beyond eight hours and then changed to a federal rule, the mobile did not create a rest break violation. This issue has been resolved.
XRS-7180 Violation alerts were not being sent when the Hours of Service application was running in the background on devices using Android 8.0 (Oreo). This issue has been resolved.
XRS-7502 When the primary driver and co-driver were both on Short Haul, only the primary driver was switched to federal rules after the allotted 12 hours; the co-driver remained on Short Haul and was in violation as a result. This issue has been resolved .
XRS-8223 In the Hours of Service application, if an Off-Duty driver has been on Personal Conveyance for 30 minutes or more, the time will not be counted toward the 30-minute off-duty time required for a rest break. This is the expected beha
XRS-8224 When a host user inserted the US 7/60 Short Haul hrs (Dec 2014) rule set into a driver's log, the 8-hour rest break violation was corrected and an Invalid Short Haul Violation was triggered. This issue has been resolved.

 


© 2019 Omnitracs, LLC. All rights reserved.
Omnitracs is a trademark of Omnitracs, LLC. All other trademarks are the property of their respective owners.

Omnitracs endeavors to ensure that the information in this document is correct and fairly stated, but Omnitracs is not liable for any errors or omissions. Published information may not be up to date, and it is important to confirm current status with Omnitracs. Specifications subject to change without notice.

This technical data may be subject to U.S. and international export, re-export or transfer (export) laws. Diversion contrary to U.S. and international law is strictly prohibited.