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 Under review
Workspace Cloud Pak for Data
Components Watson Studio
Created by Guest
Created on Nov 2, 2021

Dynamic Number of Time Series Forecasted in Watson Studio SPSS Modeler Flow

There is need to be able to run a forecasting job even if the amount of timeseries changes (without going to the modeler to manually select a Type for each series). This can happen (but is not limited to) when using MDX to import data from IBM Planning Analytics.

Often there are hierarchical dimensions where one would like to forecast for all timeseries in a (sub)hierarchy. For example when forecasting monthly for all accounts in an account group.

There can be hundreds of timeseries and the number might change between runs. The change can be because a series added/deleted in the hierarchy or because the user wants to run a different subset of series (e.g. if erroneous values were detected in the historical data for those).

It is very time-consuming and frustrating to manually verify all target fields every time the script is run. Since this can be solved with a trivial for-loop in Python, Modeler Flow should also have some way to tackle this.

There seems to be two methods (at least) that would work:
1) Each column (excluding the time column) contains one timeseries to be used as Target.
2) Each column (excluding the time column and the value column) corresponds to one dimension. All unique combinations of dimension column values define one timeseries to be used as Target.

All of this can currently be done in Watson Studio if using Jupyter notebooks. However, they are more of an exploration tool and it doesn't look so great marketing-wise that a fancy tool like Watson Studio is just a place to put your open source scripts. Modeler Flow would be more sexy, easier to explain to end users, and more structured.

Needed By Yesterday (Let's go already!)