Roadnet 5.5 - New Features and Enhancements in Roadnet Anywhere

 

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

Miscellaneous

Dispatching

Compliance

  • You can create and manage compliance alerts to avoid HOS violations.
  • You can now run the HOS Driver Payroll Summary Report and schedule it to run automatically.
  • You can now choose a Default Reporting Site in the Driver Log Editor and UVA editor.
  • The Driver Log Editor and UVA Editor use the driver's default reporting site to determine whether the driver is eligible to use Short Haul or Big Day exemptions.
  • There is a new Reason column in the Assign Fuel Purchases window to indicate why a fuel file was not auto-reconciled. The options are:
    • No Matching Distance - the vehicle listed in the import file did not include any distance in the state
    • Vehicle Does Not Exist - the vehicle listed in the import file was not found in the company it was imported into
  • 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").
  • The trailer's license plate number, state or province, and license issuing jurisdiction will now be included in the trailer inspection form.
  • Previously, when users performed a Relay swap, they received a mesage saying "Relay data is cleared. You can now unplug the relay." This message, however, sometimes led drivers to unplug the Relay prematurely because data is not actually cleared until the green LED light bliks every 3 seconds. 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 Rleay reboot has completed! When the green LED blinks once every 3 seconds, you may unplug the Relay."
  • 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 US).
  • To relax the validation process for Compliance customers, Roadnet Anywhere has made some changes to the HOS information you need to enter when adding or editing a user, a worker or a region.
    • You are required to enter a first and last name for every user.
    • You are no longer required to enter a worker's CDL license number or license issuing country/ state.
    • You are no longer required to enter a complete HOS fleet address when editing or adding a region.
  • Roadnet Mobile

    Roadnet Mobile Manager

    Centralized Messaging

    Telematics

    Routing

    Reports

    Insight

    • When setting up your company's structure in Insight, you can choose to set up a custom hierarchy in which you can have only five levels of information or you can set up a region hierarchy which lets you create an unlimited number of levels. If you choose to setup a region hierarchy, you cannot change to a custom hierarchy in Insight.
    • You can see data from all levels in your region hierarchy, even those on skipped levels on KPIs in Insight.

    Web Services

    Navigation

     

    Maintenance

    Adding Equipment Manufacturers

    When adding a piece of equipment, you are able to chose a manufacturer from a list of common manufacturers. Now, rather than selecting Other when you have a piece of equipment not made by one of those listed manufacturers, you are able to add your manufacturer to that list yourself. Once added, that new manufacturer will appear on the list of manufacturers when an piece of equipment is added.

    Found in Roadnet Anywhere Web

    Go to Maintenance and scroll to Equipment Manufacturers.

    To add an Equipment Manufacture, click the [Add] button. The Add Equipment Manufacturer window opens.

    To edit an Equipment Manufacturer, click the edit icon. The Edit Equipment Manufacturer window opens.

    Enter an ID and description for the Equipment Manufacturer.

    Click [Save].

    The Equipment Manufacturer will now appear on the Manufacturer list when adding or editing a piece of equipment.

     

    Found in Roadnet Anywhere Client

    Click on Maintenance and select Equipment Manufacturers.

    To add an Equipment Manufacture, click the add icon. The Add Equipment Manufacturer window opens.

    To edit an Equipment Manufacturer, click the edit icon. The Edit Equipment Manufacturer window opens.

    Enter an ID and description for the Equipment Manufacturer.

    Click the Save button.

    The Equipment Manufacturer will now appear on the Manufacturer list when adding or editing a piece of equipment.

     

    Specifying Whether to Delete Service Locations While Importing

    Found in Roadnet Anywhere Client

    In the past, when you imported service locations you could simply import a service location ID, and the service location was deleted. But, what if you don't want those service locations deleted? Now, you can choose whether or not you want those items deleted when importing. If you choose not to have the service locations deleted, those records will be ignored during the import.

    To delete service locations that only contain an ID in the import file, click on the Import menu and choose Import Service Locations; the Import Service Locations tab open. In the Service Location Options, check Delete Records With Only ID Specified. Choose the other options then click [Import] to start the Import process.

    Note: If you check Delete Records With Only ID Specified, a warning message will appear, letting you know that service locations will be deleted.

     

    Importing Mobile Devices Into Multiple Regions

    If you work for a large organization that has multiple regions, you may want your mobile devices to be available in more than simply the region it is imported into. However, if you want to import the mobile devices and make them available in more than one region, you need to import them into each region separately, which can be very time consuming. Now, you can specify the region(s) where the mobile device should be available in your import file, reducing the number of times you need to import each device.

    When importing mobile devices into regions, there are some things you should keep in mind: 

    • If you don't specify a region in the import file, the mobile device will be created in the current region and only be available in that region.
    • If you specify a region in the import file, the mobile device will be created and available in that region.
    • If you want the mobile device to be available in multiple regions, enter a separate line in the import file for each region. The device will be created in the first region, but available in all specified regions.
    • If you want the mobile device to be available to all regions, enter T, True, Y, or 1 for Shared to All in the import file.

     

    FieldRequiredMax. LengthDescription
    RegionNo32The identifier of the region the device should have visibility in. If you do not include a region ID, the mobile device will only be visible in the region it is imported into. If you want the device to be visible in multiple regions, include a separate row for each region.

     

     

    Identifying a Mobile Device

    When mobile devices are added to Roadnet Anywhere, they need to be identified by either a phone number or a mobile device ID. However, it was not always clear whether you should enter a phone number or mobile ID to identify the device. Now, some changes have been made to the Mobile Device window to help clarify the proper way to identify a mobile device based on the provider.

    For Compliance customers:

    If the provider is set to No Operator - enter a mobile device ID. You can click the [Generate ID] button to have Roadnet Anywhere generate a unique ID for you. The Mobile Phone Number is not available.

    If the provider is set to anything other than No Operator - enter a Mobile Phone Number. The Mobile Device ID is not available.

    For Non-Compliance customers:

    If the provider is set to No Operator - enter a mobile device ID. You can click the [Generate ID] button to have Roadnet Anywhere generate a unique ID for you. The Mobile Field Number is visible for display purposes only.

    If the provider is set to anything other than No Operator - enter a mobile device ID. You can click the [Generate ID] button to have Roadnet Anywhere generate a unique ID for you. You have the option to also enter a Mobile Phone Number; entering a Mobile Phone Number will allow you to send text messages to the worker from Roadnet Anywhere.

     

     

    Using Mobile Device Diagnostics

    Found In Roadnet Anywhere Web

    Mobile Device Diagnostics is a tool in Omnitracs Roadnet Anywhere that displays useful information about your mobile devices. You can use this tool to see information about all of your mobile devices, in all of the business unit's regions, in one place. Mobile Device Diagnostics shows which Omnitracs applications are loaded on the mobile device, the version of each application, when the device last contacted Omnitracs Roadnet Anywhere, as well as how much power is left in the mobile device's battery, among other information.

    When you open Mobile Device Diagnostics, all mobile devices that exist in your regions will be listed by default. You can filter by region to see only the mobile devices assigned to the regions that you choose. The list of devices contains several columns, providing various information about each device. You can click the [Refresh] button at any time to update the page with the latest available data. The table below provides information about each column. If you want to rearrange the columns, hide columns, sort the list of devices, or filter the list of devices, refer to Arranging the Screen.

    From Mobile Device Diagnostics, you can also quickly access the route information for any mobile device assigned to a route that is in progress. To view the route information for a mobile device, click on the route in the Current Route column. The Route Details for that route opens.

    Note: If you want to open the Route Details for more than one route, check the box at the beginning of that device's row, then click the [Show Route Details] button. A Route Details page will only open for those devices assigned to a route that is in progress. You can select and un-select all mobile devices by checking and un-checking the box in the header row at the top of the far left column.

    Granting Users Permission to Use Mobile Device Diagnostics

    If a user should be able to access Mobile Device Diagnostics, their role needs to have permission to access the tool. You can give the role permission to Mobile Device Diagnostics in Administration.

    Found in Roadnet Anywhere Web

    In Administration, click the green button and scroll to Roles. The Roles list opens. Click the [Add] button to add a new role, or the Edit icon to change an existing role; the Roles window opens. On the Permissions tab, check Can Use Roadnet Info Center (RIC) Web Component, then choose either Can Use All RIC Components or Can Use Selected RIC Components. If you chose Can Use Selected RIC Components, check Mobile Device Diagnostics.

    Found in Roadnet Anywhere Client

    Click on the Administration menu and scroll to Roles; the Roles list opens. Click the Add new item icon, or select a role to change and click on the Edit icon; the Roles window opens. On the Permissions tab, check Can Use Roadnet Info Center (RIC) Web Component, then choose either Can Use All RIC Components or Can Use Selected RIC Components. If you chose Can Use Selected RIC Components, check Mobile Device Diagnostics.

    Starting Mobile Device Diagnostics

    To start Mobile Device Diagnostics, click the Mobile Device Diagnostics icon.

    Mobile Device Diagnostics opens, showing all your mobile devices.

     

    Arranging the Screen

    You can rearrange and hide columns within Mobile Device Diagnostics so that the information that is most important to you is easily visible. You can also sort the list of mobile devices based on any column, allowing you to change the order in which the devices are listed. If you want only mobile devices that meet certain criteria to appear in the list, you can filter the list of devices based on one or more columns. If you want only mobile devices in certain regions to appear in the list, you can filter by region.

    To move a column to a different position, simply click on the column header and drag and drop it on the new position.

    To rearrange several columns or hide columns, click on the ClosedView Configuration Icon located on the far right side of the screen, next to the column headers. You can select a view configuration or create a new one. Refer to Working with View Configurations for information on using the Edit View Configuration window.

    To change the width of a column, hover over the bar that separates the column's header on the right side. When the cursor changes to a double-ended arrow, drag the bar to make the column wider or narrower.

    To sort the list of mobile devices, go to the upper-right corner in the header you want to sort by. Click on the arrow that appears and select either Sort Ascending to sort from lowest to highest (ABC) or Sort Descending to sort from highest to lowest (CBA). Once the list is sorted, a second arrow is available in the upper-right corner of that column header which will reverse the sort order if selected. If you decide you want to sort by a different column, simply repeat this process on the new column header you want to sort by.

    To filter the list of mobile devices by specific criteria, such as Roadnet Mobile Version, use the field located below the column header you want to filter on. Depending on which column you are filtering on, the filter options are different. If there is more than one page of mobile devices, any filters will apply to all devices across all pages. Click Closedhere for more information about using filters.

    Columns with a single checkbox allow you to filter between two different values.

    Columns with a blank field allow you to enter text to filter on. You can enter just a few characters you want to match. For example, if you enter 4.1 in the Roadnet Mobile Version column filter, devices with a version of 4.1.2B, 4.1.5A, 4.1.7F, etc. would be listed.

    Columns with a blank field and an arrow allow you to enter a numeric value and choose a comparison (equal, not equal, greater than, etc.) that must be met. For example, if you want to see only older equipment with high mileage, you could enter 100000 in the Odometer column filter, then click the arrow and choose Greater Than.

    Columns with a calendar icon allow you filter based on a specific date that must be matched. For example, if you want to see only the devices used today, click the calendar icon on the Last Contact column filter and select the current date.

    Columns with a Select Filter field allow you to click the arrow and choose specific criteria to filter on. For example, if you want to see only the equipment where the engine is currently running, click the arrow on the Ignition column filter and check only On.

    If necessary, you can filter the list of mobile devices by more than one column. Only devices that match all filters will appear in the list.

    A Closedfilter icon will appear on any column header that the list of mobile devices is filtered on.

    If you want to remove all filters, click the [Clear Filters] button.

    Exporting the Mobile Device Diagnostic Information

    There may be times when you want to export your mobile device diagnostic information so that you can manipulate the data and create your own report. You can export the visible information to a csv file.

    To export your information to a CSV file, click the [Export] button. A CSV file containing your Mobile Device Diagnostics information downloads to your computer.

    Notes: Only the information displayed is exported to the CSV file. Device Power information is not exported to the CSV file.

    When exported, all time durations, such as last communication and last known position age are converted to minutes.

     

    Miscellaneous

    Viewing Verification History in Order Status

    Found in Roadnet Anywhere Web

    Order Status in Roadnet Anywhere Web allows you to see a variety of information about an order. You can see the stop that an order is related to, a stop or order signature, if one was collected, the date and time the order was delivered or picked up, you can even see a photo that is related to the order. But, previously you could only see the order quantities for the delivery or pickup. Now, the chain of custody for an order can be viewed in Order Status so that you can see when a worker scans a barcode or enters a quantity manually, throughout the delivery process.

    This information displays in Order Status if a worker scans an order or line item when a route is started, performs a pre-delivery inventory, or enters quantities for the order or line item when a stop is serviced.

    To see the history for an order or line item, search for the order in Order Status. Click on the order to see more information.

    When you collect information at order level, Verification History is part of the order details card.

    When you collect information at line item level, you can see the line items delivered, along with a Verification History column for each.

    Click on View History for the item you want to see. For each action the worker took, you see the date and time, what prompted the action, size 1, 2, and 3 quantities, how the quantity was input, the worker ID, and if available, a quantity reason code associated with the item.

     

    Viewing a Line Item's SKU ID and Description

    Found in Roadnet Anywhere Web

    While working in Route Details you can view an order's individual line items. Previously you've been able to identify the line item by its SKU ID, but if you're working with thousands of SKU's, the number alone may not be very helpful. Now, when viewing a line item in Route Details, you'll see a description of the SKU, in addition to its ID. You'll also be able to see a description when viewing line items in Order Status.

    Giving you the ability to see the ID and description of the actual product rather than a simple SKU ID can help you make decisions for the order, spot any potential mistakes, and keep track of every line item associated with the order.

    To see a line item's SKU ID and Description in Route Details , click the arrow next to a stop in the stop list. A list of the stop's orders will expand below. Drill down further to see the line items included in that order. The line item list will display the SKU ID and description.

    To see a line item's SKU ID and description in Order Status, click the arrow next to the order. Information about the order will expand below, including any line items. The line item list will display the SKU ID and description.

     

    Dispatching

    Monitoring the Amount of Fuel Used for a Stop

    Any transportation manager knows that one of their major expenses is fuel, including the amount of fuel used at a stop. This can be particularly important if your trucks are running PTOs, such as cement mixer. To help monitor the fuel used at stops, two new columns have been added to the stop list - Fuel Used and Fuel Used To. Fuel Used displays the amount of fuel used while the vehicle is at the stop, while Fuel Used To displays the amount of fuel used from the previous stop to the current stop. Both amounts are calculated using the Liquid Volume unit selected for the business unit.

    In Roadnet Anywhere Web

    In FleetView, select a route, then go to Route Details for the route. Scroll across the stop list to find the Fuel Used and Fuel Used To columns.

    Note: To see the Fuel Used and Fuel Used To columns, you may need to scroll or even update your view configuration. To update the view configuration, click on the View Configuration icon to open the Edit View Configuration window, where you can change the column order or restore hidden columns.

    In Roadnet Anywhere Client

    Click on Dispatching, then Route Dispatching to open the Dispatching manifest. Double click on the route to open the stop list. Scroll across the stop list to find the Fuel Used and Fuel Used To columns.

    Note: To see the Fuel Used and Fuel Used To columns, you may need to scroll or even update your view configuration. To update the view configuration, right click on a column in the stop list, then click on the Edit icon to open the Edit View Configuration window, where you can change the column order or restore hidden columns.

     

    Cancel, Uncancel, and Unassign Orders on Planned Stops

    Found in Roadnet Anywhere Web and Roadnet Anywhere Client

    In the world of a dispatcher, things can change very quickly. There may be times when big changes need to made to an order, while the route is already underway. For instance, if you're contacted by a customer and find out that an order needs to be canceled or if complications with a driver require you to unassign an order from a route, you'll need to make adjustments to your routes as soon as possible. Roadnet Anywhere now gives you the ability to make these kinds of changes right from the stop list. You can simply right click on an order and select Cancel or Unassign, and if things continue to change, you can even uncancel an order in the same way. This new functionality gives you the complete ability to quickly edit an order even after it has been dispatched.

    To Cancel, Uncancel, and Unassign orders in Roadnet Anywhere Web

    Go to the stop list and drill down until you find the order you want to edit. You can use the arrows to see which line items are included in the order.

    To cancel an order, right click on the order and select Cancel Order. Canceled orders will appear with a line through them.

    To unassign an order, right click on the order and select Unassign Order.

    To uncancel an order, right click on the order and select Uncancel Order.

    To Cancel, Uncancel and unassign orders on the Stops Window in Roadnet Anywhere Client

    Change your view to Dispatching, if necessary. Select a route, then select a stop. The orders associated with that stop will appear in the orders window.

    Note: If you are using line items, you can click on an order to view or edit its line items..

    To cancel an order, right click the order and select Cancel Order. A canceled order will appear with a line through it.

    To unassign an order,right click the order and select Unassign.

    To uncancel an order, right click on the order and select Uncancel Order.

    Click the Save button.

     

    Compliance

    Working with Compliance Alerts

    Found in Roadnet Anywhere Web

    As a Compliance customer, it is essential to track all of your driver's HOS information. If you've got multiple drivers, that can be overwhelming. Roadnet Anywhere now allows you to create compliance alerts for your drivers, so that you will be notified of an HOS violation. For instance, if one of your dozens of drivers is starting to approach low drive time, and both you and the driver are occupied by your day to day activities, a low drive time alert can be sent so you can get that driver off of the road. You are able to customize the priority and frequency of each alert and can chose which alerts you want to use and which regions or drivers those alerts will apply to.

     

    HOS Driver Payroll Summary Report

    Found in Roadnet Anywhere Web

    For Compliance customers, the Driver Payroll Summary report can be used by managers and supervisors to review and monitor drivers' time and attendance. Selected driver's daily hours, from clock-in to clock-out, are combined and displayed as one total for a selected time period. The report also shows on duty time, off duty time, driving time, and distance to give you a snapshot of a driver's activity during whatever time period you chose. You can even schedule the Driver Payroll Summary Report to run automatically daily, weekly, or monthly, to ensure that the right users are receiving this important information on a regular basis.

    Granting Permission to use the HOS Driver Payroll Summary Report

    The Driver Payroll Summary Report is very useful for managers and supervisors who need to keep track of driver information. You can grant specific roles permission to use the Driver Payroll Summary Report to a role in the Administration module.

    Go to Administration and select Roles.

    To add a role, click the [Add] button. The Add Role window will appear.

    To edit a role, click the edit icon. The Edit Role window will appear.

    Click the Compliance Permissions tab and check Driver Payroll Summary Report.

    Click [Save].

    Running the HOS Driver Payroll Summary Report

    Go to reporting and select Driver Payroll Summary Report. The options for the report will open.

    To filter by region, go to the Organization field and click [Select]. You can select one region, multiple regions, or all regions. You must make a selection.

    To filter by resource group, go to the Resource Group field and click [Select]. You can select one resource group, multiple resource groups, or all resource groups.

    To filter by driver, go to the Driver field and click the list icon. Select which drivers you want the report to include. You can select one driver, multiple drivers, or all drivers.

    To select a start and end date for the report, go to the start date and end date fields, click the calendar icon to select a date or enter a date in MM/DD/YY format.

    Note: The end date will default to the current date, the start date will default to six days prior to the current date.

    To filter the report by shift, go to the Shift Based field and select Yes.

    To filter the report by calendar day, go to the Shift Based field and select No.

    Click [Generate Report] to generate the report.

    The Report will display the driver ID, driver's name, date, check in time, on duty hours, driving hours, off duty hours, check out time, total hours, distance, and activity.

    Use the arrows to navigate the different pages of the report or the search bar to find specific information.

    If you want to export the report, click the export icon and use the arrow to select PDF, Word, Excel, or CSV.

    If you want to print the report, click the print icon.

    Scheduling the HOS Driver Payroll Summary Report

    To help you save time, you can schedule the HOS Driver Payroll Summary to be automatically generated and emailed to designated users on a regular basis.

    Once you have opened Reporting, click Schedules at the top of the screen.

    To add a new report schedule, click the [Add] button.

    To make changes to an existing report schedule, click on the Edit icon next to the report schedule.

    In the Report field, click the arrow and select HOS Driver Payroll Summary Report. Enter a Description that will help you identify the report.

    In the Schedule field, click the arrow and select whether the report will be generated and emailed on a daily, weekly, or monthly basis. Use the Day field to designate which day of the month, day of the week, or time of day the report will be generated. Click the Reporting Period arrow and choose to run the report based on the previous day, the previous week, or the previous month.

    To select which users will receive the report, click [Select]. The Select Users window will open. Use the arrows to place users on the Included or Excluded lists. Click [Save] to close the Select Users window.

    Click the Select Region bar to select the regions that you want to include on the report when it is generated.

    Note: You cannot create a report schedule for a report that has multiple regions selected; you must create a separate schedule for each region of the report.

    Click [Save].

    New Location Option in Driver Log Editor and UVA Editor

    Users now have a new location choice when they insert driver log events using the Driver Log Editor or UVA Editor. In addition to Site, City, and Free Input, you can now choose Default Reporting Site (as long as the driver has a default reporting site). When you select this option, the Site field automatically fills with the driver’s default reporting site. The field is not editable.

    If the driver does not have a default reporting site, the Default Reporting Site option does not appear. If you switch to a different Location option, the default reporting site is removed.

    The default reporting site is also reflected in the Driver Log Report and ELD Driver Log Report.

    The Default Reporting Site ensures that drivers will be compliant when they use Big Day or Short Haul exemptions.

    Big Day/Short Haul Validation in Driver Log Editor and UVA Editor

    The Driver Log Editor and UVA Editor now use the driver’s Default Reporting Site to determine whether the driver is eligible to use the Short Haul or Big Day exemptions.

    For Big Day validation, users will receive a warning message if the start and end locations of the five duty tours prior to Big Day being declared are not within a 0.5-mile radius of the driver’s Default Reporting Site.

    • If there are fewer than five previous duty tours, the Big Day exemption will be available for the driver.

    • If there are at least five previous duty tours but the start or end location of any of them cannot be identified, the user will receive a message warning that the locations are not available and that the user needs to verify that the driver is eligible for Big Day.

    The validation process is similar for Short Haul. When users save log edits, they will receive a warning if the start and end locations of the duty tour where Short Haul was declared is not within a 0.5-mile radius of the driver’s Default Reporting Site.

    In both cases, users can still save the log edits even if they receive a warning message.

 

