We are pleased to inform you that we have successfully launched a new version of our Control Tower, 2025 v5.
Dynamic Load Type Updates
Goal
To allow shippers to automatically update the load type in Transport Orders (TOs) whenever the carrier is changed or auto-allocated. This ensures the load type accurately reflects the carrier's contract and service capabilities, improving data consistency and workflow efficiency.
What's New?
Previously, the load type was set based on the initial carrier selection and didn't update if the carrier was changed later. With this enhancement, you can now enable an option in the Transport Order Form Settings that automatically updates the load type whenever the carrier is switched or assigned by rate allocation. This is particularly useful for shippers who rely on carriers to determine the appropriate load type (e.g., a specific carrier only handles FTL shipments).
For further details see Transport Order Form Settings.
How To Use
How To Use
You can configure this new functionality within the Transport Order Form Settings.
Example
Before: You create a TO and select Carrier A, which sets the load type to "LTL" based on your form settings. If the system later finds a better rate with Carrier B (an "FTL" carrier), the carrier in the TO is updated, but the load type remains "LTL," leading to a mismatch.
Now (with new setting): When the carrier is switched to Carrier B, the system automatically re-evaluates the form settings and updates the load type to "FTL," ensuring the data is correct and aligned with the new carrier.
Milestone Reason Codes for Scheduled Events
Goal
To allow users to change reason codes and remarks for scheduled milestones without having to modify the scheduled date and time. This improves the accuracy of reporting and history tracking, providing more detailed insights into why a scheduled event may have been adjusted.
What's New?
Previously, reason codes could only be changed when the scheduled time for a milestone was changed. You can now add a reason code to a milestone's scheduled section even if the date itself hasn't changed. This gives you greater flexibility in documenting why a scheduled time was, for example, intentionally set early or late.
Also it will allowed to change the Reason even if the Actual has been set until the Transport order has the status "Ready for Reporting".
In version 2025 v3 we provided that change already for Reasons for the Actual part, link.
How To Use
How To Use
Navigate to the Milestone Dialog of a Material Order (MO).
Go to the Scheduled section.
You can now change the Reason from the dropdown menu without changing the time
The system will automatically log this change in the milestone's history.
Example
Before: A scheduled delivery for 2 PM had to be updated to 1 PM. User added a Reason code. Afterwards you like to correct the Reason and it was not possible to do that.
Now: You can change the Reason even without changing the time. This change is logged in the history for better traceability.
Reverting Collection Window Calculation
Goal
To revert the calculation of the Collection To time for scheduled dates of orders.
What's New?
The new logic provides an option to calculate the Collection To time based on a reverse calculation from the delivery deadline. Previously, the Collection To time was calculated from the order creation time, leading to unnecessarily tight collection windows for drivers.
The updated calculation is: Collection TO = Delivery TO - Delay of Milestone DELIVER - Calculated Drive Time
This change ensures that drivers have an appropriate window for collection, taking into account the full journey and all handling delays.
If there would be no "Delivery TO" date in the Material Order the calculation would skip considering the delays on that stop like the Handling time.
How To Use
How To Use
The new calculation option can be configured in the settings for Material Orders.
Go to Settings
Material Order Settings
"Schedule Calculation" --> "Auto-complete"
In the Section "Collection" "From and TO is the latest of" select "Calculated from Delivery"
Example
Order Created: 13:00
Scheduled Delivery: 16:00
Delays: 20 min (Milestone COLLECT) + 10 min (Milestone COLLECT) + 20 min (Milestone DELIVER)
Drive Time: 60 min
New Calculation (reverted): Collection TO = 16:00 - 20 min - 60 min = 14:40 This provides the driver with a much more realistic and flexible pickup window.
Smaller Improvements
TO number hyperlinked in Shipping Container grid which allows the user to jump to the Transport Order tab
Enriched Account table export of missing fields like Mobile Device, Platform & Version, App Version
Improved search for Alerts in "My Alerts" dialog