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

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

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

EDI

Use Hours Out and Hours Back with Date range to retrieve orders on EDI tab (NSUITE-208133)

In previous versions, the Planning Worksheet’s EDI tab, like all the tabs, retrieved trips using a date range. A user could manually enter the dates. If the user did not enter the date range, the system would use the entries in the Hours Out and Hours Back fields to determine it. The stored procedure used to retrieve data for the EDI tab did not use a date range. It used the hours out and hours back values. It treated the lookup as if the Hours Out and Hours Back fields had the default values of 0 (zero) which equals 1,000,000 hours or 277 days.

Now, the system accommodates using a date range. It translates the range to the number of hours back and the number of hours out.

Use multiple types of check calls for location reporting (PB-200071)

Currently, EDI location reporting uses only checkcall with an event type of TRP.

Now, you can set up the system to allow multiple types of check calls.

General system setup

Using an alphanumeric prefix with order IDs (NSUITE-90432, NSUITE-94043)

The first time you save an order, the system assigns an order ID. By default, the system assigns a sequential numeric value. The existing OrderIDFormat INI setting allows you to set up the system to append a prefix to the order number.

Now, the OrderIDFormat setting has two new options:

  • TERMINALPREFIX6

    The system appends a three-character prefix to the order ID. The prefix is determined by the RevType1 option recorded in the order header. The system uses the first three characters from the option’s Abbr column entry in the RevType1 label as the prefix. The numeric part of the order ID consists of a six-digit, zero-filled sequential number. The system starts numbering orders as XXX000001.

  • TERMINALPREFIX9

    The system appends a three-character prefix to the order ID. The prefix is determined by the RevType1 option recorded in the order header. The system uses the first three characters from the option’s Abbr column entry in the RevType1 label as the prefix. The numeric part of the order ID consists of an eight-digit, zero-filled sequential number. The system starts numbering orders as XXX00000001.

  1. This functionality is available in both Order Entry and the Trip Folder.

  2. These options are designed for use with booking terminals.

Fuel Maintenance

New fuel card vendor (INT-201479 CR-156)

Now QuikQ is a supported vendor for TMW.

Planning Worksheet

Turnpike Doubles feature supported for LTL (NSUITE-204309)

A turnpike double is a tractor hauling two full sized trailers. Because of their length, these combinations are usually restricted to turnpikes or freeways. They allow truck fleets to haul the same amount of cargo with fewer trips. The tractor and two trailers are coupled (or uncoupled) at a designated location near a turnpike exchange, often referred to as a yard.

The Turnpike Doubles feature allows for easier dispatch of turnpike doubles.

In previous versions the Turnpike Doubles feature was only supported for full truckload (FTL) trips.

Now, the Turnpike Doubles feature supports LTL (less than truckload) trips created with the LTL Operations Module.

The LTL Operations Module is a licensed add-on feature.

Removing redundant moves in the Turnpike Doubles Edit window (NSUITE-204356)

When creating a turnpike double, it is possible for the pickup location (for either trip) to be at the same location as the merge location.

In previous versions, the system always created five moves: one for each of the two pickup moves, one for each of the two-drop moves, and one for the Doubles move. It did this even when one of the pickups was at the merge location. This caused redundant moves.

The Turnpike Doubles Edit window would show these three redundant events at the same location

  • LLD (pickup) at Company A (part of Move 1)

  • XDT (drop trailer) at Company A (part of Move 1)

  • XHT (hook trailer) at Company A (part of Move 3 the Doubles move)

Now, when a pickup occurs at the merge location, the system places the pickup into the Doubles move. It does not display any events for Move 1. So, the turnpike double consists of four total moves instead of the usual five. The Doubles move will include these events:

  • XHT at Company A

  • LLD at Company A

  • XDT at Company E

Similar functionality can apply to the delivery portions of the turnpike double when either of the delivery locations is at the turnpike split location.

Resolved issues

3G-TM Rating integration

  • NSUITE-204521
    Sometimes the 3G I/S Load Data callback fails because of a null object reference when the system is loading company data.

  • NSUITE-204542
    Orphan pay details caused by 3G processing. The client sends orders to 3G multiple times and every time that the order comes back to TMW, the process creates a new leg number. The issue is that the pay details for the old leg number remain on the table and the client’s financial reporting includes the old records.

  • NSUITE-204798
    Removed a 3G Integration trigger from the company table, because it is loading updates for orders in bad states and putting an unnecessary load on the system.

Advances/Misc Labor window

  • NSUITE-204769
    Sometimes a pay detail exists for a given asset that is no longer associated with the leg stamped on the pay detail.

    The Advances/Misc Labor window can update these existing orphaned pay details, which could result in an overpayment.

Brokerage

  • NSUITE-205353
    Incorrect asset assignment when using the ACS window and Asset Assignment window to make assignments on split trips.

  • NSUITE-205654
    When you have a String1 value of Y set for the General Info Table setting CarrierWantsReloadDefault, it cause available orders to have the lgh_wants_reload on legheader_brokered set to 1. When a carrier is assigned to the order, you are unable to make modifications and save in the Advanced Carrier Selection window.

Common dispatch features

