Apparatus for generating fault tree and method for generating fault tree using same

Abstract

The present invention relates to an apparatus for generating a fault tree and a method for generating a fault tree using same and, more specifically, to an apparatus for generating a fault tree and a method for generating a fault tree using same, whereby a fault tree is generated on the basis of a resource flow diagram, and a final fault tree is generated by extracting fault tree configuration items for each layer according to flow lines of the resource flow diagram and sequentially generating fault trees according to layer. To this end, the present invention relates to an apparatus for generating a fault tree on the basis of a resource flow diagram composed of a plurality of components, the apparatus for generating a fault tree comprising a control unit for generating a final fault tree by extracting fault tree configuration items including an input start point, an output destination, a simple component, and a composite component on the basis of the received resource flow diagram, and using the fault tree configuration items to sequentially generate fault trees according to layer.

Description

Fault tree generation device and fault tree generation method using the same

[0001] The present invention relates to a fault tree generation device and a fault tree generation method using the same, and more particularly, to a fault tree generation device and a fault tree generation method using the same, which generate a fault tree based on a resource flow diagram, extract fault tree configuration items for each layer along a flow line of the resource flow diagram, and sequentially generate fault trees for each layer, thereby generating a final fault tree.

[0002] In general, a fault tree is a method of deductively tracing failure scenarios and events. In the past, a fault tree developer reviewed the P&ID (Pipe and Instrumentation Diagram) of the corresponding resource supply system (cooling water, electricity, signal, etc.), and based on the overall success / failure conditions of the system, removed parts that were not related to success / failure, and produced a core simple resource flow diagram, which was then manually converted into a fault tree by an analyst.

[0003] Accordingly, it takes a lot of time to write and has the disadvantage that errors due to illusory errors can often occur, especially in distinguishing between success and failure.

[0004] Furthermore, existing fault trees typically have limitations in representing failures of components within a system. For example, pumps and valves, frequently considered in fluid flow diagrams, are key components of the system. When these components fail, the same logic can be expressed in a wide variety of ways, depending on the developer.

[0005] Failure descriptions for valves include events such as (1) fail to start, (2) fail to run, (3) common cause failure, (4) electrical support failure, (5) cooling failure, and (6) signal failure. These can be expressed in a wide variety of ways. Because these diverse failure types are not standardized, there is a risk of inconsistency in their writing and review, increasing the likelihood of errors.

[0006] In addition, circular logic may occur in large-scale fault trees, and this circular logic may cause various problems in fault tree creation as this auxiliary relationship is returned in a system that receives assistance from electricity or cooling to perform a specific function.

[0007] (Patent Document 1) Korean Publication No. 10-2018-0046524 (Published: May 9, 2018)

[0008] The present invention has been devised to solve the above problems, and extracts fault tree components based on a resource flow diagram, sequentially generates fault trees by layering the fault tree components to generate a final fault tree, thereby increasing intuitive understanding and drastically reducing the time and errors in fault tree development, and provides a fault tree generation device capable of automatically generating a fault tree using a resource flow diagram and a fault tree generation method using the same.

[0009] The present invention has the following features to solve the above problems.

[0010] The present invention relates to a fault tree generation device that generates a fault tree based on a resource flow diagram composed of a plurality of components, wherein the fault tree generation device includes a control unit that extracts fault tree configuration items including an input starting point, an output arrival point, a simple component, and a complex component based on a received resource flow diagram, and sequentially generates a fault tree by connecting the fault tree configuration items according to layers, thereby generating a final fault tree.

[0011] Here, the control unit generates a fault tree of the first layer in which the fault tree configuration items are serially connected along the flow line of the resource flow diagram, and if there is a composite component among the fault tree configuration items constituting the fault tree of the first layer, the control unit first decomposes the composite component into a configuration of a plurality of branched simple components or lower composite components to generate a fault tree of the second layer.

[0012] In addition, if there is a lower-level complex component among the fault tree configuration items constituting the fault tree of the second layer, the control unit decomposes the lower-level complex component into a configuration of a plurality of simple components or lower-level complex components branching along the flow line of the resource flow diagram, and decomposes it (N-1) times until the fault tree configuration items are composed of only a plurality of simple components, thereby generating a fault tree of the Nth layer. (Here, N is a natural number, and 3≤N.)

[0013] In addition, the control unit includes an item extraction unit that extracts layer-by-layer fault tree configuration items based on the received resource flow diagram; and a fault tree generation unit that sequentially generates layer-by-layer fault trees based on the resource flow diagram and layer-by-layer fault tree configuration items, thereby generating a final fault tree.

[0014] In addition, the above composite component includes a plurality of simple components or lower composite components that are configured by branching along a flow line of a resource flow diagram, and the lower composite components are included as fault tree configuration items within the upper composite component, and a plurality of simple components or lower composite components are included as fault tree configuration items inside.

[0015] In addition, the fault tree generation unit positions the output arrival point, which is the last point reached along the flow line of the resource flow diagram when constructing the fault tree of the first layer, at the top, and places the input starting point, which is the point starting from the flow line of the resource flow diagram, and the simple component or composite component connected in series therewith, respectively, spaced to the left and right below the output arrival point, and connects the output arrival point to receive fault information from the input starting point, simple component, or composite component.

[0016] In addition, when the fault tree generation unit configures the fault tree of the second layer, if there is a composite component in the fault tree of the first layer, it places the simple component or the lower composite component included in the composite component to the left and right of the lower side of the composite component, and connects them to receive fault information.

[0017] In addition, when configuring a fault tree of the Nth layer, if there is a lower complex component in the fault tree of the (N-1)th layer, the fault tree generation unit places the simple components or lower complex components included in the lower complex component to the left and right of the lower side of the lower complex component, and connects them to receive fault information. (Here, N is a natural number, and 3≤N.)

[0018] In addition, the above item extraction unit generates a layer flowchart that sequentially displays fault tree configuration items by layer based on the resource flowchart, and the above fault tree generation unit sequentially generates a fault tree for each layer based on the above layer flowchart.

[0019] In addition, the item extraction unit displays a node for each layer between the fault tree configuration items for each layer in the layer flowchart, and the fault tree generation unit classifies the fault information of the fault tree configuration items according to the fault mode and the fault type and connects them to receive the fault information, wherein the fault information according to the fault mode includes at least one of a start failure event and an operation failure event, and the fault information according to the fault type includes at least one of a component itself failure and an auxiliary system failure.

[0020] In addition, failure information due to failure of the component itself includes at least one of an independent failure, a common cause failure, and a human error, and failure information due to failure of the auxiliary system includes at least one of a cooling failure, a power supply failure, a signal transmission failure, and failure information due to a user setting.

[0021] Meanwhile, as a fault tree generation method according to an embodiment of the present invention, the control unit includes the steps of: a) extracting fault tree configuration items including an input starting point, an output arrival point, a simple component, and a complex component based on a received resource flow diagram, and generating a fault tree of a first layer, which is a fault tree of a serial structure; b) determining whether there are fault tree configuration items of a lower layer; and c) decomposing the fault tree configuration items of the lower layer if there are any, generating a fault tree of the corresponding layer, returning to step b), and generating a fault tree of the corresponding layer as a final fault tree if there are no fault tree configuration items of the lower layer.

[0022] Here, the above composite component includes a plurality of simple components or lower composite components that are configured by branching along a flow line of a resource flow diagram, and the lower composite components are included as fault tree configuration items within the upper composite component, and a plurality of simple components or lower composite components are included as fault tree configuration items inside.

[0023] In addition, the control unit includes an item extraction unit that extracts layer-by-layer fault tree configuration items based on the received resource flow diagram; and a fault tree generation unit that sequentially generates layer-by-layer fault trees based on the resource flow diagram and layer-by-layer fault tree configuration items, thereby generating a final fault tree.

[0024] According to the present invention, by using a resource flow diagram as an interface for creating a fault tree, intuitive understanding can be increased and the time and errors in developing a fault tree can be drastically reduced, and there is an effect of automatically generating a fault tree using a resource flow diagram instead of developing a fault tree manually in the past.

