Go-flow automatic modeling and analysis method, system and medium based on system flowchart

Abstract

The application discloses a GO-FLOW automatic modeling and analysis method and system based on a system flowchart, an electronic device and a storage medium, and the method comprises the following steps: through analysis and reading of a system CAD or Visio data structure file, system flow structure and equipment composition information are identified and extracted; further, in combination with consideration of general system equipment division and equipment failure modes, a GO-FLOW componentized model of system equipment is constructed; according to a modelized mapping relationship of a GO-FLOW operator, a system model data structure file is automatically generated; finally, the generated system model file is imported into a GO-FLOW computing engine, and system reliability analysis is realized.

Description

Technical Field

[0001] This invention belongs to the field of process system reliability and safety analysis, and specifically relates to a GO-FLOW automatic modeling and analysis method, system, electronic device and storage medium based on system flowchart. Background Technology

[0002] System reliability and safety are always key concerns for high-risk industrial process systems. System reliability and probabilistic safety analysis are also crucial technical foundations for risk-guided safety management. Risk-guided safety management aims to rapidly update risk monitoring models based on real-time changes in system operating characteristics and equipment configuration, and to reflect the current risk level of the system effectively and promptly through real-time risk profile calculations, thereby providing technical support for system operation decisions. Therefore, system reliability and probabilistic risk monitoring models must meet requirements such as accurate model mapping, rapid updates and efficient calculations, and traceability of the analysis process and results.

[0003] Risk-guided safety management systems represent an advancement over traditional probabilistic safety assessment techniques, with event tree / fault tree methods remaining the fundamental approach. While fault tree methods offer advantages such as maturity, high identifiability, clear logical relationships, and ease of identifying system weaknesses, they struggle to handle system configuration changes, sequential failures, equipment lifespan effects, and multi-stage task problems. Furthermore, the methods require a high level of expertise, and fault tree models constructed by different modelers often exhibit significant differences, making verification and validation difficult. These limitations directly restrict the further application of fault tree methods in online risk monitoring and management.

[0004] The GO-FLOW method is a success-oriented system reliability and safety analysis technique that can describe the complex characteristics of a system under multi-task profiles and handle timing issues. The GO-FLOW method directly constructs a GO-FLOW model based on the system's physical flow diagram. GO-FLOW operators are used to simulate the functionality and failure of components in the system, or to simulate the logical relationships between components, while signal lines reflect the interrelationships and interactions between components. The resulting GO-FLOW model is compact, corresponds to the system configuration, is easy to verify, and is readily modifiable and updatable. Summary of the Invention

[0005] This invention addresses the technical problems of existing system reliability analysis methods, such as complex modeling, high professional requirements, lack of automated modeling tools, and difficulty in model verification. It provides a GO-FLOW-based automatic modeling and analysis method, system, electronic equipment, and storage medium based on system flowcharts. This method automatically identifies system flow structure relationships and equipment composition information by parsing CAD or Visio data structure files. Combined with the GO-FLOW model mapping relationship of general equipment, it constructs a success-oriented system reliability model. This allows for the direct conversion of system CAD or Visio design drawings into a system reliability model, solving the problem of model inconsistencies caused by varying levels of proficiency or misunderstandings among different professionals. This facilitates system design improvement and reliability evaluation. Furthermore, the system reliability model serves as an effective supplement to traditional event tree / fault tree methods for system failure, improving the accuracy and rapid updating capability of the system reliability / risk model to the actual physical process system. This lays the technical foundation for real-time risk guidance and safety management of the system.

[0006] The first objective of this invention is to provide a GO-FLOW automatic modeling and analysis method for system flowcharts.

[0007] The second objective of this invention is to provide a GO-FLOW automatic modeling and analysis system for system flowcharts.

[0008] A third objective of this invention is to provide an electronic device.

[0009] A fourth objective of this invention is to provide a storage medium.

[0010] The first objective of this invention can be achieved by adopting the following technical solution:

[0011] A GO-FLOW automated modeling and analysis method based on system flowcharts, the method comprising:

[0012] Based on the classification of system equipment, typical failure modes and reliability parameters of various general-purpose equipment are determined through equipment failure mode and impact analysis.

[0013] Based on the classification of system equipment, typical failure modes, and reliability parameters, and combined with the functional modeling characteristics of the GO-FLOW operator, a model mapping relationship between general-purpose equipment and the GO-FLOW operator is established, and a GO-FLOW component model library for general-purpose equipment is constructed.

[0014] By parsing the structure data file of the system flowchart, the connection relationships between system devices can be obtained;

[0015] Based on the connection relationships between system devices, a GO-FLOW model file is generated using the modeled mapping relationship between general-purpose devices and the GO-FLOW operator, thereby realizing the automatic generation of the system's GO-FLOW model;

[0016] By reading the GO-FLOW model file through the GO-FLOW computing engine, dynamic updates and calculations of system reliability can be achieved.

[0017] Furthermore, based on the classification of system devices, typical failure modes, and reliability parameters, and combined with the functional modeling characteristics of the GO-FLOW operator, a model-based mapping relationship between general-purpose devices and the GO-FLOW operator is established, and a GO-FLOW component-based model library for general-purpose devices is constructed, including:

[0018] Based on the classification of system equipment, the corresponding GO-FLOW operator is automatically selected to express the component-based model of the basic functional reliability of the equipment.

[0019] Based on the equipment failure mode or specific function, selectively add functional component model modules.

