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.
IV Node availability call to accomodate custom supply and demand types when integrated with OMS
Most of the OMS implementation would have custom supply and/or demand types part of their business. Currently, the IV node availability call considers only OOB supply and demand types when integrated with OMS, which gives an incorrect inventory pi...
Publish SKU attributes as part of IV API's including ATP lookup and ATP publish events
In our ecosystem, we have systems that use alternate SKU identifiers (ex- UPCCode instead of SKU Id). Without the support for cross referencing SKU's between the various item aliases, additional lookup calls will be needed to get the Item id neede...
Get Availability by tag (inventory identifier)
IV does not currently provide availability by tag. It does support taking supplies/demands by tag. OMoC will generate the TagNumber and pass it to IV for supply/demand updates. IV will store them as OMoC had provided. However, you will not be able...
Ability for a child item (keyboard) to belong to multiple parent items (Intel PC as well as AMD PC) at the same time
Ability for a child item (keyboard) to belong to multiple parent items (Inter PC as well as AMD PC) at the same time. It is common in the retail world that a product is bundled as combos in multiple permutation and combinations. It means allowing ...
Inventory Visibility Service | Event Publish | Reservation Event
We would need to use the node level reservation event message to create activity for RTAM to consider this reservation for publishing to all consumers of the inventory.
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...
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.
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...
Do not place IBM confidential, company confidential, or personal information into any field.