Carrier Assignment Recognition: This flag will control whether the Update Carrier/Tariff/Service/Lane Constraints process (one of the steps performed during the Update Constraints process) will be based on live trip/load data and/or tender audit data. This is applicable only for percentage based constraints; evaluation of integer based constraints will always be based exclusively on live trip/load data. It will support the following settings:
Currently Assigned and Tendered: Will use live data to establish a count of loads/trips that have been assigned to each carrier. All loads in Planned operational status or higher, plus approved loads in Open operational status, will be counted. Unapproved loads in Open operational status will be counted if the Optimization Parameter ResourceUpdatingApprovalRequired is False. Trips will be counted when the first load on the trip's itinerary qualifies. Integer based constraints will always be handled using this approach.
Previously Tendered to First Carrier: Will use tender audit data to get a count of loads assigned to a carrier. Using this option, a load that was tendered to a carrier, and subsequently cancelled can still be counted when Update Constraints evaluates the number of loads offered to the carrier. Loads in Open or Planned operational status but never tendered will not be counted. Therefore, there is a possibility that a carrier could be over-allocated in a subsequent Optimization. For example, a carrier should get 50% of the loads on a lane per week and 10 loads have already been allocated to the carrier out of a total of 20 loads. If only 8 of the 10 loads for the carrier have been tendered, a subsequent Optimization process could allocate an additional load to the carrier if the remaining 2 loads are not selected for Re-Planning.
Assigned and First Tendered: Similar to "Previously Tendered to First Carrier", except that approved loads in Open operational status plus all loads in Planned operational status will be included in the count provided they have never been tendered. Unapproved loads in Open operational status will be also counted if the Optimization Parameter ResourceUpdatingApprovalRequired is False and the load has never been tendered.
Assigned and All Tendered: For Percentage based constraints, the total load/trip count or resource associated FEU will be calculated from tender audit data, for both first tender and non-first tenders, and from current assigned resources of loads or trips that have never been tendered. Since this option considers all tenders, if tender is issued to an entity with same carrier/tariff/service combinations multiple times, then multiple resource usage may be counted, depending on the tender cancel/reject reason code and defined usage count behavior.
Include Open Unapproved for Location Throughput: Indicates whether evaluation for location level location throughput groups will consider loads in Open operational status if they are not approved. All other loads will be eligible. Note that since location level location throughput group capacity evaluation is performed using stop data, only loads with stops can be considered. This setting has no impact on dock level location throughput groups. Capacity evaluation for those location throughput groups will consider all dock commitments, regardless of the setting for the operational status or load composition approved flag for any corresponding load.