2019.4

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.

Required update

As of V. 2018.3, the Forecaster Console no longer uses Common Volumes to calculate order quantities. Now, it uses Trailer Compartments to maximize gallons and fit orders to specific trailer compartments. The V. 2018.3 update requires a simple setup process to forecast to trailer compartments. We have included a mass update tool in the ClientCenter download to ease this transition.

  1. Download V. 2018.3 or greater. The Fuel Setup application is included.

  2. Install V. 2018.3 or greater in your test environment.

  3. Use the Inventory Services Trailer Profile window to define trailer compartments. You make your entries on the Compartments tab.

  4. Test the functionality in your test environment.

  5. Once testing is complete, before upgrading your production environment, use the Fuel Setup application’s Trailer Compartment Setup tool to add trailer compartment to prepare the production database. Running the setup tool has no effect on current production data.

  6. Once trailers are setup in your production database, proceed with the upgrade as you normally would.

  7. Test the new production system.

Requirements

  • TMWSuite®

    You must be using TMWSuite V. 2019.4.

  • Microsoft® .NET Framework

    Install or upgrade to the latest version of the Microsoft .NET Framework on your system. At a minimum, you should have V.4.6.2 installed.

    The framework must be installed on the FuelTMS applications server, client, and administrator systems before you install FuelTMS. If it is not present, the system displays an advisory message during the installation. Install the framework before running the application.

  • Microsoft SQL Server®

    Microsoft SQL Server 2012 or later

    Note: SQL Server 2014, SQL Server 2016, and SQL Server 2017 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 the FuelTMS applications, and have administrator rights for that system.

    Like most applications, FuelTMS applications can be installed locally on a user’s system. It is also possible to install FuelTMS applications 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 FuelTMS applications 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

There are no enhancements for this release.

Resolved issues

Card Planner

  • FS-201591
    Adjusted the Inventory Services forecast logic to compare the compartments on a loading configuration instead of checking the Trailer ID, when assigning an order to an asset in the Fuel Dispatch Card Planner and Planning Worksheet.

Forecaster

  • FS-201395
    In Inventory Services, there was an issue where the Forecaster’s load projection exceeded the maximum number of gallons that the driver’s trailer compartment could hold. This caused an issue in the Card Planner. When you assigned a forecasted order to a driver’s trailer and it exceeded the trailer compartment’s maximum total, the system did not adjust the order volume to match the trailer’s maximum compartment volume.

  • FS-201527, FS-201602
    Fixed performance issues related to the GetFuelInvAmountsReadingDate stored procedure.

  • FS-201556
    Fixed the issue where the Forecaster created orders for volumes that exceeded tank safe fill amounts, even when the [InventoryService]PreventDuplicateLoadOnCritical setting was set to Y in your INI file. This caused a situation where a new load could be scheduled ahead of a previously Planned load resulting in a retain.