nt are: Resource utilization: This would involve the representation of data on how effective the configuration is in getting the best out of the network. Some examples include count of the number of trunks that are not working prop- erly, plot of under utilization of a trunk with less traffic routing, and SO on. Fundamentals of EMS, NMS and OSS/BSS Network provisioning: Involves configuring network elements and subre- sources in the element to offer a service, or in other words the network is set up using interactive interfaces for proper working. Auto discovery: When the management application comes up it scans the network and discovers the resources in the network, which is called auto discovery. As part of auto discovery the state of the resource (in service, in trouble, offline, busy, etc.) and its attributes that are to be displayed and used in the management application are also collected. Backup and restore: It is critical to backup configuration information and restore the data when required. Some possible scenarios include, installing a new version of software on the NE, upgrading a software, taking the NE down for some maintenance or fault correction, and SO forth. Inventory management: This involves keeping track of the resources (both active and inactive) in the enterprise, SO that they can be allocated, provi- sioned, rolled out, kept as backup, and SO forth. The output of auto discovery is a feed to inventory management to synchronize the status of the resources allocated for a network. Change management: The change in status of the network elements needs to be continuously monitored and updated. Break down of an element without proper mitigation strategy can result in loss of business and in a military domain it could result in loss of life. So the change in status would trigger actions corresponding to the new state. Preprovisioning: A set of parameters needs to be set during provisioning. Effective decision on the parameters to set can be obtained by trend analysis of the network element. This wo