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
Future supply/demand graph, should the supply be cumulative
In the item inventory details screen , the supply and demand graph shows the total supply and total demand per day. It wil be ideal to show the cumulative supply ( sum of all supplies upto that day / or availability graph )
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 rev...
The design of the Pick Declined metric in the BUC should be looking at line status = 1400 even when the line moves to the next status and 1400 is no longer active
Current design of BUC reporting Declined by Node metrics has gap that will under-report and under represent the declines/reject/short-picks by node. -Design as explained in Case #TS004179727 " Pick Decline is a status of BUC and we do not have a s...
Account for store time zone in RTAM node level availability calculation
RTAM would honor the property yfs.useNodeLocaleTimeForCapacityCheck, which is currently required in CoC implementations to have inventory APIs correctly calculate availability in the store's local time.
Sterling Business Center (SBC) UI option for node level onhand safety factor
Business wants to maintain node level onhand safety factory and currently SBC hasn't provided UI to enable support business with this requirement. We wanted to understand why this option is not provided on "Manage Node Information" screen by the p...
Alert search result screen needs to have additional data columns: Node and Order Date. BUC Module
The current search results list shows order No and alert type, which is insufficient for a user to narrow down which alert(s) to focus on. At the very least the Node/Store and Order Date will allow the user to group and prioritize review and actio...
Allow configuration of the filters in the Alert search result list to selected events of the order pipeline
The current filters are quite generic and limited, rendering them almost pointless. Each client will have specific meaningful steps/events within its order pipeline that will serve as much more relevant filters. The UI needs to allow configuration...
Do not place IBM confidential, company confidential, or personal information into any field.