or the predefined values identified by the NMS. That is, the inventory module will reallocate the resources based on its original configuration and the provisioning agent will make the changes on the resources to remove any discrepancies in the network. This method of synchronization is usually used in large service pro- vider setups. Discrepancy reporting: Some management applications gives the operator the choice to select whether a reconciliation or reprovisioning is to be per- formed when a discrepancy is identified. The synchronization application only provides a report rather than taking immediate action. This gives the operator an opportunity to make choices on a case-by-case basis. Element management: The data collection module in the NMS usually does not interact with individual NEs, instead it interacts with the element man- agers for the NEs. Using predefined and standardized interface queries, the NMS module gets management data using the EMS. Both query for a spe- cific data and bulk download are supported in most NMS. Other OSS solutions: Data from the NMS can be distributed to multiple applications. The processed data can be sent to another NMS, like a master NMS that provides a converged GUI for a set of networks managed using Fundamentals of EMS, NMS and OSS/BSS different NMS. The distribution can be to OSS (operation support systems) applications like a service quality management module. The data from NMS could even be distrusted to higher layers like BSS (business support systems) like a billing module or SIP (strategy, infrastructure, and product) invest- ment planning module. 12.4 Resource Trouble Management Network trouble management involves handling the network related issues. This could be analyzing a trouble condition, fixing a bug or just sending an action report to the operator. Some of the activities in network trouble management like raising a trouble ticket and tracking the ticket to final closure cannot be performed at the NMS. These kinds of activities are handled in the OSS/BSS a