1. Support Technical Exchange Enhancements in Real Time Availability Monitor Sudhanshu Shekhar sshekhal@in.ibm.comsshekhal@in.ibm.comAugust 2016

2. Agenda 9.3 Enhancements Velocity Based RTAM Capacity Consideration in RTAM 9.4 Enhancements Ignore Capacity for RTAM 9.5 Enhancements Consider procurement availability below a desired threshold Consider open quantities Monitor multiple delivery methods Raise Event on all changes below a desired threshold References Q n A

3. RTAM (Real Time Availability Monitor) Time-triggered transaction, used to publish an item’s current availability information Three Modes Activity Based Mode (Monitor Option1) Quick Sync Mode (Monitor Option 2) Full Sync Mode (Monitor Option 3) Monitors availability across DG or individual Nodes Advantages Improved response time Quick publish of entire inventory picture

4. Activity RTAM Prior to 9.3, RTAM in activity mode would process activity records and raise events if available quantity has crossed defined threshold values Consider a scenario Low Threshold- 5 Medium Threshold- 10 High Threshold- 15 Current available quantity - 20 Order scheduled for 1 qty, record created in YFS_INVENTORY_ACTIVITY RTAM picks up the activity, processes the item but no event is raised as available quantity is 19, still below threshold Order is released, another activity record gets created. No event raised. Yet another order is scheduled and released, RTAM processes the item, but no event raised as availability is still 18, below threshold of 15. Drawbacks Unnecessary processing of items Memory and CPU overheads

5. Solution ?

6. Velocity RTAM Identifies item velocity : the rate at which item gets depleted at node Based on this velocity, RTAM predicts when to process the item How this velocity is calculated ? Every 5 minutes, each JVM dumps data into YFS_ITEM_NODE_VELOCITY_DUMP table with velocity information within that window Each day’s peak is stored in YFS_ITEM_NODE_VELOCITY A new agent CALCULATE_INVENTORY_VELOCITY processes the velocity dumps and identifies new peak velocity for the day Two modes 01 – calculates new peak item velocity 10 – processes suddenly hot items Based on calculated peak velocity, RTAM calculates the predictable time around which the next threshold would be reached, updates the NEXT_PROCESSING_TS field in YFS_INVENTORY_ACTIVITY table with this new time. No further processing until NEXT_PROCESSING_TS

7. Velocity RTAM - Example Low Threshold- 5 Medium Threshold- 10 High Threshold- 15 Calculated peak velocity- 1 qty an hour Current available quantity- 20 Order scheduled for 1 qty, record created in YFS_INVENTORY_ACTIVITY with NEXT_PROCESSING_TS as current_time + 5 hours. Calculation logic as below - Current available qty (20) – next threshold (15) / peak velocity (1) = 5 hours RTAM does not process this record until next 5 hours Order is released, no further activity record created. After 5 hours, RTAM processes the item, but no event raised as availability is still 19, below threshold of 15.

8. Velocity RTAM - Configuration Under GIV > Inventory Rules > Other Rules Under Process Modelling > General > Transactions

9. Velocity RTAM - Advantages No more unnecessary processing of items Improved response time. Reduced memory usage and CPU overhead

10. Capacity Consideration in RTAM RTAM considers capacity and publishes availability information as below – If capacity > 0, RTAM publishes onhand availability as current_date If capacity is 0, RTAM publishes onhand availability as next ship date as per node calendar, capacity and any other constraints. If capacity is 0, within monitoring window (lead time days), RTAM publishes availability as 0 RTAM does not trigger on capacity change alone Configure ON_STD_CAPACITY_FILLED event to create activity on capacity depletion.

11. Capacity Consideration by Activity RTAM - Example Onhand Qty-60 Low Threshold-15 Medium Threshold-35 High Threshold-55 Capacity configured at Node-10 units for 4 days – Total 40 units Lead days monitoring window-2 Assume RTAM has published onhand qty as 60, onhand available date as current date and alert level as 0. Create and schedule an order for 10 qty. Run activity RTAM. Alert raised with onhand qty as 50, onhand available date as current_date + 1, alert level as 1. Create and schedule another order for 10 qty. Run activity RTAM. Alert raised with onhand qty as 0, and alert level 3, as the entire capacity has been consumed within the monitoring window of 2 days.

12. Enhancement to Ignore Capacity for RTAM A new rule has been introduced under GIV > Inventory Rules > Other Rules to ‘Ignore Capacity for RTAM’ Available on 9.4-Foundation-Fix Pack 11 and above

