Event correlation usually takes place inside one or several management platforms.
This component is automatically fed with events originating from managed elements (applications, devices), monitoring tools, the Trouble Ticket System, etc.
However, only some of them are able to notify trouble ticket systems when a problem is solved, which partly explains the difficulty for Service Desks to keep updated with the latest news.
In theory, the integration of management in organizations requires the communication between the event correlator and the trouble ticket system to work both ways.
It may also report that a situation goes back to normal, or simply send some information that it deems relevant (e.g., policy P has been updated on device D).
A fifth step (action triggering) is often associated with event correlation and therefore briefly mentioned here.
For instance, a number of bottom-of-the-range devices are difficult to configure and occasionally send events of no interest to the management platform (e.g., printer P needs A4 paper in tray 1).
However, by language abuse, the event correlators found on the market (e.g., in network management) sometimes also include problem-solving capabilities.