Transportation Policies

Internal Table Name: TransportationPolicies

Transportation Policies are considered unique based on the combination of Source Site, Destination Site, Product Name and Mode.

Evaluation of policy records depends on the use of groups and filters for the columns listed above. For more information, see Group precedence.

Source

Technology: NO IO S

Table: TransportationPolicies

Internal Name: SourceSite

Type: Short Text (100)

Choose the source site or site group from which the product is to be transported.

Destination

Technology: NO IO S

Table: TransportationPolicies

Internal Name: DestinationSite

Type: Short Text (100)

Select the destination site or site group that will receive the product.

Ship To

Technology: S

Table: TransportationPolicies

Internal Name: ShipToSite

Type: Short Text (100)

Available only in Classic Simulation. If the Ship To field is used in a transportation policy it means that the Source-Destination lane becomes a virtual lane. The Source does not ship directly to the Destination, but it ships to the site specified in the Ship To field (the end destination of the route is still the site specified in the Destination Site field). Transportation policies for the Source - Ship To and Ship To - Destination site combinations need to exist in the Transportation Policies table. The Ship To value should be different than both the Source and Destination values.

Product

Technology: NO IO S

Table: TransportationPolicies

Internal Name: ProductName

Type: Short Text (100)

Choose the product or product group to be transported. Transportation Policies can be product-specific, apply only to a set of products (using a group or filter), or apply to all products on that lane if the Product Name is left blank. Specifying a product will create a product-specific transportation policy that only affects transporting this product from Site A to Site B. No other product will use this policy.

If you select a dynamic filter or group for the Product value, please note the following:

• For Network Optimization, you will select:
  • The “Each” method to create a lane for each product in the filter/group. This is the more common use case.
  • The "All" method in the case where a Mode is applied to the Transportation Policies record and the Mode record has Bundle Products set to "Yes". This is considered a Product set. When the Mode conditions are met, the Product set name is included in the transportation input files for use by Network Optimization. When the Mode conditions are not met, the Product set name is not written to the transportation input files.
• For Simulation, you can select either “Each” to create a lane for each product, or “All”. For example, there may be 100 "Frozen" products that require a "Frozen" mode of transportation. Define a group of the 100 products and use that group name in the Product field of the Transportation Policies table with “All” as the method. This allows all 100 products to be routed together.

If you are using the aggregate or disaggregate transportation policy, you will designate a transportation asset type as "container" in the Transportation Assets table.

Mode

Technology: NO IO S

Table: TransportationPolicies

Internal Name: Mode

Type: Short Text (100)

The mode can be either a descriptive term, such as Customer_Delivery or TruckingCompany1, or the name of a detailed mode definition created in the Modes table. You use the Modes table to define the costs, assets and other characteristics of a transportation mode.

Default: 1

Transportation Policy

Technology: NO IO S

Table: TransportationPolicies

Internal Name: ModeSelectionRule

Type: Short Text (100)

Enumerated list.

Choose the Transportation Policy to be used for transportation policies that have multiple modes (these have the same Source-Destination combination). The options are explained in the table below.

Default: First

Policy Parameter

Technology: NO IO S

Table: TransportationPolicies

Internal Name: ModeParameter

Type: Short Text (100)

Enumerated list.

The parameter is used differently depending on the Transportation Policy specified.

Default: null

Review Period

Technology: NO S

Table: TransportationPolicies

Internal Name: ReviewPeriod

Type: Short Text (100)

Enter how often the queue at the transportation lane is checked in Simulation. If shipment requirements based on Mode Function are met (such as Transportation Asset fill levels) at a Review Period, the shipment occurs. Select the Review Period: Continuous, Hourly, Daily, Weekly, Monthly. Alternately, you can enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

The default Review Period is Continuous, the queue is evaluated every time a shipping item enters. If you specify a Review Period, items are queued and then evaluated together. By default, all of the provided transportation policies make decisions of the aggregate contents of the queue. For example, if the Transportation Policy is "On Weight", and you have a Review Period of Daily, then each day, Simulation sums the weight of all the items in queue and applies the Transportation Policy to choose a mode.

The Review Period can be one of the values in the drop down list, set to one value, or assigned a schedule. The table below shows how to enter data in this field:

Review Periods themselves are dependent on the start time of Simulation. For example, assume the start time set in the Model Settings is 12:00 AM 1/1/2016, and the Review Period is set to 2 DAY. The queue at the lane is reviewed every two days at 12:00 AM. You can enter an offset in front of the Review Period to change the time the model will start reviewing. The offset is incurred only once. For example, if you want to review the queue every day at 4 PM, and the Simulation starts at 12 AM, enter an offset of 16 hours to shift the review time to 4 PM. Then, if the Review Period is 2 DAY, it checks every 2 days from the time to which it was offset. The format for the offset is: < "time" >

