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

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

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

Brokerage

Look up trips by order or move number (NSUITE-101435)

You can look up trips in Brokerage’s Carrier Load Information pane.

In previous version, you could use only the trip segment (leg) number to look up trips.

Now, you can also use order number or move number to look up trips.

E-mail confirmation template for the Advanced Carrier Selection window (NSUITE-201527)

When assigning a carrier to a trip in TMW Brokerage’s Advanced Carrier Selection (ACS) window, you can send them a confirmation message by e-mail. By default, the system sends a generic message.

Now, you can create custom messages in the new Email Confirmation Template Maintenance window.

In the template, you can specify the:

  • Subject line

  • Message body, based on data pulled from the trip

  • Carrier’s assigned to the template

    When one of those carriers is assigned to a load, the system bases the e-mail confirmation on the assigned template.

Specify whether the External Trailer checkbox is selected by default (NSUITE-103781)

In the TMW brokerage feature, you use the Advanced Carrier Selection (ACS) window to assign a carrier to an order. In the ACS window, you use the External Trailer checkbox to specify whether the trailer is company owned or owned by an external entity.

When you clear the checkbox, you must select a trailer from a drop-down list. The list contains all of your company’s trailers.

When you select the checkbox, you can enter a free form trailer ID.

Now, you can specify whether the External Trailer checkbox is cleared or selected by default.

Access the Advanced Carrier Selection window from the Carrier Load Information pane (NSUITE-200705)

In TMW Brokerage, you use the Advanced Carrier Selection (ACS) window to do the following:

  • Review or edit target profit calculations

  • Assign the carrier

  • Create and edit pay details

  • Submit a confirmation to the carrier

In previous versions, you could access the ACS window from the Brokerage board.

Now, you can access the Advanced Carrier Selection window from the Carrier Load Information pane also.

Common dispatch features

Specifying the default check call event (NSUITE-202818)

A check call is a record that lists a resource’s location at an exact date/time during a specified event.

In previous versions, when a new check call is added, the default event type Track Point is automatically assigned. If a different event type is desired, the user must manually select the event.

Now, you can set up your system to assign a specific default value to a check call upon creation.

Link to topic: Specifying the default event type

Data grids

Using logic operators with grid column filters (NSUITE-202501)

In TMW Operations, you can apply multiple column filters to a grid. This restricts the number of items that appear in the grid.

When working with two or more filters, you set the logic operator - AND or OR - for values within a single column.

Now, you can also use the Column Conjunction field to apply AND or OR between columns.

Link to topic: Adding multiple filters to a grid

Layouts - Windows

Including command line arguments in hyperlinks to programs (NSUITE-202502)

In TMW Operations, you can add hyperlinks to screen layouts in QuickDesigner. When clicked, a hyperlink can open a program, file, or webpage. You use the Add New Item feature to create a hyperlink.

Now, you can pass one or more command line arguments when the hyperlink is clicked. A command line argument can contain static text, a field value from the host window, the result of an expression, or the contents of a variable.

A new Command Arguments field has been added to the Add New Item window. It is available only when creating hyperlinks. In it, you can enter a string containing the arguments to be passed.

Notes

Preserving profile-based notes (NSUITE-102537)

You can record a note in a resource or company profile.

Previously, updating a profile-based note on an order caused the system to overwrite the note on the profile.

You can now set up your system to preserve profile-based notes. The system:

  • Allows you to specify whether the profile note should be copied to orders

  • Does not write changes to a note back to the profile.

The following profiles support this enhancement:

  • Driver

  • Tractor

  • Trailer

  • Company

  • Carrier

  • Commodity

  • Third Party

  • Pay To

Planning Worksheet

Add Priority 1 and Priority 2 indicators for secondary drivers on the Inbound tab (NSUITE-202086)

On the Planning Worksheet’s Inbound tab, the P1 and P2 indicators show whether a driver has active Priority 1 or Priority 2 expirations.

