 defined for a set of alarms as a single event and can generate multiple alarms on different network elements. For example, a connection loss between two NEs would generate multiple alarms not just related to connection but also on associated resources and its attributes that are affected by the connection loss. The relevant log(s)/alarm(s) needs to be filtered out and corrective action defined for the same. Event Correlation: An integral part of effective fault handling is event correla- tion. This mostly happens in the network and service management layers. It involves comparing events generated on different NEs or for different reasons and taking corrective actions based on the correlated information. For example, when the con- nection between a call server and media gateway goes down, alarms are generated on the media gateway as well as the call server, but the NMS handling both these NEs will have to correlate the alarms and identify the underlying single event. The process of grouping similar events is known as aggregation and generating a single event is called event aggregation. Event processing usually involves event filtering as well as event correlation. Event processing in a service layer can generate reports on a service that could help to analyze/improve quality of service or to diagnose/fix a service problem. Some of the applications where basic fault data can be used as feed are: Quality assurance application: The lesser the faults the better the quality Inventory management application: Faulty NEs would need service or replacement Service and resource defect tracker Event driven intelligent resource configuration and maintenance Product and infrastructure budget planning Most EMS/NMS applications also have fault clearing, fault synchronization, fault generation, and fault handling capabilities. 3.3 Configuration Management Configuration management involves work on configuration data asso- ciated with the managed device/network element. Some of the functionalities handled in configuration manageme