Fault tree creation method, fault tree creation device, and program
The automated fault tree creation method and device efficiently generate fault trees from system diagrams by analyzing block abnormalities, reducing labor and time, and producing clear, detailed fault trees.
Patent Information
- Application Number
- JP2021183816
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-11-11
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2041-11-11
AI Technical Summary
The manual creation of fault trees from plant system diagrams in probabilistic risk assessment (PRA) models is labor-intensive and time-consuming, necessitating an efficient automated method.
A fault tree creation method and device that utilizes a computer to analyze system diagrams, divide components into blocks, and automatically generate fault trees based on logical conditions, determining block abnormalities that impede system functions.
This approach reduces the time and effort required for fault tree creation, producing concise and understandable fault trees that are equivalent to manual methods, while allowing for detailed analysis.
Smart Images

Figure 0007592000000001 
Figure 0007592000000002 
Figure 0007592000000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a fault tree creation method, a fault tree creation device, and a program. [Background technology]
[0002] A probabilistic risk assessment (PRA) model (hereinafter, referred to as a PRA model) is used for risk assessment of a nuclear power plant. In order to create a PRA model without omissions, devices and the like are comprehensively extracted from a system diagram of the plant, failure modes of the extracted devices and the like are examined, and an event tree and a fault tree are created. Patent Document 1 discloses a system in which devices constituting a system and their malfunction modes are input, malfunction modes of each device are combined to create a hazard scenario leading to the occurrence of a dangerous event, the created hazard scenario is expressed in a flow chart format, and a fault tree is created from the flow chart. Patent Document 1 does not mention creating a fault tree from a system diagram of a plant. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 3622302 Summary of the Invention [Problem to be solved by the invention]
[0004] When constructing a PRA model, the equipment is extracted from the plant system diagram and a fault tree is created, but currently this work is done manually, which requires a lot of labor and time.There is a demand for an efficient method of creating a fault tree from a system diagram.
[0005] The present disclosure provides a fault tree creation method, a fault tree creation device, and a program that can solve the above problems. [Means for solving the problem]
[0006] The method for creating a fault tree to be evaluated according to the present disclosure includes the steps of: 1. A computer-implemented fault tree creation method, comprising: obtaining a system diagram showing the connection relationships of the components of the plant; The computer, calculating a logical condition for a state of the components when a target system loses a function based on a connection relationship between the components of the target system, which is a system to be evaluated and included in the system diagram; The computer, A step of creating a fault tree with the loss of function of the target system as a top event based on the calculated logical conditions. The components are blocks obtained by dividing the target system from the start point to the end point into predetermined ranges, and in the step of calculating the logical condition, when it is assumed that a flow passes from an upstream end to a downstream end of the block in a flow direction from the start point to the end point when the block is normal, and that the flow does not pass when the block is abnormal, the computer calculates the logical condition for one or more of the blocks based on whether or not an abnormality in the one or more blocks inhibits the flow from the start point to the end point. .
[0007] The fault tree creation device of the present disclosure includes: a means for acquiring a system diagram showing the connection relationships of components of a plant; a means for calculating, based on the connection relationships of the components of a target system that is a system to be evaluated and included in the system diagram, a logical condition for the state of the components when the target system loses function; and a means for creating, based on the calculated logical condition, a fault tree in which the loss of function of the target system is a top event. The components are blocks obtained by dividing the target system from the start point to the end point into predetermined ranges, and the means for calculating the logical condition calculates the logical condition for one or more of the blocks based on whether or not an abnormality in one or more of the blocks inhibits the flow from the start point to the end point when it is assumed that a flow passes from an upstream end to a downstream end of the block in a flow direction from the start point to the end point when the block is normal, and that the flow does not pass when the block is abnormal. .
[0008] The program of the present disclosure includes the steps of: acquiring a system diagram showing connections between components of a plant; calculating, based on the connections between the components of a target system that is a system to be evaluated and included in the system diagram, logical conditions for the states of the components when the target system loses function; and creating, based on the calculated logical conditions, a fault tree with the loss of function of the target system as a top event. the components are blocks obtained by dividing the target system from a start point to an end point into predetermined ranges, and in the step of calculating the logical condition, when it is assumed that a flow passes from an upstream end to a downstream end of the block in a flow direction from the start point to the end point when the block is normal, and that the flow does not pass when the block is abnormal, a process of calculating the logical condition for one or more of the blocks based on whether or not an abnormality in the one or more blocks inhibits the flow from the start point to the end point; Execute the command. Effect of the Invention
[0009] According to the above-mentioned fault tree creation method, fault tree creation device, and program, a fault tree can be automatically created from a system diagram. [Brief description of the drawings]
[0010] [Figure 1] 1 is a functional block diagram illustrating an example of a fault tree creation device according to an embodiment. [Figure 2A] FIG. 1 is a first diagram showing an example of system diagram data according to an embodiment. [Figure 2B] FIG. 2 is a second diagram showing an example of system diagram data according to the embodiment. [Figure 2C] FIG. 3 is a third diagram showing an example of system diagram data according to the embodiment. [Figure 3A] 11 is a flowchart illustrating an example of a block division process according to the embodiment. [Figure 3B] FIG. 13 is a diagram showing an example of a system diagram after block division according to the embodiment; [Figure 4] FIG. 4 is a diagram illustrating an example of a device list according to the embodiment. [Figure 5A] 13 is a flowchart illustrating an example of an FT creation process according to the embodiment. [Figure 5B] FIG. 1 is a first diagram illustrating an FT creation process according to an embodiment. [Figure 5C] FIG. 2 is a second diagram illustrating the FT creation process according to the embodiment. [Figure 5D] FIG. 3 is a third diagram illustrating the FT creation process according to the embodiment. [Figure 5E] FIG. 4 is a fourth diagram illustrating the FT creation process according to the embodiment. [Figure 5F] FIG. 5 is a fifth diagram illustrating the FT creation process according to the embodiment. [Figure 6A] FIG. 1 is a first diagram for explaining processing for a branch pipe according to the embodiment. [Figure 6B] FIG. 2 is a second diagram illustrating processing for a branch pipe according to the embodiment. [Figure 7] 4 is a flowchart showing an example of an operation of the fault tree creation device according to the embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of a hardware configuration of a fault tree creation device according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] <Embodiment> Hereinafter, the fault tree creation method of the present disclosure will be described with reference to FIGS. (System Configuration) 1 is a functional block diagram showing an example of a fault tree creation device according to an embodiment. The fault tree creation device 10 automatically creates a fault tree from a system diagram of an evaluation target such as a nuclear power plant. Hereinafter, the fault tree creation device 10 may be referred to as the FT creation device 10, and the fault tree may be referred to as the FT.
[0012] The FT creation device 10 comprises a data acquisition unit 11 that acquires system diagram data to be evaluated, an input acceptance unit 12 that accepts user operations, a control unit 13 that controls the execution of the process of creating a FT from the system diagram data, an output unit 14 that outputs the created FT etc. as a display device or electronic file, and a memory unit 15 that stores the system diagram data, various data being processed, etc.
[0013] (System data) The data acquisition unit 11 acquires system diagram data of a plant such as CAD data. Here, reference is made to Figs. 2A to 2C. Figs. 2A to 2C show a part of CAD data of a certain plant as an example of system diagram data. In the system diagram of Fig. 2A, P1 to P8 indicate pipes, D1 to D3 indicate equipment, C1 to C3 indicate branching points or confluence points, and a start point, an end point 1, and an end point 2 of a fluid flow are shown. For example, a valve D1 connects a pipe P2 to a pipe P3. In addition to the valve D1, a valve D2 and a pipe P8 are connected to the pipe P3 at the branching point C2. In general, CAD data for displaying a plant system diagram includes pipe configuration data exemplified in Fig. 2B and pipe connection data exemplified in Fig. 2C, and the system diagram exemplified in Fig. 2A is output based on these data. Alternatively, the pipe configuration data of Fig. 2B and the pipe connection data of Fig. 2C can be created based on the system diagram of Fig. 2A. The CAD data illustrated in FIG. 2B is an excerpt of data related to the pipe P3, and the CAD data illustrated in FIG. 2C is an excerpt of data related to the pipes P1, P3, and P4.
[0014] As shown in Fig. 2B, the piping configuration data includes information on valves and other equipment connected to each pipe, branching, and merging. As described with reference to Fig. 2A, for example, the pipe P3 is connected to valves D1-D2 and the pipe P8 at the branching point C2. This configuration is set in the second to fourth lines of the piping configuration data in Fig. 2B. That is, for the pipe P3, the TYPE (type of equipment) of the valve D1, the valve D2, and the branching point C2, the merging / branching classification, the size (piping diameter), and the XY coordinate information of the position where the equipment is located are set. The XY coordinate information indicates the coordinate position in the system diagram of Fig. 2A.
[0015] In the pipe connection data of FIG. 2C, connection information between pipes and the flow direction of the fluid flowing through the pipes are set. For example, pipe P3 is connected to pipes P2, P4, and P8. The fluid flows in the direction of pipes P2, P3, and P4, or in the direction of pipes P2, P3, and P8, or in the direction of pipes P8, P3, and P4. In order to define this connection information, pipe P3 is set in the line number column, pipe P2 in the FROM column, and pipes P4 and P8 in the TO column. In addition, in the case where the fluid flows in from pipe P8, pipe P3 is set in the FROM column, pipe P8 in the FROM column, and pipe P4 in the TO column. Similarly, for pipe P4, pipe P3 is set in the FROM column and "end point 1" is set in the TO column, and for pipe P1, "start point" is set in the FROM column, and pipes P2 and P5 in the TO column.
[0016] In this way, the system diagram data (piping configuration data and piping connection data) defines the connection relationships between pipes and between pipes and devices (valves, pumps, etc.), making it possible to analyze junctions and branching points in the system. The data acquisition unit 11 acquires the piping configuration data (FIG. 2B) and the piping connection data (FIG. 2C) as the system diagram data.
[0017] In addition, in FIG. 2A, in addition to the CAD data, the flow direction of the fluid is additionally shown for later explanation. The system illustrated in FIG. 2A performs two functions. The first function is to inject a fluid from a starting point to an end point 1, and the second function is to inject a fluid from a starting point to an end point 2. When the first function (hereinafter referred to as function 1) is performed, the fluid flows into the end point 1 through the pipes P1, P2, P3, and P4. Alternatively, the fluid flows into the end point 1 through the pipes P1, P5, P6, P8, and P4. When the second function (hereinafter referred to as function 2) is performed, the fluid flows into the end point 2 through the pipes P1, P5, P6, and P7. Alternatively, the fluid flows into the end point 2 through the pipes P1, P2, P3, P8, and P7. Pipe P8 is a tie line connecting pipe P3 with pipes P6 and P7, and fluid can flow in either direction from branch point C2 to branch point C3 or from branch point C3 to branch point C2 as shown by the arrows. When creating a FT from the system diagram of FIG. 2A, a FT is created with focus on either function 1 or function 2, with the loss of that function as the top event. In addition, a pipe through which fluid flows to perform the function of interest (a path necessary for achieving the function of the system) is called a main pipe, and a path through which no fluid flows but which should be evaluated to achieve the function of the system is called a branch pipe. For example, in the case of function 1, no fluid flows through pipe P7, but if a leak occurs in pipe P7, it may affect function 1, so pipe P7 is a branch pipe, and the other pipes P1 to P6 and pipe P8 are main pipes. In the case of function 2, pipe P4 is a branch pipe, and the other pipes P1 to P3 and pipes P5 to P8 are main pipes.
[0018] Returning to Figure 1, the input receiving unit 12 is configured to include input devices such as a touch panel and a keyboard, receives operations performed by the user using the input device, generates information according to the operations, and outputs the generated information to the control unit 13.
[0019] The control unit 13 creates a FT from the system diagram data. The control unit 13 includes an analysis unit 131 that analyzes the system diagram data, and a FT creation unit 132 that creates a FT using the analysis results.
[0020] (Dividing into blocks) The analysis unit 131 analyzes the system diagram data and divides the system diagram into blocks. By dividing the system diagram into blocks, one block is regarded as one configuration, and a FT is created with a failure of each configuration as a base event. This makes it possible to automatically create a simple and highly visible FT. Next, with reference to FIG. 3A, the process of dividing the system diagram into blocks will be described. The analysis unit 131 extracts a start point, an end point, a branch point, and a merge point from the system diagram data (step S1). The analysis unit 131 extracts the start point, the end point, the branch point, and the merge point by referring to the "Merge / Branch" column of the piping configuration data (FIG. 2B) and the "FROM" column and the "TO" column of the piping connection data (FIG. 2C). Next, the analysis unit 131 traces from the start point to the end point and sets a block (step S2). The analysis unit 131 repeats tracing the piping from the start point in the downstream direction of the flow and setting one block until it reaches one of the branch point, the merge point, and the end point. A specific description will be given using the system diagram of FIG. 2A as an example. First, the analysis unit 131 divides the flow from the starting point to the end point 1 into blocks. The analysis unit 131 starts from the starting point and traces the pipe P1 downstream. When it encounters the junction C1, the analysis unit 131 sets the area from the starting point to the junction C1 as one block. This block is called BLK001. BLK001 is shown in FIG. 3B. Next, the analysis unit 131 traces the flow from the junction C1 along the pipe P2 downstream and encounters a valve D1, which is not a starting point, an end point, a branch point, or a junction, so it continues to trace downstream along the pipe P3 and reaches the branch point C2. Since the branch point C2 is a branch point to the pipe P8, the analysis unit 131 sets the area from the junction C1 to the branch point C2 as one block, BLK002 (FIG. 3B). Similarly, the analysis unit 131 sets the section from the branch point C2 to the end point 1 as one block, BLK004. The analysis unit 131 performs similar processing on the flow from the junction C1 along the pipe P5, and sets the section from the junction C1 to the branch point C3 as BLK003, and the section from the branch point C3 to the branch point C2 as one block, as illustrated in Fig. 3B. The analysis unit 131 also divides the flow from the start point to the end point 2 into blocks.In the block division from the start point to the end point 2, BLK001, BLK002, and BLK003 already set in the block division from the start point to the end point 1 are set, and in addition, a block from the branch point C2 to the branch point C3 and a block from the branch point C3 to the end point 2 are set as BLK006. Next, the analysis unit 131 handles the tie line (piping P8) (step S3). The analysis unit 131 distinguishes two blocks that have the same equipment on both ends and on the piping and only differ in the flow direction by giving them the same block name (BLK005) and adding "_number". For example, the analysis unit 131 sets the block from the branch point C2 to the branch point C3 as BLK005_1 and the block from the branch point C3 to the branch point C2 as BLK005_2. FIG. 3B shows the system diagram after the block division.
[0021] The analysis unit 131 also creates an equipment list from the system diagram data. An example of the equipment list is shown in Fig. 4. The analysis unit 131 extracts equipment, junctions, and branching points from the system diagram data (Fig. 2B) and creates an equipment list as shown in Fig. 4. The equipment list organizes the functions required of the equipment to be evaluated in the PRA, and is referred to when creating a more detailed FT after creating a FT with block-based failures as the base event based on the system diagram after block division (hereinafter referred to as a block system diagram).
[0022] (Creating a fault tree) The FT creation unit 132 creates a FT from the system diagram after block division (FIG. 3B). Based on the block system diagram of FIG. 3B, the procedure of the FT creation process will be described along the flowchart of FIG. 5A. First, the user specifies a function for which the FT is to be created. For example, when creating a FT for function 1, the user performs an operation to specify function 1 on the FT creation device 10. For example, the user inputs the start point and end point 1 in the block system diagram of FIG. 3B to the FT creation device 10. The input acceptance unit 12 accepts this operation and outputs it to the control unit 13. The control unit 13 sets the start point to the end point 1 as the target of the FT creation (step S11). For example, the control unit 13 records the set start point and end point 1 in the storage unit 15 as the start point and end point of the system to be evaluated. Based on this setting, the FT creation unit 132 identifies blocks that are not the target of processing and blocks composed of branch pipes (step S12). In this example, the FT creation unit 132 sets BLK005_1 of the tie lines as not to be processed, and sets BLK006 as a block made up of branch pipes. The FT creation unit 132 also sets a top event (step S13). The FT creation unit 132 sets "injection into end point 1 not allowed" as the top event. Figure 5B illustrates the results of processing up to step S13. W1 in Figure 5B shows the state in which the FT top event has been set, and W2 shows a block system diagram in which BLK005_1 is not to be processed and BLK006 is a branch pipe.
[0023] Next, the FT creation unit 132 sets the top event as a target event in the FT creation (step S14). Next, the FT creation unit 132 identifies a block that is connected to the target (top event) with OR (step S15). Specifically, the FT creation unit 132 identifies a block that will cause a top event when the block fails. Refer to W2 in FIG. 5C. For each of the blocks to be processed, BLK001 to BLK004 and BLK005_2, the FT creation unit 132 determines whether function 1 will be lost when the block fails. For example, when BLK001 or BLK004 fails, the fluid will not flow from the start point to the end point 1. On the other hand, even if BLK002 fails, the fluid will flow from the start point to the end point 1 by passing through BLK001, BLK003, BLK005_2, and BLK004, so the top event "injection to end point 1 is not possible" does not occur even if BLK002 fails. Furthermore, even if BLK003 or BLK005_2 fails, the routes of BLK001, BLK002, and BLK004 still function, so "injection to end point 1 is not possible" does not occur. For these reasons, the FT creation unit 132 identifies BLK001 and BLK004 as blocks that are directly connected to the top event with OR, and connects these to the top event with OR. W1 in Figure 5C shows a FT being created in which the failures of BLK001 and BLK004 are connected to the top event with OR.
[0024] Next, the FT creation unit 132 executes the following process while tracing blocks one by one upstream from the end point 1 toward the start point (step S16). First, the FT creation unit 132 judges whether there is a branch of two or more blocks upstream (step S17). For example, tracing one block upstream from the end point 1, it is BLK004. Upstream of BLK004, there are two blocks, BLK002 and BLK005_2. In such a case, the judgment in step S17 is Yes. If there is a branch of two or more blocks upstream (step S17; Yes), if all of these blocks fail, it will lead to a top event, so the upstream blocks (BLK002 and BLK005_2) are connected with AND and connected to the target top event with OR (step S18). The processing contents of steps S17 to S18 are shown in W2 of FIG. 5D. W1 in FIG. 5C shows a FT in which the intermediate event "BLK002 failure & BLK005_2 failure" created by connecting the BLK002 failure and the BLK005_2 failure with AND is connected to the top event with OR. If there is no branch with two or more blocks upstream (step S17; No), proceed to step S19. Next, the FT creation unit 132 removes overlapping blocks in the FT being created (step S19). Referring to W1 in FIG. 5D, the blocks included in the FT being created are BLK001, BLK002, BLK004, and BLK005_2, and there is no overlap, so no blocks are deleted.
[0025] Next, the FT creation unit 132 changes the target (step S20). For example, since there is currently a branch between BLK005_2 and BLK002 one block upstream from BLK004, it moves to BLK005_2 or BLK002 (follows one block upstream) and sets the target event to "injection not allowed to the destination block." Here, it is assumed to move to BLK005_2. In this case, the FT creation unit 132 sets "injection not allowed to the end point of BLK005_2" as the target. In addition, the FT creation unit 132 changes the basic event "fault of BLK005_2" in the FT to "injection not allowed to the end point of BLK005_2." Next, the FT creation unit 132 judges whether the start point has been reached (step S21). Since the start point has not been reached, the judgment in step S21 is No. If the start point has not been reached (step S21; No), the process from step S15 is repeated.
[0026] The FT creation unit 132 targets the path of BLK005_2, BLK003, and BLK001 when tracing from BLK005_2 to the starting point, identifies a block that, if the block fails, will prevent the fluid from flowing from the starting point to the end point of the target BLK005_2 (step S15), and connects the identified block to the target "injection not allowed to end point of BLK005_2" with OR. In this example, if any of BLK005_2, BLK003, and BLK001 fails, "injection not allowed to end point of BLK005_2" occurs, so BLK005_2, BLK003, and BLK001 are connected to the target "injection not allowed to end point of BLK005_2" with OR. W2 in FIG. 5E shows the processing content of step S15 this time, and W1 shows an FT in which the targets BLK005_2 failure, BLK003 failure, and BLK001 failure are connected with OR to the current target event “Injection to BLK005_2 endpoint not possible.”
[0027] Next, the FT creation unit 132 judges whether there are multiple blocks branching upstream (step S17). Since there is no branching to multiple blocks even when tracing upstream from BLK005_2, the judgment in step S17 is No. Next, the FT creation unit 132 removes overlapping blocks in the FT being created (step S19). Referring to the FT of W1 in FIG. 5E, the "BLK001 failure" connected to the top event with OR and the "BLK001 failure" connected to the current target "Cannot inject into BLK005_2 end point" with OR are overlapping. In such a case, the "BLK001 failure" set in the upper layer of the FT is left, and the "BLK001 failure" connected to the current target in the lower layer is removed. The FT after removal is shown in FIG. 5F.
[0028] Next, the FT creation unit 132 moves one block upstream, changes the target to "BLK003 end point injection not allowed", and executes the process from step S15 onwards. If the target is set to BLK003, the block identified in step S15 overlaps with a block already set in the upper hierarchy, and is therefore excluded in step S19. Also, there is no point upstream where the block branches into multiple blocks (step S17; No). In other words, the FT is not changed with the movement of the target. In this case, the FT creation unit 132 returns the target "BLK003 end point injection not allowed" to "BLK003 failure". Next, the FT creation unit 132 changes the target to "BLK001 end point injection not allowed" and executes the process from step S15 onwards. The process in this case is the same as that in the case of BLK003. Next, the FT creation unit 132 changes the target to "BLK002 end point injection not allowed" and executes the process from step S15 onwards. This case is also the same as that in the case of BLK003. Next, the FT creation unit 132 changes the target to "BLK001 Cannot be injected into the end point" and executes the process from step S15 onwards, but this process has already been executed. Next, the FT creation unit 132 determines that the start point has been reached (step S21) and ends the flowchart in Figure 5A. The finally created FT is shown in Figure 5F.
[0029] (Treatment of branch pipes) Next, a process of adding a block composed of a branch pipe to an FT will be described with reference to FIGS. 6A and 6B. FIG. 6A shows an example of a block system diagram. In the block system diagram of FIG. 6A, a block BLK007 is added to the block system diagram of FIG. 3B. In BLK007, a fluid flows in the direction of the arrow. From the viewpoint of function 1 of injecting from the starting point to the end point 1, BLK007 is not an injection path of the fluid, and therefore is a branch pipe like BLK006. BLK006 and BLK007 are not directly involved in "injection into end point 1 is not possible", but if a leak occurs in BLK006 or BLK007, for example, it may affect the entire system and cause "injection into end point 1 is not possible". Therefore, a branch pipe failure is connected to a top event. Specifically, the FT creation unit 132 connects blocks corresponding to branch pipes with OR to aggregate them as "branch pipe failure", and connects the aggregated "branch pipe failure" to the top event with OR. Figure 6B illustrates an example of FT with the addition of a "branch pipe failure."
[0030] (Overall process flow) Next, the overall flow of the fault tree creation process will be described with reference to FIG. First, the data acquisition unit 11 acquires system diagram data exemplified in FIG. 2B to FIG. 2C (step S31), and records the acquired system diagram data in the storage unit 15. Next, the analysis unit 131 performs block division (step S32). The analysis unit 131 creates a block system diagram exemplified in FIG. 3B, FIG. 6B, etc. from the system diagram data acquired in step S31. This process has been described with reference to FIG. 3A. Next, the user designates a target function of the FT (for example, function 1). The control unit 13 sets a target function of the FT based on this designation (step S33). This process corresponds to step S11 in FIG. 5A. Next, the FT creation unit 132 separates the main pipe from the branch pipe (step S34). Based on the function set in step S33, the FT creation unit 132 sets a block necessary for the performance of the function as the main pipe, and sets a block that is not necessary for the performance of the function but affects the performance of the function due to the failure of the block as a branch pipe. For example, the FT creation unit 132 sets a block that is connected to the main pipe and is not included in the flow path from the start point to the end point as a branch pipe. This process corresponds to step S12 in FIG. 5A. Next, the FT creation unit 132 creates a FT for the block classified as the main pipe (step S35). The FT creation unit 132 creates a FT as described with reference to FIG. 5A. This process corresponds to steps S13 to S21 in FIG. 5A. Next, the FT creation unit 132 aggregates the branch pipes and adds them to the FT (step S36). The FT creation unit 132 aggregates the branch pipes and adds them to the FT as described with reference to FIGS. 6A to 6B. Next, the output unit 14 outputs the created FT to a display device or the like (step S37). The FT creation unit 132 specifies the FT structure using an arbitrary data format (text data) that expresses the tree structure of the FT, and this text data is stored in the storage unit 15. The output unit 14 reads out the text data in which the FT structure is defined from the storage unit 15, converts it into an image of the FT as exemplified in FIG. 6B etc. using predetermined software, and outputs this image.
[0031] (effect) Conventionally, devices and the like are manually extracted from a system diagram, and failure modes of the extracted devices and the like are examined to create a fault tree. In contrast, according to the present embodiment, by simply inputting system diagram data, a logical condition of a base event (e.g., a failure of a component) is determined based on the connection relationship of the components, and a fault tree is automatically created. This can reduce the work time and workload required for creating a fault tree. In addition, by dividing and capturing the components described in the system diagram into certain groups (blocks), a simple and systematic fault tree that is easy for engineers to understand can be generated. If necessary, a more detailed fault tree can be created by referring to the device list exemplified in FIG. 4, and in this case, a simple automatically created fault tree can be used, thereby reducing the workload. In addition, by searching for an injection route and distinguishing between the injection route (main piping) and the rest in the same way as when creating a fault tree manually, a fault tree equivalent to that created by manual work can be generated.
[0032] In the above embodiment, in order to create a PRA model for reliability evaluation of a nuclear power plant, the target range of the reliability evaluation is extracted based on the CAD data of the system diagram of the nuclear power plant, but the application field of the FT creation device 10 is not limited to the reliability evaluation of the nuclear power plant. In addition, it is possible to apply the FT creation device 10 to industrial fields where reliability evaluation is performed by other methods, not limited to the PRA model. In addition, the system diagram is not limited to the plant, and may be a system diagram of electrical wiring or a system diagram of a control system.
[0033] In addition, in the above embodiment, an example has been described in which a single block is divided each time a branch point, a junction point, or an end point is reached from the starting point. However, the method of dividing the blocks is not limited to this. For example, each time a device is reached while tracing from the starting point to the end point, each area obtained by breaking down the device and the piping connecting the device may be treated as a block.
[0034] In addition, in the above embodiment, an example of selecting a start point and an end point 1 to specify a target function of an FT is described, but the method of specifying a target function of an FT is not limited to this, and for example, blocks that are not subject to processing or branch pipes may be arbitrarily changed by setting intermediate points.
[0035] 8 is a diagram showing an example of the hardware configuration of a fault tree creation device according to an embodiment. A computer 900 includes a CPU 901, a main storage device 902, an auxiliary storage device 903, an input / output interface 904, and a communication interface 905. The above-described fault tree creation device 10 is implemented in a computer 900. Each of the above-described functions is stored in the auxiliary storage device 903 in the form of a program. The CPU 901 reads the program from the auxiliary storage device 903, loads it in the main storage device 902, and executes the above-described processing in accordance with the program. The CPU 901 also reserves a storage area in the main storage device 902 in accordance with the program. The CPU 901 also reserves a storage area in the auxiliary storage device 903 for storing data being processed in accordance with the program.
[0036] In addition, a program for realizing all or part of the functions of the fault tree creation device 10 may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into a computer system and executed to perform processing by each functional unit. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. In addition, if a WWW system is used, the term "computer system" also includes a homepage providing environment (or display environment). In addition, the term "computer-readable recording medium" refers to a portable medium such as a CD, DVD, or USB, and a storage device such as a hard disk built into a computer system. In addition, if the program is distributed to the computer 900 through a communication line, the computer 900 that receives the program may deploy the program in the main storage device 902 and execute the above processing. In addition, the above program may be for realizing part of the above-mentioned functions, and may further be capable of realizing the above-mentioned functions in combination with a program already recorded in the computer system.
[0037] As described above, several embodiments according to the present disclosure have been described, but all of these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents as described in the claims, as well as in the scope and gist of the invention.
[0038] <Additional Notes> The fault tree creation method, the fault tree creation device, and the program described in each embodiment can be understood, for example, as follows.
[0039] (1) A first aspect of a method for creating a fault tree for an evaluation target includes the steps of: acquiring a system diagram showing the connections of components of a plant (S31); calculating, based on the connections of the components of a target system that is the evaluation target system included in the system diagram, logical conditions for the state of the components when the target system loses function (S15 to S18, S36); and creating, based on the calculated logical conditions, a fault tree in which the loss of function of the target system is the top event (S35, S36). This makes it possible to automatically create a fault tree from a system diagram of a plant, etc.
[0040] (2) A second aspect of the fault tree creation method for an evaluation target is the fault tree creation method of (1), wherein the components are blocks obtained by dividing the target system from its start point to its end point into predetermined ranges, and when the block is normal, a flow passes from the upstream end to the downstream end of the block in the flow direction from the start point to the end point, and when the block is abnormal, the flow does not pass. In this case, the logical condition for one or more of the blocks is calculated based on whether or not an abnormality in one or more of the blocks obstructs the flow from the start point to the end point (S15, S18). If the flow is interrupted, a logical condition is calculated so that one or more blocks are connected to the top event by OR. By such processing, a fault tree can be automatically created.
[0041] (3) A fault tree creation method according to a third aspect is a fault tree creation method according to (1) to (2), in which the blocks are each range obtained by decomposing the target system from its start point to its end point into each branch point or junction point (Figure 3A). This makes it possible to automatically create a FT by the process in FIG. 5A, making it possible to create a simple and clear FT.
[0042] (4) A fault tree creation method according to a fourth aspect is a fault tree creation method according to (2) to (3), in which, when an abnormality in the block causes a flow from the start point to the end point of the system to be interrupted, the block is connected to a top event of the fault tree with an OR condition (S15). Such processing allows the structure connected to the top event in the fault tree to be determined.
[0043] (5) A fault tree creation method according to a fifth aspect is a fault tree creation method according to (2) to (3), in which the blocks are traced from the end point upstream in the system, and if there are branches to multiple blocks upstream, the multiple blocks are connected with an AND condition, and the multiple blocks connected with the AND condition are connected to a top event with an OR condition (S18). Such processing allows the structure connected to the top event in the fault tree to be determined.
[0044] (6) A fault tree creation method according to a sixth aspect is the fault tree creation method of (5), in which, when each of the plurality of blocks is an intermediate block, if an abnormality in a block upstream of the intermediate block prevents a flow from the starting point to the end of the intermediate block, the block is connected to the intermediate block with an OR condition (S15). By such processing, the structure of the lower hierarchical levels in the fault tree can be determined.
[0045] (7) A fault tree creation method according to a seventh aspect is a fault tree creation method according to (5) to (6), in which the blocks are traced upstream from the intermediate block, and if there are branches to multiple blocks upstream, the multiple blocks are connected together with an AND condition, and the multiple blocks connected with the AND condition are connected to the intermediate block with an OR condition (S18). By such processing, the structure of the lower hierarchical levels in the fault tree can be determined.
[0046] (8) A fault tree creation method according to an eighth aspect is a fault tree creation method according to any one of (2) to (7), in which, for a branch pipe that is connected to the target system and is not included in the flow path from the starting point to the end point, if there is one branch pipe, the branch pipe is connected to a top event with an OR condition, and if there are two or more branch pipes, the branch pipes are grouped together and connected to the top event with an OR condition, and each of the branch pipes is connected to each other under the grouped branch pipe with an OR condition. This makes it possible to add branch pipes to the FT that will affect its function in the event of an abnormality.
[0047] (9) A fault tree creation device 10 according to a tenth aspect includes a means for acquiring a system diagram showing the connection relationships of components of a plant, a means for calculating logical conditions for the state of the components when a target system, which is a system to be evaluated and included in the system diagram, loses function based on the connection relationships of the components, and a means for creating a fault tree in which the loss of function of the target system is the top event based on the calculated logical conditions.
[0048] (10) A program according to an eleventh aspect causes a computer 900 to execute the steps of: acquiring a system diagram showing the connections of components of a plant; calculating, based on the connections of the components of a target system that is a system to be evaluated and included in the system diagram, logical conditions for the state of the components when the target system loses function, based on the calculated logical conditions; and creating a fault tree in which the loss of function of the target system is the top event. [Explanation of symbols]
[0049] 10. Fault tree creation device 11 Data acquisition section 12 Input reception section 13. Control section 131...Analysis Department 132 ···FT Creation Department 14 Output section 15...Storage section 900...Computer 901···CPU 902...Main memory 903...Auxiliary storage device 904 Input / Output Interface 905 Communication Interface
Claims
1. A computer-implemented method for creating a fault tree, comprising: The computer acquires a system diagram showing a connection relationship of components of a plant; a step of calculating, by the computer, a logical condition for a state of the components of a target system, which is a system to be evaluated and is included in the system diagram, when the target system loses a function, based on a connection relationship between the components of the target system; A step of generating a fault tree in which a top event is a loss of function of the target system based on the calculated logical conditions by the computer; having The components are blocks obtained by dividing the target system from the start point to the end point into predetermined ranges, and in the step of calculating the logical condition, when it is assumed that a flow passes from the upstream end to the downstream end of the block in the flow direction from the start point to the end point when the block is normal, and that the flow does not pass when the block is abnormal, the computer calculates the logical condition for one or more of the blocks based on whether or not an abnormality in the one or more blocks obstructs the flow from the start point to the end point. How to create a fault tree.
2. The blocks are each range obtained by decomposing the starting point to the end point of the target system at each branch point or junction point. The method for creating a fault tree according to claim 1 .
3. When a flow from the start point to the end point of the target system is blocked due to an abnormality in the block, the computer connects the block to a top event of the fault tree using an OR condition.
3. The fault tree creation method according to claim 1 or 2.
4. the computer traces the blocks from the end point upstream in the target system, and when there are branches to a plurality of the blocks upstream, connects the plurality of the blocks together with an AND condition, and connects the plurality of the blocks connected with the AND condition to a top event with an OR condition; A fault tree creation method according to any one of claims 1 to 3.
5. When each of the plurality of blocks is an intermediate block, if a flow from the starting point to the intermediate block cannot pass due to an abnormality in the block present upstream of the intermediate block, the computer connects the block to the intermediate block with an OR condition. The fault tree creation method according to claim 4 .
6. the computer traces the blocks from the intermediate block upstream, and when there are branches to a plurality of the blocks upstream, connects the plurality of the blocks together under an AND condition, and connects the plurality of the blocks connected under the AND condition to the intermediate block under an OR condition; The fault tree creation method according to claim 5 .
7. With respect to branch pipes that are connected to the target system and are not included in the flow path from the starting point to the end point, the computer groups the branch pipes together and connects them to a top event under an OR condition, and connects each of the branch pipes under the grouped branch pipes to each other under an OR condition. A fault tree creation method according to any one of claims 1 to 6.
8. A means for acquiring a system diagram showing the connection relationship of components of a plant; means for calculating a logical condition for a state of the components of a target system, which is a system to be evaluated and is included in the system diagram, when the target system loses a function, based on a connection relationship between the components of the target system; A means for creating a fault tree in which a top event is the loss of function of the target system based on the calculated logical conditions; having the components are blocks obtained by dividing the target system from the start point to the end point into predetermined ranges, and the means for calculating the logical condition calculates the logical condition for one or more of the blocks based on whether or not an abnormality in one or more of the blocks inhibits the flow from the start point to the end point when it is assumed that a flow passes from an upstream end to a downstream end of the block in a flow direction from the start point to the end point when the block is normal, and that the flow does not pass when the block is abnormal; Fault tree creation device.
9. On the computer, obtaining a system diagram showing the connection relationships of the components of the plant; calculating a logical condition for a state of the components when a target system loses a function based on a connection relationship of the components in the target system, which is a system to be evaluated and included in the system diagram; creating a fault tree with a top event being the loss of function of the target system based on the calculated logical conditions; having the components are blocks obtained by dividing the target system from the start point to the end point into predetermined ranges, and in the step of calculating the logical condition, when it is assumed that a flow passes from an upstream end to a downstream end of the block in a flow direction from the start point to the end point when the block is normal, and when it is assumed that the flow does not pass when the block is abnormal, a process of calculating the logical condition for one or more of the blocks based on whether or not an abnormality in the one or more blocks inhibits the flow from the start point to the end point; A program that executes the following.
Citation Information
Patent Citations
Simulation condition setting apparatus, simulation condition setting method, and drive training assist system
JP2016145917A
Risk analysis assistance device, risk analysis assistance method, and risk analysis assistance program
JP2020017238A
Process safety evaluation procedure creation device
JP3622302B2