[0020] Furthermore, based on the functional structure design and operating characteristics of the system equipment, the system equipment is classified into non-active components and active components. A mapping relationship between the system equipment classification and the GO-FLOW operator is established. The non-active components refer to system equipment without action requirements, and are divided into source components and non-source components according to whether they constitute a signal source. The active components refer to components that have specific action requirements, and are divided into normally closed components, normally open components, and switching components according to their design and operating characteristics.

[0021] Furthermore, based on the system phase task problem description, the system configuration structure model under different phases is transformed through corresponding operators; wherein, the phase task component model is composed of multiple corresponding operators connected by "AND" logic gates, representing the conditions and correlations between multiple task phases.

[0022] Furthermore, the step of parsing the structure data file of the system flowchart to obtain the connection relationships between system devices includes:

[0023] The parsing module is used to convert the structure data file of the system flowchart into a text file format data file.

[0024] Iterate through all block structures in the block segment of the data file in sequence. If the block structure is a real system device, simplify the block structure into a rectangle to determine the physical connection relationship between devices in the entity segment.

[0025] Iterate through the entities in the entity segment of the data file. If the entity is a device, read the center coordinates and reliability modeling parameters of the device and store them in a custom device parameter information data structure. If the entity is a pipe, read the start and end coordinates of the pipe and store them in the device parameter information data structure.

[0026] For all pipes in the device parameter information data structure, find the connected devices and store the physical connection relationships between them in the device connection relationship data structure.

[0027] Furthermore, the connected devices are found for all pipes in the device parameter information data structure, including:

[0028] Extract the pipeline information sequentially from the equipment parameter information data structure, and use the extracted pipeline as the current pipeline;

[0029] Determine whether the current pipeline is connected to other pipelines or equipment. If it is connected to equipment, store the physical connection relationship between them in the equipment connection relationship data structure. If it is connected to a pipeline, search along the connecting pipeline for connected equipment or pipelines until a connected equipment is found.

[0030] Furthermore, the step of generating a GO-FLOW model file based on the connection relationships between system devices and the modeled mapping relationship between general-purpose devices and the GO-FLOW operator includes:

[0031] Based on the connection relationships between each pair of devices in the device connection relationship data structure, construct the front and back device lists;

[0032] Based on the number of times a device appears repeatedly in the preceding and following device lists, the device is determined to be a starting device, an ending device, a multi-output device, or a multi-input device.

[0033] All starting devices are added to the stack as nodes. All nodes in the stack are traversed. Depending on whether a node is a starting device or a multi-input device, the corresponding GO-FLOW operator parameter table is generated according to the model mapping relationship, and the GO-FLOW model data structure is constructed to realize the construction of the system model data structure.

[0034] Write the GO-FLOW operator parameter table into the GO-FLOW model file according to the GO-FLOW operator type index;

[0035] Based on the characteristics of the system's operation process and the defined time point sequence, the signal strength values ​​at different time points are written into the GO-FLOW model file according to the operator sequence number;

[0036] The operator sequence number corresponding to the endpoint device is written as the final output signal into the GO-FLOW model file to achieve the complete construction of the system's GO-FLOW model file.

[0037] Furthermore, the step of adding all starting devices as nodes to a stack, traversing all nodes in the stack, and further generating corresponding GO-FLOW operator parameter tables and constructing the GO-FLOW model data structure based on whether a node is a starting device or a multi-input device according to the modeled mapping relationship, includes:

[0038] Add all starting devices to the stack as nodes, pop nodes from the stack one by one, and use the popped node as the current device node;

[0039] Determining whether the current device node is the starting device includes:

[0040] If it is the starting device, generate a main input signal and construct the GO-FLOW model data structure; otherwise: determine whether the current device node is a multi-input device, including:

[0041] If the current device node is a multi-input device, then: if all input device nodes have been accessed, generate logic gates and construct the GO-FLOW model data structure; otherwise, pop a node from the stack and use it as the current device node, and determine whether the current device node is the starting device; otherwise, generate the corresponding GO-FLOW operator parameter table according to the model mapping relationship and construct the GO-FLOW model data structure.

[0042] If the current device node is the destination device, then: if the stack is empty, it means that all device nodes have been traversed, and the traversal ends; otherwise, pop a node from the stack as the current device node, and determine whether the current device node is the starting device; otherwise:

[0043] Search for downstream device nodes of the current device node and determine whether there is one or more downstream device nodes. If there is only one, then the downstream device node is used as the current device node, and it is determined whether the current device node is a multi-input device. Otherwise, add the searched downstream device node to the stack, pop a node from the top of the stack as the current device node, and determine whether the current device node is a multi-input device.

[0044] The second objective of this invention can be achieved by adopting the following technical solution:

[0045] A GO-FLOW automated modeling and analysis system based on system flowcharts, the system comprising:

[0046] The reliability characteristic parameter determination module is used to classify system equipment according to its composition and design and operation characteristics; based on the classification of system equipment, it determines the typical failure modes and reliability parameters of various general-purpose equipment through equipment failure mode and impact analysis.

[0047] The mapping relationship establishment module is used to establish a model-based mapping relationship between general-purpose devices and the GO-FLOW operator based on the classification of system devices, typical failure modes and reliability parameters, combined with the functional modeling characteristics of the GO-FLOW operator, and to construct a GO-FLOW component model library for general-purpose devices;

[0048] The connection relationship acquisition module is used to obtain the connection relationships between system devices by parsing the structure data file of the system flowchart;

