PSI - Issue 22

324 Jerzy STANIK et al. / Procedia Structural Integrity 22 (2019) 322–333 "Author name" / Structural Integrity Procedia 00 (2019) 000 – 000 3 An example specification of features for engineering infrastructure may be as follows: 1 – functionality of engineering architecture, 2 - complexity of engineering architecture, 3 – quality and reliability of operation, 4 – technological innovation, 5 – operational efficiency, 6 – business continuity, 7 – functional security, 8 – information security Technical infrastructures are used by various economic entities in various ways, depending on the nature of the operations performed and the type of infrastructure-specific equipment. In systemic terms, engineering infrastructure is comprised of all kinds of system groups (Ciekanowski, Stachowiak, (2011)): = ⋃ ∈ ∥ = { , } ∈ (3) where: – engineering infrastructure in systemic terms (understood as a collection of engineering infrastructure systems), N - a collection of system types numbers emphasized within IT , – a collection of systems of the r-th kind included in the engineering infrastructure, - a set of system numbers in relation to the r-th type, , – the l-th system within the framework of this type. For the use of the risk model to be developed, the set will be decomposed into two system types: = ∪ (4) The set of basic systems comprises of , for example (Kudłowicz, Hołduj, (2015)) : transportation, power engineering, communication and water and sanitation systems, which include: roads, bus stops, railways, stations, river and sea ports, gas network, power grid, drainage, telecommunication facilities, etc. The set of supporting systems includes systems supporting basic systems in order to maintain their basic operating indices, affecting the behavior of acceptable risk levels in relation to individual features of usefulness of the engineering infrastructure. The set of supporting systems includes, among others (Ficoń, 2011) : hazard system, safeguard system, vulnerability system, etc. The subject of further analysis will be the selected, specific IT attribute/parameter, being the engineering infrastructure risk ( ℛ ) , which should be managed throughout the life cycle of the engineering infrastructure, while meeting other features or properties present in the formula (2). Engineering infrastructure risk The risk is usually defined in a descriptive way as a random attribute of decision making. In the risk theory, the qualitative approach dominates, thanks to which the elements of uncertainty and randomness are added to the decision making process. Attempts at quantifying risk are rare. In professional literature, (Adamkiewicz, (2012), Pawełczyk, Sokołowski, (2013)) systemic risk is defined as the product of the probability p of occurrence of a negative phenomenon/result and the negative value or usefulness of this phenomenon/result. The quantitative risk approach is expressed in the form of a product: ℛ = ( ) × ( ) (5) where: ( ) – probability of occurrence of this phenomenon (events, hazards), ( ) - estimated negative effects and consequences of the z-th phenomenon (hazard, result). The analytical risk definition (5), although attractive and very useful within the theory of security, is difficult in practical use in the IT industry, because it requires a prior knowledge of the probability of occurrence of an event and where: – set of basic IT systems, - set of systems supporting basic systems 2.