RU2699682C1 - Automated risk management system - Google Patents

Abstract

FIELD: data processing.

SUBSTANCE: invention relates to data processing means, in particular, to means of managing risks. Automated risk management system comprises a common data bus: a unit for receiving and generating initial data for risk assessment, a distributed access organization unit configured to protect data on risks of editing and deleting, unit for formation and updating of risk registers, pyramid of risks, risk factors, unit for qualitative and quantitative risk assessment, unit for automatic distribution of notifications to participants of risk management process; unit for development and control of risk management actions plans, a unit for automated monitoring and re-evaluation of risks, a unit for automated preparation of reporting on risk management, a unit for documenting and archiving information on the execution of procedures of the risk management process, an information visualization unit, a processor, a unit for permanent storage of data, a unit for temporary storage of data, a power circuit connected to a power supply unit.

EFFECT: technical result consists in improvement of efficiency of risk management process.

1 cl, 6 dwg, 5 tbl

Description

FIELD OF TECHNOLOGY

The technical solution relates to the field of devices or methods of digital computing or data processing, specially designed for specific functions, as well as to the field of computer technology, in particular, to automation in the field of risk management.

BACKGROUND

Risk management occurs when you need to make complex decisions. Risks must be assessed at the stages of product development, when studying the feasibility of making changes, when investigating deviations, for organizing a workspace or when deciding on the possibility of combining the production scheme of different products, etc., that is, where there is a problem of choosing from several options and there are no clear regulatory requirements. Projects implemented in modern practice more and more fall under the classification of "open". This means that it is becoming increasingly difficult to clearly formulate the ultimate goal, to describe the product of the project at the initial stages of its implementation. Understanding and clarity come later, at the stage of implementation and completion of the project. The lack of a clear understanding of which technical solution, at what stage to use, the need to act in a rapidly changing environment, make decisions in the face of incomplete information and uncertainty force us to increasingly use risk management technologies in their activities.

Automation of identification processes and risk response planning significantly improves work efficiency. Talking about a quantitative risk assessment without using modern information technologies simply does not make sense. The range of quantitative analysis techniques is wide: from PERT analysis and what-if analysis to complex Monte Carlo calculations. There are a large number of software packages that support certain risk management processes. However, it is quite difficult to select an integrated risk management system that could provide automation of the entire risk management process, from the creation of a risk management plan to the monitoring of the implementation of the risk response plan.

The prior art knows the technical solution described in RU 2396598 "Automated information and analytical system for managing financial risks", published: 08/10/2010, patent holder: Committee of Finance of St. Petersburg (RU). The document describes a system containing a tool for collecting data on financial obligations, a tool for forming the structure of a portfolio of financial obligations, a tool for processing data on alternative management options, a tool for generating a multidimensional presentation of data, a tool for ranking alternative management options and a data visualization tool. As well as consistently included means for collecting and processing historical data on risk factors and means for generating forecasts of risk factors, means for collecting data on base rates, means for discounting / aging time series and means for analyzing data on financial liabilities.

Also known from the prior art is the technical solution described in RU 2579981 “Automated system for integrated management of resources, risks, reliability of railway transport facilities”, published: 04/10/2016, patent holder: Open Joint-Stock Company “Research and Design Institute of Informatization, automation and communication in railway transport "(RU). The document describes a system containing a central processor, input / output blocks of information, memory, display, analysis of the state of technical objects (TO), analysis of the reliability of TO, assessment of the impact of failure of objects on the transportation process (PP), calculation of residual life and risk indicators, optimization resource allocation, analysis of the implementation of software, decision support to improve the reliability of infrastructure (OI), the formation of reference objects, registration of operating and investment costs, hardware and software software devices for an integrated automated accounting system, monitoring of vehicle failure elimination and analysis of their reliability, a unified corporate automated infrastructure management system, an automated system for maintaining and analyzing the schedule of executed traffic, a unified corporate automated financial and resource management system and a diagnostic system for OI.

Also currently the most famous and used solutions are SAP GRS (Governance, Risk & Compliance) and SAS Risk Management.

But their main limitations and disadvantages, as well as other analogues known from the prior art, are in the complex:

- focus on the management of risks associated with operational or financial activities;

- a complex process of adaptation in the automation of business processes of the organization;

- the lack of the ability to quickly configure the interface for each specific user and add the necessary attributes of the system entities without a long and complicated process of refinement and modification.

ESSENCE OF TECHNICAL SOLUTION

The objective of the claimed technical solution is to eliminate the disadvantages inherent in existing analogues.

The technical result from the use of this technical solution is to increase the efficiency of the risk management process and increase the reliability of the results of the risk management system, as well as to increase the convenience and speed of users.

These main and additional technical results are achieved due to the joint work of the unit for conducting a qualitative and quantitative risk assessment, the development and control unit of risk management action plans, the automated monitoring and re-risk assessment unit, the distributed access organization unit, which is capable of protecting risk data from editing and deleting, information visualization unit, configured to customize the interface for each specific user , add and modify the necessary attributes of system entities.

This technical solution can be made in the form of an automated risk management system containing the following common data bus: unit for receiving and generating initial data for risk assessment; a distributed access organization unit configured to protect risk data from editing and deletion; unit for the formation and updating of risk registers, risk pyramids, risk factors; unit for conducting a qualitative and quantitative risk assessment; block for automatic distribution of notifications to participants in the risk management process; unit for the development and control of risk management action plans; automated monitoring and reassessment unit; Risk management automated reporting unit; unit for documenting and archiving information on the implementation of risk management process procedures; an information visualization unit configured to configure an interface for each specific user, add and change the necessary attributes of system entities; a processor that reads and executes machine instructions (programs) from blocks of permanent data storage, temporary data storage; a permanent data storage unit, which is a permanent storage device; block temporary storage of data, which is a random access memory device that provides temporary storage of data; power circuit connected to the power supply.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 - project life cycle in an automated risk management system;

FIG. 2 - life cycle of a control event in an automated risk management system;

FIG. 3-classification of risks in an automated risk management system;

FIG. 4 - life cycle of a risk factor of 1, 2, 3 levels in an automated risk management system;

FIG. 5 - life cycle of a compensating measure for risk factor management in an automated risk management system;

FIG. 6 is an example of information visualization in an automated risk management system.

DETAILED DESCRIPTION OF THE TECHNICAL SOLUTION

Below we will consider some terms that will be used later in the description of the technical solution.

Risks - risk in project activities means a probable event, as a result of which the decision maker loses the opportunity to achieve the planned results of the project or its individual parameters having a temporary, quantitative and cost estimate. The risk is characterized by certain sources or causes and has consequences, i.e. affects the results of the project.

ACS (automated control system) is a man-machine control system that provides automated collection and processing of information necessary to optimize the management of a technological object in accordance with the accepted criterion. The automated control system is designed to develop and implement control actions on the technological control object, in other words, they are intended to ensure the effective functioning of the control object by the automated execution of control functions.

The user interface, it is the user interface (UI - English user interface) - an interface that provides information transfer between the human user and the hardware and software components of a computer system (ISO / IEC / IEEE 24765-2010).

Usability (from the English. Usability - “usability, degree of usability”), also usability, usability, ergonomics - the ability of the product to be understood, studied, used and attractive to the user under specified conditions (ISO / IEC 25010); a property of a system, product or service, in the presence of which a specific user can operate the system in certain conditions to achieve established goals with the necessary effectiveness, efficiency and satisfaction (ISO 9241-210).

Entity Attributes — An entity can be defined as an object, event, or concept about which information should be stored. Entities must have a name with a clear meaning, in fact this is the name of its instance. Each copy is individual and must be different from all other copies. An attribute expresses a specific property of an object.

In this technical solution, the technical result, consisting in increasing the efficiency of the risk management process and increasing the reliability of the results of the risk management system, as well as improving the convenience and speed of users, is achieved through the joint work of the unit for conducting a qualitative and quantitative risk assessment, development and control unit risk management action plans, automated monitoring and re-risk assessment unit, distributed access organization unit, ying with data protection at risk from editing and deletion of information visualization unit configured to customize the interface for each user, add and modify the necessary attributes of the entities of the system.

This technical solution can be made in the form of an automated risk management system containing the following common data bus: unit for receiving and generating initial data for risk assessment; a distributed access organization unit configured to protect risk data from editing and deletion; unit for the formation and updating of risk registers, risk pyramids, risk factors; unit for conducting a qualitative and quantitative risk assessment; block for automatic distribution of notifications to participants in the risk management process; unit for the development and control of risk management action plans; automated monitoring and reassessment unit; Risk management automated reporting unit; unit for documenting and archiving information on the implementation of risk management process procedures; an information visualization unit configured to configure an interface for each specific user, add and change the necessary attributes of system entities; a processor that reads and executes machine instructions (programs) from blocks of permanent data storage, temporary data storage; a permanent data storage unit, which is a permanent storage device; block temporary storage of data, which is a random access memory device that provides temporary storage of data; power circuit connected to the power supply.

