Risk data display method and system

Abstract

The application relates to a risk data display method and system, and belongs to the field of process safety risk analysis. The risk data display method comprises the following steps: providing a cause display interface, obtaining accident cause data through the cause display interface; providing an influence analysis interface, obtaining equipment node data through the influence analysis interface; in response to receiving a first trigger operation and the equipment node data meeting a preset condition, providing a result display interface, obtaining accident result data through the result display interface; according to the association relationship among the cause display interface, the influence analysis interface and the result display interface, storing the accident cause data, the equipment node data and the accident result data in the form of an accident link in a database; and according to a search instruction, obtaining a target accident link from the database and displaying the target accident link.

Description

Risk data display methods and systems Technical Field

[0001] This application relates to the field of process safety risk analysis, and in particular to a risk data display method and system. Background Technology

[0002] In industrial production, technological processes directly affect product quality, efficiency, and personnel safety. Therefore, analyzing the risks inherent in these processes is of paramount importance. Process risk analysis involves assessing and analyzing the causes and potential consequences that might lead to equipment deviating from its normal operating state during a process, and implementing protective measures to effectively control or reduce potential risks.

[0003] Traditional risk analysis mainly uses Excel to display all the data in a flat manner, which hides the logical relationship between the causes and consequences of potential risks in the data and makes them difficult to discover.

[0004] Existing technologies cannot intuitively represent the logical relationships between accidents in the process, which is not conducive to the analysis of accident results, thus leading to poor risk analysis. Summary of the Invention

[0005] This application provides a risk data display method and system to at least address the problem of unintuitive logical relationships between accidents in related technologies.

[0006] In a first aspect, embodiments of this application provide a risk data display method, including:

[0007] Provide a cause display interface, through which accident cause data can be obtained;

[0008] Provides an impact analysis interface to obtain device node data;

[0009] In response to receiving a first trigger operation and the device node data meeting preset conditions, a result display interface is provided, and accident result data is obtained through the result display interface;

[0010] Based on the relationship between the cause display interface, the impact analysis interface, and the result display interface, the accident cause data, equipment node data, and accident result data are stored in the database in the form of an accident chain.

[0011] The target incident link is retrieved from the database according to the search command and displayed.

[0012] In one embodiment, the device node data includes the secondary node types of the current node, and the provision of an impact analysis interface for obtaining device node data includes:

[0013] A first impact analysis interface is provided, through which first device node data is obtained;

[0014] In response to the fact that the secondary node type of the first device does not meet the preset conditions, a second impact analysis interface is provided, which is used to obtain the secondary device node data of the first device.

[0015] In one embodiment, the second impact analysis interface is configured to be displayed with an indentation relative to the first impact analysis interface; and / or

[0016] The results display interface is configured to be displayed indented relative to the impact analysis interface.

[0017] In one embodiment, the device node data includes protective measure data; the accident cause data includes a first probability level characterizing the probability of the accident occurring; the accident result data includes a severity level and a risk level; and obtaining the accident result data through the result display interface includes:

[0018] Based on the protective measures data, the first probability level is revised to obtain the second probability level in the result data;

[0019] The risk level is determined by querying a preset risk assessment matrix based on the second probability level and the severity level.

[0020] In one embodiment, revising the first probability level based on the protective measure data to obtain a second probability level in the result data includes:

[0021] Based on the preset filtering rules, effective protection data is determined according to the protection measures data;

[0022] The first probability level is revised based on the effective protection data to obtain a second probability level in the result data.

[0023] In one embodiment, the protective measure data includes protective measure type and protective measure reduction coefficient, and the step of determining effective protective data from the protective measure data according to a preset screening rule includes:

[0024] For each protective measure data acquired, determine whether the number of protective measures of the same type as the current protective measure is less than or equal to the first threshold.

[0025] If so, determine whether the effective protection data is less than or equal to the second threshold. In response to the effective protection data being less than or equal to the second threshold, calculate the protection measure reduction value based on the protection measure reduction coefficient, and update the effective protection data based on the protection measure reduction value.

[0026] In one embodiment, retrieving and displaying the target incident link from the database according to a search instruction includes:

[0027] The search key information is obtained according to the search instruction, and the target accident link is determined in the database using the search key information as an index.

[0028] The target display method is determined based on the risk level of the target accident link, and the accident link image is displayed in the target display method.

[0029] In one embodiment, obtaining key search information according to the search specification and determining the target incident link in the database using the key search information as an index includes:

[0030] The first and second accident links are determined based on the key search information.

[0031] The target accident link is obtained by merging identical data from the first and second accident links.

[0032] In one embodiment, determining the target display method based on the risk level of the target accident link includes:

[0033] Determine the line colors in the accident link image based on the risk level; and / or

[0034] The initial line width of the accident cause image is determined based on the first probability level in the accident cause data;

[0035] According to the preset calculation rules, the linewidth of each device node in the accident link image is obtained based on the reduction value of the protection measures and the initial linewidth.

[0036] Secondly, embodiments of this application provide a risk data display system, including:

[0037] Cause module: Used to provide a cause display interface, through which accident cause data can be obtained;

[0038] Impact module: Provides an impact analysis interface to obtain device node data.

[0039] Results module: In response to receiving a first trigger operation and the device node data meeting preset conditions, it provides a results display interface and obtains accident result data through the results display interface;

[0040] Storage module: Used to store the accident cause data, equipment node data, and accident result data in the database in the form of an accident chain, according to the hierarchical relationship of the cause display interface, impact analysis interface, and result display interface;

[0041] Display module: used to retrieve and display the target accident link from the database according to the search command.

[0042] The risk data display method and system provided in this application have at least the following technical effects.

[0043] This application visually demonstrates the chain-like logic between accidents by displaying the accident chain relationships in the cause analysis interface, impact analysis interface, and result display interface during the analysis process. By storing the accident chain in the database using a chain-like storage structure, it is possible to trace back all upstream nodes and the complete chain in which the current node belongs from any node. This facilitates the automatic data retrieval during subsequent analysis, achieving automated analysis. It clearly and intuitively displays the chain-like logical relationship between the causes, impacts, and results of accidents during the accident analysis process, facilitating accident analysis and effectively improving the results of risk analysis.

[0044] Details of one or more embodiments of this application are set forth in the following drawings and description to make other features, objects and advantages of this application more readily apparent. Attached Figure Description

[0045] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0046] Figure 1 is a flowchart illustrating a risk data display method according to an exemplary embodiment;

[0047] Figure 2 is a schematic diagram of a risk analysis interface according to an exemplary embodiment;

[0048] Figure 3 is a flowchart illustrating risk level calculation according to an exemplary embodiment;

[0049] Figure 4 is a diagram of a chain data structure according to an exemplary embodiment;

[0050] Figure 5 is a schematic diagram of an accident link according to an exemplary embodiment;

[0051] Figure 6 is a block diagram of a risk data display system provided according to an exemplary embodiment. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this application clearer, the application is described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application.

[0053] Obviously, the accompanying drawings described below are merely some examples or embodiments of this application. Those skilled in the art can apply this application to other similar scenarios based on these drawings without any inventive effort. Furthermore, it is understood that although the efforts made in this development process may be complex and lengthy, for those skilled in the art related to the content disclosed in this application, any changes to design, manufacturing, or production based on the technical content disclosed in this application are merely conventional technical means and should not be construed as insufficient disclosure of the content of this application.

[0054] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment that is mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0055] Unless otherwise defined, the technical or scientific terms used in this application shall have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms “a,” “an,” “an,” “the,” and similar words used in this application do not indicate quantity limitation and may indicate singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units not listed, or may include other steps or units inherent to these processes, methods, products, or devices. The terms “connected,” “linked,” “coupled,” and similar words used in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. “Multiple” used in this application refers to two or more. “And / or” describes the relationship between related objects, indicating that three relationships may exist; for example, “A and / or B” can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following objects are in an "or" relationship. The terms "first," "second," and "third" used in this application are merely to distinguish similar objects and do not represent a specific ordering of the objects.

[0056] First aspect

[0057] This application provides a method for displaying risk data.

[0058] Figure 1 is a flowchart illustrating a risk data display method according to an exemplary embodiment, and Figure 2 is a schematic diagram illustrating a risk analysis interface according to an exemplary embodiment. As shown in Figure 1, the method includes:

[0059] Step S101: Provide a cause display interface and obtain accident cause data through the cause display interface.

[0060] Optionally, the cause display interface is generated based on pre-added device names and deviation names. Accident cause data includes a cause description, cause type, tag number, and the likelihood level of the accident. The cause accident data is obtained by professionals analyzing existing or potential faults in the device nodes. The tag number is used to identify the device or its components.

[0061] Optionally, before executing step S101, the method further includes adding data such as equipment nodes, deviation information, and protective measure information. The equipment node information includes parameters such as equipment name, equipment type, equipment description, tag number, contained materials, and the next equipment node. The equipment name represents the specific name and model of the current equipment, the equipment type represents the current equipment's application category, and the equipment description represents the equipment's remarks. Deviation information corresponds to the fault that occurred in the equipment node, and includes parameters such as deviation name, deviation parameters, and operating range. Protective measure information includes parameters such as protective measure description, protective measure type, protective measure reduction factor, the equipment to which the protective measure is applied, and the protective measure tag number. The protective measure tag number indicates that the protective measure is used on the equipment or equipment component corresponding to the current tag number.

[0062] Regarding the implementation of the cause display interface, refer to Figure 2. The cause display interface 10 includes a cause description, cause type, tag number, and probability level of the incident. Optionally, the cause description and tag number information are obtained through user input, while the cause type and probability level of the incident are obtained through a drop-down menu selection.

[0063] Referring again to Figure 1, step S102 is executed after step S101.

[0064] Step S102: Provide an impact analysis interface to obtain device node data.

[0065] Optionally, the number of impact analysis interfaces is at least one. Equipment node data includes impact information, protective measure information, and recommended measure information. Impact information includes the current equipment node, deviations caused by equipment node failure, impacts, materials, and secondary node types. Secondary nodes are nodes affected by the deviation of the current equipment node. Protective measure types include protective measure description, protective measure type, protective measure reduction factor, and protective measure tag number.

[0066] Regarding the implementation of the impact analysis interface: Referring to Figure 2, deviation information and the next device in the impact analysis interface 20 are obtained through drop-down menu selection; impact description information and material information are obtained through user input. Adding protective measures and suggested measures involves selecting existing measures or creating new measures.

[0067] In one example, the device node data includes a secondary node type, and step S102 includes:

[0068] Step S1021: Provide a first impact analysis interface and obtain the first device node data through the first impact analysis interface.

[0069] In step S1022, in response to the second trigger operation and the fact that the secondary node type of the first device does not meet the preset conditions, a second impact analysis interface is provided. The second impact analysis interface is used to obtain the secondary device node data of the first device.

[0070] Optionally, the second triggering operation is a page addition operation, and the number of impact analysis interfaces is at least one. Secondary node types include the model or name of the secondary node device, the current node having no impact on the secondary node, and the secondary node being an external environment. Preset conditions include the current node having no impact on the secondary node and the secondary node being an external environment.

[0071] In one example, the second impact analysis interface is configured to be indented relative to the first impact analysis interface. Referring to Figure 2, in this case, the first impact analysis interface is the parent interface of the second impact analysis interface, and the second impact analysis interface is a child interface of the first impact analysis interface. This embodiment uses the indentation relationship between the impact analysis interfaces corresponding to each step of the accident analysis process to reflect the chain relationship of the accident chain, thus more intuitively demonstrating the chain logic between accidents.

[0072] Referring again to Figure 1, step S103 is executed after step S102.

[0073] Step S103: In response to receiving the first trigger operation and the device node data meeting the preset conditions, a result display interface is provided, and the accident result data is obtained through the result display interface.