For a 16 hour offset with a Review Period every 2 days, you would enter: <16 HR>, 2 DAY.

For Network Optimization, Review Period is used as part of a Replenishment Frequency replacement scheme when calculating cycle stock. If Replenishment Frequency is not defined, Network Optimization uses the maximum of Review Period or Shipment Period in calculating cycle stock.

Mode Function

Technology: NO S

Table: TransportationPolicies

Internal Name: TransportationPolicy

Type: Short Text (100)

Enumerated list.

Select the Mode Function that applies to the lane (source-destination-product/group/set):

Default: LTL

Shipment Period

Technology: NO S

Table: TransportationPolicies

Internal Name: ShipmentPeriod

Type: Short Text (255)

Enter the schedule for a periodic shipment. The Shipment Period is not dependent on other conditions being met; it simply specifies the schedule for shipment departures for items in the Mode queue.

The Shipment Period can be left blank, set to one value, or assigned a schedule. The table below shows how to enter data in this field:

Shipment schedules themselves are dependent on the start time of Simulation. For example, assume the start time set in the Model Settings is 12:00 AM 1/1/2016, and the Shipment Period is set to 24 HR. The shipment departs every day at 12:00 AM. You can enter an offset in front of the Shipment Period to change the time the shipment will depart. The offset is incurred only once. For example, if you want to ship every day at 4 PM, and the Simulation starts at 12 AM, enter an offset of 16 hours to shift the departure time to 4 PM. Then, if the Shipment Period is 24 HR, it checks every 24 hours from the time to which it was offset. The format for the offset is: < "time" >

For a 16 hour offset with a daily Shipment Period, you would enter: <16 HR>, 24 HR.

For Network Optimization, Shipment Period is used as part of a Replenishment Frequency replacement scheme when calculating cycle stock. If Replenishment Frequency is not defined, Network Optimization uses the maximum of Review Period or Shipment Period in calculating cycle stock.

Replenishment Frequency

Technology: NO IO S

Table: TransportationPolicies

Internal Name: ShipmentFrequency

Type: Short Text (255)

Specifies the number of days between receipt of additional product at the destination site. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used. This field is primarily used for demand propagation, and in cycle stock optimization and safety stock optimization. For safety stock calculation, when the Service Definition is Type 2 or Type 3, this value is used to derive the Min Replenishment Qty. For more information about Replenishment Frequency, see Cycle Stock Optimization. For information about Min Replenishment Qty, refer to Inventory Policy Details.

Transport Time

Technology: NO IO S

Table: TransportationPolicies

Internal Name: TransportTime

Type: Short Text (100)

Enter the length of time that a shipment takes to travel from the Source site to Destination site. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

If a probability distribution is used, in Simulation the distribution is sampled and a different transport time is determined for each shipment. Simulation is the only solver that uses all parameters in bounded distributions. In Network Optimization, the transport time (using the mean) and transport time standard deviation is used as fixed inputs. In Safety Stock Optimization, only Normal distributions can be used - these populate the transportation lead time mean and standard deviation.

Transport Time is not a required field for any transportation policy. If no time is entered, a default will be calculated from Source site to Destination site based on the latitude and longitude of each site, taking the speed of the transportation asset into account (Distance / Speed). When no Asset is defined on the Mode in the transportation policy, the Default Transport Speed specified on the Model Settings will be used.

Transport Time and Multiple Periods

Network Optimization looks at the Transport Time of each Transportation Policy individually compared to time period length. If individual Transport Times are less than the period length, all flows will occur within a single period. The Transport Times are not summed up for the full transportation path. For example, assume you have period lengths of one week. The Transport Time from MFG to DC is 5 days and from DC to Customer is 4 days. The InterSite Flow and Customer Flow for this solution will both occur within the same period if no other factors are considered.

Distance

Technology: NO IO S

Table: TransportationPolicies

Internal Name: Distance

Type: Short Text (255)

Enter the distance between the source and destination. Enter a value, then optionally select a distance unit of measure. If you do not select a unit of measure, the default Distance Unit Of Measure from Model Settings is used.

Asset

Technology: NO IO S

Table: TransportationPolicies

Internal Name: AssetName

Type: Short Text (100)

Choose the asset that will transport your product. This field is necessary when using the Full TL and Pooled policies and optional for others.

Variable Transportation Cost

Technology: NO IO S

Table: TransportationPolicies

Internal Name: VariableTransportationCost

Type: Short Text (100)

RNE Eligible

The Variable Transportation Cost field is related to the Variable Cost Basis field. The value entered in the Variable Transportation Cost field is the transportation cost per Variable Cost Basis unit. For example, in Variable Cost Basis select Quantity from the drop down list, then select EA, Variable Transportation Cost should be the cost to ship 1 unit. If Variable Cost Basis is MI, the Variable Transportation Cost should be the cost of shipping 1 mile.