[0025] In addition, it has the effect of minimizing and optimizing the fault tree size by using the layer concept and eliminating the possibility of errors through standardization of component fault structures.

[0026] Additionally, it has the effect of eliminating circular logic relationships in the system by automatically setting up system mutual assistance relationships and eliminating the possibility of errors, and adding failure information by failure mode and failure type.

[0027] FIG. 1 is a drawing showing a fault tree generation device according to one embodiment of the present invention.

[0028] Figure 2 is a diagram showing an example of a resource flow diagram.

[0029] FIG. 3 is a drawing showing a layer flow diagram having a second layer according to one embodiment of the present invention.

[0030] Figure 4 is a drawing showing Figure 3 as a layer flow diagram having a first layer.

[0031] Figure 5 is a diagram showing a fault tree of the first layer generated based on the layer flow diagram of Figure 4.

[0032] FIG. 6 is a diagram showing a fault tree of the second layer by decomposing composite component 1 and composite component 2 of FIG. 5.

[0033] Figure 7 is a diagram including additional fault tree items from Figure 6.

[0034] FIG. 8 is a diagram showing a failure tree of a simple component by failure type and failure mode of the component according to another embodiment of the present invention.

[0035] Figure 9 is a flowchart showing a fault tree generation method according to one embodiment of the present invention.

[0036] In order to explain the present invention, its operational advantages, and the purpose achieved by the practice of the present invention, preferred embodiments of the present invention are exemplified and examined with reference thereto below.

[0037] First, the terms used in this application are only used to describe specific embodiments and are not intended to limit the present invention, and the singular expression may include plural expressions unless the context clearly indicates otherwise. In addition, it should be understood that the terms “comprise” or “have” in this application are intended to specify the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, and do not exclude in advance the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

[0038] In describing the present invention, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description will be omitted.

[0039] FIG. 1 is a drawing showing a fault tree generation device according to one embodiment of the present invention, and FIG. 2 is a drawing showing an example of a resource flow diagram.

[0040] Referring to the drawings, a fault tree generation device (1000) according to an embodiment of the present invention is largely composed of an input unit (200) that receives a resource flow chart composed of a plurality of components, a control unit (100) that extracts fault tree configuration items (111) including an input starting point (111a), an output arrival point (111d), a simple component (111b), and a complex component (111c) based on the resource flow chart received from the input unit (200), and sequentially generates a fault tree by connecting the fault tree configuration items (111) according to layers to thereby generate a final fault tree, and an output unit (300) that receives the final fault tree from the control unit (100) and transmits it to the outside or outputs it through a display means.

[0041] Here, the resource flow diagram means a diagram that expresses using flow lines and components that a specific resource (e.g., cooling water, electricity, signal, etc.) is supplied to a necessary location after going through a processing process, as illustrated in Fig. 2.

[0042] In the case of Figure 2, a resource flow diagram for supplying emergency cooling water to a nuclear power plant is shown, showing the process in which cooling water is supplied from the tank (1) on the upper left through components such as a valve (3) and a pump (2) to the feed nozzle of the reactor coolant system.

[0043] In the present invention, the control unit (100) automatically generates a fault tree based on such a resource flow diagram. By generating a fault tree based on such a resource flow diagram, intuitive understanding can be improved and the fault tree generation time and errors can be shortened.

[0044] Meanwhile, the control unit (100) first extracts an input starting point (111a) and an output arrival point (111d) along a flow line in the resource flow chart based on the resource flow chart received as described above, and extracts a plurality of simple components (111b) and complex components (111c) in the process of moving from the input starting point (111a) to the output arrival point (111d).

[0045] Here, the input starting point (111a) is the starting point of the resource flow diagram, which may be a resource storage such as a tank or a battery, or may be started by receiving an external output and may be expressed in the form of a simple component.

[0046] Additionally, the output destination (111d) is the final point where a resource reaches in the resource flow diagram and can be an input point for a specific storage or another system. There can be two or more output destinations (111d).

[0047] In addition, the above simple component (111b) refers to one individual component, and the above composite component (111c) refers to one set of a plurality of such simple components (111b) connected by a flow line of a resource flow diagram.

