2019.3

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

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

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

Buttons now display mapped state/province locations involved with trips (NSUITE-207373)

Map query buttons are now located in the Origin and Destination fields of the External Equipment tab and in the Destination field of the Company Carriers tab. Use these buttons to select multiple states or provinces in the United States, Canada, and/or Mexico to use as filters when matching resources to trip locations.

For additional information, see Setting up the system to use an interactive map and Matching carriers to trips based on location.

Database

SQL changes related to the trc_transponder column update (PB-200661 and TSI-269)

Updated Microsoft® SQL stored procedures in conjunction with the changes related to the trc_transponder column update.

EDI

File creating changes to 309s and 358s for the trc_transponder change (TSI-270)

Previously, you could enter up to 17 characters in the trc_transponder field. This would cause outbound EDI 309 and EDI 358 documents to fail or not update correctly.

Now, you can enter up to 50 characters in the Transponder ID field. The system will write all 50 characters to the outbound 309 and 358 EDI documents.

Loading by Compartment

Loading by Compartment maximizes compartment-loading capabilities (NSUITE-207275)

Dispatchers use the Loading by Compartment feature to load trailers to maximum capacities. This allows you to:

  • Increase trailer revenue

  • Avoid fines related to overloaded or improper compartment loading.

    You perform the required setup in TMWSuite’s System Administration and in the TMW Operations applications.

Starting with Version 2019.3, the feature supports loading based on jurisdictional setup. The equipment configuration assigned to a load must:

  • Be licensed to operate in all jurisdictions associated with a trip

  • Meet gross vehicle weight road restrictions for the jurisdictions.

For additional information, see Loading By Compartment.

Planning Worksheet

Planning Worksheet timeout (INT-104982)

The Planning Worksheet uses the value in the [Misc]PlanningBoardQueryTimeout INI setting to determine how long it runs while retrieving trips. Previously, the setting was not used when retrieving EDI orders so the EDI tab timed out if it took longer than 30 (seconds) to retrieve EDI trips.

Now, the setting applies to the EDI tab. The default timeout for all tabs is 60 seconds and that can now be changed by adding the entry to the Misc section of your TTS50.

If the Planning Worksheet times out when retrieving EDI trips (by clicking the Retrieve button when the EDI tab is displayed), the system does not display an error message. Instead, you must verify the information on the Planning Worksheet is updating correctly. If it is not, increase the time.

Performance Enhancement Rewrite

Performance Rewrite UpdateCarrierHist_sp (NSUITE-207783, PB-200716)

The overnight job calling the stored procedure UpdateCarrierHist_sp that was running in excess of an hour. After implementing the rewritten code, the job is more efficient.

Prior Commodity Cleaning

New Prior Commodity Cleaning window (NSUITE-207433)

You can set up validation for cleaning trailers carrying prior commodities using the new Prior Commodity Cleaning window.

Trailer profile

Trailer storage now allows users to change order numbers and set storage status to Completed (NSUITE-207410)

You can now add or change order numbers listed for trailer storage in the Order# field on the trailer profile’s Storage tab. Note that the order number must be valid and cannot have any trailer storage invoices processed for it. You also cannot change the order number to an order number that has an active trailer storage record.

The Storage Status field also has a new option - Completed - that allows users to stop charging for a trailer that has not been released. Note that when a storage status is set to Completed, it cannot be reset to Active, but can be set to Released so you can resume invoicing it again.

Resolved Issues

Brokerage

  • NSUITE-207075
    When copying recipients, the ACS window was sending separate e-mail messages - one to addressees and a separate message to copied recipients. This prevented recipients from being able to use the Reply All feature to contact all involved parties. The system now sends the same e-mail message to all recipients.

  • NSUITE-207349
    In Brokerage Company Planner, customers were unable to use an https:// URL within the CarrierHubEmailServicesURL General Info Table setting to send a Quote Offer e-mail message to a carrier. It was only able to send out e-mail messages using an address that contained http://. This issue has been resolved.

Commodity Profile

  • NSUITE-207608
    When a custom grid layout was saved on the Commodity Profile’s Sub Codes tab, deleted categories from the Prior commodity cleaning window continued to appear in the Commodity Category drop-down list. The Sub Codes tab now displays the category as None, and there are no categories available in the drop-down list.

Common Dispatch Features

  • NSUITE-207300
    Fixed issue on the Profit and Loss tab that was causing incorrect conversions between miles and kilometers.

  • NSUITE-207607
    Fixed an issue that was preventing the Profit and Loss tab from computing charges when a hub mile based billing rate with a minimum distance was applied.

Company Planner

  • NSUITE-207427
    When indicated by user response, the ACS window now discards changes when canceling as expected.

  • NSUITE-207485
    On the Company Planner board, users can choose to include a Trip Folder button to open the Trip Folder. When users clicked the Group By button on a Company Planner board that had a Trip Folder button included, an object reference error would occur. This issue has been resolved.

