Shipment constraints baseline definition

When you solve a model using baseline shipments, the Baseline Output Shipments table is populated. You can then use this output to populate the Shipment Constraints table.

Baseline modeling rules

The general rules for using the constrained baseline are as follows:

• For all problem types except periodic optimization (PVRP) and hub optimization, fixed baseline and partial baseline are both supported. The following rules apply:
  • Shipments that are not defined as baseline shipments (in the Shipment Constraints table or the Shipments table) will not be routed on the baseline routes if no Additional Shipments Insertion Rule is defined.
  • Baseline definitions with only one of either Pickup Sequence ID or Delivery Sequence ID are not supported.
  • Pickup Sequence and Delivery Sequence values require a valid route ID.
  • The Route Sequence value requires a route ID and a valid asset tour ID.
  • The Asset requires a valid reference in the Transportation Assets input table.
  • The Asset Site Name requires a valid reference in the Sites input table.
  • For each route ID, you must have consistent Asset, Asset Site Name, Asset Tour and Route Sequence values.
  • For each asset tour ID, you must have consistent Asset Name and Asset Site Namevalues.
  • Currently, if any of the rules are violated, the shipments will become Invalid Shipments.
  • When using interleaved optimization, you must define both the Pickup Sequence and Delivery Sequence for baseline shipments, or you can leave both Pickup Sequence and Delivery Sequence blank.
  • If you define an Asset Tour, you can define either Asset, Asset Site Name, or both, or you can leave Asset and Asset Site Name blank.
  • You can use the Additional Shipments Insertion Rule column to identify where additional shipments can be inserted in the delivery sequence with respect to the shipment in the shipment constraint. See Additional Shipments Insertion Rule for additional information.

• When multiple shipments are grouped on a single route without their pickup and delivery sequences specified, the baseline solver uses a greedy shipment insertion algorithm to quickly construct the route. The algorithm may not discover the optimal sequence that would result in a feasible route due to its myopic nature. Therefore, when feasible pickup and delivery sequences are known beforehand, Coupa recommends that you specify them in the table to obviate the reliance on the greedy algorithm.

• You can use the Shipment Constraints table to define the equivalent of asset – shipment relationship constraints. To do so:
  • You must define the Shipment, Asset and Asset Site Name in Shipment Constraints.
  • Optionally, set Force Ship Direct to “Yes” if you want the shipment to go LTL.
• Baseline routing is not currently supported for periodic optimization.