[0048] The above composite component (111c) can be displayed to include composite components of separate sub-concepts, and in the present invention, the sub-concepts of the composite component (111c) are expressed as layers, and a final fault tree is created through sequential fault tree creation according to the layers.

[0049] The concept of layer in this resource flow diagram is that, as described above, a set of elements that can be merged into a composite component (111c) in the flow of resources from an input starting point (111a) to an output destination point (111d) is merged into a composite component (111c) to represent a layer flow diagram in a serial structure of a plurality of simple components (111b) or composite components (111c), and this can be defined as a layer flow diagram of the first layer.

[0050] Then, if there is a composite component (111c) in the first layer, it can be decomposed into a plurality of simple components or sub-complex components (111c) branching along the flow line in the resource flow diagram and displayed in the layer flow diagram of the second layer.

[0051] In addition, if there is a lower complex component (111c) in the layer flow chart of the second layer, it can be decomposed again and displayed as a layer flow chart of the third layer, and the layer flow chart of the Nth layer can be displayed by continuously decomposing it until it is displayed as only simple components (111b).

[0052] Here, the layer flow diagram is expressed by grafting the layer concept onto the resource flow diagram, and the control unit (100) according to the present invention sequentially displays the layer flow diagram according to each layer when generating the final fault tree, and generates a fault tree for each layer, and when the final layer is reached, the final fault tree is generated.

[0053] Of course, the above layer flowchart is conceptually displayed by layer to generate a final fault tree by the control unit (100) according to one embodiment of the present invention, and the present invention is not limited thereto.

[0054] In addition, in the layer flowchart above, a node (112) may be displayed to distinguish each layer. This node (112) is displayed as a node in a specific layer, and since resources between composite components (111c) or simple components (111b) are not separated, each layer displays at least two nodes (112).

[0055] The above node may also be displayed between a composite component (111c) or a simple component (111b), and may also be displayed between a node and a composite component (111c) or a node and a simple component (111b).

[0056] That is, a second layer node can be displayed between the first layer node and the second layer fault tree configuration item.

[0057]

[0058] Below, we will examine in more detail the process of creating a final fault tree by extracting the fault tree configuration items (111) for each layer of the control unit (100) and creating a layer flow diagram for each layer.

[0059] FIG. 3 is a drawing showing a layer flow chart having a second layer according to one embodiment of the present invention, FIG. 4 is a drawing showing FIG. 3 as a layer flow chart having a first layer, FIG. 5 is a drawing showing a fault tree of the first layer generated based on the layer flow chart of FIG. 4, FIG. 6 is a drawing showing a fault tree of the second layer by decomposing composite component 1 and composite component 2 of FIG. 5, and FIG. 7 is a drawing including additional fault tree items in FIG. 6.

[0060] Referring to the drawing, as described above, the control unit (100) of the present invention includes an item extraction unit (110) that extracts layer-by-layer fault tree configuration items (111) based on the received resource flow diagram, and generates a layer flow diagram for each layer by connecting and displaying the extracted fault tree configuration items (111) along flow lines, and a fault tree generation unit (120) that sequentially generates layer-by-layer fault trees based on the resource flow diagram, the layer-by-layer fault tree configuration items (111), and the layer flow diagram for each layer, thereby generating a final fault tree.

[0061] Here, the above item extraction unit (110) extracts a fault tree configuration item (111) for each layer based on the resource flow diagram. First, as shown in FIG. 4, a fault tree configuration item (111) having a first layer in which the resource flow is connected in the form of a serial structure from the input starting point (111a) to the output arrival point (111d) is extracted.

[0062] Of course, in order to extract a fault tree configuration item (111) having a first layer like this, a final layer flow chart detailed for each layer is first derived based on the resource flow chart as in Fig. 3, and through this, a layer flow chart of the first layer is produced to sequentially generate a fault tree in layer order.

[0063] That is, the item extraction unit (110) according to the present invention first extracts a plurality of simple components (111b) based on a resource flow diagram, and can merge some of the simple components (111b) into a composite component (111c) along the flow line of the resource flow diagram, and sequentially merges them 1 to N times to create a layer flow diagram of the first layer in which the fault tree configuration items (111) are displayed only in a serial structure.

