2020.4

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 Transportation 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 LTL Operations Module version 2020.4, 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, SQL Server 2017, and SQL Server 2019 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

Appian DirectRoute integration

Upgrading to 2018.1.1.1 WebService and related DLLs (NSUITE-210134)

The Appian DirectRoute integration now uses the newer 2018.1.1.1.1 version of the DirectRoute DLL library.

Send to Appian: Showing a company’s open and closed days (NSUITE-210251)

The Pattern1 field values in the Route Response grid identify the days of the week in which a company is open and closed. In previous versions, it showed the days of the week based on a Monday (M) to Sunday (S) pattern (MTWRFAS). Now it shows the days of the week based on a Sunday (S) to Saturday (A) pattern (SMTWRFA).

Editing and saving Appian DirectRroute request and response data (NSUITE-210331)

Now you have the ability to edit and save Send to Appian route request and response data. This means that certain fields remain editable before the export and after the import of data. You access the fields in Field Chooser. The fields show in various sections of the application. The fields include:

  • General
    UnldPerf% - TerminalTripScheduleLegs

  • Truck Work Rules
    Edate - TerminalTripScheduleLegs
    Ldate - TerminalTripScheduleLegs
    EarStart - TerminalTripScheduleLegs
    LatStart - TerminalTripScheduleLegs
    LatFinish - TerminalTripScheduleLegs
    MaxWorkTm - TerminalTripScheduleLegs
    MaxDriveTm - TerminalTripScheduleLegs
    MinLayover - TerminalTripScheduleLegs
    MaxLayover - TerminalTripScheduleLegs
    MaxLayovers - TerminalTripScheduleLegs
    PreTrip - TerminalTripScheduleLegs
    PostTrip - TerminalTripScheduleLegs
    Brk1Duration - TerminalTripScheduleLegs
    Brk1Start - TerminalTripScheduleLegs
    Brk2Duration - TerminalTripScheduleLegs
    Brk2Start - TerminalTripScheduleLegs
    Brk3Duration - TerminalTripScheduleLegs
    Brk3Start - TerminalTripScheduleLegs
    Brk4Duration - TerminalTripScheduleLegs
    Brk4Start - TerminalTripScheduleLegs
    Brk5Duration - TerminalTripScheduleLegs
    Brk5Start - TerminalTripScheduleLegs

  • User Fields
    DispatchLoc - TerminalTripScheduleLegs.RevType1
    StartLoc - TerminalTripScheduleLegs.RevType2
    RtType - TerminalTripScheduleLegs.RevType3
    RevType3 - TerminalTripScheduleLegs.RevType4

  • Truck Volume
    Weight - TrailerTemplate
    Cube - TrailerTemplate
    Piece - TrailerTemplate

  • Stop File fields

    • Time Window
      EarliestDate -Only non-master order - Ord Dest Earliest
      LatestDate -Only non-master order - Ord Dest Latest
      Weight - Master Order
      Cube - Master Order
      Piece - Master Order

    • Stop level
      These fields are editable during the route request process to affect the specific stops within the Send to Appian window. When the system accepts the routes, it does not save the changes in the Company profile. To change the company hours permanently, you must add them in the company profiles.
      CloseTW
      Unload Rate

Send to Appian: Route map labels clear on refresh (NSUITE-210463)

When you selected new manifests to map routes, the route labels for the prior manifest were not cleared from the map. Now the system clears any pre-existing route labels when you refresh the map.

Import Route Book: CloseTW functionality (NSUITE-210508)

The new CloseTW check box allows you to indicate whether a delivery:

  • Must be completed before a stop’s delivery window close time
    Select the check box to apply this option.

  • Can start at a store’s delivery window close time
    Clear the check box to apply this option.

The field is available for editing in the Terminal Companies window and the Route Response grid.

The RouteBook Import must accept and store the option values. The system now stores these values at the company level, instead of the route level. It stores the data in the companyltlinfo table.

Send to Appian: Use Schedule Trailer if Manifest Trailer = UNKNOWN (NSUITE-210513)