As a means of exchanging information between units in this technical solution, a computer data exchange bus can be used.

The blocks used in this technical solution can be implemented using electronic components used to create digital integrated circuits. Not limited to, can be used microcircuits, the logic of which is determined during manufacture, or programmable logic integrated circuits (FPGA), the logic of which is set by programming. For programming, programmers and debugging environments are used that allow you to specify the desired structure of a digital device in the form of a circuit diagram or programs in special equipment description languages: Verilog, VHDL, AHDL, etc. Alternative FPGAs are: programmable logic controllers (PLCs), base matrix crystals ( BMK) requiring a factory production process for programming; ASIC - specialized custom large integrated circuits (LSI), which are much more expensive in small-scale and single-unit production.

Blocks can also be implemented using read-only memory devices (see O. Lebedev. Memory microcircuits and their application. - M.: Radio and communications, 1990. - 160 s; Large integrated circuits of memory devices: Reference / A.Yu. Gordenov et al. - M.: Radio and Communications, 1990. - 288 p.).

Thus, the implementation of all used blocks is achieved by standard means based on the classical principles of implementing the foundations of computer technology.

Block for receiving and generating initial data for risk assessment.

The initial data can be information on risks entered, downloaded and processed as necessary in a specific data structure. At the same time, data can be downloaded from external information systems to the block in an already pre-structured form, as well as unstructured data for post-processing in this block and the formation of initial data for subsequent risk assessment.

As an example of the implementation of the described technical solution, we give a description of the data structure and the users working in it: the project is the root entity for consolidating risk information. The project contains information on control events. A set of risks and their factors of various levels (risk factors), in turn, are assigned to control events. A project can be created both for a specific object (for example, Ruppur NPP), and with an abstract task, for example, “General risks”.

In the context of the project, in the graphical user interface, you can view all the tasks of the project (control events), all risks with factors (risk factors) of the project

The project as an attribute of the entity has a list of experts who have the right to assess risks.

A project as an attribute of an entity has the property “project manager”.

The project life cycle in the described technical solution is depicted in FIG. one.

After creating a project, it is assigned the status of “Draft”. The project is transferred to the Active status automatically or by the project coordinator after the appointment of experts for the project and their coordination with the project manager. In the “Active” status, the system allows you to change the appointment of experts.

The attributive structure of the project is presented in Table 1:

Table 1

Control events (hereinafter - CS) are important milestones of the project and are the basis for the management and systematization of risks. Control events relate to the project and are selected by the coordinator and agreed with the project manager. Monitoring events can be downloaded from third-party systems, for example: from project planning application software, such as Primavera, by uploading the entire schedule and providing an interface in the system for filter selection and linking monitoring events to the project. It is also possible to create a control event manually in the described technical solution. The attributive composition of a control event may vary for different types of control events. The binding of risk factors to the control event occurs automatically, after the experts have assessed the risk pyramid (by assessing the factors), sent to them in conjunction with the control event. In order to optimize the work of experts, it is possible to limit the visibility of risk factors from the pyramid to them, depending on the filter created.

The attributive structure of the control event (for different types of control events) is presented in Table 2:

table 2

The life cycle of a control event in the described technical solution is depicted in FIG. 2.

Distributed access organization unit, configured to protect risk data from editing and deletion. After the creation of the project (the root entity for consolidating risk information), access rights for various roles are automatically assigned to the project scope and the data inherent to it, according to the role matrix used, which in a particular embodiment of the technical solution is a list of users of the system indicating their rights access to editing and visibility of certain entities and their attributes in the described automated risk management system. This allows you to increase the reliability of the results of the risk management system.

At the same time, the visibility and access to change the entities and their attributes described in this technical solution can be changed and specified separately.

The unit of formation and updating of risk registers, risk pyramids, risk factors.

In this block, the basic entities of the described technical solution are formed on the basis of the accepted and generated initial data for the subsequent risk assessment.

As an example of the implementation of the technical solution, we give a description of these entities.

The risk register refers either to the project or to the control event. A risk register is a set of key risk factors.

