2019.2

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.2, 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

Advanced Cascading (NSUITE-206029)

Due to customer needs for static dwell times between an asset’s arrival and departure, the system can determine whether to adjust the schedule after a change to arrival or departure.

The system can calculate the difference between the arrival and departure time. It will reclaim time to try to catch up if behind, using slack time within a layover stop or between stops. However, to do this requires time in excess of the protected amount.

If the system finds valid slack to use in the dwell time of a layover event, it will reclaim time in an attempt to catch up. The system will adjust arrival and departure times if there is remaining cascade.

Commodities

New Maintain Commodity Sub Codes window (NSUITE-206861)

To align with other windows in TMW Operations, there is now a Maintain Sub Codes window available as an additional tab on the Commodity Profile. This tab will only appear when you set [Misc]MaintainCommoditySubcodes=Y in your TTS50.

Commodity Validation using the CompanyProducts table (NSUITE-207065)

When saving a trip, the system can use the CompanyProducts table to validate that a commodity is available at the pickup and drop companies on the arrival date of the stops. Use the CompanyProductsRule setting in your TTS50 to activate this feature.

New user interface for the Tank Maintenance window (NSUITE-207241)

The Tank Maintenance window allows users to configure tanks at a particular customer location (such as a consignee or delivery point).

Enhanced Mileage

New Manage Mileage Table window (NSUITE-205825)

The Manage Mileage Table window includes enhanced mileage features, which ensure that a trip route identifies all jurisdictions through which a load must travel.

Equipment Configuration

New Equipment Configuration Maintenance window (NSUITE-205798)

The new Equipment Configuration window allows users to enter new equipment configurations, look up existing equipment configurations, and sample weight distributions by axle based on components entered in the Units Info section. Components included on a trailer configuration are the power unit, the lead trailer, and when applicable, the pup.

New Units Info section on the Equipment Configuration Maintenance window (NSUITE-206018)

The Units Info section of the Equipment Configuration Maintenance window now accepts actual Tractor and Trailer IDs and fills in the properties associated with the configuration.

Fleet Licensing

New Fleet Licensing window (NSUITE-205823)

The new Fleet Licensing window supports the following activities:

  • Loading current data by fleet.

  • Creating new entries in the FleetLicense table by Fleet ID.

  • Updating expiration data.

  • Updating gross vehicle weight by jurisdiction data.

Trip Validation for Fleet Licensing (NSUITE-206158)

The system performs Fleet Licensing validation when saving a trip where the assigned tractor is not set to UNKNOWN and the FleetLicense and DistanceCacheByState General Info Table settings are both activated. Each leg of the trip is validated; if there is a split trip, the system validates all tractors on each leg.

Fuel Maintenance

Setting a policy for any EFS rebate transaction (TSI-88)

The Service Center Chain Code Rebates window allows you to add or edit rebates.

In previous versions, you could set a Policy # only for transactions with a Rate Unit of % Rebate Amount.

Now on EFS transactions, you can set a Policy # for transactions associated with any Rate Unit: % Rebate Amount, % Fuel Purchase Amt, or $/Gallon.

EFS 110 pre-processor functionality changes (TSI-153)

Previously, EFS 110 transaction records displayed the transaction date only. They did not include the Point Of Sale (POS) date. Now, the EFS 110 records will append the POS date to the preprocessor output file so that users can map that date to the correct field in the table.

EFS Interactive functionality changes (TSI-153)

Previously, EFS Interactive records displayed the transaction date only. They did not include the Point Of Sale (POS) date. Now, the user can specify which date is included and mapped to the correct field in the table. Created a new [FuelServ]EFSUsePosDate setting to determine the functionality.

General system setup

Setting up currency conversions (NSUITE-206677)

In previous versions, you set up exchange rates for currency conversions in TMWSuite’s System Administration application.

Now, you can set up currency conversions in the Currency Conversion Maintenance window. You can access this window in TMW Back Office and in TMW Operations.

Jurisdictional Restrictions

New Jurisdictions Road Restrictions window (NSUITE-205824)

The new Jurisdiction Road Restrictions window supports the following activities:

  • Loading current data by jurisdiction.

  • Creating new table entries by jurisdiction.

  • Updating Max Gross Vehicle Weight by Train Configuration data.

Mileage

Flammable and Corrosive system codes added for ALK’s HazMat add-on module (NSUITE-206531)

Clients using ALK’s HazMat add-on module in conjunction with PC*MILER can create routes and calculate mileages based on hazardous material classifications.

In previous versions, the ALKHazLevel label provided four classifications as system codes:

  • General hazardous material

  • Explosives

  • Inhalants

  • Radioactive material

