and its elements are ready to offer a specific service. For example, if the element being provisioned is a call agent that provides call processing capability, then the test would involve running some test scripts that simulate an actual call and verifying the call records generated against an expected record set created for the simulated call. A test case can even be a simple check to ensure that no errors were generated during a software instal- lation or verifying if the modules are running with the parameters specified as part of configuration. Track and manage: The network provisioning operations needs to be tracked and managed. Tracking involves ensuring that the various manage- ment functions involved in provisioning are executed properly. Tracking helps to identify errors or issues that are raised during provisioning SO that the same can be posted to an administrator for taking corrective action. Managing involves interaction with other modules, for example if a par- ticular element in a network is identified as faulty, the same needs to be communicated to the inventory management system for allocating a new replacement element and once network and service provisioning is com- plete, the order management system needs to be informed to close the request. Issue reports: The reports issued in network provisioning are quite differ- ent from the FCAPS reports in maintenance. The reports issued in net- work provisioning is intended to provide interested parties, information on the status of provisioning, efficiency achieved with current configura- tion parameters, total time for provisioning, elements that failed and the operation that caused failure, and SO forth. This would mean that the pro- visioning reports are customized reports for a specific audience unlike a maintenance report. Recovery of element: Similar to allocation of resource, the unused resource or element needs to be deallocated for use in satisfying a new order or as a replacement for some faulty element in an existing order. The process of is