network to identify the running or active configuration. The audit can reveal the current state of the network elements and other dynamic data like number of packets dropped, which forms a key input to service quality modules. As can be seen in the example of packets dropped, the audit is not restricted to just configuration. It can be used to get attributes on fault, security, accounting, and performance as well. Discovery is a process closely associated with auditing, though these operations are not the same. Discovery is about identifying a new resource or configuration, while audit is verifying the status of an already discovered resource or configuration. Though in a service provider set up any new resource or configuration is not expected due to flow through provisioning, there could still be scenarios where a discovery is required like inventory records might not be accurate, an operator might change things in the network and not always record those changes properly, discovering specific components the network might be more efficient than the current mechanism used, or inventory records might not be available. Many NMS product specifications use the term "discovery" instead of "audit." In these scenarios, the process of initial discovery is explicitly expressed using the term "auto discovery." In addition to understanding the functions performed by the resource data collection and processing (RDCP) module it is also important to have an under- standing of the modules that interact with the RDCP module. The main modules that interact with the RDCP module are: Service quality management: The service management module dealing with quality, issues requests to the data collection module for performance reports. These reports are used for customer QoS (quality of service) management. This service module also requests customer usage records from the data collec- tion module that can be used for rating and discounting. Based on the usage records, the customer is billed using rating or tariff policies of the specif