This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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?
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.