13. Consider Procurement Availability below a desired Threshold Consider a scenario Store A has no inventory. It can procure certain quantities from nearby stores B and C within a lead time of 5 hours. Earlier, RTAM would not consider procurements, hence availability would be 0. With this enhancement, RTAM will consider the nodes based on the procurement sourcing rule and publish the availability information as per below sample xml –

14. Consider Procurement Availability below a desired Threshold - Configuration A new field CONSIDER_PROC_AT_LEVEL has been introduced in YFS_INVENTORY_MONITOR_RULES. manageInventoryMonitorRule API is used to specify ConsiderProcurementAtLevel attribute as per below sample xml –

15. Consider Open Quantities When an order comes, RTAM considers that order while publishing availability Earlier, it worked only when one DG was being monitored With 9.5, Multiple DGs can be monitored. Priority can be configured at DGs to consider open orders Prevents over-sell

16. Consider Open Quantities - Configuration manageCommonCode API can be used to set priorities for DGs against CodeType DIST_GRP_LVL_MONITOR as per below sample xmls – Example – DG_CENTRAL has 5 qty, DG_STORES has 10 qty. An order comes for 5 qty. RTAM publishes Availability for DG_CENTRAL- 0 Availability for DG_STORES- 10

17. Monitor Multiple Delivery Methods Allows publishing availability for multiple delivery methods. Stores and DCs maintain different safety factor for PICKUP and SHIPPING Published data is more detailed and accurate Allows Stores to Ship even if Pickup capacity for the day has been exhausted

18. Monitor Multiple Delivery Methods - Configuration A new DELIVERY_METHOD field in INV_MON_RULE_DEL_METHOD manageInventoryMonitorRule API can be used to add Delivery Methods to monitor as per below xml - Example –

19. Raise Event On All Changes below a desired Threshold RTAM currently raises events either on all changes (With RaiseEventOnAllAvailabilityChanges flag) or only on threshold changes. If configured to raise event on threshold changes, no further events raised until next threshold is reached. Consider a scenario Low Threshold- 5 Available qty - 4 RTAM raises event and publishes available qty of 4 An order for 1 qty is captured and scheduled. No event raised Yet another order for 1 qty scheduled. No event raised With this feature, RTAM will raise event each time there’s change in activity when quantity goes below a certain threshold.

20. Raise Event On All Changes below a desired Threshold – Configuration A new field ALWAYS_RAISE_BEYOND_LEVEL has been introduced in YFS_INVENTORY_MONITOR_RULES. manageInventoryMonitorRule API is used to specify AlwaysRaiseBeyondLevel attribute as per below sample xml -

21. Raise Event On All Changes below a desired Threshold – Benefits Allows websites to dynamically display “Only 3 Left in Stock !” as inventory adjustments occur Prevents over promising during order capture stage itself.

22. References https://www.ibm.com/support/knowledgecenter/en/SS6PEW_9.3.0/com.ibm.help.omnewfeatures.doc/c_nf_RTAM.html https://www.ibm.com/support/knowledgecenter/SS6PEW_9.4.0/com.ibm.help.om.foundation.fixpack.doc/OMSFixPackRelea seNotes_plugin-gentopic8.html#genTopProcId9https://www.ibm.com/support/knowledgecenter/SS6PEW_9.4.0/com.ibm.help.om.foundation.fixpack.doc/OMSFixPackRelea seNotes_plugin-gentopic8.html#genTopProcId9 https://www.ibm.com/support/knowledgecenter/en/SS6PEW_9.5.0/com.ibm.help.config.timetriggered.doc/configuration/r_RT AM_Cal_Inv_Velocity_Agent.htmlhttps://www.ibm.com/support/knowledgecenter/en/SS6PEW_9.5.0/com.ibm.help.config.timetriggered.doc/configuration/r_RT AM_Cal_Inv_Velocity_Agent.html https://www.ibm.com/support/knowledgecenter/en/SS6PEW_9.5.0/com.ibm.help.om.newfeatures.doc/newfeatures/Realtime _95.htmlhttps://www.ibm.com/support/knowledgecenter/en/SS6PEW_9.5.0/com.ibm.help.om.newfeatures.doc/newfeatures/Realtime _95.html https://www.ibm.com/support/knowledgecenter/en/SS6PEW_9.5.0/com.ibm.help.giv.concepts.doc/productconcepts/c_Invent oryAvailabilityMonitoring.htmlhttps://www.ibm.com/support/knowledgecenter/en/SS6PEW_9.5.0/com.ibm.help.giv.concepts.doc/productconcepts/c_Invent oryAvailabilityMonitoring.html

23. Questions

24. THANK YOU