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
Start by posting 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,
Post an idea
Upvote ideas that matter most to you
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 offering manager 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 notifications 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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.
Do not place IBM confidential, company confidential, or personal information into any field.