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 Not under consideration
Workspace Spectrum Symphony
Components Version 7.1
Created by Guest
Created on Aug 22, 2018

User-based scheduling policy by SSM

Add a new scheduling policy to consider resources a user used and make it fair among users. We could call it user-based (fair share) scheduling policy.

For example, for N users that has active sessions, each user can only get 1/N of total allocated slots to that application. Furthermore, we can make different users have different "weight" instead of the simple/uniform 1/N share

I remember in Spectrum LSF, there's a fair-share policy which considers "user" as input. While we may not need as complex as the fair-share policy in LSF, it'd be great that Symphony also have similar policies.

  • Guest
    Nov 26, 2020

    .Tag Scheduling can be used to solve the case.

  • Guest
    Oct 31, 2018

    I realized there's a feature called tag scheduling, which actually does provide what needed here, so we can close this one