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.
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.
Multiple User Credentials
Our product team has grown exponentially; we now have around 9 teams with 2-4 developers in each team, and potentially all will have PROD access to IV at some point. Currently, we only have one generic user credentials to make changes in PROD. Thi...
Inventory segmentation support for sourcing using IBM IV services and OMS
Customer has DCs in US and EMEA while they maintain inventory within each DC with different buckets including bulk inventory and common ATP. Common ATP is shared with the wholesale orders. Sourcing requirement is to use the bulk inventory of a DC,...
Bulk Supply/Demand API
Ability to call multiple API's with single API similar to multiAPI in OMS product. This will enable the customers to call multiple API's like get supplies, get demands with in same response for an Item and parse the data accordingly. Requirement S...
Ability to disable item and node combination for specific DGs
We need an ability to disable item and node combination for some specific DGs in IV whereas for other
DGs this Item and Node Combination should be enabled. Currently IV does not seem to support this feature.
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
Ability to schedule on hand inventory publish for a set of DG’s or nodes
Currently, the IV events for inventory publish only include available units (supply - demands - safety stock). We have a need to schedule (intra day changes and nightly sync) the publish of ON HAND units for SKU/location level to certain external ...
Ability to schedule the publish of network level availability for a set of DG's
The trigger DgAvailabilityChange Event allow you to publish availability changes for all DG's within a tenant ID. This does not allow us to schedule the publish from within IV and also restrict the data publish to a subset of DG's. Within IV, we n...
Report inventory for multiple items in a table in BUC
We can currently search on multiple SKUs by separating the SKU with a comma. But the user still has to drill into each item separately once the search results come back. If the user has searched on a single node or singe DG, they should be able to...
BUC - make inventory reporting bundle aware
BUC inventory search should be able to take a SKU which is a bundle and return the inventory at the selected nodes, calculating the inventory of the bundle based on the inventory of the component SKUs.
Do not place IBM confidential, company confidential, or personal information into any field.