The risk pyramid is the main category to which the classification of risks (categories, risks, factors) belongs. Has the “Code” property - this is a unique digital designation of the pyramid. This property is generated in order, starting with 1. In the future, subordinate risk categories that are created in the pyramid, in turn, receive a “Code” depending on the parent pyramid. For example, 1.2, 2.4 (the first digit is the pyramid code, the second is the category code).

Affiliation - one pyramid per project. In this technical solution, it is possible to separately send users the selected category from the risk pyramid to carry out actions with risk factors and when they add new factors so that they immediately become attached to this category.

This technical solution also implements the procedure for copying the existing pyramid of risks to a new project, i.e. transfer of all pyramid objects to the new pyramid, with the change of the pyramid number in the "Pyramid ID" field.

This technical solution also implements the procedure for transferring risk factors to another branch of the pyramid with changing the value of the attribute “ID in the pyramid”.

Risk factors in this technical solution have an additional attribute “Type”, which is selected from the values: Investproject, Business Plan, Budget, PFD, Corporate Risks. All risks (with factors) for the project are carried out in a single pyramid, and, depending on the value of the “Type” attribute, LC schemes of risk factors are the same for different types, have differences in additional attributes. Risk factors, depending on the level, receive their code 1.2.1, 2.4.4. The first digit is the pyramid code, the second is the category code, the third is the risk code, the fourth is the risk level 1 factor code, the fifth is the risk level 2 factor code (if any) and the sixth is the level 3 factor code (if any).

The final code format will be, for example, 1.2.1.1.1.1. This code belongs to a level 3 risk factor. Code, for example, 1.2.1 must belong to risk. Users evaluate the lowest level of the pyramid, which may vary depending on the branch (this may be a factor of 1, 2, 3 levels depending on the nesting in a particular branch).

The attributive composition of the risk pyramid is presented in Table 3:

Table 3

A risk pyramid category is a classification category that includes risks along with its factors.

The category of risk pyramid is at the second level of the hierarchy (at the first - the pyramid); the entire classifier of the risk pyramid has a tree structure; the last level is a risk factor of 1 or 2 or 3 levels, depending on its presence in this branch of the pyramid. An example of a risk classification is shown in FIG. 3.

The category of the risk pyramid has the following attributive structure, shown in Table 4:

Table 4

A risk template is an entity with which the main work of users takes place and which is at risk of a risk pyramid and is essentially a template of a risk factor of 1, 2, 3 levels (a risk factor associated with the risk template that is at the very end when the pyramid branch is opened risks).

From risk templates, instances of risk factors 1, 2, 3 of the level for the control event are created;

The risk template has a relationship with all instances of risk factors of levels 1, 2, 3, therefore, the template allows you to track the entire history of risk factors 1, 2, 3 (in which projects you participated, which had assessments, etc.)

Risk - reference information that refers to a risk template. Information about the risk, as well as other elements of the hierarchical structure over the estimated risk factor 1, 2, 3 of the level should be available to the user for the correct assessment of this risk factor.

A risk factor of 1, 2, 3 levels (or an instance of a factor of 1, 2, 3 risk levels) is an entity created from a risk template in the risk pyramid. In the absence of a risk factor of 1, 2, 3 levels in the risk pyramid, the user at the stage of a qualitative assessment has the opportunity to add a risk factor of 1, 2, 3 levels and he will automatically be attached to the section “Additional risks not included in the risk pyramid” for the investment project, according to Programs (budget, business plan, VFD) are automatically assigned to the sections (Risks of the budget of the current year, Risks of the business plan, Risks of VFD).

There are newly emerging risk factors that have already been realized, they are added by the project coordinator and immediately marked as a “key risk factor” and supplemented with already known information with the appointment of experts, the owner, who enters an action plan to minimize the consequences.

Risk factor 1, 2, 3 of the level has advanced attributes with many related objects.

Risk factor 1, 2, 3 of the level refers directly to the control event.

Risk factor 1, 2, 3 of the level has its life cycle depicted in FIG. four.

The unit for conducting a qualitative and quantitative risk assessment is made with the ability to conduct an initial assessment, ranking of risk factors and identifying key factors from the ranked risk factors. Key risk factors are ranked and, if necessary, adjustments and additions or deletions of key risk factors are made. For all operations with risk factors, the lowest factors of each node are taken. Moreover, a risk factor of level 1 should be evaluated if there are no factors of levels 2 and 3 to this risk. Level 2 risk factor is assessed in the absence of level 3 factors for this risk. Level 3 risk factor is assessed if available. In this case, factors of only one lowest level at each risk are evaluated.

