JP5347776B2 - Problem analysis support system, method and program - Google Patents

Description

  The present invention relates to a problem analysis support system.

  2. Description of the Related Art Conventionally, there is a fault tree creation device that calculates an unreliability for the top event of a fault tree based on the probability of occurrence for each event (see Patent Document 1). In addition, there is an equipment abnormality detection device that predicts an abnormality that occurs by comparing the occurrence reference value of an event included in the failure tree with an inspection result and determining whether an abnormal condition is satisfied in the failure tree. (See Patent Document 2).

JP 2000-194561 A Japanese Patent Application Laid-Open No. 8-190681

  Conventionally, in an analysis support system related to an analysis method of accident / trouble cases, an event relation diagram for grasping the chain of events, a behind factor diagram for analyzing factors behind the occurred event, and an event A measure evaluation sheet for evaluating measures applied to the factors is used. In particular, the background factor diagram can be used to confirm whether the measures taken for the background factor are sufficient to prevent the occurrence of the top event.

  However, even if the above event-related charts, background factor diagrams, countermeasure evaluation sheets, etc. are used, simply examining, evaluating, and adopting measures will break the chain of background factors that lead to the top event due to the applied measures. Without logical verification and confirmation, the relationship that contributes to the prevention of the top event of the countermeasure becomes opaque, and it is not possible to obtain the benefits of creating these charts. In this regard, it was necessary for the analyst to judge whether the chain of the underlying factors leading to the event could be broken by the application of countermeasures based on his own experience and knowledge.

  In the present invention, in view of the above-described problems, whether or not the chain of factors leading to a predetermined event is broken by the applied countermeasures, and as a result, the occurrence of the predetermined event is prevented, It is an object to make it easy for a user who does not have knowledge to make a judgment.

The present invention has the following configuration to solve the above-described problems. That is, the present invention is a tree structure having a node indicating an event, and displays a tree structure including a parent node and a child node indicating a child event that is a cause of occurrence of the parent event related to the parent node. By referring to the measure status information holding means for holding the measure status information indicating the measure status for the event in association with the node related to each event, and the measure status information relating to the child event, Determining means for determining whether or not the occurrence of a parent event caused by an event is prevented, wherein the determining means generates a parent event when the true AND of the event occurrence is true When a measure is applied to at least one of its child events, it is determined that the occurrence of the parent event is prevented, and the true OR of the event occurrence is true Child events that cause a parent event to occur When the countermeasure is applied to all of the child events, it is determined that the occurrence of the parent event is prevented, and the display means determines that the occurrence of the parent event is prevented by the determination means. In this case, the problem analysis support system displays the determination result on the tree structure.

  Here, the event is an event as a problem such as an accident / trouble to be finally solved or an event as a factor for deriving such a problem. An event is expressed as a tree-structured node in the present invention. For example, an event that is a problem to be finally solved is placed at the root node of the tree-structure as a top event, and other events are other factors as a cause event. Placed in the node. As for an event having a relationship between the cause and result of event occurrence, the event that occurs as a result is displayed as a parent event on the parent node, and the event that occurs as a cause is displayed as a child event on the child node.

  In the present invention, countermeasure status information indicating whether or not a countermeasure is taken for an event related to this node is held in association with the node where the event is displayed. Such countermeasure status information is held, for example, as a countermeasure application mark or a countermeasure mark displayed on the node related to the event, or a countermeasure status flag “1”.

  In the present invention, it is determined whether or not the occurrence of a parent event is prevented in the countermeasure situation for the current child event by referring to the countermeasure status information for one or more child events hanging from the parent event. It is said. At this time, if all child events occur (when the true AND of the event occurrence is true), a child event that generates a parent event and any child event occurs (event) And a child event that causes a parent event to occur (if the true or false OR of the occurrences is true). For this reason, in the present invention, when all child events occur, the child event that causes the parent event occurs when the countermeasure is applied to at least one of the child events. It is determined that it will be prevented. Further, regarding any child event that generates a parent event when any child event occurs, it is determined that the occurrence of the parent event is prevented when countermeasures are applied to all the child events.

  In the present invention, when it is determined that the occurrence of the parent event is prevented, the determination result is displayed on the tree structure. As a result, according to the present invention, even if the user does not have analysis experience or knowledge, whether the chain of factors leading to the event is broken by the applied measures, and the occurrence of the event is prevented. It is possible to easily determine whether or not.

  In the present invention, the display means displays a mark indicating that the occurrence of the parent event is prevented from being displayed on the node indicating the parent event that is determined to be prevented by the determination means. Also good.

  As a mark indicating that the occurrence of an event is prevented, for example, a countermeasured mark or the like displayed in a superimposed manner on a node related to the event whose occurrence is prevented can be used. Moreover, as such a mark, a character, a symbol, an icon, etc. may be used, and the mark may be displayed superimposed on the node or displayed near the node. By displaying a mark indicating that the occurrence of the parent event is prevented, according to the present invention, the user can visually grasp the contribution of the chain of events to the event and the countermeasure solution to the problem solving. I can do it. In addition, even if the current measures applied by the user are insufficient, it is possible to indicate the direction of re-examination on which part should be taken, thus reducing the time required for problem analysis It is also possible to do.

