IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
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, 1. Post an idea 2. Upvote ideas that matter most to you 3. 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.
Two of the things we utilize Control Center for is SLC notification and processes that do not end successfully. We have some transmissions that are monitored on SLCs that are contractual (sla). We do get an alert if the sla transmission has not started yet or is late. However, if the same sla transmission fails, that comes out on Control Center as a different type of alert due to it being a different event type. Currently it seems to be impossible to build what I call an "error in process" rule that can use rule key SLC name. We would like to somehow correlate the failure of the transmission to it being a contractual transmission so that it will be more apparent to the operator. Our only alternative is to build multiple error in process rules that would contain a list of the contractual transmissions and the rule can be named so that when it comes out, the operator knows that the transmission that failed is contractual.
|What is your industry?||Non-Industry Specific|
How will this idea be used?
This will be used to provide correlation between a contractual transmission that is on a slc and a transmission failure.
Do not place IBM confidential, company confidential, or personal information into any field.