Load requirement conflicts

A load requirement is a special resource qualification that has been recorded for a trip. Such requirements allow you to specify the type of resource that should be assigned to a trip. For example, for a hazardous load, you may want to indicate that a driver should be assigned only if he/she has hazardous materials training.

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

  • A requirement is signified by a must condition.

    Only a resource that meets the requirement can be assigned to move the load. If the resourced does not meet a load requirement, the Save Warnings window opens to show the details of the mismatch.

  • A preference is signified by a should condition.

    By default, the system does not display a warning for should condition mismatches and allows the assignment. If you want the Save Warnings window to open when a should condition exists, you must have [FuelDispatch]ShowWarnings=Y in your TTS50.

In this example, at least one resource assigned to the order does not meet a must condition

image1

To view the details of the conflict, expand the warning by clicking image2 in its row. A resource assigned to the order does not meet a must condition. Another resource assigned to the order does not meet a should condition.

image3

The load requirement conflict information is displayed in these fields:

Field definitions

Assign Type

The asset type specified by the load requirement

Assign ID

The ID of the asset that does not meet the load requirement

OrderNumber

The system-assigned order ID

LoadRequirement

Identifies the conflict as a load requirement mismatch

ErrorMessage

The system constructs a message specific to the individual conflict. It uses the value from the load requirement’s Readable Message field and inserts:

  • The order number

  • The resource type

  • The assigned resource’s ID

image4

CheckLevel

The severity of the mismatch

The options are:

  • PreventSave

    A load requirement (a must condition) has not been met. The current resource assignment cannot be saved.

  • Warn

    A load preference (a should condition) has not been met. However, the current resource assignment can be saved.

CheckLevelImage

Icon that identifies the severity of the mismatch

  • image5

    A critical problem exists. You will not be able to save the resource assignment.

  • image6

    You are being warned of a potential problem; however, you will be allowed to save the resource assignment.

To dispatch the order, you must resolve the conflict for a must condition. To do so, you can: