2020.1

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.

Warnings

Cancel order/trip feature warning

Starting in version 2020.1, the user interface for the cancel order/trip functionality has changed. Several enhancements were made to make the process easier and more intuitive. Also, the same Cancel Trip/Order window is now used in both Order Entry and in the Trip Folder.
For more information, see Canceling an order in version 2020.1 and later.

User level record security

Starting with TMW Operations version 2019.1, there is a functional change that will affect customers using custom views on Company Planner, Brokerage, or Covering boards that rely on User Level Record Security. Affected customers may need to contact Support for assistance before upgrading. See the User level record security resolved issue for details.

Minimum technical requirements for 17.50 or higher warning

To upgrade from a build lower than 17.50 to 17.50 or higher, you must follow these steps.

  1. Notify your Support team that you will upgrade. (As noted in Step 4, they will need to work with you to complete the installation process.)

  2. Verify that your environment adheres to these minimum technical requirements:

    • Microsoft .NET Framework version 4.6.2 must be installed.

    • Client operating systems must be at Windows 7 SP1 or higher.

    • Server operating systems must be at Windows Server 2012 or higher.

    • In addition, verify that your system adheres to the additional requirements listed in the General requirements section for the build you are upgrading to.

  3. Run the TMW Operations installation program.

  4. Before any users attempt to use TMW Operations, call your Support representative to have them update your Planning Worksheet boards.

Trimble Transportation has added columns to the system default Planning Worksheet views to enhance the inline editing feature. These columns also must be added to all custom views. Support will perform this step for you at no cost.

Case sensitive passwords warning

Starting with V.17.50, the system treats all passwords as case sensitive. This includes existing passwords.

This change affects how you log in with an existing password:

  • If your password was created with [Misc]CaseSensitivePasswords=OFF in your TTS50, you must enter that password in all upper case characters.

  • If your password was created with [Misc]CaseSensitivePasswords=ON in your TTS50, you can enter that password as you originally recorded it (case sensitive).

Requirements

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

  • TMWSuite®
    You must be using TMWSuite V. 2020.1.0.0009 or later.

  • 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 2008 R2 or later

  • Microsoft SQL Server®

    • Microsoft SQL Server 2012 or later

      Note: SQL Server 2014 and SQL Server 2016 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 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.

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

Enhancements

Brokerage

Sending multiple load confirmations from Advanced Carrier Selection (ACS) window (NSUITE-208072)
You can now send multiple load confirmations by print, fax, or email. Use the Carrier Mass Assignment feature in the ACS window to send them.

To be mass-assign compatible, selected trip segments must:

  • Have the same origin and destination

  • Have the same number of stops

  • Be set to Available status

After clicking Save and Send, the results of the load confirmation appear in the Selected Loads tab.

To use this feature, you must have [Brokerage]MassACSAssignment=Y in your TTS50.

The ACS Carrier Mass Assignment setting relocated to [Brokerage] section of TTS50 (NSUITE-209491)
The [ApplicationToggles]MassACSAssignment setting is now located in the [Brokerage] section of the TTS50.

State Chooser map added to the Origin field and Planning Worksheet restriction options (NSUITE-209527)
The State Chooser feature has been added to these locations:

  • Planning Worksheet
    The State field in the Shipper and Consignee sections on the Trips Board Definition window
    The Restrict button opens this window.

    The Origin field on the External Equipment tab.

  • Company Planner
    Several boards include the Company Carriers and External Equipment tabs. The Origin field on those tabs now has this functionality.

The State Chooser feature is available when you have [TMWSuiteAddins]EnablePWStateChooser=Y in your TTS50.

Common Dispatch Features

Displaying the Item Code on the Profit and Loss tab (NSUITE-207923)
You can create invoice details or pay details for a trip on the Profit and Loss tab in TMW Operations.

By default, the Item Code field in the Profit and Loss tab shows the value recorded in the Description field for the pay type or charge type.

Now, you can set up your system to display either the Item Code or the Description in the Item Code field.

