Site Orders

Internal Table Name: SiteOrders

You can use Site Orders in place of Site Demand for Network Optimization, Demand Analysis (Safety Stock Optimization), and Simulation.

For each technology, use the Run Options as described below to select demand source:

• Customer Model Demand – Select “Run from Demand table” if you want to use demand as defined in the Customer Demand table. Select “Run from Orders table” if you want to use demand as defined in the Customer Orders table.
• Site Model Demand – Select “Run from Demand table” if you want to use demand as defined in the Site Demand table. Select “Run from Orders table” if you want to use demand as defined in the Site Orders table.

When using Site Orders with Simulation, be sure to create Inventory Policies records for each Site-Product combination used in the Site Orders table.

Site

Technology: NO IO S

Table: SiteOrders

Internal Name: SiteName

Type: Short Text (100)

Enter the Site or site group that is requesting the product.

Product

Technology: NO IO S

Table: SiteOrders

Internal Name: ProductName

Type: Short Text (100)

Enter the product or product group that is being demanded.

Quantity

Technology: NO IO S

Table: SiteOrders

Internal Name: Quantity

Type: Short Text (50)

Enter the amount of product demanded by the customer for this order. 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.

If a probability distribution is specified, the requirement will be randomly selected each time the demand requirement occurs in Simulation. For Optimization, the mean of the distribution will be used as the demand amount.

Demand Date

Technology: NO IO S

Table: SiteOrders

Internal Name: OrderDate

Type: Date/Time

The Demand Date is the date the demand transaction is placed.

For Network Optimization, the Demand Date (or Demand Date Formula) is used to determine the period in which the demand must be satisfied. For example, assume that your model has weekly periods:

If you have demand with an Demand Date of 1/10/2016, this means that the demand must be satisfied in Period_002. Fixed Order Time and Transport Time must be such that the product can reach the customer in Period_002 or the model is infeasible.

Demand Date Formula

Technology: NO IO S

Table: SiteOrders

Internal Name: OrderDateFormula

Type: Short Text (50)

Specify a number or distribution that defines when the order is placed. 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. A value of 0 is the first day of the model horizon.

For Network Optimization, the Demand Date Formula (or Demand Date) is used to determine the period in which the demand must be satisfied. For example, assume that your model has weekly periods:

If you have demand with an Demand Date Formula of 9, this means that the demand must be satisfied in Period_002. Fixed Order Time and Transport Time must be such that the product can reach the customer in Period_002 or the model is infeasible.

Unit Price Override

Technology: NO S

Table: SiteOrders

Internal Name: UnitPrice

Type: Short Text (50)

You can define a customer-specific price for each order. This number will then be used to calculate revenue generated by this site demanding this specific product instead of the value listed in the Price field on the Products Table. Optionally, select a currency to apply to the value. If no currency is selected, the default Currency from Model Settings is used.

If you set Unit Price Override for one or more entries in the Site Orders table, be aware of the following Optimization behavior:

• When the Unit Price Override field is left blank for all Site Orders records, the Price field of the Products table will be used to calculate revenue.
• If you have multiple entries in the Site Orders table for the same Period for the same Site-Product combination, and one of them uses the Unit Price Override field, then this price is used to override the Price of the Products table for this Site-Product combination for the whole order amount in that period. This is because optimization works on aggregates and not individual orders.
• If you have multiple entries in the Site Orders table for the same Period for the same Site-Product combination, and a number of these use the Unit Price field, the straight average of these Unit Price Override numbers is used for the entire order in that Period for this Site-Product combination.
• The Price is a weighted average of the Site Order records per Site-Product created over each period. The weighting of this value takes into consideration demand quantity and occurrences.

Priority

Technology: S

Table: SiteOrders

Internal Name: Priority

Type: Short Text (50)

Simulation: Enter a number indicating priority. This property is accessible when using scripting in simulation.

Tracking ID

Technology: S

Table: SiteOrders

Internal Name: TrackingID

Type: Short Text (50)

If Tracking ID is populated, this value is traced through simulation as long as the facilities through which the order is sourced have inventory policies of "Demand Flow" for the product. This property is accessible when using scripting in simulation as well.

Status

Technology: NO IO S

Table: SiteOrders

Internal Name: Status

Type: Short Text (80)

One of Include, Exclude.

Use this field to exclude Site Orders records when running the model.

Default: Include

Notes

Technology: NO IO S

Table: SiteOrders

Internal Name: Notes

Type: Memo

Use this field to enter optional descriptive information about the order.