Further, in the present invention, the countermeasure status information is set to true when a countermeasure is applied to an event, and set to false when the countermeasure is not applied to the event. For a child event that generates a parent event when the logical product of the two is true, it is determined that the occurrence of the parent event is prevented when the logical sum of the countermeasure status information of the child event is true. For a child event that generates a parent event when the true OR of the event occurrence is true, the occurrence of the parent event is prevented if the logical product of countermeasure status information of the child event is true It is good also as determining.

That is, in the present invention, whether or not a countermeasure is applied to at least one of the child events that cause a parent event by logical product is determined by a logical sum of countermeasure states,
Whether or not a countermeasure is applied to all child events that cause a parent event by logical sum is determined by a logical product of countermeasure states.

  According to the present invention, by determining whether or not a countermeasure is possible using such a logical calculation, the chain of factors leading to an event is broken by the applied countermeasure without performing complicated determination processing, and as a result It is possible to easily determine whether or not the occurrence of an event is prevented.

  Furthermore, the present invention can be understood as a method executed by a computer or a program executed by a computer. Further, the present invention may be a program in which such a program is recorded on a recording medium readable by a computer, other devices, machines, or the like. Here, a computer-readable recording medium is a recording medium that stores information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read from a computer or the like. Say.

  According to the present invention, it has experience and knowledge for analysis whether the chain of factors leading to a predetermined event is broken by the applied countermeasures, and as a result, the occurrence of the predetermined event is prevented. It is possible to make a determination easily even for a user who is not present.

It is a figure which shows the hardware constitutions of the problem analysis support system which concerns on embodiment. It is a figure which shows the outline of a function structure of the problem analysis support system which concerns on embodiment. It is a figure which shows the image of the back factor figure preparation screen displayed on a display apparatus in embodiment. It is a figure which shows the display image of the background factor figure produced in embodiment. It is a flowchart which shows the flow of the countermeasure check process which concerns on embodiment. It is a figure which shows the logic calculation table after completion of countermeasure check process produced in embodiment. It is flowchart A which shows the detailed flow of the countermeasure state check process of an event based on embodiment. It is a flowchart B which shows the detailed flow of the countermeasure state check process of an event based on embodiment. It is a figure which shows the image of the determination result dialog displayed in embodiment. It is a figure which shows the display image of the background factor figure on which the countermeasure finished mark produced | generated in embodiment was superimposed and displayed. In an embodiment, it is a figure showing a back factor figure in the state where some branches were excluded from the object of a countermeasure check by an exclusion mark. FIG. 11 is a diagram showing a logical calculation table created based on the background factor diagram shown in FIG. 10 in the embodiment.

  Hereinafter, an embodiment of a problem analysis support system 1 according to the present invention will be described with reference to the drawings.

