4 About SRP and WRP Workbooks and Views

This chapter describes the standard workbooks, views, and associated measures that are used within SRP and WRP. Information for each measure is entered by the client based on the client's needs. This chapter also describes the differences between global domains and simple domains.

Global Domains

The SRP and WRP solution is always implemented on global domains. Global domains provide you with the ability to build, review, save, and commit workbooks in a master domain with data from multiple local domains.

Low Variability Measures

AIP employs the concept of low variability for several high-density measures. Low Variability measures are those which are time-phased by day and tend to change very little over time. Because there is little change, the same value is often repeated for several days. AIP takes advantage of this redundancy, by storing only changed values in low variability measures.

AIP also allows maintenance of replenishment parameters at various level of the product hierarchy to provide you with the capability of creating settings, using overrides only for exceptions.

You can maintain these parameters at three levels in the hierarchy:

• Global parameters are the highest default level used in determining the effective value of the measure. In other words, the parameter values at the global level are only used if no lower level (default or exception) parameters exist.

• Default Parameters are the second and middle default level used in determining the effective value of the measure. In other words, the parameter values at the default level are only used if no lower level (exception) parameters exist.

• Exception parameters are the next lowest level used in determining the effective value. Parameters values at the exception level will only be used if no lower level parameters exist.

• Event parameters are the lowest level defined. This level allows for normal day-to-day exception level usage while changing the value for an event. Event parameters will override all others

The default parameters allow you to enter parameters that affects many SKUs. Defaults can be used to set up basic replenishment parameters to meet the objectives of the business, with exceptions used for override values. Many of the exception level parameters are also time-phased by day or week, allowing you to change parameters prior to the actual date the change is effective.

At the exception level, when data is entered on a specific date, that date becomes an effective date for that measure. Once a value is entered on a date, the value remains in effect until the value is changed to another valid value, or a special value is entered. The special values are introduced for low variability measures to allow you to enter an exception value only on the date it becomes effective, remove the exception value to set the parameter back to the default value, and to indicate the parameter has no upper boundary.

Note: Only measures with the day dimension may be low variability

Table 4-1 describes the special values.

Table 4-1 Special Values for Low Variability Measures

Value	Description
-1 (Use Previous)	Indicates the measure uses the value from the previous day (that is, the value remains the same as the prior day).
-2 (Use Default)	Indicates the measure is set to its original default value from the global or default level.
-3 (Unbounded)	Indicates the measure is unbounded; it has no minimum or maximum limits.

Expanded Measures

Expanded measures show logical results of the multi-tiered defaults and low variability measures that are used in calculations.

The following example shows the results of a user entering data at the exception level.

Example: Max Time Supply Days has a global default value of 14 and no value at the default level.

Date	11/27	11/28	11/29	11/30	12/01	12/02
User Entered Value (exception level)		7			-2
Expanded Results	14	7	7	7	14	14

Low Variability Example

The example in Table 4-2 shows the expanded values of an unbounded measure (Warehouse Maximum Stock) with global, default and exception data. Note that this is a low variability measure at both exception level (SKU/Destination/Day) and the default level (scls/Destination/Day).

• Maximum Stock Global Default at dept level

• Maximum Stock Default at scls/Destination/Day

• Maximum Stock Exception at SKU/Destination/Day

Table 4-2 Example Results of an Unbounded Measure (Warehouse Maximum Stock)

Day		0	1	2	3	4	5	6	7
Global	800
Default		500	-1	-1	-1	-1	-3	-1	-2
Exception		200	-3	-1	-2	-1	-1	-1	-1
Expanded Results		200	�¥	�¥	500	500	�¥	�¥	800

Based on the example in Table 4-2,the following table describes the results.

Day	Entry	Result
Day 1	Enter -3 at the exception level, indicating that there is no upper limit (unbounded) for Maximum Stock. The expanded value is the unbounded value from the exception level. The default level is not queried. Nothing is entered at the default level. The value of -1 indicates that the previous default value of 500 will be used. The global level is not queried.	Maximum Stock is unbounded.
Day 2	Nothing is entered at the exception level. The default value of -1 indicates the previous value will be used.	Maximum Stock remains unbounded.
Day 3	Enter -2 at the exception level, setting the exception level to the NA value (-1), indicating the default value will be used	Maximum Stock is 500
Day 4	Nothing is entered at the exception level. Nothing is entered at the default level. The value of -1 indicates the previous default value of 500 will be used. The NA Value (-1) at the exception level indicates the default value will be used,	Maximum Stock is 500 (default level)
Day 5	Nothing is entered at the exception level. Enter -3 at the exception level, indicating that there is no upper limit for Maximum Stock. Thus the value of default level is infinity. The NA Value (-1) at the exception level indicates the default value will be used	Maximum Stock has no upper limit (unbounded)
Day 6	Nothing is entered at the exception level. Nothing is entered at the default level. The value of -1 indicates the previous unbounded value will be used. The NA Value (-1) at the exception level indicates the default value will be used	Maximum Stock remains unbounded.
Day 7	Nothing is entered at the exception level. Enter -2 at the default level, setting the default to the NA value (-1), indicating the global default value will be used	Maximum Stock is 800 (global default level)

About User Specified Allocations (USAs) for SRP

Note: For the USA workbooks, see Chapter 7, "Analyzing Activity."

The allocation of product to store locations is a critical component of the merchandising supply chain that affects customer service, inventory costs, sales and turn over goals, and profitability. SRP provides you with functionality to support User Specified Allocations (USAs).

USA Adjustments

User Specified Allocations allow users to make adjustments to inventory flow by:

• Reviewing and revising order quantities at an aggregate or individual location/SKU level

• Adding to or replacing store replenishment plans

• Using projected inventory to plan future allocations

• Using rule-based methods

• Triggering POs to be launched to suppliers by Warehouse Replenishment Planning or for Direct to Store when needed

USA Types

There are four types of User Specified Allocations:

• Replacement

• Additive

• Delivery window

• Allocation On Index (AOI), which is a rule-based allocation

USA Business Events

Planning and Allocation are not two independent processes in AIP. Store Planning incorporates the allocation process directly into the planning process by adding to or replacing the planned order that is generated with the User Specified Allocation. USAs give you the ability to review and revise the allocation prior to approving it. This functionality allows for revisions at an aggregate level or at an individual SKU/location level and review by chosen attributes prior to approval.

• USAs are typically used to manage the following types of business events:

• Clearances, which push stock from the warehouses to the stores

• Seasonal SKUs, which are affected by seasonal changes, such as weather-related product like ice scrapers and snow blowers

• Known limited supply (drip-feeding the stores with the product)

• New stores/reinvigorated stores

• Sampling

• Disaster management

• Forecasting is not possible or accurate

• Product launch, which refers to filling up stores with stock that is based on display needs

USA Business Process

The USA process is illustrated in Figure 4-1 and described in Table 4-3.

Figure 4-1 USA Business Process Flow

Table 4-3 USA Business Process Flow Description

Process Phase	Description
Create USA Workbook	Select the type of USA that you want to perform (Replacement, Top Up, Delivery Window, or AOI) and walk through a series of wizards that provide SRP with the additional data it needs in order to build the USA workbook.
Setup User-specified Allocation	Through the USA workbook, enter the quantity that you want to allocate (either by store or by source).
Commit Modified Allocations	Once the quantities have been entered and modified based on factors like pack-size or AOI, review the final store-level impact of the USA and commit the modified allocation.
Incorporate USAs into the Store Replenishment Plan	Once a USA is committed, its values become available to AIP to incorporate the USA into the store plan by modifying the replenishment boundaries so they account for the newly allocated quantities.