[0049] The GO-FLOW model generation module is used to generate GO-FLOW model files based on the connection relationships between system devices and the modeled mapping relationship between general-purpose devices and GO-FLOW operators, thereby realizing the automatic generation of the system's GO-FLOW model.

[0050] The update calculation module is used to read the GO-FLOW model file through the GO-FLOW calculation engine to realize dynamic update calculation of system reliability.

[0051] The third objective of this invention can be achieved by adopting the following technical solution:

[0052] An electronic device includes a processor and a memory for storing a processor-executable program, wherein when the processor executes the program stored in the memory, it implements the above-described GO-FLOW automatic modeling and analysis method.

[0053] The fourth objective of this invention can be achieved by adopting the following technical solution:

[0054] A storage medium storing a program that, when executed by a processor, implements the GO-FLOW automatic modeling and analysis method described above.

[0055] The present invention has the following advantages over the prior art:

[0056] 1. The method provided by this invention can directly generate a system reliability model from system CAD or Visio design drawings, which greatly reduces the complexity of system reliability modeling and analysis. Moreover, the established model is similar to the system flowchart, which facilitates model checking and verification. Furthermore, the signal flow in the GO-FLOW method is an intuitive expression of the existence of material flow, energy flow and control flow signals in the actual physical world. Its task-oriented modeling and analysis ideas are in line with human cognitive thinking habits and facilitate model understanding.

[0057] 2. The GO-FLOW component-based modeling method for equipment provided by this invention comprehensively considers the functional structure design characteristics, operational process characteristics, and failure modes of system equipment. It decomposes basic reliability functional requirement failures, operational failures, and functional recovery and maintenance processes into relatively independent functional modules. Through the construction of a standardized GO-FLOW component-based model library, even non-professionals can easily construct a GO-FLOW model of the system according to the specific level of detail required for modeling and analysis. Furthermore, the GO-FLOW component-based model library also includes component-based model expressions for specific functions such as control signal delay effects, signal differential relationships, and stage task transitions, enhancing the modeling and representation capabilities of GO-FLOW.

[0058] 3. The automatic generation and analysis method of GO-FLOW model files provided by this invention can realize automatic reading and writing of GO-FLOW model data structures in text files based on the model-based mapping relationship between general-purpose devices and GO-FLOW operators, which facilitates model updates, modifications and analysis. The related technology can be further extended to online real-time reliability monitoring and risk monitoring applications. Attached Figure Description

[0059] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the structures shown in these drawings without creative effort.

[0060] Figure 1 This is a schematic diagram of the GO-FLOW automatic modeling and analysis method based on system flowchart according to Embodiment 1 of the present invention.

[0061] Figure 2 This is a schematic diagram of the device GO-FLOW model mapping relationship in Embodiment 1 of the present invention.

[0062] Figure 3 This is a flowchart of the data structure reading algorithm in the system flowchart of Embodiment 1 of the present invention.

[0063] Figure 4 This is a flowchart of the automatic generation and analysis algorithm for the GO-FLOW model in Embodiment 1 of the present invention.

[0064] Figure 5 This is a schematic diagram of a simplified water supply system structure based on CAD drawing design according to Embodiment 2 of the present invention.

[0065] Figure 6 This is an example diagram of system CAD data file parsing in Embodiment 2 of the present invention.

[0066] Figure 7 This is a schematic diagram of the system GO-FLOW model file data structure in Embodiment 2 of the present invention.

[0067] Figure 8 This is a schematic diagram of the system GO-FLOW analysis results in Embodiment 2 of the present invention.

[0068] Figure 9 This is a structural block diagram of the GO-FLOW automatic modeling and analysis system based on a system flowchart, according to Embodiment 3 of the present invention.

[0069] Figure 10 This is a structural block diagram of the electronic device according to Embodiment 4 of the present invention. Detailed Implementation

[0070] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention. It should be understood that the specific embodiments described are merely used to explain this application and are not intended to limit this application.

[0071] Example 1:

[0072] like Figure 1 As shown, the GO-FLOW automatic modeling and analysis method based on system flowcharts provided in this embodiment specifically includes:

[0073] (1) Establish a model-based mapping relationship between general-purpose devices and GO-FLOW operators, and construct a GO-FLOW component-based model library for general-purpose devices.

[0074] Based on the system equipment composition and design and operation characteristics, the system equipment is generally classified and defined. Furthermore, through equipment failure mode and impact analysis, the typical failure modes and reliability parameters of various general-purpose equipment are determined.

[0075] Based on the functional modeling characteristics of the GO-FLOW operator, a model-based mapping relationship between general-purpose devices and the GO-FLOW operator is established, and a GO-FLOW component-based model library for general-purpose devices is constructed.

[0076] Specifically, based on the equipment classification, the corresponding GO-FLOW operator is automatically selected to express the basic functional reliability component model of the equipment, and functional component model modules are selectively added according to the specific considerations of equipment failure modes or specific functions.

[0077] Based on the functional structure design and operational characteristics of the system equipment, the system equipment is classified into non-active components and active components. Non-active components generally refer to system equipment without operational requirements, and are further classified into source components and non-source components according to whether they constitute a signal source, which are represented by GO-FLOW operator No. 25 or GO-FLOW operator No. 21, respectively. Active components refer to components that contain specific operational requirements. Based on their design and operational characteristics, active components can be further subdivided into normally closed components, normally open components, and switching components, which are represented by GO-FLOW operator No. 26, GO-FLOW operator No. 27, and GO-FLOW operator No. 39, respectively.

