Site Demand

Internal Table Name: SiteDemand

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

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.

Period

Technology: NO IO S

Table: SiteDemand

Internal Name: PeriodName

Type: Short Text (100)

Optionally, select the period name to which the demand applies.

For Network Optimization and Inventory Optimization, if you enter a Period , the Series Offset Time is used as an offset from the start of this period. If you do not enter a Period Name, the Series Offset Time is used as an offset from the start of the model horizon.

For Simulation, the Series Offset Time is always used as an offset from the start of the model horizon, regardless of the Period .

Site

Technology: NO IO S

Table: SiteDemand

Internal Name: SiteName

Type: Short Text (100)

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

Product

Technology: NO IO S

Table: SiteDemand

Internal Name: ProductName

Type: Short Text (100)

Enter the product or product group that is being demanded.

Quantity

Technology: NO IO S

Table: SiteDemand

Internal Name: Demand

Type: Short Text (50)

Enter the amount of product demanded by the site. Enter a value, the 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 quantity 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.

Default: 1

Series Offset Time

Technology: NO IO S

Table: SiteDemand

Internal Name: PeriodOffsetTime

Type: Short Text (50)

Specify a number or distribution that defines when the order is placed. A value of 0 is the first day of the model horizon. If you have selected a Period and you are using Network Optimization or Inventory Optimization, a value of 0 is the first day of that period. Enter a value, the 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.

In Simulation, if more than one occurrence is scheduled, then the Series Offset Time field becomes the time of the first Order, and the Demand Frequency field dictates the next time an order occurs.

For Network Optimization, the Series Offset Time 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 Series Offset Time 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.

Optimization currently only supports orders with one Occurrence.

Safety Stock Optimization Series Offset Time to perform Demand Analysis.

Occurrences

Technology: NO IO S

Table: SiteDemand

Internal Name: Occurrences

Type: Short Text (50)

Enter how many times this demand requirement will occur. A demand must occur at least once. When you enter a number greater than one, demand will occur multiple times.

For example:

Default: 1

Demand Frequency

Technology: NO S

Table: SiteDemand

Internal Name: Frequency

Type: Short Text (50)

For Simulation, the Demand Frequency field is used to specify the time between multiple orders. Enter how much time must pass between each recurring demand. Enter a value, the 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. For example, Demand Frequency can be 24 HR, meaning that orders recur every 24 hours for as many occurrences specified.

For optimization, the Demand Frequency is ignored if the demand doesn’t have Occurrences defined. If the Occurrences are greater than 1, You must enter data in this field. If you do not enter Demand Frequency and demand recurs, the software will assume that this demand happens once a day.

Demand Frequency examples are shown below:

Seasonality

Technology: NO IO S

Table: SiteDemand

Internal Name: SeasonalityName

Type: Short Text (100)

Select the Seasonality that applies to the demand. If a Seasonality is selected, the Factor associated with the Period as defined in the Demand Seasonality Factors is applied to the demand.

If both a Seasonality and Trend are assigned to the demand then:

Demand(n) = calculated Avg Quantity * Seasonality Factor(n) * (Trend)^(n-1)

Trend

Technology: NO IO S

Table: SiteDemand

Internal Name: Trend

Type: Number (Float)

In multi-period models, use the Trend to define a factor that is applied to the demand in a period over period method. For example:

Period 1 demand = calculated Average Quantity * Trend

Period 2 demand = calculated Average Quantity * Trend * Trend

... Period n demand = calculated Average Quantity * Trend^(n-1)

If both a Seasonality Name and Trend are assigned to the demand then:

Demand(n) = calculated Avg Quantity * Seasonality Factor(n) * (Trend)^(n-1)

Unit Price Override

Technology: NO IO S

Table: SiteDemand

Internal Name: UnitPrice

Type: Short Text (50)

You can define a site-specific price for each unit of the product being demanded. 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 Demand table, be aware of the following Optimization behavior:

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

Priority

Technology: NO IO S

Table: SiteDemand

Internal Name: Priority

Type: Short Text (50)

Enter a number indicating priority.

Simulation: This property is accessible when using scripting in simulation. Aside from use in simulation scripting, it does not have any direct functionality.

Tracking ID

Technology: S

Table: SiteDemand

Internal Name: TrackingID

Type: Short Text (50)

If a Tracking ID is populated, this ID will be 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.

Seed

Technology: S

Table: SiteDemand

Internal Name: Seed

Type: Number (Long Integer)

Use this field to control the ordering pattern used for demand. For example, if you have customers that should follow the same ordering pattern, you can populate the Seed value with the same value in the demand records for these customers. By default, this field is not populated and the seed value is determined based on the order in which the demand is processed. As a result, it is somewhat random in its results.

Status

Technology: NO IO S

Table: SiteDemand

Internal Name: Status

Type: Short Text (80)

One of Include, Exclude.

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

Default: Include

Notes

Technology: NO IO S

Table: SiteDemand

Internal Name: Notes

Type: Memo

Enter optional descriptive information about the demand.