[0074] Optionally, the first triggering operation is an interface addition operation. Accident result data is obtained through analysis by professionals and input into the result display interface. Optionally, the result display data includes consequence type, consequence description, related materials, and risk data. Risk data includes the severity of the accident, initial probability level, residual probability level, and risk level. The initial probability level is the probability level of the accident's occurrence obtained from the cause display interface, and the residual probability level is the probability level of the accident's occurrence after adding effective protective measures.

[0075] Regarding the implementation of the impact analysis interface, please refer to Figure 2. The results display interface 30 provides input boxes for receiving result data. The consequence type and the severity of the accident are obtained through drop-down menu selection; the consequence description information and material information are obtained through user input; the probability level and risk level of the accident are automatically filled and displayed after being calculated by calculation rules.

[0076] In one example, the results display interface is configured to be indented relative to the impact analysis interface. Referring to Figure 2, in this case, the impact analysis interface is the parent interface of the results display interface, and the results display interface is a child interface of the impact analysis interface. This embodiment uses the indentation relationship between the impact analysis interface and the results display interface during the accident analysis process to demonstrate the chain relationship of accident impacts and consequences, more intuitively illustrating the chain logic in the accident analysis process.

[0077] In one example, the device node data includes protective measure data; the accident cause data includes a first probability level characterizing the probability of the accident occurring; and the accident outcome data includes a severity level and a risk level. Figure 3 is a flowchart illustrating the risk level calculation according to an exemplary embodiment. As shown in Figure 3, step S103 involves obtaining accident outcome data through a result display interface, including:

[0078] Step S301: Revise the first probability level based on the protective measures data to obtain the second probability level in the result data. Optionally, update the first probability level of the accident based on the protective measures coefficient and the effectiveness of the protective measures in the protective measures data.

[0079] In one example, step S301 includes:

[0080] Step S3011: Determine effective protection data based on the protection measures data according to the preset screening rules.

[0081] As an example, step S3011 includes:

[0082] For each protective measure data acquired, it is determined whether the number of protective measures of the same type as the current protective measure is less than or equal to a first threshold. If so, it is determined whether the effective protective data is less than or equal to a second threshold. In response to the effective protective data being less than or equal to the second threshold, a protective measure reduction value is calculated based on the protective measure reduction coefficient, and the effective protective data is updated based on the protective measure reduction value.

[0083] Optionally, the first and second thresholds can be set according to actual conditions. If the number of protective measures of the same type as the currently added protective measure does not exceed the first threshold, and the effective protective data has not reached the second threshold, then the currently added protective measure can be made effective. The protective measure reduction value is calculated based on the protective measure reduction coefficient. Optionally, the protective data characterizes the degree to which the protective measure reduces the probability level of an accident, and the logarithm of the protective measure reduction coefficient can be taken as the reduction value. For example, if the protective reduction coefficients are 0.1, 0.001, and 0.0001, then the corresponding protective measure reduction values, i.e., the effective protective data, are 1, 2, and 3. In this example, by judging the effectiveness of the added protective measures and calculating the effective protective data, it is beneficial to reduce the probability level of an accident.

[0084] As another example, step S3011 includes:

[0085] Optionally, when multiple protective measures have been added, filtering rules are obtained based on the received configuration instructions. The protective measures are then activated or deactivated by selecting an instruction. For activated protective measures, a reduction value is calculated, and the effective protection data is updated, using the same calculation method as the previous example.

[0086] In this example, configuration commands enable or disable corresponding protective measures. When multiple protective measures have already been added, the most suitable or more effective measure for the current device node can be selected. This helps increase the mitigation value of protective measures, thereby minimizing the probability of an incident. This approach improves the flexibility and effectiveness of incident analysis.

[0087] Step S3012: Revise the first probability level based on the effective protection data to obtain the second probability level in the result data. Optionally, the second probability level is obtained by subtracting the effective protection data from the first probability level of the accident.

[0088] Step S302: Based on the severity level and the second probability level obtained in step S301, query the preset risk assessment matrix to determine the risk level.

[0089] Optionally, a risk assessment matrix is ​​pre-configured. This matrix is ​​a two-dimensional matrix constructed based on the severity level and the probability level of an accident. The risk level is retrieved from the risk assessment matrix based on the second probability level of the accident and the severity level in the accident outcome data.

[0090] In this example, the effectiveness of a protective measure is calculated each time it is added, determining whether it is valid. Alternatively, configuration commands can be used to enable or disable corresponding protective measures. When multiple protective measures have already been added, the most suitable or more effective measure for the current device node can be selected. This helps to increase the reduction value of protective measures, thereby minimizing the probability of an incident and reducing its risk level. This approach improves the flexibility and effectiveness of incident analysis.

[0091] Referring again to Figure 1, step S104 is executed after step S103.

[0092] Step S104, Figure 4 is a chain data structure diagram according to an exemplary embodiment. As shown in Figure 4, based on the relationship between the cause display interface, the impact analysis interface and the result display interface, the accident cause data, equipment node data and accident result data are stored in the database in the form of an accident chain.

[0093] Optionally, based on the link relationship between the cause display interface, the impact analysis interface, and the result display interface during the analysis process, the accident link is stored in the database in a chain-like data structure as shown in Figure 4.

[0094] In this example, a chained data structure is used to store the complete chain of the analysis process. From any node, it is possible to trace back all the upstream nodes of that node and the complete chain in which that node is located. This is beneficial for the automatic extraction of data in subsequent analysis processes, thereby clearly and intuitively displaying the chained logical relationship of accident causes, effects and results in the accident analysis process, which facilitates the analysis of accidents and improves the effectiveness of risk analysis.

[0095] Referring again to Figure 1, proceed to step S105 after step S104.

[0096] Step S105: Retrieve the target incident link from the database according to the search instruction and display it. Optionally, the search instruction may include searching based on the protective measure tag number or searching based on equipment, deviation, and impact.

[0097] In one example, step S105 includes:

[0098] Step S1051: Obtain key search information according to the search instruction, and determine the target incident link in the database using the key search information as an index. Optionally, the target incident link can be searched based on the protective measure tag number or based on the device, deviation, and impact.

[0099] In one example, step S1051 includes: determining a first incident link and a second incident link based on search key information; merging identical data from the first incident link and the second incident link to obtain the target incident link.

[0100] Optionally, based on the protection measure tag number, all incident links where the current protection measure is located can be searched. Data on nodes with the same device and data on the same incident results in the queried incident links are then merged and displayed to obtain the target incident link. In this example, the protection measure tag number is associated with the device; querying the incident link by the protection measure tag number makes it easy to find the faulty device and facilitates analysis.

[0101] Step S1052: Determine the target display method based on the risk level of the target accident link, and display the accident link image in the target display method.

[0102] Figure 5 is a schematic diagram of an accident chain image according to an exemplary embodiment. As shown in Figure 5, the accident chain image includes a cause analysis box, an impact analysis box, a result analysis box, and the relationship between the three represented by connecting lines. In this embodiment, the target display method includes configuring the color and / or line width of the cause analysis box, the impact analysis box, the result analysis box, and the connecting lines. Specifically, the following optional methods are provided for the target display method:

[0103] <First Option>

[0104] The target display method includes configuring different colors for differentiated display, specifically determining the line color of the frame or connecting line in the accident link image based on the risk level.

[0105] Optionally, the line colors in the accident link image are determined based on the risk level in the accident result data calculated in step S104. If the risk level is the highest level in the preset risk assessment matrix, then the line color identifying the accident result data as being in the same accident link is the highest level color in the preset risk assessment matrix.

[0106] <Second Optional Method>

[0107] The target display method includes configuring different line widths for differentiated display. Specifically, based on the first probability level in the accident cause data, the initial line width of the bounding boxes or connecting lines in the accident cause image is determined. According to the calculation rules, the line width of each device node in the accident link image is obtained based on the protective measure reduction value and the initial line width.