In previous versions, when you sent a manifest with a Unit ID of UNKNOWN, the system used the default values in the LTLAppianTruckCapacity General Info Table setting to populate the trailer capacity information. This information includes values for the Weight Cap, Pallet Cap, and Volume Cap fields.

Now the system can apply the values shown in the trailer profile for the trailer listed in the Schedule Details grid. If the trailer profile does not include trailer capacity information, the system uses the default values from the LTLAppianTruckCapacity GeneraI Info Table setting.

Appointment Queue

Improved performance on stored procedure (NSUITE-210241)

A severe performance issue occurred with the new Appointment Queue stored procedure. The three Left Outer Joins on the Reverence Number table caused the issue. These joins and others were converted to sub-queries, which drastically improved performance.

Appointments

Ignore contact requirement when booking appointments (NSUITE-210544)

Now, you can use the LTLIgnoreApmtRequireContact=Y General Info Table setting to bypass the contact requirement when booking appointments.

FleetConneX integration

Arriving at stops out of sequence (NSUITE-210454)

In previous versions, when a driver arrived at a stop out of sequence, updating the stops caused an exception in FleetConneX. It indicated that prior stops were not completed. Now, SystemsLink re-orders the stops automatically. This guarantees that the stop is the next stop in the sequence.

FreightOrder Import

Mapping the freight order load date (NSUITE-210550)

In previous versions, the system used the freight order’s load date for the drop on dock date. This caused some issues where the drop on dock date was greater than the delivery date in the Terminal Deliveries window.

Now, the system maps the load date to the Requested Delivery Date. As a result:

  • Routing entries show in order by date

  • The Requested Delivery Date value shows in most dispatch grids and the Contact tab in order entry.

Manifest

ETA/ETD calculations schedule Actual Arrive and Actual Depart times correctly (NSUITE-210415)

Updates to the ETA calculation on the Manifest’s Stops grid ensure that a stop’s Actual Arrival time is scheduled earlier than the stop’s Actual Depart time.

Removing Scheduled Load stops (NSUITE-210462)

In previous versions, you could not remove Scheduled Load stops in the Manifest Stops grid. This occurred when you:

  1. Assigned assets to a manifest

  2. Attempted to update the manifest’s status to Loaded to Go before removing its Scheduled Load stops
    As a result, the system prevented the update because the Scheduled Load stops were on the manifest.

  3. Used the Stops tab to remove the appropriate stop(s), but the Remove command was not activated

  4. Manually updated the manifest’s status to Empty, which should have been its current status

  5. Used the Stops tab to remove the appropriate stop(s), but the Remove command was not activated

You now have the ability to remove the stops.

Manifest driver assignments (NSUITE-210477)

Validation now ensures that a driver’s shifts cannot overlap. When a conflict occurs, the system generates a message that describes the issue.

Stops tab’s key field (NSUITE-210565)

System updates allow the ltl_manifeststops procedure to view the correct note type for the cust_ref value. This change affects the Key? check box in the Manifest Stops grid in the Terminal Deliveries window.

Miscellaneous

New License to make the LTL generic MobileComm API publishable (NSUITE-210248)

The LTL generic MobileComm API is now a licensed feature (TMWLTLMOBCOMMAPI license). It applies to LTL versions 2019.3 and later.

For information on purchasing the license, contact Trimble Support.

LTLBackGround Service (NSUITE-210470)

In addition to the LTLEDIService, recalculation of the ETA logic is now available in the LTLBackGround Service.

Incorrect Dwell calculation for Hotel and Diversion stops (NSUITE-210552)

Hotel and Diversion stops used the same dwell calculation as regular stops. Now, these stops use the appropriate dwell calculation.

LTL Recall API mobile message (NSUITE-210612)

The LTL Recall API returns the mobile Manifest Recall confirmation message only once when processing a manifest recall.

Manifests

Using additional fields in the manifest’s Trips and Stops grids (NSUITE-210721)

