Development of reference incident management model

2022

Full text Open access: Gold Metadata (CSL-JSON)
DOI 10.15587/1729-4061.2022.266387
Data confidence 70 medium
How this score is calculated

It is built from checkable properties of the record itself: whether the article has a DOI, how many independent sources confirmed its data, whether the required fields are filled in, and how recent the latest confirmation is. Disagreement between sources and a missing identifier lower it. A value of 80 or above means the record was published without further checking; 60 to 79 means it is published at reduced confidence, with a manual check advisable. A record verified by an editor by hand is never pushed below 90 by a recalculation. This scores our data about the article, not the article itself.

Abstract

One of the most important tasks of improving the information technology infrastructure of an enterprise is to increase the efficiency of the incident management system. The relevance of this study lies in the fact that at present the work of the technical support service in the conditions of a large flow of applications accelerates violation of the deadlines for resolution established by the business. It, in turn, leads to downtime of information systems and financial losses of the enterprise. This article analyzes the feasibility of introducing a third line of technical support to increase the proportion of incidents resolved within the framework of the Service Level Agreement adopted at the enterprise. A comparative analysis of the widely used two-level model with the proposed three-level model in this work is considered, using business process model notation. The effectiveness of the model is confirmed by automated computations using metrics, by calculating the rate and satisfaction coefficients within the framework of two and three levels of the model and then comparing these indicators to establish patterns. Thus, it is possible to track how successfully and timely incidents of information systems are resolved, which in turn directly reflects the availability and correct functioning of systems and the entire company. The company's practical losses due to system downtime were calculated, as well as the resulting financial losses before and after the adopting of the three-level system, taking into account the associated costs to identify if the initiation of the model is justified and profitable. Thus, the proposed model can be adopted by organizations in order to improve the quality of services provided by the IT department, to reduce the effect and impact of incidents on the performance and availability of systems that affect the formation of financial statements