In a particular embodiment of the described technical solution, qualitative assessments of risk factors are a set of assessments from experts belonging to a risk factor. Each expert puts down his assessment of probability and exposure. Next, the significance of risk (the product of probability and exposure) is automatically calculated. All expert estimates are summed up and the average value is calculated. This value is subsequently involved in the assessment of the risk factor.

Experts evaluate risk factors, then rank them by importance, then select key factors from the most significant. The assignment of key risk factors is agreed upon and, if necessary, adjustments and additions or additions of key risk factors are made. Then a quantitative assessment of the risk factors is given.

Risk factor life cycle:

- Primary;

- Revaluation;

- Archive.

The risk information always displays the initial rating and the last revaluation. At each subsequent reassessment of the risk factor, all previous reassessments are sent to the “Archive”. Newly created estimates will exist in the "Revaluation" status. Archival ratings can be viewed in the ratings filter.

The automatic notification blocking participants of the risk management process is configured to support the mechanism of notifying users via e-mail and other means of remotely sending electronic messages and notifications. For example, users are automatically notified when an object passes through various stages of the life cycle with the ability to dynamically add notifications if an entity is transferred to a specific stage in the life cycle.

Notifications are also automatically sent when executors receive a task about a task. The task executor is automatically reminded by e-mail about the approaching deadline for the task and the delay in completing the assigned task. At the same time, the message contains a link, when opened, a window opens in the system with the assigned work area (project, control event, “Type” attribute of the risk factor with an additional indication of the project or control event).

The development and control unit of risk management action plans is made with the possibility of supporting the development and monitoring of the implementation of compensatory measures and action plans in case of implementation of the risk factor.

Compensatory measures (hereinafter - KM) or risk management measures relate directly to the risk factor. Compensatory measures may be updated over time and may have a harmonization process.

The attributive composition of the risk factor management measure (and the additional measure) is presented in Table 5:

Table 5

The life cycle of a compensating risk factor management (CM) measure is shown in FIG. 5.

A compensating event begins with its planning. In a particular embodiment of this technical solution, planning is carried out by the owner of the key risk factor. Then, the object is placed on hold by the contractor for the implementation of the event. When the deadline approaches the planned start of the CM implementation (for 7 days and on the day the implementation starts), the system sends notifications to the owner of the risk factor about the approaching deadline for the implementation of the CM or if the start date for the implementation is overdue - a notice of its delay. After implementation, the compensating event can be transferred to the “Coordination of Implementation” status for approval by the project coordinator of the fact of the implementation of the CM and, subject to approval by the CM, the project’s curator will be transferred to the status of “Completed” (the actual deadline will be set - the date the compensation event is transferred to the status of “Completed ”And the attributes responsible for the implementation of the compensating event are filled in), or the event is transferred to the status of“ Failed ”or the status of“ Canceled ”. The owner of the risk factor can set the status “Pending implementation”, “Implementation”, “Coordination of implementation”, “Not completed”.

The action plan refers directly to the risk factor and is a plan of measures aimed at reducing the consequences of the realized key risk factor and can be updated over time.

The automated monitoring and re-risk assessment unit is configured to automatically restart the procedure for conducting a qualitative and quantitative risk assessment upon receipt of new source data for risk assessment. This functionality can be activated according to the schedule with a specified frequency, and manually, which allows to increase the effectiveness of the risk management process and the reliability of the results of the risk management system.

The automated reporting unit for risk management is configured to generate, transmit for display, upload and send reports outside the system in the form of files in the required format according to a predetermined schedule, as well as arbitrarily. When information is displayed in reports on risk factors, the report includes information on all attributes of risk factors. When generating reports for a certain period, it is possible to select the start and end dates of the period. Unless otherwise specified, all relevant risks (having any status except “archive ...”) fall into the sample of risk factors.

As an example of the actual implementation of the described technical solution, we give examples of reports that are generated by the automated reporting unit for risk management:

1) A selection of risk factors for domestic, foreign projects.

It provides for the unloading of risk factors with all attributes separately for a group of projects related to domestic and separately for a group of projects related to foreign ones, previously providing the user with the opportunity to select projects of both types from the entire list of projects.

2) A selection of risk factors for a certain period.

Actual risk factors are limited by the date range selected by the user. At the same time, all risk factors relevant to the selected range are selected (whose CS fall into the selected period). In addition, it is necessary to provide for the possibility of choosing both all projects, and certain ones.

3) A sample of the realized project risk factors for the period.