If a lookup cannot be found for a cost definition (such as Step Costs and Lane Costs), a cost of 9999 will be incurred.

Variable Transportation Cost is reflected in the Total Transportation Cost in the Network Summary output table.

For Simulation, you can also populate the Variable Transportation Cost using a Scripted Simulation input pipe.

Default: 0

Variable Cost Basis

Technology: NO IO S

Table: TransportationPolicies

Internal Name: VariableCostBasis

Type: Short Text (100)

One of Weight, Quantity, Volume, Distance, Time, Weight-Distance, Quantity-Distance, Volume-Distance, Weight-Time, Quantity-Time, Volume-Time.

Choose the formula for calculating the total transportation cost for a shipment from Source site to Destination site. The default Variable Cost Basis is Qty. Actual shipment Cost is calculated as follows:

The unit transportation cost is then multiplied by the flow to calculate the shipment cost.

For example, assume you have the following Product and Customer Demand data:

and the following Transportation Policy data:

For various Variable Cost Basis settings and with all demand served on the flow, the shipment costs for Product A are as follows:

Default: Quantity

Fixed Shipment Cost

Technology: NO IO S

Table: TransportationPolicies

Internal Name: FixedShipmentCost

Type: Short Text (100)

Enter the fixed cost for each shipment that uses this Transportation Policy.

If a lookup cannot be found for a cost definition (such as Step Costs and Lane Costs), a cost of 9999 will be incurred.

Fixed Transportation Cost is reflected in the Total Transportation Cost in the Network Summary output table.

Fixed Shipment Cost cannot be applied to a transportation policy that is used for returns modeling (where product is being returned from a customer to a site).

Shipment Size

Technology: NO S

Table: TransportationPolicies

Internal Name: AverageShipmentSize

Type: Short Text (100)

In this field, enter the average size of your shipments. Enter a value, then optionally select a quantity, weight or volume unit of measure. If you do not select a unit of measure, the default Quantity Unit Of Measure from Model Settings is used. It is used to determine how many trips are needed to satisfy the flow of product for the respective mode.

For example, if the average shipment weight for a mode is 50 and 100 units of weight flow on the mode, there are 2 required trips. If the Variable Cost Basis is Distance, the transportation cost for this mode would be the Variable Transportation Cost (200 from the previous example) times the distance (found in the Distance field) times the number of trips (2).

Simulation makes use of the Shipment Period in the Transportation Policies table when looking to consolidate eligible shipments. For example, if a lane supports both Product1 and Product2 and the Shipment Period is 1 DAY, shipments for each of these products that occur on a specific date, such as 1/1/2021, can be consolidated. This consolidation is not supported with Classic Simulation.

Default: 1

Shipment Rule

Technology: NO

Table: TransportationPolicies

Internal Name: ShipmentRule

Type: Short Text (50)

One of Prorate Shipment Cost, Treat Shipment Cost as Fixed, Enforce Full Shipments, Treat All Costs as Fixed .

This field determines how Shipment Size is handled in terms of applying the Fixed Shipment Cost:

• Prorate Shipment Cost – The fixed cost is prorated based on the Shipment Size.
• Treat Shipment Cost as Fixed – The fixed cost is based on a flow quantity that is rounded to the next multiple of Shipment Size.
• Treat All Costs as Fixed - Both the fixed cost and the variable cost is based on a flow quantity that is rounded to the next multiple of Shipment Size.
• Enforce Full Shipments – The fixed cost is based on a flow value that must be a multiple of Shipment Size or 0. If the flow on a lane is not a multiple of the lane’s Shipment Size and the destination location can store inventory, the flow is rounded up and the excess is held as inventory. If the destination does not have the ability to store inventory (a site with no inventory policy or a customer), the model is infeasible assuming the flow is necessary.

For example, assume a Shipment Size of 1000 and a Fixed Cost of 100. There is also a Variable Transportation Cost of 1. If the flow quantity is 1500:

• Prorate Shipment Cost – The fixed cost is prorated for the flow quantity of 1500, so the fixed cost is 150.
• Treat Shipment Cost as Fixed – The flow quantity of 1500 is rounded to the next multiple of Shipment Size (2000), so the fixed cost is 200.

• Treat All Costs as Fixed – The flow quantity of 1500 is rounded to the next multiple of Shipment Size (2000). The fixed cost 200. The variable cost is 2000. The total cost is 2200

• Enforce Full Shipments – The flow quantity of 1500 is not a multiple of Shipment Size. If the flow is to a site that has an inventory policy, the flow is rounded up and the excess is held as inventory. If the flow is to a customer or a site with no inventory policy, the model is infeasible since it cannot satisfy this Shipment Rule and there is no fixed cost.