Roadnet Mobile

Viewing Contact Names when Collecting Signatures

Found in Roadnet Mobile for Android

Roadnet Mobile now displays a contact name and alternate contact name for a service location when the worker is collecting a signature or verifying an order. The names can also be seen with the stop details. This information helps the worker determine if the proper person is signing for the delivery or ensuring that the alternate contact's signature is collected if the primary contact is unavailable.

If the contact and alternate contact information exists for the service location in Roadnet Anywhere it will display in Roadnet Mobile.

 

Collecting an Image as Proof of Delivery

Found in Roadnet Anywhere

It is always nice to have more information than you need rather than not enough when it comes to proving a delivery was made. The problem comes in when you require a signature or consignee, but the customer is not available. The worker must collect that information before the stop can be departed. If you let your workers use the Signer not available box when a signature or consignee cannot be collected, you are trusting that the package was left in a spot where the customer can find it. Now, you can require that a picture be taken of the delivery, if the worker marks that the signer was not available. If the worker doesn't provide an image, the stop cannot be departed. Snapping a quick picture gives you one more piece of information for proof of delivery, when leaving a package for a customer without collecting a signature.

When the worker takes a picture for proof of delivery, it is sent back to Roadnet Anywhere Web and can be viewed in Order Status.

Requiring a Delivery Image