You now have access to additional fields and functionality in the Trips and Stops grids. Use the Field Chooser to add them to the grids.

  • Terminal Schedules

    • Default Driver First Name

    • Default Driver Middle Name

    • Default Driver Last Name

    • Default Driver Name
      Driver’s name as it appears in the Driver Profile

    • Default Driver 2 First Name

    • Default Driver 2 Middle Name

    • Default Driver 2 Last Name

    • Default Driver 2 Name
      Driver’s name as it appears in the Driver Profile

    • Default Third Party 1 Name
      Third Party’s name as it appears in its profile

    • Default Third Party 2 Name
      Third Party’s name as it appears in its profile

  • Terminal Deliveries - Trips

    • Driver 2 First Name

    • Driver 2 Middle Name

    • Driver 2 Last Name

    • TruETA Planned Stop Status
      Shows the TruETA’s stop status for an active trip. Values include:

      • On Time

      • Early

      • Late

      • At Risk

    • TruETA URL
      A manifest’s web hyperlink to the ALK Trip Management page

  • Terminal Deliveries – Stops

    • TruETA Last Updated
      The last time a TruETA calculation was made for this stop

Maps

Add option to determine which route labels show in LTL maps (NSUITE-210424)

LTL maps allow you to view and track trip data on a graphical map. Now you can use the LTLMappingRouteLabels General Info Table setting to determine how you want a route label to appear on a map. You can specify the type of ID or number you want to show in a label based on the setting options you select.

String1
Maps now show a new Route Label drop-down field. The String1 field allows you to specify which route label option you want to use when you first open a map. When the map is open, you can select other options as needed. Options include:

  • N (default)
    Show no labels when the map opens.
    You must select an option from the Route Label drop-down field to view labels.

  • L
    Show the label on the map’s route line.

  • C
    Center the label on the map’s route line.

String2
This field allows you to determine what text to show in the labels for Appian Response maps.
Options include:

  • RI (default)
    Show the Appian route ID in the label.

  • RN
    Show the manifest route number in the label.

String3
This field allows you to determine what text to show in labels for other maps, such as those that show pickups and deliveries. Options include:

  • MAN (default)
    Show the manifest number in the label.

  • MOV
    Show the movement number in the label.

  • LEG
    Show the leg number in the label.

  • RN
    Show the LTL route ID or number in the label.

  • RD
    Show the route description (Appian ID) in the label.

MobileComm integration

Expose Route information from LTL Manifest (NSUITE-210338)

A new SystemsLink API now provides information about LTL manifests, such as the route ID, leg ID, and route description.

The LTL API method logs out a driver when there is no trip assignment (NSUITE-210453)

The LTL Driver Logout API tried to log out a driver based on a leg number. When a driver logged in and had no trip assignment, a leg number was not available. The API method now logs out a driver based on a driver’s ID.

Store route description as reference number on first stop of manifest (NSUITE-210341)

The system now stores a route description as a reference number on the first stop of a manifest. This setup allows a driver to view a route description from their device.

Order Entry

Finding a delivery time when the delivery window starts and ends within the hour (NSUITE-210648)

When a delivery window’s time started and ended within an hour, the system did not find a delivery route. For example, if the delivery time was between 11:15 and 11:45 AM. The system could only schedule delivery times in increments of one hour.

Now, you can set up the system to allow the increments to occur in less than 60 minutes. You use the LTLHoursOfOperationIncrement General Info Table setting to do this.

Slotting

Order slotting is not respecting the manifest status (NSUITE-210566)

System updates now allow order slotting to occur for a manifest with a Committed or Hold status.

Team driver logins and logouts

Improving team driver login and logout functionality (NSUITE-210471)

The LTL Mobile Comm and SystemsLink integration now allows team drivers to work as expected in a variety of scenarios.

Trimble Privacy Policy

The Trimble Privacy Policy link added (NSUITE-210381, NSUITE-210391)

The Trimble Privacy link has been added to the TMW LTL Operations login window. When you click the link, the Privacy Policy page opens in a web browser.

