Setting up the system to use load requirements

A load requirement is a special resource qualification for a trip. The requirement specifies the type of resource that should be assigned to a trip. Setting up your system to use load requirements is a three-step process.

  • Define labels for resource qualifications and accessories

  • Create load requirements that require those same qualifications or accessories

  • Outfit your assets with qualifications and accessories for fulfilling the load requirements

When you save an order, the system compares the order’s load requirements with the qualifications or accessories recorded on the profiles of the assigned assets. If the resources satisfy the load requirements, the system will allow you to save the order without issuing a warning or error message.

Defining load requirement labels

The qualifications and accessories on which you base load requirements are identified in the label file using these labels:

  • DrvAcc
    Identifies qualifications and attributes possessed by the driver (e.g., the driver may be HAZMAT-certified). You maintain qualification data for drivers in the Driver Profile window.

  • TrcAcc
    Identifies items attached to, or carried by, a tractor (e.g., the tractor may have tire chains). You maintain accessory data for tractors in the Tractor Profile window.

  • TrlAcc
    Identifies items attached to, or carried by, a trailer (e.g., the trailer may have straps or swing doors). You maintain accessory data for trailers in the Trailer Profile window.

  • CarQual
    Identifies qualifications that pertain to the carrier as an entity (e.g., the carrier may be a minority-owned business).

You define these labels in the in the Edit User Definable Fields window. For details, see Using the label file to customize fields.

image1

After adding a new label, you must close and reopen TMW Operations for the changes to take effect.

Specifying the default condition for load requirements

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

  • A must condition denotes a requirement. Only a resource that meets the requirement can be assigned to the load.

    image2

  • A should condition denotes a preference. If the assigned resource does not satisfy the condition, the system displays a warning. It will, however, allow the assignment.

    image3

By default, the condition is set to must when a new load requirement is added. You can change the default condition to should by setting [.NetOperations]DefaultLRMandatory=N in your TTS50.

Setting up resource profiles to satisfy load requirements

When you assign a resource to a trip that has load requirements, the system checks the resource’s profile to verify that the resource has the appropriate qualifications/accessories to meet the load requirements.

You identify a resource’s qualifications/accessories in the resource profiles.

  • For drivers, you record qualifications, such as HAZMAT training.

  • For tractors and trailers, you record accessories, such as product handling equipment or safety devices.

  • For carriers, you record qualifications that pertain to the carrier as an entity, such as whether it is insured or bonded. For non-board carriers, you can also record driver qualifications, tractor accessories, and trailer accessories in the carrier’s profile.

    Note: For board carriers, you should record qualifications for drivers and tractor/trailer accessories in the profiles of the individual resources, not in the carrier’s profile.

image4 See it in action