To require the worker to take a picture when the Signer note available box is checked, do the following:

In Roadnet Anywhere Web

Click on the Administration icon to open Administration. Click on the green button and scroll to Regions. The Regions list opens.

To add a new region, click the Add icon. To edit an existing region, find the region you want to change and click the Edit icon. The Add/Edit Region window opens.

Check the Delivery Image Required when Skipped box to require the worker to take a picture of a delivery when a signature or consignee cannot be collected.

Note: The Allow Worker To Skip Consignee/Signature box must be checked for this option to be available. The Consignee Required and/or Signature Required box must be checked to make taking the picture a required action.

Make any other necessary changes and click Save.

In Roadnet Anywhere Client

Click the Administration menu and select Regions, or click the Regions icon. The Regions list opens.

To add a new region, click the New item icon. To edit an existing region, highlight the region you want to change and click the Edit icon. The Add/Edit Region window opens.

Check the Delivery Image Required when Skipped box, to require the worker to take a picture of a delivery when a signature or consignee cannot be collected.

Note: The Allow Worker To Skip Consignee/Signature box must be checked for this option to be available. The Consignee Required and/or Signature Required box must be checked to make taking the picture a required action.

Make any other necessary changes and click Save.

Collecting a Delivery Image on the Mobile Device

In Roadnet Mobile for Android

