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 following attributes of the entities are visible across the interface: Name: The entity instance on the CCV can be uniquely identified using the "name" attribute. Once the naming OS sets the attribute, its value does not vary for the life of the entity. Discovered name: In the case where the OS that publishes the entity on the CCV is not the naming OS, the name of the entity is known as the discov- ered name. This attribute may be left empty if the naming OS publishes the entity first on the CCV. The value of the name attribute and the discovered name attribute of the entity can be set to the same value or different value. Naming OS: The os that is responsible for setting the "name" of the enti