6. Event model: An event is an incident that can involve a change in the state of the environment or behavior of a component in the environment. An event usually results in a notification. The events present in the event model could be pervasive or infrequent events. The consequences of an event can last a long time affecting many things. Some events may require immediate action on the part of the observer whereas other events could be handled at a later point of time. 7. Interop model: The management components describing the WBEM infra- structure and how they interact with the infrastructure are defined as the CIM interop model. The WBEM infrastructure has: CIM client: The client issues operation requests to the CIM server. It also receives and processes operation responses from the CIM server. CIM server: The server issues operation responses after receiving and pro- cessing requests from the CIM client. CIM object manager (CIMOM): It is a part of the CIM server that facili- tates communication between server components. 8. Metrics model: This model consists of CIM classes specifying the semantics and usage of a metric and classes containing data values captured for a partic- ular instance of the metric definition class. Metrics model facilitate dynamic definition and retrieval of metric information. Management of the transaction response time information generalized to the concept of unit of work and providing the additional metric information about the transaction can be done using metric definition. Information Models 24.4 Conclusion The SID and CIM are two widely accepted frameworks for information modeling. There is considerable divergence between the two models as they were developed by different standardizing organizations. TeleManagement Forum the developers of SID and Distributed Management Task Force the developers of CIM have jointly worked toward harmonizing the two models. The TMF document GB932/DMTF document DSP2004 has the physical model mapping and TMF document GB933/ DMTF document DSP2009 has 