Advanced Supply chain Plan (ASCP) and Inventory Optimization (IO) Safety Stock Calculation Lead Time I have

a distributed Advanced Supply chain Plan (ASCP) and Inventory Optimization (IO) plus Demantra. Demantra is not the focus of this paper. For the test I have created a forecast with Weekly buckets on the Source, setup item, lead time, sourcing rules, assignment sets and all relevant setups in ASCP and IO modules. I plan to use IO for optimizing the inventory by managing safety stock (SS) with proper application of demand variability. Using item lead time and supplier lead time variability. Today I use static safety stock. Today all products in general are targeted as same service level of 95%. I plan to segregate products to different service levels from 95 to 90 %. I am in the testing stage and on my first system configuration I would like to understand the underlying logic as to how the system is recommending SS level under specific parameters. When I use the ASCP plan alone I can relate the demand to supply. When I feed a static safety stock I know the number I targeted. I tried using MyOracleSupport.com notes and the user guide to analyze the scenarios below but I am at a loss to explain some of the behavior. In the initial few scenarios I could relate to the formula described in available notes but for the rest of the scenarios I cannot. Do we have a way to evaluate data as suggested by the ASCP/IO plan? 1. In the SS calculation formula, when calculating the Lead time I find the system uses 7 days where as I use a calendar with 5 working days. Forecast is set at weekly buckets. So how does the 7 days calculation effect my output. What will happen if I have a monthly bucket forecast or say a day bucket? 2. For changes in fulfillment Lead-time, purchase lead-time variability, budget constraint and supply constraint scenarios, I Need to understand how the SS level is calculated. Answers are after the test case scenarios.

Scenario One

Scenario 2

Scenario Three

Scenario Four

Scenario Five

Scenario Six

Scenario Seven

Scenario Eight

Scenario Nine

Answer
1. The length of the weekly bucket is onsidered as 7 days and that goes to denominator as shown in the spreadsheet. The lead time of the 5 days is in the numerator: 2. The DFLT is just subtracted from the cumulative lead time. So the value of 5 they modeled will be subtracted from the lead time to arrive at a smaller safety stock. 3. The supplier variability safety stock is calculated separately and then pooled into the demand variability safety stock. Supplier variability safety stock = K * sigma_LT * mean demand for a buy item where: K = safety factor for the service level which is propagated down to the buy item sigma_LT = supplier variability % * transit lead time Overall safety stock = sqrt( supplier variability safety stock^2 + demand variability safety stock^2) 4. For the budget constraint plan, the allocation is based on solving a global linear program, so it is not an item-by-item allocation which can be easily explained looking only at an item by itself. But in general, the system compares the budget provided with the inventory value corresponding to the target service level. For this, one can run an enforce service level plan with the same settings. Then if the budget is deficit compared to the target inventory value, the system allocates safety stock among various items in order of margin and probability of corresponding demand. If the budget is surplus, the system ensures that at least the target safety stock is met for all items, and again, allocated based on margin and probability of the demand 5. For enforce capacity constraints mode, the method used is again a global linear program which considers all the capacity constraints defined in the system. The system ensures material and resource capacity defined are honored, and tries to meet target safety stocks. It is possible that the system may not be able to achieve target safety stocks or even satisfy the mean demand if the capacity is insufficient.