[0078] Based on the categories of time-related failure modes of the equipment, componentized models of operational or standby failures are established to represent the lifespan characteristics of equipment failure over time. Operational failures are represented using the GO-FLOW operator (number 35), and standby failures are represented using the GO-FLOW operator (number 37). The maintenance process for repairable equipment is modeled and represented using the GO-FLOW operator (number 38).

[0079] Based on the differential relationship of the equipment output at different time points, the GO-FLOW operator No. 24 is used to describe the trend change of the equipment reliability or risk value over time.

[0080] Based on the delay effect of the device control signals, a component-based model of the device's delay function is established using the GO-FLOW operator (No. 28); the data structure of the component-based model of the delay function includes the delay time.

[0081] Based on the system's functional design characteristics and the process structure of the system's equipment, the logical structure for implementing system functions is constructed using the "AND", "OR", and "NOT" GO-FLOW logical operators.

[0082] Based on the system phase task problem description, the system configuration structure model under different phases is transformed by the 40th GO-FLOW operator; the phase task component model is composed of multiple 40th GO-FLOW operators connected by an AND logic gate, representing the conditions and correlations between multiple task phases.

[0083] The modeled mapping relationship between the general-purpose devices and the GO-FLOW operator established in this embodiment is as follows: Figure 2 As shown.

[0084] (2) By parsing the structure data file of the system flowchart, the connection relationship between system devices can be obtained.

[0085] Furthermore, such as Figure 3 As shown, step (2) includes:

[0086] (2-1) Use the Python Numpy parsing module to convert the system process flow diagram (PI&D) design data structure file into a text file format, open and read the structured information in the data file.

[0087] The data structure file contains headers, classes, tables, blocks, entities, and objects. During file data reading and parsing, the header, class, and table information in the system flowchart is ignored, and the process jumps directly to the blocks to identify system devices.

[0088] (2-2) Read the block structures in the data structure file in sequence and determine whether the block structure is a real system device. If it is, simplify the identified intangible block structure into a rectangle for further determination of the physical connection relationship between devices in the entity segment. Otherwise, jump to the reading of the next block structure and the identification of system devices until all block structures have been traversed. The block structure refers to the external structure of the system device in the computer-aided design (CAD) drawing.

[0089] (2-3) Upon entering the entity segment, entities are read sequentially according to the text data compilation order. It is determined whether the current entity is a device or a pipeline. If it is a device, the center coordinates and reliability modeling parameters of the device are read and stored in a custom device parameter information data structure. If it is a pipeline, the start and end coordinates of the pipeline are read and stored in the same device parameter information data structure. If neither is the case, the process jumps to the reading and judgment of the next entity until all entities in the entity segment have been completely traversed. The entity segment can be simply understood as an entity queue, which records all entity information. Entities constitute the most basic information block, or it can refer to the above-mentioned basic block structure or combined block structure.

[0090] (2-4) Extract pipeline information sequentially from the equipment parameter information data structure, determine whether the current pipeline is connected to other pipelines or equipment. If it is connected to equipment, store the physical connection relationship between them in the equipment connection relationship data structure; if it is a pipeline, search for connected equipment or pipelines along the connecting pipeline until a connected equipment is found, and store the physical connection relationship between them in the equipment association relationship data structure.

[0091] (3) Based on the connection relationship between the GO-FLOW component model library and system devices, generate GO-FLOW model files to realize the automatic generation of the system GO-FLOW model (i.e., system reliability model).

[0092] Furthermore, such as Figure 4 As shown, step (3) includes:

[0093] (3-1) Determine the devices based on the connection relationships between each pair of devices in the device association data structure.

[0094] Based on the connection relationships between pairs of devices in the device association data structure, construct the front and back device lists;

[0095] Compare the number of times a device appears in the front and back device lists. If a device appears only in the front device list, it is determined to be the starting device; if it appears only in the back device list, it is determined to be the ending device; if it appears multiple times in the front device list, it is a multi-output device; if it appears multiple times in the back device list, it is a multi-input device.

[0096] (3-2) Add all devices that are determined to be the starting device to the stack as nodes, pop nodes from the stack in sequence, and take the popped node as the current device node. Depending on whether the current device node is the starting device or a multi-input device, generate the corresponding GO-FLOW operator parameter table and construct the GO-FLOW model data structure to realize the construction of the system model data structure.

[0097] Furthermore, step (3-2) specifically includes:

[0098] All starting devices are added to the stack as nodes. Then, device nodes are popped from the stack one by one. It is then determined whether the current device node is the starting device. If it is the starting device, a main input signal is generated and the GO-FLOW model data structure is constructed. If it is not the starting device, then: it is determined whether the current device node is a multi-input device. If it is a multi-input device, then it is further determined whether all input device nodes have been accessed. If all input device nodes have been accessed, a logic gate is generated and the GO-FLOW model data structure is constructed. Otherwise, the next device node is popped from the stack and used as the current device node. The process is then repeated to determine whether the current device node is the starting device. If the current device node is not a multi-input device, the GO-FLOW model data structure is constructed directly.

[0099] After constructing the GO-FLOW model data structure, determine whether the current device node is the endpoint device. If so, end the search for the associated system flow structure diagram of the current device node and check if the stack is empty. If the stack is empty, it means that all device nodes have been traversed, and the loop ends. If there are still device nodes in the stack, pop the next device node from the stack and repeat the determination of whether it is the starting device. If not, continue to search for downstream device nodes of the current device node and determine whether there is one or more downstream device nodes. If there is only one downstream device node, use the downstream device node as the current device node and return to determine whether the current device node is a multi-input device. If there are multiple downstream device nodes, add the searched downstream device nodes to the stack, pop a node from the top of the stack as the current device node, and return to determine whether the current device node is a multi-input device. Based on the completed system model data structure, write the GO-FLOW operator parameter list generated when constructing the GO-FLOW model data structure into the GO-FLOW model file according to the GO-FLOW operator type index.