[0064] Then, the fault tree generation unit (120) generates a fault tree of the first layer as shown in Fig. 5 based on the layer flow chart of the first layer, and again, in the item extraction unit (110), if there is a composite component (111c) among the fault tree configuration items (111) of the first layer, it is decomposed for the first time to generate a layer flow chart of the second layer.

[0065] In addition, the fault tree generation unit (120) arranges fault tree configuration items into simple components (111b) or lower complex components (111c) decomposed left and right on the lower side of the fault tree configuration items for the composite component (111c) in the fault tree of the first layer based on the layer flow diagram of the second layer.

[0066] The resource flow diagram of Fig. 3 is a resource flow diagram arbitrarily illustrated for the fault tree generation process. In the case of Fig. 3, there are two complex components (111c), but they can all be represented as simple components (111b) in the second layer, so the final fault tree has a second layer.

[0067] However, these layers can be displayed up to the 3rd layer to the Nth layer when the resource flow diagram is complex.

[0068] To express this in general terms, if there is a lower composite component (111c) among the fault tree configuration items constituting the fault tree of the Nth layer, the fault tree generation unit (120) decomposes the lower composite component (111c) into a configuration of a simple component (111b) or a lower composite component (111c) branching along the flow line of the resource flow diagram (N-1), and continues decomposing (N-1) times until the fault tree configuration items are composed of only a plurality of simple components, and generates the fault tree of the Nth layer. At this time, N is a natural number, and 3≤N.

[0069] In addition, when the fault tree generation unit (120) configures the fault tree of the Nth layer, if there is a lower complex component (111c) in the fault tree of the (N-1)th layer, it arranges the simple component (111b) or the lower complex component (111c) included in the lower complex component (111c) to the left and right of the lower side of the lower complex component (111c) and connects them to receive fault information from them.

[0070] In this way, the creation of a layer flowchart and a fault tree generation configuration using the layer concept can induce minimization and optimization of the fault tree size by more clearly processing the fault tree construction process, and can minimize the possibility of errors during automated implementation.

[0071] In addition, as illustrated in FIG. 5, the fault tree of the first layer of the serial structure has the fault tree configuration item (SYSTEM_FAIL) corresponding to the output arrival point (111d) placed at the top, and on the left and right below it, the fault tree configuration item (INPUT_FAILURE) corresponding to the input starting point (111a) and the fault tree configuration item (COMPLEX_COM1_FAILURE) corresponding to the first composite component (111c) are placed, respectively, and the output arrival point (111d) receives input from these as an OR gate.

[0072] In the case of components that are connected in series in the layer flowchart, if a failure occurs in any one of them, the upper component that receives failure information from them will also experience a failure, so it is input as an OR gate.

[0073] Of course, in Fig. 5, a fault tree configuration item was added before the output arrival point (111d) to include functional failures and failures due to causes other than functional failures.

[0074] Accordingly, in Fig. 5, a fault tree was created so that a functional failure item is input to an OR gate for a failure in the resource input, a failure of the first composite component, and a failure of the second composite component, and an output arrival point (111d) is input to an OR gate for a functional failure item and a failure item due to a cause other than the function.

[0075] Meanwhile, when decomposing a composite component (111c), since the multiple simple components (111b) or lower composite components (111c) that constitute the composite component (111c) are structured to branch in parallel in the resource flow diagram and layer flow diagram, they can be merged into separate composite components (111c) according to these branching structures.

[0076] That is, the first composite component (111c) in FIG. 3 is composed of a total of three branch flow lines, and two simple components (111b) connected along the first branch flow line can be merged into one composite component (111c).

[0077] Accordingly, as shown in Fig. 6, among the three branch flow lines of the first composite component (111c), the failure item of the first separation flow line, the failure item of the second branch flow line, and the failure item of the third branch flow line can be displayed, and these are each input to the first composite component (111c) as an AND gate.

[0078] If each branch flow line consists of only one simple component, there is no need to configure it as a composite component.

[0079] Accordingly, an example is shown in Fig. 7 in which the OR gate input of simple components is configured to be received on the lower side of the failure item of the first branch flow line.

