retrieving data. Example: EquipmentOr HolderIterator_I The CORBA services that are intended to be used along with TMF814 are: Naming service: It involves mapping objects with a hierarchical naming structure. So that names can be used instead of objects in making queries for a specific interface. The server binds the object and name to a namespace. When the client makes a request with a name, the namespace is used to iden- tify the associated object and then invoke a method on the object. Notification service: This service of CORBA allows a server to notify a list of registered clients about an event in a distributed environment. It also provides event filtering and QoS. Telecoms log service: This service of CORBA allows creation of events, review of past events, and recovery of events during a catastrophe. 8.6 MTNM Implementation Statement and Guidelines (TMF 814A) The MTNM CORBA interface defined in TMF814 implemented in different ways. This leads to the need for a document that can guide in the realization of an MTNM interface that ensures interoperability among various vendor imple- mentations. TMF 814A document serves this purpose by giving an implementa- tion statement template and set of interoperability guidelines for the NML-EML interface. According to the TMF 814A document, this can be used: For system vendors to specify in a standard format, the set of MTNM inter- face capabilities supported by their product For service providers to specific to the system vendors in a standard format, the set of MTNM interface capabilities required in the product To create an implementation agreement that has a standard format between multiple management system vendors. TMF 814A has three main sections: 1. Functional Implementation Statements (FIS) This section describes templates to show that all functional capabilities of MTNM interface are supported. The functional capabilities include opera- tions, notifications, and data structures related to objects in the informa- tion model. Fundamentals of EMS, NMS and OSS/BSS 