hus, ideally, we would also like to isolate the cause of the problem. Fault management should include the means to (a) bypass troubled sections of a net- work and (b) patch in new equipment for deteriorated or failed equipment. The complexity of modern telecommunication networks is such that as many network management tasks as possible should be automated. All displays, readouts, and hard copy records should be referenced to a network time base down to 0.1 sec. 1 This helps correlating events, an important troubleshooting tool. 21.3.2 Configuration Management Configuration management establishes an inventory of the resources to be managed. It includes resource provisioning (timely deployment of resources to satisfy an expected service demand) and service provisioning (assigning services and features to end-users). It identifies, exercises control over, collects data from, and provides data to the network for the purpose of preparing for, initializing, starting, and providing for the operation and termination of services. Configuration management deals with equipment and services, subnetworks, networks, and interfaces. Its functions are closely tied to fault management, as we have defined it above. 21.3.3 Performance Management Performance management is responsible for monitoring the network to ensure that it is meeting specified performance. Some literature references (Ref. 1) add growth manage- ment. They then state that the objective of performance and growth management is to ensure that sufficient capacity exists to support end-user communication requirements. 1 Network time bases are usually much more precise and derive from a network clock, which may be external to the network, such as GPS. Stratum #1 clock +1 X 10-11 per month. 21.4 SURVIVABILITY - WHERE NETWORK MANAGEMENT REALLY PAYS Of course there is a fine line defining network capacity. If too much capacity exists, there will probably be few user complaints, but there is excess capacity. Excess capacity implies wasted resources and, thus, wasted money.