<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A methodology for assessment and management of process-related risks</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>I.V. Abramov</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>V. Taratukhin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>I.V. Illarionov</string-name>
          <email>igor.illarionov@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Muenster</institution>
          ,
          <addr-line>Muenster</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Voronezh State University</institution>
          ,
          <addr-line>Voronezh</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The paper suggests a methodology of risk assessment based on the recommendations and requirements of ISO/IEC 31010 standard regarding the outer and inner parameters of a specific organisation. A System for Prevention and Management of Process-Related Risks (SPMR) is suggested. It helps to forecast and monitor the risks effectively. The system is based on the BI system workflow, which allows the Managers of the organisation to receive graphic information.</p>
      </abstract>
      <kwd-group>
        <kwd>risk management system</kwd>
        <kwd>BI System</kwd>
        <kwd>process-related risks</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Heads of various organisations always face a range of risks and pay a lot of attention to
risk management in decision-making process. The problem of risk management is
therefore of great importance for IT developers. The need for information that would
allow for timely risk management has led to the development of a new sphere - risk
management. Experts working worldwide in various spheres of human activity
managed to develop an internationally recognised risk management standard [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] (further
referred to as ISO/IEC 31010).
      </p>
      <p>
        The need to produce quality goods that would meet consumers’ requirements resulted
in the introduction of quality management systems (QMS) in organisations. The design
and introduction of such systems, in turn, led to the development of quality standards.
International standards for quality management systems were elaborated over time to
meet the requirements of people. It therefore became necessary to assess and manage
risks [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        A specific feature of ISO/IEC 31010 is that it takes into account various criteria
applicable to risk management. On the one hand, the standard recommends using clear and
consistent risk assessment techniques. On the other hand, it also suggests the most
effective risk assessment methods for enterprises. The standard provides a unified
description of such methods, their specifics, strengths, and limitations. ISO/IEC 31010
also lists the requirements to the risk assessment methods that must be met when
designing a risk management system (RMS). According to the standard, RMSs must
regard the following parameters: 1) applicability of the methods at various stages of risk
assessment and 2) factors influencing the choice of the assessment methods.
The applicability of risk assessment methods (Table A) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] is strictly determined as
“strongly applicable” (SA), “applicable” (A), and “not applicable” (NA). Using this
information, developers of a RMS can determine a range of risk assessment methods
they should use when designing the system. However, the recommendations provided
by the standard also determine a strictly limited set of risk assessment methods that can
be employed in specific circumstances. This may result in the ambiguity of the results
of the risk assessment process. It also and makes it much more difficult to design a
RMS and causes confusion for the developers.
      </p>
      <p>
        Taking into account the factors determining the selection of risk assessment techniques
(Table B) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], such as “Resources and Capabilities”, “Uncertainty”, and “Complexity”,
allows to evaluate their relevance as “Low”, “Medium”, and “High”. ISO/IEC 31010
also provides information regarding the quantitative output of each technique. The
necessity to account for the listed factors when selecting the assessment techniques results
in the same ambiguity as the necessity to account for their applicability (Table A) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
This means that there are two overlapping uncertainties in selecting the assessment
methods.
      </p>
      <p>Another issue that should be regarded when selecting risk assessment methods is the
fact that ISO/IEC 31010 also focuses on the level of expertise in various spheres. It
should be noted that the standard is general in nature - it reflects good practices of
selecting risk assessment techniques and provides guidance across various industries
and types of organisations.</p>
      <p>
        Corollary. In order to develop a functional RMS, the recommendations of ISO/IEC
31010 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] should be adapted to the specific parameters of the organisation.
In this paper we suggest a methodology and a BI system for risk assessment and
management that has the following benefits.
• On the development stage it is possible to:
–
–
–
select risk assessment methods suggested in ISO/IEC 31010 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] regarding the
specifics of a certain organisation;
create a risks register of a certain type;
generate a graphic representation of the risk level, both for individual risks and
ranges of risks.
• On the production stage it is possible to:
–
–
–
evaluate the current values of various parameters of risks;
monitor the risks and create graphic representations of their level;
take risk prevention measures
      </p>
    </sec>
    <sec id="sec-2">
      <title>Selection of risk assessment techniques</title>
      <p>
        When designing a RMS, the developers should take into account the recommendations