Now, the system provides two more system code options:

  • Flammable

  • Corrosive

In previous versions, you could set up these options manually.

Resolved Issues

Advanced Carrier Selection (ACS)

  • NSUITE-207211
    To prevent multiple agents from accessing and working on the same opportunity, record locking now prevents more than one agent from viewing and editing an order.

Advanced Cascading

  • NSUITE-207168
    On the Assignments tab in the Date Time Cascading Configuration Maintenance window, there is now a blank option available for setting an assignment configuration to blank. In addition, the menu option and window for Date Time Cascading Configuration Maintenance now match.

Brokerage

  • NSUITE-203547
    Fixed a problem that was preventing users from accessing the ACS window for Completed and invoiced orders.

  • NSUITE-207086
    Previously, in Company Planner, an error occurred when users selected a row with non-billable stops. The system now displays a row with non-billable stops without any errors.

Common Dispatch Features

  • NSUITE-206153
    Fixed problem that was causing the Profit and Loss tab to use the wrong rate index.

  • NSUITE-201695
    The system was not stamping the Pay To ID on manually added pay details.

  • NSUITE-206280, NSUITE-206928
    On the Profit and Loss tab, the system was ignoring asset restrictions set on the rate index when assets were not assigned to the trip.

  • NSUITE-206528
    Fixed an issue on the Profit and Loss tab. The system was not rating empty moves (marked as payable) for trips with multiple segments.

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

Cross Dock orders

  • NSUITE-205604
    The option in the LghRateMode field on Cross Dock orders was changing from 3PL Billing to UNKNOWN. This issue has been resolved.

Database

  • PB-200161
    Fixed an issue with a NULL value error message appearing when an in-service move expiration for a new tractor was created. This issue would only occur after first saving a non-dispatch expiration on a new driver, and then saving the invoice.

  • PB-200513
    Previously, when creating a master order or quote in Order Entry or Dispatch, the system would create a legheader and set the lgh_active value to 'Y'. The master order or quote would then appear in the Planning Worksheet. This issue has been resolved.

  • NSUITE-204929
    When a user created an accident record but did not assign the record to a tractor, the system overwrote the accident record when a user created a new tractor. This issue has been resolved.

  • NSUITE-207170
    The dapper repository created INSERT statements using the OUTPUT clause. This resulted in a SQL error that occurred on tables with triggers. The SQL generation now uses a declared table variable instead.

Dispatch

  • NSUITE-206295
    Previously, if you copied an order that included hub odometer readings, the copied version of the order also included hub odometer readings. This issue has been resolved.

  • NSUITE-206791
    Previously, if an order was consolidated, a user could not open the order from the Asset Assignment History window in Trip Folder. This issue has been resolved; trips can be opened from the Asset Assignment History window, and will load by leg number rather than order number.

Intermodal

  • NSUITE-205701
    If there was an Intermodal order that began with a CPUP stop and the user inserted a BBT prior to the CPUP, any changes to the chassis or container resulted in the system adding the chassis and container to the BBT stop, but not to the CPUP stop. This resulted in errors occurring in TotalMail and TMW Operations. This issue has been resolved.

Introduction to TMW Operations

  • NSUITE-207195
    Fixed telemetry logging for mileage errors. Origin and Destination were accidentally removed.

Order Entry

  • PB-200569
    The Copy function was not copying toll information.

Planning Worksheet

  • PB-200309
    When using the Relative Dates option to restrict trips in the Planning Worksheet, the system was interpreting an entry of 0 (zero) to mean no restriction. Now, the system correctly interprets an entry of 0 (zero) as restrict to today’s date.

  • NSUITE-200318
    The record locking feature, which involves setting [Misc]RecordLocking=Y in your TTS50, was not preventing the Asset Assignment window in the Planning Worksheet from opening. It was also causing trip validation errors when saving the assignment. The system will now prevent users from opening the Asset Assignment window on a locked order.

  • NSUITE-206420
    Read-only column security for the lgh_comment, Earliest Date, and Latest Date fields on the Planning Worksheet was not functioning as expected, and users were able to edit column information. This issue has been resolved.

  • NSUITE-206706
    When multiple layouts were included for the Trips grid on the Planning Worksheet, right-clicking on the grid and selecting the Reset Layout menu option would hide all rows, columns, and trip data. Users would then have to click Retrieve to repopulate the grid. This issue has been resolved, and the Reset Layout menu option resets the grid to the default layout.

Tracking paperwork

  • NSUITE-206473
    Fixed an issue that was causing the system to update the last_updatedby and the last_updateddatetime columns in the database each time you clicked on the Paperwork tab.