TruETA integration

Trip status visibility improvement (NSUITE-210436)

TruETA calculates a driver’s Scheduled Early Arrival and Scheduled Late Arrival dates and times. System updates now increase the visibility of TruETA’s calculated stop statuses for arrival and departure events. These new ETA fields are available to add to various grids in the system. You add the fields from the Field Chooser.

  • Next Stop Sequence
    The sequence number of the manifest’s first stop that has not yet arrived.
    For example if stops 1 - 4 are complete, this stop would be 5. The stop shows a status of Open.

  • Next Stop ETA Status
    The next stop’s estimated time of arrival

The grids are available in these locations:

  • Trips tab in the Terminal Deliveries window

  • Stops tab in the Manifest Editor window

Added TruETA fields to the Stops grid layout (NSUITE-210551)

Now, you can add these TruETA fields to the Stops grid in the Terminal Deliveries and Manifest Editor windows:

  • Activity Starts Date

  • Activity Ends Date

  • Customer Pickup Date

  • Customer Delivery Date

You select these fields from the Field Chooser.

Resolved issues

Appian DirectRoute integration

  • NSUITE-210254
    Updates were made to correct issues pertaining to company hours, manifests, and routes.

    • The system did not apply proper formatting to fields that display time values. The fields now show time in the HH:MM, HH:SS, or MM:SS formats where appropriate. The affected fields include but are not limited to:

      • Break Time

      • Drive Time

      • Duration Time

      • Layover Time

      • Unload Time

      • Wait Time

      • Work Time

    • The Total Work Time calculations in the Manifest Trips grid were inaccurate.

    • The system did not calculate mileage during the initial creation of a manifest from a schedule. This occurred because terminal stops were not included in the static stop routes.

    • In the Route Response Route tab, the system imported the Arrive Time value instead of the Departure Time value.

    • In the Manifest Stops tab, the system did not add the Drive Time value to the Cumulative Work Time value.

    • When using Send to Appian on a new manifest with no orders, Accept routes did not update the trip.

    • The Building Key in the Route Response window’s Stops grid was updated to show as a check box. The TimeZone field now shows values in a simplified format (PT, MT, CT, and ET).

    • In the Route Response Route grid, the midnight close time of 23:59 should have shown as 24:00. When the company profile shows 23:59, the system now passes 00:00 to Appian. The system still shows 24:00 in the Route Response window. Manually setting a Close value to 24:00 passes 00:00 in the background. The change affects Close times only, not Open times.

    • In the Route Response Route grid, the system now converts arrival and departure times based on the local terminal’s time zone.

    • The Terminal Deliveries window did not calculate Drive Time correctly.

    • The system increased the manifest Work Time value each time you clicked, Refresh ETA/ETD.

    • When using Send to Appian, Apply results, the system did not recalculate the Drive Time value.

  • NSUITE-210445
    Import Route Book: During the import, the master order copy could lose its master order status, MST. The order would then show in the dispatch grids. This occurred under these conditions:

    • You did not use the validate master orders option during the validation step.

    • The master order copy failed to save.

  • NSUITE-210446
    Send to Appian: When you clicked the Update Dates button to change the Effective Date and Expiry Date, only one of the two dates updated. This caused an issue where the current date range overlapped the new date range. As a result, the date validation process failed.

  • NSUITE-210458
    Send to Appian: New editable fields did not work as designed when you used Send to Appian from trips grids. Affected grids and fields include:

    • Route Response grid

      • Dispatch Date

      • Close 1-5

      • Open 1-5

      • Truck EDay

      • Truck LDay

    • Unassigned Stops grid

      • Volume

      • Weight

    Additional changes were made to include these updates:

    • Field values representing time show in 24 hour format.

    • The ENTER key no longer closes a window.

    • The ESCAPE key no longer closes a window.

  • NSUITE-210499
    Route Response window: System changes resolve the following issues:

    • You assigned a shift to the Driver 1 and Driver 2 positions. Then you tried to assign Driver 2 to the Driver 1 position, which caused an error. The error message that opened did not identify the nature of the problem.

    • You created a shift with Driver 1 and Driver 2 assignments. Then you created another shift where Driver 2 from the previous shift was assigned to the Driver 1 position. The system allowed the assignment and showed no error message. The system should not have permitted the second shift to be created.

    • Team driver assignments were not validated properly.

  • NSUITE-210514
    Route Response window: These changes are completed:

    • All Appian formatted string times were changed from PT##H##M##S to just HH:MM or a decimal value where applicable.

    • Truck Break Start/Duration columns are now formatted as HH:MM.

    • The Route row’s Truck Start Time and Truck End Time fields were removed.
      The field values did not provide useful information.

    • The Leg row’s Dist column was removed.
      It was a duplicate of the Distance column, which showed the same information.

    • The Stops.ID field was renamed to the Stops.AltID field.
      It is a better representation of the actual field value.

    • The label file drop-down list for LghType1-4 was added to the Route row.
      In previous versions, these entries showed as plain text fields.

    • The Count2 field (Total Hazmat pounds) that is visible at the Stop level is now also visible at the Route level. At the Route level, this field shows a sum of Count2 values for each stop row on a route.

    • A validation check was added to the RouteBook Import.
      This change should help reduce the number of pickup earlier than delivery errors received.

  • NSUITE-210547
    The Manifest Stops ETA and ETD field values for the terminal HXT event did not reflect DirectRoute changes. This occurred when the changes returned through the Send to Appian process.

  • NSUITE-210576
    Send to Appian: An Execution Timeout Expired error occurred when you:

    1. Selected two (delivery) manifests where each had scheduled stops and a Driver 1 assignment

    2. Clicked Send To Appian

  • NSUITE-210589
    Send to Appian: The ETD times did not save correctly to a manifest after you applied Send to Appian changes. The Unload Time and ETA values showed in the stop fields, but the ETD value did not.

  • NSUITE-210601
    Send to Appian: When using Send to Appian, several issues occurred that involved the Earliest and Latest field values. These changes resolved the issues:

    • In the Terminal Deliveries window, the Earliest and Latest date values show in the Route Response grid correctly. They are formatted to show the date only, not the time.

    • The fields in the Truck Late Finish grid are formatted to show hours and minutes (HH:MM).

    • In the Terminal’s Schedules Legs grid, the EarlyStart, NormalStart, LateStart, and LateFinish time values display with the proper formatting (nn:nn). For example, 1600 now shows as 16:00.

    • The issue in the Terminal Routes window that showed the "No stops have been found to optimize" error message was corrected.

    • The issue that caused an error message to occur when using the Filter feature in the ScheduleGrouping field was corrected. The field shows in the Company Hours of Operation Overrides grid.

  • NSUITE-210613
    Import Route Book: The import process converts stop times based on a terminal’s location and time zone. For delivery locations that were not in the same time zone as the terminal, the import did not adjust the stop times appropriately.

