n. 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 supports bulk inventory and alarm operations, and replaces many fine grain operations that were advocated in previous interface specifications. In XML, MTOSI supports most Web service standards including WDSL, SOAP, and XSD. It can be seen that MTOSI offers support for service oriented architecture (SOA) and enterprise service bus (ESB). In MTOSI, the requirements of network management or service resource man- agement have been specified in terms of the entities visible across the interface and the service requests that may be invoked across the interface. The interface agreement document contains the data model describing the entities and associated service requests while the business agreement document contains requirements for the visible data entities and the associated service requests. The information exchange infrastructure through which OSS solutions interact is called a common communications vehicle or CCV. The CCV is used to publish new entities. The OSS has direct access to the CCV. The existence of the entity instance on the CCV is announced by the publishing. Storage and naming of the entity instance is done by naming OS. The entity name could be the name used to Fundamentals of EMS, NMS and OSS/BSS announce the entity. The discovering OS and the naming OS need not be the same OS for any particular entity. The followi