2025.5
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.5, check that these requirements are met:
-
TMWSuite®
You must be using TMWSuite V. 2025.5. -
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.38 -
TruETA Preplanning
You must have these Trimble Web Products and modules installed:-
Licensing
-
For details, see the Trimble Web Products installation guide.
-
-
SystemsLink
-
This version should match the version of TMW Operations.
-
For details, see the SystemsLink installation guide.
-
-
WorkCycle
-
This version should match the version of TMW Operations.
-
For details, see the WorkCycle installation guide.
-
-
Resolved issues
Freight Board Interface
-
TTESUITE-213129
Previously, when posting loads to freight board vendor Truckstop.com through Freight Board Interface with the TTC API option enabled, stop location country codes having only two characters resulted in an error, preventing the load from posting. This issue has been resolved so that the country code may be two characters (e.g. US, CA, MX) or three characters (e.g. USA, CAN, MEX).
Fuel Import
-
TTESUITE-213061
Implements the change to the Comdata password which is now case-sensitive and up to 50 characters in length.
-
TTESUITE-213195
This updates the password requirements for Intraday so it would accept the updated case-sensitive 50 character password changes for Comdata.
Profit and Loss tab
-
TTESUITE-212595
Fixed an issue where order charge information wasn’t properly synced with the corresponding subtotal invoice detail if changed.
Route Planner
-
TTESUITE-212995
Fixed a validation issue that happened when creating new cell layouts in the Route Planner and Trip Planner windows.
TMW Data Exchange
-
TTESUITE-204885
Fixed a data type conversion error that could occur when a note was deleted with an EDI 204 update tender.
Trip Folder
-
TTESUITE-211982
Fixed an issue when changing the company on the shipper stop or consignee stop. If you set the company on the shipper or consignee stop to a valid company, that Company Id gets pushed to either the ord_showshipper or ord_showconsignee field on the orderheader. If you changed the company to UNKNOWN and then changed the company to a valid company, the ord_showshipper and ord_consignee would still be set to the original company from the shipper or consignee stop.