The Variable Transportation Cost is based on the actual flow/shipment size and is not rounded in the same way the Fixed Shipment Cost is handled, unless you are using the Treat All Costs as Fixed rule.

Keep in mind that units of measure are considered when calculating the fixed cost. Assume a Shipment Size of 100 EA and a Fixed Shipment Cost of 1000. If the flow quantity is 100 EA and you are using Prorate Shipment Cost, the fixed cost is 1000. However, if the Shipment Size is 100 DOZ, the fixed cost is 1000 * (100/1200) = 83.33

Product Class

Technology: NO IO S

Table: TransportationPolicies

Internal Name: ProductClass

Type: Short Text (50)

Enumerated list.

Product Class supports non product-specific Transportation Policies for use with RateWare XL in the Cost and Variable Transportation Cost fields.

If you enter a value for this field, it is used for RateWare XL lookups in the Variable Transportation Cost and Cost fields in combination with the Shipment Weight field. This class is used instead of the Class value on the Products table (based on the Product specified in the Product Name field on the Transportation Policies table).

If you do not provide a value for this field and the Transportation Policy is product-specific, the Product Name field is used to look up the Class on the Products table. If neither Class nor Product Name is specified for the Transportation Policy, a message is displayed: "Rate request data missing".

Duty Rate

Technology: NO IO S

Table: TransportationPolicies

Internal Name: DutyRate

Type: Short Text (100)

In this column, enter a duty rate to represent the taxes and tariffs that will be levied for each shipment on this lane. If the Duty Rate percentage is 10%, enter "0.1" in this column. The actual duty cost is calculated by multiplying the duty rate by the shipment’s total value (Unit Value from the Product table multiplied by shipment quantity.)

Duty Rate is reflected in the Total Duty Cost in the Network Summary output table. It is also reported in the Duty Cost column in the Cost To Serve Details output table when Cost To Serve Analysis is run.

Discount Rate

Technology: NO IO S

Table: TransportationPolicies

Internal Name: DiscountRate

Type: Short Text (100)

Enter the discount factor negotiated with the transportation company. This rate is multiplied by the cost to determine the actual cost. For example, if the negotiated discount is 30%, the discount rate is 1.0 - .30 or .70, so you enter a discount rate of 0.70. If the cost is $100, 0.70 is multiplied by 100 to get an actual rate of $70.

Discount Rate is reflected in the Total Transportation Cost in the Network Summary output table.

If no value is populated, the default is 1 (no discount).

Default: null

Minimum Charge

Technology: NO IO S

Table: TransportationPolicies

Internal Name: MinimumCharge

Type: Short Text (100)

In this column enter the minimum rate negotiated with the transportation company. Minimum charges override costs if the total transportation cost is less than the minimum cost calculated using Minimum Charge. In that case, the calculated minimum cost is applied.

minimum cost = Minimum Charge / avg shipment qty

where avg shipment qty = avg shipment weight / product Unit Weight

Assume the following:

Product Unit Weight = 5 LB

Minimum Charge = 10000

Variable Transportation Cost = 3

Fixed Shipment Cost = 1150

Shipment Size = 250 LB

Demand Quantity = 10 EA

The minimum cost would be calculated as:

Minimum Charge / (Shipment Size / Unit Weight) = 10000 / (250 / 5) = 200

The cost for comparison is determined based on the Shipment Rule:

If Shipment Rule is Prorate Shipment Cost, the cost for comparison is the summation of Variable Transportation Cost and Fixed Shipment Cost:

Total Transportation Cost = Flow Qty * MAX(minimum cost, Variable Transportation Cost + Fixed Shipment Cost / Shipment Size)

Total Transportation Cost = 10 * MAX(200, 3 + (1100 / 250)) = 10 * 200 = 2000

If Shipment Rule is not Prorate Shipment Cost, the Minimum Charge is compared with the Variable Transportation Cost only:

Total Transportation Cost = (Flow Qty * MAX(minimum cost, Variable Transportation Cost)) + Fixed Shipment Cost * number of shipments

Total Transportation Cost = (10 * MAX(200, 3)) + 1150 = 2000 + 1500 = 3500

Minimum Charge is reflected in the Total Transportation Cost in the Network Summary output table.

The Transportation Cost based on the Minimum Charge calculation uses the Shipment Size, the Product Unit Weight, the Flow associated with the Shipment Size and the Minimum Charge.

If you change the Shipment Size to Volume, then the Product Unit Volume value is considered.

Fuel Surcharge

Technology: NO

Table: TransportationPolicies

Internal Name: FuelSurcharge

Type: Short Text (255)

