med by combining the ATM information model (ATMIM) team that was formed to address ATM management and SONET/SDH information model (SSIM) team. MTNM was one of the most deployed interface suites of TM Forum. It includes a business agreement document titled TMF513, an information agreement titled TMF608, a CORBA solution set titled TMF814, and an implementation statement titled TMF814A. Popular NMS solutions like AdventNet Web NMS provide support for TMNF MTNM interfaces. MTNM was mainly focusing on management of connectionless networks with an emphasis on Ethernet and control plane-based networks. When most OS suppliers started converting MTNM IDL to XML, TMF started the MTOSI group. This group took a subset of MTNM and generalized the proce- dures for OS-OS interactions (see Figure 25.1) on an XML-based interface that was most required for the telecom market. A major MTOSI goal is to make the XML interface independent of the transport and gradually supports more transports. Use of MTOSI has many benefits to different players in the telecom value chain. To equipment vendors, MTOSI results in reduction of development costs and provides a faster time to market. It also lowers deployment risks and enables Standard Interfaces CORBA MTOSI MTOSI MTOSI MTOSI MTOSI Figure 25.1 MTNM (point to point) and MTOSI (bus) structure. differentiation. Service providers benefit by a reduction of integration costs and faster time to market for new service rollout. Use of MTOSI helps in reducing development cost for software vendors. It reduces relationship costs and provides easier maintenance and testing that enables product differentiation. For system integrators, MTOSI simplifies interoperability testing and provides faster time to market for integrated solutions. The technical skills and training requirements are also reduced with the use of MTOSI. MTOSI leverages the knowledge gained from MTNM deployments and arti- facts. It supports multiple synchronous and asynchronous communication styles to satisfy the interaction needs. It 