[0108] Optionally, a preset probability level table is queried according to the first probability level to determine the occurrence frequency value of the accident cause data, and the initial line width is set based on the occurrence frequency value.

[0109] Optionally, for example, assuming the occurrence frequency of accident cause data in link 1 is 1 / 10, when the impact analysis interface A on this accident link uses effective protection measures with a protection coefficient of 0.1, if the next node is the impact analysis interface B, then the reduction value is (1 / 10 * 0.1) / (1 / 10), and the linewidth is now one level thinner than the initial linewidth. Assuming the initial linewidth is 10, then the linewidth of the impact interface B is 9. In response to the current interface's linewidth being less than or equal to the third threshold, the linewidths after the current device node on the accident link where the current device node is located are all the third threshold.

[0110] When multiple links converge to the same impact analysis interface, the protection reduction values ​​of multiple nodes are added together. For example, assuming the occurrence frequency of accident cause data in link 1 is 1 / 10, and impact analysis interface A on this accident link uses effective protection measures with a protection coefficient of 0.1, and the next node is impact analysis interface B; simultaneously, the occurrence frequency of accident cause data in link 2 is 1 / 10, the protection reduction coefficient on impact C on this link is 0.01, and the next node is also impact analysis interface B, then the reduction value at this time is 1 / 10 * 0.1 + 1 * 0.01. This result is reduced to approximately 1 / 100, and the linewidth at this time is two levels thinner than the initial linewidth. Assuming the initial linewidth is 10, then the linewidth of impact interface B is 8. In response to the current interface's linewidth being less than or equal to the third threshold, the linewidths after the current device node on the accident link where the current device node is located are all the third threshold.

[0111] <Third Option>

[0112] The target display method also includes differentiating the display by configuring different colors and line widths; that is, the third optional method combines the first and second optional methods mentioned above. This provides users with a more intuitive visual difference, highlighting the logical relationships between different pieces of information.

[0113] Based on the above, step S1051 searches the database for accident links according to the search instruction, merges identical data in the accident links, and obtains the target accident link. Step S1052 displays the obtained target accident link, determines the line color and initial line width of the accident link image based on the risk level, and obtains the line width changes during the accident link process by calculating the reduction value of effective protective measures taken. In this way, the logical relationships and changes between accident links are dynamically and intuitively displayed, which is beneficial for analyzing accident results.

[0114] In summary, this application uses the indentation relationship between the cause display interface, impact analysis interface, and result display interface during the analysis process to reflect the chain relationship of the accident chain, more intuitively demonstrating the chain logic between accidents. By storing the accident chain in the database using a chain-like storage structure, it is possible to trace back all upstream nodes and the complete chain in which any node is located, facilitating the automatic data retrieval during subsequent analysis. This clearly and intuitively displays the chain logic relationship of accident causes, impacts, and results during accident analysis, simplifying accident analysis and improving the effectiveness of risk analysis. Preset filtering rules enable or disable corresponding protective measures. When adding multiple protective measures, the most suitable or more effective protective measures for the current device node can be selected, which helps to increase the reduction value of protective measures, thereby minimizing the probability of accident occurrence and reducing the risk level of the accident. This improves the flexibility and effectiveness of accident analysis. Simultaneously, accident chains are searched from the database using search commands, and identical data in the accident chains are merged to obtain the target accident chain. Preset calculation rules determine the line color of the accident chain image and the changes in line width during the accident chain process. This method dynamically and intuitively displays the logical relationships and changes between accident links, which is beneficial for analyzing accident results.

[0115] Second aspect

[0116] This application provides a risk data display system. Figure 6 is a block diagram of a risk data display system according to an exemplary embodiment. As shown in Figure 6, the system includes:

[0117] Cause module 100: Used to provide a cause display interface, through which accident cause data can be obtained.

[0118] Impact Module 200: This module provides an impact analysis interface, through which device node data can be obtained.

[0119] Result module 300: In response to receiving the first trigger operation and the device node data meeting the preset conditions, it provides a result display interface and obtains the accident result data through the result display interface.

