17.60

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.

Requirements

  • TMWSuite®

    You must be using TMWSuite TMWSuite V. 2017.17_01.0248 or later.

  • Microsoft® .NET Framework

    Install or upgrade to the latest version of the Microsoft .NET Framework on your system.

    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

  • 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

Introduction to Inventory Services

Providing telemetry data to TMW (FS-200491)

To better serve you, TMW now offers you the option to provide application telemetry data. This data allows us to see near real-time information about the application and how you are using it. It logs:

  • User actions, such as opening windows, clicking icons and buttons, responses to errors

  • Performance information on saving and loading trips, window load times, and SQL view execution

  • Environment information, such as the application version, database SQL level, user name, TMW license values, machine statistics, and operating system version

There is no performance overhead. Data is sent using the store-and-forward method when the machine has open cycles.

You can decide to share or stop sharing data at any time.

Link to topic: Providing telemetry data to TMW

Inventory Services

Setting up the Importer reading configuration file (FS-200364)

A readings import file may start with multiple blank lines, or have multiple lines of irrelevant data. This can cause the Importer to incorrectly process the readings data.

Now, the Readings Import Configuration Maintenance window allows you to specify the number of lines to be ignored when the Importer is processing readings files.

Using FTP, FTPS, or SFTP protocol to import tank readings in CSV or TXT file format (FS-200459)

You can use different file transfer protocols, including FTP and FTPS, to import tank readings in CSV or TXT files. The Import Service Console now supports SFTP file imports.

Performing preliminary setup

Preventing duplicate critical loads (FS-200495)

When a tank is in critical need of product, the Forecaster creates an order to meet that need. It sets the order’s arrival and departure dates to ensure it is filled as soon as possible. Currently, when the Forecaster sets the critical order’s arrival/departure dates, it ignores the store’s existing orders. It may place the new order before those that are Planned, Started, or Dispatched. If the dispatcher does not know the critical order will put the tank over its Safefill level, a retain can occur.

Now, you can set up the system to prevent the Forecaster from generating orders and assigning their arrival/departure times earlier than orders that are Planned, Started, or Dispatched.

Link to topic: Managing duplicate critical orders

Resolved issues

  • FS-200271
    Unable to retrieve data in Adjust Tank Forecast unless you type in a company ID.

  • FS-200272
    A lot of orders all have the same runout date. This is causing dispatchers to send loads too soon.

  • FS-200275
    Orders are being set up for a delivery time during a restricted window. Hourly Details in side Inventory Services in the Order Forecast Review screen clearly show loads that are planned for delivery inside a restriction.

  • FS-200344
    If a user deletes a company tank detail record without deleting the Forecast setup for that commodity (assuming that is the only tank with that commodity) Commodity forecast setup, Forecast order site review, and likely other screens will fail to load that company. Validation needs to be added to prevent tank commodity change/deletion where there is an existing Forecast.

  • FS-200363
    When the store closed hours for Store 3637 are set from 15:00 - 15:59 and the "WEEK" option, order forecast review will lock up. When the hours have been changed to 15:00 - 16:00, order forecast review opens normally.

  • FS-200373
    Customer has sites where the Tank ID exceeds the value of 10 and will not match the Forecast Bucket (i.e., Tank ID=11 and Forecast Bucket=2). Readings cannot be imported for these tanks due to a Tank is not being forecast Error.

  • FS-200397
    The forecaster is adjusting volume amounts for an order that is in a started status when the arrival date is changed

  • FS-200400
    The import console is not importing the first reading in the import file.

  • FS-200520
    When Single Delivery is turned on it is generating an order with a 6 day window. There are three other orders of the same product that are projected after this delivery, but prior to the runout time