cord problems and provide necessary escalation of the problem based on predefined criteria. Problem management systems are able to associate the effects of problems to root causes based on root cause analysis systems or human deduction. The trouble ticket application records a trouble condition. If the trouble condition relates to a network level problem, then the ticket details are send to the network problem management module. The service or customer level description of the problem is mapped to network specific events and con- ditions at the network problem manager. The network problem manager internally tracks the problem resolution at network level between various departments and notifies the service problem management module on the problem status. 49. Network provisioning and configuration: Order fulfillment involves service provisioning/configuration and network or resource provisioning/configura- tion. In resource provisioning, the order details are converted to resource level requirements that need to be configured and activated. Network provisioning and configuration module works on the resource level requirements to con- figure the resource identified by the inventory management module to offer a specific service. The provisioning and configuration module has multiple interactions with inventory management module. Hence it is important to make these two applications interoperable. After completing provisioning and configuration of network resources, the provisioning application updates information on the status of the resources with inventory application. Some applications also support creation of resource configuration plan. This plan has details of the required resource actions that can be sent to an orchestration to trigger auto provisioning and configuration of resources. 50. Specification management: These applications are used for creating, editing, storing, and retrieving specifications. Specifications can be at the service level, capability level, and resource level. Service specifications deal