[0120] Storage module 400: Used to store accident cause data, equipment node data, and accident result data in the database in the form of accident links, according to the hierarchical relationship between the cause display interface, the impact analysis interface, and the result display interface.

[0121] Display module 500: Used to retrieve and display the target accident link from the database according to the search command.

[0122] In one example, the device node data includes the secondary node type of the current node, and the affected module 200 includes:

[0123] First data unit 210: used to provide a first impact analysis interface, and to obtain the first device node data through the first impact analysis interface.

[0124] Second data unit 220: In response to the fact that the secondary node type of the first device does not meet the preset conditions, it provides a second impact analysis interface, which is used to obtain the secondary device node data of the first device.

[0125] In one example, the second impact analysis interface is configured to be displayed with an indentation relative to the first impact analysis interface.

[0126] In one example, the results display interface is configured to display the relative impact analysis interface with indentation.

[0127] In one example, the device node data includes protective measure data; the accident cause data includes a first probability level characterizing the probability of the accident occurring; the accident outcome data includes a severity level and a risk level; and the outcome module 300 includes:

[0128] Possibility level acquisition unit 310: used to revise the first possibility level based on the protective measures data to obtain the second possibility level in the result data.

[0129] Risk level acquisition unit 320: used to determine the risk level by querying a preset risk assessment matrix based on the second probability level and severity level.

[0130] In one example, the probability level acquisition unit 310 includes:

[0131] Protection data subunit 311: used to determine effective protection data based on protection measure data according to preset filtering rules.

[0132] Second possibility level determination subunit 312: used to revise the first possibility level based on effective protection data to obtain the second possibility level in the result data.

[0133] In one example, the protective measures data includes the type of protective measures and the reduction factor of the protective measures. The protective data sub-unit 311 specifically includes:

[0134] For each protective measure data acquired, it is determined whether the number of protective measures of the same type as the current protective measure is less than or equal to the first threshold; if so, it is determined whether the effective protective data is less than or equal to the second threshold. In response to the effective protective data being less than or equal to the second threshold, the protective measure reduction value is calculated based on the protective measure reduction coefficient, and the effective protective data is updated based on the protective measure reduction value.

[0135] In one example, display module 500 includes:

[0136] Search unit 510: Obtains key search information according to search instructions, and uses the key search information as an index to determine the target accident link in the database.

[0137] Display unit 520: Determines the target display mode based on the risk level of the target accident link, and displays the accident link image in the target display mode.

[0138] In one example, display unit 520 includes:

[0139] Line color subunit: determines the line color in the accident link image based on the risk level; and / or

[0140] Initial linewidth sub-unit: Determine the initial linewidth of the accident cause image based on the first probability level in the accident cause data.

[0141] Node linewidth sub-unit: Based on preset calculation rules, the linewidth of each device node in the accident link image is obtained based on the protection measure reduction value and the initial linewidth.

[0142] In one example, search unit 510 includes:

[0143] Search subunit: Determine the first and second accident links based on key search information.

[0144] Merging sub-units: Merging identical data from the first and second accident links to obtain the target accident link.

[0145] In summary, this application uses the indentation relationship between the cause module 100, the impact module 200, and the result module 300 during the analysis process to represent the chain relationship of the accident chain, providing a more intuitive representation of the chain logic between accidents. The storage module 400 stores the accident chain in the database using a chain-like storage structure, enabling tracing back all upstream nodes and the complete chain from any node. This facilitates the automatic retrieval of data during subsequent analysis, clearly and intuitively displaying the chain logic relationship of accident causes, impacts, and results during accident analysis, thus improving the effectiveness of risk analysis. By using preset filtering rules to enable or disable corresponding protective measures, when adding multiple protective measures, the most suitable or more effective protective measures for the current device node can be selected, which helps to increase the reduction value of protective measures, thereby minimizing the probability of accident occurrence and reducing the risk level of the accident. In this way, the flexibility and effectiveness of accident analysis are improved. Simultaneously, the display module 500 searches the database for accident links using search commands, merges identical data within the accident links to obtain the target accident link, and determines the line color and line width changes in the accident link image according to preset calculation rules. This method dynamically and intuitively displays the logical relationships and changes between accident links, facilitating the analysis of accident results.

