Skip to main content

Event Management

Event Management is the process that monitors all events that occur throughout the IT infrastructure. It provides the basis for normal operation (service assurance) and also detects, reports on and escalates exception conditions.
An event can be defined as any detectable or discernible occurrence that has significance for the management of the IT Infrastructure or the delivery of IT service and evaluation of the impact a deviation might cause to the services. Events are typically notifications created by an IT service, configuration item (CI) or monitoring tool.
It is unusual for an organization to appoint an “event manager” as most events tend to occur for many different reasons and will in most cases be managed by the technical or application management team whose technology or application is impacting the delivery of an associated service.  However, it is important that Event Management procedures are well defined documented and coordinated among ITIL processes and Service Operation functions. An Event Process Owner and Process Manager would carry out the generic functions of those roles.
Service Desk is not usually involved within the Event Management process unless the event has been identified as an incident which, in its initial stages, will be handled by the Service Desk who will continue to communicate about the incident throughout its lifecycle, but will typically be escalate to the appropriate functional teams for resolution.
Technical and application teams do play significant roles in Event Management during operations but also during design where they will participate in designing aspects of a service such as event classification, definitions for auto responses and reprogramming of correlation engines when necessary.  During the transition stage of the life cycle these designs will be tested to ensure that they are generating the applicable responses.  During service operations these teams will perform Event Management for the systems and applications under their control.  They may also be involved with managing any incidents or problems that arise from these events.
It is a frequent practice for event monitoring and first line response to be supervised by IT Operations Management.  Operators will be tasked with monitoring events and ensuring that they can initiate, coordinate or even perform proper documentation and when appropriate that escalations occur according to standard operating practices.   

To learn more about this topic: http://www.itsmacademy.com/itil-osa/ 

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL® Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem