Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Jan 25, 2017

Dynamic Critical Path DCP

Provide a parameter to desensitize the triggering of EQQP23I Potential Risk Alert

Current functionality: Potential risk alerts trigger when a job on the critical network is late, or on abend even if the critical jobs deadline time is many hours in the future.

I appreciate that if a job in the critical network leading to a critical job abends there is potential that the critical job may be delayed. But what I observe is that a job in the critical network would abend several hours before the critical job deadline time causing the potential risk alert. Given most abends are resolved in under 30 minutes in our shop, I would like to be able to desensitize the alert possibly based on amount slack time to the end point.

Perhaps a parameter that would take into account slack time in the critical network before the critical job is delayed. One way would be by percentage: Suppress the alert until 20% of the slack time has elapsed. Another would be by an absolute value. If slack time > 3 hours suppress the alert.

Idea priority Medium
RFE ID 100114
RFE Product IBM Workload Scheduler (IWS)
  • Guest
    Apr 15, 2022

    This requirement is valid but low priority and not in plan in the near future. We close it for now, you may re-open it if still needed.

  • Guest
    Nov 6, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Workload Automation and Control Desk
    Product - IBM Workload Scheduler (IWS)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - IBM Workload Scheduler (IWS)