2025.7

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

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

  • Microsoft® .NET Framework
    Install or upgrade to the latest version of the Microsoft .NET Framework on your system. At a minimum, you should have V.4.6.2 installed.

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

  • 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 the FuelTMS applications, and have administrator rights for that system.
    Like most applications, FuelTMS applications can be installed locally on a user’s system. It is also possible to install FuelTMS applications 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 FuelTMS applications 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

Enhancements

Card Planner

Enable Bulk Removal of orders (TTESUITE-214191)

A right-click menu feature has been added in the Card Planner that enhances schedule management. Users can now efficiently remove orders from a shift or a specific driver, allowing for the quick return of multiple orders to the available loads grid.

Resolved issues

Call On Demand Order Entry

  • TTESUITE-212958

This resolves an error when users attempted to consolidate orders that were in a Planned (PLN) status. The order consolidation feature is designed to work exclusively with orders in an Available (AVL) status. To prevent future errors and clarify the workflow, we have implemented the following checks:

From the "Call On Demand Order Entry" Screen: Users will now be prevented from opening the consolidation window if any selected orders are not in AVL status. An informational message will appear explaining why the action cannot be completed.

Within the Consolidation Window: If a user attempts to add an order that is not in AVL status to an existing consolidation, the action will be blocked, and a dialog will explain that only AVL orders are eligible.

This ensures that the consolidation process is more stable and works as intended.

Forecast Order Site Review

  • TTESUITE-212680

This release introduces a tolerance for minor tank reading increases in the Forecast Order Site Review. Previously, any uptick in a tank’s volume reading after an order was completed would flag that order for review. This could be triggered by non-delivery events, such as pressure changes.

We have now implemented a threshold that allows for a reading increase of up to 1% of a tank’s total volume before flagging a completed order for dispatcher review. This change is designed to reduce the number of false positives and ensure that only orders requiring genuine attention are highlighted.

Note: This functionality is only active if you have the TankReadingOrderAdjustment=Y setting enabled in the [InventoryService] section of the TTS50.ini file.

Mileage

  • TTESUITE-212945

Resolved an issue where mileage lookups were not being properly cached. This correction ensures the system uses existing data when available, reducing redundant calls to our external mileage provider and improving system performance.