On the mobile device, when the worker opens the Signature screen, what the worker sees depends on how you set the region options. If you don't allow the worker to skip the required Consignee/Signature, then only the photo icon displays. The worker can take a photo from the Signature screen, even if a signature is not required.

When a signature or consignee is required and you allow the worker to override the requirement, the worker sees both the Signer not available box and the photo icon. If you set up the region to require the worker to provide an image when the Signer is not available box is checked and the worker checks the box and then returns to the Signature list, the worker is prompted that an image is required.

If the worker does not return to the Signature screen and take the picture, the worker cannot depart the stop. To take the picture, the worker simply presses the Photo icon, takes the pictures, and presses OK. A thumbnail of the image displays on the screen. If the worker wants to re-take the picture, simply press the Photo icon again and take a different picture.

Note: The worker cannot attach an image that has already been taken. The picture must be taken at the time that the Photo icon is pressed.

 

Preventing Workers From Resequencing Stops

Found in Roadnet Anywhere

You've enabled resequencing for your workers because you want them to be able to move stops around on the route as they need to. But, some workers either don't make wise moves or are too inexperienced to make the proper moves on a route.

You can now give individual workers permission to resequence stops. If you want to require new workers to be with the company for three months before being able to move stops around on the route, or if some workers just shouldn't have that kind of responsibility, you can choose to turn off stop resequencing for those specific workers.

To manage permission for each worker, you must first enable the Resequence Stops region option in Administration. This gives all workers the ability to resequence stops. Then, go to Workers setup in Maintenance and for any worker you don't want to have the ability to resequence stops, uncheck the Enable Stop Resequencing box. Those specific workers will no longer have permission to move stops around on the route.

Note: The Resequence Stops region setting in Administration must be enabled for the new option to work. If the region option is not turned on, the new Enable Stop Resequencing setting will be ignored and no workers will be able to resequence stops.

In Roadnet Anywhere Web

Click on the Maintenance icon to open Maintenance. Click on the green button and scroll to Workers. The Workers list opens.

To add a new worker, click the Add icon. To edit an existing worker, find the worker you want to change and click the edit icon. The Add/Edit Worker window opens.

To turn off the ability for a worker to resequence stops, uncheck the Enable Stop Resequencing on the Worker Details tab. Make any other necessary changes to the worker's settings and click Save.

In Roadnet Anywhere Client

Click the Maintenance menu and select Workers, or click the Workers icon. The Workers list opens.

To add a new worker, click the New item icon. To edit an existing worker, highlight the worker you want to change and click the edit icon. The Add/Edit Workers window opens.

To turn off the ability for a worker to resequence stops, uncheck the Enable Stop Resequencing box on the Standard Properties tab. Make any other necessary changes to the worker's settings and click Save.

 

Sharing Mobile Forms to Specific Regions

Found in Roadnet Anywhere Web

Currently, when you create mobile forms, they are created for the entire business unit. The list of forms can become extremely long when you are seeing forms for every region in the business unit. Now, rather than everyone see all the forms that have been created you can choose which regions see specific forms. Each region will only see the forms that are assigned to them, rather than the complete list.

To see a mobile form across all regions, when creating or editing a form in Mobile Workflow, ensure that the Shared To All Regions box is checked.

To see a mobile form in specific regions, when creating or editing a form in Mobile Workflow, uncheck the Shared To All Regions box. In the list that displays, check the box next to the region(s) you want included or check the box above the list of regions to select all the regions. You can then go through the list and remove the check from any regions you do not want included. To sort the region list by ID or description, click the ID arrow and choose how you want the list sorted. To search for a region in the list, start typing the region ID or description in the search box. The list narrows to show regions that start with the text you've entered.

Note: The default setting is Shared To All Regions.

Viewing A Delivery Image in Order Status

In Roadnet Anywhere Web Order Status

When the worker takes a picture for proof of delivery, it is sent back to Roadnet Anywhere Web and can be viewed in Order Status. Search for and show the details of the order in Order Status. Then, press Stop Proof of Delivery or Order Proof of Delivery to see the image that was collected.

 

 

Scanning Items to Locate a Stop

If your trucks are packed full when they leave the warehouse and workers are delivering to multiple customers in a building, it can be difficult to match an order/line item with the proper stop when it is time to pull items from the back of the truck. An enhancement to the scanning feature now allows the worker to scan a unique barcode for an order or line item and have Roadnet Mobile match that order with the stop to which it belongs. The worker can then decide if that order will be delivered next or if another order is more appropriate to deliver.

If the worker is on an in transit screen and scans an order or line item barcode, a prompt displays stating which stop the item is part of and if that stop is not the next stop on the route, asks if the next stop should be changed to the one associated with the item. If the worker answers yes, the route changes and the worker is redirected to the new next stop.

If the worker has already arrived at a stop and scans an order or line item barcode, a prompt displays asking if the worker wants to create a group stop. If the worker answers yes, the Select Stops in Group screen displays, with that stop selected.

If the worker is already servicing a group stop, the prompt asks if the stop should be added to the current group. If the worker answers yes, that stop is added to the current group stop.

If the worker answers no to any of the questions, the scan is discarded and the worker can scan another barcode or continue the route as it is.

Notes: Barcodes must be unique for each order or line item, otherwise the ability to find the correct stop will be unpredictable.

The Check-Off Scanning or Increment Scanning option must be turned on in Roadnet Anywhere Administration.

To find a stop by scanning a barcode, the worker must be on the In Transit, At Stop, or At Group Stop screen.

 

Specifying To Whom A Route is Tendered

Found in Roadnet Mobile for Android

When a route tendered message shows up on your driver's mobile device, it simply states that there is a route tendered to "you" and the accepted and declined lists do not specify the name of who has accepted or declined the tendered route. For more clarity, names of drivers are now visible in tendered route notifications and in the accepted and declined area of the Tendered Routes list on the mobile device.

 

Roadnet Mobile Manager

Filtering the Workers List by Duty Status

Found in Roadnet Mobile Manager

On the Workers tab in Roadnet Mobile Manager, you can see the duty status alongside the worker's name as well as the duty time that remains for the worker, if the information is available.

So that you can focus on only those workers that have a specific duty status, such as driving or sleeper berth, now you can filter the workers by duty status. To filter the workers list to see information for a specific duty status, press the Filter icon, then toggle each duty status on or off, depending on if you want to include it in the Workers list. Press Apply to update the information on the Workers tab.

This information is only available for Compliance customers.

Sorting the Workers List by Duty Time Left

Found in Roadnet Mobile Manager

When viewing the Workers tab in Roadnet Mobile Manager, you may need to look at your workers list in a different sort order to make better use of the data. Previously you were only able to sort by worker ID or name. You can now sort by Duty Time Left.

This information is only available for Compliance customers.

Marking Items as a Favorite

Found in Roadnet Mobile Manager

If you have new employees and want to keep an eye on how they are doing out in the field or if there is a piece of equipment that you need to keep track of, you realize that searching through a list of workers or equipment can take time. Filters, although they limit the list, don't make it simple and quick to find that new worker three or four times a day when you are reviewing workers and their routes.

