2020.4

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

Before upgrading your production environment, Trimble recommends that you read the system requirements and install the latest version in a test environment. If you have questions, please contact your Trimble customer representative.

Warnings

Social Security number encryption warning

Starting in version 2020.2, Social Security numbers you enter in the Driver profile are encrypted in the database by default.
However, you can set up the system so that the Social Security numbers you enter in the Driver profile are not encrypted in the database.
To do so, set the DataEncryption General Info Table setting’s String1 field to N.

The Data Conversion Administration Utility lets you encrypt/decrypt a group of Social Security numbers in your database. Contact your Professional Services representative to obtain the DataConversionAdministrationUtilityInstall.msi.

Only a system administrator should have access to the utility. Users without sys admin rights should not use it. The utility provides access to all highly sensitive data. It should be used only in the explicit instance of needing to encrypt or decrypt the driver profile.

Cancel order/trip feature warning

Starting in version 2020.1, the user interface for the cancel order/trip functionality has changed. Several enhancements were made to make the process easier and more intuitive. Also, the same Cancel Trip/Order window is now used in both Order Entry and in the Trip Folder.
For more information, see Canceling an order in version 2020.1 and later.

User level record security

Starting with TMW Operations version 2019.1, there is a functional change that will affect customers using custom views on Company Planner, Brokerage, or Covering boards that rely on User Level Record Security. Affected customers may need to contact Support for assistance before upgrading. See the User level record security resolved issue for details.

Minimum technical requirements for 17.50 or higher warning

To upgrade from a build lower than 17.50 to 17.50 or higher, you must follow these steps.

  1. Notify your Support team that you will upgrade. (As noted in Step 4, they will need to work with you to complete the installation process.)

  2. Verify that your environment adheres to these minimum technical requirements:

    • Microsoft .NET Framework version 4.6.2 must be installed.

    • Client operating systems must be at Windows 7 SP1 or higher.

    • Server operating systems must be at Windows Server 2012 or higher.

    • In addition, verify that your system adheres to the additional requirements listed in the General requirements section for the build you are upgrading to.

  3. Run the TMW Operations installation program.

  4. Before any users attempt to use TMW Operations, call your Support representative to have them update your Planning Worksheet boards.

Trimble Transportation has added columns to the system default Planning Worksheet views to enhance the inline editing feature. These columns also must be added to all custom views. Support will perform this step for you at no cost.

Case sensitive passwords warning

Starting with V.17.50, the system treats all passwords as case sensitive. This includes existing passwords.

This change affects how you log in with an existing password:

  • If your password was created with [Misc]CaseSensitivePasswords=OFF in your TTS50, you must enter that password in all upper case characters.

  • If your password was created with [Misc]CaseSensitivePasswords=ON in your TTS50, you can enter that password as you originally recorded it (case sensitive).

Requirements

Before you begin installing TMW Operations version 2020.4, check that these requirements are met:

  • TMWSuite®
    You must be using TMWSuite V. 2020.4.

  • TMW Back Office
    If you are using TMW Back Office, your version of TMW Operations must be the same as your version of TMW Back Office.

  • Microsoft® .NET Framework
    .NET Framework 4.6.2 or later (full package not client)

    The framework must be installed on the TMW Operations server, client, and administrator systems before you install TMW Operations. If it is not present, the system displays an advisory message during the installation. Install the framework before running the application.

  • Internet Information Services (IIS) for Microsoft Windows Server®
    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft SQL Server®

    • Microsoft SQL Server 2012 or later

      Note: SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019 are certified for use with this application. Trimble Transportation recommends using the latest service pack of whichever version you use.

  • You must be logged into the system where you want to install TMW Operations, and have administrator rights for that system.
    Like most applications, TMW Operations can be installed locally on a user’s system. It is also possible to install TMW Operations on a network drive. To do so, you must be logged into the system where the drive is physically located, and have administrator rights for that system.

  • SQL Server System Administrator rights are necessary.
    The installation of TMW Operations includes the manual application of a SQL script to the TMWSuite database. You must have a SQL Server administrator login and password to apply it.

  • TruETA Preplanning
    You must have these Trimble Web Products and modules installed:

Enhancements

Privacy Policy link

The Trimble Privacy Policy link added (NSUITE-210473)

The Trimble Privacy link has been added to the TMW Operations login window. When you click the link, the Privacy Policy page opens in a web browser.

Freight Board Interface

Suppressing pop-up messages (TSI-727)

When using the Load Status Monitor, these pop-up messages are enabled by default:

  • FTP errors.

  • Postings are put into the queue to be sent.

  • The user that submitted the original posting is different from the current user.
    Note: This applies only to Truckstop.com.

They can be disabled on the server. When you use the Load Status Monitor with Freight Board Interface, these messages can negatively affect performance.

Now, new settings let you disable these pop-up messages. The settings are available for both the server and client installations.

Planning Worksheet

Preventing assignment overrides when validating assignments (NSUITE-210406)

You can set up the Planning Worksheet to check for asset changes between when you opened it and when you saved an assignment. This made a validation message appear if an order already had assets assigned. The message allowed you to overwrite the assigned assets or keep the last saved assignment. Now, you can also set up the system so that it does not offer the choice to overwrite the saved assignment.

Profit and Loss tab

Hiding accessorial charges (NSUITE-209995)

The Profit and Loss tab is available in Order Maintenance, Trip Folder, and Company Planner. The tab’s Invoice Charges grid shows line haul and accessorial charges calculated for the trip.

Your company may want only supervisors and system administrators to see some accessorial charges. Using Field Chooser, you can add the Hide if not Supervisor (iv_hide) checkbox to the grid. Then, you can select the checkbox to hide invoice details based on specific accessorial charge types from general users.