2018.4

  • NSUITE-204536
    The Edit in Dispatch flag on a pay type is not preventing a user from editing the pay detail in the Profit and Loss tab.

  • NSUITE-204855
    Fixed an issue in the Profit and Loss tab where the default quantity was not pulled correctly for manually entered invoice details.

    Now, the quantity used for manually entered invoice details is determined by the invoice detail’s unit basis. When the invoice detail’s Unit Basis is:

    • Distance, Weight, Volume, or Count the invoice detail’s quantity is based on the order’s quantity.

    • Flat the invoice detail’s quantity is always 1.

    • Something other than Distance, Weight, Volume, Count, or Flat the invoice quantity is based on the quantity recorded on the charge type.

    This change only affects manually added invoice details.

  • NSUITE-205506
    Fixed an issue that was causing trailer assignments on one trip segment to cascade to other trip segments on a split trip.

  • NSUITE-205560
    When you manually add a charge in the Profit and Loss tab, you should not be able to select any charge type with a Basis of DEL or TAX or a Basis Unit of Minimum or Maximum.

  • NSUITE-205610
    ALK Maps is placing the truck at the first check call position and not the last one.

  • NSUITE-205635
    Unable to set read-only column security on the Quantity and Charge columns in the Invoicing grid on the Profit and Loss tab.

2018.4 SP1

  • PB-200429
    Adding two splits to a trip at the same time and attempting to save corrupts the order and crashes the application.

Company Planner

  • NSUITE-205308
    Using the Auto Refresh feature on a Company Planner SQL grid causes the grid layout to reset to the user’s default each time it is refreshed. Columns that are added on the fly will be removed after the auto refresh occurs.

  • NSUITE-205702
    Fixed a memory leak in the Company Planner’s Stops grid.

  • NSUITE-205702
    Fixed a memory leak in the Company Planner Stops grid.

EDI

  • INT-201019
    Inbound 350 messages are applying multiple entries to the same trip.

  • INT-201055
    Data Exchange is timing out anywhere from two minutes to an hour a day.

  • INT-201111
    An execution timeout error occurs when attempting to access the audit information in the EDI archive window.

  • INT-201123
    Custom scripts are wiped out when importing the dx_204 script into Data Exchange.

  • INT-201445
    Importing the dx_businessrules.xml could potentially cause the edi_trading_partner table to be overwritten.

  • INT-201522
    When adding a passenger to a trip in TMW Operations or in eManifest, the system pulls the incorrect value from the label file to identify the Passenger document. This in turn causes an invalid value to be submitted to US Customs.

  • INT-201523
    The system is auto accepting 204s with UNKNOWN company.

  • INT-201528
    Sometimes DX fails to connect to the SQL server. This can result in the dx_archive_recordlock table remaining in lock status, preventing DX from processing inbound 204s.

eManifest

  • INT-201276
    When processing multiple moves, if one move has an error all moves that follow will also be marked as having an error. As a result, manifests are not created for these moves.

Fuel Maintenance

  • INT-201469
    Getting error in fuel import log when importing EFS fuel file.

  • INT-201485
    When the same transaction number is used more than once on fuel files, the action fails and does not give a proper error message.

Systemwide

  • NSUITE-205641
    System freezes when a client-side workflow changes a property on an order.

TMW-Synergize

  • INT-201550
    TMW-Synergize license not handled properly causing customer to run out of licenses.

Freight Order

  • NSUITE-205441
    User is unable to delete a Promised Date.

  • NSUITE-205443
    User unable to use Order History tab as reference to undo a mistake, because the selected row does not remain constant. In the background, the screen refreshes and jumps to first row in grid.

Layouts - Windows

  • NSUITE-205234
    Customer is unable to set up a field-level validation to prevent users from saving when the legheader.lgh_extrainfo1 and lgh_extrainfo2 fields are not populated.

Paperwork Tracking

  • NSUITE-204385
    Paperwork tab doesn’t change color when paperwork is required.

Scroll Records

  • NSUITE-205435
    Issues found in Freight Order Scroll:

  • Users allowed to type in the Status and Source field instead of picking from a drop-down list.

  • GEH generated when manually delete PickUpId and PickUpAltId.

Trip Folder

  • NSUITE-204688
    Map Column functionality to open Trip Folder by Ordernumber is not an available option.

  • NSUITE-205611
    The ALK Web mapping was not showing a graphic display of the route line (green), the check call line (red), or an icon for the truck location.

  • NSUITE-205659
    After splitting a trip in the Trip Folder, changing the company on one trip segment does not ripple to the trip segment.

Trip Planner

  • NSUITE-200799
    When unplanning a job order in Trip Planner, getting a message stating that "'CAN' is not a valid status option."

TruETA

  • NSUITE-205301
    Fixed performance issues caused by TruETA executing a query against the order header table without a Where clause.

  • NSUITE-205687
    When the TruETA license is active and the TruETA Tab is selected, retrieving a trip that does not have a valid TruETA URL value (teml_url) in the truetamessaglog table causes an error message window to be displayed.

Systemwide

  • NSUITE-204879
    Performance improvement for SQL called by TMW Operations.