You can now mark a worker, piece of equipment, or a route as a favorite. When an item is marked as a favorite, it is placed at the top of the list, making it quick and easy to find. Your favorites also show at the top of the equipment list that displays when you tap on the Fleet Overview map.

Note: Roadnet Mobile Manager favorites do not carry over to Fleetview.

To mark an item as a favorite, press the Favorites icon.

Note: When using an iOS mobile device, you can swipe the screen to the left to mark an individual item as a favorite.

Press the star next to the item(s) you want to mark as a favorite and then press Apply.

Note: You can mark as many items as you need as a favorite.

You are returned to the list and your favorites are displayed at the top with a favorites star.

Acknowledging Exceptions

Found in Roadnet Mobile Manager

Previously, you were only able to view exceptions in Roadnet Mobile Manager. Although you could filter your exceptions so the list only displayed a specific one or only showed unacknowledged exceptions, you still had to return to Roadnet Anywhere to acknowledge exceptions. Now, you can acknowledge exceptions in Roadnet Mobile Manager.

To acknowledge an exception, press the Acknowledge icon on the Exceptions screen. A list of unacknowledged exceptions displays.

Note: If you filter your list and then press the Acknowledge icon, the list only displays the unacknowledged exceptions that meet the criteria of your filter.

Press the exclamation point next to any exception(s) you want to acknowledge. The exclamation point changes to a check mark, indicating it has been acknowledged.

Press Acknowledge Selected. The updated Exceptions list displays.

Note: You may be able to swipe the screen to the side to acknowledge an individual exception.

Filtering Cancelled Orders

Found in Roadnet Mobile Manager

On the Cancelled Orders tab in Roadnet Mobile Manager, you can see information about a cancelled order. So that you can more easily find a cancelled order that you are looking for, new filters have been added. You can now filter the Cancelled Orders list by who cancelled the order, the dispatcher or the driver, and the reason it was cancelled.

To filter the Cancelled Orders list so that you see orders that were cancelled by a specific source, press the Filter icon. Then, toggle each Cancel Source on or off, depending on if you want to include it in the Cancelled Orders list. Press Apply to update the information on the Cancelled Orders tab.

To filter the cancelled order list so that you see orders that were cancelled for a specific reason, press the Filter icon and then press the arrow next to Order Cancel Reason Codes or Stop Cancel Reason Codes. To see all cancelled orders in the list, toggle Select All on; all cancel reason codes are selected. To see orders assigned to a specific reason code, toggle Select All off, and then turn on all the cancel reason codes that you want to view information for.

Press Apply to update the information on the Cancelled Order tab.

Note: You can filter the cancelled orders list by the stop reason code that was assigned when a stop is cancelled, resulting in a cancelled order.

Filtering Routes by Route State

Found in Roadnet Mobile Manager

You can quickly see how your routes are doing for the day on the Route tab in Roadnet Mobile Manager. But if you have a lot of routes, the list can become overwhelming and hard to analyze. So that you can more easily find those routes you are looking for, a new filter has been added. You can now filter the Routes list by the state of the route, such as pending, at a stop, at a break, or completed.

To filter the Routes list so that you see routes that are in a specific route state, press the Filter icon. Then, toggle each Route State on or off, depending on if you want to include it in the Routes list. Press Apply to update the information on the Routes tab.

Using the Legend to Decipher the Map

Found in Roadnet Mobile Manager

When you look at the map, you will notice that there are different shapes and colors representing stops on the map. Each shape and color represents a different phase and arrival for a stop. To see what the different shapes and colors mean, on the Show on Map screen, press the Legend icon to open the legend.

The legend displays all the icons that might display on the map and what they mean. A square icon means the stop is pending while a circle icon means that the stop is complete.

Colors on the map represent the arrival of the stop. If the icon is blue, the worker arrived on time, green means early, and red indicates the worker arrived late.

Viewing Diversion and Restricted Stops

Found in Roadnet Mobile Manager

There are a variety of stop types that can be part of a route, this includes delays, reloads, unknown stops, diversions, and restricted stops. Previously, diversion and restricted stops were displayed as unknown stops in Roadnet Mobile Manager. Now, to enhance the information that is provided, these stop types have been split out from unknown stops. You can now see the amount of time that was spent at a diversion or restricted stop on the stop list. The amount of time does not include the time spent idling at the stop.

Diversion and restricted stops also display on the route map. The map legend shows you the icons that represent diversion and restricted stops on the map.

Update to iOS

Found in Roadnet Mobile Manager for iOS

To make Roadnet Mobile Manager for iOS look and act more like other iOS applications, the call feature on the Workers tab has been moved to a slide menu. Now, while you are on the Workers tab, if a phone number exists for a worker, simply swipe the screen to the left to see the Call Worker action. Tap it to call the worker.

 

 

Centralized Messaging

Changing Read Messages Back to Unread

Found in Roadnet Anywhere Web

When you click on the condensed view of a message in Centralized Messaging, the complete message displays and the message is marked as read. This means that the blue dot beside the message changes to white, and the number beside the Inbox folder and on the Inbox icon reduces by one. But, you may want to use the Read status of your Inbox messages to indicate that you've completed a task that is contained in the message. If the message is unread, you are more likely to reread the message or keep track of the task that is included in the message.

You can now mark messages in your Inbox as Unread. This allows you to view a message and get the details, and then mark the message as unread. Each time you visit the Inbox, the unread message can be viewed and marked as unread again or left as read.

To mark a message as unread, after clicking on and reading a message, simply press the [Mark As Unread] button.

When a message is marked as unread, the dot beside the message in the condensed view reverts to blue and the number beside the Inbox folder and the Inbox icon increment by one. This indicates that there is an additional unread message in the Inbox.

 

Rearranging the Order of Folders

Found in Roadnet Anywhere Web

For ease of use, the folders in Centralized Messaging have been rearranged. You will notice that the Inbox has been moved to the top of the folder list, while the Route Notes folder has been moved to the bottom. There is now a dividing line between the message folders and the Route Notes folder, indicating that they are separate types of correspondence.

 

Telematics

Entering a Vendor When Completing a Performed Service

To help keep your records accurate, while entering a performed service in Equipment Maintenance Planning you can now identify the vendor. This new field is optional, but it can be useful if you need to know who performed a service. For instance, if there is an issue with the services performed or if you need contact information for billing or other paperwork.

Go to Equipment Maintenance Planning.

Click the [Enter Performed Service] button, the Enter Performed Service window will open.

 

Disabling Auto Assignment of Telematics Routes

Found in Roadnet Anywhere

If you use Telematics devices with auto arrival and depart, you can choose to have your routes automatically assigned based on equipment or worker. But, if your workers use Roadnet Mobile, you may want to allow them to select a route from a list of available routes. You can now choose to disable the auto-assignment of routes entirely so that workers can select the route in Roadnet Mobile. If your workers use Roadnet Mobile, this will let them choose which route to load, from a list on the mobile device.

Notes:Route Assignment Mode has been renamed Route Auto-Assignment Mode.

If you choose Disabled as the Route Auto-Assignment Mode, the worker must select a route in Roadnet Mobile to load a route on the mobile device.

To disable auto assignment of routes to Telematics devices, do the following:

In Roadnet Anywhere Web

Click on the Administration icon to open Administration. Click on the green button and scroll to Regions. The Regions list opens.

To add a new region, click the Add icon. To edit an existing region, find the region you want to change and click the Edit icon. The Add/Edit Region window opens.

On the Telematics page of the Auto Arrive/Depart tab, press the Route Auto-Assignment Mode arrow and choose Disabled.

Make any other necessary changes and click Save.

In Roadnet Anywhere Client

Click the Administration menu and select Regions, or click the Regions icon. The Regions list opens.

To add a new region, click the New item icon. To edit an existing region, highlight the region you want to change and click the Edit icon. The Add/Edit Region window opens.

On the Auto Arrive/Depart tab of the Dispatch Settings page, under Route Auto-Assignment Mode, choose Disabled.

Make any other necessary changes and click Save.

 

