IBM Sterling Ideas
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Enhancement request to support safety stock solution at the following levels,
Date range support - Ability to configure safety stock based on applicate date range. This allows the users to configure these ahead of time and does not rely on just in time system updates for safety stock to take effect.
Channel specific safety stock - Currently, we have support for safety stock by delivery method , but this cannot be varied by the selling channel (web Vs retail). Need the ability to set high thresholds for web pickups than for pickup orders placed form instore (retail SOP calls for store associates to call the pickup store to confirm inventory availability).
Node Type - We have different retail store types (outlet Vs full priced stores) and need the ability to setup different thresholds based on node type. (Node type, Node type - merchandising hierarchy (Dept/Class/Subclass/Style level) , Node type - SKU combination).
Node Level - safety stock at node level that applies to location unless one is define for the SKU/Location level. Tis is to protect for the scenarios where specific stores that have a higher in store traffic and need to protect more units using safety stock.
Merchandising hierarchy level - Define thresholds at merchandizing hierarchy level (Dept/class/subclass/style level). Either at the level or intersection of merchandizing level and node type/node combination.
Supply type - configure different safety stock thresholds based on supply type. higher for in transit inv Vs on hand. Even within future supplies, the safety stock can be different for PO and PO ASN supply as ASN is much more firm in terms of qty that is shipped.
|What is your industry?||Retail|
How will this idea be used?
This enhancement will allow us to retire the existing custom safety stock solution (implemented on our existing OMS platform) and allow us to configure appropriate thresholds in the IV solution to protect against oversells.
Do not place IBM confidential, company confidential, or personal information into any field.