ggregation component: The role of this component is to collect fault data from the data collection components and convert them to events on objects in the topology model or network object model. This could be faults on the network elements or resources in the network elements. The aggrega- tion logic would be given in the XML files as rulesets, which would have as inputs the different fields of the fault record. Each fault record is expected to have a specific set of fields giving data like the severity of the event that gener- ated the record, the element in which the record was generated, the probable cause of the event, and SO forth. 4. Fault correlation component: This component would be triggered on each event. Based on a set of predefined rules, the fault information is updated when each fault record or event is obtained. The update can be an add, mod- ify, or delete operation in the database. 5. Fault delivery and query component: This component provides the applica- tion program interfaces for delivery of faults and query of faults from a data- base. This functionality is implemented using a listener module that registers for fault data. The registration as well as a fault related query can be filtered on any parameter of the fault record. 6. Performance aggregation and correlation component: This component col- lects performance records from the data collection components and pro- vides object persistence by interacting with the object persistence modules in platform components. It can also perform correlation functions on the data based on predefined rules. These rules can be changed dynamically using APIs. What Is NMS? 7. Performance query and threshold component: This component makes per- formance data queries to the database based on parameters in performance records. The threshold functionality permits setting, modifying, and deleting threshold alarm generation rules based on performance data. That is, a thresh- old alarm is generated when a performance parameter crosses a predefined rule value. Bot