toring data. In between the MoM and the managed object is an intermediate component having a manager, agent NMS, and an agent. We will call it the intermediate component similar to the explanation for three-tier to avoid confusion. The manager in the intermediate component of MoM collects data from the managed object, the agent in the intermediate component feeds the MoM, and the "agent NMS" is the management process that deals with functions for managing network in a specific domain. There is one more relationship defined in OSI organizational model that specifies: An agent NMS and a manager NMS share a peer-to-peer relationship. This is suitable for exchange of information between network service providers. Thus the organizational model defines the network management components, their Fundamentals of EMS, NMS and OSS/BSS functions, and the relationships possible with these components in various network management scenarios. 5.3 OSI Information Model The OSI information model deals with structure and storage of information. It details how to form an information base using managed network objects and their relationships. Specified by ISO 10165, the OSI information model is an object- oriented data model. It has two main definitions: structure of management information (SMI) management information base (MIB) 5.3.1 Structure of Management Information (SMI) The SMI defines the syntax, semantics, and addition information like access permis- sion, status, and SO on of a managed object. A managed object in the information model is similar to "class" in high level programming language (see Figure 5.4). The managed object definition like class provides a template to encapsulate attributes and management operations of the object. It also supports asynchronous interac- tions as events. Consider the scenarios where the managed object class is representing a gate- way. The rectangle is the MO, ellipsoidal shape represent attributes, rectangle with smooth corners represent behavior, and triangle represents event. There can be