<System configuration>
FIG. 1 is a diagram illustrating a hardware configuration of a problem analysis support system 1 according to the present embodiment. The problem analysis support system 1 includes a CPU (Central Processing Unit) 11, a RAM (Random Access Memory) 13 as a main storage device, a ROM (Read Only Memory) 12, a HDD (Hard Disk Drive), an SSD (Solid State Drive), and the like. The auxiliary storage device 14, the display device 15 as a display, and the input device 16 as a computer (information processing device) including a keyboard and a mouse.

  FIG. 2 is a diagram showing an outline of a functional configuration of the problem analysis support system 1 according to the present embodiment. In the computer having the configuration shown in FIG. 1, the problem analysis support program recorded in the auxiliary storage device 14 is read into the RAM 13 and executed by the CPU 11, so that the input receiving unit 21 and the logical calculation table creation are performed. It functions as the problem analysis support system 1 including the unit 22, the display unit 23, the information holding unit 24, and the determination unit 25. Of these, the display unit 23, the information holding unit 24, and the determination unit 25 correspond to the display unit, countermeasure status information holding unit, and determination unit according to the present invention, respectively.

  In the problem analysis support system 1 according to the present embodiment, the background factor diagram 3 is used to analyze the factor behind the occurred event. Fig. 3 shows the top event as a problem to be solved and the factor event that is the back factor that the top event occurs as a node, and the event that becomes the back factor of each event with the top event as a base point (root node) Is a diagram of a tree structure connected as child nodes.

  FIG. 3 is a diagram showing an image of a background factor diagram creation screen displayed on the display device 15 in the present embodiment. In FIG. 3, the word “problem 1” is displayed as the top event, but the top event node includes the content of the event to be solved (for example, the specific name of the accident / trouble, for example, “Power failure” or the like may be displayed. Similarly, in FIG. 3, words such as “Factor 1” and “Factor 2” are displayed as the causal event, but the causal event node shows the event that has caused the parent event (occurrence condition). The content of the event that should be treated (for example, “disconnection”), such as a specific name, may be displayed.

  Background Factor Nodes such as the top event and the factor event displayed in FIG. 3 are input by a user input operation using a keyboard, a mouse, and the like, and are displayed on the display device 15. Figure 3 shows the tree structure in which events such as accidents and troubles that ultimately want to be prevented are placed at the top as top events, and the factor events that cause the top events occur as subordinate nodes. Associated with the top event. In addition, other causal events that are the background factors in which these causal events occur are associated with the causal events as lower nodes. That is, in the background factor FIG. 3, the top event and the factor event are associated with each other in a multi-layer parent-child relationship. Among the top event and the factor event, when a certain event is a parent event, an event that is a factor causing the parent event and is directly connected to the parent event by a branch is called a child event. In other words, a parent event is an event that occurs due to a child event directly connected by a branch.

  When the user creates a new background factor diagram 3, the user places a problem to be solved using the background factor diagram 3 as a top event at the root node of the tree structure (see “Problem 1” in FIG. 3), and , The factor behind the occurrence of the top event is arranged in a tree structure according to the parent-child relationship between the parent event and the child event that is the factor behind the occurrence of the parent event. FIG. 3 is generated. The background factor diagram 3 is created by allowing the user to select the operation palette 40 or the operation panel 50 displayed on the background factor diagram 3 by using a mouse or the like, and if necessary, using a keyboard to enter characters. This is done by performing an operation such as inputting.

In the present embodiment, the operation palette 40 has an operation panel call button 41 for calling the operation panel 50 to add an event (node), and whether the selected factor event is an AND factor with respect to the parent event. A factor type setting button 42 for setting whether the factor is an OR factor, a countermeasure application button 43 for setting a countermeasure application mark 63 indicating that a countermeasure is applied to the selected factor event, Various buttons such as a countermeasure check button 44 for starting execution of countermeasure check processing, which will be described later, and an exclusion button 45 for designating branches not considered in the countermeasure check (details of the function of the exclusion button 45 will be described later) are arranged. ing. The operation panel 50 includes an event content input box 51, a color selection field 52, an OK button (decision button), a cancel button, and the like.

  When inputting an event, the user designates a position to add the event in the background factor FIG. 3, and the name and content of the event displayed in the event node ("Problem 1" and "Power failure" described above, "Factor 1", "disconnection", etc.) are input to the content input box 51, and the event node color is designated according to the event type. When the type of event to be input is a factor event, the user selects “background factor” from the color selection field 52 shown in FIG. 3, and the event type in which the input event type is estimated to be a factor event 3 is selected from the color selection column 52 of FIG. 3, and when the type of event to be input is the top event, the “problem” is selected from the color selection column 52 shown in FIG. Select Point.

  In addition, the user operates the factor type setting button 42 of the operation palette 40 to specify whether each factor event included in the background factor FIG. 3 is an AND factor or an OR factor. Here, the AND factor is a factor event that is considered to occur when a plurality of child events occur for the parent event, that is, when the true AND of the event occurrence of the child event is true. Means. The OR factor means a factor event that is considered to cause a parent event when any of a plurality of child events occurs, that is, when the true OR of the occurrences of child events is true. . Note that a child event that is an AND factor and a child event that is an OR factor may be mixedly associated with one parent event. If a child event that is an AND factor and a child event that is an OR factor are associated with one parent event, is the parent event satisfied by at least one of the child events that are OR factors? Occurs when all child events that are AND factors are satisfied.

  In the present embodiment, a cause event (child event) that is not designated as an AND factor or an OR factor is treated as an OR factor with respect to a parent event. By doing this, even if it is difficult for the user to determine whether the user is an AND factor or an OR factor, the event is considered as an event that causes a parent event if no countermeasure is taken. Handling and measures can be made more reliable.

  In addition, the user operates the mouse or the like to specify a factor event to which the countermeasure is applied, and operates a countermeasure application button 43 provided on the operation palette 40, thereby setting a countermeasure application mark 63 for the factor event. It is possible to set the cause event to the countermeasure application state. The countermeasure application mark 63 set by the user is held by the information holding unit 24 and used for the countermeasure status check process by the determination unit 25.

FIG. 4 is a diagram showing a display image of the background factor FIG. 3 created in the present embodiment. As explained above, each factor event included in FIG. 3 in the background factor is set whether the factor event (child event) is an AND factor or an OR factor with respect to the parent event. Whether or not countermeasures are applied to the cause event is set. In the present embodiment, a factor event that is an AND factor for a parent event is set by adding a rectangular AND factor mark 61 to a branch that is connected to the parent event, and a factor event that is an OR factor for the parent event is the parent event. It is set by attaching a circular OR factor mark 62 to the connected branch. In the present embodiment, a countermeasure application mark 63 indicating that the countermeasure event is applied to the cause event to which the countermeasure is applied and that the association as the cause of the parent event is no longer applied. Attached.

<Process flow>
Next, the flow of countermeasure check processing executed by the problem analysis support system 1 according to the present embodiment will be described. In the problem analysis support system 1 according to the present embodiment, by executing the countermeasure check process, the occurrence of the top event in the background factor diagram 3 created by the method described above is marked with the countermeasure application mark 63. Determine whether measures against the causal event can be surely prevented.

  FIG. 5 is a flowchart showing a flow of countermeasure check processing according to the present embodiment. In the measure check processing according to the present embodiment, in the problem analysis support system 1 described above, the measure check button 44 displayed on the display device 15 uses a mouse or the like after the creation of the background factor diagram 3 by the user is completed. It is triggered by the selection and pressing operation by user operation.

  In step S101, the logical calculation table 4 is checked. When the input reception unit 21 detects that the countermeasure check button 44 is pressed by a user operation, first, the logical calculation table creation unit 22 confirms whether or not the existing logical calculation table 4 exists, and the existing logical calculation table 4. If this exists, this logical calculation table 4 is deleted. This is a process for deleting the old logical calculation table 4 generated in the countermeasure check process executed last time when the countermeasure check process is started. Thereafter, the process proceeds to step S102.

  In step S102, a logical calculation table 4 is newly created. When the existing logical calculation table 4 is deleted, the logical calculation table creation unit 22 newly creates the logical calculation table 4 based on the current background factor diagram 3. The logical calculation table 4 is a matrix format table in which the state of the corresponding event (node) is recorded in the cell corresponding to the node where the event is arranged in the background factor FIG. Retained.

  FIG. 6 is a diagram showing the logical calculation table 4 created in the present embodiment after the countermeasure check processing is completed. According to the logical calculation table 4 of FIG. 6, it can be seen that the state of the corresponding event is recorded in the cell corresponding to the event shown in FIG. First, the logical calculation table creation unit 22 sets the countermeasure status flag “0” in the cell of the logical calculation table 4 corresponding to the node in which the factor event is input in the background factor diagram 3.

  When the input of the countermeasure status flag “0” to the cells corresponding to all the factor events set in the background factor FIG. 3 is completed, the logical calculation table creation unit 22 refers to these factor events, and each factor event It is determined whether or not the countermeasure application mark 63 is set. Then, the logical calculation table creation unit 22 changes the countermeasure status flag in which the countermeasure application mark 63 is set to the corresponding cause event among the countermeasure status flags “0” set in the logical calculation table 4 to “1”. To do. That is, at the time when the processing so far is completed, the logical calculation table 4 has the countermeasure status flag “1” and the countermeasure application mark 63 attached to the cell corresponding to the cause event to which the countermeasure application mark 63 is attached. The countermeasure status flag “0” is set in the cell corresponding to the non-cause event (see FIG. 6).

Further, the logical calculation table creation unit 22 refers to the AND factor mark 61 and the OR factor mark 62 set in the background factor FIG. 3, and each factor event is an AND factor or an OR factor with respect to the parent event. Determine whether. Then, the logical calculation table creation unit 22 sends information indicating that the cause event is an AND factor (in this embodiment, a character string “and” in the corresponding cell of the logic calculation table 4 for the cause event that is an AND factor. “)” Is set, and for a cause event that is an OR factor, information indicating that this cause event is an OR factor (in this embodiment, a character string “or”) is set in the corresponding cell of the logical calculation table 4. (See FIG. 6). When the logical calculation table 4 is completed, the process proceeds to step S103.

  In step S103, the countermeasured mark 64 (see FIG. 9) is deleted from the background factor FIG. Here, the countermeasured mark 64 corresponds to an event that is determined to be prevented from occurring because the countermeasures taken for the child event are appropriate as a result of the countermeasure checking process shown in the flowchart. This mark is different from the countermeasure application mark 63 attached by user operation. More specifically, in the countermeasured mark 64, a certain parent event (the top event or the factor event) has a countermeasure applied to any of the child events that are AND factors or all of the child events that are OR factors. (Specifically, the countermeasure application mark 63 or the countermeasure-completed mark 64 is attached), and this mark indicates that this parent event does not occur. In this step, the display unit 23 deletes the countermeasured mark 64 attached as a result of the countermeasure check process executed last time. Thereafter, the process proceeds to step S104.

  In step S104, whether or not the countermeasure taken for each factor event is sufficient to prevent the occurrence of the event, in other words, for all parent events, the parent event is taken according to the measures taken for the child events. A check is made as to whether or not the occurrence of the occurrence is prevented. The determination unit 25 performs a countermeasure check from the bottom up toward the top event from the factor event at the lowest layer node (the rightmost side in FIG. 4) in FIG. If it can be said that the parent event has already been taken as a result of the check, the determination unit 25 sets the countermeasure status flag “1” in the cell corresponding to this parent event in the logical calculation table 4 (see FIG. 6). .

  7A and 7B are flowcharts showing the detailed flow of the countermeasure state check process for events shown in step S104 of FIG. Hereinafter, more specific contents of the check method in step S104 will be described with reference to FIGS. 7A and 7B.

  Step S201 is the start of a column loop for specifying the column of the check target cell in the logic calculation table 4, and step S202 is the start of a row loop for specifying the row of the check target cell in the logic calculation table 4 At the end. The end of the row loop is step S223, and the end of the column loop is step S224.

  In this embodiment, the logical calculation table 4 is configured by inputting a countermeasure status flag (“0” or “1”), a character string such as “and”, “or”, or the like into a cell of a matrix format table. ing. For this reason, in this embodiment, the row and the column of the check target cell are specified by the column loop and the row loop, whereby the check target cell is specified in a predetermined order, and the contents of the cell are checked. More specifically, in the present embodiment, a column loop for checking from the last column to the first column (from the lowest-level factor event to the top event), and from the first row for each column (hierarchy) of the column loop By executing the line loop for checking toward the last line (from the top cause event to the bottom cause event in the same hierarchy), from the bottom cause event to the top event A bottom-up check is going to be done.

  However, the logical calculation table in the form of a table as described in the present embodiment is used to check whether each factor event has been treated, whether each factor event is an AND event or an OR event, etc. 4 and the method using the row loop and the column loop may not be used. Other methods for checking the contents of the tree structure include a method of determining whether countermeasure application to a child event is sufficient while following a branch that associates nodes with each other as a specific method of the countermeasure state check However, it may be adopted depending on the embodiment.

In step S203, it is determined whether or not there is an input to the cell corresponding to the parent event for the check target cell specified by the row loop and the column loop, that is, whether or not the parent event exists. . If there is no parent event, there is no parent event for which it is determined whether countermeasures have been taken or not, and the process advances to step S222. In step S222, the check target is advanced to the next cell according to the row loop and the column loop. On the other hand, if there is a parent event, in step S204, variables used in the processing after step S205 are initialized. Here, the variables used in the processing after step S205 include, for example, an AND factor countermeasure status flag, an OR factor counter, an OR factor countermeasure status counter, and the like.

  Here, the AND factor countermeasure status flag is a flag that is set to ON when a countermeasure is taken for at least one of the child events that are AND factors for a parent event (the countermeasure status flag is “1”). The OR factor counter is a counter for counting the total number of child events that are OR factors for a certain parent event, and the OR factor countermeasure status counter is a countermeasure among the child events that are OR factors for a certain parent event. This is a counter for counting the number of child events that have been applied (the countermeasure status flag is “1”). When the variable initialization is completed, the process proceeds to step S205.

  In the item loop from step S205 to step S211, it is determined whether or not the parent event to which the child event corresponding to the current check target cell is connected can be said to have been taken countermeasures in the current background factor state of FIG. Information for is collected. Here, using the item loop, all child events connected to the parent event of the child event corresponding to the current check target cell are checked. First, the determination unit 25 confirms whether or not there is a child event corresponding to the cell to be checked by referring to the node in the background factor diagram 3 corresponding to the check target cell (step S206). . If there is no corresponding child event, the check target cell moves to the next cell (step S211). If there is a corresponding child event, the determination unit 25 records a cell in which information indicating whether the child event is an AND factor or an OR factor (in the example illustrated in FIG. It is confirmed which of the character strings “and” and “or” is recorded in the cell (step S207).

  When “and” is input to the corresponding cell, the determination unit 25 determines whether or not the countermeasure status flag of this child event is “1”, in other words, the child event that is an AND factor has already been countermeasured or applied countermeasures. It is confirmed whether it has been done (step S208). If the countermeasure status flag is “1”, the determination unit 25 sets the AND factor countermeasure completed flag to “ON” (step S209).

  When “or” is input to the corresponding cell as a result of the confirmation in step S207, the determination unit 25 adds 1 to the OR factor counter (increment). In addition, the determination unit 25 confirms whether or not the countermeasure status flag of this child event is “1”, in other words, whether or not the child event that is an OR factor has been countermeasured or applied. If the countermeasure status flag is “1”, the OR factor countermeasure status counter is incremented by 1 (step S210). The process shown in step S210 is executed for all OR factor events connected to a parent event in the item loop, so that the number of OR factor events connected to the parent event is calculated as an OR factor counter. Furthermore, the number of OR factor child events whose countermeasure status flag is “1” is counted in the OR factor countermeasure status counter. When all the cells corresponding to the child events connected to the parent event are checked, the item loop ends (step S211), and the process proceeds to step S212.

  In step S212 to step S220, it is determined whether or not it can be said that the parent event has been taken countermeasures based on the information collected in the item loop from step S205 to step S211.

When the OR factor counter is “0” and the AND factor countermeasure completed flag is “ON”, the occurrence of this parent event is prevented. That is, since the AND factor is a factor event that is considered to cause a parent event when a plurality of child events occur, all the child events that cause the parent event are AND factors, and at least one of When countermeasures are taken for the AND cause event, the occurrence of the parent event is prevented. Therefore, the determination unit 25 sets the countermeasure status flag of the cell corresponding to the parent event to “1” which means that the countermeasure has been taken (steps S212, S213, and S214).

  If the OR factor counter is equal to or greater than “1”, the OR factor counter is equal to the OR factor countermeasure status counter, and there is one or more AND factor, but the AND factor countered flag is “ON”, this parent event Occurrence is prevented. In other words, since the OR factor is a factor event that is considered to cause a parent event if any of a plurality of child events occurs, an OR factor and an AND factor are mixed as a child event that is a cause of the parent event. However, when all the OR factor events are treated and at least one of the AND factor events is treated, the occurrence of the parent event is prevented. Therefore, the determination unit 25 sets the countermeasure status flag of the cell corresponding to the parent event to “1” (steps S212, S216, S217).

  When the OR factor counter is “1” or more, the OR factor counter is equal to the OR factor countermeasure status counter, and there is no AND factor and the AND factor countermeasure completed flag is “OFF”, the occurrence of this parent event is Is prevented. That is, since the OR factor is a factor event that is considered to generate a parent event if any of a plurality of child events occurs, all the child events that are the generation factors of the parent event are OR factors, and all the OR events When countermeasures are taken for the cause event, the occurrence of the parent event is prevented. Therefore, the determination unit 25 sets the countermeasure status flag of the cell corresponding to the parent event to “1” (steps S212, S218, S219, and S220).

  If none of the above conditions apply, that is, if there is an OR factor event for which no countermeasure is taken as a child event, or if there is any unmeasured AND factor event, it corresponds to the parent event The countermeasure status flag of the cell to be changed remains “0”.

  When the determination process for determining whether or not the parent event has been taken is completed, the process proceeds to step S221. In step S221, the check target cell is advanced to the next cell, and the process proceeds to step S223. Step S223 is the end of the row loop, and step S224 is the end of the column loop. That is, in the processing shown in this flowchart, the column loop and the row loop are executed, so that cells to be checked are sequentially identified from the lowest-level factor event to the top event, and the bottom-up check of the tree is performed. Is called. When the check for all the cells is finished by the column loop and the row loop, the processing shown in this flowchart is finished.

  The processing flow described with reference to FIGS. 7A and 7B is the details of the processing for checking whether or not it can be said that the parent event has been taken countermeasures in step S104. At the time when the processing shown in step S104 is completed, “1” is set in the countermeasure status flag for the event for which the occurrence of the event is prevented because the countermeasure is taken. Thereafter, the process proceeds to step S105.

  In step S105, the check result is displayed. FIG. 8 is a diagram showing an image of the determination result dialog 60 displayed in the present embodiment. The display unit 23 refers to the contents of the logical calculation table 4 generated by the processing up to step S104, and when the countermeasure status flag of the cell corresponding to the top event is set to “1” (see FIG. 6). Then, a “measures OK” determination result dialog 60 is displayed to notify the user that the occurrence of the top event can be prevented with the set countermeasure contents (see FIG. 8).

Further, in step S105, a countermeasure completed mark 64 is displayed. FIG. 9 is a diagram showing a display image of the background factor FIG. 3 in which the countermeasured mark 64 generated in the present embodiment is superimposed and displayed. The display unit 23 refers to the contents of the logical calculation table 4 generated by the processing up to step S104, and the cell whose countermeasure status flag is set to “1” among the events shown in FIG. The countermeasured mark 64 is superimposed on the event corresponding to (see FIG. 9). In the present embodiment, a round mark is used as the countermeasured mark 64. Thereafter, the processing shown in this flowchart ends.

  According to the problem analysis support system 1 according to the present embodiment, the user can logically easily grasp whether or not the chain of events leading to the top event in FIG. It becomes possible. In addition, the problem analysis support system 1 according to the present embodiment does not have specialized knowledge of problem analysis in order for the user to visually understand the contribution of the chain of events to the event and the solution of the problem to the problem. It is possible for the user to easily grasp whether or not a problem can be prevented. In addition, even if the current measures applied by the user are insufficient, it is possible to indicate the direction of re-examination on which part should be taken, thus reducing the time required for problem analysis You can also

  FIG. 10 is a diagram showing the background factor diagram 3 in a state in which some branches are excluded from the countermeasure check target by the exclusion mark 65 in the present embodiment. Using the exclude button 45 of the operation palette 40, the user can specify and exclude a desired branch from the countermeasure check target in the tree structure shown in the background factor diagram. For example, in the example shown in FIG. 10, branches below the node of “factor 2” are excluded from the countermeasure check. In this case, in the new creation of the logical calculation table 4 described in step S102, the node hanging on the branch with the exclusion mark 65 is ignored.

  FIG. 11 is a diagram showing the logical calculation table 4 created based on the background factor diagram 3 shown in FIG. 10 in the present embodiment. According to FIG. 11, it can be seen that the branch with the exclusion mark 65 is excluded from the background factor diagram 3 shown in FIG. 10. For this reason, since “factor 1” and “factor 2” are OR factors, the “problem 1” is not completed unless the countermeasure application mark 63 is attached to both of them. However, in the example shown in FIG. 11, among “Factor 1” and “Factor 2”, only “Factor 1” is provided with the countermeasure application mark 63, but the “Factor 2” branch is excluded. Therefore, the countermeasure status flag of “Problem 1” is “1”.

  According to the problem analysis support system 1 according to the present embodiment, using the exclusion function using the exclusion mark 65, the user can arbitrarily analyze various problems by assuming various situations. In the present embodiment, as a method for displaying that a predetermined branch is excluded from the countermeasure check target, a symbol such as an exclusion mark 65 that reminds prohibition or closure is used. Instead of this, other display methods such as displaying the branches to be excluded by shading, semi-transparent display, and light color display may be employed.

DESCRIPTION OF SYMBOLS 1 Problem analysis support system 3 Backside factor diagram 4 Logical calculation table 23 Display part 24 Information holding part 25 Judgment part 61 AND factor mark 62 OR factor mark 63 Countermeasure application mark 64 Countermeasure mark 65 Exclusion mark

Claims (9)

Display means for displaying a tree structure including a node indicating an event, including a parent node and a child node indicating a child event that is a cause of occurrence of the parent event related to the parent node;
Countermeasure status information holding means for holding countermeasure status information indicating a countermeasure status for the event in association with a node related to each event;
Determination means for determining whether or not the occurrence of a parent event caused by the child event is prevented by referring to the countermeasure status information related to the child event; and
The determination means includes
For a child event that generates a parent event when the logical AND of the event occurrence is true, the occurrence of the parent event is prevented if measures are applied to at least one of the child events. And
For child events that generate a parent event when the true OR of the event occurrence is true, the occurrence of the parent event is prevented when measures are applied to all of the child events. Judgment,
The display means displays the determination result on the tree structure when it is determined that the occurrence of a parent event is prevented by the determination means.
Problem analysis support system. The display means displays a mark indicating that the occurrence of the parent event is prevented for the node indicating the parent event that is determined to be prevented by the determination means.
The problem analysis support system according to claim 1. The countermeasure status information is set to true when a countermeasure is taken for an event, false when a countermeasure is not taken for the event,
The determination means includes
For a child event that generates a parent event when the true logical product of the event occurrence is true, when the logical sum of countermeasure status information of the child event is true, the occurrence of the parent event is prevented Judgment,
For a child event that generates a parent event when the true OR of the event occurrence is true, if the logical product of countermeasure status information of the child event is true, the occurrence of the parent event is prevented judge,
The problem analysis support system according to claim 1 or 2. A computer connected to the display device and the storage device
A display step of displaying on the display device a tree structure including a node indicating an event, the parent node and a child node indicating a child event that is a cause of occurrence of the parent event related to the parent node; ,
Countermeasure status information holding step for holding the countermeasure status information indicating the countermeasure status for the event in the storage device in association with the node related to each event;
Determining whether or not the occurrence of a parent event caused by the child event is prevented by referring to the countermeasure status information related to the child event; and
In the determination step,
For a child event that generates a parent event when the logical AND of the event occurrence is true, the occurrence of the parent event is prevented if measures are applied to at least one of the child events. And
For child events that generate a parent event when the true OR of the event occurrence is true, the occurrence of the parent event is prevented when measures are applied to all of the child events. Judgment,
In the display step, when it is determined that the occurrence of a parent event is prevented by the determination step, the determination result is displayed on the tree structure.
Problem analysis support method. In the display step, for a node indicating a parent event determined to be prevented by the determination step, a mark indicating that the occurrence of the parent event is prevented is displayed.
The problem analysis support method according to claim 4. The countermeasure status information is set to true when a countermeasure is taken for an event, false when a countermeasure is not taken for the event,
In the determination step,
For a child event that generates a parent event when the true logical product of the event occurrence is true, when the logical sum of countermeasure status information of the child event is true, the occurrence of the parent event is prevented Judgment,
For a child event that generates a parent event when the true OR of the event occurrence is true, if the logical product of countermeasure status information of the child event is true, the occurrence of the parent event is prevented judge,
The problem analysis support method according to claim 4 or 5. A computer connected to a display device and a storage device;
Display means for displaying, on the display device, a tree structure including a node indicating an event, the parent node and a child node indicating a child event that is a cause of occurrence of the parent event related to the parent node; ,
Measure status information holding means for holding measure status information indicating the measure status for the event in the storage device in association with a node related to each event;
By making reference to the countermeasure status information related to the child event, and functioning as a determination unit that determines whether or not the occurrence of the parent event caused by the child event is prevented,
The determination means includes
For a child event that generates a parent event when the logical AND of the event occurrence is true, the occurrence of the parent event is prevented if measures are applied to at least one of the child events. And
For child events that generate a parent event when the true OR of the event occurrence is true, the occurrence of the parent event is prevented when measures are applied to all of the child events. Judgment,
The display means displays the determination result on the tree structure when it is determined that the occurrence of a parent event is prevented by the determination means.
Problem analysis support program. The display means displays a mark indicating that the occurrence of the parent event is prevented for the node indicating the parent event that is determined to be prevented by the determination means.
The problem analysis support program according to claim 7. The countermeasure status information is set to true when a countermeasure is taken for an event, false when a countermeasure is not taken for the event,
The determination means includes
For a child event that generates a parent event when the true logical product of the event occurrence is true, when the logical sum of countermeasure status information of the child event is true, the occurrence of the parent event is prevented Judgment,
For a child event that generates a parent event when the true OR of the event occurrence is true, if the logical product of countermeasure status information of the child event is true, the occurrence of the parent event is prevented judge,
The problem analysis support program according to claim 7 or 8.

Images