[0146] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0147] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for displaying risk data, characterized in that, include: Provide a cause display interface, through which accident cause data can be obtained; Provide an impact analysis interface to obtain device node data; In response to receiving a first trigger operation and the device node data meeting preset conditions, a result display interface is provided, and accident result data is obtained through the result display interface; Based on the relationship between the cause display interface, the impact analysis interface, and the result display interface, the accident cause data, equipment node data, and accident result data are stored in the database in the form of an accident chain. The target incident link is retrieved from the database according to the search command and displayed. The device node data includes the secondary node type of the current node. Providing an impact analysis interface to obtain device node data includes: providing a first impact analysis interface to obtain first device node data; responding to the fact that the secondary node type of the first device does not meet the preset condition, providing a second impact analysis interface, the second impact analysis interface being used to obtain the secondary device node data of the first device; the device node data includes protective measure data; the accident cause data includes a first probability level characterizing the probability of an accident occurring, and the accident result data includes a severity level and a risk level; the device node data includes protective measure data; the accident cause data includes a first probability level characterizing the probability of an accident occurring, and the accident result data includes a severity level and a risk level; obtaining accident result data through the result display interface includes: revising the first probability level based on the protective measure data to obtain a second probability level in the result data; based on... The risk level is determined by querying a preset risk assessment matrix using the second probability level and the severity level. Revising the first probability level based on the protective measure data to obtain the second probability level in the result data includes: determining effective protective data based on the protective measure data according to preset filtering rules; revising the first probability level based on the effective protective data to obtain the second probability level in the result data. The protective measure data includes protective measure types and protective measure reduction coefficients. Determining effective protective data in the protective measure data according to preset filtering rules includes: for each piece of protective measure data acquired, determining whether the number of protective measures of the same type as the current protective measure is less than or equal to a first threshold; if so, determining whether the effective protective data is less than or equal to a second threshold; in response to the effective protective data being less than or equal to the second threshold, calculating a protective measure reduction value based on the protective measure reduction coefficient, and updating the effective protective data based on the protective measure reduction value.

2. The risk data display method according to claim 1, characterized in that, The second impact analysis interface is configured to be displayed with an indentation relative to the first impact analysis interface; and / or the result display interface is configured to be displayed with an indentation relative to the impact analysis interface.

3. The risk data display method according to claim 1, characterized in that, The step of retrieving and displaying the target accident link from the database according to the search instruction includes: retrieving key search information according to the search instruction; determining the target accident link in the database using the key search information as an index; determining the target display method according to the risk level of the target accident link; and displaying the accident link image in the target display method.

4. The risk data display method according to claim 3, characterized in that, The step of obtaining key search information according to the search instruction and determining the target accident link in the database using the key search information as an index includes: determining a first accident link and a second accident link based on the key search information; and merging identical data in the first accident link and the second accident link to obtain the target accident link.

5. The risk data display method according to claim 3, characterized in that, The step of determining the target display method based on the risk level of the target accident link includes: determining the line color in the accident link image based on the risk level; and / or determining the initial line width of the accident cause image based on the first probability level in the accident cause data; and obtaining the line width of each device node in the accident link image based on the protective measure reduction value and the initial line width according to a preset calculation rule.

6. A risk data display system, characterized in that, A method for displaying risk data according to any one of claims 1-5 includes: a cause module for providing a cause display interface and obtaining accident cause data through the cause display interface; an impact module for providing an impact analysis interface and obtaining device node data through the impact analysis interface; a result module for providing a result display interface in response to receiving a first trigger operation and the device node data meeting preset conditions, and obtaining accident result data through the result display interface; a storage module for storing the accident cause data, device node data, and accident result data in the form of an accident link in a database according to the hierarchical relationship of the cause display interface, the impact analysis interface, and the result display interface; and a display module for retrieving and displaying a target accident link from the database according to a search instruction.

Images