Periodic Schedule

Internal Table Name: PeriodicVRPSchedule

You use this table to define constraints, by site (or group of sites) or by customer (or group of customers), for Periodic Optimization. The constraints you populate depend on the source input table - one of Transportation Daily Orders or Shipments:

• Transportation Daily Orders - Populate the Inventory Holding Cost, Inventory Holding Cost Basis, Max Drop Size and Max Storage Capacity. Periodic optimization determines the frequency and delivery days based on the Transportation Daily Orders and a balance of transportation cost and inventory holding cost. If you want to control delivery days, you can also populate the Frequency, Minimum Days Between, Maximum Days Between, Force Include Day(s) and Force Exclude Day(s).
• Shipments - Populate the frequency of deliveries over the model horizon and the minimum and maximum number of days between visits. Additionally, you can force which days in the horizon must be used and which days cannot be used for visits.

Location

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: SiteName

Type: Short Text (100)

This is the site or site group, or customer or customer group, to which the visit schedule applies.

Frequency

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: Frequency

Type: Short Text (100)

Enter the number of visits to the site during the model horizon.

Minimum Days Between

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: MinDaysBetween

Type: Number (Long Integer)

Enter the minimum number of days between visits, if multiple visits occur during the model horizon.

Maximum Days Between

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: MaxDaysBetween

Type: Number (Long Integer)

Enter the maximum number of days between visits, if multiple visits occur during the model horizon.

Forced Include Day(s)

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: ForcedInclude

Type: Short Text (255)

Enter days on which the visits must occur. The first day of the model horizon is 1. For example, assume a model horizon of 1/5/2020 to 1/13/2020. 1/5/2020 (a Sunday) is day 1. If you want visits on Monday and Thursday, enter 2|5 (day values separated by the pipe character).

Forced Exclude Day(s)

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: ForcedExclude

Type: Short Text (255)

Enter days on which the visits must not occur. The first day of the model horizon is 1. For example, assume a model horizon of 1/5/2020 to 1/13/2020. 1/5/2020 (a Sunday) is day 1. If you do not want visits on Tuesday and Friday, enter 3|6 (day values separated by the pipe character).

Inventory Holding Cost

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: InventoryHoldingCost

Type: Short Text (100)

Enter the cost for holding inventory at the location when using Transportation Daily Orders. This is the cost per unit as defined by the Inventory Holding Cost Basis. For example, if the Inventory Holding Cost Basis is set to Weight and your weight unit of measure is LB, the Inventory Holding Cost is the cost per LB held in inventory.

Inventory Holding Cost Basis

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: InventoryHoldingCostBasis

Type: Short Text (100)

One of Quantity, Weight, Volume

Select the basis by which inventory holding cost is assessed. The Inventory Holding Cost is applied to the quantity, weight or volume of Transportation Daily Orders as determined by the Inventory Holding Cost Basis. If no value is populated, the basis is Quantity.

Max Drop Size

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: MaxDropSize

Type: Short Text (100)

Provide the maximum units (based on the Inventory Holding Cost Basis) that can be dropped at the location per day. If you include a unit of measure (such as LB), it must match the Inventory Holding Cost Basis category. In the example of LB, the Inventory Holding Cost Basis must be Weight.

Max Storage Capacity

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: MaxStorageCapacity

Type: Short Text (100)

Enter the maximum units (based on the Inventory Holding Cost Basis) that can be held at the location at any time. If you include a unit of measure (such as LB), it must match the Inventory Holding Cost Basis category. In the example of LB, the Inventory Holding Cost Basis must be Weight.

Status

Technology: TO

Table: PeriodicVRPSchedule

Internal Name: Status

Type: Short Text (50)

One of Include, Exclude.

Use this field to determine if Transportation Optimization should consider the Periodic Schedule record.

Default: Include