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 |
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 | Audit Trail |
Description | Determines the way the fractional new buy is reported on the Prioritized Buy List page. Valid entries are:
For example, consider a New Buy quantity of 10.35:
| ||||||||||||||||||
Default Value | -1 | ||||||||||||||||||
Usage | Prioritized Buy List page |
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 |
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. |
Description | Determines the number of months of demand transactions to consider. |
Default Value | 24 |
Usage | • Demand Streams • Scenarios |
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 |
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 |
Description | Demand records that are outside the range of mean + CUST_ORDER_SIZE_OUTLIER_STD * Standard Deviation are considered outliers.
| ||
Default Value | 3.0 | ||
Usage | • Demand Streams • Scenarios |
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.
• 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 |
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 |
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 |
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 |
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:
| ||||||
Default Value | = | ||||||
Usage | SKU Summary page |
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. |
Description | This determines how the Customer Order Size is calculated. Values are:
| ||||||||
Default Value | CUSTOMER | ||||||||
Usage | System wide to determine the Customer Order Size Average and Customer Order Standard Deviation |
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 |
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 |
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 |
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 |
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 |
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), and scenarios can have a State of Promoted to Production
• 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. |
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. |
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.
| ||
Default Value | false | ||
Usage | System wide. |
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 |
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. |
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. |
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 |
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 |
Description | This global setting controls the default level that is displayed when a new SKU Override is entered on the Create/Edit SKU Override dialog box. The value of this global setting can be any Override Type. |
Default Value | ROP |
Usage |
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 |
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 |
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 |