2020.1
This section contains the following for the latest version:
-
System requirements
-
Enhancements (new or updated features)
-
Resolved issues (application improvements)
We have updated our company name and logo to the Trimble brand.
Before upgrading your production environment, Trimble Transportation recommends that you read the system requirements and install the latest version in a test environment. If you have questions, please contact your Customer representative. |
Requirements
Before you begin installing LTL Operations Module version 2020.1, check that these requirements are met:
-
TMWSuite®
You must be using TMWSuite V.2018.18_01.0192 or later.
-
Microsoft® .NET Framework
NET Framework 4.6.2 or later (full package not client)The framework must be installed on the LTL Operations Module server, client, and administrator systems before you install LTL Operations Module. 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, and SQL Server 2017 are supported. 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 LTL Operations Module, and have administrator rights for that system.
Like most applications, LTL Operations Module can be installed locally on a user’s system. It is also possible to install LTL Operations Module 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 LTL Operations Module 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.
Enhancements
Rail drayage
Removing orders from completed stops (NSUITE-209449)
Orders where the container exited the rail yard, offloaded, loaded, and then returned to the rail yard, did not execute. This occurred because the manifest ID was assigned to a prior reservation. You can now use the Deassign button in the Order Window’s Routes tab to remove orders from completed stops. Additional modifications allow you to set the origin of the manifest to a pickup company.
Showing columns in terminal schedules
Viewing columns in schedule grids (NSUITE-209478)
When a grid has enough columns to show a horizontal scrollbar, a pop-up window opens allowing you to see all columns in one view. The pop-up window is now available in the Terminal Schedules and Schedule Legs grids.
Resolved issues
Interoperability
-
NSUITE-208270
Assets from a truckload delivery leg were pushed incorrectly to earlier truckload legs.
-
NSUITE-208272
A truckload delivery (with HCT) done by LTL, changed the driver on the pickup leg.
-
NSUITE-208283
When the LTL order with the UNKNOWN company code was completed, the stop times and completion statuses were not updated into TMW Operations. This only occurred when the LTL order, with the UNKNOWN company code, was part of a truckload leg with multiple stops. If a truckload leg was completed in LTL with only one UNKNOWN company code stop, the information updated correctly.
-
NSUITE-208284
When the Drop Crossdock stop was completed (last stop in the leg) the corresponding truckload stop statuses/times were not updated.
-
NSUITE 208325
A trailer sync issue occurred for an HMT/DMT and HPL/DLT truckload scenario.
-
NSUITE-208336
When a truckload leg with two stops (HLT/DLT) was completed in LTL, the assets used on the prior leg were overwritten by the LTL assets.
-
NSUITE-208341
When LTL handles the Linehaul leg of a truckload trip, the Final truckload stop did not get set to complete when the corresponding LTL stop was completed.
Manifest
-
NSUITE-208345
Creating a TMW Operations/LTL Manifest failed without a helpful error message. This occurred when multiple LTL orders were created for a single Truckload Trip, but one of the orders could not be saved.
Miscellaneous
-
NSUITE-205334
When you assigned a Bill To on an index for a line item on a carrier charge, the system did not apply the line item to the charge. You had to remove the Bill To restriction for the line item to process.
-
NSUITE-208281
When attempting to process a master bill (with additional invoices) to TMW Imaging, the invoice queue failed to transfer the.ps files to the managing system for processing.
-
NSUITE-208471
Persistent DateTime values existed in DAL objects. This caused the accrual_date of Brokerage legs to be set incorrectly by the LTL EDI Service.
-
NSUITE-209448
The Assign Rail reservation validity check did not take into account a parent/child terminal relationship when you made a rail reservation assignment.
-
NSUITE-209459
The mileage rating process failed when using a Pass Through State Tariff.
-
NSUITE-209551
The Route Id dropdown list in the Terminal Schedules window showed routes from all terminals. The list should only show values for the current terminal.
Mobile
-
NSUITE-209406
LTL Mobile Comm was issuing warning messages for many different types of events, including those that were informational only. A warning or error message should only show to identify a problem.
-
NSUITE-209436
Modified LTL Mobile to truncate and correctly handle State codes that are more than three characters.