Skip to main content

Simulation (SIM) Solver

Information on the Solver Settings when using the SIM engine

R
Written by Renee Thiesing
Updated over 4 months ago

The Simulation (SIM) solver is executed from within Architect when using a GAINS Simulation database. The simulation settings are populated from the table named SimOptions (dbo.SimOptions) upon an Excel import or can be populated and edited manually from within Architect.

The Settings can be viewed in Architect when Simulation is selected in the Solver dropdown list of the Output Scenario, as shown below.

The Start Date is the point in simulated time at which the model begins processing events.

The Stop Date is the point in simulated time at which the model will stop processing events.

The Warm Up Length is the amount of time at the beginning of the simulation that is not counted in the results, used to eliminate start-up bias and reflect normal operating conditions. Often referred to as the Warmup Period. NOTE: When using a warm-up period, the simulation solver will begin processing events at the Start Date (specified above) minus the Warmup Length.

The Warm Up Length UOM is the unit of measure used to define the Warm Up Length.

The Inventory Snapshot Interval is the time between when a snapshot of the current inventory position, of each SKUL, is reported out.

The Inventory Snapshot Interval UOM is the unit of measure used to define the Inventory Snapshot Interval.

The Days of Supply Measure can optionally be used in replenishment buying logic

The Default Weight UOM is the unit of measure that will be used in all of the weight output. Since the simulation input schema can support different UOM for each weight input across all of the tables, the user must specify which UOM should be used when the simulation solver generates output. This setting is also used by the solver if a weight UOM field is ever left NULL.

The Default Volume UOM is the unit of measure that will be used in all of the volume output. Since the simulation input schema can support different UOM for each volume input across all of the tables, the user must specify which UOM should be used when the simulation solver generates output. This setting is also used by the solver if a volume UOM field is ever left NULL.

The Default Distance UOM is the unit of measure that will be used in all of the distance output. Since the simulation input schema can support different UOM for each distance input across all of the tables, the user must specify which UOM should be used when the simulation solver generates output. This setting is also used by the solver if a distance UOM field is ever left NULL.

The Default Time UOM is the unit of measure that will be used in all of the time output. Since the simulation input schema can support different UOM for each time input across all of the tables, the user must specify which UOM should be used when the simulation solver generates output. This setting is also used by the solver if a time UOM field is ever left NULL.

Did this answer your question?