<!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>Computer System for Evaluation the Reliability of Technological Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kateryna Yalova</string-name>
          <email>yalovakateryna@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kseniia Yashyna</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Leonid Dranishnikov</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Abdel-Badeeh M. Salem</string-name>
          <email>abmsalem@yahoo.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fault Tree</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Analysis.</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ain Shams University</institution>
          ,
          <addr-line>El-Khalyfa El-Mamoun Street Abbasya, Cairo</addr-line>
          ,
          <country country="EG">Egypt</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Dniprovsky State Technical University</institution>
          ,
          <addr-line>Dniprobydivska str.2, Kamyanske, 51918</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>IntelITSIS'2022: 3rd International Workshop on Intelligent Information Technologies and Systems of Information Security</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>on the Fault Tree of different</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>The paper presents the results of developing a computer system for evaluation of reliability of technological systems, which Automation of the Fault Tree construction process is aimed at accelerating and improving the accuracy of graphical representation process of the technological system model to assess the level of its reliability and identify the components that most affect the risk of accidents. The paper substantiates the feasibility of using the Fault Tree and describes the algorithm for qualitative and quantitative analysis of Fault Tree data. The architecture of the developed computer system is multi-layered, divided into data layer, user interface layer, and business logic layer. The input for a computer system is a description of a technological system - the object of study - which is defined by a set of interrelated events with a given intensity of occurrence, the combination of which can result in a particular major undesirable event. Based on the entered input data, the Fault Tree is automatically constructed, the probability polynomial is formed, the probabilities of occurrence of intermediate events and the top event are calculated, the list of the minimum emergency combinations and trajectories is developed. The relational database proposes storing data on technological systems, events, types of connections, and graphic notations to implement information actions of inserting, deleting, editing, committing, and exporting data. The adequacy of the implemented design solutions was proved by testing the computer system complexity from different domain. The results of its application to analyze the reliability of the technological design of brown smoke suppression of metallurgical production in the framework of research work “System analysis and computer modeling of technological processes and information technologies” are presented. System reliability analysis, fault tree analysis, computer system ORCID: 0000-0002-2687-5863 (K. Yalova); 0000-0002-8817-8609 (K. Yashyna); 0000-0002-9291-4074 (L. Dranyshnykov); 0000-0003-</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        It is impossible to achieve absolute safety for systems that use energy. All measures for the safe