Appointments

  • NSUITE-210243

    • When booking an appointment, an error occurred. It stated, "The added or subtracted value results in an un-representable DateTime. Parameter name: value."

    • When booking an appointment outside of a company’s hours of operation, the system did not provide an option to apply a special handling code for an Appointment Delivery charge.

Invoicing

  • NSUITE-205258
    The system added an extra invoice detail line on an order that you could not remove. This occurred when you:

    1. Created a new order

    2. Created a freight line and assigned a manual charge to an invoice

    3. Created an advanced copy on the order and selected freight and invoice details

  • NSUITE-210485
    The Credit Memo on F-Invoices (Invoice Consolidations) was not calculating the Average Fuel Price correctly.

Manifest

  • NSUITE-205315
    Entering improper values for the Origin and Destination Rail Terminals placed the manifest in an unusable state. This prohibited you from un-assigning the move from the rail reservation. As a workaround, you can create a new manifest and assign the order to it.

  • NSUITE-210242

    • Child terminal manifests
      The linked Terminal functionality no longer showed manifests from child terminals in the parent terminal’s Pickups window. Selecting the Linked Term check box, in the Manifest Trips tab, activates the functionality.

    • Trips grid changes
      Changes were made to the manifest’s display criteria for Trips grids.

    • Multi leg manifests
      In previous versions:

      • Completed legs were removed upon completion. They now show in the grid.

      • Criteria to load a manifest leg had a restriction to load only legs pertaining to a specific terminal. Now, when a manifest spans multiple terminals, all legs show in the grid regardless of their terminal association.

    • Terminal truck load moves
      The Terminal Truck Load Moves window did not show any manifests in the Trips grid for existing manifests. This occurred when you set the grid’s Manifest Type field value to Truck Load & Linked.

  • NSUITE-210388
    When you created a manifest from a schedule, it applied the SUL (Scheduled Unload) events correctly. If you deleted the first of multiple orders with LUL/DUL events, the system set the LUL events to SUL. This change should not have occurred until the last order was removed.

  • NSUITE-210414
    When you used the Mass Status Change to set a trip to the Loaded to Go status, the RTT event was generated. When the driver arrived at the terminal at the end of his manifest, he received a text message about a Dispatch Horizon error. It stated, "There are no planned stops on the dispatch horizon for the leg (xxxxx)."

  • NSUITE-210632
    A manually inserted SUL event had the ord_hdrnumber populated on the matching Order Assignment. This caused the order’s routing to become corrupted.

    Send to Appian: The Hours of Operation were different when a manifest was generated from a schedule instead of SUL stops that were inserted manually.

  • NSUITE-210634
    Removing a driver from a leg in the Manifest Trips grid intermittently caused a Resolve date conflict dialog box to open. When accepting the terms to remove the driver, the leg date was set to the driver’s shift.

  • NSUITE-210649
    The manifest cloning process picked up expired schedules because it ignored effective and expiry date restrictions.