Use this field to represent a fuel surcharge that is incurred in addition to the normal transportation cost in Network Optimization. The Fuel Surcharge affects how the calculated Variable Transportation Cost is determined. Use the Fuel Surcharge Basis column to determine how the Fuel Surcharge is determined.

Assume the Fuel Surcharge Basis is "% Variable Cost" and the Variable Cost Basis is "MI":

Variable Transportation Cost = 10

Distance = 100 MI

Shipment Size = 2

Fuel Surcharge = 15

The per unit transportation cost is calculated as:

(Variable Transportation Cost * Distance) / Shipment Size = (10 * 100) / 2 = 500

Applying the fuel surcharge is calculated as:

500 * (1 + (Fuel Surcharge / 100)) = 500 * (1 + 0.15) = 575

Fuel Surcharge Basis

Technology: NO

Table: TransportationPolicies

Internal Name: FuelSurchargeBasis

Type: Short Text (100)

One of % Variable Cost, Cost per Unit, or a valid Unit of Measure such as LB, KM

Use this field to determine how the Fuel Surcharge should be applied:

• % Variable Cost – Variable transportation cost is calculated as Variable Transportation Cost * (1 + Fuel Surcharge percentage)
• Cost per Unit – Variable transportation cost is calculated as Variable Transportation Cost + Fuel Surcharge.
• Unit of Measure – Variable transportation cost is calculated as Variable Transportation Cost + Value of UOM column

For example, assume:

Variable Transportation Cost = 50

Fixed Shipment Cost = 125

Fuel Surcharge = 5

Distance = 35 MI

If Fuel Surcharge Basis = % Variable Cost:

Variable transportation cost = 50 * (1 + 0.05) = 52.5

If Fuel Surcharge Basis = Cost per Unit

Variable transportation cost = 50 + 5 = 55

If Fuel Surcharge Basis = MI

Variable transportation cost = 50 + (5 * 35) = 225

CO2

Technology: NO IO S

Table: TransportationPolicies

Internal Name: CO2

Type: Short Text (255)

In this field, set the CO2 emissions for this transportation policy based on the CO2 Basis. This is the emission amount expressed as a weight. Enter a value, then optionally select a weight unit of measure. If you do not select a unit of measure, the default Weight Unit Of Measure from Model Settings is used.

For example, assume that you enter .04 and select LB as the Unit Of Measure for CO2. Also assume that you select Weight-Distance for CO2 Basis, then select T-MI (ton per mile) as the Units Of Measure for CO2 Basis. This defines .04 LB of CO2 per ton of product moved over one mile by this transportation asset.

CO2 Basis

Technology: NO IO S

Table: TransportationPolicies

Internal Name: CO2Basis

Type: Short Text (50)

Use this field to select the basis for determining CO2 emissions. The CO2 Basis is applied to the CO2 value. If you select a basis that is made up of two different measures (such as Weight-Distance), you can select the Unit Of Measure for each of these measures.

For example, assume that you enter .04 and select LB as the Unit Of Measure for CO2. Also assume that you select Weight-Distance for CO2 Basis, then select T-MI (ton per mile) as the Units Of Measure for CO2 Basis. This defines .04 LB of CO2 per ton of product moved over one mile by this transportation asset.

Select one of the values as shown:

Require Return Trip

Technology: S

Table: TransportationPolicies

Internal Name: RequireReturnTrip

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

If an Asset is defined on the Mode used in the transportation policy, this field specifies if the asset must require a return trip.

Default: Yes

Return Trip Time

Technology: NO IO S

Table: TransportationPolicies

Internal Name: ReturnTripTime

Type: Short Text (100)

In Simulation, if an asset requires a return trip, this is the time it takes for asset to travel from final destination to initial start point. In Network Optimization, this time is included when an Asset is defined on the Mode used for the transportation policy, regardless of the Require Return Trip field value. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Return Trip Cost

Technology: NO IO S

Table: TransportationPolicies

Internal Name: ReturnTripCost

Type: Short Text (50)

If an Asset is defined on the Mode used in the transportation policy, this field specifies the cost for the asset to return to the Source Site. This cost is reported in the Variable Cost field of Transportation Assets Summary Optimization Output.

Load Resource

Technology: S

Table: TransportationPolicies

Internal Name: LoadWorkResource

Type: Short Text (100)

Select the work resource used to load the shipment. The work resource must be listed in the Work Resource table.

Unload Resource

Technology: S

Table: TransportationPolicies

Internal Name: UnloadWorkResource

Type: Short Text (100)

Select the work resource used to unload the shipment. The work resource must be listed in the Work Resource table.

Auto-Release Load Resource

Technology: S

Table: TransportationPolicies

Internal Name: AutoReleaseLoadWorkResource

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

