Global Settings — Inventory Optimization
A method of applying a configuration parameter at the system level. Global settings can be used to do the following:
• Enable or disable features
• Define limits and boundaries to sets of data
• Control parameters used during processing
These are a few of the more common global settings that apply to the Inventory Optimization module. Contact your Technical Support representative for assistance configuring global settings in your installation of Servigistics.
ALLOW_NEGATIVE_SAFETY_STOCK
Description
Enables the calculated safety stock value to go below -1.
◦ When set to false the safety stock is floored at -1
◦ When set to true the safety stock is calculated by subtracting the rounded value of the pipeline forecast from the ROP
Default Value
false
Usage
AUDIT_TRAIL_KEEP_DAYS
Description
This is the number of days to keep audit records in the IPCS_AUDIT_TRAIL and IPCS_AUDIT_TRAIL_DETAILS tables.
Audit Trail records that are older than the value set by the AUDIT_TRAIL_KEEP_DAYS global setting are deleted when the Gateway Clean-up AutoPilot process is run.
Default Value
90
Usage
BUY_LIST_ROUNDING_RULE
Description
Determines the way the fractional new buy is reported on the Prioritized Buy List page. Valid entries are:
Value | Result |
|---|---|
-1 | New Buy quantities are not rounded. |
Fractional numbers between 0 and 1 | New Buy quantities are rounded. Calculated as Truncate (new buy qty + (1 - <global setting value>)) |
For example, consider a New Buy quantity of 10.35:
Global Setting Value | New Buy Result |
|---|---|
-1 | 10.35 |
.0001 | 11 |
.35 | 11 |
.5 | 10 |
1 | 10 |
Default Value
-1
Usage
Prioritized Buy List page
CARBON_MEASURE_TYPE
Description
Defines the measure label that is displayed for Sustainability headings.
For example: Sustainability (<gs value>)
◦ Where CARBON_MEASURE_TYPE = kg of CO2e
◦ Displayed as Sustainability (kg of CO2e)
Default Value
kg of CO2e
Usage
For use with Sustainability.
◦ Create/Edit window on the Inventory Optimization Planning Parameters page
◦ Carbon Footprint container on the Scenario Budget Summary page
◦ Carbon Footprint container on the Part Budget Summary page
◦ Carbon Footprint container on the Service Group Budget Summary page
CARBON_TAX_RATE
Description
Defines the Carbon Tax Rate to be applied when the Location or Region does not have a Carbon Tax Rate defined.
Default Value
0
Usage
For use with Sustainability.
CUST_ORDER_SIZE_DMD_HIST_HORIZON
Description
Determines the number of months of demand transactions to consider.
Default Value
24
Usage
◦ Demand Streams
◦ Scenarios
CUST_ORDER_SIZE_MIN_DMD_RECS
Description
Determines the minimum number of demand records required to calculate a Customer Order Size > 1 or a Customer Order Size Standard Deviation > 0.
The Customer Order Size and Customer Order Size Standard Deviation are calculated after outliers are considered.
If the number of transactions is less than the value of this global setting, then:
◦ Customer Order Size is set to 1.
◦ Customer Order Size Standard Deviation is set to 0.
Default Value
5
Usage
◦ Demand Streams
◦ Scenarios
CUST_ORDER_SIZE_OUTLIER_HANDLING
Description
Indicates how to handle an outlier
◦ When set to REMOVE, the outlier record is removed.
◦ When set to REPLACE, the outlier is replaced with Mean – STD or Mean + STD
Default Value
REMOVE
Usage
◦ Demand Streams
◦ Scenarios
CUST_ORDER_SIZE_OUTLIER_STD
Description
Demand records that are outside the range of mean + CUST_ORDER_SIZE_OUTLIER_STD * Standard Deviation are considered outliers.
 | A value of -1 indicates that there is no outlier detection consideration. |
