Products
Internal Table Name: Products
Name
Technology: All
Table: Products
Internal Name: ProductName
Type: Short Text (100)
Enter a unique Name to represent product or a Stock Keeping Unit (SKU) number.
Unit Value
Technology: All
Table: Products
Internal Name: ProductCost
Type: Short Text (50)
Enter a monetary value for each unit. The Unit Value field is used to calculate the inventory investment and inventory holding costs. It is incorporated in the following formula:
Inv Holding Cost = Avg Inv * Product value * Inv Carrying Cost % * Length of Time in Inventory
In Network Optimization, the Product Value in the Inventory Policies table overrides the Unit Value in the Products table.
In Simulation, the Product Value in the Products table is always used. The Inv Carrying Cost % in the Inventory Policies is used if populated; otherwise, the Inv Carrying Cost % in Model Settings is used.
The Unit Value is reflected in the Total Inv Holding Cost in the Network Summary output table.
Unit Price
Technology: All
Table: Products
Internal Name: ProductPrice
Type: Short Text (50)
Enter the revenue generated from the sale of a single unit of this product. The product price is used to calculate revenue statistics.
Each time a customer order for this product is filled, it is registered as a sale. Revenue is determined by the number of units sold multiplied by the price of the product. If a Unit Price is specified on the Customer Demand or Site Demand tables, the Unit Price in the Products table is overridden. When no Unit Price is specified on the Customer Demand or Site Demand tables, the Unit Price field on the Product table is the default for revenue calculations.
Unit Weight
Technology: All
Table: Products
Internal Name: ProductWeight
Type: Short Text (50)
Enter the weight for a single unit of your product. Unit Weight is used to calculate truck fill levels and weight-based transportation costs. Enter a value, then 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.
Unit Volume
Technology: All
Table: Products
Internal Name: ProductCubic
Type: Short Text (50)
Enter the volume for each unit of product. Unit Volume is used to calculate truck fill levels and cubic-based transportation costs. It is also used to calculate site space utilization statistics. Enter a value, then select a volume unit of measure. If you do not select a unit of measure, the default Volume Unit Of Measure from Model Settings is used.
Type
Technology: IO S
Table: Products
Internal Name: ProductAllowableQuantities
Type: Short Text (50)
One of Discrete, Continuous
The type field enables you to define the allowable quantity values for this product. Many products must use specific quantity values. For example, if you are modeling a product such as "airplane", it would not make sense to have ½ of an airplane. The Type can be one of:
- Discrete – Use this value for products that are produced in integer quantities.
- Continuous – Use this value for products that can have fractional values, such as liquid chemicals.
Default: Discrete
Class
Technology: All
Table: Products
Internal Name: ProductClass
Type: Short Text (50)
Enumerated list
Select the shipping class. Only use this field if your shipping policy is Less Than Truckload (LTL). The National Motor Freight Classification Blue Book designates the shipping category classification numbers.
The shipping class determines shipping costs for any product shipped as LTL.
Default: 77.5.
Shelf Life
Technology: NO S
Table: Products
Internal Name: ShelfLife
Type: Number (Long Integer)
As a product moves through the supply chain, its relative age is tracked and compared to the Shelf Life.
Network Optimization: The Shelf Life field in the Products table determines the maximum number of periods in which a product is able to satisfy demand. A common use is to limit how early products can be pre-built. The value must be a non-negative integer. The Shelf Life is an index into the period in which the product will expire. For example, if your model uses monthly periods and the shelf life for a product is about 60 days (2 months), you define the Shelf Life as 2. A value of 1 indicates the product expires within the current period. A Shelf Life of 0 is considered invalid. If you use 0, the solver will consider no Shelf Life (similar to using null; that is, the product never expires). An error will be reported in the ErrorLog.txt file in this case.
Initial inventory is treated like it came into the system in the period before the model starts (that is, period 0). If the Shelf Life value in the Products table is set to 1, the initial inventory is already expired and never used. If the Shelf Life is set to 2, initial inventory can be used to fulfill demand in period 1, but not 2, 3, and so on.
Simulation: You can use the Shelf Life field in the Products table to determine the maximum number of days for which a product can satisfy demand. Once this limit is reached, the product expires. When the product expires, it is removed from available inventory and added to the cumulative scrap output. You can use this feature to model and track expiration dates, to determine how early products should be pre-built, and to track the life span of the product.
Enter the Shelf Life in the Products table as a number of days, using a non-negative integer value.
Initial inventory is treated as if it came into the system at the start of the model horizon; therefore, it is available to meet demand at the beginning of the model horizon.
Lead Time Cost/Day/Unit
Technology: NO
Table: Products
Internal Name: ProductLeadTimeCost
Type: Short Text (50)
Use this field to specify the cost of 1 day of lead time per unit of product. It is used in lead time optimization. This field accepts positive values.
Maximum Lead Time x Flow
Technology: NO
Table: Products
Internal Name: ProductMaxLeadTimeTimesFlow
Type: Short Text (50)
Use this field to specify the maximum limit of the flow times the lead time. It is used in lead time optimization.
Start Date
Technology: IO
Table: Products
Internal Name: StartDate
Type: Date/Time
Enter a start date for the product if you want Demand Analysis to consider product age. The Start Date applies only when using Demand Series as the propagation method.
If the Start/End Date is populated in Products, and the resulting product lifetime falls within the model horizon, the product lifetime is used as the period length when calculating Safety Stock Cost. If the product lifetime falls outside the horizon, the regular period length value is used.
Default: null
End Date
Technology: IO
Table: Products
Internal Name: EndDate
Type: Date/Time
Enter an end date for the product if you want Demand Analysis to consider product age. The End Date applies only when using Demand Series as the propagation method.
If the Start/End Date is populated in Products, and the resulting product lifetime falls within the model horizon, the product lifetime is used as the period length when calculating Safety Stock Cost. If the product lifetime falls outside the horizon, the regular period length value is used.
Default: null
Description
Technology: All
Table: Products
Internal Name: ProductDescription
Type: Short Text (255)
Use this field to provide an optional description of the product.
Temperature Class
Technology: All
Table: Products
Internal Name: TemperatureClass
Type: Short Text (100)
One of Standard, Refrigerated, Frozen, Heated
Defines the class of temperature control required for the product. Select one of:
-
Standard
-
Refrigerated
-
Frozen
-
Heated
You can use this column to filter your products.
Default: Standard
Hazardous Goods
Technology: All
Table: Products
Internal Name: HazardousGoods
Type: Bit
One of Yes, No, null
Use this column to indicate whether or not the product is considered a hazardous material.
You can use this column to filter your products.
Default: null (equates to No)
Maximum Risk
Technology: NO
Table: Products
Internal Name: MaximumRisk
Type: Double
The maximum risk score allowed for this product. The value of this field is used for formulating the maximum risk constraint on product level.
Status
Technology: All
Table: Products
Internal Name: ProductStatus
Type: Short Text (10)
One of Include, Exclude, Consider
The status field allows you to specify whether a product is included or excluded from a simulation or optimization.
If the field is left blank, the product is assumed to be included.
If the product status is set to "Exclude", none of the policies that use this product will be built, including inventory, sourcing, product-specific transportation policies, and processes.
Default: Include
Notes
Technology: All
Table: Products
Internal Name: ProductNotes
Type: Memo
Enter optional descriptive notes about the product.
Custom 1
Technology: NO IO S
Table: Products
Internal Name: Custom1
Type: Short Text (255)
Use this field for any additional custom information you want to records about the product.
Custom 2
Technology: NO IO S
Table: Products
Internal Name: Custom2
Type: Short Text (255)
Use this field for any additional custom information you want to records about the product.
Custom 3
Technology: NO IO S
Table: Products
Internal Name: Custom3
Type: Short Text (255)
Use this field for any additional custom information you want to records about the product.
Custom 4
Technology: NO IO S
Table: Products
Internal Name: Custom4
Type: Short Text (255)
Use this field for any additional custom information you want to records about the product.
Last modified: Wednesday May 15, 2024