Mileage lookup

  • NSUITE-210495
    You can set up the [MileageInterface]DefaultLookupBy INI setting to calculate mileage between origin and destination locations. When you used the setting to calculate mileage based on latitude and longitude coordinates instead of ZIP Codes, a performance issue occurred. Performance was most affected when you used the Appian upload or download process to create hundreds of master orders.

Miscellaneous

  • NSUITE-210431
    Modifications were made to the SQL TMWTripExtractDetails table to include the Manifest Status column.

MobileComm integration

  • NSUITE-210439
    The driver Log In process did not find the driver’s correct shift.

  • NSUITE-210487
    A duplicate shift error occurred when a driver followed these steps:

    1. Logged in when no loads were assigned

    2. Took a break and then logged out

    3. Logged back in

  • NSUITE-210549
    The LTLShiftService showed duplicate Assign Trip messages. This occurred when:

    1. The driver logged out of their shift

    2. The dispatcher assigned a trip to the driver

    3. The driver logged back into their shift

  • NSUITE-210581
    The “Exception: Index was out of range” error that a driver received when logging in did not identify the reason for the error accurately. The driver’s shift had expired.

    When a driver’s shift is unavailable, LTL Dispatch and the LTL API should allow you to assign a driver to a manifest. In this case, the systems prevented the assignment.

  • NSUITE-210688
    When the second driver logged in for a trip, a login error occurred.

Slotting

  • NSUITE-210250, NSUITE-210536, NSUITE-210554
    All orders on a particular route are given the same load date in the Freight Order Import. This presented a problem for routes that spanned multiple days. It created the possibility that a route could be associated with an order incorrectly.

    For example, consider that all routes numbered 100-199 were configured to dispatch on Sunday (depart the terminal).

    • The load date in FreightOrder was the following Monday.

    • Your customer delivers on Sunday and Wednesday.

    • Since the load date fell on Monday, the Wednesday route was associated with the order.
      The system did not recognize that the order should have applied a Sunday date rather than a Monday date.