2019.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 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

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 2019.1, check that these requirements are met:

  • TMWSuite®
    You must be using TMWSuite V. 2019.1.0.0008 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.

Enhancements

Brokerage

  • NSUITE-205867, PB-200342
    On the Summary tab in the Advanced Carrier Selection (ACS) window, you can calculate revenue, costs, and profit margins for a trip.

    Now, you can specify that certain types of charges are not included in the calculation of revenue in the ACS window in TMW Operations. This only prevents the charge from displaying in the ACS window. It does not affect the calculation of billing or pay.

    The set up includes using Quick Designer to add an exclude checkbox in the Charge Type Maintenance window.

Profiles

  • NSUITE-205797
    You can use trailer compartments when calculating the volumes on orders. Setting up trailer compartments allows you to create orders that maximize the number of gallons that will fit in a trailer. Trailer compartments also determine the products that can be included on a load. A trailer with single bulkheads can carry only light or heavy products. A trailer with double bulkheads can carry a mixture of light and heavy products.

Resolved issues

CarrierHub

  • NSUITE-205631
    When AutoRecalc was turned off for Web, the customer’s CarrierHub user was able to make adjustments to InvoiceDetails and change invoicing rates. This issue has been resolved.

Common Dispatch Features

  • NSUITE-205785
    When entering charges or pay in the Profit and Loss tab, users should be able to select the charge type or pay type by description.

  • NSUITE-205813
    Fixed issue that was preventing users from setting a payable stop to non-payable.

  • NSUITE-205814
    Fixed issue that was preventing users from setting a billable stop to non-billable.

  • NSUITE-205852
    Previously, when opening the Park and Hook window for Hook Change Trailer (HCT) events, the system had listed the original trip segment trailer in the Trailer 1 field. The system now lists UNKNOWN in the Trailer 1 field for HCT events.

  • NSUITE-206068
    When RateOrderOnSave=Y, receiving an Object Reference Error when saving trip with $0.00 Lumper Charge.

  • NSUITE-206385
    When dispatching an empty move, a GEH crash error would occur. This issue has been resolved.

  • NSUITE-206790
    System was not re-rating a trip when stop is deleted and you have [Order]RateOrderOnSave=E set. This issue has been resolved.

  • PB-200429
    Adding two splits to a trip at the same time and then attempting to save the trip corrupted the order and crashed the application. This issue has been resolved.

Order Maintenance

  • NSUITE-203381
    When building an order in Order Maintenance and adding a single order level reference number, the sequence number had a sequence value of 3 instead of 1. This issue has been resolved.

Profiles

  • NSUITE-202669
    The Accident Module on Driver Profile was not retaining the trailer. The Order Number, Move Number, and Leg Number fields are now non-editable in the Accidents tab grid (any changes must be made using the Driver Accident window), and the system only accepts valid values. If there is an order assigned, the tractor and trailer fields are not editable.

Scrolls

  • NSUITE-200029
    The Show Map feature in Company Scroll displayed the company location on the wrong continent. This feature now displays a correct, localized map of the company location.

Trip Folder

  • NSUITE-200249
    The system was unable to save an empty move with a trailer wash included. This issue has been resolved.

  • PB-200430
    The system is now updating orders that had the ord_order_source field set incorrectly.

Trip Folder/Trip Planner

  • NSUITE-206401
    Reinserted overwritten code for Memory usage improvement opportunity - DispatchLegAssetPayTos.

User level record security

  • NSUITE-203447
    When activating user level record security, performance issues existed in custom Company Planner, Brokerage, and Covering boards relying on user level record security. This issue has now been resolved with the 2019.1 release. Since this upgrade will result in a breaking change, clients may need to contact Support to resolve the issue.