TruckMate 2023.3 New Features: Operations

The following improvements have been made:

The DISPATCH.EXE Application Configurator option Status Change Date - Apply Time Zone affects time zone functionality. By default, it is set to False.

If it is set to True, and you change a status manually, the times now adjust automatically if the zone being used to change the status has a GMT Offset value applied against it.

The offset adjusts the zone in accordance to the value in the zone rather than the time zone of the machine. For example, if the local machine time zone is Pacific Time, and the time is 12:00 PM, the value in the Date field on the Freight Bill Status Change window changes based on the zone. Daylight Saving Time (DST) values are applied if the option is selected for the zone.

This illustration shows the window for Vancouver (Pacific Time), Winnipeg (Central Time), and Montreal (Eastern Time).

TruckMate makes the adjustment automatically. You can change the time manually, but if you do this, TruckMate will not make any additional automatic adjustments.

The same logic applies if you make a status change on the Intermodal Status Change window.

You cannot change dates on this window, but you can see the time zone adjustments within the Status History tab.

A new application, Threaded Log Viewer, lets you import and review ART-based logs in a user-friendly interface. With it, you can:

To access Threaded Log Viewer:

In SQL Execute’s Tools menu, a new Zone Tree Import option lets you import existing zone tree structures into your database.

When you select this option, the Zone Tree Import window opens.

On this window, select the folder that contains the zone tree files you want to import. Then, choose one of these options:

Once you click Import, you can see the process in the log area of the window. TruckMate also creates a log file when the process is complete.

The SERVICE_FAILURE_CODES table contains reason code data.

A new index has been added to improve performance.

Previously, TruckMate used the DROPDOWN database table to access state, province, and country data. However, the data in that table was incomplete.

Now, TruckMate uses the COUNTRY_SUBDIVISION table, which contains information for all supported countries and their corresponding states and/or provinces. These countries are:

These applications have been updated to reflect this change.

Previously, when installing the Mileage Server, a single instance was created that handled both interactive and process jobs.

Now, the installer prompts you to create two instances, both of which must be running for the Mileage Server to work. The instances are created in this order:

If you experience many mileage calls during a typical day, you can add more process job instances to increase calculated mileage job outputs. This should help reduce the amount of time it takes for a record to receive a calculation.

Previously, when TruckMate processed a Mileage Service job, it called a procedure that cleared any "stuck" resources identified on trips. The MILESERV.EXE Frequency to fix up resources Application Configurator option determined how often the procedure was called.

With this version of TruckMate, the procedure and the Application Configurator option have been removed.

If you notice a large amount of "stuck" resources within your environment, contact Trimble Transportation Support for assistance.

These PROFILE.EXE Application Configurator options have been removed:

In addition, the MAP_URLS table has been removed from the TruckMate database.

Previously, these features were used to specify different mapping options, such as Google Maps or MapQuest. Now, TruckMate uses Trimble Maps exclusively for all mapping operations.

With this version of TruckMate, PC*MILER 37 (Webservices) is certified to work with these features:

Previously, delays could occur when attempting to send a form message and an image together from D2Link in an area with poor reception.

Now, the mobile communications workflow allows for messages and images to be sent separately for the same requested message. Typically the message should appear first, followed by the image(s). The amount of time between the delivery will differ depending on the reception.

A number of modifications have been made to several queries to improve how these TruckMate applications handle large amounts of incoming Hours of Service data:

If you use PeopleNet Mobile Communications and your setup allows it, you can import a power unit’s or trailer’s engine hours into TruckMate. The processing happens with PerformX data, which is provided by PeopleNet.

Information appears in specific fields in the profile.

image:TM2023-3/tm-168249-233b.png[

Also, you can see a history of the engine hours and driver information in the PerformX History window available in Dispatch and Multi Mode Dispatch.

Occasionally, it is possible to corrupt a freight bill’s terminal plan. One of the most common scenarios where this occurs involves changing a customer after a bill has been assigned to a trip. This can cause the terminal plan to be recalculated, changing the terminal with which the bill is associated.

Previously, this corruption resulted in the freight bill terminal plan marking this as an invalid route, because the terminals used on the trip no longer alighned with the terminal plan. The freight bill would then disappear from the trip in the Freight Bills grid, even though it was still assigned to the trip.

Now, "corrupt" freight bills appear in the grid, along with a stop type value in bold red letters that indicates the issue.

The most common stop type values displayed include:

Although freight bills can still be moved in this state, Trimble strongly recommends that you review and correct these issue(s) before the trip starts.

Previously, when filtering data on the Deliveries, Pickups, or CrossDock grids in Multi Mode Dispatch, the contents of the Fixed SQL field displayed only the call to the stored procedure used to populate the grid. This caused problems when switching terminals.

Now, the Fixed SQL field displays all the SQL used. It resolves the issue with terminal switching, and it should be easier for you to write and refer to grid fields.

This illustration shows the SQL for the Deliveries grid.

The DISPATCH.EXE Application Configurator option Status Change Date - Apply Time Zone affects time zone functionality. By default, it is set to False.

If it is set to True, and you change a status manually, the times now adjust automatically if the zone being used to change the status has a GMT Offset value applied against it.

The offset adjusts the zone in accordance to the value in the zone rather than the time zone of the machine. For example, if the local machine time zone is Pacific Time, and the time is 12:00 PM, the value in the Date field on the Freight Bill Status Change window changes based on the zone. Daylight Saving Time (DST) values are applied if the option is selected for the zone.

This illustration shows the window for Vancouver (Pacific Time), Winnipeg (Central Time), and Montreal (Eastern Time).

TruckMate makes the adjustment automatically. You can change the time manually, but if you do this, TruckMate will not make any additional automatic adjustments.

This logic applies in these situations:

In addition, TruckMate uses this logic automatically in these situations:

The following changes were made to improve date threshold functionality.

The following Dispatch fields have been added to the Power Units grid in Multi Mode Dispatch:

These fields display the resources with which a power unit was associated on its previous trip. TruckMate updates them according to status updates and actions that occur on a trip.

As described in these subtopics, columns have been added to resource grids to ensure that their contents are identical in Multi Mode Dispatch and Dispatch. You will now see the same data regardless of the application being used.

Previously, a To Be Unloaded (TBU) trip automatically associated itself with the next terminal plan sequence, so that it could have a trip number. This caused these issues:

Now, if a TBU trip is included in a Trip Operation Planning workflow, these events occur:

This prevents blocking of the next sequence in the terminal plan. You can now see freight bills in the planning grids and perform cross docking procedures in Multi Mode Dispatch and ConnectedDock.

Previously, if a user was listed as a supervisor, the value in the Override PIN field in ConnectedDock Admin was not hidden. This has been corrected.

In addition, if a change needs to be made to this PIN, you must reenter the entire PIN. This prevents any errors that could occur when the PIN is not visible.

Existing dockworkers' PINs are unaffected by this change.

The following Keyence devices have been certified for use with ConnectedDock:

Use of these devices requires the keyenceRelease APK, which is now included in the APK package provided with TruckMate. You access this package by running ConnectedDock in your TruckMate software folder.

For more information on supported devices, see ConnectedDock Supported Devices.