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.
Search by multiple order types simultaneously
Need an ability to search by multiple orders simultaneously. Currently its only allowed to search by a single order type ( Sales order or transfer order, etc )
Graph to display fulfillment plan for a particular order
being capable to see a graph related to fulfillment plan of a particular order: where/when each item is sourced, with TO and PO generated to transfer items between nodes, items merge visualized with dates at a particular node then at the end, del...
Want to drill down to order data (PO , MFG Order) from inventory screen
From the inventory screen , user should be able to see the orders( Purchase orders , sales orders ) that is causing the supply and demand. This is currently possible in Inventory console screens
An option to extract/export search results
For all search results available in OrderHub ( Orders, orderlines items, shipments, releases ) , an option to download in a csv form will be useful
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 )
In BUC Prepopulate the enterprise entry field when there is just the one value available
Selecting the enterprise over and over again seems like an irrelevent user task. Usually there is just one enterprise configured in the system. Even with multiple enterprises defined, perhaps one could be preselected as the default.It would be gr...
Add user, role management to the BUC tool for users who are administrators
Allow a BUC authorized user with admin privelages to manage OMS users directly in BUC. BUC users should be able to see users by enterprise, team, group or role. Actions allowed should be to delete a user, create a user, or update a user's info...
Provide capability for a BUC user to get from Node exception alert or a Node Details page to Node’s order list
OMNI Fulfillment managers oversee several hundred nodes and need the ability to see a Node's open order, or orders flagged as an exception, while reviewing the node's alerts or from the Node Detail page. Use Case. How to get from Node exception to...
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 calculationNode 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 sta...