[0080] Of course, failure items in the second branch flow line and the third branch flow line can also be displayed like failure items in the first branch flow line.

[0081] But even in this case, the layer of the final failure tree must have a second layer.

[0082] In this way, the item extraction unit (110) and fault tree generation unit (120) according to one embodiment of the present invention generate a fault tree of the first layer in which the fault tree configuration items (111) are connected in series along the flow line of the resource flow diagram, and when the composite component (111c) is present among the fault tree configuration items (111) constituting the fault tree of the first layer, the composite component (111c) is first decomposed into a configuration of a plurality of branched simple components (111b) or lower composite components (111c) to generate a fault tree of the second layer.

[0083] In addition, if there is a lower composite component (111c) among the fault tree configuration items constituting the fault tree of the second layer, the lower composite component (111c) is decomposed into a second configuration of a plurality of simple components or lower composite components branching along the flow line of the resource flow diagram, and the Nth layer fault tree is generated by continuously decomposing it into (N-1) configurations until the fault tree configuration items are composed of only a plurality of simple components.

[0084]

[0085] FIG. 8 is a diagram showing a failure tree of a simple component by failure type and failure mode of the component according to another embodiment of the present invention.

[0086] Referring to the drawing, according to the present embodiment, the fault tree generation unit can be connected to receive fault information by classifying the fault information of the fault tree configuration items according to the fault mode and fault type.

[0087] In the case of a system that forms a circular logic by receiving failure information according to these failure modes and failure types, the circular logic is fundamentally prevented from occurring within the fault tree.

[0088] In other words, the cyclic logic can be fundamentally blocked in the fault tree because the cause items that constitute the cyclic logic are created as separate failure items according to failure mode and failure type and failure information is input.

[0089] The classification of failure information according to failure mode and failure type is shown in [Table 1] below.

[0090] Fault Type \ Fault Mode Startup Failure Event Operation Failure Event Component Self-Failure Independent Failure Independent Failure Common Cause Failure Common Cause Failure Human Error Human Error Auxiliary System Failure (User Defined) Cooling Failure Cooling Failure Power Supply Failure Power Supply Failure Signal Transmission Failure Signal Transmission Failure Missignal Other (by definition) Other (by definition)

[0091] As shown in the above [Table 1], the failure information items according to the failure mode include a start failure event and an operation failure event, and the failure information items according to the failure type include a component itself failure and an auxiliary system failure.

[0092] In addition, the failure information items due to the component's own failure include more specifically at least one of an independent failure, a common cause failure, and a human error, and the failure information due to the auxiliary system failure includes at least one of a cooling failure, a power supply failure, a signal transmission failure, and a failure information due to a user setting.

[0093] Here, the administrator can add failure information items according to user settings through the input unit (200) or a separate interface.

[0094] In addition, since all of the failure information items in [Table 1] for the above components are OR relationships of Boolean algebra, they can be expressed as a failure tree as in Fig. 8.

[0095] By creating a fault tree in this way, all components can be written in a standard form, errors during fault tree creation can be minimized, and as mentioned above, the occurrence of circular logic can be fundamentally prevented.

[0096] Failure information due to the above auxiliary system failure can be expressed as examples of cooling failure, power supply failure, etc., as in [Table 1], where each component can have one or more auxiliary systems to perform its function.

[0097] By including failure information items of these auxiliary systems, an independent failure tree using a resource flow diagram can be constructed, and a failure tree of the auxiliary system can be generated together with the failure of the component itself, as shown in Fig. 8.

[0098]

[0099] Figure 9 is a flowchart showing a fault tree generation method according to one embodiment of the present invention.

[0100] Referring to the drawings, a fault tree generation method according to an embodiment of the present invention largely includes a step (S200) in which a control unit (100) extracts fault tree configuration items including an input starting point, an output arrival point, a simple component, and a complex component based on a received support flowchart, and generates a fault tree of a first layer, which is a fault tree of a serial structure, a step (S200) of determining whether there are fault tree configuration items of a lower layer, and if there are fault tree configuration items of a lower layer, decomposing them to generate a fault tree of the corresponding layer, and then returning to step S200, and if there are no fault tree configuration items of the lower layer, a step (S300) of generating a fault tree of the corresponding layer as a final fault tree.