Select Yes if the work resource used for loading is to be automatically released and becomes immediately available for loading. Selecting No assumes that the user will write a script for simulation to release the resource.

Default: Yes

Auto-Release Unload Resource

Technology: S

Table: TransportationPolicies

Internal Name: AutoReleaseUnloadWorkResource

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

Select Yes if the work resource used for unloading is to be automatically released and becomes immediately available for unloading. Selecting No assumes that the user will write a script for simulation to release the resource.

Default: Yes

Fixed Load Cost

Technology: NO S

Table: TransportationPolicies

Internal Name: LoadCost

Type: Short Text (50)

This is the cost to load a complete shipment onto the transportation asset. This cost is only triggered when an Asset is defined on the Mode assigned to the Transportation Policy.

Optimization: Takes the number of trips traveled by an asset type and applies the load cost to each individual trip. This cost is reported in the Total Transportation Asset Cost in the Network Summary and in the Variable Transportation Cost field of Transportation Assets Summary Optimization Output.

Simulation: Applies the load cost to each individual shipment.

Fixed Load Cost is reflected in the Total Transportation Cost in the Network Summary output table.

Unit Load Cost

Technology: S

Table: TransportationPolicies

Internal Name: UnitLoadCost

Type: Short Text (50)

This is the cost to load one unit of product.

Fixed Load Time

Technology: NO S

Table: TransportationPolicies

Internal Name: LoadTime

Type: Short Text (50)

This is the time taken for the product to be prepared for dispatch. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Optimization: This is the fixed load time for the overall flow, not per unit.

Unit Load Time

Technology: S

Table: TransportationPolicies

Internal Name: LoadUnitTime

Type: Short Text (50)

The amount of time to load each individual unit of product. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Fixed Unload Cost

Technology: NO S

Table: TransportationPolicies

Internal Name: UnloadCost

Type: Short Text (50)

This is the cost to unload a complete shipment from the transportation asset. This cost is only triggered when an Asset is defined on the Mode assigned to the Transportation Policy.

Optimization: Takes the number of trips traveled by an asset type and applies the unload cost to each individual trip. This cost is reported in the Total Transportation Asset Cost in the Network Summary and in the Variable Transportation Cost field of Transportation Assets Summary Optimization Output.

Simulation: Applies the unload cost to each individual order.

Fixed Unload Cost is reflected in the Total Transportation Cost in the Network Summary output table.

Unit Unload Cost

Technology: S

Table: TransportationPolicies

Internal Name: UnitUnloadCost

Type: Short Text (50)

This is the cost to unload one unit of product.

Fixed Unload Time

Technology: NO S

Table: TransportationPolicies

Internal Name: UnloadTime

Type: Short Text (50)

This is the time taken for the product to be unloaded. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Optimization: This is the fixed unload time for the overall flow, not per unit.

Unit Unload Time

Technology: S

Table: TransportationPolicies

Internal Name: UnloadUnitTime

Type: Short Text (50)

The amount of time to unload each individual unit of product. Enter a value, then optionally select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Requirement Type

Technology: NO

Table: TransportationPolicies

Internal Name: FlowRequirementType

Type: Short Text (50)

One of Min, Cond Min, Max, Fixed.

Choose the flow requirement type - conditional minimum, minimum, maximum, or fixed. This defines how the Requirement Value is used in an optimization. The conditional minimum flow establishes that, in order to use this transportation lane for any shipments, a minimum flow is necessary. Essentially this constraint is similar to saying the flow can be 0 or higher than the minimum.

Simulation: This field is not used.

Requirement Value

Technology: NO

Table: TransportationPolicies

Internal Name: FlowRequirement

Type: Short Text (100)

Enter the amount of this product required for shipment over the transportation lane. Enter a value, then optionally select a quantity, weight or volume unit of measure. If you do not select a unit of measure, the default Quantity Unit Of Measure from Model Settings is used. Its use is determined by other flow requirement fields listed below; Requirement Type and Requirement Period.

Flow refers to the amount of product moved by this transportation policy in a given time period. Constraint fields are only used in an optimization; a simulation run will ignore these four fields. An optimization will use flow requirements as constraints.

Simulation: This field is not used.

Default: 0

Requirement Period

Technology: NO

Table: TransportationPolicies

Internal Name: FlowRequirementPeriod

Type: Short Text (50)

One of Period Length, Day, Week, Month (30 Day), Quarter (91 Day), Year.

Choose the period over which the Requirement Value is to be established - Day, Week, Month, Quarter, or Year. When left blank the horizon of the optimization will be used as the Requirement Period.

Simulation: This field is not used.

Lane Consignment Queue Basis

Technology: S

Table: TransportationPolicies

Internal Name: LaneConsignmentQueueBasis

Type: Short Text (50)

