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)
compliance manager process - select by VTMOS realm AND device realm
In a Compliance Manager process, we need a way to get it to select the devices to run policies against by both VTMOS realm AND device realm - the GUI currently only allows either/or and we really need to be able to do both.
E.g. at present we can configure a process to run a policy A against all devices in realm Z, or we can configure it to run policy A against all routers in all realms, but we can't configure it to run policy A against all routers in realm Z.
The way it works at present, a/ It means that each policy gets checked against ALL devices in the realm identified by the process filter, which does not seem very efficient. (I understand that the VTMOS filter on the policy will stop it from getting very far – but it seems to me that it will be initiating this check un-necessarily on all devices in the realm. If the filtering could be done at the process level, it would not even need to start checking devices that were not the desired VTMOS).
b/ It means that we can't have a truly GENERIC policy (e.g. “every device must have a hostname”) and run it against routers in realm A every Monday and against switches in realm A every Tuesday.
We have a number of device realms that are used as a "holding bay" into which devices are initially discovered. When we are sure that configs have been imported successfully they are moved to realms representing location etc. We do not want to run Policies against devices while they are in the holding bay realms. This means that we always need to use the realm filter in the process we are running, so we cannot also do VTMOS filtering in the process.
Do not place IBM confidential, company confidential, or personal information into any field.