Routing

Using the Total Order Quantity When Filtering Orders for a Pass

When you create routes in Roadnet Anywhere, you can choose to include or exclude orders based on different criteria, including the quantity of product the order contains. But, in the past, if you used combine orders to make sure that all orders for the same service location were considered together, Roadnet Anywhere did not use the total combined order quantity when filtering the orders for the pass. Now, if you are using combine orders, the total quantity of all the orders will be considered when determining if the orders meet the criteria for the filter. To reflect this change, the label on the Filter page of the Pass Template notebook has been updated to say Total Order Quantity.

To create a filter for orders, click on Routing, then Routing Pass Templates; the Routing Pass Templates list opens. Click the Add icon to add a new pass template, or select a template and click the Edit icon to change an existing template. The Routing Pass Templates notebook opens. Click on the Filters tab to open the Filters page, then click on Include Filters or Exclude Filters. Enter the Total Delivery Quantities or Total Pickup Quantities for the orders to be included in or excluded from the pass. Complete the remaining filters and pass options, then click the [Save] button. When routes are created, the total quantity for all orders for the service location will be considered when determining if those orders meet the filter critera.

 

Viewing the Order Class for Unassigned Orders

Found in Roadnet Anywhere Client

When looking at your unassigned orders, you may need to know what classifications the order falls under to decide which route to place it on. Order classes can be created to cover a number of categories and topics, such as DEL (Delivery), FZN (Frozen), MER (Merchandiser), or DRY (Dry/Grocery). Your order may have a product that you want a merchandiser (MER) to place in a certain spot at a customer location. An order class can be used to bring attention to the order. In Roadnet Anywhere Client, you can now see the order classes information when viewing unassigned orders. This will give you more information when trying to place an unassigned order on a route.

Notes: If there is an Order Group, all order classes for all orders in the group appear.

You may need to add the column to your view configuration so you can see it.

The Order Classes column displays the unique ID and/or description of the classification associated with the unassigned order. You can choose if the ID and/or description of the order class will be shown in the column on the General page of the Options notebook on the Tools menu.

Note: You must recalculate to get the order class to show for existing orders.

 

Enhancements to Send Orders

Found in Roadnet Anywhere Client

After you have created routes, you may want to use Send Orders to copy the route information so that other parts of your organization have access to the information. Send Orders lets you select the information that you want to include when you send the routing information. There have been a couple of enhancements that make Send Orders

  • You can have the routes' phase when the order information is sent.
  • You can include the files names as the first row in the file that is created.

Changing the Routes' Phase when Sending Orders

Once you have created your routes and used Send Orders to send the routing information to other parts of your organization, you may need to keep track of which routes have already been sent, and which ones still need to be sent. An easy way to do this is to simply have the routes moved to a different phase after they are successfully sent, so they are no longer in your list of active routes. Now, you can choose to have Roadnet Anywhere automatically move the routes to a different phase once they have been sent using Send Orders.

Click the Tools menu and scroll to Send Orders, or right-click on a selected route and choose Send Orders. The Send Orders tab opens. If necessary, choose the routes that you want to send. In the Route Phase After Send box, uncheck Keep Current Phase/Status, then choose the phase you want the routes moved to.

Some considerations when choosing the destination phase:  

Move to Plan - Built - the routes can not be loaded onto devices

Move to Dispatch - the routes are currently in Plan status

Move to Archive - the routes can not be loaded onto devices

 

Notes: Routes will not be moved to a different phase unless you have permission to modify routes.

Only routes that are successfully sent will change their phase.

 

Including the Field Name when Sending Orders

Send Orders lets you communicate a lot of detailed information about your routes throughout your organization. But, it can be difficult to match the data in a column with what it actually represents. Now, you can choose to have Roadnet Anywhere include the field names as the first in the files created when orders are sent.

Click the Tools menu and scroll to Send Orders, or right-click on a selected route and choose Send Orders. The Send Orders tab opens. If necessary, choose the routes that you want to send. Check Include Fields Names as First Row.

Note: This option is only available if you are creating a csv or delimited file.

 

Sequencing Stops Before and After Mid-Route Depots

Once Roadnet Anywhere creates routes, you may need to add stops to handle last minute orders, or even transfer stops between routes to handle special situations. Roadnet Anywhere provides many tools to help you with evaluating and updating the routes, including the ability to sequence the stops on the route based on reducing cost, the pass options, or meeting service windows. But, what if there was a reload depot on the route that you did not want moved when the route was re-sequenced? Now, you can have Roadnet Anywhere treat the stops on each side of the reload depot as a complete trip, and re-sequence each trip independently, while keeping the reload depot in place.

Note: Sequence By Trip is only available on Plan - Active routes.

To sequence the stops on the trip, right-click the routes you want to re-sequence and select Sequence by Trip, then choose By Cost, By Service Window, or Using Pass Goals. Each trip on the route is re-sequenced, but the mid-route depot is not moved.

 

Reports

Choosing Today as a Reporting Period

Found in Roadnet Anywhere Web

Scheduling reports to run automatically saves you time and effort. When you schedule a report, you define how often the report is generated, the format the report is presented in, and who to email the report to. You can also specify the reporting period for the report. Previously, you could only include information for yesterday, the previous 24 hours, last week, this week, the previous 7 days, last month, and this month. Now, you can also run reports with a reporting period of today.

When you generate a report for today, it will include data beginning at midnight (00:00) up until the current moment.

Note: Not all reporting period options are available for every report.

 

Viewing the Region ID and Description on a Report

Found in Roadnet Anywhere

If you have multiple regions, it is difficult to know from which region the report came, because there is no region information on the report. For single region based reports, the Region ID and Region Description have been added to the header of the report, so that you can easily tell what region the information came from.

 

Updates to the Driver Log Report

The Driver Log Report has the following updates:

  • The vehicle ID is displayed in the header of the co-driver's log for all the days the vehicle was associated to the primary driver.
  • The driver's name now appears beneath the signature line in the report.
  • Start and end odometer values included in the Detail column for Personal Conveyance events if the Personal Conveyance started or ended in Canada.

 

HOS Updates

For drivers using Texas Intrastate rules or Texas Oilfield rules, periods of Off Duty time or Sleeper Berth will not count against their 15-hour duty period. Instead, the 15-hour duty period will be extended by the time the driver took off during the Off Duty or Sleeper Berth period.

 

Web Services

Subscribing to Events for Web Services

If you are using the REST APIs to retrieve information from Roadnet Anywhere, you may want to gather information about when your drivers arrive at a stop, start servicing a stop, or other events that happen throughout a route. Now, you can easily select the events that you want to be able to retrieve through the APIs. The events you can subscribe to are:

Route

Status Change - the route has changed it status from plan to dispatch, plan active to plan built, or from pending to loaded.

Started - the worker has started the route

Departed - the worker has departed the origin

Arrived - the worker has arrived at the destination

Completed - the worker has completed the route

 

Stop

Arrived - the worker has arrived at the stop

Servicing - the worker has started servicing the stop

Departed - the worker has departed the stop

Cancelled - the stop has been cancelled

 

Worker

Login Status Changed - the worker logged into, or out of, the mobile application.

 

In Roadnet Anywhere Web

In Administration, click on the green button and scroll to Event Subscriptions; the event subscriptions list opens. Click the Add button to add a new subscription, or click the Edit icon to edit an existing subscription. The Event Subscription window opens.

Enter an ID and a Description.

In the Subscriptions area, check the events you want to be able to retrieve.

 

In Roadnet Anywhere Client

Click on the Administration menu and scroll to Event Subscriptions. The Event Subscription list opens. Click the Add icon to add a new subscription, or select an existing subscription then click the Edit icon. The Event Subscription window opens.

Enter an ID and a Description.

In the Subscriptions area, check the events you want to be able to retrieve.

 

Navigation

Using Waypoints to Help Specify a Trip

Waypoints are geographical points the driver wants to pass through on their way to a destination. Waypoints differ from stops. Stops represent places where the driver stops moving and performs some activity. Activities might include delivering product, dropping a truck load, filling up for gas or eating lunch. In each case, the driver will remain at the stop for some period of time. By contrast, waypoints are pass through points. They are directional guides that help navigate the driver in a particular direction without the intention of stopping. Waypoints are a good option if a road is under construction for the week or as a way of bypassing roads near a sporting venue during a major sporting event.

