2 Pre-implementation Considerations

When preparing to implement the Advanced Inventory Planning solution, you must closely explore the retailer's infrastructure, hierarchy data, and other factors that can require customizing the AIP environment through the use of configuration files and settings, custom scripts, and the RPAS Configuration Tool. Prepare your environment and analyze your retail and data needs thoroughly before implementing AIP.

Considerations Prior to Implementation

Table 2-1 provides some of the considerations that the implementation team will need to address prior to implementation.

Table 2-1 Pre-implementation Considerations

Item	Issue	Description
1	Hierarchy Setup	Identify the attributes used by the Product, Location, and Time hierarchies, as well as their sources and update frequency. Define the dimensions within each of the Hierarchies and determine the default spreading settings. Define any Alternate Hierarchies and identify the relationship of the required Attributes that drive those Alternates. Define User Defined Hierarchies to be used by planners. The hierarchy setup mentioned above can vary, depending on the extent that the Configuration Tool will be used by the application.
2	Measure Settings	The following measure settings must be addressed during implementation and can vary depending on the extent that the Configuration Tool will be used by the application. Metric/Measure definitions, usage, interaction, and calculations Default Label to use when building measure labels Default Data Type Default not applicable Value Default Base Intersection Default Aggregation Method Default Spread Method Default Base State Read / Write Status at the base level Default Agg State Read / Write Status at aggregated levels
3	Setting Custom Wizards	Determine if any custom wizards are required that do not exist in the base application. The use or implementation of wizards can vary, depending on the extent that the Configuration Tool will be used by the application.
4	Workbook Templates, Worksheets, Tabs, Formats	Workbooks can be created or refreshed through batch processing. By doing the processing in batch at night, the end users are spared from the wait time associated with each action. The Batch Processing section should outline when each of these operations will take place. For these default auto workbook builds, the layout, formatting, hierarchies, wizard, tabs, and worksheets must be defined. The the timing of data loads, refreshes, and purges/deletions of workbooks must be set.
5	Daily and Weekly Batch Processing and Scheduling	Configure the system for the following defaults: Batch Processes Week-ending Processes Day-Ending Processes Data Updates Restructures - Adds, Renames, Deletes New Year Setup-- 53 weeks Data Aging/Purging Administrative Processes Backups
6	Sizing Estimates/Hardware Requirements	A sizing estimate spreadsheet and hardware requirements should be supplied to the client. These factors are dependent on the number of domains, intersection points, number of workbooks, purge and delete strategy, planning horizon, retention of data, and so forth.
7	Security Access and Viewing	User Setup/Security To define Workbook Template Security, the system administrator grants individual users or user groups access to specific workbook templates. Access to workbook templates provides users the ability to create, modify, save, and commit workbooks for the assigned workbook templates. Users will typically be assigned to groups based on their user application (or solution) role. Users in the same group can be given access to workbook templates that belong to that group alone. Users can be assigned to more than one group and granted workbook template access without belonging to the user group that typically uses a specific workbook template. Workbook access is either denied, read-only, or full access. Read-only access will allow a user to create a workbook for the template, but you will not be able to edit any values or commit the workbook. The read-only workbook can be refreshed. When users save a workbook, they assign one of three access permissions to the workbook: World - Allow any user to open and edit the workbook. Group - Allow only those users in their same group to open and edit the workbooks. User - Allow no other users to open and edit the workbook. Note: A user must have access to the workbook template in order to access the workbook, even if the workbook has world access rights. Workbook Limits Another aspect of workbook security is the ability to set limits for the number of workbooks that a user can save at any given time. Limits can be set at the following levels: User per template User Group per template Globally per template for all users The limits are evaluated in the above order, which means that a limit defined at user-template overrides any values defined at group-template or global-template levels. If the above limits are not defined, the default value is one billion. The limits are checked when a user begins the workbook build process. If the user's limit has been reached, an error message appears that informs the user that the workbook build process cannot be completed because the user has reached its limit. The message informs that the user has reached its limit. The wizard process then terminates.
8	Data Management Automation	Creation of certain logical constructs in Data Management can be set automatically, depending on the setting of certain parameters. Examine the system parameter configurations and determine which pieces of automation will be turned on. Map out each supplier's Ship-to value and each warehouse's Warehouse Type that will be needed to effectively automate the supply chain setup for those processes that are enabled. Note: Keep in mind that the Warehouse Type helps define Order Group destinations, and the default ordering pack size for a SKU into a store and warehouse.
9	Reconciliation	The reconciliation period is set to a day if the method is Reconciliation day-on-day and is set to a review period at source if the method is Reconciliation-over-time. Therefore, it has to be determined which reconciliation method will be selected at SKU level. You must set a flag to have a SKU reconciled in a constrained scenario.
10	Replenishment Methods	Define the replenishment methods to be used. Rule out replenishment methods that are not applicable.
11	Perishables functionality	Spoilage threshold is calculated using the Acceptable Loss parameter. Acceptable loss is a user-managed parameter in SRP, defined either at the class/store format level or the SKU/store/day level. Users have the ability to determine when to use expected spoilage through a Store use inventory aging flag. Constraints on the application of inventory aging are as follows: A global limit: in number of days, on or inside of which an item with product life can be considered in the expected spoilage calculation. An expected write-off's user-maintained measure. The first constraint is used as a high limit in number of days for a product life and is called Store Inventory Aging Limit. Product life as entered by a user does not have a limit. The effectiveness of product life needs to be controlled by a user. Therefore, a global limit respective to the product life is necessary and configurable. The second constraint refers to the fact that aging is a calculated number, not an actual number. You can have an actual number of spoilage that is to be used. A measure (expected write-offs) can be entered by you and if entered will override any spoilage calculation and be used as the amount to spoil on the given day. To summarize the user input for expected spoilage: The product life of the inventory at the point of receipt into the final selling destination. (SKU/Str/Day) The Store use inventory aging flag (SKU) The global limit for using inventory aging (Scalar) The expected write-offs (amount to spoil). (SKU/Str/Day)
12	Shelf capacity	If the Shelf Capacity flag is set to True, then shelf capacity will be considered when setting boundaries.
13	Substitution and value added functionality	The linked product flag is only used for user review purposes in AIP and indicates whether there is a value added/pre-priced commodity or banded item association with that particular SKU. If there is a value added/pre-priced association, the linked product flag is only True between the promotional start and end dates. This flag will be set within RMS. Also a Substitution Flag must be set at the SKU level within Data Management, which indicates that a SKU is substitutable across Demand Group.
14	User Specified Allocations	You must set the number of days of history required for using USA Indexed.
15	Alerts	Set the days that an alert will be run.
16	Store Reconciliation Matrix configuration	The number of store priorities is configurable; therefore, the Shortage and Stockless Surplus Priority Matrices can grow or shrink. However, no windows or workbooks are provided to view and maintain the configuration. The priority of each boundary, for each store priority, will depend on the number of store priorities defined. The order in which each boundary is met is configurable; however, no windows or workbooks are provided to view and maintain the configuration.
17	Network Throughput settings	The WRP Network Threshold Maintenance workbook is used to maintain network alert parameters. The WRP Network Threshold Maintenance workbook is available at the global and local domain levels. All measures should reflect the value in the domain during load and refresh times, and all editable measures should be committed to the domain unless otherwise stated.