Solution Set (TMF 814) While TMF 513 and 608 present a technology neutral representation of require- ments and information agreement, the TMF814 gives a CORBA based (technology specific) IDL solution set for implementing the EML-NML interface. An EMS MTNM Compliant EMS compliant to TMF 814 means that the EMS uses CORBA IDL for communi- cation with the NMS. Each object in a CORBA interface is provided a unique address known as an interoperable object reference (IOR). While in fine-grained approaches each interface object has an IOR and a coarse-grained approach for cli- ent/server interface means that only a small number of interface objects have IORs. A lightweight object managed by a CORBA object (first-level object), is called a second-level object. The object model in TMF814 follows a course grained approach. A coarse- grained approach with many-to-one mapping between object instances in the information model (TMF 608) and the objects (interfaces) in the interface model (TMF 814). But the operations vary from fine-grained as in getEquipment opera- tion returns the data structure for a single equipment, to course grained as in getAllEquipments operation that returns the data structures for all the equip- ments identified by the management system. So certain interfaces can return mul- tiple entities unlike a separate query for each network entity. The objects in the network exposed using interface are based on the layered con- cepts and layer decomposition detailed in ITU G.805. While the managed objects having a naming convention of <Name>_T, the object manager or interfaces objects used to manage the managed objects including session objects are named <Name>_I. The key manager interfaces are: EMSMgr_I: The NMS uses this interface to request information about the EMS. Active alarms, top level equipments, subnetworks, and topological links information can be obtained using this interface. In addition to collect- ing information, operations such as add/delete can also be performed using this interface. EquipmentI