Load Pro-Ration Strategy: Controls how load level charges are distributed to stop and shipment level. See "Load Pro-Ration".
Trip/Booking Pro-Ration Strategy: Controls how trip or booking level charges are distributed to the associated loads. See “Trip/Booking Pro-Ration”.
Default Tender Accepted By Name from User Profile: When selected, a default value will be provided for the Tender Accepted By Name when any user performs the Tender Accept operation for a load or trip. The default will be established by retrieving the user name from the user profile for the user accepting the tender. This flag should not be checked if multiple individuals working for a carrier will be sharing the same User ID.
Exclude Pre-Purchased from Carrier Pages: When selected, all monetary amounts for loads that are presented on web UI pages accessible by carriers will exclude amounts associated with pre-purchased charges. If not checked, carriers will be presented the total rated amount for each load, regardless of whether or not any of the charges are pre-purchased.
Maintain Comparative Load Costs for Trip: Controls whether comparative costs will be maintained for loads attached to trips. When functionality is enabled, an amount will be maintained at load level reflecting the cost that would have been incurred had the load been handled individually rather than as a load on a trip. See "Trip Cost Savings".
Use Planning Tariff for Minimum Cost Savings: Controls whether Planning Tariffs will be considered when evaluating minimum trip saving requirements. If false, execution tariffs will be considered exclusively. If true, planning tariffs will be used, if defined; otherwise, the most appropriate execution tariffs will be used.
Trailer Activities Date Relationship Verification: Controls the level of cross-validation that will be performed between the dates/times on the trailer activities page in the web UI only:
Full: TM web UI will validate to ensure that all dates/times that have been reported on the Trailer Activities page have occurred in the expected sequence. The expected sequence will vary depending on whether the location is a pick or drop and whether the environment is live or non-live.
Partial: TM web UI will validate to ensure that Driver Check-In occurs before Driver Check-Out when both dates/times have been reported. TM will validate to ensure that Trailer (Un)Loading Start occurs before Trailer (Un)Loading End when both dates/times have been reported. There will be no cross-validation between the dates/times for Driver Check-In / Check-Out and Trailer (Un)Loading Start / End. This corresponds to validation that will be performed via API.
In Transit Unloaded Distance Assignment Method: Controls assignment of unloaded distance between consecutive loads on a trip. The following options are available:
Evenly Split: Half of the in-transit unloaded distance is assigned to each connected loads. For a trip that contains more than two loads, the loads in middle (other than first and last load) will have the in-transit unloaded distance equal to half of the unloaded distance from last delivery stop on the preceding load plus half of the unloaded distance to first pickup stop on subsequent load.
Preceding Load: The in-transit unloaded distance between two loads is assigned to the preceding load on the trip. The associated cost is prorated to the shipments assigned to the preceding load.
Subsequent Load: The in-transit unloaded distance is assigned to the subsequent load. The associated cost is prorated to the shipments assigned to the subsequent load.
Load Priority Calculation Method: This value is used as a default when creating load plans. The value for the load plan controls how the load priority is computed.
Highest from Shipments: The load priority will be equal to the highest priority among all shipment legs assigned to the load.
Volume Basis: The priority of each shipment leg will be multiplied by the shipment volume and the load priority will be equal to the total of shipment leg priorities*volume divided by the total volume of all shipment legs. For shipment legs having volume equal to '0', the volume will be considered as '1'.
Weight Basis: The priority of each shipment leg will be multiplied by the shipment weight and the load priority will be equal to the total of shipment leg priorities*weight divided by the total weight of all shipment legs.