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)
Up-issuing a Definition should automatically up-issue any Rule and/or Policy which calls it
ITNCM Compliance manager has a feature whereby once you "activate" a Policy, Rule, or Definition - the version number of that Policy, Rule or Definition is automatically incremented whenever it is edited. It is normal to have each Policy call one or more of Rules, which in turn may call one or more Definitions. The way ITNCM works at present, if a Definition is edited (and hence it's version gets automatically incremented) this has no effect on the version number of the Rule which calls it and the Policy which calls the Rule. It is not obvious by just looking at the Policy that anything has changed. If (as we are) you are developing Policies etc. in a lab environment, for export to a number of production instances of ITNCM, this makes it extremely difficult to maintain version control. The policyExport utility permits a particular version of a Policy (and all Rules and Definitions it calls) to be exported - but at present, if (say) a Definition is updated, there is no indication that the Policy has changed in any way. If we want to convey this by changing the Rule and Policy version we have to do it manually- which is time consuming and prone to error. This enhancement request is for the incrementing of the version number of any Definition or Rule to also automatically increment the version number of any Rule or Policy which calls it. (This should also be extended to extractions etc.)
A multinational company is developing compliance policies using ITNCM, to be rolled out to ITNCM instances in multiple countries. Policies call Rules and Definitions as described above. Strict version control is needed to ensure that the correct policies etc. are deployed everywhere.
Do not place IBM confidential, company confidential, or personal information into any field.