Database

  • NSUITE-207822
    During the Copy Trip process, the lgh_booked_revtype1 was not being copied to the new leg. The system now copies ord_booked_revtype1 to lgh_booked_revtype1.

Dispatch

  • NSUITE-202880
    When the [Dispatch]AutoRecalcTimes INI setting is set to N and an empty move is dispatched, the Pickup On and Drop On fields are set to the same time instead of one minute apart. This issue has been resolved.

EDI

  • NSUITE-207358
    Previously, when an initial instance of the Trip Folder was opened with an order and a second instance of the Trip Folder was opened with an EDI order, the second instance would adopt the order number from the first. This issue has been resolved.

  • PB-200674
    Fixed an issue in the EDI Accept 204 process where, under certain circumstances, it failed to generate the required 990.

  • TSI-220
    Fixed an issue where users could not delete On Hold 214s if the associated stop had been previously deleted.

  • TSI-317
    Fixed an issue in the EDI tab of the Planning Worksheet that caused performance issues when users retrieved or refreshed the tab after the EDI Accept 204 process completed.

Equipment Configuration

  • NSUITE-207221
    To alleviate a field label spacing issue, the Commodity Class field on the Equipment Configuration window was moved slightly.

Fleet Licensing

  • NSUITE-207263
    If there was a duplicate row on the Fleet Licensing window, a GEH error would appear when the user tried to save changes. An error message now advises users that each entry must be unique and instructs users to correct any duplicate entries.

    The labels for the Fleet Licensing window and menu option are now consistent.

  • NSUITE-207318
    When users added information to fields but did not press the TAB key immediately afterwards, the changes were not copied to the database. Instead, the data in the fields would revert to the previous values. This issue has been resolved.

Fuel Maintenance

  • TSI-310
    Fixed an issue with the P/L field on the Advances/Misc Labor window not allowing Plus as the default value.

Jurisdiction Road Restrictions

  • NSUITE-207317
    When users added information to fields but did not press the TAB key after, the changes were not copied to the database; the data in the fields would revert to the previous values. This issue has been resolved.

  • NSUITE-207319
    When adding a duplicate row in the Axle Limits or Gross Vehicle Weight Limits grids on the Jurisdiction Road Restrictions window, a GEH error would appear when users tried to save changes. An error message now advises users that the system found a duplicate entry and prevents them from saving changes.

LTL

  • NSUITE-207245
    When a pre-existing turnpike delivery movement was used to create a subsequent turnpike double, and the pre-existing turnpike double’s split location matched the new turnpike double’s merge location, the system created a movement shared by both turnpike doubles_ with redundant hook/drop stops at that location_. Because of the redundancy, the system should not have created this movement. This issue is resolved as of this release.

If the split/merge locations are not the same (i.e. no redundancy), then the shared movement should be created.

Mobile Comm

  • NSUITE-207474
    If users created a custom layout on the Mobile Comm Send Assignment window that removed the Transmit Assignment Only button and saved the layout as the default, the system disabled the Transmit button. This issue has been resolved.

Order Entry

  • NSUITE-207173
    When users assigned or un-assigned a trailer from an order, the trl_type1 field in the Order Entry’s order header would change as well. This issue has been resolved, and the value listed in the trl_type1 field now remains the same.

Planning Worksheet

  • NSUITE-206977
    The TrlType2 field on the Inbound/Power Board Definition window in Planning Worksheet was duplicating the value included in the TrcType2 field. This issue has been resolved.

Schedule History

  • NSUITE-207578
    When a user included and saved a change on the Schedule/Reschedule window, the Schedule History record displayed duplicate values in the Updated By, Updated On, and Reason Code fields. This issue has been resolved.

Scroll Records

  • NSUITE-207611
    Fixed an issue with reference numbers not appearing in the Reference Number Scroll window. This occurred when the reference numbers were associated with orders that had not yet been invoiced.

Split Trips

  • NSUITE-206705
    When the first leg of a trip was settled, users were unable to edit unsettled portions of the trip. This issue has been resolved.

Loading By Compartment

  • NSUITE-207178
    Additional loading class and compartment configuration validations are now included in the Units Info Tester window. In addition, if the selected asset unit does not match the equipment configuration, the system sets the drop-down field for that particular unit to Read Only status.

Trip Folder

  • NSUITE-207475
    The record lock tooltip now appears when multiple individuals access the same order.

  • NSUITE-207539
    When the system is configured to display the Schedule tab, it did not consistently save the stop_schchange_log row. This issue is now resolved.

  • NSUITE-207722
    When users clicked Yes in response to the prompt asking whether to save unsaved changes in the Trip Folder, the system was not saving changes made to the Schedule Change History records. This issue has been resolved.

Trip Planner

  • NSUITE-207605
    When retrieving off-duty drivers in the Trip Planner, the system would create shifts for all drivers retrieved when using the Shift drop-down menu, even when drivers did not have a default shift template assigned. The only way drivers can now have shifts built for them is if they are listed on a template.