2020.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
Forecaster Console update warning
As of V. 2018.3, the Forecaster Console in Inventory Services 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. Instructions on using the tool are provided in the Inventory Services 2018.3 release notes.
Social Security number encryption warning
Starting in version 2020.4, Social Security numbers you enter in the Driver profile are encrypted in the database by default.
Having encrypted Social Security numbers could interfere with third-party applications accessing the data. This happens because the data is encrypted when transferred. The third-party application would not have the ability to decrypt it.
You can set up the system so that the Social Security numbers you enter in the Driver profile are not encrypted in the database. To do so, set the DataEncryption General Info Table setting’s String1 field to N.
The Data Conversion Administration Utility allows you to encrypt/decrypt a group of Social Security numbers in your database. Contact your Professional Services representative to obtain the DataConversionAdministrationUtilityInstall.msi. Access and usage of The Data Conversion Administration Utility should only be provided to a system administrator. That utility provides access to all highly sensitive data and should only be used in the explicit instance of needing to encrypt or decrypt the driver profile. |
ALK warning
In very limited circumstances, your system could generate incorrect mileages when using PC*MILER version 32 with any of these products:
-
TMW Operations version 2018.2 or lower
-
TMW Back Office version 2018.2 or lower
-
Fuel Dispatch version 2018.2 or lower
-
TMWSuite version 2018.2.0.0275 or lower
This problem is associated only with systems that have one of these options set in their TTS50:
-
[MileageInterface]ExOptions[x]=I
-
[MileageInterface]ExOptions[x]=X
Having either of these options set will cause Practical mileage to be computed as Shortest, and Shortest mileage to be computed as Practical.
This will not affect mileages previously retrieved and stored in the mileage table.
The issue is fixed in the next general release, such as 2018.3 for TMW Operations.
A temporary workaround to bypass the incorrect code is to do any of the following:
-
Use an additional ExOption in conjunction with the I or X option.
-
Remove the I or X option entirely.
-
Install an earlier version of PC*MILER.
Requirements
-
TMWSuite®
You must be using TMWSuite V. 2020.1 or later. -
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 laterNote: 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.
Enhancement
Ordering and planning volumes for multiple asset types
Assigning a default Tractor, Trailer 1, and Trailer 2 to a company (FS-201553)
In Inventory Services, the Order Forecast Review’s Setup tab, allowed you to specify a company’s default trailer. Now, additional fields allow you to add a default tractor and second trailer. To forecast orders, you must specify a default Tractor or Trailer. The tractor or trailer you add must have compartments defined in its profile.
Forecasting orders based on compartments from any combination of assets (FS-201554)
In Inventory Services, the Forecaster Console can now use tractor and trailer compartments when calculating the volumes on forecasted orders. It can project orders based on a collection of compartments created from any combination of assets. This allows it to create orders that maximize gallons to what will fit in a tractor or trailer. These asset compartments also determine the products that can be included on a load.
In Fuel Dispatch’s Call On Demand Order Entry, Dispatch Dashboard, Card Planner and Planning Worksheet, the system adjusts ordered and planned volumes based on default asset compartment information.
Resolved issues
Call On Demand Order Entry
-
FS-201615
When you saved a new order with the cursor in the Consignee ID field and used the right-click shortcut menu to close the application, an exception error occurred. -
FS-201626
An error occurred when deleting freight on a JOB order and using[FuelDispatch]AllowEditJOBOrdered =Y
in your TTS50. -
FS-201958
When you changed the volume and assigned a driver at the same time, the Source field value showed Locked Volume (LCKVOL). This occurred even when you had[InventoryService]ForecastPLNStatus=Locked
in your TTS50. In addition, all Freight grid volumes reset to 0 (zero) when you planned stops and assigned a driver in the Stops grid.
Card Planner
-
FS-200753
When using TotalMail in the Card Planner to send Company Profile information, the driver only received a blank Company Profile form. -
FS-200774
An Index error occurred if too many trips were planned on a shift-based driver. A warning message now displays when this situation occurs. -
FS-201173
After you assigned a resource with an expiration to an order, removed the assignment, and then attempted to update the board, a Save Warning message opened. The system should have allowed you to update the board without error. -
FS-201386
When consolidating orders using the Group By feature in the Avl. Orders grid in Card Planner or Planning Worksheet, you received an error message. -
FS-201531
Changing a company’s forecaster mode to something other than Forecast in the Forecast Order Review window caused an issue when planning loads in Fuel Dispatch. When you changed a planned load to an available load in Card Planner or Planning Worksheet, the Forecaster continued to create available orders for the site. -
FS-201557
The Card Planner and Planning Worksheet showed an incorrect trip Retain Date and Runout Date for split trips. -
FS-201603
When planning either multiple loads for one driver or multiple consolidated loads in Card Planner, you received a System.OutOfMemoryException error. -
FS-201790, FS-201792
When creating new driver shifts, you could create shifts that were longer than what the Fuel Dispatch application supported. You should not have been able to create driver shifts that extended beyond 20 hours. This prohibited the long haul boards from opening.
Certificate of Analysis
-
FS-201567
You were unable to dispatch a splash blend load that included a Certificate of Analysis. -
FS-201613
Creating an order for a splash blend product and a Certificate of Analysis in Call On Demand Order Entry caused an error.
Commodity Profile
-
FS-201127
After saving a commodity class in the Commodity Classes window, you could not use the Delete button to delete the commodity class. The fix allows the button to function in two ways. The system deletes the commodity class if it was not saved and retires the commodity class if it was saved.
Company Relations
-
FS-201443
Adding manifolded tanks of the same commodity in the Company Relations Profile resulted in an error in the first tank row. The error occurred in the Percent of Forecast column even though its sum total equaled 100.
Dispatch Dashboard
-
FS-201343
After running the Forecaster and updating the Dispatch Dashboard window, its ForecastDate field did not update to show the Forecaster’s last run date.
Expiration Edit
-
FS-201117
The Route To company information for carriers did not show in the Expiration Edit window’s Available At fields.
Forecast Order Review
-
FS-201322
After running the Forecaster and updating the Forecast Order Review window, its ForecastDate field did not update to show the Forecaster’s last run date.
Job Order by Volume
-
FS-201619
You were able to create a child order that exceeded the volume remaining on the parent order.
Oil Field Order Entry
-
FS-201604
When using the Main toolbar’s Close icon to exit the Oil Field Order Entry window, you received a GEH error. It stated, "Close is not identified."
Tractor and Trailer Compartments
-
FS-201812
When creating a new tractor or trailer profile there was no indication that you had to save the profile before adding compartments.Note: When creating a new asset, the system requires that you save its profile before adding compartments.
Miscellaneous
-
FS-201614
Removed the Help folder containing out-of-date .chm files in the product deliverables. This change was made to ensure that you do not inadvertently access the outdated help files. -
FS-201772
When working with orders that had many deliveries and one pickup, a significant performance lag occurred. This issue affected Call On Demand Order Entry, Card Planner and the Deadhead/Trip Editor window.