Waypoints show in the trip listing. When the driver passes near the waypoint, Navigation notifies the driver the waypoint has been passed and proceeds to navigate to the next waypoint or final destination. If the driver passes a waypoint but is too far away for automatic detection, the driver can select SKIP WAYPOINT. Navigation will then move on to the next waypoint or final destination.

Waypoints show on the map and the trip list. Waypoints that have been passed are indicated with a green check mark. Those that are skipped are noted with a red X.

For customers using Direct TMS Integration, waypoints can be included along with the destination in the integration from your TMS.

 

Alerts Regarding Path Settings

Navigation has allowed you to specify path settings that help determine the path that the driver should take. For instance, you can say that the driver should avoid dirt roads, or even toll roads. However, if it was unavoidable, the path would violate the settings and take the dirt road or toll road. Now, if this happens, the driver is alerted to the violation and can see which path setting was broken.

When the driver's path is obeying the path settings, there is a green flag icon to indicate no violations have occurred.

If a violation has occurred, the flag icon turns from green to orange, and the driver receives an audio alert. If the driver presses the orange flag icon, a window opens indicating which path setting was violated.

 

 

Software Corrections

The following software corrections were made in Roadnet Anywhere 5.5.

Item Read Me Notes
  Compliance
RA-39439 Previously, selecting links on some Compliance reports would give the user access to the backend system. This has been corrected.
RA-35044 For Compliance customers, deleting a Telematics device that was assigned to a piece of equipment could cause problems. Now, deleting a Telematics device will now remove the association to the equipment as well as unassign it from the customer.
RA-39866 Compliance customers are no longer required to enter the city, state and country when entering the region's HOS address.
XRS-3164 The ELD Driver Log Report was not showing the last duty status of the co-driver. This has been corrected.
XRS-4375

The description of Paper Log Mode in the Diagnostic and Malfunction Detail Report, which currently says "Other ELD detected malfunction" has been changed to the more specific "Other ELD (Bleutooth) malfunction."

XRS-4424 Canadian DVIR requires that data be retained for 6 months for inspections with no defects and 24 months for inspections with defects. The Certify Repair tool, however, only retained data for 3 months prior to the current month. Now records are retained for up to 24 months prior to the current month.
XRS-4450 The value for the Unidentified Driver Profile even "Elapsed Engine Hours" in eRODS extracts sent from the host did not match the value in extracts sent from the mobile. This issue has been resolved.
XRS-4808 Shipping information in the header of the ELD Driver Log Report was not being carried over to the second day of the report. This issue has been resolved.
XRS-6301 Official reports sometimes showed multiple rows for jurisdictions that have no surcharge taxes. This has been corrected.
XRS-7267 If you added an event n the Driver Log Editor for a time before or after the last duty ot status event, the changes wee not updated in the database, which meant that sometimes violations did not get recorded correctly. This issue has been resolved.
XRS-7552 If an ELD login occurred on day 1 and logout occurred on day 2, with several events occurring in between, some of those events were duplicated in the eRODS when it was run for both days. This has been corrected.
XRS-11979 The information on the Performance dashboard, which was not being updated for some customers, is now showing current data and getting updated as designed.
XRS-12331 When a vehicle is moved to a new region, the OFTA Reconciliation Report displayed duplicate rows. This has been corrected.
XRS-12643 Some users were unable to edit duty status events in the Driver Log Editor; when they selected the pencil icon net to a duty status event, they received an error message instead of the Edit Duty Status window. This has been corrected.
XRS-12716 An issue that prevented Adverse Weather extensions from appearing on a driver's log has been corrected.
XRS-12859 If two drive time segments were reassigned to the same driver, the changes could not be saved. This has been corrected.
XRS-12951 An issue that caused eRODS extracts to fail if they wre generated for multiple days has been resolved.
XRS-12982 An issue that caused co-driver details not to appear in the eRODS extract has been resolved.
XRS-13083 The User List section in the eRODS extract should be populated with all drivers who had a drive time within the specified date range, but this was not happening consistently. This issue has been resolved.
XRS-13226 When drive time was reassigned from one driver to another, and both drivers accepted the changed, the reassigned time was still showing up as pending in the Driver Log Editor, although the mobile log editor was updated as expected. This has been corrected.
XRS-13284 If the user was using a version of the Scheduler mobile app that was older than 5.20.0130, the header in the eRODS extract was missing the ELD ID, which caused the extract to fail. This has been corrected.
XRS-3449 If the Relay rebooted during a UVA event, the UVA editor erroneously listed duplicate drive events. This has been corrected.
XRS-3465 An issue that caused HOS to be calculated for active drivers in inactive companies has been resolved.
XRS-3712 The HOS system sometimes attempted to calculated HOS for drivers who do not use an HOS rule set. This has been corrected.
XRS-4174 An issue that caused the Relay Inventory Report to show duplicate relays has been corrected.
XRS-4345 The Rejected Edits report was generating a "Sync was generate report failed" error message and not returning any data. This has been corrected.
XRS-4636 When the date range for the Formatted IFTA extract report was set to the current month, the results row included a row from the subsequent month. This has been corrected.
XRS-4706 The Driver Log Editor's graph drawing tool was not working properly in Internet Explorer or Firefox browsers. This has been resolved.
XRS-4843 If a region had two rule sets enabled and both allowed Short Haul, users received an error message when they tried to select the HOS Rule Change button in the Driver Log Editor. This has been corrected.
XRS-5213 Pending events that had already been accepted were not being included in the update under the On Duty + Driving Last [X] Days field in the Driver Log Editor until midnight of the current day. This has been corrected.
XRS-5228 An issue that was causing some UVA events to not show up in the UVA editor has been resolved.
XRS-5239 The Yard Move option was not appearing in the Insert Work Time Extension window of the Driver Log Editor for drivers that belonged to a sub region. This has been corrected.
XRS-5266 Text alignment problems in the IFTA Fuel Tax report for Alabama have been corrected.
XRS-5355 The Relay Communication report did not generate the correct results when it was exported as a .csv file. This has been corrected.
XRS-5360 The Available Time report was showing 70 hours available for drivers who had not completed a 34-hour reset. This has been resolved.
XRS-5378 Co-drivers were still appearing in the Driver Log report after they had been deleted. This has been corrected.
XRS-6613 When Shift Based was set to No in the Driver Payroll Summary report, time of more than 16 hours spent on duty was not highlighted in yellow, as expected. This has been corrected.
XRS-7263 The UVA displayed on the Compliance dashboard did not match the activity shown in the UVA editor. This has been corrected.
XRS-12767 When drive time was reassigned from Driver A to Driver B and Driver A accepted the reassignment but Driver B rejected it, the drive time should have remained in Driver A's log. Instead the drive time ws removed from Driver A's log, and because it was not added to Driver B's log, the time was lost. This has been corrected.
XRS-12968 If a driver was reassigned drive time while another reassignment to the same driver was still pending, the system should have blocked the second reassignment. Instead, it did not detect the pending transaction and allowed the second reassignment to occur. This has been corrected.
XRS-13522 The Vehicle Inspection Form report for trailers was displaying the form header and the signature line, but not the list of components. This has been corrected.
XRS-12616 An issue that caused the Driver Log Summary report to return an error message when it was generated has been resolved.
XRS-13556 When duty status events were created in the Driver Log Editor and then confirmed by the driver on the mobile device, the events were still being seen as pending when an eRODS transfer was initiated from the host. This has been corrected.
XRS-13711 Due to an incorrect state abbreviation in the database, eRODS file transfers for drivers in the state of Queretaro Mexico were failing. This has been corrected.
  Data Transfer