operation of technological systems must consider the possibility of dangerous, undesirable situations
and focus on the relevant risk [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Analyzing the reliability of technological equipment has recently
become increasingly important. The concept of manufactured risk management emerged when, given
the growing number of potentially dangerous facilities and the associated increase in accidents and
catastrophes, the question arose as to which strategy to choose to ensure the safety of manufacturing
facilities. The tasks of systems reliability evaluation in engineering practice are faced by specialists
who perform design and engineering work, developers of plans for localization and elimination of
      </p>
      <p>2022 Copyright for this paper by its authors.
emergencies and accidents, developers of safety declarations for high-risk facilities. Risk should be
understood as the expected frequency or probability of specific hazards class or the amount of
possible damage (loss, damage) from an undesired event or some combination of these values. The
application of the concept of risk, thus, allows to translate the danger into the category of measurable
categories, where risk is a measure of danger and includes the following quantitative indicators:
• probability of occurrence (frequency of occurrence) of the dangerous factor under
consideration;
• the amount of damage from the influence of a dangerous factor;
• uncertainty of losses and probabilities.</p>
      <p>
        The term “risk” is used to analyze the reliability of technological systems, determine the level of
hazards and form a set of actions to reduce the risk of an adverse event [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Suppose the concept of
“risk” is applied to the technosphere. In that case, it should describe the probability of an accident
when using the mechanisms or machines of a technological system particular process. The
manufactured risk analysis is used to assess the reliability of technological systems, which aims to
determine the frequency of adverse events and calculate the probabilities of their occurrence.
In general, the main tasks of risk assessment are related to:
1. Identification of hazards.
2. Analysis of the frequency or probability of adverse events.
      </p>
      <p>3. Assessing the consequences of adverse events.</p>
      <p>The generalized assessment of the reliability of technological systems should reflect the state of
industrial safety, taking into account the risk indicators of all adverse events that may occur at the
hazardous production facility, and based on the results:
• integration of risk indicators of all adverse events (accident scenarios), taking into account
their mutual influence;
• analysis of uncertainty and accuracy of the obtained results;
• analysis of operating conditions compliance with industrial safety requirements and
acceptable risk criteria.</p>
      <p>In modern accidents researching, causation and effect diagrams with a branching structure and
called a “tree” (fault tree, event tree), each of which is a branched, finite and connected graph that
does not have loops or cycles, have become widespread.</p>
      <p>
        To solve the problems of a quantitative evaluation of reliability and safety of complex
technological systems, logical-probabilistic methods, logical-graphic methods [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]: event trees, Fault
Tree Analysis (FTA), topological methods have become the most widespread. The first analysis of the
reliability of complex technological systems, implemented by FTA, was conducted in the ’60s [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
Today, FTA is effectively used in the aerospace, nuclear energy, chemical and processing industries,
pharmaceuticals, petrochemicals, and other high-risk industries [
        <xref ref-type="bibr" rid="ref5 ref6 ref7">5-7</xref>
        ].
      </p>
      <p>
        Despite the extensive coverage in the scientific and technical literature, experts make some
methodological and logical errors in practice, which leads to incorrect results of the technological
systems reliability analysis [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. The urgency of automating the process of technological systems
reliability evaluation is associated with the ever-increasing structural complexity and dimensionality
of modern technical systems and the need to increase the level of reliability and safety of such
systems. Computer systems development and software applications with the function of automatic
construction and calculation of the events occurrence probability allows to increase the speed of
technological system model construction, simplify the Fault Tree (FT) design process, reduce errors
in calculations, get a mechanism for modeling various system states occurrence of adverse events.
Currently, there are a lot of commercial and non-commercial software and platforms that allow
building the FT and performing analysis of the technological systems reliability in automated mode,
such as [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]: OpenFTA, OpenAltaRica platform, ALD Fault Tree Analyzer, DFTCalc, CAFTA, RAM
Commander FTA. In addition to opening and advertising software products, scientists Y. Hiraoka, M.
Takahashi, A. Majdara, T. Wakabayashi [
        <xref ref-type="bibr" rid="ref10 ref11">10,11</xref>
        ] describe corporate software development to assess
the reliability of specific technological systems. The main disadvantage of commercial software is
paying for the purchased license. Free software has some limitations for building a FT, such as
restrictions on the number of initiating events or logical operators, the inability to save or reuse the
created FT, customization for a specific data domain.
      </p>
      <p>The primary purpose of this work is to present the results of modeling, development, and practical
application of non-profit computer system, which provides the ability to design a FT for quantitative
and qualitative analysis of a wide range of technological systems reliability.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Models, methods and technology</title>
      <p>System analysis, including the formulation and decomposition of the problem’s solution, is used to
formalize the process of technological system research, the reliability of which must be evaluated.</p>
      <p>FTA is used to evaluate the system’s reliability, which is one of the main methods of quantifying
the probabilistic component of risk – the frequency of accidents. When constructing a FT, it is
necessary to define the conditions for the appearance of the top event; decompose complex
prerequisites; identify co-operating factors; exclude feedback between elements specify the reasons
for their occurrence; check the validity of all accepted assumptions and initial data. Using the
traceback algorithm allows calculating the probability of events occurrence included in the FT, starting
from the bottom level of the tree. The significance of the events leading to the main undesirable event
is assessed using the Fussell-Vesely algorithm.</p>
      <p>During the computer system design and implementation, the principles of system analysis,
function-oriented method of data domain analysis, data normalization rules, principles of relational
database design are used. The user interface development was carried out, taking into account the
interface’s usability.</p>
      <p>The methods, principles, and algorithms used in the course of the work make it possible to state
that the study results are reasonable and reproducible.
2.1.</p>
    </sec>
    <sec id="sec-3">
      <title>Features of the Fault Tree construction</title>
      <p>5. Graphical representation of the failure tree and calculation of intermediate events and top one
probabilities.</p>
      <p>The main reasons for errors when building a FT are:
• errors of system analysis when describing the composition of the technological system and
the set of process events to be analyzed;
• incorrect use of logical symbols;
• incorrect use of statistics on the initiating events probabilities.</p>
      <p>The following steps of working with the graphic model data of FT are aimed to conduct a
qualitative and quantitative analysis of system reliability.</p>
    </sec>
    <sec id="sec-4">
      <title>2.1.1. Fault tree elements</title>
      <p>The FT elements can be divided into three groups: primary failures or initiating, or basic events
(conditions in which the technical system usually operates); secondary failures (deviations from
process regulations); control failures (equipment does not receive control signals for any reason). A
FT includes one top event connected by logical conditions with those intermediate and initial
prerequisites, the occurrence of some of which can lead to a specific incident.</p>
      <p>
        The graphical display of the FT uses standardized graphic notations, which makes it possible to
clearly define events, logical elements, and types of transmission [
        <xref ref-type="bibr" rid="ref11 ref4">4,11</xref>
        ]. Event symbols allow setting
such events as: “Top Event”, “Intermediate Event”, “Initiating Basic Event”, undeveloped event,
external event. The initiating events do not develop further, and the intermediate events are at the
output of the elements. The logical gates symbols describe the relationship between input and output
events and correspond to classical Boolean logic. Transmission elements are used to connect the
inputs and outputs of the corresponding FT, such as the FT of the subsystem in its system. Table 1
shows the basic graphic notations used to build the FT.
      </p>
      <p>The most commonly used logical elements are AND and OR, but some trees may also use logical
operators such as XOR or NAND. For any event to be further analyzed, first look at all possible
events that are inputs of operation OR, then that are inputs of operation AND. This scheme is applied
to the basic event and all other events whose analysis makes sense to continue.</p>
    </sec>
    <sec id="sec-5">
      <title>2.1.2. Fault tree analysis</title>
      <p>FT can be used for qualitative and quantitative analysis of system reliability. At the qualitative
level, it is used to identify possible causes and ways of failure (final event); at the quantitative level –
to calculate the probability of a final event based on data on the probabilities of causal events.</p>
      <p>Qualitative analysis requires an understanding of the system and the reasons for the failure and a
technical understanding of how the system may fail. When conducting the analysis, it is advisable to
draw up detailed schemes. It is necessary to set basic events BE={BE1,…BEn} and a set of
intermediate events IE={IE1,…IEn}, each of which occurs when a single initiating event or set of
initiating events. Boolean algebra is used to describe the relationships between intermediate and
initiating events. A complex tree has different sets of initiating events, in which an event is reached at
the top; they are called emergency combinations (sections). The minimal cut set is the minor set of
initiating events in which an event occurs at the top. The complete set of minimum emergency
combinations of a tree represents all variants of combinations of events at which there can be an
accident. The minimum trajectory is the smallest group of events in which an accident occurs.
Qualitative analysis of the tree is carried out using the selected minimum emergency combinations
and trajectories; it compares different routes and initial events to the final and identifies critical (most
dangerous) pathways leading to the accident.</p>
      <p>Quantitative analysis of the FT calculates the probability of an accident during a given time on all
possible routes. The calculation of the probabilities of the intermediate and main events, which are
part of the constructed FT, is based on the input statistics of the frequency of occurrence of the
initiating events. The following data are used to determine the frequency of occurrence of initiating
where  – the intensity of the failure event in the technological system, t – the operating time of the
technological system, which determines the intensity of the failure event in the technological system.
statistical data on accidents and reliability of the technological system, the specifics of the
hazardous production facility;
expert assessments by taking into account the opinion of experts in this field;
analysis of accidents in order to determine the required probability.</p>
      <p>The probability of occurrence of events is associated with the intensity of the event by exponential
In the case of⁡ &lt; 0,1 equation (1) turns into:
FT quantitative analysis can be carried out in various ways:
 = 1 − exp⁡(− ),</p>
      <p>
          .
events:
law [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]:
•
•
•
•
•
•
      </p>
      <p>
        prerequisites.
using structural functions (calculated probability polynomials);
step-by-step reduction of the FT using trace-back algorithm;
quantitative assessment of the top event probability using minimal combinations of initial
Using structural functions. In this case the problem is to simplify the relations according to the
rules of event algebra in order to obtain calculated probability polynomials. The prediction of the
probability of a top event is carried out in the following sequence [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]:
      </p>
      <p>The analytical model of the process is decompressed into separate blocks;</p>
      <p>In selected blocks, those subsets of events that are interconnected by conditions AND, OR
and have known probabilities are distinguished;</p>
      <p>For the selected units the probability calculation at the event vertices is performed;
The structural function is simplified by replacing each subset of the property with one
(1)
(2)
(3)
member having an equivalent probability;</p>
      <p>The probability of the occurrence of the FT top event is calculated in a similar way.</p>
      <p>
        Using trace-back algorithm. If the probabilities of all initiating events are known, the trace-back
algorithm to calculate the probabilities of intermediate events and the main undesirable event can be
used. The probability of intermediate events depends on the relationship between the events that lead
to them. The trace-back algorithm calculates the probability of events that are part of the generated FT
by levels, starting from the lowest. N failure tree prerequisites combined by logical condition AND
are replaced by one event with equivalent probability of occurrence  ∩ [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]:
 ∩ =  1 ∙  2⁡ ∙∙∙   =
∏   .
      </p>
      <p>=1
realizing at least one initial event:</p>
      <p>M of the FT initial prerequisites, connected by a logical gate OR, are also replaced by one event,
and its equivalent probability  ∪ is calculated using a formula that estimates the probability of

 =1
 ∪ = 1 − (1 −  1)(1 −  2⁡)∙∙∙ (1 −   )= 1 − ∏(1 −   ),
where Pi – the probability of i-th event occurrence.</p>
      <p>
        Also, the probability of a basic event can be determined based on the minimum cut sets as [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]:
 
 =1
 ( )= 1 − ∏(1 −  (  )).
      </p>
      <p>=1
where Ci(i=1,..,Nc) – is the minimum cut set combination at which a top event occurs.</p>
      <p>
        Using minimal combinations of initial prerequisites. This method consists of constructing another
tree equivalent to the analyzed FT and including all minimal combinations of one type [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. The new
diagram is also a FT and has only one logical condition: AND if only minimum cut set combinations
are used, and OR – when only minimum throughput combinations are used. To calculate the
probability Q of incidents, the following expressions are used:


 min
      </p>
      <p>(Х )

where a ,b – the amount of minimum cut set and minimum throughput combination of the FT, mi, nk,
the number of initial prerequisites in each of its i-th throughput and k-th cut set minimum
combinations of initial events prerequisites.</p>
      <p>
        Importance indicators are used to determine the contribution of each event or their combination to
the occurrence of a system failure. The assessment of the importance of an event is based on the logic
of its association with other FT events. It is advisable to use the Fussell-Vesely algorithm to assess the
importance of the occurrence of a particular event on the occurrence of the main adverse event.
Fussell-Vesely Importance is defined as [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]:
where Pmin cut (Xi) – is the probability of the i-th minimum cut sets leading to the basic event, Q is the
probability of the main undesirable event.
      </p>
    </sec>
    <sec id="sec-6">
      <title>3. Experiment, Results and Discussions</title>
      <p>The analysis of software used to build a FT of complex technological systems made it possible to
form functional and non-functional requirements for system software, main of which are:
1. Client-server data processing, with the ability to save data in a database.</p>
      <p>2. Implementation of mechanisms for forming a description of the technological process or system
in the form of events set with the probabilities of their occurrence.</p>
      <p>3. Implementation of probabilistic modeling software mechanisms with automatic calculation of
events occurrence probabilities in the system and creation of probability function polynomial.
4. Graphical construction of the FT.</p>
      <p>5. Qualitative and quantitative analysis realizing on FT data.
3.1.</p>
    </sec>
    <sec id="sec-7">
      <title>Computing system for automated FTA construction</title>
      <p>The computer system is designed as a desktop application in C # as Windows Form Application,
does not require an Internet connection, interacts with the user through a standardized interface. The
primary functional purpose is the automated design of FT to conduct qualitative and quantitative
analysis of the reliability of technological systems.</p>
      <p>The system architecture is multi-layered, consisting of a data representation layer, a business logic
layer, and a data layer. The scheme of the architecture of the developed computer system is presented
in the Figure 1.</p>
      <p>
        The data layer of the system was designed based on the approach described in [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], which
implements the division of the data layer into three components: normative, operation, and resulting
information. Normative information of the system is conditionally unchanged data, repeatedly used in
data entry and the resulting samples formation. Operation information entered by the user is the
primary source of data describing changes in the state of the data domain. Obtaining the resulting
information is the purpose of the system; it is formed based on the results of queries to the database.
The data storage in this system is a relational database, which stores descriptions of technological
systems, sets of graphic notations, and types of relationships between events to build a FT, sets of
accidents, and the intensity of their occurrence over time.
      </p>
      <p>The business logic layer is designed as a set of software modules:
1. Module for data and descriptions of the technological system input.
2. Module of the FT graphic model construction.
3. Module for calculating and analyzing the data obtained.</p>
      <p>Data processing mechanisms were implemented through stored procedures and representations of
the database level and software application.</p>
      <p>The data representation layer is a user interface developed on the base of the Window – Image –
Menu – Pointer (WIMP) graphics standard as a set of screen forms. All graphic forms meet the
requirements of unification and standardization and implement the same algorithms to build a
dialogue between the user and the software application.
3.2.</p>
    </sec>
    <sec id="sec-8">
      <title>Roles and functions analysis</title>
      <p>The developed computer system is user-dependent, i.e., the reliability of input data describing
basic and intermediate events sets, the establishment of the main undesirable event, the choice of the
logical relationships types of between events, the correctness of initiating events intensity or
probability input is the responsibility of system users. The system validates the input data.</p>
      <p>During the data domain analysis, two roles of computer system users were identified: the operator
and the administrator. The available functions are determined, and the schemes of interaction and
support of work with the system are formed considering each user’s rights to access information. The
system operator is a user-analyst who has sufficient knowledge of the technological system, the
reliability analysis of which will be carried out. Table 2 lists the main functions and available
operations for the system operator.</p>
      <p>A system administrator is a user who has access rights to the information stored in a database. In
addition to the actions described in Table 2, the administrator has the functions of database
management and administration: backup, recovery, data archiving, determination of server connection
characteristics, etc.</p>
      <p>The functions and actions of users are distributed between screen forms to simplify the dialogue of
users with the system, the general scheme of transition between which corresponds to the following
logical sequence:
1. Entering data on the technological system, determining the main adverse event.
2. Form a list of initiating events with data entry on the intensity of their occurrence over time
and entering data of intermediate events that may affect the technological system reliability and
contribute to emergencies.
3. Forming relations between events.
4. Request for automatic construction of the FT and obtaining its graphical model.
5. Request for qualitative and quantitative analysis of the generated FT data.</p>
      <p>In addition to the mainline of dialogue with the computer system to implement all the actions
described in Table 2, child modal forms are used. The results of confirmed data transactions are
displayed in a single relational database.
3.3.</p>
    </sec>
    <sec id="sec-9">
      <title>Data storage</title>
      <p>Data and system logic are shared between the database, user interface, and business rule
algorithms for implementing information operations with data. According to the proposed system
architecture (Figure 1), the normative and operation data are subject to storage in the data storage,
implemented in a relational database. The normative information of the system includes:
• set of graphic notations;
• list of developed projects;
• description of technological systems and a set of events.</p>
      <p>The input information of the system, which has the properties of dynamism and is entered by
operators, is the relationship between events, the intensity of events, the timing of the system, for
which it is necessary to calculate the probabilities. The resulting information is a graphical
representation of the FT, the formed probability polynomial, the set of calculated probabilities of the
base, intermediate and main event, the set of minimum emergency combinations and trajectories. The
resulting information is generated by the system automatically according to the input parameters of
the calculation.</p>
      <p>Database modeling was performed based on the data domain object model with the application of
data normalization rules. The specification of the main objects characteristics stored in the database is
presented in Table 3.</p>
      <p>Inserting data on the “event” entity, the user is given the opportunity to choose which numerical
characteristic will be included in the list of initiating events properties of a particular system: the
intensity of occurrence or probability. If the user enters the intensity, the system automatically
calculates the probabilities of occurrence for the initiating events for (1) – (2). The obtained
probability values are then used to calculate the probabilities of intermediate events and top event
probabilities using (3) – (5).</p>
      <sec id="sec-9-1">
        <title>Entity</title>
      </sec>
      <sec id="sec-9-2">
        <title>Tree event</title>
      </sec>
      <sec id="sec-9-3">
        <title>Project</title>
      </sec>
      <sec id="sec-9-4">
        <title>Relation</title>
      </sec>
      <sec id="sec-9-5">
        <title>Tree</title>
      </sec>
      <sec id="sec-9-6">
        <title>Event type</title>
      </sec>
      <sec id="sec-9-7">
        <title>Graphic notation</title>
      </sec>
      <sec id="sec-9-8">
        <title>A dynamic entity describing the data of each event included in the tree</title>
      </sec>
      <sec id="sec-9-9">
        <title>Static entity describing the main characteristics of a given data domain</title>
      </sec>
      <sec id="sec-9-10">
        <title>A dynamic entity describing data about the type of relationship between tree events</title>
      </sec>
      <sec id="sec-9-11">
        <title>Dynamic entity describing data for system reliability analysis</title>
      </sec>
      <sec id="sec-9-12">
        <title>Static entity</title>
      </sec>
      <sec id="sec-9-13">
        <title>Static entity</title>
      </sec>
      <sec id="sec-9-14">
        <title>The entity is characterized by:</title>
        <p>name, serial number in the tree,
intensity/probability of
occurrence, graphical notation.</p>
      </sec>
      <sec id="sec-9-15">
        <title>Entity, characterized by the</title>
        <p>name of the technological
system, a description of the
main characteristics of the
system.</p>
      </sec>
      <sec id="sec-9-16">
        <title>The entity is characterized by: name, graphic notation, calculation algorithm.</title>
      </sec>
      <sec id="sec-9-17">
        <title>The entity is characterized by the name, the name of the top event, the date, time of creation.</title>
      </sec>
      <sec id="sec-9-18">
        <title>The entity is used to determine the type of event: base, intermediate, main</title>
      </sec>
      <sec id="sec-9-19">
        <title>The entity is used to store and display the type of the project object</title>
      </sec>
      <sec id="sec-9-20">
        <title>Links to</title>
        <p>external
entities</p>
      </sec>
      <sec id="sec-9-21">
        <title>Event</title>
      </sec>
      <sec id="sec-9-22">
        <title>Type</title>
      </sec>
      <sec id="sec-9-23">
        <title>Graphic</title>
        <p>notation</p>
      </sec>
      <sec id="sec-9-24">
        <title>Tree</title>
      </sec>
      <sec id="sec-9-25">
        <title>Event</title>
      </sec>
      <sec id="sec-9-26">
        <title>Graphic notation</title>
      </sec>
      <sec id="sec-9-27">
        <title>Event</title>
      </sec>
      <sec id="sec-9-28">
        <title>Tree</title>
        <p>event</p>
        <p>Relation
plurality
1:1
1:1
1:N
1:N
1:1
1:N
1:1</p>
        <p>The default calculating period is a calendar year. The user can change this value. If necessary, the
user can specify n time calculation periods for which the system will give the results of the probability
calculation. Based on the introduced characteristics and calculated probabilities, the system generates
minimal cut sets and calculates their contribution to the occurrence of the top event according to (7).
Accuracy of probability calculations is 10-5.
3.4.</p>
      </sec>
    </sec>
    <sec id="sec-10">
      <title>Adequacy substantiation</title>
      <p>
        The adequacy of the implemented design solutions was carried out by checking the manually
constructed FTs for different technological systems and the results obtained in the developed system.
The data of technological systems were used as a test set:
1. Conveyor system bulk cargo overload in assessing the main undesirable event, “Destruction
of the conveyor belt”, data on the intensity of the initiating events, and the results of calculating
the probabilities described in the works of A. A. Tverigin.
2. Computer System in estimating the top adverse event “Computer is not functioning” based on
A. Saxena and T. Manglani.
3. Filling system in an automotive production line in assessing the main adverse event “Failure
in the fluid filling system” based on data from H. Soltanali, M. Khojastehpour, J. T. Farinha, J. E.
Pais [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>Testing the developed software on actual data showed the adequacy of the applied methods,
correctness of calculations, and indicators of system reliability. The result of test checks was the
conclusion that the implemented design solutions are universal and can be used to calculate the
reliability of other technological systems.</p>
    </sec>
    <sec id="sec-11">
      <title>4. Practical application</title>
      <p>After substantiating the adequacy of the implemented software solutions, the developed computer
system was used to assess the reliability of the brown smoke suppression system during the release of
steel from the blast furnace in the research work “System analysis and computer modeling of
technological processes and information technologies” conducted by the team of the Department of
Software Systems at Dniprovsky State Technical University. Input data on the technological chain,
equipment composition, the intensity of accidents are taken from actual industrial data of
technological process logs.</p>
      <p>The top event for the analysis and construction of the FT is the emission of brown smoke during
the release of steel from the blast furnace.</p>
      <p>This event is undesirable because, during the interaction of steel with oxygen, iron oxidizes and
partially evaporates, turning into dust, the particles of which rise into the air and form orange (brown)
smoke. Emissions of brown smoke reduce the volume of fused steel by 0.0025-0.0075%, significantly
pollute the environment, and threaten employees.</p>
      <p>The technological system is supplemented by various devices controlled through an automated
control system to minimize the formation of brown smoke – the type of automated workplace shown
in Figure 2.</p>
      <p>The input parameters for building a FT in a given data domain are technological processes set,
technological events, and technological equipment, presented in a hierarchical dependence of system
states and transitions between them.</p>
      <p>The array of input data describing the baseline events was set with the values of the intensity of
occurrence and the period t = 1 year. The set of initiating events BE={BE1,…BE11}, their description
and intensity are given in Table 4.</p>
      <p>The set of intermediate events IE={IE1,…IE8}, the occurrence of which contributes to the
development of the emergency situation consists of 8 events described in Table 5.</p>
      <sec id="sec-11-1">
        <title>There is no electricity</title>
      </sec>
      <sec id="sec-11-2">
        <title>There is no nitrogen pressure</title>
      </sec>
      <sec id="sec-11-3">
        <title>The dome of the tap hole does not fall</title>
      </sec>
      <sec id="sec-11-4">
        <title>The dome of the ladle does not fall</title>
      </sec>
      <sec id="sec-11-5">
        <title>There is no pressure in the network</title>
      </sec>
      <sec id="sec-11-6">
        <title>Closed valve</title>
      </sec>
      <sec id="sec-11-7">
        <title>Pressure sensor failure</title>
      </sec>
      <sec id="sec-11-8">
        <title>Lack of power to the pressure sensor</title>
        <p>After entering the input data, the user is allowed to view the results of the automatic FT design and
analyze the results of automatic calculations. The screen form of the system with the generated tree is
shown in Figure 3. The events B9-B14 on Figure 3 are the same as BE3-BE8 respectively. The events
B15 B16, B17 are the same as BE9, BE10, BE11 respectively.</p>
        <p>The screen form of the resulting information is divided into three parts:
1. The area of the FT graphical representation.
2. The area of the output descriptions of the events entering into the FT;
3. The area of calculated data presentation.</p>
        <p>Standardized graphical elements for events and logical elements are used to increase the visibility
of the displayed FT.</p>
        <p>Each event graphic element contains its sequence number in the event list, displayed in an
additional area of the screen form.</p>
        <p>The top event has the sequence number 0, the base and intermediate events are marked with the
sequence number of their set. There are no restrictions on the number of basic, intermediate events
and logical elements.</p>
        <p>As the size of the FT increases, horizontal and vertical scrolls appear on the screen. The graphic
representation of the tree can be exported as a graphic element.</p>
        <p>The data generated by the system allows for qualitative and quantitative analysis of the generated
FT. The result of the qualitative analysis is the formed set of minimal emergency combinations.</p>
        <p>For the case under consideration, C={C1,..,C6} and is described as:
 1 =  1 ∩  2, (8)</p>
        <p>2 =  3,
 3 =  10 ∪  11,
 4 =  5 =  4 ∪  5 ∪  6 ∪  7 ∪  8 ∪  9,</p>
        <p>6 =  3 ∪  10 ∪  11.</p>
        <p>The probability РТ of the top event occurrence event can be calculated as follow:</p>
        <p>= 1 − [(1 −  1)(1 −  2)(1 −  3)(1 −  4)(1 −  5)(1 −  6)]. (9)
where PС1,..,PС6 is the probability of the i-th minimum emergency combination leading to the top
event. Quantitative analysis of the tree is performed by the system automatically based on (8) - (9).
The results of calculating the probabilities of occurrence of all intermediate events are presented in
Table 6. The probabilities of occurrence of the minimum cut sets, and their weight in the occurrence
of the main event are shown in table 7.</p>
        <p>The estimated probability of occurrence of the main event is 0.40757. Obtained data can be used to
identify potential causes of failure, understand co-occurrence events that lead to system failure,
establish a list of measures to reduce the probabilities of a “brown smoke emission” event, and
increase the reliability of the process as a whole.
5. Сonclusions</p>
        <p>Determining the reliability of technological systems is an important task. It allows identifying
hazardous parts of the technological system and developing measures to minimize adverse events.
One of the ways to quantitatively and qualitatively assess the system’s reliability and the probability
of occurrence of a particular event is FTA, which allows to visually and mathematically describe a
given technological system.</p>
        <p>The developed computer system is a unified software tool for creating FTs and risk analysis of
technological systems. It is not adapted to a specific data domain or a specific process, expertly
dependent at the stage of process description and entering of input parameters of the frequency of
occurrence of events included in the FT.</p>
        <p>The primary purpose of creating a computer system for FT design is to increase the speed of FT
construction, automatic polynomial construction to calculate the probabilities of the intermediate and
main event, increase the accuracy of calculation, minimize the impact of skills and accuracy of
analysts’ calculations. Otherwise, the calculation is performed automatically under the rules for
constructing a probabilistic polynomial, changing the incoming system parameters to analyze risks
and identify the most vulnerable points in the system. Using trace-back algorithm makes it possible to
calculate the probability of FT events occurrence starting from the lowest level. Application of the
Fussell-Vesely algorithm allows evaluating the contribution of each event to the probability of the
main undesirable event occurrence.</p>
        <p>The paper describes main functional requirements for the system, defines the target audience,
functions, and available actions depending on the level of data access rights. The system architecture
is multi-layered, which ensures the logical and functional independence of the layers. The system data
storage is implemented in the form of a relational database that allows storing data on the results of
design and analysis of the FT. Testing of the developed system on real industrial data showed the
adequacy of the applied methods, correctness of calculations and indicators of system reliability. The
practical value of the proposed system is applicability to various data domains, no restrictions on the
size of the studied system, the ability to save and export data.</p>
      </sec>
    </sec>
    <sec id="sec-12">
      <title>6. References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Gabriska</surname>
          </string-name>
          ,
          <article-title>Evaluation of the level of reliability in hazardous technological process</article-title>
          ,
          <source>Applied Sciences</source>
          <volume>11</volume>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>13</lpage>
          . doi:
          <volume>10</volume>
          .3390/app11010134.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Leimeister</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Kolios</surname>
          </string-name>
          ,
          <article-title>A review of reliability-based methods for rosk analysis and their application in the offshore wind industry</article-title>
          ,
          <source>Renewable and Sustainable Energy Reviews</source>
          <volume>91</volume>
          (
          <year>2018</year>
          )
          <fpage>1065</fpage>
          -
          <lpage>1076</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.rser.
          <year>2018</year>
          .
          <volume>04</volume>
          .004.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Wessiani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Yoshio</surname>
          </string-name>
          ,
          <article-title>Failure mode effect analysis and fault tree analysis as a combined methodology in risk management</article-title>
          ,
          <source>in: Proceeding of the International Conference on Industrial and System Engineering</source>
          ,
          <source>IConISE</source>
          <year>2017</year>
          , IOP Publishing Ltd, Denpasar,
          <year>Indonesia 2017</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>11</lpage>
          . doi:
          <volume>10</volume>
          .1088/
          <fpage>1757</fpage>
          -899X/337/1/012033.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>S.</given-names>
            <surname>Kabir</surname>
          </string-name>
          ,
          <article-title>An overview of fault tree analysis and its application in model based dependability analysis</article-title>
          ,
          <source>Expert systems with application 77</source>
          (
          <year>2018</year>
          )
          <fpage>114</fpage>
          -
          <lpage>135</lpage>
          doi: 10.1016/j.eswa.
          <year>2017</year>
          .
          <volume>01</volume>
          .058.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>H.</given-names>
            <surname>Soltanali</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Khojastehpour</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. T.</given-names>
            <surname>Farinha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. E.</given-names>
            <surname>Pais</surname>
          </string-name>
          ,
          <article-title>An integrated fuzzy fault tree model with Bayesian network-based maintenance optimization of complex equipment in automotive manufacturing</article-title>
          ,
          <source>Energies</source>
          <volume>14</volume>
          (
          <year>2021</year>
          )
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          doi: 10.3390/en14227758.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>J.</given-names>
            <surname>Ignac-Nowicka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Krenicky</surname>
          </string-name>
          ,
          <article-title>Fault tree analysis as a tool to increase the level of security in an enterprise</article-title>
          ,
          <source>MAPE</source>
          <volume>1</volume>
          (
          <year>2018</year>
          )
          <fpage>719</fpage>
          -
          <lpage>725</lpage>
          . doi:
          <volume>10</volume>
          .2478/mape-2018-0091.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>N. R.</given-names>
            <surname>Nurwulan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. A.</given-names>
            <surname>Veronica</surname>
          </string-name>
          ,
          <article-title>Implementaion of failure mode and effect analysis and fault tree analysis in paper mill: a case study</article-title>
          ,
          <source>Jurnal Rekayasa Sistem Industri</source>
          <volume>9</volume>
          (
          <year>2020</year>
          )
          <fpage>171</fpage>
          -
          <lpage>176</lpage>
          doi: 10.26593/jrsi.v9i3.
          <volume>4059</volume>
          .
          <fpage>171</fpage>
          -
          <lpage>176</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>G.-J.</given-names>
            <surname>Jiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.-Y.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Qiao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.-X.</given-names>
            <surname>Chen. H.-B. Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.-H.</given-names>
            <surname>Sun</surname>
          </string-name>
          ,
          <article-title>Reliability analysis of dynamic fault tree based on binary decision diagrams for explosive vehicle</article-title>
          , Mathematical Problems in Engineering 2021 1-
          <fpage>13</fpage>
          . doi:
          <volume>10</volume>
          .1155/
          <year>2021</year>
          /5559475.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Baklouti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Nguyen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Choley</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Mhenni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mlika</surname>
          </string-name>
          ,
          <article-title>Free and open source fault tree analysis tools survey</article-title>
          ,
          <source>in: Proceeding of the Annual IEEE International Systems Conference, SysCon</source>
          <year>2017</year>
          , IEEE, Monreal,
          <year>Canada 2017</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          , doi: 10.1109/SYSCON.
          <year>2017</year>
          .
          <volume>7934794</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Hiraoka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Murakami</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Yamamoto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Furukawa</surname>
          </string-name>
          ,
          <article-title>Method of computer-aided fault tree analysis for high-reliable and safety design</article-title>
          ,
          <source>Transactions on Reliability</source>
          <volume>65</volume>
          (
          <year>2016</year>
          )
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          . doi:
          <volume>10</volume>
          .1109/TR.
          <year>2015</year>
          .
          <volume>2513050</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>M.</given-names>
            <surname>Takahashi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Anang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Watanabe</surname>
          </string-name>
          ,
          <article-title>A proposal of fault tree analysis for embedded control software</article-title>
          ,
          <source>Information</source>
          <volume>11</volume>
          (
          <issue>9</issue>
          ) (
          <year>2020</year>
          )
          <fpage>1</fpage>
          -
          <lpage>22</lpage>
          . doi:
          <volume>10</volume>
          .3390/info11090402.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>G. M.</given-names>
            <surname>Chodur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhao</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Biehl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mitrani-Reiser</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Neff</surname>
          </string-name>
          ,
          <article-title>Assessing food system vulnerabilities: a fault tree modelling approach</article-title>
          ,
          <source>Public Health</source>
          <volume>18</volume>
          :
          <fpage>817</fpage>
          (
          <year>2018</year>
          )
          <fpage>1</fpage>
          -
          <lpage>18</lpage>
          . doi:
          <volume>10</volume>
          .1186/s12889-018-5563-x.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Zahrin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. A.</given-names>
            <surname>Sobri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mohamed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. F.</given-names>
            <surname>Mohamed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. O.</given-names>
            <surname>Ismail</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. R.</given-names>
            <surname>Taharin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Hairi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Junid</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Shuaib</surname>
          </string-name>
          ,
          <article-title>Implementation of fault tree analysis (FTA) in manufacruting process: a case study from a wood-based product company</article-title>
          ,
          <source>Journal of critical reviews 7</source>
          (
          <year>2020</year>
          )
          <fpage>3086</fpage>
          -
          <lpage>3096</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>F.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Tan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Gao</surname>
          </string-name>
          ,
          <article-title>Fault tree interval analysis of complex systems based on universal grey operation</article-title>
          ,
          <source>Complexity</source>
          (
          <year>2019</year>
          )
          <fpage>1</fpage>
          -
          <lpage>8</lpage>
          . doi:
          <volume>10</volume>
          .1155/
          <year>2019</year>
          /1046054.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>F.</given-names>
            <surname>Oshiro</surname>
          </string-name>
          ,
          <article-title>Using quantitative fault tree analysis based on methods of cut sets to predict failure, 2021</article-title>
          . URL: https://reliabilityweb.com/articles/entry/using
          <article-title>-quantitative-fault-treeanalysis-based-on-method-of-cut-sets-to-predi</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>А. Saxena</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Manglani</surname>
          </string-name>
          ,
          <article-title>Enhahcing computer system reliability using fault tree analysis</article-title>
          ,
          <source>International Journal of Recent Research and Review</source>
          <volume>6</volume>
          (
          <year>2013</year>
          )
          <fpage>12</fpage>
          -
          <lpage>17</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>K.</given-names>
            <surname>Yalova</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Yashyna</surname>
          </string-name>
          ,
          <source>The 11th IEEE International Conference on Intelligent Data Acquisition and Advanced Computing Systems: Technology and Applications</source>
          ,
          <string-name>
            <surname>IDAACS</surname>
          </string-name>
          <year>2021</year>
          , IEEE, Cracow,
          <year>Poland 2021</year>
          , pp.
          <fpage>774</fpage>
          -
          <lpage>778</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>