Now, you can add Drv2P1 and Drv2P2 indicators to the Inbound tab to show whether a secondary driver has active Priority 1 or Priority 2 expirations.

Trip Folder

Allow grouped stops to be moved together on the Trip Folder Stops grid (NSUITE 202802)

You can set up the Trip Folder to hide duplicate, sequential stops that occur at the same location and have the same event code.

In previous versions, grouped stops could not be dragged at the same time.

Now, you can set up your system to move grouped stops together.

Link to topic: Hiding and moving duplicate stops in the Trip Folder

Retrieve by Segment Ref # and Driver Name in the Trip Folder (NSUITE-202748)

In the Trip Folder header, you can look up trips using various ID types, such as order number, move number, etc.

Now the Segment Ref # and Driver Name are options in the drop down menu.

Link to topic: Using the Trip Folder lookup field

Resolved issues

3PL Billing

  • NSUITE-202330
    Pass thru not working on some orders (normally multi-stop).

  • NSUITE-202364
    When an order goes through the 3PL Billing Autogen process and contains only one reference number, the Reference Number type is change to Reference#.

  • NSUITE-202599
    3PL order gets stuck in 3PLHOLD.

  • NSUITE-202785
    TM Billing (3PL Billing) fails to rate/allocate the invoice details due to DB concurrency violation error.

  • NSUITE-202839
    TM Billing (3PL Billing) fails to rate when order on first stop is not the primary order.

ALK Web Services

  • NSUITE-64965
    Address validation in TMWSuite does not work if you are using ALK Web services. This PTS is for the PowerBuilder changes.

  • NSUITE-202873
    Address validation in TMWSuite does not work if you are using ALK Web services. This PTS is for the .Net TMWSuite Addins changes.

Brokerage

  • NSUITE-102688
    The Advanced Carrier Selection window is not allocating revenue to each leg of a split trip. All the revenue is showing on all legs.

  • NSUITE-105379
    When you use the top 'X' to close a company planner board, the system shows the 'Are you sure you would like to exit TMW Operations?' message. When you click 'No' the system clears the company planner board. It should return you to the populated company planner board.

  • NSUITE-105550
    When a change in the Advance Carrier Selection window affects only the legheader_brokered information, the system should save only to the legheader_brokered table.

  • NSUITE-105578
    In the Advanced Carrier Selection window, the Carrier Contact shows only the last name when selected from the contact window. If it is defaulted in, it shows the first and last name.

  • NSUITE-200671
    Carrier pay details from prior trips are being associated to new trips when carrier pay is added via the Advances/Misc Labor window.

  • NSUITE-202448
    From the Brokerage Company Planner Board a "Subquery returned more than 1 value" error is thrown when retrieving Company Carrier information for carriers with multiple contacts or carriers that share an ID with a company with multiple contacts.

Carrier CSA

  • NSUITE-202596
    When you open the inquiry window the provider should default based on the [Misc]DefaultCarrierCSA= setting. It does not.

Common Dispatch Features

  • NSUITE-105474
    Client is getting a GEH error every time they consolidate loads. The orders are still consolidated, but the error produces every time.

  • NSUITE-201644
    When attempting to remove all orders from a consolidated movement with greater than 40 orders, a GEH error is thrown.

  • NSUITE-202508
    When a user does not have the ability to delete pay, the option to delete pay should not be available from the UI. The user would not be able to un-assign the carrier from the trip due to the existence of the pay details.

  • NSUITE-202598
    You receive an error in the Maintain Tractor-Driver Assignment window when the window opens with a Null (not Unknown) value in the Tractor or Driver field.

  • NSUITE-202800
    Load Builder timeout issue

  • NSUITE-203343
    When copying a master order where the stop dates are the Genesis date (01/01/50) the dates on the copied order do not get updated to the new start date entered in the Copy Order/Trip window.

  • NSUITE-203357
    Row Level Security is not working properly for various Instant best-match fields.

