Alright, My learners, we are on less than 6.3 service operations processes.
So the learning objective for today in this video we will cover the major service operation processes the scope and concepts of incident management as well as the scope of problem management. Okay,
so the major service operation processes now that is instant management. So that is to restore normal service operations as quickly as possible and to minimize the adverse impact on the business operations, as well as ensuring that the most
possible levels of service quality and val abilities are always maintained.
now, some of the important terms to take mention off this incident and normal service operations. Right? So incident is an unplanned interact interruption to an I T service or a reduction of the quality of an I T service
and then the normal service operations. More restored of normal service,
which is gonna be defined in the S. L. A. Is the operational state where services and sea ice are performing within the agreed service and operational levels.
So when we start thinking and looking into the incident management now, do you have to ensure that the standardized methods and procedures are used for efficient and prompt response analysis documentations as well as ongoing management of those incidents.
You increase that visibility and communication of those incidents
enhance those business perceptions of the i. T. You align the incident management activities and priorities with those particular businesses as faras the matrix of those incidents. And when you start looking into those,
you maintain that user satisfaction with the quality of the services, which comes in place of like surveys of that nature. Okay,
so when we started looking at the scope of the incident management, so incident management like the process that responds to the incidents. So as the definition of the incident extends through events that are causing a disruption off a service as well as the events that could impact the service if not responding to appropriately
so incidents can be open before there is even a verse impact
of that business. So incidents can be communicated by users or technical staffs or even some of the suppliers that's within that's chain. So if if the event doesn't match the definition, it will be out of scope for this. For this process and handled by another, I T service management process as
as appropriate, so this would include information of events that indicate normal service or device operations.
In addition, the customers contact the service desk and making requests not related to an incident will result in a service that's logging as a service request, which will be handled outside of the incident management in that request fulfillment process that we discussed earlier in
all right, so some of the basic concepts of the incident management so each provide each service provider environment will have a number of incident types that are likely to happen more than once due to the nature of the service provided. So some of the
incident remind. Some of the incident models are pre defined steps to handle known types of incidents in the agreed manner,
right, So incident incident models should include the following information such as the steps that should be taken to handle that particular incident or chronic order. Where these steps should be taken and with any dependencies or cold processing is to find so those responsibilities,
who should do what precautions and
to be taken before resolving those incidents are very critical, such as like backing up those status or configuration files of things of that nature. So then we start looking into the time scales,
time skills. It represents the span of time within that certain events should occur. So this is related to the understanding that each activity within that process will contribute to how long it takes to resolve that incident. So you communicate that to all the support groups
and must be based on the great response and resolutions of that target within the S L. A's.
so some of the major concepts of the major incidents that we have followed so that some of the major incidents require higher levels of response from the service provided so clear definition must exist
for what constitutes as a major incident. And a major incident procedure must be defined and communicated to articulate the organization response when a major incident does occur.
So the major incidents, the highest category oven impact for incident results into a significant disruption of to the business and the major incident procedure is a separate procedure with a shorter time scales
in a greater urgency which must be used for major incidents.
Okay, that was our important terms to reference
and then when you go into the instant status tracking when you go into these particular realms. So this status of incidents should be tracked throughout. Right. So the life cycle to support a proper handling and as well that's facilitate the accurate reporting of incidents statuses.
So you probably handle and escalated. You accurately report those incidents statuses,
and then you capture within the incident management system for everyone that, in the need to know, is understanding if it's open or if it's in progress, if it's resolved or if it's closed
and then we go into the problem. The problem management process. Now This process is to manage the life cycle of all problems from first identification through further investigation, documentation and eventual removal. So the purpose
of proper management it seeks to understand the causes of a problem documenting those communicating those known errors
to support staff to minimize the impact of incidents related to those problems
and being pro actively prevent career occurrence of incidents related to those issues as well.
So the objectives of those problems management So it's two. It's responsible for managing those problems cycles. The primary objective is to prevent the occurrences of problems and resorting insistent incidents, eliminating recurring incidents as well as minimize the adverse impact to avoid
So the scope of the problem management So it's probably within the scope of the service operation. So it's more of a reactive problem management as well as the problem, the proactive problem management. Okay,
so that's more on a false primarily within the scope of the eso phase, like was stated. So it's supporting the operational services. So problem measure supports to see is the S C. I activities by proactively identifying those causes and problems before the incident occurs. And then you look into the reactive as well.
Okay, and where that is, problem contains both aspects of both
our focus on identifying and correcting those problems that are triggered in different ways. So, I tell describes the difference between reactive and proactive as being just a process of activities that typically be triggered and reaction, and then focusing and then focusing on the trigger Activities are seeking to improve that service on
the reactive problem management. So that resolves those problems in response to specific incidents or or events. And then you're proactive management, which again is triggered by those improvement activities.
And in some of the basic concepts of problem management, some of them or key definitions, is the workarounds is the known errors and is also the known error database, which is the K e d B, which is the centralized storage of known errors. And those resolutions of those incidents. Foreign problems.
so in summary, the less than 6.3 the major service operation processes within the incident management. We provided you the basic concepts of incident management as well as the problem management processes that within the business structure Now we will be followed by your in the lesson
you're in the lesson quiz and then to the next, um, lesson. All right, so you there.