[0100] Based on the characteristics of the system's operation process, a time point sequence is defined, and the signal strength values ​​at different time points are written into the GO-FLOW model file according to the operator sequence number.

[0101] The operator sequence number corresponding to the endpoint device is written as the final output signal into the GO-FLOW model file to achieve the complete construction of the system's GO-FLOW model file.

[0102] (4) The GO-FLOW model file is read in through the GO-FLOW calculation engine to realize automatic analysis and calculation of system reliability.

[0103] Example 2:

[0104] This embodiment provides a simplified water supply system based on CAD drawing design. See [link / reference] Figure 5 The system described in this case consists of two water storage tanks (Tank#1 and Tank#2), five electrically operated isolation valves (V1, V2, V3, V4, V5), one check valve (V6), two water supply pumps (Pump#1 and Pump#2), and related pipelines.

[0105] Step 1: Read the data file.

[0106] Data file conversion: The exported CAD data structure file (.dxf format) is converted to a text file (.txt file) using the Python Numpy parsing module. The data structure information is then extracted from the file. The converted CAD data structure file contains information including headers, classes, tables, blocks, entities, and objects. During the file data reading and parsing process, headers, classes, and tables in the system flowchart are ignored; the process directly jumps to blocks to identify system devices.

[0107] Block structure name recognition: Read the block structure in the block segment sequentially according to the data compilation order. First, identify the block structure name. If the block structure name is a custom name, then read the block structure information. If the block structure is just a simple name code, such as U2, U3, etc., then it is considered that the block structure is automatically generated by the system and no parsing processing is performed.

[0108] Block structure information reading: For the block structure of the system device, the relative center coordinate position of the block structure is read and recorded, and various basic drawing elements (such as circles, line segments, etc.) that make up the block structure are further extracted to obtain the maximum and minimum values ​​of the block structure on the x-axis and y-axis. The block structure system device is represented by a rectangular box to cover the expression of the drawing shape information of the system device.

[0109] Entity Segment Information Reading: Next, the entity segments of the file are read to obtain the coordinates and parameters of the start / end points of the equipment and pipelines. These entity segments contain all attribute information of the equipment and pipelines, such as coatings, absolute coordinate positions, colors, fonts, and parameters. However, this invention only needs to extract the coordinate positions and parameter information of the equipment and pipelines; other information is considered irrelevant and is ignored. Considering the potential for the equipment to flip, rotate, scale, or shrink, after obtaining the rectangular entity equipment, the position parameters need to be updated to determine the final coordinate position of the equipment.

[0110] like Figure 6 As shown, ① represents the representative block information of the embodiment; ② indicates that the name of the currently selected block structure is "Tank"; ③ indicates the three-dimensional center coordinate position (0, 0, 0) of the currently selected block structure; ④ indicates that the currently selected block structure is composed of basic drawing elements such as circles and line segments.

[0111] Step 2: Determine the physical connection relationship of system devices.

[0112] Equipment / Pipeline Connection Information Identification: Since the information read from the entity segment in the previous step did not include equipment / pipeline connection information, the next step is to use the pipeline as the object and search for the connecting devices before and after the pipeline to establish "equipment-pipeline" or "pipeline-equipment" connection relationships. Consider the following two cases: ① The pipeline is directly connected to the equipment, in which case the coordinates of the pipeline's start (end) point fall exactly within the rectangular frame of the entity equipment; ② Pipelines are connected to each other: The start (end) point of the pipeline connects to another pipeline, which can be used as an extension of the current pipeline to further search for the equipment connection relationships of the other pipeline until the system equipment connected to it is found. Cases where equipment is not directly connected to each other via pipelines are not considered.

[0113] Equipment connection information table construction: Under the premise of not considering the impact of pipelines on system reliability (note: pipeline reliability can also be included in the system reliability calculation as needed), delete the physical location information of pipelines and their connection relationship with equipment (this part of the information is only used to determine the physical connection relationship of equipment and is not used for system reliability analysis and calculation), and only retain the reliability parameters of equipment and the series connection relationship between equipment.

[0114] Step 3: Generate GO-FLOW model file.

[0115] GO-FLOW Data Structure Generation: Based on the starting and ending devices identified by the GO-FLOW model file's automatic generation and analysis algorithm, a depth-first traversal method is used to sequentially generate functional operators corresponding to the system devices along the working fluid flow direction, and logical operators are supplemented according to multi-input devices. Then, the reliability parameters from the GO-FLOW operator parameter list are written into the model file, and the primary input signal strength of the starting device is uniformly set to 1 (indicating the presence of an active signal), while the secondary input signal strength of all devices is set to 0 (indicating no action on the system device). Finally, the final signal is defined based on the identified ending device, and the complete GO-FLOW model data structure file is output as follows: Figure 7 As shown.

[0116] During the construction of the GO-FLOW component model for the equipment, the corresponding GO-FLOW operator is selected according to the specific equipment category to complete the model representation of the equipment. In this embodiment, water tanks Tank#1 and Tank#2 are source-class devices, and GO-FLOW operator #25 is used to represent the generation of water source signals. The basic reliability of the water tank equipment is represented by GO-FLOW operator #21, and the probability of normal operation of the equipment is P. gThis information can be directly read from the equipment parameters. The water supply pumps (Pump#1, Pump#2) and electric isolation valves (V1, V2, V3, V4, V5) are switching components. Their functional failures are modeled using the GO-FLOW operator (No. 39), and their operational failures are simulated using the GO-FLOW operator (No. 35). Equipment reliability characteristic parameters include the probability P of premature start / stop. p The probability P of successfully shutting down the device c The probability P of successfully starting the device o Failure rate λ and maintenance rate μ can also be obtained directly from the equipment parameter list; check valve V6 is a two-state conducting non-acting component. Its normal operating state is represented by the GO-FLOW operator No. 21, and its failure process over time is described by the GO-FLOW operator No. 37. Reliability characteristic parameters include P g , λ and μ.

[0117] Figure 7 As shown, the generated system data structure consists of five parts: system structure model, equipment reliability characteristic parameters, task time series, source signal strength, and final signal identifier. Different data structures are separated by zero-space lines.

[0118] (1) System structure model.

[0119] The system structure model reflects the upstream and downstream physical and logical connections of the system devices. Combined with graph theory search, it can realize qualitative analysis of system reliability and obtain the combination of successful path sets of the system.

[0120] In the system structure model module, the first column represents the generated operator sequence number, the second column represents the operator type, the third column represents the row sequence number of operators of the same type but with different parameter settings, the fourth column represents the operator output signal name, and subsequent columns represent the number of primary input signals, the source of the primary input signals, the number of secondary input signals, and the source of the secondary input signals, respectively. If an operator has multiple primary input signals, multiple columns are inserted after the column for the number of primary input signals; similarly, if an operator has multiple secondary input signals, multiple columns are inserted after the column for the number of secondary input signals.

[0121] For example, in the system structure model module, the first row of data structure, from left to right, represents operator #1 (starting device Tank #1) as the 25th GO-FLOW operator (signal generator). The operator has no parameters, so the third column number is 0, and the output signal number is 1. Other data rows can be parsed in a similar way, which will not be elaborated here.

[0122] (2) Equipment reliability characteristic parameters.

[0123] Equipment reliability characteristic parameters can be directly obtained from the equipment parameter list in CAD or Visio computer-aided design platforms to achieve quantitative calculation of system reliability.

[0124] In the Equipment Reliability Characteristic Parameters module, the first column represents the operator type, the second column represents the operator parameter setting row number, and the third to fifth columns represent the specific parameters of the operator. The GO-FLOW operator has a maximum of 3 parameters, and if there are less than 3, they are automatically padded with 0.

[0125] For example, the first line in the equipment reliability characteristic parameter module indicates the setting of reliability characteristic parameters for the GO-FLOW operator (number 21), which represents the normal operating probability P of the equipment. g =0.9999. Other data rows can be parsed in a similar way, which will not be elaborated here.

[0126] (3) Task time sequence.

[0127] Task time series describes the system operation and manipulation task process through a series of discrete time points to support the reliability analysis of time series systems.

[0128] The first line in the task time series module indicates the number of time points, and the middle lines from the second line to the end of this module represent the definition and description of each time point.

[0129] For example, the number 5 in the first row of the task time series module represents 5 time points, and "1INITIAL STATE" in the second row represents the definition description of time point 1. Other time point descriptions can be parsed and understood in a similar way.

[0130] (4) Source signal strength.

[0131] The source signal strength represents the ability of the source function device to generate the source signal at each point in time, and is expressed as a probability value setting.

[0132] The source signal strength module uses a two-row single source signal representation. The first row in the two-row structure represents the sequence number of the GO-FLOW operator of the source signal generator, and the second row represents the signal strength of the source signal at different time points.

[0133] For example, the first line in the source signal strength module represents the operator #1, i.e., Tank #1; the five numbers 1.000E+00 in the second line represent the signal strength value of the source signal at five time points, respectively.

[0134] (5) Final signal identifier.

[0135] The final signal identifier is used to help system modelers and analysts extract system reliability analysis results.

[0136] The final signal identifier represents the output signal number of the endpoint device.

[0137] Step 4: GO-FLOW model analysis and calculation.

[0138] The generated GO-FLOW model file is imported into the GO-FLOW engine to perform qualitative and quantitative analysis and calculation of system reliability. The GO-FLOW analysis results for this embodiment are as follows: Figure 8 As shown.

[0139] Those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware, and the corresponding program can be stored in a computer-readable storage medium.

[0140] It should be noted that although the method operations of the above embodiments are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. On the contrary, the order of execution of the described steps may be changed. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0141] Example 3:

