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.
converting Node reservation(node1) into Node Demand(node2)
For DFS(delivery from store) often times a reservation made aginst a store may have to be reassigned to a different store due to inventory reasons. The legacy OMS makes the determination to resource to the second node.
Note: For this implementatio...
Include Time Limit For Dirty Node
We would like to be able to add a time limit to a dirty node instead of waiting on incoming units. For example, if the node is marked as dirty, only leave it marked dirty for 24 hours.
Metrics in IV to understand the exposure rates
Ability to have insights into how much Inventory we are exposing for Demand and the reasons behind blocking by Dirty Node Vs Safety Stock vs Demand…etc., This information is critical for business and operations team. The below metrics are needed t...
Order Hub UI should be displaying all the product classes and corresponding inventory similar to Legacy Inventory Management UI
Please refer to the attached document.
Need milliseconds in Source timestamp in IV
Currently in IV we have field "sourceTs" :"2021-02-24T18:42:01Z" but it does not contain milliseconds in it.
API to GET all items having supplies for a node
IBM Inventory Visibility Service does not provide an API to GET all supplies available for a node. In our implementaion, there are hundreds of shipnodes. Also, many old items are discontinued often. If we want to do a comparison with IV for any ol...
IV Supply Sync Visibility
Need an acknowledgement process for Supply Sync in IV that will summarize saying they received “x” number of updates, processed “x” number, and the supply for “x” number of items did not change. IBM informed this requirement is on the product road...
Add Fields to Order Hub (reference, referenceType, lineReference, segment, segmentType)
We would like to have the option to view the following fields in Order Hub: reference, referenceType, lineReference, segment, segmentType.
GTIN based Inventory Availability and Scheduling in OMS CoC and Inventory Visibility
For our current client, inventory items are uniquely identified using UPCs(not to be confused with UPC in generic sense) and not SKUs, while the selling catalog identifies items using SKUs. These UPCs can change every year for the same item. For e...
Trigger SupplyChange Event based on change in timestamp in addition to quantity change
Currently, IV triggers supply change event for an item only when there is an update to supply bucket quantity. To make the event updates robust, we need capability to generate the events on the change of timestamps.
Do not place IBM confidential, company confidential, or personal information into any field.