Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 notification 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Created by Guest
Created on Nov 13, 2017

Create a rest endpoint to duplicate WKS custom model instance.

Currently, we are unable to scale to more than 20 threads when using a WKS custom model for entity and relation prediction with the NLU service. Our documents are very large and one document can take up to 5 minutes to process. If we have multiple users and multiple documents, we cannot process more than one document at a time, or if we do, we need to share the 20 threads among these documents. IBM employees told us that the only way we could scale is to manually deploy WKS models to new NLU instances when our usage increases. So we either have the choice to deploy WKS instances manually when our usage increases, or always have a high number of WKS instances deployed at all time and pay 800$*number of instances/month  (even when we don't need it). An easy solution would be for you to provide and endpoint to duplicate a custom model. Either from Watson Knowledge Studio directly, or from the NLU Service. That way, we can handle the scaling on our side, and we don't need to hire an employee whose amazing job would be to deploy custom models manually.