Default Value
3.0
Usage
◦ Demand Streams
◦ Scenarios
CUST_ORDER_SIZE_VARIABILITY_CAP
Description
Limits the potential increase of Customer Order Size. The value entered is a multiple of the configured application expression of variability as identified by the SL_VARIABILITY_TYPE global setting.
| | Valid values are whole numbers >= 0 A value of -1 indicates that there is no cap. |
◦ When SL_VARIABILITY_TYPE is COV then CUST_ORDER_SIZE_VARIABILITY_CAP is interpreted as a maximum coefficient of variation:
▪ Customer Order Size Standard Deviation / Customer Order Size
▪ A value of 3 limits the Customer Order Size Standard Deviation to Customer Order Size * 3
◦ SL_VARIABILITY_TYPE is VMR then CUST_ORDER_SIZE_VARIABILITY_CAP is interpreted as a maximum variance to mean ratio:
▪ Customer Order Size Standard Deviation^2 / Customer Order Size
▪ A value of 3 limits the Customer Order Size Standard Deviation to Square Root (Customer Order Size * 3)
Default Value
-1
Usage
◦ Demand Streams
◦ Scenarios
DEALER_APP_RESTRICTIONS
Description
Determines if users with a Role Name of Dealer have restricted access to the following:
◦ The Minimum and Maximum field entries are not visible when creating or modifying a SKU Override on all pages where SKU Overrides can be managed.
◦ The Pre-Optimization fields on the Create/Edit SKU Override page are not available.
◦ Filters created on the Configurable Filters page cannot be shared. A user will only have access to modify and use filters that they have saved.
When set to true, the access rights are restricted. When set to false, the access rights are not restricted.
Default Value
false
Usage
ENABLE_FORECAST_APPROVAL
Description
Determines the type of scenarios listed in the Forecast Type dropdown on the Create/Edit Scenario window.
When set to true, these forecast types are available:
◦ Production
◦ Recommended
◦ Causal Forecast Scenario
◦ SIOP Forecast Scenario
When set to false, these forecast types are available:
◦ Production
◦ Causal Forecast Scenario
◦ SIOP Forecast Scenario
Default Value
false
Usage
ENABLE_LOCATION_HIERARCHY
Description
Enables or disables the use of location hierarchies.
◦ When set to true, location hierarchies can be defined and used.
◦ When set to false, the location hierarchies feature is not available.
Default Value
false
Usage
ENABLE_NRTS
Description
This determines if the Not Repairable This Station functionality is enabled
◦ When set to true, the Not Repairable This Station is enabled and the Return Wash Rate and NFF Rate are used by the calculation for consumable parts
◦ When set to false, the Not Repairable This Station is not enabled
Default Value
true
Usage
EXCEL_EXPORT_ESCAPE_CHARACTER
Description
This determines the escape character used for export files when they are opened in Microsoft Excel. This escape character only applies to fields that start with a zero (0). Values are:
Setting | Definition |
|---|---|
= | When a field starts with a zero (0), then the value is output with an equals symbol and then quotations around the value. For example, 097520R is output as =”097520R”. |
t | When a field starts with a zero (0), then the value is output with a tab and then the value. For example, 097520R is output as 097520R |
Default Value
=
Usage
SKU Summary page
INVENTORY_OPTIMIZATION_MULTI_PERIOD_APPROVE
Description
This determines if the Multi-Period Approval option is selected by default on the Scenarios page when a new scenario is created.
◦ When set to true, the Multi-Period Approval option on the Scenarios page is selected by default.
◦ When set to false, the Multi-Period Approval option on the Scenarios page is not selected by default.
Default Value
false
Usage
INVENTORY_OPTIMIZATION_MODE
Description
This determines the method of Inventory Optimization that is used. Values are:
◦ Single Item Optimization (SIO)
◦ Multi-Item Optimization (MIO)
◦ Multi-Echelon Optimization (MEO)
◦ Multi-Indenture Multi-Echelon Optimization (MIME)
Default Value
MEO
Usage
◦ System wide to determine Inventory Optimization method
◦ Service Group Results page
▪ The Contract option is enabled on the Display button when the INVENTORY_OPTIMIZATION_MODE global setting is set to MIME.
IO_ANCESTOR_STABILITY_METRIC
Description
This determines the how the current Scenario results influence the recalculated stock levels for non-requested resupply hierarchy ancestors of the requested SKU. Values are:
◦ FIXED_WAIT_TIME
◦ FIXED_ROP
◦ FIXED_FILL_RATE
◦ MAX_WAIT_TIME
◦ MIN_ROP
◦ MIN_FILL_RATE
Default Value
FIXED_WAIT_TIME
Usage
IO_CALC_RESUPPLY_CUST_ORDER_SIZE
Description
This determines how the Customer Order Size is calculated. Values are:
Setting | Definition |
|---|---|
CUSTOMER | The calculation of the Customer Order Size at a resupply location considers the customer order sizes of the children. |
EFFOQ | The calculation of the Customer Order Size at a resupply location considers the Effective Order Quantity of the children. |
NONE | The calculation of the Customer Order Size does not include the Customer Order Size of the children. |
Default Value
CUSTOMER
Usage
System wide to determine the Customer Order Size Average and Customer Order Standard Deviation
IO_ENFORCE_ROTABLE_POOL_BEFORE_BUDGET
Description
This determines the order that constraints are applied during Rotable Pooling calculations. Values are:
◦ When set to true, enforces rotable pool maximum constraints first and then applies capacity and budget constraints.
◦ When set to false, enforces capacity and budget constraints first and then applies rotable pool maximum constraints.
Default Value
false
Usage
Used with Rotable Pooling
IO_EVALUATE_EMERGENCY_BACKUP_VALUES
Description
This controls when the Emergency Order values are populated for both Production and calculated Scenarios on the Scenario Summary, Location Summary, Part Summary, and Segment Summary pages:
◦ When set to true, the Emergency Order values are populated on the summary records.
◦ When set to false, the Emergency Order values are not populated on the summary records.
The fields that are affected by this global setting are:
◦ Emergency Period Forecast (Optimized)
◦ Primary Emergency Fill Rate
◦ Primary Emergency Fill Rate (Optimized)
◦ Secondary Emergency Fill Rate
◦ Secondary Emergency Fill Rate (Optimized)
Default Value
false
Usage
IO_EMERGENCY_NETWORK_SOLVES_COMMON_GROUPS
Description
Determines if service groups with service metrics other than Fill Rate with Emergency Backup are loaded into the emergency backup location algorithm when they have SKU in common with service groups with a service metric of Fill Rate with Emergency Backup.
◦ When true, groups of common SKU are loaded.
◦ When false, only Fill Rate with Emergency Backup service groups are loaded
Default Value
true
Usage
IO_FULL_COMPARE_MODE
Description
This controls what records are displayed when comparing two scenarios on the SKU Summary page.
Only records that are in the first scenario are displayed. To enable a full comparison, the IO_FULL_COMPARE_MODE global setting must be set to true.
◦ When true, the two scenarios selected are fully compared.
▪ Records that are in both scenarios are displayed
▪ Records that are in the first scenario but not in the second scenario are displayed
▪ Records that are in the second scenario but not in the first scenario are displayed
◦ When set to false, the two scenarios selected are only evaluated and displayed for records that are in the first scenario.
▪ Records that are in both scenarios are displayed
▪ Records that are in the first scenario but not in the second scenario are displayed
▪ Records that are in the second scenario but not in the first scenario are not displayed
Default Value
false
Usage
IO_MAX_AUTO_DETECT_LTB_SUPPORT_DAYS
Description
This setting determines whether the scenario horizon is adjusted for Inventory Optimization scenarios designated as either Planning or Monitoring for Last Time Buy SKUs.
◦ If the Calculated Duration < IO_MAX_AUTO_DETECT_LTB_SUPPORT_DAYS then the scenario horizon is updated to align with the Support To Date
◦ If the Calculated Duration >= IO_MAX_AUTO_DETECT_LTB_SUPPORT_DAYS then the scenario horizon is not updated
Where:
Calculated Duration = The number of days between the Scenario Start Date and the maximum Support To Date
| | For a maximum auto-detection horizon of 10 years, set this global setting to 3650 To disable this functionality, set the global setting to -1 |
Default Value
-1
Usage
IO_MAX_YEARS_BETWEEN_DEMANDS_TO_HONOR_MINS
Description
This global setting controls if the following constraints and overrides are ignored:
◦ Minimum and Fixed Fill Rate
◦ Minimum and Fixed Safety Stock
◦ Minimum and Fixed Safety Stock Days
◦ Minimum and Fixed ROP Days
◦ Minimum and Fixed Stock Maximum Days
◦ Maximum and Fixed Wait Time Days
The value of the global setting is used in this equation: SKU Daily Demand Rate < [1/(365 * IO_MAX_YEARS_BETWEEN_DEMANDS_TO_HONOR_MINS)]
◦ When the global setting is set to zero (0) or any negative number, all constraints and overrides listed are ignored.
◦ When the global setting is set to any number greater than zero (0), the equation is evaluated. If the SKU Daily Demand Rate is less than the result, all constraints and overrides are respected.
Default Value
-1
Usage
IO_NEW_BUY_PROC_EFFOQ_THRESHOLD
Description
This controls when a purchase order is triggered.
◦ When set to true the New Buy Need (Procurement) value is compared to the Effective Order Quantity to trigger the creation of a purchase order.
◦ When set to false the purchase order is always triggered when there is a new buy need.
Default Value
false
Usage
IO_OVERRIDE_CLEANUP_EXPIRED_RECORDS_DAYS
Description
This specifies the number of days after a SKU Override has expired before it is purged from the system. SKU Overrides with an End Date older than today minus the number of days specified by IO_OVERRIDE_CLEANUP_EXPIRED_RECORDS_DAYS are purged when the Synchronize Database AutoPilot process is run.
For example, when IO_OVERRIDE_CLEANUP_EXPIRED_RECORDS_DAYS is set to the default value of 180 days, and today is February 11, 2022, any SKU Override with an End Date that is prior to August 15, 2021 are purged when the Synchronize Database AutoPilot process is run.
◦ When this value is greater than 0, the SKU Overrides are evaluated and purged when the Synchronize Database AutoPilot process runs
◦ When this value is 0 or -1. SKU Overrides are never purged.
Default Value
180
Usage
IO_PEER_STABILITY_METRIC
Description
This determines the how the current Scenario results influence the recalculated stock levels for non-requested SKU that are not resupply hierarchy ancestors of the requested SKU. Values are:
◦ FIXED_WAIT_TIME
◦ FIXED_ROP
◦ FIXED_FILL_RATE
◦ MAX_WAIT_TIME
◦ MIN_ROP
◦ MIN_FILL_RATE
Default Value
FIXED_ROP
Usage
IO_PROD_SKU_TRACKING
Description
This controls the tracking of the Inventory Optimization scenarios that served Stock Levels to Production. Valid settings are:
◦ Global Setting = 0
No records are inserted to the IPCS_MEO_PROD_SKU table. Therefore, no production SKU counts are greater than zero (0), and there are no scenarios that will have a State of Promoted to Production
◦ Global Setting = 1
Records for the current period are inserted to the IPCS_MEO_PROD_SKU table. Therefore, the production SKU counts in subsequent periods are zero (0)
 | This is the recommended setting for large configurations to provide the best performance without sacrificing the scenario status. |