Trip Folder

Having the PUP trailer assigned when the primary trailer is assigned (NSUITE-210246)

When you set up a trailer profile, you can assign a secondary trailer (PUP) that is attached to it. Additionally, you can set up the system to:

  • Autofill the Trailer1 field with the ID of the trailer last used by the tractor you assign on a trip.

  • Autofill the Trailer2 field with the ID of the secondary trailer last used by the tractor you assign on a trip.

Now, you can set up the system to autofill the Trailer2 field with the ID of the secondary trailer when you assign a trailer in the Trailer 1 field. The system assigns the PUP specified in the primary trailer’s profile. If no PUP is specified in the primary trailer’s profile, the Trailer2 field value stays UNKNOWN.

TruETA

Identifying stop types sent to TruETA (NSUITE-210461)

Before, TruETA sent only Origin, Destination, and Work stop types for processing. Now, the StopType3 label includes options for these rest stop types:

  • Work - A standard stop within a trip.

  • Waypoint - A point used to help shape the route, if needed. The driver passes through a waypoint, but doesn’t have to stop at a waypoint.

  • FuelStop - A planned fuel stop.

  • RestStopShort - The rest stop planned for a short break.

  • RestStopLong - The rest stop planned for a long break.

  • RestStopCycleReset - The rest stop planned to reset the drive time cycle.

  • RestStopFullDay - The rest stop for a day break.

  • RestStopDriverSwitch - The rest stop used to swap drivers.

  • BorderCrossing - North America only. This is triggered automatically if you cross a border, and it is added as a stop. Border crossings will have a dwell time of 1 hour automatically added.

Only interim stops can be set as any of these TruETA stop types. The first stop on the trip will always be the Origin. The last stop on the trip will always be the Destination.

Resolved issues

Asset Assignment History

  • NSUITE-210342
    The Asset Assignment History window did not show order numbers for consolidated orders.

  • NSUITE-210559
    The Asset Assignment window was showing trailer beaming errors. The error messages were not clearly stating the cause.

  • NSUITE-210146
    TruETA Preplanning did not see the correct prior date/location for preplanned trips.

Brokerage

  • NSUITE-210476
    If you:

    1. Awarded an order to a carrier using the Company Planner Covering board’s Company Carriers tab.

    2. Opened the order in the Trip Folder and set the Carrier field back to UNKNOWN and saved the trip.

    3. Then awarded the order to the same carrier in the Company Planner.

      The ACS window would show UNKNOWN instead of the same carrier being awarded again.

Company Order Requirements

  • NSUITE-207049
    The system was applying company order trailer requirements for departures when arrivals were actualized.

Company Scroll window

  • NSUITE-210247
    The Company Scroll window closed when you clicked Show Map. This happened if you were using PCMilerV.31 or earlier.

Credit Checking

  • PB-200711
    You can use the [Misc]ForceOrderStatusWhenCreditCheckFails setting to specify the non-dispatch status to apply to orders when the Bill To fails a credit check. The system was ignoring this setting. It let you set an order’s status to Available.

  • NSUITE-210215
    You can set up the system to have Completed orders excluded from credit checking. The system was ignoring this setup.

  • NSUITE-210433
    You can set up the Credit Checking feature to request a password be entered before the system will let you save orders for a Bill To that failed the credit check. The system was ignoring this setup was not prompting for a password when you copied order for a Bill To that failed the credit check.

EDI

  • TSI-631
    Incoming 204s became attached to manual orders due to the Divert 204 functionality. This caused the manual order’s RevType1 value to change to that of the incoming 204.

  • TSI-731
    Importing 204s in Data Exchange produced SQL errors.

Fuel Tax Export

  • NSUITE-207634
    The Fuel Tax Export module was not finding all fuel transactions.

Freight Board Interface

  • TSI-750
    The rate was no longer posting to TruckStop.com after an API upgrade.

Master Orders

  • NSUITE-210401
    You could not edit stops on a master order in the Trip Folder or the Route Maintenance window. This prevented you from changing an existing route.

Mileage

  • NSUITE-208153
    When you do company-to-company lookups, basing it on the values recorded in the Map Address field is more accurate. The system was ignoring Map Address field entries in company profiles. Instead, it used the value from the profiles' Address 1 field.

Planning Worksheet

  • NSUITE-210420
    When you use drag-and-drop functionality to assign a resource to a trip, the Asset Assignment window opens. The Location field in the Dead head start time, location and trailer(s) section did not show the tractor’s previous location.

  • PB-200699
    The Planning Worksheet’s External Equipment board combined the city and state in the Destination City column. This caused issues when searching by those destination cities.

Profit and Loss tab

  • NSUITE-210201
    When rating a rate by detail order by a Distance (Furthest) rate, the charge should be calculated for the furthest distance traveled by a commodity with the same commodity class as the drop. The distance for all pickups and drops is used. TMW Operations was not applying Distance (Furthest) rates to calculate charges for orders that matched the rates. This happened when the order had only two stops.

Trailer Profile window

  • NSUITE-209869
    The system allowed you to enter data in the UNKNOWN Trailer Profile. When the window is first opened, some fields on the various tabs can be edited and saved. If you retrieved another trailer and went back to the UNKNOWN trailer, the fields were locked.

Trip Folder

  • NSUITE-209582
    The system ignored the [Misc]AllowBkgIfCreditFails=X setting. You could save orders for BillTo’s that had negative available credit. This could happen in Order Maintenance, the Trip Folder, and when you copied orders.

  • NSUITE-210433
    When you save an order that exceeds the Bill To’s credit limit, you are prompted for a credit check password. If you created copies of that order, the copies would also exceed the credit limit. The system was not prompting you for a password when you copied the orders.