[0101] Here, the S100 step extracts fault tree configuration items according to layers based on the resource flow diagram received by the control unit (100) as described in the fault tree generation device described above, and generates a fault tree of the first layer that connects fault tree configuration items in the form of the first layer.

[0102] Accordingly, when the fault tree of the first layer is generated, it is determined whether there is a composite component (111c) having a second layer among the fault trees of the first layer (S200). If there is, it is decomposed to generate a fault tree of the second layer, and the process returns to step S200 (S310). If there is not, the fault tree of the first layer is confirmed as the final fault tree and terminated (S320).

[0103] Of course, when the fault tree of the second layer is generated and the process returns to step S200, the process described above is repeated by determining whether there is a composite component (111c) with the next layer again, and the process is repeated until only a simple component (111b) is displayed without a composite component (111c).

[0104] Here, the composite component (111c) includes a plurality of simple components (111b) or lower composite components (111c) that are configured by branching along the flow line of the resource flow diagram as described above, and the lower composite component (111c) is included as a fault tree configuration item (111) within the upper composite component (111c), and a plurality of simple components (111b) or lower composite components (111c) are included as fault tree configuration items (111) within it.

[0105] The above lower or upper refers to the height of the layer, with lower referring to a layer that is 1 higher than the layer in question, and upper referring to a layer that is 1 lower than the layer in question.

[0106] In addition, the control unit (100) is configured with an item extraction unit (110) that extracts layer-by-layer fault tree configuration items (111) based on the resource flow diagram received as described above, and a fault tree generation unit (120) that sequentially generates layer-by-layer fault trees based on the resource flow diagram and layer-by-layer fault tree configuration items (111), thereby generating a final fault tree.

[0107] As described in the above-mentioned fault tree generation device, a separate detailed description will be omitted.

[0108] While preferred embodiments of the present invention have been described above, the present invention is not limited to the specific embodiments described above. That is, those skilled in the art to which the present invention pertains may make numerous changes and modifications to the present invention without departing from the spirit and scope of the appended claims, and all such appropriate changes and modifications should be considered equivalents and fall within the scope of the present invention.

[0109]

[0110] [Explanation of symbols]

[0111] 100: Control unit

[0112] 110: Item Extraction Section

[0113] 111: Fault tree configuration item 111a: Input starting point

[0114] 111b: Simple component 111c: Complex component

[0115] 111d: Output arrival point 112: Node

[0116] 112a: 1st layer node 112b: 2nd layer node

[0117] 120: Fault tree generation unit

[0118] 200: Input section

[0119] 300: Output section

[0120] 1000: Fault tree generator

[0121] The present invention relates to a fault tree generation device that generates a final fault tree by sequentially generating a fault tree according to a layer by extracting a fault tree configuration item for each layer along a flow line of a resource flow diagram, and thus has industrial applicability.

Claims

1. In a fault tree generation device that generates a fault tree based on a resource flow diagram composed of multiple components, The above fault tree generation device is, A control unit that extracts fault tree configuration items including input starting points, output arrival points, simple components, and complex components based on a received resource flow diagram, and sequentially generates a fault tree by connecting the fault tree configuration items according to layers, thereby generating a final fault tree. A fault tree generating device characterized by:

2. In paragraph 1, The above control unit Generate a fault tree of the first layer in which the fault tree configuration items are connected in series along the flow lines of the above resource flow diagram, If the composite component is present among the fault tree components constituting the fault tree of the first layer above, Generating a fault tree of the second layer by first decomposing the complex component into a composition of multiple branched simple components or lower complex components. A fault tree generating device characterized by:

3. In paragraph 2, The above control unit If there is a composite component among the fault tree components that constitute the fault tree of the second layer above, Decompose the lower complex component into a plurality of simple components or lower complex components branching along the flow line of the resource flow diagram, and decompose it (N-1) times until the fault tree configuration items are composed of only multiple simple components, thereby generating the Nth layer fault tree. A fault tree generating device characterized by: (Here, N is a natural number, and 3≤N.) 4. In paragraph 3, The above control unit An item extraction unit that extracts a fault tree configuration item for each layer based on the received resource flow diagram; and A fault tree generation unit that sequentially generates a layer-by-layer fault tree based on the resource flow diagram and the layer-by-layer fault tree configuration items to generate a final fault tree; A fault tree generating device characterized by:

