Responding to warnings and fixing errors

When a trip is in view in the Order Maintenance window, Trip Folder, or Planning Worksheet, you can use the Assign Driver/Equipment window to assign resources. When conflicts exist, they are shown in the Save Warnings section at the bottom of the Assign Driver/Equipment window. If the conflict(s) will prevent you from saving, the Save Warnings: Errors tab is red.

Instead of using the Assign Driver/Equipment window, you can assign resources directly on the header of the Trip Folder. If conflicts exist, the system signals this by displaying the Save Warnings/Errors link to the right of the lookup tab.

To see the conflicts, you can do either of the following:

The Save Warnings window will open automatically.

At the top of the display, the system lists the number of warnings and errors currently in effect for the trip. In addition, to the left of each conflict, it displays an icon identifying the severity of the conflict.

Warning

A non-critical conflict exists, such as:

The resource assignment can be saved.

Error

A critical conflict exists, such as:

The resource assignment cannot be saved.

The display groups conflicts according to type: Asset Conflicts (scheduling conflicts), Expirations, and Load Requirements. By default, the system displays the conflict information in one line of text.

By selecting the Details checkbox, you can display the information in a grid format with headers. This format also displays the trip segment number (in the LegNumber column).

In TMW Operations, if you attempt to save a resource assignment that conflicts with another trip using the same resource, the system will notify you that a scheduling conflict exists.

The system displays information about the conflict in both the Save Warnings window and in the Assign Driver/Equipment window’s Save Warnings: Errors tab.

To view more information about the conflict and/or to correct the conflict, you can access the Conflict Corrections window by double-clicking the row that displays the conflict message.

When the Conflict Corrections window is displayed:

In addition, one of these symbols displays in the header area to indicate the conflict’s severity:

In the Conflict Corrections window, you can make the following types of changes:

When a Priority 1 expiration has reached its effective date, the system will not allow the resource to be dispatched.

To mark the expiration as done, you must select the expiration’s Completed checkbox in the Driver/Asset Expiration window from the resource’s profile. Until you do so, the expiration remains in effect.

For more information about completing expirations, see Manually completing an expiration.

For more information about expirations, see What are expirations?

Load requirements specify special criteria that must, or should, be met when assigning resources (driver, tractor, trailer, or carrier) to an order.

When a resource assigned on the order does not meet the load requirement, the mismatch will be noted in both the Save Warnings window and in the Assign Driver/Equipment window’s Save Warnings: Errors tab.

Error shown in the Save Warnings window:

The system will not allow you to save a resource assignment when a must requirement has not been satisfied. You must resolve the load requirement before you can save the order.

For more information about clearing load requirement conflicts, see Resolving load requirement conflicts when assigning resources.

For more information about load requirements, see What are load requirements/preferences?

When creating and updating orders and trips, you may encounter warnings and errors caused by improper data entry or configuration settings chosen by your system administrator. Some of these messages will display in the Save Warnings window. Others will display in message boxes. The tables below list common messages, their causes, and links to topics that provide additional information.