ent group) log service. MTNM Compliant EMS Connection management: MTNM supports both protected and unprotected subnetwork connections, with functionality to set subnetwork connec- tion (establishment, modification, and deletion) parameters, configuration of ATM inverse multiplexing traffic descriptors and SONET/SDH virtual concatenation. Call management: Involves creation of calls, deletion, or modification of calls. It also has adding, deleting, or routing connections linked with calls. Equipment management: This includes equipment provisioning, inventory discovery, and equipment mismatch notifications. Performance management: Capability to retrieve current and historical per- formance data, creation/enabling/disabling of threshold cross alert, transfer of historical performance data, and support for tandem connection monitor- ing (TCM). Security management: Includes identification, authentication, detection, and session establishment based on authentication. Miscellaneous: Other capabilities include GUI cut-through where the NMS GUI interacts with EMS GUI and gets data from the EMS without involving the interface modules and support for software backups on the elements (see Figure 8.1). Latest release of MTNM also includes connectionless and control plane man- agement capabilities and the functional areas associated with these capabilities. The deliverables of MTNM are: TMF513: MTNM Business Agreement TMF608: MTNM Information Agreement TMF814: MTNM Solution Set TMF814A: MTNM Implementation Statement and Guidelines NMS GUI GUI cut through CORBA interface EMS GUI EMS GUI EMS GUI EMS-X EMS-Y EMS-Z GUI cut through CORBA interface Figure 8.1 GUI cut through in MTNM. Fundamentals of EMS, NMS and OSS/BSS 8.3 MTNM Business Agreement (TMF 513) TMF 513 defines the requirements for the interface between NML and EML in terms of the objects involved and operations that the interface is required to sup- port for interaction between the objects. The MTNM Business Agreement has two parts. They are the Business Problem Statemen