Enhancing cancel order/trip functionality (NSUITE-208266)
The user interface for the cancel order/trip functionality has changed. Several enhancements were made that make the cancel process easier and more intuitive. Also, the same Cancel Trip/Order window is now used in both Order Entry and in the Trip Folder.
Link to topic: Canceling an order in version 2020.1 and later.

eManifest

Auto Process Console creates 309 documents automatically (NSUITE-202581)
eManifest’s Auto Process Console allows you to create 309 board crossing documents automatically. This functionality applies only to trips having a single origin, single SCN loads. It cannot be used for LTL, consolidated moves, or double trailer moves.

You must be using TotalMail to use this feature.

Setting added to allow file creation when validation warnings are received (TSI-359)
Previously, the eManifest Auto Process Console was preventing a file from being created when there were validation warnings. It considered a warning message to be the same level as a critical item. As a result, the application was marking some moves as being in error status instead of having them pass validation.

Now, you can set up the system to control whether warning messages are bypassed. The error messages are logged.

Warning: If you elect to bypass warnings, be sure to review the log file for failures. It is your responsibility to provide files that will not be rejected by the border agency.

Solutions for Cleo mapping added (TSI-513)
Previously, eManifest header and trailer record formatting supported mapping to Kleinschmidt. Now, you can set up the system to provide header/footer mappings for Cleo. This setup affects these files:

  • 309 - Customs Manifest

  • 358 - Customs Consist Information (Trip)

  • 353 - Customs Events Advisory Details

Fuel Maintenance

Improved TCH/EFS Interactive card import performance (TSI-195)
In previous versions, importing cards could take 6 or 7 seconds per card. Now, the process is faster because the system only gets the information needed to create the card in the Card Maintenance window.

Support for Comdata’s 10-character tractor IDs (TSI-498)
Comdata recently changed their formatting to allow tractor IDs to be up to 10 characters. Previously, the IDs were limited to six characters. Now, Fuel Maintenance allows tractor IDs of up to 10 characters to be recorded for a unit.

Planning Worksheet

Mass Status Change window now allows for reverting planned orders and canceling multi-job orders (NSUITE-209437/NSUITE-209445)
To make status changes to multiple orders, the Mass Status Change window now allows mass cancellation of multi-job orders. You can also revert multiple Planned orders back to Available status.

Trimble Dispatch Advisor feature now available (NSUITE-207665)
Trimble Dispatch Advisor (TDA) is a load-planning aid. It is available in the Planning Worksheet. TDA recommends the drivers and tractors that are a better match for specific loads. Recommendations appear in a results grid that:

  • Identifies a primary match

  • Ranks other suitable options

  • Provide reasons why other options are judged incompatible

Using an automated tool like Trimble Dispatch Assistant helps you make efficient load-planning decisions.

TDA helps you:

  • Efficiently match the right driver to the right freight

  • Reduce driver churn

  • Reduce compliance-related violations

  • Avoid problems with load restrictions

  • Ensure a driver has sufficient hours to meet delivery windows

Trip Planner

Bypassing date/time validation errors in the Quick Edit window (NSUITE-209502)
Now you can set up the system to allow you to change trips in the Quick Edit window when there are date/time validation errors. You can manually update all trips as needed.

TruETA

SystemsLink function generates the trip segment TruETA comment (NSUITE-207548)
The TruETA SystemsLink service now contains a function that returns Comment and Status values when processing a trip segment. The Trip Folder and Planning Worksheet call this function. The values are stored on the trip segment.

TruETA Preplanning

Inbound resource information now calculated and displayed in Trips grid (NSUITE-208391)
Previously, if you wanted to pre-plan a trip with a driver in the Planning Worksheet using TruETA, you had to:

  1. Select a trip in the Trips grid.

  2. Select a driver in the Driver tab.

You had to switch tabs from the Inbound tab to the Driver tab to complete this action.

Now, you no longer need to switch between tabs to pre-plan a trip with a driver.

When selecting a trip in the Trips grid and an asset in the Inbound grid:

  • The system calculates TruETA based on the driver’s information from the Inbound grid.

  • The Driver ID appears in the TruETAPrePlan column in the Trip grid.

  • The TruETA information appears in a ToolTip.

You can use either the Inbound or Driver tab to determine driver availability.

Resolved Issues

Brokerage

  • NSUITE-206747
    After selecting the Company Planner grid’s filter row, an error occurred when clicking a custom menu command button on any row.

Commodities

  • NSUITE-208122
    If you entered a note on a new, unsaved commodity profile, it was applied to every commodity profile.

Company Planner

  • NSUITE-208113
    When filtering the Brokerage Covering board, customers received an error when clicking the Cover button.

Credit Check

  • NSUITE-208170
    When the Copy Rates checkbox remained cleared for a copied order, the system would bypass the Credit Check feature for the Bill To. Users would not receive a warning if the Bill To on the copied order was over the credit limit.

Database

  • NSUITE-206429
    When you create an order in TMW Operations, the lgh_createapp field is set to .NO. If you canceled the order and then made it available again, the system sets the lgh_createapp field to NULL. This caused loads to drop off Company Planning boards. This fix sets the lgh_createapp field back to .NO when the order becomes available.

  • PB-200374
    The stored procedure, UtStopsConsolidated_FingerprintAudit_sp, was not recording updated values for these columns:

    • stp_departuredate

    • stp_arrivaldate

    • stp_reasonlate

    • stp_reasonlate_depart

EDI

  • NSUITE-207704
    Inbound EDI orders that have the same arrival and departure date and time for every stop caused issues on the Planning Worksheet. The system listed the OriginCity as the FinalCity. It now adds one minute between each event arrival and departure when details are the same.

  • NSUITE-209538
    The system showed an error when you retrieved a Pending order in the Trip Folder. This happened if you were using an older Stops grid layout that did not have "LegAssetAssignmentButton" in the MoveStop field chooser. The error stated, "Key not found: LegAssetAssignmentButton."

  • TSI-438
    If any stops on a trip were deleted, the system would not allow updates from 204s. Now, if stops were deleted by a 204, the trip will be updated.

  • TSI-463
    The system was not creating X6 Statuses for split and consolidated trips.

  • TSI-494
    Tender expiration date stopped working, defaulting to 12/31/49. This prevented dispatchers from knowing when a tendered load would expire.

eManifest

  • TSI-441
    The eManifest ACE Freight tab showed only move-level information for turnpike double trip segments that contain a border crossing. It should also show order-level freight information.

  • TSI-442
    The ACE Company Information tab did not show information for turnpike double trip segments with a border crossing.

  • TSI-443
    The ACE Trip Profile tab showed incorrect information for turnpike double trip segments with a border crossing. This issue applied to truckload and LTL moves.

FreightBoard

  • TSI-432
    The application was allowing equipment types to be posted incorrectly. This happened if you tabbed to different fields in the window and lost focus on the Equipment Type field. It was set to N-None.

Fuel Maintenance

  • TSI-94
    Importing EFS fuel card produced an object reference error. This happened if the system failed to populate the mpp_lastfirst calculated field from the first and last name entries in the driver’s profile.

  • TSI-451
    The system was ignoring the [FuelServ]PreventOwnerOperatorReeferPayDetail setting. It always created reefer pay details for owner/operators.

  • TSI-454
    EFS contract call was being made more than once.

Intermodal

  • NSUITE-209422
    Errors occurred when saving an order with a Final Drop Loaded (DRL) stop in Intermodal Order Entry. If you switched the Service field from Live to Drop and then back to Live, the system was attaching an extra DRL stop after the Chassis Drop (CDRP) stop.

Load requirements

  • PB-200722
    Performance issues involving triggers on the loadrequirement view and loadrequirementtable were improved.

Mileage

  • NSUITE-208385
    When using RANDDLL, the system was not calculating RAND mileage within the Shortest (HHG) option.

  • NSUITE-209505
    The system stamped the wrong mileage in the stp_ord_mileage_mtid table, which caused reporting errors.

Order Entry

  • NSUITE-203545
    When setting a cancelled order back to Available status, the system did not reset the Invoice status to Pending.

Performance issues

  • NSUITE-207804
    When the Trip Planner was refreshed, memory issues occurred that would cause the window to crash.

  • NSUITE-208262
    Performance issues involving editing invoice charges on the Profit and Loss tab have been improved. The tab is available in Order Maintenance and the Trip Folder.

Planning Worksheet

  • NSUITE-205447
    In some scenarios, the Sort Trips Closest to Power command returned inaccurate air mileage.

QuickDesigner

  • NSUITE-209552
    When you applied changes to a tab, reset the tab, and then saved the new layout, the cleared items still appeared in the new layout.

SSRS Reports

  • NSUITE-207369
    If separate reports were added to newly created tabs, the only report that worked was located on the main tab.

System updates

  • NSUITE-206854
    To avoid conflicts with updating orders, the system now compares uppercase values and evaluates them in these tables:

    • assetassignment

    • orderheader

    • legheader

    • legheader_active

    • event

Trailer profile

  • NSUITE-209468

    An error occurred if:

    1. You clicked a link within a web browser added using QuickDesigner

      and

    2. You used the browser to pass through a variable.

    Clicking the Imaging tab on the trailer profile that retrieves relevant trailer documents is an example.

Trip Folder

  • NSUITE-208190
    When manually adding a check call on the Trip Folder’s Check Calls tab, the system was not activating the Save button.

  • NSUITE-209394
    Adding pay to a completed leg produced an error message if the trailer from that leg was started on a later leg. The system incorrectly determined that the later leg occurred before the completed one.

Trip Planner

  • NSUITE-208155
    When reassigning loads to drivers, the system no longer removes the Begin Empty stop from the first driver’s first trip.

  • NSUITE-208251/NSUITE-208409/NSUITE-208410
    Previously, when updating a planned trip’s End Location in the Quick Edit window, the system also updated the Begin Empty stop for the driver’s next planned trip. However, after changing deadhead locations for current and future trips, the system did not adjust stop arrival and departure times correctly. Time conflicts could occur between the end of a trip and the beginning of the next trip.

    Date and time recalculations are now more accurate. The system also updates deadhead locations when trips are in Dispatched and Started statuses.

  • NSUITE-208253
    Multiple users can now use the same planning board without encountering the "Existing Stop Asset Not Found ID ####" error.

  • NSUITE-208346
    Removed shift validation for driver changes on trips that have not been assigned to a shift.

  • NSUITE-209403
    You use the Optimize Solution Review window to commit an optimization solution. When you do, the system now runs leg shift resequencing automatically. This occurs on all current and upcoming legs.

  • NSUITE-209690
    An issue occurred when using the Trip Planner’s Quick Edit window to adjust an End Empty location on a Planned or Started trip. The system would overwrite the arrival time of a subsequent actualized stop. It would change that time to the driver’s shift start time.

TruETA

  • NSUITE-207969
    Planned trips in TruETA are trips that have a TruETA Trip ID in the truetamessagelog table. These trips did not receive Planned Start Location updates. This occurred when the driver or first stop location was changed. Now, until trips are started in TruETA, the system updates the Planned Start Locations when changes are made.

    Note: This does not apply to the Planning Worksheet Preplanning since there is no trip stored in TruETA.

  • NSUITE-208332
    An error occurred when sending TruETA the TMW apocalypse date. The date appears in the StopScheduledLatest field. Now the system changes the TMW apocalypse date (2049-12-31) to the TruETA apocalypse date (2037-12-31).

    Note: To use the Earliest Date and Latest Date fields when sending data, you must have [MobileComm]ETAArrDepDeterminesLate=L in the TTS50 used by SystemsLink.

  • NSUITE-208464
    TruETA logic sent all check calls for a leg each time it updated the trip position.

    This led to:

    • Duplicate check call entries

    • Cluttered the map

    • Disrupted ETA calculations

  • NSUITE-209432
    The ETSDBMods.sql file included with SystemsLink was missing a stored procedure and General Info Table setting. In addition, the default value for TruETALimitTrips is now set to 14 days (336 hours) instead of zero.

TruETA Preplanning

  • NSUITE-208211
    WorkCycle was not updating the proper log tables and did not save information to TruETA.

  • NSUITE-209434
    The Planning Worksheet preplanning process incorrectly identified drivers as being ineligible for trips. This occurred when the load’s only requirements were carrier requirements.