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 Delivered
Categories Performance
Created by Guest
Created on Jun 30, 2020

TNPM. CommonPack Models (Application Studio): Changing BH_VALUE field name in the SBH Definition area to the counter name

The new structure of Common Pack models (CP) introduced with TNPMW v1.4.1 changed the whole logic of the busy hours (BH).
It was discovered that the so called BH determiner does not come from the same source tables as it was in the old method, but it is sourced from a certain measurement table. While the values are fine in the most of the situations, we found one, where such usage was problematic and the values were missing.
The analysis showed (see attachment) that the true equivalent of former SBHD tables is the field BH_VALUE, which stays the beginning of each query subject and the source field is database table SBH_BUSY_HOUR_DAILY, which is correct. As the field does not bear the counter name, for users it is inconvenient to work with it.
That's why we propose to rename BH_VALUE field to the respective counter name and keep it at the beginning of each of SBH Definition's query subjects, right after the IDs (for the detailed description of the overall structure, see RFE #142657).
It was also discovered that there are at least two or three different fields in the whole query subject, which show the same kind of value. That's why we propose:
- In situations, where only a determiner is defined for a particular BH definition: to rename the BH_VALUE as the respective counter and leave it at the beginning (without adding suffix in the form of entity name and KPI group name as per RFE #142657)
- In situations, where determiner as well as value is defined for a particular BH: to perform exactly the same change as it is described above + there will be a standard counter coming from a measurement table. The standard counter should be sorted together with other counters as per RFE #142657. It should also get entity name and KPI group name suffix, which comes from the same RFE – this will prevent duplicate names and “_1” will no longer be needed.

Idea priority Medium
RFE ID 143592
RFE Product Tivoli Netcool Performance Manager
  • Guest
    Jun 30, 2020

    Attachment (Description): A visual demonstration of what the proposed change will look like.

  • Guest
    Jun 30, 2020

    Attachment (Description): The comparison between new and old method determiner definition.