ormation 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 Statement and the Business Requirement Model. The problem statement defines the scope of the problem and identifies the problem needs or issues, while the requirement model handles an implementation independent description of requirements. The aim of this document is to provide a single common solution to address interoperability between element management and network management layers that involves (see Figure 8.2): Multiple network technologies: Including SONET, SDH DWDM, and ATM Network elements that support multiple technologies Open standards Multivendor EMS and NMS TMF513 is a set of use cases, and static and dynamic UML diagrams that can be used as: Foundation for information and requirement agreement of TMF and other bodies working in this area Definition of requirement agreement and input for information agreement for service providers Development of commercial off the shelf (COTS) products by vendor According to TMF513, adopting MTNM will lead to: Lesser time for service activation Scalable NML-EML interface Reduced effort and time in integration vendor X vendor Y vendor X vendor Y SONET interface interface interface MTNM common interface EMS A EMS B EMS C EMS A EMS B EMS C Figure 8.2 Single solution based on MTNM. MTNM Compliant EMS More options for service providers in choosing products for interoperability Lesser cost to EMS vendors in making their product work with multiple NMS Rapid service delivery Easier to fix