[0142] like Figure 9 As shown, this embodiment provides a GO-FLOW automatic modeling and analysis system based on a system flowchart. The system includes a reliability characteristic parameter determination module 901, a mapping relationship establishment module 902, a connection relationship acquisition module 903, a GO-FLOW model generation module 904, and an update calculation module 905, wherein:

[0143] The reliability characteristic parameter determination module 901 is used to classify system equipment according to the system equipment composition and design and operation characteristics; based on the classification of system equipment, it determines the typical failure modes and reliability parameters of various general-purpose equipment through equipment failure mode and impact analysis;

[0144] The mapping relationship establishment module 902 is used to establish a model-based mapping relationship between general-purpose devices and the GO-FLOW operator based on the classification of system devices, typical failure modes and reliability parameters, and combined with the functional modeling characteristics of the GO-FLOW operator, and to construct a GO-FLOW component model library for general-purpose devices;

[0145] The connection relationship acquisition module 903 is used to obtain the connection relationships between system devices by parsing the structure data file of the system flowchart;

[0146] The GO-FLOW model generation module 904 is used to generate GO-FLOW model files based on the connection relationship between system devices and the modeled mapping relationship between general-purpose devices and GO-FLOW operators, thereby realizing the automatic generation of the system's GO-FLOW model.

