Written by Ana Canteli on 17 July 2020
Incident Management is an ICT management process whose objective is to restore the usual level of service as soon as possible, while trying to minimize the impact that the interruption may have on business operations; ensuring, as much as possible, the maintenance of the best standards of availability and quality of service. The latter is what is known as a service level agreement (SLA).
Incidents may arise from pre-existing problems, known errors, or be the product of a single event, for which there is no prior evidence and for which no information is available. As you can see, incident management can arise from many situations, which is why providing your staff with the platform they can depend on is essential to create a team that shares principles, objectives, and values.
OpenKM's document management system offers all the functionalities, integration, extension, and customization capabilities that your company needs to create the best process management and incident management platform for your company.
Any organization can develop the classification that best suits their needs. Still, ITIL or the Information Technology Infrastructure Library offers a set of concepts and good practices that can be especially useful.
Following these recommendations, it is necessary to differentiate between incidents (unplanned service interruptions) and requests (anything that is inconvenient but does not mean a service interruption. For example a user returns from vacation and does not remember the password and we need to reset it).
Incidents are generally classified according to the assigned priority, this being the result of various considerations: number of users affected, services compromised, operating units affected, urgency, and others. This is where the service level agreement -SLA- becomes essential, since depending on the classification, categorization and possible status assignment (new, assigned, in progress, stopped / waiting, resolved, closed) the teams responsible for Incident management will have more or less time and resources at their disposal to manage the life cycle of incidents. We can mainly consider three categories:
Correctly classifying is a crucial step in incident management processes, as it achieves several goals. It provides workgroups with information based on the Incident Management Model, which allows automatic prioritization. Such information may also determine the assignment of the incident to a particular workgroup. As a result of the classification, patterns and trends can be better detected; in this way, it is easier to identify which incidents are most frequent and, therefore, to develop the most appropriate solution: change of procedure, training courses, or something else.
OpenKM offers category navigation so that you can see all the content that corresponds to a specific classification or categorization at a glance. Also, the Reports functionality allows us to obtain meaningful and detailed information on any aspect relevant to our objectives. And thanks to the subscription service, when an incident is declared or detected, the system immediately informs us about the event. From the search engine, we can retrieve any record based on any information we have: metadata, content, date, author, or any relevant data.
All incidents should be recorded in the organization's incident management system. Keep in mind that incidents can be reported by different actors and be reported in very different ways: a user can call, send an email, use a chat to report a problem, or even a technician can receive an automatic alert of a monitoring system. That is why it is vital to have an incident management system that adapts to our current and future needs, to exercise exhaustive control over service interruptions so that they are adequately treated and do not become an additional source of problems.
Once we have identified an incident, registering an incident means creating a new registry in the system, which will document all the necessary information about the event: date, the information provided by the user, description, and associated problems. OpenKM is an electronic records management system that guarantees the adequate treatment of this type of content, with particular attention to the control of the record's life cycle, including final disposal.
It is the fundamental step that will allow us to continue with the rest of the stages of the incident management process:
OpenKM, thanks to automatic tasks, among workflow and OCR engine can cover all incident related management processes.
The objectives of incident management are to facilitate the operational control of the business, increase productivity, maintain adequate service levels, promote the identification, and even prevention of incidents that may evolve in more severe cases.
Implementing an incident management system is done in part to achieve a series of objectives, because it provides a multitude of advantages, including:
But we must not lose sight of the fact that incident management can be a complicated issue when not sensitive, therefore it is advisable to follow a series of tips:
JBA Solutions Sdn Bhd
Malaysia: Sila telefon +60 12 809 1368.
Isnin - Jumaat: 08:00 pagi - 12:00 petang, 13:00 petang - 17:00 petang GMT+8 untuk bantuan segera. Masa sekarang ialah hari Ahad 06:47 am di Kuching, Sarawak, Malaysia.
OpenKM di seluruh dunia: