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.

Order Optimizer Dashboard additions for Stockout and Markdown avoidance

Add Inventory Model metrics to the Order Optimizer Dashboard.
Metrics should include but are not necessarily limited to those listed below.

Additional metrics in-time with current Shipping Model Dashboard (i.e. cumulative daily):
1. Current snapshot of stockouts projected to be avoided
2. Current snapshot of markdowns projected to be avoided
3. Current snapshot of ratio between incremental projected shipping & processing costs vs. projected stockout & markdown avoidance savings

Note: Current in-time metrics should be displayed at network level in the main screen as well as at node level if displayed in the pop-ups/map section

Added metrics trending over time (e.g. quarterly; likely a separate screen from the current Shipping Dashboard):
4. Projected stockout avoidance (total, avg per order, avg per day)
5. Projected markdown avoidance (total, avg per order, avg per day)
6. Predicted vs. actual stockout avoidance (percent)
7. Predicted vs. actual markdown avoidance (percent)
8. Average ratio between incremental shipping and processing costs vs. markdowns and stockouts avoided
9. % of orders sourced to optimal shipping cost node(s) -- i.e. projected shipping cost equal to an optimization done for shipping model at 100% and others at 0%
10. shipping cost (total, avg per order, avg per day)
11. processing labor cost (total, avg per order, avg per day)
12. orders (total, avg per day)
13. packages (total, avg per order, avg per day)
14. avg units per order
15. % of units sourced to DCs
16. % of units sourced to stores

Note: trends over time are assumed to be network level, but having capability to aggregate differently would be a nice to have
  • Guest
  • Jul 6 2018
  • Delivered
DeveloperWorks ID DW_ID114304
Link to original RFE
What is your industry? Retail

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.