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.

Node Fill Rate Metrics in the BUC module needs to consider Pick Declines in calculating rate, and should not ignore them

Per feedback regarding Fill Rate calculation

Node metrics not considering cancelled/rejected orders - Per the current product design, BUC was not considering cancelled/rejected orders while calculating the node metrics. Our engineering team is revisiting the design and I will keep you posted with the updates on this. Status - In Progress


1) Orders assigned to the store and rejected by the store (rejected, short-picked, etc) that result in cancellation must be part of the #‌ of records send to store.

2) Orders assigned to the store and rejected by the store (rejected, short-picked, etc) that result in cancellation must be included in the denominator when calculating Fill Rate

  • Guest
  • Oct 9 2020
  • Planned for future release
How will this idea be used?

Accurate number of orders/lines sent to the node.

Lines that are declined by the node still need to be accounted for. Calculating fill rate metrics isn't like baseball, when "walks" don't count against the batting average.

What is your industry? Retail
What is the idea priority? High
  • Attach files