TruckMate 2023.2 New Features: Operations

With this release, Trimble Dispatch Advisor now exists in the Trimble Transportation Cloud (TTC). Endpoints used to connect to this service have been updated. Trimble Dispatch Advisor now also uses the TTC Trust Center for authentication and authorization.

Currently, the original endpoints are still active.

With the TruckMate 2022.4 release, City Dispatch and CrossDock were removed. Users of these applications were encouraged to switch to Multi Mode Dispatch.

City Dispatch (#26000) and Multi Mode Dispatch (#26010) have different licenses. Previously, if you only had a City Dispatch license, you could not use Multi Mode Dispatch.

Now, if you have at least one of these licenses, you can use Multi Mode Dispatch.

If you do not have either license, you must purchase a Multi Mode Dispatch license.

Previously, if you wanted to import zone trees into a new TruckMate database, you had to do so on the DB2 command line.

Now, the Database Creation Wizard contains an option to import zone tree files automatically. Available choices are Australia (ANZA) and North American (NA).

If selected, ZONE, FASTZONE and ZONE_DESCRIPTION data is imported.

TruckMate now reports when the EDI update service was last run with an EDI job. It stores the information in the LAST_RUN, SERVICE_ID, and SERVICE_NAME_1 columns of the TM_SERVICE table. You can use the information to track service behavior.

After upgrading to TruckMate 2023.2, records for services are automatically created in this table.

TruckMate now reports when the Dawg update service was last run with a Scheduler Dawg job. It stores the information in the LAST_RUN, SERVICE_ID, and SERVICE_NAME_1 columns of the TM_SERVICE table. You can use the information to track service behavior.

After upgrading to TruckMate 2023.2, records for services are automatically created in this table.

Within SQL Execute, a new table, TM_DELETED_RECORDS, is available.

Currently, this table contains records of freight bills that have been deleted and that do not have a freight bill number of NA or 0. You can use this information for tracking and/or auditing purposes.

Mileage processing now provides more accurate results for freight bills with extra stops.

Previously, the date range fields on the Resource History View tab in the Trimble Map View window were not dynamic. Depending on which field value was changed, updates to the other field did not happen automatically, causing an error when viewing a resource’s history..

Now, if you set the From date to a date that is later than the To date, TruckMate automatically changes the To date to match the From date.

Previously, during processing, a Mileage Server job would not complete for various reasons. Chances of this "locked" state happening increased when multiple instances of the Process Jobs thread existed.

Now, handling has improved so that fewer locked jobs will occur.

TruckMate 23.2 is certified to work with on-premise PC*MILER 37 only. The Web Services version has yet to be certified.

These features have been verified against PC*MILER 37:

Previously, if the DB2 service stopped unexpectedly, mileage services did not recover completely. Process instances stopped, but interactive instances did not, causing the mileage server to hang.

Now, if the DB2 service stops, mileage services continue to run. Although jobs will not be processed while DB2 is down, processing will continue once DB2 restarts.

Currently, you can create list options for user-defined fields in several TruckMate applications.

Now, if a driver enters data in a user-defined field as part of a macro, the mobile communications workflow checks to ensure that the data is valid. If it is not valid, TruckMate records an error in the mobile communications log.

Two workflows have been enhanced so that you can assign drivers to trips based on the container associated with a freight bill or scheduled trip.

These changes have been made to the Find Near windows in Dispatch and Multi Mode Dispatch:

Changes affect these resources:

As of this release, endpoints for the Trimble Dispatch Advisor service were updated for improved security.

You should not see any changes to Dispatch and Multi Mode Dispatch functionality. If you experience any issues, contact Trimble Transportation Support.

Now, TruckMate removes from the TLORDER_TERMINAL_LOC_PLAN table all planning records associated with freight bills that meet one of these conditions:

If a freight bill is in progress, all planning records are kept until they reach one of the conditions listed above.

TruckMate does not delete actual movement history.

The following changes were made to the functionality controlled by the DISPATCH.EXE Application Configurator options Underline Bills with Notes and Underline Trips with Notes. These changes affect both Dispatch and Multi Mode Dispatch.

Currently, when a trailer or chassis is dropped from a trip due to a spotting status, one of the following takes place:

Now, on the Additional Rules sub-tab in the Status Codes tab of Codes Maintenance, a new option, Spotting Resource Status, lets you choose the default available or spotting status code that TruckMate will use.

On this tab, the Resource to drop on leg option determines which resource is dropped. If a Spotting Resource Status value is not specified, the original trip status code is applied. If an invalid or inactive status is specified, it is ignored and the default status code is applied.

Previously, trip template functionality only existed in Dispatch. It is now available in Multi Mode Dispatch.

A new Trip Templates option has been added to the Tools menu. Clicking it opens the Trip Template window.

+

Templates that were created in Dispatch are now available in Multi Mode Dispatch, and vice versa.

For information on how to use trip templates, see Trip Templates.

The stored procedures used to populate the Deliveries, Pickups, and CrossDock grids have been rewritten.When used with the appropriate filters and lanes/routes features, you should notice a significant improvement in performance.

In Multi Mode Dispatch, you can preassign a driver to a specific trip schedule.

Previously, when selecting a driver for a schedule, only those drivers whose home zones (as defined in their profile) matched the schedule’s terminal zone were eligible.

Now, TruckMate checks a driver’s defined terminal zone against the schedule’s terminal zone to determine driver eligibility.

With this release, these functions and stored procedures have been removed for Multi Mode Dispatch:

However, CUSTOM_CITY_LINK code has been changed to a function. If you use this stored procedure, contact Trimble Transportation Support before upgrading to TruckMate 2023.2 so that your custom code can be preserved.

Previously, in the Deliveries, Pickups, and CrossDock grids of Multi Mode Dispatch, each of the Trace Number 1-10 columns let you display a single trace number of a particular type. You define the trace number types using these MMDISP.EXE Application Configurator options:

Now, each Trace Number 1-10 field for an individual record can display multiple trace numbers. They are listed in descending alphanumeric order and separated by commas, as shown in this illustration.

If the total number of trace number characters for a record is 97 or less, all trace numbers appear in full.

If the total number of trace number characters for a record is 98 or greater, an ellipsis appears in the field, indicating that there are additional trace numbers available. To see the complete list, you must view the freight bill in Customer Service.

If you have defined trace number types for these columns in Application Configurator, these lists appear automatically when you upgrade to TruckMate 2023.2.

The following changes have been made to the CUSTOM_GET_DISP_TRIP_QUERY stored procedure. Typically, you use it to display custom fields in the Trips grid in Dispatch.