◦ Global Setting = 2
Records for all periods are inserted to the IPCS_MEO_PROD_SKU table. Therefore, the production SKU counts and the production SKU counts in subsequent periods are greater than zero (0), and scenarios can have a State of Promoted to Production
Default Value
2
Usage
Controls what is displayed in the Production SKUs field.
IO_PRODUCTION_SCENARIO_SKU_SQL_METHOD
Description
This determines the method used to build the production scenario SKU table (PM+ScenarioID) during the Make Production process and improves performance. Valid settings are:
◦ A value of 1, uses a create table query based on the approved promoted scenario SKU, followed by an append query for any other SKU already in production.
◦ A value of 2 uses a create table query based on the union of approved promoted scenario SKU and any other SKU already in production.
Default Value
1
Usage
Improves the performance of the Make Production process.
IO_TPROP_ROUND_SS
Description
This determines if Safety Stock will be rounded when the Time-Phased ROP Order Policy is enabled.
◦ When set to true the Safety Stock is rounded using the safety stock rounding rule. This setting generates results that are similar between Time-Phased ROP and Time-Phased Safety Stock planning, especially when there are overrides or constraints.
◦ When set to false the Safety Stock is not rounded. This setting generates results that are consistent with Inventory Optimization, and is the recommended setting when using Time-Phased ROP.
| | This global setting is evaluated only when the Time-Phased ROP Order Policy is enabled. |
Default Value
false
Usage
System wide.
LEVELS_DAYS_CONSTANT
Description
This determines how many days are included in an interval for converting EOQ (slices) to quantity.
◦ When set to true then 30 for monthly or 7 for weekly is used as the number of days in the interval to convert EOQ (slices) to a quantity.
◦ When set to false the actual number of days in the interval is used to convert EOQ (slices) to a quantity.
Default Value
false
Usage
MAXIMUM_ADDITIONAL_SCENARIOS_DISPLAY_COUNT
Description
A numeric value between 0 and 12 that determines the number of additional scenarios that can be displayed on the Scenario Budget Summary page.
Default Value
5
Users can override this value on the Set Additional Scenarios Selection Size page.
Usage
Scenario Budget Summary page.
MEO_OVERRIDE_CODE_REQUIRED
Description
This determines if the Reason (general) must be populated to create a SKU Override.
◦ When set to true, the Reason (general) field on the SKU Override is a required entry in order to save the SKU Override.
◦ When set to false, the Reason (general) field on the SKU Override is optional.
Default Value
false
Usage
SKU Overrides page
A default setting can be defined on the Override Reasons page.
MEO_OVERRIDE_DEFAULT_PERIODS_TO_EXPIRE
Description
This is used to calculate the default setting of the End Date when a SKU override is created.
◦ When this global setting is set to 0, the End Date is not populated
◦ When this global setting is > 0, the value is added to the Begin Date and the End Date is populated with the last date of that period
Examples for monthly processing:
◦ Global setting = 1
Begin Date = Jan 15
End Date = Jan 31
◦ Global setting = 2
Begin Date = Feb 15
End Date = Mar 31
◦ Global setting = 3
Begin Date = Apr 15
End Date = Jun 30
Default Value
0
Usage
MEO_REPAIR_TYPE
Description
This is used to determine the composite lead time mean and variance method. Valid entries are:
Value | Methodology | Description | ||
|---|---|---|---|---|
1 | Serial Mode | The repair and new buy process is done sequentially assuming the repair pipeline quantity is the smallest.
| ||
2 | Aggregate Mode | The calculation of pipeline quantity is the combination of repair/return and procurement/replenishment lead time, weighted by their proportion of use. This method considers wash rate, but does not consider demand.
| ||
3 | Demand Weighted Mode | The calculation weights the Composite Lead Time by the demand conditions as defined by the Return Wash Rate, Repair Wash Rate, NRTS, NFF and supply chain hierarchy.
|
Default Value
3
Usage
MEO_OVERRIDE_MAX_QTY
Description
This is the value that triggers a notification that the maximum suggested override limit was exceeded. An override above this amount requires a confirmation from the user before the override can be saved.
◦ When this global setting is set to 0, there is no maximum limit in place and the override is automatically accepted
◦ When this global setting is > 0 and the override entered is greater than the value, the user must confirm the override before it can be saved
Default Value
0
Usage
MEO_SKU_OVERRIDE_TYPE
Description
This global setting controls the default level that is displayed when a new SKU Override is entered on the Create/Edit SKU Override window. The value of this global setting can be any Override Type.
Default Value
ROP
Usage
NOPT_CROSS_BORDERS
Description
This global setting controls the Network Optimization calculation of response time from a service location to an install site.
Default Value
true
◦ When this global setting is set to true, the response time from a service location to an install site is calculated as the driving time from the location to the site plus the Hours to Cross time.
When this global setting is set to false, no border crossings are allowed and locations can only service install sites in their own country.
Usage
SL_VARIABILITY_TYPE
Description
Determines how the variability is capped.
◦ When this global setting is set to COV, then the variability is capped using Coefficient of Variance and the Coefficient of Variance Cap Parameters page is enabled. You can set COV cap parameter values for high and low volume SKUs and assign them to a segment. The COV cap applies to all SKUs in the segment.
◦ When this global setting is set to VMR then the variability is capped using Variance to Mean Ratio and the Variance to Mean Ratio Cap Parameters page is enabled. You can set VMR cap parameter values for high and low volume SKUs and assign them to a segment. The VMR cap applies to all SKUs in the segment.
Default Value
COV
Usage
SPACE_CONSTRAINT_TYPE
Description
Defines the label of the Space Constraints tab on the Create/Edit Service Group Parameter page.
The value of this global setting will be displayed in columns and fields as follows:
◦ Service Group Parameters Add/Edit tab — “<gs value> Constraint”
◦ Parts and SKU pages — “<gs value> per Unit”
◦ Scenario Summary, Location Summary, Part Summary, SKU Summary and Service Group Results — <gs value> Required
Default Value
Cubic Meter
Usage