2024.2

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.

Requirements

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

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

  • 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 2014 or later

      Note: SQL Server 2016, SQL Server 2017, SQL Server 2019, and SQL Server 2022 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.

  • PC*MILER®
    Certified with PC*MILER v.37

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

Enhancements

RateWareFgtSource General Info Table setting

Setting option available for computing invoice details (TTESUITE-205785)

You can now use the RateWareFgtSource General Info Table setting with TMW Operations and TMW Back Office.

Neither application supports the ANY option.

Repair Order window

Add Repair Order functionality from TMWSuite (TTESUITE-203764)

The Repair Order window is a part of the Tank Wash program, which is a TMT Fleet Maintenance and TMWSuite Integration. This had previously only been available to use in the TMWSuite - Dispatch application. Now, this functionality of the Repair Order window has been added in the Trip Folder of TMW Operations.

Tender Evaluation

Tender Evaluation integration in TMW Operations (TTESUITE-207164)

Tender Evaluation is to assist carriers in evaluating if an order is a good fit for their business operations. The Tender Evaluation functionality has been integrated with the EDI Planning Worksheet in TMW Operations. Tender Evaluation will use a carrier’s historical data as well as current operating conditions and will help in selecting an order.

Tolls

View toll data in TMW Operations (TTESUITE-206632)

Previously, toll costs for stops were not visible in the Trip Folder in TMW Operations. Now, a new Toll Cost column can be added using Screen Designer into the Stops grid in Trip Folder. Furthermore, a Toll Cost field for the order header can also be added to the Trip Folder layout and will display the total Toll Costs for the order.

TruETA

Capture additional information from TruETA estimates (TTESUITE-208335)

Capture the Status and actual Arrival/Departure times returned from TruETA in the TMW database.

Resolved issues

Mileage

  • TTESUITE-208318
    Fixed a bug in SQL retrieving cached Mileages from the MileageTable. Logic was automatically changing the sign of the Company Longitude. If the sign was already negative, this caused the Longitude to become positive and could cause the logic to not find the record in the Cache (when the cache had a negative longitude). Updated the logic to change the sign only when the longitude is not already negative on the Company record.