of ISO/IEC 31010 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] as well as the inner parameters of the organisation where the
RMS will be employed [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The suggested methodology of selection of risk assessment
techniques is based on the analytic hierarchy process (AHP), heuristic logical actions
of the experts, and the decisions of the decision maker. The following decision making
algorithm is suggested (Fig. 1):
Strengths and limitations of every risk assessment technique were analysed. At the first
stage of the analysis we divided the assessment techniques into 20 groups based on
their strengths and limitations. Each group includes techniques with equal
characteristics. As a result we obtained two sets of groups (strengths / limitations) with each group
including its own set of techniques. Some techniques can be included into several
different groups [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Each group is ranked by the experts of the organisation, using the
expert scale.
      </p>
      <p>At the second stage, the criteria relevant for certain activities of the organisation are
determined. and ranked by the organisation’s experts. The criteria are universal, i.e.
applicable to any group of risk assessment techniques.</p>
      <p>As a result, we obtain a hierarchy where the top level is the target (selection of the best
group of assessment techniques), the second level contains the criteria for the selection
of groups of assessment techniques, and the third level contains the groups of
assessment techniques.
The third stage includes selecting groups of techniques (alternatives) using the analytic
hierarchy process (AHP).</p>
      <p>The selection of risk assessment techniques is performed by means of VBA - a
programming language used in Microsoft Excel. The selection process is demonstrated in
Fig. 2.
The selection process is demonstrated in Fig. 3.</p>
      <p>
        The fourth stage includes graphic selection of risk assessment methods. The selection
process is based on the relevance of the groups of methods of both sets.
The fifth stage includes the analysis of the selected techniques regarding the
recommendations of ISO/IEC 31010 (Table A, B) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
If the results are not satisfactory, it is possible to repeat the above listed stages
correcting the process of expert ranking, the criteria, and the sets of selected risk assessment
methods.
      </p>
      <p>Corollary. Development of a RMS includes the following.
• It is necessary and possible to take into account inner and outer parameters of the
organisation when selecting risk assessment methods.
• Parameter-based selection process allows the developers to broaden or narrow the
search area based on the relevance of the groups of methods.</p>
      <p>The process of RMS design involves experts working at the organisation.
Risk assessment methods help to identify the risk, its category, level, and type, the
probability of risk and its consequences.</p>
      <p>The suggested programme for selecting risk assessment methods is a subsystem of the
BI system “System for Prevention and Management of Process-Related Risks”
(SPMR).
3</p>
    </sec>
    <sec id="sec-3">
      <title>BI system SPMR - development stage</title>
      <p>
        The development stage starts with “Risk Identification” [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. The interface of the
programme is demonstrated in Fig. 4. The ranking chart is generated step-by-step, and is
thus completed with the data obtained during the “Risk Analysis” (P - probability of
risk, I - impact, R - rank of the risk). Each element (P, I, R) of the BI system SPMR
has its own graphic representation.
The last part of the development stage is the “Comparative Analysis of Risks”. Risks
are first analysed separately with regard to the relevant areas. Then they are analysed
all together with regard to a specific area (Fig. 5).
• Administrators - members of the IT service. They develop the organisational
structure of the system's users: lists if employees and their status, passwords, and
directories of personal RISK REGISTERs.
• Status 1 employees - Managers / Executives who can work with subsystems of the
risk assessment process and certain RISK REGISTERs.
• Status 2 employees - Managers who can work with subsystem “Risk Assessment
METHODS”, subsystems of the risk assessment process, and certain RISK
REGISTERs of executives.
To assess the dynamics of risks, the following parameters are used that allow for
monitoring risk generation (Fig. 4):
      </p>
      <sec id="sec-3-1">
        <title>Source</title>
      </sec>
      <sec id="sec-3-2">
        <title>CAUSE</title>
      </sec>
      <sec id="sec-3-3">
        <title>Event</title>
      </sec>
      <sec id="sec-3-4">
        <title>SOURCE</title>
      </sec>
      <sec id="sec-3-5">
        <title>EVENT</title>
      </sec>
      <sec id="sec-3-6">
        <title>RISK</title>
        <p>The initial stage of risk occurrence is represented by the parameter “Source CAUSE”.
Its value, as well as the set of such parameters corresponding to a certain parameter
“Event SOURCE”, denote the moment when the source occurs. The set of parameters
“Event SOURCE” denotes the moment when the parameter “EVENT” occurs. The set
of parameters “EVENT” results in the occurrence of risk.</p>
        <p>As the occurrence of risk has certain impact on the organisation, the parameter “Source
CAUSE” is the key one. It allows to identify the initial stage of risk occurrence and
take measures to eliminate the cause of risk. These actions correspond to Risk
MITIGATION.</p>
        <p>To implement this process within the BI system SPMR, the value of the parameter
“Source CAUSE” is determined by experts. This value is shown in the column “Norm”
of the Risk Register chart (Fig. 4). The BI system can also generate an .xlsx file, which
is completed with the current data and the values of the parameter “Source CAUSE”
imported in the column “Fact” of the Risk Register (Fig. 4).
The dynamic monitoring of risk probability is performed using the Risk Assessment
Graph (Fig. 6).</p>
        <p>This graph enables the Manager to see risk probabilities at a certain period of time.
When the Manager of the organisation makes a decision to take certain measures, the
BI system locks the values of the parameters in the column “Source CAUSE” in the
RISK REGISTER. These values correlate with the values in columns “Norm” and
“Fact” and thus, when the value of the “Fact” exceeds the value of the “Norm” the cells
of the column “Source CAUSE” are highlighted.</p>
        <p>If all the cells of the column “Source CAUSE” corresponding to the parameter “Event
SOURCE” are highlighted, the colour of this cell also changes.
The same algorithm is applied to the cells of the RISK REGISTER. If all the cells of
the column “Event SOURCE” corresponding to the parameter “EVENT” are
highlighted, the colour of this cell also changes.</p>
        <p>If all the cells of the column “EVENT” corresponding to the parameter “RISK” are
highlighted, the colour of this cell also changes. This denotes the moment of the
occurrence of risk at the organisation.</p>
        <p>Highlighting of the cells of the RISK REGISTER allows to make a Risk Diagram which
reflects the process of risk occurrence in time. An example of such a process is shown
in Fig. 7.</p>
        <p>In order to prevent and monitor risks, the organisation creates a set of documents, which
describe the measures and procedures of elimination of the factors that may cause risks.
All the documents are approved by the administration of the organisation and stored in
accordance with the rules of the IT service.</p>
        <p>The BI system also has a function that allows Managers to take risk prevention
measures using the Risk Diagram.
When a Manager makes a decision to take certain actions to eliminate a threat of risk
based on the Risk Diagram, the employees can open a corresponding document and act
accordingly. The subsystem responsible for the process is demonstrated in Fig. 8.
Thus, the proposed algorithm allows for real time risk elimination.
• The paper suggests a methodology of risk assessment based on the recommendations
and requirements of ISO/IEC 31010 standard regarding the outer and inner
parameters of a specific organisation.
• A System for Prevention and Management of Process-Related Risks (SPMR) is
suggested. It helps to forecast and monitor the risks effectively.
• The system is based on the BI system workflow, which allows the Managers of the
organisation to receive graphic information.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. ISO/IEC 31010:
          <year>2009</year>
          ,
          <article-title>Risk management - Risk assessment techniques</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. ISO 9001:
          <year>2015</year>
          ,
          <article-title>Quality management systems - Requirements</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Abramov</surname>
            <given-names>I.V.</given-names>
          </string-name>
          <article-title>Working with risks based on GOST</article-title>
          R ISO/IEC 31010.
          <article-title>- Economy and society</article-title>
          , №
          <volume>4</volume>
          (
          <issue>23</issue>
          )
          <year>2016</year>
          . 30p.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Beasley</surname>
            ,
            <given-names>M.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clune</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Hermanson</surname>
            ,
            <given-names>D.R.</given-names>
          </string-name>
          ,
          <year>2005</year>
          .
          <article-title>Enterprise Risk Management: An Empirical Analysis of Factors Associated with the Extent of Implementation</article-title>
          .
          <source>Journal of Accounting and Public Policy</source>
          ,
          <volume>24</volume>
          :
          <fpage>521</fpage>
          -
          <lpage>531</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Hoyt</surname>
            ,
            <given-names>R. E.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Liebenberg</surname>
            ,
            <given-names>A. F.</given-names>
          </string-name>
          ,
          <year>2011</year>
          .
          <article-title>The value of Enterprise Risk Management</article-title>
          .
          <source>The Journal of Risk and Insurance</source>
          ,
          <volume>78</volume>
          (
          <issue>4</issue>
          ),
          <fpage>795</fpage>
          -
          <lpage>822</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>