2018.2

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

ALK Warning

In very limited circumstances, your system could generate incorrect mileages when using PC*MILER version 32 with any of these products:

  • TMW Operations version 2018.2 or lower

  • TMW Back Office version 2018.2 or lower

  • Fuel Dispatch version 2018.2 or lower

  • TMWSuite version 2018.2.0.0275 or lower

This problem is associated only with systems that have one of these options set in their TTS50:

  • [MileageInterface]ExOptions[x]=I

  • [MileageInterface]ExOptions[x]=X

Having either of these options set will cause Practical mileage to be computed as Shortest, and Shortest mileage to be computed as Practical.

This will not affect mileages previously retrieved and stored in the mileage table.

The issue is fixed in the next general release, such as 2018.3 for TMW Operations.

A temporary workaround to bypass the incorrect code is to do any of the following:

  • Use an additional ExOption in conjunction with the I or X option.

  • Remove the I or X option entirely.

  • Install an earlier version of PC*MILER.

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

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

3PL Billing

Editing 3PL rating rules and Allocation Rules in TMW Rating (NSUITE-203057)

TMW.Suite’s 3PL Billing feature provides 3PL companies a process for billing for their services. The feature allows you to specify unique billing rules for your Bill To companies.

Now, you can set up the system so that you can create and delete new Rating Rules and Allocation Rules for 3PL rating in TMWSuite’s Edit Billing Rate Schedule Folder.

Common dispatch features

Setting a default date range for the Asset Assignment History window (NSUITE-203185, NSUITE-201518, NSUITE-203159)

You use the Asset Assignment History window to retrieve a list of a resource’s trips for a specific date range. By default, the system pulls 30 days of data, 15 days before, and 15 after the current date.

From and To fields in the window allow you set a different date range manually for the current session. However, the next time you open the window the date range reverts to the default.

Now, you can set a different default date range, such as 30 days before and 30 days after.

Credit checking

Running a credit check only when charges change (NSUITE-203215)

You can set up your system to use the Credit Checking feature. This feature monitors customer’s accounts receivable balance to ensure that it does not exceed your specified limits.

In previous versions, the system ran a credit check every time you saved an order.

Now, the system will run a credit check only when you do one of the following:

  • Save a new order

  • Edit the charges

General system set up

Preventing the assignment of a non-board carrier and other resources to a trip (NSUITE-203273)

An outside carrier is called a non-board carrier because the activities of its resources are not tracked on the Planning Worksheet.

For maximum flexibility, the system allows you to assign a non-board carrier and other resources (driver, tractor, or trailer) to a trip.

Now, you can set up the system to do one of the following when you assign both a non-board carrier and other resources to the same trip:

  • Show a warning message, but allow the assignment

  • Prevent the assignment

  • Allow the assignment without a warning

Scrolls

Add restrictions to the Reference Number Scroll (NSUITE-203256, NSUITE-202694)

You use the Reference Number Scroll to look up orders based on reference numbers. In the scroll window, you can set restrictions to limit the record retrieval.

Now, you can set up your system to include four additional restriction fields:

  • Order Header Bill To

  • Stop Company ID

  • Order Ship Date

  • Order Invoice Date

Resolved issues

3G-TM integration

  • NSUITE-202897
    Currently, the Integration Server includes validation logic to check that 3G did not send an optimization result from the future.

    Because server clocks can be off by fractions of a second, the system will now validate to the minute instead of to the millisecond.

Brokerage

  • NSUITE-203254
    The Carrier Load Information window was prompting to save when clicking on different loads in the Company Planner.

  • NSUITE-203782
    Field Level Validations are not working and values entered for lgh_extrainfo1 and lgh_extrainfo2 are not saved.

Common Dispatch Features

  • NSUITE-201137
    When adding a cross-docked (XDL > LUL) trip to the consolidation via the Load Builder, the total size of the commodities (TotalSize) does not calculate properly.

  • NSUITE-203178
    The [Asset Assignment]AutoSelectDHEmptyEvent INI setting does not work in the Dispatch Empty Move window.

  • NSUITE-203334
    The system exhibits very poor performance when adding a new check call from the Trip Folder’s Check Calls window.

  • NSUITE-203959
    When trying to create a Dispatch Empty Move with a Shift Driver, the system tries to insert an RTP stop when it isn’t needed and won’t allow you to actually complete the action.

  • NSUITE-203982
    When a trip is flagged as an intermodal order, a user is unable to assign a trailer to a Hook Empty Trailer/Drop Empty Trailer portion of a trip segment.

  • NSUITE-204090
    When creating a split trip in the Park and Hook window, the system defaults the split after the first stop. It should default the split after the first pickup stop.

  • NSUITE-204295
    The wrong trailer is listed in the Asset Assignment window for the current segment of a split trip that has more than two trip segments and the prior segment contains no billable type stops.

  • NSUITE-204442
    When adding a check call in the Trip Folder for a split trip having different carriers assigned to individual trip segments, the system displays the wrong segment-carrier combination on the Check Call tab.

EDI

  • NSUITE-203442
    Receiving an Inbound 214 error when importing a 214 file that has a trailer ID mapped on the file.

Order Maintenance

  • NSUITE-204379
    Orders created in Order Entry for a Bill To company that has the Print Mail To checkbox selected in its company profile cannot be retrieved in the Trip Folder.

Planning Worksheet

  • NSUITE-203209
    Loads not getting set to HST correctly on legheader_active table

    After an upgrade to 2015.14_07.0590 SP7, Completed trips are not removed from the Planning Worksheet’s Inbound view.

  • NSUITE-204359
    The Save Changes dialog prompt persists after successfully combining orders in the Turnpike Doubles window.

Profiles

  • NSUITE-203211
    A user who does not have system administrator rights or access to File Maintenance is unable to load the Tractor, Driver, or Trailer profile windows by entering the ID and tabbing out of the field.

Scroll records

  • NSUITE-203435
    Scroll windows are not clearing old data when performing new search.

Trip Folder

  • NSUITE-201936
    The system no longer prevents users from changing assets on trips that have pay details assigned.

  • NSUITE-203253
    Users are unable to update the Bill To company for particular orders without an error occurring.

  • NSUITE-203395
    The system is slow to respond when updating a freight commodity from the Stops Grid in the Trip Folder.

  • NSUITE-204431
    Fixed an issue that was preventing the cross dock of trips to which a Third Party was assigned.