[0147] The update calculation module 905 is used to read the GO-FLOW model file through the GO-FLOW calculation engine to realize dynamic update calculation of system reliability.

[0148] The specific implementation of each module in this embodiment can be found in Embodiment 1 above, and will not be repeated here. It should be noted that the device provided in this embodiment is only illustrated by the division of the above functional modules. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure can be divided into different functional modules to complete all or part of the functions described above.

[0149] Example 4:

[0150] This embodiment provides an electronic device, which can be a computer, such as... Figure 10 As shown, the processor 1002, memory, input device 1003, display 1004, and network interface 1005 are connected via system bus 1001. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium 1006 and internal memory 1007. The non-volatile storage medium 1006 stores the operating system, computer programs, and database. The internal memory 1007 provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. When the processor 1002 executes the computer programs stored in the memory, it implements the GO-FLOW automatic modeling and analysis method of Embodiment 1 above, as follows:

[0151] Based on the classification of system equipment, typical failure modes and reliability parameters of various general-purpose equipment are determined through equipment failure mode and impact analysis.

[0152] Based on the classification of system equipment, typical failure modes, and reliability parameters, and combined with the functional modeling characteristics of the GO-FLOW operator, a model mapping relationship between general-purpose equipment and the GO-FLOW operator is established, and a GO-FLOW component model library for general-purpose equipment is constructed.

[0153] By parsing the structure data file of the system flowchart, the connection relationships between system devices can be obtained;

[0154] Based on the connection relationships between system devices, a GO-FLOW model file is generated using the modeled mapping relationship between general-purpose devices and the GO-FLOW operator, thereby realizing the automatic generation of the system's GO-FLOW model;

[0155] By reading the GO-FLOW model file through the GO-FLOW computing engine, dynamic updates and calculations of system reliability can be achieved.

[0156] Example 4:

[0157] This embodiment provides a storage medium, which is a computer-readable storage medium, storing a computer program. When the computer program is executed by a processor, it implements the GO-FLOW automatic modeling and analysis method of Embodiment 1 above, as follows:

[0158] Based on the classification of system equipment, typical failure modes and reliability parameters of various general-purpose equipment are determined through equipment failure mode and impact analysis.

[0159] Based on the classification of system equipment, typical failure modes, and reliability parameters, and combined with the functional modeling characteristics of the GO-FLOW operator, a model mapping relationship between general-purpose equipment and the GO-FLOW operator is established, and a GO-FLOW component model library for general-purpose equipment is constructed.

[0160] By parsing the structure data file of the system flowchart, the connection relationships between system devices can be obtained;

[0161] Based on the connection relationships between system devices, a GO-FLOW model file is generated using the modeled mapping relationship between general-purpose devices and the GO-FLOW operator, thereby realizing the automatic generation of the system's GO-FLOW model;

[0162] By reading the GO-FLOW model file through the GO-FLOW computing engine, dynamic updates and calculations of system reliability can be achieved.

[0163] It should be noted that the computer-readable storage medium in this embodiment can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0164] In summary, the GO-FLOW automatic modeling and analysis method based on system flowcharts proposed in this invention automatically identifies system process structure relationships and equipment composition information by parsing CAD or Visio data structure files. It constructs a success-oriented system reliability model by combining the general equipment GO-FLOW model mapping relationship. This serves as an effective supplement to the traditional event tree / fault tree method for system failure, improving the accuracy and rapid updating capability of the system reliability / risk model to the actual physical process system. This lays the technical foundation for real-time operational risk guidance and safety management of the system.

[0165] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope disclosed in the present invention, based on the technical solution and inventive concept of the present invention, shall fall within the scope of protection of the present invention.

Claims

1. A GO-FLOW automatic modeling and analysis method based on system flowcharts, characterized in that, The method includes: Based on the classification of system equipment, typical failure modes and reliability parameters of various general-purpose equipment are determined through equipment failure mode and impact analysis. Based on the classification of system equipment, typical failure modes, and reliability parameters, and combined with the functional modeling characteristics of the GO-FLOW operator, a model-based mapping relationship between general-purpose equipment and the GO-FLOW operator is established. A GO-FLOW component-based model library for general-purpose equipment is constructed, including: selecting corresponding GO-FLOW operators to express the basic functional reliability of equipment in a component-based model according to the classification of system equipment; selectively adding functional component-based model modules according to equipment failure modes or specific functions; and converting the system configuration structure model for different stages based on the description of system stage tasks using corresponding operators. The stage task component-based model consists of multiple corresponding operators connected by AND logic gates, representing the conditions and dependencies between multiple task stages. By parsing the structure data file of the system flowchart, the connection relationships between system devices can be obtained; Based on the connection relationships between system devices, a GO-FLOW model file is generated using the modeled mapping relationship between general-purpose devices and the GO-FLOW operator, thereby realizing the automatic generation of the system's GO-FLOW model; By reading the GO-FLOW model file through the GO-FLOW computing engine, dynamic updates and calculations of system reliability can be achieved. The step of generating a GO-FLOW model file based on the connection relationships between system devices and the modeled mapping relationship between general-purpose devices and the GO-FLOW operator includes: Based on the connection relationships between each pair of devices in the device connection relationship data structure, construct the front and back device lists; Based on the number of times a device appears repeatedly in the preceding and following device lists, the device is determined to be a starting device, an ending device, a multi-output device, or a multi-input device. All starting devices are added to the stack as nodes. All nodes in the stack are traversed. Depending on whether a node is a starting device or a multi-input device, the corresponding GO-FLOW operator parameter table is generated according to the model mapping relationship, and the GO-FLOW model data structure is constructed to realize the construction of the system model data structure. Write the GO-FLOW operator parameter table into the GO-FLOW model file according to the GO-FLOW operator type index; Based on the characteristics of the system's operation process and the defined time point sequence, the signal strength values ​​at different time points are written into the GO-FLOW model file according to the operator sequence number; The operator sequence number corresponding to the endpoint device is written as the final output signal into the GO-FLOW model file to achieve the complete construction of the system's GO-FLOW model file.