EDI

  • NSUITE-202837
    TMW’s carrier EDI 214 process does not respect TMW’s date rules and is changing dates on the LLD without updating the LUL. This problem occurs with arrivals, departures, and more importantly appointment times.

Mapping

  • NSUITE-203005
    The check call mapping does not show the red line between the check call points which are represented by blue pin icons.

  • NSUITE-203042
    The Position Reports map which displays check call points on the ALK web map displays only the trip route associated to the first trip segment of a split trip.

Notes

  • NSUITE-105375
    When attempting to set a screen layout on the Company profile’s Notes tab, the layout is not defaulting as it should.

  • NSUITE-105380
    The Send to Driver (TM Send) value on order-based notes is not copying correctly from the Company Profile to the company’s orders.

  • NSUITE-105509
    Order-based notes are being duplicated when copying an order.

  • NSUITE-105521
    Profile notes set up to auto copy to order are being re-copied if they had been previously auto-copied but deleted.

  • NSUITE-105600
    Auto copy notes functionality creates an issue where empty movements cannot be retrieved or saved.

  • NSUITE-105603
    Order-based notes for third parties are not being copied to orders as expected.

Planning Worksheet

  • NSUITE-202731
    The Mass Status Change window prevents the cancellation of an order that has an InvoiceDetail record associated to it.

Profiles

  • NSUITE-104419
    Assets (carrier, driver1, and driver2) are not defaulting from the tractor’s profile.

  • NSUITE-105359
    Setting the cmp_invoiceimageflag (set up from label Invoiceimageflag) in the company profile does not update the companyimaginghandling (set up from label ImagingHandling) table. The companyimaginghandling table is used by imaging vendor within this stored procedure (image_invoicedata002_splong) to handle the output for the invoice.

  • NSUITE-200294
    Error received when adding a commodity.

  • NSUITE-202503
    In the City profile, the L (Latitude/Longitude) button uses normal city name instead of the mileage vendor’s city names.

  • NSUITE-202504
    City Profile ALK validation fails to indicate ALK entries is valid even after selecting a valid ALK entry.

  • NSUITE-202505
    Company profile ALK validation is failing to show any information in Matches dialog.

  • NSUITE-202506
    ALK MVS performance issue while working in city profile

  • NSUITE-202507
    City profile ALK/MVS validation does not use zip code if provided. This can result in performance issue when validating.

  • NSUITE-202817
    If an asset profile has a single qualification/accessory record and that record is removed, the Remove button is appropriately updated to a disabled state.

When opening a different asset profile, which also has a qualification/accessory record, the Remove button will remain in a disabled state and the qualification cannot be removed.

  • NSUITE-203677
    When creating a Pay To for a carrier, the city/state field is changed to unknown when focus switches to Tax ID or Tax ID Type

Scroll Records

  • NSUITE-200026
    When restricting by the Bill To company in the Order Scroll, the system returns trips where the Bill To ID is LIKE the ID instead of EQUAL to the ID.

  • NSUITE-202395
    The Order scroll times-out when retrieving only by carrier profile and date restrictions.

  • NSUITE-202587
    The Team Lead restriction within Tractor Scrolls is not working. No matter what is selected, all tractors are retrieved.

TotalMail

  • NSUITE-200555
    The customer will often pre-plan a driver on his next several orders and transmit load assignments. When attempting to send the second load assignment via the Operations > Mobile Comm > Load Assignment command, it brings up the current time in the Deadhead Information area instead of the end time of the prior trip. This gives us a date/time conflict error even though no dead head stop is being added to the trip segment.

  • NSUITE-200615
    Client encounters deadlock errors while in Trip Folder.

  • NSUITE-201452
    When transmitting a load assignment using the Mobile Comm > Load Assignment command, the existing arrival/departure times of the stops are incorrectly being updated to current date and time.

