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,
Post an idea
Upvote ideas that matter most to you
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.
Ability to add/remove rows in "Input Data" tables in Model Builder
Use case: I duplicate a scenario in the "Scenarios" panel. The scenario I'd like to test involves adding/removing one data point, e.g. adding a new machine in the predictive maintenance model or taking that machine out of service by removing it.
Pain points/problem: not possible to add / remove rows. We can only change values in existing tables
Current workaround: download .csv files used in the original scenario, copy, rename and modify them to add/remove row, upload the files as data assets for the project or directly in the data panel. At this point we also need to rename the data tables in "Input Data" for this new scenario. If .csv was renamed to machine2.csv, the table will be named machine2, and we'll have to change the name back to machine as this is what is expected by the optimization model. This in practice becomes messy due to multiple .csv files involved. And every time we duplicate a scenario, we have to create a new set of data files. Another workaround is to use a Python model to programmatically generate scenarios.
Proposed solution: add ability to add/remove rows in "Input Data" for a scenario.
Benefits/value: easier scenario manipulation directly in the Model Builder. Ability to create, solve, and compare scenarios directly in the Model Builder instead of programmatically.
# of users impacted: anyone who wants to compare scenarios directly in Model Builder without generating scenarios using Python code
Do not place IBM confidential, company confidential, or personal information into any field.