Actual risk factors whose CS fell into the selected date range and the attribute “realized / not realized” for these factors takes the value “Yes” (risk factor realized in the project).

4) A sample of unrealized risk factors for the period.

Actual risk factors whose CS fell into the selected date range and the attribute “realized / not realized” for these factors takes the value “No” (the risk factor that was not implemented in the project).

5) A selection of risk factors for unfulfilled compensatory measures.

Actual risk factors whose CS fall into the selected date range and these factors have at least 1 unfulfilled CM (in the status of "Not completed") or expired.

6) A selection of risk factors by risk owners.

Actual risk factors whose CS fell into the selected range with the addition of the field “Status of completion of the CM”, which takes the value “Not met”, if at least 1 included in the risk factor of the CM.

7) A selection of risk factors by risk categories.

Actual risk factors whose CS fall into the selected date range and the category attribute of these factors takes the value of the category value previously selected by the user.

8) A sample of risk factors for 4 archives (reflected in the LC scheme of the risk factor).

Actual risk factors whose CS fell into the selected date range and the status of these factors has the meaning of “archive ...”.

9) A selection of risk factors for the control event from different projects.

Actual risk factors whose CS fall into the selected date range and the attribute “Control Event” for these factors takes on the value previously selected by the user.

10) Report on compensatory measures.

Conclusion of all compensating events (with all their attributes and status) according to the actual risk factors, whose COP fell into the selected date range.

11) Report on budget risks.

Actual risk factors whose CS fall into the selected date range and the attribute of these factors “Type” takes the value “Budget”.

12) Risk report of the business plan.

Actual risk factors whose CS fall into the selected date range and the attribute of these factors “Type” takes the value “Business Plan”.

The unit for documenting and archiving information on the implementation of the procedures of the risk management process is made with the ability to isolate, process, save and transmit for display, information on any changes that occur with objects, entities and their attributes used in the described automated risk management system, at all stages of their life cycle.

The information visualization unit, configured to customize the interface for each specific user, add and change the necessary attributes of system entities.

The block is implemented with the ability to display information in a graphical and tabular presentation (example in Fig. 6), while the user has the ability to customize the interface (change the column width, display columns, etc.), which significantly increases the usability of the described technical solution, then it improves the user experience in the described automated risk management system. Moreover, in this technical solution, if there are certain access rights (see the distributed access organization block, configured to protect risk data from editing and deleting), the functionality for quickly adding and changing the necessary attributes of an entity is implemented. For example, in a particular embodiment of this technical solution, this possibility is as follows - the user has the ability to add the necessary additional fields for entering information to system objects using the graphical interface and built-in tools without stopping the system and not rebooting the system. This allows you to significantly increase the speed of users in the described automated risk management system.

In a particular embodiment of this technical solution, the ability to customize the interface and quickly add and change the necessary attributes of an entity are implemented by the native drag-and-drop functionality developed using HTML5.

The power supply unit described in the technical solution may be an electronic device that provides the conversion of alternating electric current to direct, with the parameters necessary to power the other elements of the described technical solution.

The processor can be an electronic unit or an integrated circuit (microprocessor) that executes machine instructions (programs), it reads and executes machine instructions (programs) from blocks for permanent data storage, temporary data storage.

The permanent data storage unit can be a ROM (read only memory), flash memory, hard disks (HDD), solid state drives (SSD), optical drives.

The temporary data storage unit is RAM - random access memory that provides temporary data storage.

To a person skilled in the art, it is obvious that specific embodiments of an automated risk management system have been described here for purposes of illustration, various modifications are permissible without departing from the scope and essence of the technical solution.

Claims (1)

An automated risk management system containing data shared by a common bus: unit for receiving and generating initial data for risk assessment; a distributed access organization unit configured to protect risk data from editing and deletion; unit for the formation and updating of risk registers, risk pyramids, risk factors; unit for conducting a qualitative and quantitative risk assessment; block for automatic distribution of notifications to participants in the risk management process; unit for the development and control of risk management action plans; automated monitoring and reassessment unit; Risk management automated reporting unit; unit for documenting and archiving information on the implementation of risk management process procedures; an information visualization unit configured to configure an interface for each specific user, add and change the necessary attributes of system entities; a processor that reads and executes machine instructions (programs) from blocks of permanent data storage, temporary data storage; a permanent data storage unit, which is a permanent storage device; block temporary storage of data, which is a random access memory device that provides temporary storage of data; power circuit connected to the power supply.

Images