2023.1

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.

A PDF version of these release notes is available.

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.

Access and usage of The Data Conversion Administration Utility should only be provided to a system administrator. That utility provides access to all highly sensitive data and should only be used 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 2023.1, check that these requirements are met:

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

  • 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

Driver Profile

Complaint tab added (TTESUITE-205737)

In TMWSuite’s File Maintenance there is an option to enter driver complaints in the Complaints History window. Previously, in TMW Operations there was not an option to enter driver complaint records in an existing tab.
Now, a Complaints tab has been added to the Driver profile window. You can add, delete, and modify driver complaint records.

Mileage

Rand County qualifier (TTESUITE-204063)

Previously, if you used Rand mileage lookups; an incorrect city lookup occurred if the county qualifier was used. Now, a setting value has been added to force the use of the Rand County value when looking up Rand mileage. The value FT (Force County) has been added that you can use in your [MileageInterface] section of the TTS50. If the CityNames setting is set to FT, Rand Intelliroute lookups will use the Rand County value no matter what the City county value is set to. This will also work with the FullCountNames option. Below is an example of the settings in place in the [MileageInterface] section of the TTS50.

XFace[1]=I - Rand PC
Type[1]=HS - Shortest (HHG)
Path[1]=tmwutil
CityNames[1]=FT

Note: This only applies to Rand Intelliroute.

Settings

SeparateArrivalandDepartureTime (TTESUITE-204136)

You use the TTS50 setting [Dispatch] SeparateArrivalandDepartureTime to specify the number of minutes that must separate the actualized Arrival and Departure times of a billable stop. Previously, this setting was only available for TMWSuite. Now, it is available to use in TMW Operations.

Tractor Profile

MC Terminal field added (TTESUITE-202805)

Previously, if you had to view and make a change to the MC Terminal ID field in the Tractor Profile, you had to open File Maintenance in TMWSuite to edit it. Now, in TMW Operations you can add the MC Terminal ID field in the Tractor Profile. The field is added using Toggle QuickDesigner in the profile. The field is alphanumeric and limited to 20 characters.

Trip Folder

Able to save a planned order with an illogical event sequence (TTESUITE-159177)

Previously, you were able to create and save an order with assets attached with a Drop Loaded (DRL) event followed by two Live Unload (LUL) events. The system did not provide a warning or error that this sequence was not valid. Now, a TTS50 setting [Asset Assignment]ValidateTrailerEventsOnPlanned is available. When the setting is set to WARN or PREVENT, the system will prompt a warning or save error message when you attempt to save an invalid event sequence.

Resolved issues

Advanced Carrier Selection

  • TTESUITE-204517
    When you added a new contact in the Advanced Carrier Selection (ACS) window, not all the contact info fields were added to the company/carrier profile. Now, if the General Info Table setting AllowAdHocContactsPhoneEmail is set to N in String1, the fields are added to the profile.

Profit and Loss tab

  • TTESUITE-204608
    If you used the General Info Table setting ContractMgmt, charge type options did not filter correctly for consolidated orders. When you consolidated an order with two separate Bill To’s, the list of charge type options available on the Profit and Loss tab in the Trip Folder only listed the options for the Bill To on the active order from the Trip Info tab. Now, the charge type drop-down list for each order is correctly filtered for the order selected on the Profit and Loss tab.

Trip Folder

  • TTESUITE-200579
    If you used a return event after a drop event on an order, the system adds a Hook Empty Trailer (HMT) event after it. The Event column drop-down list only displayed HMT and IHMT events to select from.
    Now, you can use the setting [.NetOperations] UseLikeEventCodeList=N in your TTS50 to view all available event codes in the drop-down list for the current stop.

  • TTESUITE-204062
    When you used a return empty split on a trip and updated the final delivery location on a second leg; an error occurred when saved. This happened when these settings did not match:

    • [MileageType] Operations

    • [MileageType] Settlements

In this scenario, the setting [MileageType] BillToBasedRoutingAndPay=N also affected this.

  • TTESUITE-204744
    If you had a cross dock order where the first leg was invoiced and you tried to complete the second leg, an error would occur. You were not able to complete the leg. The system now checks whether any of the movements in the order are locked and does not attempt to change freight details on the locked movement.