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 Submitted
Created by Guest
Created on Oct 1, 2026

Enable Enterprise-Level Failure Hierarchy Management Across Multiple Organisations

I've been consulting for DP World, and they have a requirement to manage failure classes and hierarchies at system-level, rather than organization level. The two key benefits are:

  • A consistent hierarchy across all global terminals
  • Less administrative burden when amending or changing the failure hierarchy

More information is below:

Current Limitation

In Maximo Manage, Failure Classes and their associated Failure Hierarchies (Problem, Cause and Remedy codes) are maintained at the Organisation level.

For organisations operating a single Maximo instance with multiple Organisations, this results in significant duplication and governance challenges. While many enterprises require a single standardised failure reporting taxonomy across all business units, each Organisation must currently maintain separate Failure Classes and Failure Code libraries.

This creates several issues:

  • Duplication of Failure Classes across Organisations
  • High administrative effort when introducing or modifying codes
  • Risk of inconsistent failure reporting between Organisations
  • Difficulty implementing enterprise-wide reliability and failure analysis standards
  • Challenges maintaining alignment with ISO 14224 and corporate reliability frameworks
  • Additional migration and deployment complexity during implementations

Large asset-intensive organisations often operate multiple Organisations within a single Maximo environment to support regulatory, commercial, or regional requirements, whilst still requiring common reliability reporting standards.

Proposed Enhancement

Introduce an Enterprise Failure Hierarchy capability that allows Failure Classes, Failure Codes and hierarchies to be defined and governed at the System level.

Administrators should be able to:

  • Create Enterprise Failure Classes once
  • Maintain Enterprise Problem, Cause and Remedy structures centrally
  • Assign Enterprise Failure Classes to assets and locations across multiple Organisations
  • Control whether a Failure Class is:
    • Enterprise-managed
    • Organisation-managed
    • Enterprise-managed with Organisation extensions
Idea priority Medium
Needed By Not sure -- Just thought it was cool