r individual member. The orga- nization to look for is determined based on requirements. For example TMF would be a good place to look for telecom management standards as it mainly focuses on this area and the documents of the forum would have information on collaboration work with other forums. In the same way DMTF would be a good choice for enter- prise management and SNIA for storage area network management. Additional Reading 1. TMF 513 TR133 NGN-M Strategy Release 1.0 Version 1.2. www.tmforum.org (accessed December 2009). Chapter 8 MTNM Compliant EMS The NMS has to interact with multiple EMS and present an integrated view of data. Now each EMS can be from a different vendor and based on a different technol- ogy. Moreover the different EMS may not talk in a common vocabulary or have a common format for data. Then how is it possible to have a single NMS for multiple EMS? This chapter gives you an understanding on the requirement to have standards for interaction between element management layer (EML) and network manage- ment layer (NML). It has a detailed discussion on the MTNM (Multi Technology Network Management) standards from TMF (TeleManagement Forum). MTNM is a copyright of TMF (www.tmforum.org) 8.1 Introduction Consider that service provider X wants to use your EMS and NE with their NMS solution. To get fault data from an EMS, the NMS solution from X sends query "getAlarmList," which your EMS does not understand and cannot respond to. The obvious solution is to write an adaptor (a process that acts as mediator between two modules and performs format conversion in message/data for the two modules to interoperate) that converts message/data from the format of NMS solution X to a format that your EMS can understand and vice versa. Now there is another service provider Y who also wants to use your EMS and sends a different query "getFaultList" for the same operation. For interoperability another adaptor needs to be written. For NMS solution X to interact with an EMS other than yours will also require an ada