beat notifications, time between two heart beats, and SO on. MTNM Compliant EMS 3. Guidelines for using the MTNM interface: These guidelines give more clarity to MTNM specifications. Some of the guidelines include: The need for NMS to understand how EMS packages managed elements to subnetworks. How the MTNM service states can be mapped to other models like the ones from ITU-T. The usage of resource names like userLabel, nativeEMSName, and SO on. Some examples of probable cause templates. Set of implementation specific use cases. Description of modes for state representation. For a detailed understanding of the usage of MTNM, the TMF 814A document can be downloaded based on details given in Additional Reading. 8.7 Conclusion This chapter may not be suitable for beginners and some of the terms and concepts expressed in this chapter might be difficult to understand for a novice in telecom management. However once the reader has completed the chapters on network management, then there will be a better understanding on the EML-NML inter- face. So the author would like to urge the reader to re-visit this chapter after cover- ing the chapters on network management. While the EML-NML involves some aspects of network and its management, the author decided to cover this chapter under Element Management System because, the major development to achieve compliancy with MTNM is to be done in the EMS. The EMS implements all the interfaces to respond for queries from the NMS. As already discussed in Section 8.5, there is only one interface supported by the NMS and used by EMS and all the other interfaces are supported by EMS and used by NMS. Additional Reading Latest version of the documents specified below can be downloaded from WWW. tmforum.org 1. TMF 513, Multi-Technology Network Management Business Agreement. 2. TMF 608, Multi-Technology Network Management Information Agreement. 3. TMF 814, Multi-Technology Network Management CORBA Solution Set. 4. TMF 814A, Multi-Technology Network Management Implementation Statement (IS) T