Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Created by Guest
Created on Apr 27, 2026

Performance Issue in Maximo Graphical Assignment – Schedule Refresh

After migrating from MAS 8 to MAS 9, we observed a significant performance degradation in Maximo Graphical Assignment when users click Refresh Schedule.

The refresh usually takes around 1 to 2 minutes, but in some cases the latency increases to approximately 3 to 4 minutes.

The refresh action now takes several minutes, especially when multiple schedulers use different graphical views at the same time. During concurrent refresh operations, CPU usage can reach 100%, and both refresh and save actions become very slow.

This behavior was not observed in MAS 8 under similar usage conditions.

Idea priority Urgent
  • ADMIN RESPONSE
    May 21, 2026

    Hi,

    Thank you for taking the time to provide your ideas to IBM. Your request is now a candidate for a future product release. Our aim is to deliver within the next 12-18 months. Thank you again for your feedback.

    Please note: IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality.

  • Guest
    Apr 28, 2026

    Additional information regarding the performance bottleneck:

    As part of our analysis of the “Refresh Schedule” action in Maximo Graphical Assignment, we captured the backend SQL queries executed during the refresh process.

    The analysis shows that the longest-running query is a COUNT query on the WORKORDER table:

    select count(*) from workorder ...

    This query took approximately 48 seconds in our test case and appears to be one of the main contributors to the overall refresh delay.

    The performance impact becomes more significant when multiple schedulers refresh different graphical views at the same time. In these situations, CPU usage may reach 100%, and both refresh and save actions become very slow.

    We understand from IBM Support that this processing is part of the standard Maximo Scheduler refresh behavior and cannot currently be disabled through configuration.

    Therefore, as part of this enhancement request, we would like IBM to consider adding more flexibility around this processing, for example:

    • the ability to avoid or reduce this COUNT query when it is not functionally required;
    • an optimization of the query execution during Refresh Schedule;
    • a configuration option to control this behavior;
    • or any alternative mechanism to reduce the number of rows processed during the refresh.

    This would help improve Graphical Assignment performance, especially in environments with large WORKORDER volumes and concurrent scheduler users.