We generally use Impact for ticketing with other ticketing applications like Remedy. We also use it for enrichment of other applications that collect information from different sources, such as on the internet. But primarily, we use Impact for ticketing purposes.

It's a customer-centric product, so in my current company there aren't that many people who use it as an end-user application. In fact, it's mostly only used by the Netcool team, rather than any end-users at all. Only the Netcool/OMNIbus event console and event dashboard will be used by the end-user. In the Netcool team that uses Impact, there are probably 20-30 people, and they assist with the console.

Mainly we're using Impact for event engagement. We're also trying to connect from the third party database like IDSM, and fetching the data. It's for event engagements. and for looking at results within the Impact as to the EF flow of data management.

The primary use case of NetCool Impact is event correlation. 

For example, we are able to manage all the events inside Omnibus. If we want to create an integration with a ticket, we cannot use Omnibus by itself. We need to work with Impact as well. If we are experiencing alarms on our database with Omnibus, and we have to reach the data from Excel, we need to use Impact.