RACS-708 The send orders feature now has the option to change the route phase upon a successful completion. See the What's New documentation for additional information.
RACS-3300 There was an issue where Published was not being marked after Send Orders completed. This has been corrected.
RACS-3487 Previously, when importing line items, if no Line Item Type was specified in the import file, the system would fail to assign the default line item type assigned to the business unit. This has been corrected.
RACS-3345 An issue using Import Routed Solution that was keeping line items to not be imported using the default Line Item Type configured for the Business Unit when Line Item Type is not mapped in the Data Transfer Layout has been fixed.
RA-39615 Previously, importing a maintenance item that had a duplicate ID in the import file resulted in an error on the second record. Now, all duplicates will be ignored and the last record with the duplicate ID will be the record added. The Import Results dialog has been updated to indicate ignored records.
RACS-3512 There was an issue where the mapped fields in the Send Orders Layout were changing if the name of the output file was changed. This has been corrected.
RACS-3363 There was an issue that was preventing existing orders from being deleted thought the import process. This has been corrected.
  Dispatching
RA-40310 A Deleted Time column was mistakenly displayed in Fleetview's Equipment and Worker grids. This column has been removed.
RA-38069 Users can now unassign orders in FleetView.
RA-42150 There was an issue causing exceptions to show for the wrong location. This has been corrected.
RACS-3444 Previously, the time values on the timeline in Fleetview's Timeline view did properly reflect the offset of the time zone. This has been corrected
RACS-3524 There was as issue that was preventing users from being able to Cease Dispatch some routes in Roadnet Anywhere Web. This has been corrected.
RACS-3205 There was an issue where some workers were not properly being logged out of routes, causing the routes to be stuck in Pending status in FleetView. This has been corrected.
RACS-3515 There was an issue where the Distance To a stop was not being correctly calculated when the previous stop was departed using AAD from the mobile device. This has been corrected.
RACS-3520 There was an issue where stops were not being sequenced properly when a cluster of stops was involved. This has been corrected.
  Maintenance
RA-40609 Previously, users could create a "Current Region" mismatch through the region sharing feature on equipment and devices. This has been corrected
RA-40514 Previously, the process time on a route exception rule that used Time of Day was not being properly converted from local time to UTC. This has been corrected.
RA-36148 There was an issue where users could create a mismatch between Current and Available Regions when sharing entities between regions. Now, users can no longer stop sharing some entities with the current region. The entities affected are: equipment, workers, Telematics devices, and mobile devices.

RA-40393 An unexpected error would occur if a Telematics device was deleted from a region the associated equipment was not shared to. This has been corrected.
RA-38035 An issue allowing mobile devices to be added using an phone number that is in use for another device has been fixed.
RA-40324 The minimum password length for workers using Compliance has been shortened from 6 characters to 4 characters.
RA-39230 There was an issue causing the process time on an Exception Rule configured using Time of Day from displaying properly if the rule was edited multiple times. This has been corrected.
RA-16955 The handling of time zones on on Time of Day Exceptions Rules is better handled and indicated. Additionally, there is a new Process Time column on the Exceptions Rule grid in Roadnet Anywhere Client which displays the time of day and time zone that a rule will be processed.
RACS-3347 The error message displayed when a user attempted to add a mobile or Telematics device that would exceed their license count was not very clear. A more clear message is now displayed in this situation.
RACS-3397 There was an issue preventing Compliance customers from being able to add workers. This has been corrected.
  Navigation
RA-39486 There was an issue where mobile devices with navigation disabled could not be deleted if Navigation was purchased. This has been corrected.
OTNAV-9050 There was an issue preventing devices that were pre-authenticated from syncing properly. This has been corrected.
OTNAV-7642 There was an issue where drivers were not able to geocode to some cities. This has been corrected.
OTNAV-9539 There was an issue geocoding addresses that included punctuation, such as apostrophe marks ('). This has been corrected.
  Roadnet Mobile - iOS
RA-39904 A user can now swipe right to left to acknowledge an exception in Roadnet Mobile Manager on iOS.
RACS-3548 There was an issue where Tracking routes on iOS devices were being completed prematurely. Now, auto-complete route for the iOS Tracking only routes has been disabled.
RA-41377 The defect preventing Roadnet Mobile for iOS users from using "First Stop is Origin" flag has been identified and resolved.
RACS-3536 There was an issue where the standard instructions were being truncated on the mobile device. This has been corrected, as along as the standard instructions are 500 characters or less.
  Routing
RA-40313 An icon between the Export icon and the view configuration picker on the Route Template Manifest's Stop Template dialog was inadvertently exposed. This icon had no function on this manifest and has again been hidden.
RA-39994 A new column, "Order Class" has been added to the Unassigned Orders List View. See the What's New for more information.
RACS-3421 There was an issue that caused the service windows to appear blank for some stops in the stop list. This has been corrected.
RACS-3517 Previously, the Proposed Distance on a modeling route did not update when the route sequence was changed. This has been corrected.
RACS-3500 There was an issue where the planned times and distances for stops were not matching when routes were copied to a new session, and stops on the original route had been cancelled. This has been corrected.
  Miscellaneous
RACS-3493 There was a typing error in the Roadnet Active Alert Admin Guide. This has been corrected.
RACS-3428 There was an issue where some users were receiving an error when trying to log into Roadnet Anywhere Web. This has been corrected.
RA-41615 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.
RACS-3313 There was an issue preventing users from editing web services users without re-entering the web service user's password. This has been corrected.
RACS-3530 There was an issue that was causing the engine hours until maintenance is due to be calculated incorrectly in Equipment Maintenance Planning. This has been corrected.
RACS-3445 There was an issue where unplanned routes were not automatically being archived. This has been corrected.
RA-42269 Users who have purchased Omnitracs Navigation can now access the Support & Learning Center from the Settings icon in Roadnet Anywhere Web.
  Mobile
RA-42033 There was an issue where routes using ADD and confirmation messages were crashing when the user completed the route on the mobile device. This has been corrected.
RACS-3527 There was an issue where the stop sequence in FleetView was not matching the stop sequence on the mobile device when transfer stops were involved and the stops were empty. This has been corrected.
RACS-3383 There was an issue where special characters in worker alerts were preventing routes from loading to the mobile device. This has been corrected.
  Roadnet Mobile Manager
RACS-3549 There was an issue were Roadnet Mobile Manager was not refreshing the nearby location when the foreground activity was closed. This has been corrected.
  Reporting
RACS-3480 There was an issue preventing the Service Window Override report from displaying some locations that had a modified service window time. This has been corrected.
RACS-3562 There was an issue where reports were displaying future dates if Last Week was selected as the date range, and the week crossed a change in months. THis has been corrected.
RACS-3532 The was an issue preventing the Relay Inventory Status report from opening. This has been corrected.
  Telematics
RA-42039 There was an issue where Telematics devices that were shared with multiple regions were still assigned to equipment in the original region, preventing themfrom being assigned to equipment in a shared region. This has been corrected.
RACS-3114 There was an issue where it would appear that a route was no longer getting GPS positions from the Telematics device for an extended period of time. This has been corrected.
  Web Services
RA-41615 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.
RACS-3695 There was an issue where web service users were seeing timeout error messages when retrieving stop depart notifications. This has been corrected.
  Admin
RACS-3230 There was an issue preventing roles from being cloned. This has been corrected.
RACS-3538 The was an issue where searching for a region in Roadnet Anywhere Web was returning the correct list of regions. This has been corrected.
RA-42226 There was an issue causing users to receive an error when attempting to reset their password. This has been corrected.
RA-42238 There was an issue where customers using region hierarchy, and sharing depots between regions, were getting an error message when adding a new region, even though the region was being added. This has been corrected.
  Insight
RA-42152 There was an issue where some Insight customers were seeing data in imperial units, such as miles, when their measurement unit options were set to metric, such as kilometers. This has been corrected.
RACS-3770 There was an issue that was causing some KPIs to time out when loading. This has been corrected.
RACS-3510 The Distribution Metrics Timeline (Exc Multi-Day and Shuttle Routes) KPI was displaying less actual route by weeks than the actual numbers. This has been resolved.
RACS-3518 There was an issue where the week number column was not sorting properly. This has been corrected.
  Relay
XRS-12527 An issue where GPS and Jurisdiction settings on the Relay could override each other and result in repeated location changes between the correct location and “UNKNOWN” 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.