One of None, Item, Quantity, Weight, Volume, Value.

Simulation: Specifies the basis by which the lane consignments are reported. Select from item, quantity, weight, volume, or value. To see output, select Lane Consignment Queue type in the Queue Statistics section of Run Options of a Simulation run.

Default: None

Mode Consignment Queue Basis

Technology: S

Table: TransportationPolicies

Internal Name: ModeConsignmentQueueBasis

Type: Short Text (50)

One of None, Item, Quantity, Weight, Volume, Value.

Simulation: Specifies the basis by which the mode consignments are reported. Select from item, quantity, weight, volume, or value. To see output, select Lane Consignment Queue type in the Queue Statistics section of Run Options of a Simulation run.

Default: None

Chance For Ambush

Technology: S

Table: TransportationPolicies

Internal Name: ChanceForAmbush

Type: Short Text (50)

Simulation: This field specifies the percent of time that an ambush will occur. It is interpreted as a percentage. It can be defined as a number or as a distribution.

Ambush Delay

Technology: S

Table: TransportationPolicies

Internal Name: AmbushDelay

Type: Short Text (50)

Simulation: When an ambush occurs, this specifies how long the shipment will be delayed.

Ambush Damage

Technology: S

Table: TransportationPolicies

Internal Name: AmbushDamage

Type: Short Text (50)

Simulation: This field specifies the percent of vehicles destroyed when an ambush occurs. It is interpreted as a percentage. It can be defined as a number or as a distribution.

Reorder When Destroyed

Technology: S

Table: TransportationPolicies

Internal Name: ReorderWhenDestroyed

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

Simulation: This field gives you a choice to place an immediate "replacement" order to make up for a destroyed shipment. When this field is "Yes", Simulation places an order that has the same characteristics (due date, qty, product type, etc.) of the destroyed shipment. When this field is "No", nothing is done.

Unit Delay Factor

Technology: S

Table: TransportationPolicies

Internal Name: UnitDelayFactor

Type: Short Text (50)

Simulation: Specify the unit delay factor for surviving members of an ambushed convoy. This factor is multiplied by the number of destroyed vehicles in the event of an ambush. You can provide a constant, such as 2 hours, or a distribution.

Delay Factor

Technology: S

Table: TransportationPolicies

Internal Name: OrderDelayFactor

Type: Short Text (50)

Simulation: Specify the order delay factor for surviving members of an ambushed convoy.

Minimum Replenishment Quantity

Technology: IO

Table: TransportationPolicies

Internal Name: MinShipmentQty

Type: Short Text (50)

In Safety Stock Optimization, the Minimum Replenishment Quantity is the maximum of the Sourcing Policies Minimum Order Quantity and the Transportation Policies Minimum Replenishment Quantity.

Minimum Service Time

Technology: IO

Table: TransportationPolicies

Internal Name: MinServiceTime

Type: Short Text (50)

Specifies the constraint for the minimum service time on the lane. This time is in units of DAY.

Maximum Service Time

Technology: IO

Table: TransportationPolicies

Internal Name: MaxServiceTime

Type: Short Text (50)

Specifies the constraint for the maximum service time on the lane. This time is in units of DAY.

Guaranteed Service Time

Technology: S

Table: TransportationPolicies

Internal Name: GuaranteedServiceTime

Type: Short Text (50)

The Guaranteed Service Time is used to determine if the Source site can ship the Product to the Destination on the defined Mode within this time frame. If this is not possible, the order is considered to have been missed and the Fill Rate may decrease. The Guaranteed Service Time is in terms of days. It is calculated on a Source-Destination-Product-Mode basis.

Responsible Party

Technology: NO

Table: TransportationPolicies

Internal Name: ResponsibleParty

Type: Short Text (100)

One of Source, Destination.

Select whether the Source or the Destination is the party responsible for taxes and duties incurred with transit. If the Sites and Customers in the Transportation Policies have Organization values assigned to them, this value will also determine whether Customer Flows and InterSite Flows are assigned to the Source Organization or Destination Organization.

Lane Name

Technology: NO IO S

Table: TransportationPolicies

Internal Name: LaneName

Type: Short Text (100)

Specify a name for this transportation lane.

Path Name

Technology: S

Table: TransportationPolicies

Internal Name: PathName

Type: Short Text (100)

Enter the name of the transportation path. You define the detailed path in the Transit Matrix table.

Load Schedule Rule

Technology: S

Table: TransportationPolicies

Internal Name: LoadScheduleRule

Type: Short Text (32)

One of null, RunUntilUnavailable, RunToCompletion, CompleteWithinWindow

Not available in Classic Simulation. The Load Schedule Rule acts as a constraint on loading at a site when using the "Simulation" problem type. The load times come from either the Unit Load Time or the Fixed Load Time in the Transportation Policies table.

