We have released the latest version of the Vehicle Mobile Application, version 1.2.0300 (483). It is currently available in Google Play for Android phones, and it will be available for iPhones in 7 – 10 days. 

This release includes the following updates and fixes:

New features in this version:

  • Prints bar codes on Gate Pass

Please ask your staff to download the latest version from Google Play (Android) today so that they are up to date. The new version will be available for iPhones in 7 – 10 days.

It can be accessed from the mobile app’s Main Menu, and displays the following information.

  • App Version
    • This will be of the form “X.Y.Z (B)”, for example “0.2.0 (408)” for the version released on 4/15/2105. X.Y.Z is the version number we assign. B is the sequential build number assigned by the build server, and is what is normally used to distinguish which version we’re talking about.
  • OS Version
  • Dispatcher
    • The name of the Dispatcher, as shown in the login list (this is NOT the four-letter Dispatcher Code).
      WebService URL Tells you which database they’re talking to.
  • Driver Name
    • The user code the driver used to log in.
  • Truck Number
  • Truck Mileage

Prompt handling of new Common Locations and Mappings is essential to the proper operation of the TMS system. Please make certain your team knows how to handle this correctly.

  • All requests for a new port or railhead must be handled immediately upon receipt.
  • This must be done before any vehicles are assigned to a new location.
  • Failure to complete this on time may result inlost or delayed revenue and potential loss of OEM contracts.

Setting up a common location for any new port or railnead is a three step process, which is demonstrated in this document. All three steps are required. 


STEP 1: Set up the Common Location in the TMS

Common locations can be added under the Admin menu, Common Location:

Screen Shot 2015-10-23 at 2.31.27 PM


Click the Add Location button:


Read More

The File Automation system takes care of receiving and sending many of the files that come and go from the OEMs. Not ALL imports and exports have been automated, and some must be done manually through the Admin/Data Import and Admin/Data Export menu items. We are continually improving the program to automate more of these functions so your job is easier. These functions have recently been automated, if you are still doing them manually you no longer need to do that:


Shows the latest app versions installed by the drivers, and how many people have installed what versions, on what platforms (iPhone or Android)



  • Click on one of the cells with a number to show a list of the drivers with that version(s) and platform(s).
  • Double-click on a driver in the lower list to open his record in the Drivers window
  • If a driver is listed in the summary line for the “(unknown)” version, it means they do not have the latest 1.2.000 (421) installed

The desktop app allows you to easily check driver mobile device and mobile app information.

On the Admin/Drivers window, there is a tab called “Mobile Device”.

vda-driver details screenshot

On there you will find:

  • “Login info” section
    • All of the driver’s login information — user code, PIN, and truck number
  • “Mobile app” section
    • The last date and time they logged in, and the app version number and build number
    • Latest released version of the mobile app
    • The earliest version of the mobile app that is compatible with the current desktop app
  • “Driver mobile device” section
    • Phone platform, make, model, OS version, device name (if any), and cell carrier

The “Login info” section is filled in for all drivers, and may help you when talking to drivers who have trouble logging in.

The “Mobile app” and “Driver mobile device” information is now being recorded by the new 1.2.0000 (421) version, so as your drivers download the new version and log in, you will be able to see their device and app information and the version of the app they are using.

NOTE: If the “Mobile app” login information and the “Driver mobile device” information are not filled in for a driver, that means they are not yet using the 1.2.000 (421) version.

There is also a Mobile Device summary window to see the status of all drivers at once and print a report, this is covered in a separate blog entry.

After a delivery is made with the mobile app, an email is sent to the dealer with a link to an online Bill of Lading (BOL). You can use the Vehicle Desktop Application to display this BOL in your browser by going to the Load Details window. Find the load you want, then click the new “Dealer Bill of Lading” button to open your browser and display just what was sent to the dealer. This way if a dealer calls in with a question, you can look at the exact document they have in front of them.


The load must be delivered using the mobile app to use this function, loads delivered using the desktop application do not generate online BOLs for the dealers.

If the driver needs to check the street address for a delivery, they can view this in the mobile app.

• Go to the Delivery tab on the Current Run screen, tap the arrow to the right of the destination location

• This will display the Location Details screen, which has the delivery address, phone number, and any directions that might have been entered by the dispatchers.


Android Only Update
Hi all, Happy Wednesday!

We hope you and the drivers are having success using the mobile app.
NOTE: New version 1.2.0100 (446) released for ANDROID ONLY
This new version is being released on Android first, the iOS version will follow in about a week. This new version has undergone extensive testing prior to release, so the drivers should have a better experience with this update than the last.

What’s new in this version:
  • Fix to problems caused by multiple delivery locations with identical names
  • Fix index out of bounds errors
  • Exceptions are now generated again for delivering to different location
  • Prompt driver when adding a load to a run not yet completed
  • Test Scanner function for identifying scan problems
  • Reporting of iPhone model numbers
  • Add driver expenses
  • View unpaid expenses
What drivers should do:
  • A new version 1.2.0100 (446) of the mobile app is now available for download on Android phones
  • Drivers with Android phones can download the update in the Google Play store, use button below
  • Drivers with iPhones will continue using 1.2.0000 (421) until the new version comes out for iPhone next week

[button link=”https://play.google.com/store/apps/details?id=m.transport.Android&hl=en” color=”silver” newwindow=”yes”] Android Download[/button]


We hope this briefing is useful to you. If there are any topics you’d like us to cover, or if we can improve the manuals, please let us know.

Walt Venable
Senior Application Engineer

How to Identify the error

Loads that have already been delivered keep showing up in the Select Loads screen of the mobile app when you Refresh from Dispatch.

What it means

One of the loads that you delivered in the past is not recorded as fully delivered in the system. It may be that an exception came in and was not dealt with, so that even though the driver delivered the load one of the vehicles is still not delivered. When this happens, new loads that the driver picks up are added to the last run, and the vehicles from the last run(s) will continue to show up in the phone.

What to do about it

Get one or more of the load numbers that keep showing up in the driver’s phone. In the desktop app, go to Payroll/Run Details, do a Find on that Load number. Open the Run, if this is the correct problem then you will see vehicles from several loads in the “Vehicles Delivered” list.

Now you have to examine the loads to see which one (or more than one) is still in the EnRoute state. Click “Modify” on the Run window, click on a line for a vehicle from one of the loads and click the “View Load” button. In the Load Details window, check the load status in the upper-right corner. If it’s EnRoute, this load must be Delivered before the Run can be Closed.

Deliver the vehicles in the load that are not yet delivered (or if it’s actually enroute, wait for the driver to deliver it). This should automatically close the Run, but if it does not then click Modify on the Run Detail window again and change the Run Status to Closed.

Now the driver can go into their phone, do Refresh from Dispatch, and see no vehicles assigned to them.

How to Identify the error

Driver scans a barcode from the car’s door column and it is not recognized.

What it means

This may be due to the bar code having extra characters, the most common example being a vertical bar character “|” appended to the front of the barcode, like this:

What to do about it

Current versions of the app will try to ignore these extra characters, but if it makes a mistake the driver can work around it by selecting the VIN from the list (or enter the last 8 digits manually) instead of scanning.


The app should be catching all odd characters now, so if drivers have a problem of this type please obtain a photocopy of the barcode they were scanning so we can analyze it and improve the app.


Loads are identified in the desktop and mobile apps by their Load Number. The load numbers are 8-digit numbers like “15040555”, which breaks down like this:


15: the last two digits of the year, so this load was created in 2015

04: the 2-digit month number, so this load was created in April

0555: load number this month, starting with 1, so this is the 555th load created in April 2015