Trip Folder

  • NSUITE-84933
    When using the setting to retain the trailer links to each other, the system is not retaining the links.

  • NSUITE-104889
    The customer is unable to insert an EBT event after a DMT event when a trip is split. An event code validation error stating that an EBT occurred before a begin bobtail event (BBT, IBBT or a Drop event expected prior to this event) prevents the save of the order.

  • NSUITE-105572
    In TMW Operations, you will get a GEH error, when you have more than five options in the CompanyImagingHandling table.

  • NSUITE-105635
    Customer is storing date/time data in the lgh_extrainfo3 field. The value for this field is getting set from several different places (UMPP, APP, somewhere else) and is getting set to different formats. Since the lgh_extrainfo3 field is a string, the different formats is causing TMW Operations to think that the value is changed when retrieved into the data objects since the default string format of the date is not the same as the string format stored in the lgh_extrainfo3 fields.

    This is causing the app to think the Trip has changed in the trip folder. So it asks users to save even if no changes were actually made. It’s also causing a problem with EDI, since users cannot create EDI 204 messages once the Order is invoiced - it thinks the Order needs to be saved before the EDI can go out, but the user isn’t allowed to save because of the Invoice status set the lgh_extrainfo3 (via SQL) value on a leg to a string format other than ""mm/dd/yyyy hh:mm am/pm "".

  • NSUITE-200455
    After adding a Begin Empty split to a trip, the event code for the DMT stop cannot be altered. The Event Code combo-box is not editable.

  • NSUITE-200506
    The Invalid Commodity Validation is preventing the assignment of a trailer if it was associated to an empty segment (HMT/EMT) on a trip that hauled a commodity that requires a trailer wash.

  • NSUITE-201785
    When you have [Dispatch]BlockEditLevelAfterSTL=LEG set, and the first leg of a trip is completed and settled, the Trip Folder locks all legs. It should lock only the first leg.

  • NSUITE-202023
    When you rearrange stops in Trip Folder, the system overwrites stops instead of rearranging them.

  • NSUITE-202119
    After invoicing a trip that has a stop with an event code of DTW (Drop Trailer for Wash), users can change the driver on the trip.

  • NSUITE-202600
    When you have CheckProductCompatibility=Yes and try to change the arrival time at the shipper, you received an error message.

  • NSUITE-202808
    After Cross Docking, unable to consolidate drop stops.

  • NSUITE-202904
    The group stops functionality is not updating stops correctly when there are more than two stops in same location.

Trip Planner

  • NSUITE-83447
    Error message thrown when attempting to edit driver schedule. Introduced by memory leak fixes.

  • NSUITE-98013
    In scenarios where an order starts with a BMT > DMT > HPL stop sequence, the Trip Planner is ignoring the trailer that is planned on the Driver’s schedule for the BMT event and is instead pulling a trailer off a prior shift.

  • NSUITE-104396
    In Trip Planner, dragging a trip in which the beginning of the segment is at an UNKNOWN company with a valid city fails to set the city in the added DMT stop, resulting in an invalid movement that cannot be saved.

  • NSUITE-104488
    When a hook event is the first event on the trip segment, removing the order from a driver the trailer remains assigned.

  • NSUITE-200209
    When updating a driver’s shift in the Trip Planner by adjusting the start and/or end times; an end deadhead (EMT/EBT) stop is added to the driver’s assigned trip even though this is not the final trip of the shift.

  • NSUITE-200485
    Moving planned trips to a different driver using the Trip Planner sometimes results in a scenario where the system removes the BMT stop paired to the DMT but does not remove the DMT as well.

  • NSUITE-203650
    When planning trips in Trip Planner, if you plan a load as trip 2 and save, and then you plan a second load as trip 1 and save, the system removes the load you planned for trip 2.

  • NSUITE-203651
    When planning trips in the Trip Planner, if you adjust the start or end date/time for the shift of a driver, the system automatically adds an EMT event to the final load on the shift.

  • NSUITE-203678
    When you add BMT/DMT stops to second leg of split trip in Trip Planner, asset validation prevents you from saving.