2023.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
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. 2023.3. -
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, SQL Server 2017, SQL Server 2019, and SQL Server 2022 are certified for use with this application. 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. -
PC*MILER®
Certified with PC*MILER v.37
Enhancements
Card Planner
Add Trimble Maps view (TTESUITE-206215)
Previously, you were not able to view Trimble Maps in the Card Planner. Now, you can view trip and shift maps through the right-click menu options Show Trip Map and Show Shift Map. The maps will display the route for the selected trip/shift in a new window. To be able to view Trimble Maps you need:
-
The INI setting
[TMWMapping] MappingInstalled=Y
in your TTS50. -
A valid
[TMWMapping] ALKWebAPIKey
.
Card Planner and Planning Worksheet
ScheduledLoadCheck all-or-none enforcement (TTESUITE-205836)
The TTS50 setting [FuelDispatch]ScheduledLoadCheck
enables additional load checking in the Card Planner and Planning Worksheet.
A system warning will display in these scenarios:
-
A Planned (PLN), Dispatched (DSP), or Started (STD) order with the same commodity and consignee, and a later delivery date than the order is dragged to the shift
-
An Available (AVL) order with the same commodity and consignee, and an earlier delivery date than the order is dragged to the shift
Now, when the setting is set to “Y” a validation step is added when you drag an order onto shifts in the Card Planner and Planning Worksheet.
In prior versions, you could ignore a system warning about a later PLN/DSP/STD order and plan the dragged order on the board. Now, you can ignore the warning and plan the order when there is an earlier AVL order.
Note: The validation will no longer run for orders that were not created by the Forecaster.
The instructional text in the system message boxes have been updated to inform of this in the application.
P1 and P2 indicators (TTESUITE-205727)
Previously, there were not P1 (Priority 1) and P2 (Priority 2) warning indicators available in the Tractor and Trailer tabs of the Card Planner and Planning Worksheet. Now, these indicators are available. The P1 and P2 indicators are related to the [Misc]ExpDate
and [Misc]TrlExpDate
TTS50 settings. You can set a number of days to use for the different color indicators. The warning indicators will turn from green to yellow to red based on the number of days.
When the indicator color is:
-
Green, means no expiration.
-
Yellow, is a warning of expiring soon.
-
Red, is an expiration.
The number of days for the tractor comes from the [Misc]ExpDate
setting. The number for the trailer comes from the [Misc]TrlExpDate
setting, however if the [Misc]TrlExpDate
is not set, it will default to the [Misc]ExpDate
setting.
Order Audit Log
Add Freight Details to Order Audit Log Update Note (TTESUITE-204629)
You use the Order Audit Log window to track an order’s history. The Audit Log section reflects changes tracked by the Activity Audit feature.
Now, Freight details have been added in the Update Note field on the freight update audit log record in the Order Audit Log window.
The Freight details include the Freight Record #, Commodity Record #, Ordered Volume, Qty, and Freight Parent Record #.
Resolved issues
Call On Demand Order Entry
-
TTESUITE-206161
When you used the Retain/Redirect button the functionality did not work as intended.
Now, these items have been improved:-
Starting a retain from a planned order, the deadhead stops are no longer removed from the resulting consolidated movement. When the stops were removed, this caused a system error.
-
On an order that a retain is started from, Actual Quantity and Net Volume on LLD freight records are no longer reduced by the retain amount.
-
On an order that is consolidated into a movement as the target of a retain, the Actual Quantity and Net Volume on LLD freight records are reduced by the retain amount.
-
-
TTESUITE-206271
When you created a new order, data was populating from the previous orders consignee info in the freight commodity fields. For example, 87ETH, and 93ETH. These fields should be blank until company data is retrieved.