• When using Unit Load Time, this load time value represents the load rate.
• The load rate is converted to hours, quantity of load possible = load rate (in hours) x hours until the site closes.
• When using Fixed Load Time, load rate = shipment quantity / Fixed Load Time

For example, assume that a site is open from 08:00 to 16:00. The current time is 13:00. As a result, there are 3 hours of load time available. The quantity loaded will be based on the Unit LoadTime or on the shipment quantity / Fixed Load Time.

You set the Load Schedule Rule to one of the following:

• RunUntilUnavailable – Loading is constrained by the closing time of the site. With this rule, whatever quantity can be loaded between the current time in the model run and the site closing time on a particular day is loaded. The remaining quantity, if any, is loaded when the site opens again. Using the example above, if there are 10 hours needed to load, the loading stops at 16:00 and resumes when the site next opens.

• RunToCompletion - Loading continues until completion irrespective of whether the business hours at the site are honored or not. Using the example above, if there are 10 hours needed to load, the loading continues and does not stop at 16:00.
• CompleteWithinWindow - Loading is constrained by the closing time of the site. With this rule, whatever quantity can be loaded between the current time in the model run and the site closing time on a particular day is loaded. The remaining quantity, if any, is loaded when the site opens again. Using the example above, if there are 10 hours needed to load, the loading stops at 16:00 and resumes when the site next opens. The loading then continues irrespective of whether the business hours at the site are honored or not. This rule is a hybrid of the other two rules.

Default: RunUntilUnavailable

Unload Schedule Rule

Technology: S

Table: TransportationPolicies

Internal Name: UnloadScheduleRule

Type: Short Text (32)

One of null, RunUntilUnavailable, RunToCompletion, CompleteWithinWindow

Not available in Classic Simulation. The Unload Schedule Rule acts as a constraint on unloading at a location when using the "Simulation" problem type. The unload times come from either the Unit Unload Time or the Fixed Unload Time in the Transportation Policies table.

• When using Unit Unload Time, this value represents the load rate.
• When using Fixed Unload Time, load rate = shipment quantity / Fixed Unload Time
• The unload rate is converted to hours, quantity of unload possible = unload rate (in hours) x hours until the site closes.

For example, assume that a site is open from 08:00 to 16:00. The current time is 13:00. As a result, there are 3 hours of unload time available. The quantity unloaded will be based on the Unit UnloadTime or on the shipment quantity / Fixed Unload Time.

You set the Unload Schedule Rule to one of the following:

• RunUntilUnavailable – Unloading is constrained by the closing time of the site. With this rule, whatever quantity can be unloaded between the current time in the model run and the site closing time on a particular day is unloaded. The remaining quantity, if any, is unloaded when the site opens again. Using the example above, if there are 10 hours needed to unload, the unloading stops at 16:00 and resumes when the site next opens.

• RunToCompletion - Unloading continues until completion irrespective of whether the business hours at the site are honored or not. Using the example above, if there are 10 hours needed to unload, the unloading continues and does not stop at 16:00.
• CompleteWithinWindow - Unloading is constrained by the closing time of the site. With this rule, whatever quantity can be unloaded between the current time in the model run and the site closing time on a particular day is unloaded. The remaining quantity, if any, is unloaded when the site opens again. Using the example above, if there are 10 hours needed to unload, the unloading stops at 16:00 and resumes when the site next opens. The unloading then continues irrespective of whether the business hours at the site are honored or not. This rule is a hybrid of the other two rules.

Default: RunUntilUnavailable

Asset Departure Schedule Rule

Technology: S

Table: TransportationPolicies

Internal Name: AssetDepartureScheduleRule

Type: Short Text (32)

One of null, LeaveImmediately, WaitUntilUp

Not available in Classic Simulation. The Asset Departure Schedule Rule acts as a constraint for when assets depart the site when using the "Simulation" problem type:

• LeaveImmediately - The shipment is queued at the downstream location irrespective of whether the downstream location’s business hours are honored or not.
• WaitUntilUp - The shipment is queued at the downstream location only if the downstream location is open based on its general business hours.

Once unloading and loading are complete at the source site, the asset only departs when the source is open based on its general business hours.

Default: LeaveImmediately

Status

Technology: NO IO S

Table: TransportationPolicies

Internal Name: TransportationPolicyStatus

Type: Short Text (25)

One of Include, Exclude.

Choose the transportation policy status:

• Include - This transportation policy is to be included in a simulation or optimization run.
• Exclude - This transportation policy is to be excluded from a simulation or optimization run.

Default: Include

Notes

Technology: NO IO S

Table: TransportationPolicies

Internal Name: TransportationPolicyNotes

Type: Memo

Enter optional descriptive notes about the transportation policy.