Shipment Constraints

Internal Table Name: BaselineShipments

Use the Shipment Constraints table to assign shipments to baseline routes. You specify the sequence in which the shipment is picked up and in which it is delivered. You can also define specific assets for the baseline routes and combine them into tours.

Baseline Solution

Technology: TO

Table: BaselineShipments

Internal Name: BaselineSolutionID

Type: Text (255)

Use this field to identify a set of Baseline Shipment records that represent a specific solution. If this value is not populated, the Baseline Solution in the Baseline Shipments Output table is set to 1.

Shipment

Technology: TO

Table: BaselineShipments

Internal Name: ShipmentID

Type: Text (255)

Select the Name from the Shipments table.

Default value: null

Route

Technology: TO

Table: BaselineShipments

Internal Name: RouteID

Type: Text (255)

Enter the name of the Route on which the shipment is placed.

Default value: null

Route Start Date

Technology: TO

Table: BaselineShipments

Internal Name: RouteStartDate

Type: Short Date

Enter the date on which the route will start. The solver determines the time at which it starts.

Default: If no value is populated, the date defaults to the start of the Transportation Optimization horizon.

Pickup Sequence

Technology: TO

Table: BaselineShipments

Internal Name: PickupSequenceID

Type: Number (Integer)

Enter the sequence number for the stop to pick up the shipment on the defined route. Sequence numbers do not need to be consecutive. For example, you can define sequence numbers as 1, 4, 5, rather than 1, 2, 3.

Default value: null

Delivery Sequence

Technology: TO

Table: BaselineShipments

Internal Name: DeliverySequenceID

Type: Number (Integer)

Enter the sequence number for the stop to deliver the shipment on the defined route. Sequence numbers do not need to be consecutive. For example, you can define sequence numbers as 1, 4, 5, rather than 1, 2, 3.

Default value: null

Additional Shipments Insertion Rule

Technology: TO

Table: BaselineShipments

Internal Name: AdditionalShipmentsInsertionRule

Type: Text (100)

Use this column to control whether or not additional shipments can be inserted into a delivery sequence when using Shipment Constraints. You identify where additional shipments can be inserted in the delivery sequence with respect to the shipment in the Shipment Constraint:

• null - If no value is populated, additional shipments cannot be inserted on the route. In this case, the route is fixed to those shipments populated in the Shipment Constraints table for the route.
• Insert After - Additional shipments can be inserted before the shipment in the Shipment Constraint.
• Insert Before - Additional shipments can be inserted after the shipment in the Shipment Constraint.
• Insert Anywhere - Additional shipments can be inserted both before and after the shipment in the Shipment Constraint.

Shipments that are not currently assigned to routes using the Shipment Constraints table are considered for insertion based on the Additional Shipments Insertion Rule.

If there are conflicting rules for shipments defined on the same route in Shipment Constraints, then the solver ignores the Additional Shipments Insertion Rule value. It treats this as case as "do not allow shipment insertion for the entire route".

If some shipments from the same route have Insert Before and others have Insert After, then the solver selects the rule from the first shipment on the route instead of treating it as null. For example, if the first Shipment Constraint record for a route has "Insert After" as the Additional Shipments Insertion Rule and the second Shipment Constraint record for the same route has "Insert Before", all shipments will be considered using "Insert After" (the first shipment's rule).

Default value: null

Asset

Technology: TO

Table: BaselineShipments

Internal Name: AssetName

Type: Text (255)

Select the transportation asset associated with the baseline shipment.

Default value: null

Asset Domicile

Technology: TO

Table: BaselineShipments

Internal Name: AssetSiteName

Type: Text (255)

Select the site at which the assigned transportation asset is located.

Default value: null

Asset Tour

Technology: TO

Table: BaselineShipments

Internal Name: TourID

Type: Text (255)

Enter the tour that defines a grouping of routes when using Optimize Fleet Size. When you assign routes to a tour, use the Route Sequence ID to determine the order in which the routes occur on the tour.

Default value: null

Route Sequence

Technology: TO

Table: BaselineShipments

Internal Name: RouteSequenceID

Type: Number (Integer)

Enter the sequence number of the route on the tour. This sequence applies when you use Optimize Fleet Size and have defined an Asset Tour for the route.

Default value: null

Force Ship Direct

Technology: TO

Table: BaselineShipments

Internal Name: ForceShipDirect

Type: Boolean

One of Yes, No

When this field is set to Yes, the solver forces the shipment to use the Direct Shipping Method. When set to No, the solver attempts to route the shipments on a multi-stop route.

Default value: No

Linehaul Route

Technology: TO

Table: BaselineShipments

Internal Name: LinehaulRouteID

Type: Text (255)

When you use the Hub Optimization problem type, you can specify the route ID for the linehaul route into or out of the hub. Use the Hub ID field to determine the hub. Linehaul routes are direct (not multi-stop).

Default value: null

Hub

Technology: TO

Table: BaselineShipments

Internal Name: HubID

Type: Text (255)

Select the hub location through which the shipment is forced. The hub applies when you use the Hub Optimization problem type.

Default value: null

Status

Technology: TO

Table: BaselineShipments

Internal Name: Status

Type: Short Text (50)

One of Include, Exclude.

Use this field to exclude records from Transportation Optimization.

Default: Include