2. The GO-FLOW automatic modeling and analysis method according to claim 1, characterized in that, Based on the functional structure design and operating characteristics of the system equipment, the system equipment is classified into non-action components and action components. A mapping relationship between the system equipment classification and the GO-FLOW operator is established. The non-action components refer to system equipment without action requirements, and are divided into source components and non-source components according to whether they constitute a signal source. The action components refer to components that have specific action requirements, and are divided into normally closed components, normally open components, and switching components according to their design and operating characteristics.

3. The GO-FLOW automatic modeling and analysis method according to claim 1, characterized in that, The step of parsing the structured data file of the system flowchart to obtain the connection relationships between system devices includes: The parsing module is used to convert the structure data file of the system flowchart into a text file format data file. Iterate through all block structures in the block segment of the data file in sequence. If the block structure is a real system device, simplify the block structure into a rectangle to determine the physical connection relationship between devices in the entity segment. Iterate through the entities in the entity segment of the data file. If the entity is a device, read the center coordinates and reliability modeling parameters of the device and store them in a custom device parameter information data structure. If the entity is a pipe, read the start and end coordinates of the pipe and store them in the device parameter information data structure. For all pipes in the device parameter information data structure, find the connected devices and store the physical connection relationships between them in the device connection relationship data structure.

4. The GO-FLOW automatic modeling and analysis method according to claim 3, characterized in that, For all pipes in the device parameter information data structure, the connected devices are found, including: Extract the pipeline information sequentially from the equipment parameter information data structure, and use the extracted pipeline as the current pipeline; Determine whether the current pipeline is connected to other pipelines or equipment. If it is connected to equipment, store the physical connection relationship between them in the equipment connection relationship data structure. If it is connected to a pipeline, search along the connecting pipeline for connected equipment or pipelines until a connected equipment is found.

5. The GO-FLOW automatic modeling and analysis method according to claim 1, characterized in that, The process of adding all starting devices as nodes to a stack, traversing all nodes in the stack, and further generating corresponding GO-FLOW operator parameter tables and constructing the GO-FLOW model data structure based on whether a node is a starting device or a multi-input device according to the modeled mapping relationship includes: Add all starting devices to the stack as nodes, pop nodes from the stack one by one, and use the popped node as the current device node; Determining whether the current device node is the starting device includes: If it is the starting device, generate a main input signal and construct the GO-FLOW model data structure; otherwise: determine whether the current device node is a multi-input device, including: If the current device node is a multi-input device, then: if all input device nodes have been accessed, generate logic gates and construct the GO-FLOW model data structure; otherwise, pop a node from the stack and use it as the current device node, and determine whether the current device node is the starting device; otherwise, generate the corresponding GO-FLOW operator parameter table according to the model mapping relationship and construct the GO-FLOW model data structure. If the current device node is the destination device, then: if the stack is empty, it means that all device nodes have been traversed, and the traversal ends; otherwise, pop a node from the stack as the current device node, and determine whether the current device node is the starting device; otherwise: Search for downstream device nodes of the current device node and determine whether there is one or more downstream device nodes. If there is only one, then the downstream device node is used as the current device node, and it is determined whether the current device node is a multi-input device. Otherwise, add the searched downstream device node to the stack, pop a node from the top of the stack as the current device node, and determine whether the current device node is a multi-input device.

6. A GO-FLOW automatic modeling and analysis system based on system flowcharts, used to implement the GO-FLOW automatic modeling and analysis method according to any one of claims 1 to 5, characterized in that, The system includes: The reliability characteristic parameter determination module is used to determine the typical failure modes and reliability parameters of various general-purpose equipment based on the classification of system equipment and through equipment failure mode and impact analysis. The mapping relationship establishment module is used to establish a model-based mapping relationship between general-purpose devices and the GO-FLOW operator based on the classification of system devices, typical failure modes and reliability parameters, combined with the functional modeling characteristics of the GO-FLOW operator, and to construct a GO-FLOW component model library for general-purpose devices; The connection relationship acquisition module is used to obtain the connection relationships between system devices by parsing the structure data file of the system flowchart; The GO-FLOW model generation module is used to generate GO-FLOW model files based on the connection relationships between system devices and the modeled mapping relationship between general-purpose devices and GO-FLOW operators, thereby realizing the automatic generation of the system's GO-FLOW model. The update calculation module is used to read the GO-FLOW model file through the GO-FLOW calculation engine to realize dynamic update calculation of system reliability.

7. A storage medium storing a program, characterized in that, When the program is executed by the processor, it implements the GO-FLOW automatic modeling and analysis method as described in any one of claims 1 to 5.

Images