5. In paragraph 4, The above composite component is It includes multiple simple components or lower complex components that are arranged along the flow lines of the resource flow diagram. The composite component below is Included as a fault tree configuration item within an upper composite component, and multiple simple components or lower composite components are included as fault tree configuration items within it. A fault tree generating device characterized by:

6. In paragraph 5, The above fault tree generation unit When constructing a fault tree in the first layer The output arrival point, which is the last point reached along the flow line of the resource flow chart, is located at the top, The input starting point, which is the starting point on the flow line of the resource flow chart, and the simple component or complex component connected in series thereto are placed left and right below the output arrival point, respectively. Connecting the above output destination to receive fault information from the above input starting point, simple component or complex component. A fault tree generating device characterized by:

7. In paragraph 6, The above fault tree generation unit When constructing a fault tree in the second layer If there is a composite component in the fault tree of the first layer above, Placing simple components or lower composite components included in the composite component to the left and right of the lower side of the composite component and connecting them to receive fault information. A fault tree generating device characterized by:

8. In paragraph 7, The above fault tree generation unit When constructing a fault tree of the Nth layer If there is a lower composite component in the fault tree of the above (N-1) layer, Placing the simple components or lower composite components included in the corresponding lower composite component to the left and right of the lower side of the corresponding lower composite component and connecting them to receive failure information from them. A fault tree generating device characterized by: (Here, N is a natural number, and 3≤N.) 9. In paragraph 4, The above item extraction section Create a layer flowchart that sequentially displays the fault tree configuration items by layer based on the resource flowchart. The above fault tree generation unit Sequentially generating a fault tree for each layer based on the above layer flowchart A fault tree generating device characterized by:

10. In paragraph 9, The above item extraction section Displaying nodes for each layer between the fault tree configuration items for each layer in the above layer flowchart A fault tree generating device characterized by:

11. In paragraph 8, The above fault tree generation unit The above fault tree configuration items are connected to receive fault information by classifying them according to fault mode and fault type. Failure information according to the above failure mode Includes at least one of a start failure event and a drive failure event, Failure information according to the above failure type Contains at least one of component failure itself and auxiliary system failure. A fault tree generating device characterized by:

12. In paragraph 11, Failure information due to failure of the above component itself Contains at least one of independent failure, common cause failure and human error; Failure information due to the above auxiliary system failure Contains at least one of the following failure information: cooling failure, power failure, signal transmission failure, and other failure information in user settings. A fault tree generating device characterized by:

13. A fault tree generation method using a fault tree generation device having the characteristics of paragraph 1, The control unit a) A step of extracting fault tree components including input starting points, output destination points, simple components, and complex components based on the received resource flow diagram, and generating a fault tree of the first layer, which is a fault tree of a serial structure; b) a step of determining whether there is a fault tree component in the lower layer; and c) If there is a fault tree component of a lower layer, decompose it to create a fault tree of that layer, and return to step b). A step of generating a fault tree of the layer as a final fault tree if there is no fault tree configuration item of the lower layer; A fault tree generation method using a fault tree generation device characterized by .

14. In paragraph 13, The above composite component is It includes multiple simple components or sub-complex components that are branched and configured along the flow line of the resource flow diagram. The composite component below is Included as a fault tree configuration item within an upper composite component, and multiple simple components or lower composite components are included as fault tree configuration items within it. A fault tree generation method using a fault tree generation device characterized by .

15. In paragraph 13, The above control unit An item extraction unit that extracts a fault tree configuration item for each layer based on the received resource flow diagram; and A fault tree generation unit that sequentially generates a layer-by-layer fault tree based on the resource flow diagram and the layer-by-layer fault tree configuration items to generate a final fault tree; A fault tree generation method using a fault tree generation device characterized by .

Images