2025.8

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.

If you want, you can print a PDF of this page.

Requirements

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

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

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

  • Microsoft SQL Server®

    • Microsoft SQL Server 2016 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.39

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

Enhancements

Driver Scroll

View assignment history menu (TTESUITE-214533)

You can now quickly view a driver’s assignment history directly from the Driver Scroll results grid. Right-click any driver row and select View Assignment History from the right-click menu to see their assignments for the past 60 days and the next 30 days in a convenient dialog.

Weather Routing MAPS Integration (TTESUITE-213937)

Defined weather routing stops, weather risk, weather summary, and next impact are seamlessly integrated into the TMW Operations Planning Worksheet as data is added to the Comments column in the Stops grid.

Resolved issues

EDI

  • TTESUITE-214287

Resolved an issue where the 139 wrapper record for EDI 210s would contain null data. This occurred when the [.NetOperations] AllowCustomerEquipmentForTrl setting was enabled ('Y') and a trailer ID on the trip did not exist in the trailerprofile table (e.g., customer equipment). The record will now populate correctly in this scenario.

eManifest

  • TTESUITE-210969

The .NET eManifest application now checks the AceTrailerSealValidationRule (TTS50) setting to determine the severity of trailer seal validation errors. If this setting’s value begins with 'E' (e.g., "ERROR"), the error status will be set to Critical. If the setting is missing or does not begin with 'E', the status will default to Information, maintaining the previous behavior.

Profit and Loss tab

  • TTESUITE-159227

Previously, the TTS50 setting [Invoice]UseOrderTrlType1 was ignored by TMW.Suite Rating. Now, the setting will be applied when computing invoice charges.

  • TTESUITE-212209, TTESUITE-214116

Fixed an error that caused incorrect data on the Profit and Loss tab in the Trip Folder. This was happening because rating information wasn’t being updated correctly on the order when it was saved, due to the [Dispatch]RateOrderOnSave setting not correctly updating rating information on the order header.

  • TTESUITE-214352

Previously, when adding Line Item charges using the LHW charge type, the system failed to divide the weight by 100 as expected. Now the LHW charge type correctly divides the weight by 100 when computing the charge amount.