WO2013047140A1

WO2013047140A1 - Ft diagram creation assistance device and ft diagram creation assistance program

Info

Publication number: WO2013047140A1
Application number: PCT/JP2012/072731
Authority: WO
Inventors: 克成山本; 洋二平岡; 古川　慈之
Original assignee: ジヤトコ株式会社
Priority date: 2011-09-27
Filing date: 2012-09-06
Publication date: 2013-04-04

Abstract

This FT diagram creation assistance device is provided with: an editing unit which edits first data describing a tree structure of an FT diagram using a markup language in order to generate second data thereby; and an export unit which, on the basis of the second data, represents the tree structure of the FT diagram with ruled lines and character strings upon the sheet of the spreadsheet software in order to generate third data.

Description

FT diagram creation support device and FT diagram creation support program

The present invention relates to a technique for analyzing the cause of failure of a device, system, etc. and improving its reliability.

Fault tree analysis (Fault Tree Analysis, FTA) expands a failure event into a logical sum (OR) or logical product (AND) of lower-level events that cause the failure event to form a tree structure (hereinafter referred to as “FT diagram”). This is a method of extracting a serious cause from subordinate events and revising the design to prevent the occurrence of a failure. Since creation of an FT diagram requires a wide range of knowledge and high expertise in that field, a technology that supports the creation of an FT diagram is required (JP2009-289020A).

FIG. 19 is an example of an FT diagram. In this example, the failure event “the transmission loss by the belt vehicle is large” is analyzed. Since this failure event occurs when “slip amount is large” or “friction force is large”, “slip amount is large” and “friction force is large” are subordinate events of the failure event, and their relationship is Logical OR.

And, the phenomenon that “the friction force is large” occurs when “the drag force is large” or “the friction coefficient is large”, so that “the friction force is large” and “the friction coefficient is large” are “the friction force is large”. Are subordinate events, and their relationship is a logical sum. Since the event “high drag” occurs when “belt tension is high”, “high belt tension” is a subordinate event of “high drag”.

Among these events, events that have no event in the lower level, such as “slip amount is large”, “belt tension is large” and “friction coefficient is large” are called basic events, and in order to prevent the occurrence of failure events Measures against these basic events should be considered.

In this example, the upper event and the lower event are simply connected by a ruled line, and it is not described whether the lower event in the same row is a logical sum or logical product. This is a logical product of the lower-order events in the same row, since in many cases the logical sum is used, the logical sum is simply connected between the higher-order event and the lower-order event and between the lower-order events in the same row with ruled lines. This is because “AND” indicating a logical product is described beside the ruled line connecting the upper event and the lower event.

FT diagrams are often created using the ruled line function of spreadsheet software such as Microsoft's Excel (registered trademark). This is because the spread rate of spreadsheet software is high, and because the spread rate is high, it is suitable for another engineer to use an FT diagram created by a certain engineer.

However, the creation of an FT diagram using spreadsheet software is not efficient, and there is a problem that it takes time and effort, especially when it is desired to modify the FT diagram once created (addition, deletion, etc.). .

An object of the present invention is to make it easy to edit an FT diagram.

According to an aspect of the present invention, there is provided an FT diagram creation support device that edits first data describing a tree structure of an FT diagram in a markup language, thereby generating second data. FT diagram creation comprising: an export unit for expressing a tree structure of the FT diagram by ruled lines and character strings on a sheet of spreadsheet software based on the second data, thereby generating third data A support device is provided.

According to another aspect of the present invention, a computer edits first data describing a tree structure of an FT diagram in a markup language, thereby generating second data, and the second processing function described above. A program for realizing the export function for expressing the tree structure of the FT diagram by ruled lines and character strings on the sheet of the spreadsheet software based on the data and generating third data thereby is provided. .

According to these aspects, the FT diagram can be easily edited.

Embodiments of the present invention and advantages of the present invention will be described in detail below with reference to the accompanying drawings.

FIG. 1 is an overall configuration diagram of an FT diagram creation support apparatus. FIG. 2 is a diagram for explaining the function of the FT diagram creation support apparatus. FIG. 3 is a flowchart showing the processing contents of the import unit. FIG. 4 is a diagram showing a state in which an event is searched from data of an FT diagram created by spreadsheet software by the import unit. FIG. 5 is a diagram showing XML data generated by the import process. FIG. 6 is an example of a tree structure displayed on the display unit. FIG. 7 is a diagram illustrating a state in which a lower event is added to the top event. FIG. 8 is a diagram illustrating a state in which a lower event is deleted. FIG. 9 is a diagram illustrating a state in which a lower event is moved. FIG. 10 is a diagram illustrating a state in which a lower event is copied. FIG. 11 is a flowchart showing the processing contents of the event analysis unit. FIG. 12 is a diagram showing the state of analysis by the event analysis unit. FIG. 13 is a diagram showing an example of a term dictionary of fault value terms. FIG. 14 is a diagram illustrating an example of a term dictionary of physical quantity terms. FIG. 15 is a flowchart showing the processing contents of the consistency verification unit. FIG. 16 is a diagram showing display on the display unit and XML data before and after the consistency verification. FIG. 17 is a flowchart showing the processing contents of the export unit. FIG. 18 is a diagram showing how the XML data is converted into the data format of the spreadsheet software by the export unit. FIG. 19 is a diagram showing an example of an FT diagram.

<Overall configuration>
FIG. 1 shows the overall configuration of the FT diagram creation support apparatus 100. The apparatus 100 includes an input / output unit 1, a processing unit 2, a storage unit 3, a display unit 4, and an operation unit 5, and as shown in FIG.
-Import function that imports FT diagram data created by Excel (registered trademark) of Macrosoft Corporation and converts it into data written in markup language-FT written in markup language Editing function for editing a diagram on the display unit 4 Event analysis function for analyzing the specific contents of an event of an FT diagram described in a markup language FT of an FT diagram described in a markup language before or after editing Consistency verification function for verifying consistency (whether or not the development of subordinate events is correct)-FT diagram data described in the markup language after editing is converted into a spreadsheet software data format and exported It has a function.

“The data of the FT diagram created by the spreadsheet software” is the data of the FT diagram in which the tree structure is expressed by ruled lines and character strings on the sheet of the spreadsheet software. As shown in FIG. 19, a character string written in a cell surrounded by a ruled line is regarded as an event, and the tree structure of the FT diagram is expressed by connecting each event with a ruled line.

In this embodiment, “FT diagram data described in a markup language” is XML (Extensible Markup Language) data, and the contents of each event of the FT diagram and their tree structure are used using tags. Describe. In the following description, “FT diagram data described in a markup language” is assumed to be XML data.

In XML data, each event element is composed of a start tag <FaultTreeNode> and an end tag </ FaultTreeNode>. In the start tag <FaultTreeNode>, there are various attributes of the corresponding event (label attribute indicating the contents of the event, unit attribute indicating the unit of physical quantity handled by the event, qstate attribute indicating the fault value state of the event, and the relationship between the lower events Logic attribute indicating logical sum or logical product and verification attribute indicating physical quantity consistency verification result) are included.

The vertical relationship between the lower event and the higher event is expressed by placing the lower event element between the start tag <FaultTreeNode> and the end tag </ FaultTreeNode> of the higher event. In addition, events in the same row are expressed by arranging those elements in parallel.

The end tag </ FaultTreeNode> can be omitted as appropriate when the relationship between events is clear only with the start tag <FaultTreeNode>.

Describing each part constituting the apparatus 100, the input / output unit 1 is a wired or wireless network interface, a card reader, a USB connector, Bluetooth (registered trademark), or the like. The input / output unit 1 is used for exchanging data with an external server, personal computer or the like. The data to be exchanged mainly includes FT diagram data created by spreadsheet software for importing into the apparatus 100, and spreadsheet software edited or created by the apparatus 100 and exported from the apparatus 100. FT diagram data in data format.

The processing unit 2 includes a microprocessor, RAM, ROM, and the like. The microprocessor reads the program stored in the ROM or the storage unit 3 (to be described later) into the RAM and executes it, thereby executing the import unit 21, the editing unit 22, the event analysis unit 23, and the consistency verification unit. 24 and the export unit 25. Specific processing contents of each unit will be described later.

The storage unit 3 is a storage device such as a hard disk or a flash memory. The storage unit 3 stores data and programs necessary for the processing of the processing unit 2.

The display unit 4 is a display device such as a liquid crystal display. The display unit 4 displays the tree structure of the FT diagram, the consistency verification result of the FT diagram, the XML data being edited or created, and the like.

The operation unit 5 is an input device such as a keyboard, a mouse, and a touch panel. The operation unit 5 receives various operations from the user.

Next, the processing contents of each unit of the processing unit 2 will be described.

<Import unit 21>
The import unit 21 has a function of reading the data of the FT diagram created by the spreadsheet software through the input / output unit 1 and converting the data into XML data.

FIG. 3 is a flowchart showing the processing contents (program contents) of the import unit 21. The processing contents of the import unit 21 will be described with reference to this.

First, the import unit 21 searches for a top event from an FT diagram created by spreadsheet software in S1. A top event is an event in which there is no further event above it. Specifically, the import unit 21 searches for cells surrounded by ruled lines in order from the upper left of the sheet. Although an event may be described using a plurality of cells, here, in order to simplify the description, the description is limited to a case where the event is described in a single cell.

In S2, the import unit 21 determines whether a top event has been found. If it is determined that a top event has been found, the process proceeds to S3, and if not, the process ends.

In S3, the import unit 21 sets the found top event cell as an analysis target cell. Further, the import unit 21 prepares XML data including a start tag <FaultTreeDocument> and an end tag </ FaultTreeDocument> indicating that the data is FT diagram data, and adds a top event to the XML data. Specifically, the top event element including the start tag <FaultTreeNode> and the end tag </ FaultTreeNode> is added between the start tag <FaultTreeDocument> and the end tag </ FaultTreeDocument>.

In S4, the import unit 21 acquires a character string from the analysis target cell, and sets the acquired character string as the label attribute of the event corresponding to the analysis target cell. Further, the import unit 21 searches the area on the right side of the analysis target cell. If there is a character string “AND”, the import unit 21 determines that the lower event of the event corresponding to the analysis target cell is a logical product. It is judged that. Then, the import unit 21 sets “OR” for the logical sum and “AND” for the logical product as the logic attribute of the event corresponding to the analysis target cell.

In S5, the import unit 21 searches for a lower event of the analysis target cell. Specifically, a ruled line extending to the right side from the analysis target cell is traced, and a cell surrounded by the ruled line ahead is searched.

In S6, the import unit 21 determines whether a lower event has been found. If it is determined that a subordinate event has been found, the process proceeds to S7, and if not, the process proceeds to S8.

In S7, the import unit 21 sets the discovered lower event cell as the analysis target cell, and adds the lower event to the XML data. In the XML data, the element of the lower event is arranged between the start tag <FaultTreeNode> and the end tag </ FaultTreeNode> of the upper event, thereby expressing that it is a lower event. Then, the process returns to S4, the label attribute is set for the lower event, and further lower events are searched.

The import unit 21 repeats the processes from S4 to S7 until no lower events are found.

In S8, the import unit 21 searches for an event in the same row as the analysis target cell (hereinafter referred to as the same row event). Specifically, a ruled line branching downward from a ruled line extending to the left from the analysis target cell is traced, and a cell surrounded by a ruled line ahead of the ruled line is searched.

In S9, the import unit 21 determines whether the same event has been found. If it is determined that a similar event has been found, the process proceeds to S10; otherwise, the process proceeds to S11.

In S10, the import unit 21 sets a cell of the found same-order event as an analysis target cell, and adds the same-order event to the XML data. Elements of the same event are arranged so as to be in parallel with other elements of the same event, thereby expressing that they are the same event. Then, the process returns to S4, the label attribute is set for the same event, and the lower event and the same event are searched again.

The import unit 21 repeats the processes from S4 to S10 until no parallel event is found.

In S11, the import unit 21 sets the upper event of the same-line event found immediately before in the analysis target cell. In S12, the import unit 21 determines whether the event corresponding to the analysis target cell is a top event. If the event is a top event, the import unit 21 ends the process. If not, the import unit 21 returns to S8 and searches for the same event again. .

FT diagram data created with spreadsheet software is converted to XML data by the above processing.

FIG. 4 shows how the import unit 21 searches for events from the data of the FT diagram created by the spreadsheet software.

According to the above processing, first, a cell described as “the transmission loss by the belt vehicle is large” was found ((1) in the figure), and the top event “the transmission loss by the belt vehicle is large” in the XML data. Added.

Next, a cell described as “the slip amount is large” arranged on the right side is found ((2) in the figure), and the lower event “the slip amount is large” is added to the XML data.

Since there is no cell for another event on the right side of the cell described as “Large slip amount”, a cell in the same row is searched next, and a cell described as “high frictional force” is found. ((3) in the figure). Then, the same event “high frictional force” is added to the XML data.

In the same manner, the cells described as “high drag”, “high belt tension”, and “high friction coefficient” were found ((4) and (5) in the figure), and the subordinate event “drag in the XML data was found. Is added ", a sub-event" high belt tension ", and a parallel event" high friction coefficient "are added.

FIG. 5 shows the XML data generated by the import process. The tree structure of the FT diagram is expressed by the inclusion relationship of the tags <FaultTreeNode> </ FaultTreeNode>, and each event has a label attribute, a logic attribute, and a verification attribute. However, since the physical quantity consistency verification has not yet been performed, the verification attribute contains a temporary value.

Further, the display unit 4 displays the tree structure in a format as shown in FIG. The displayed tree structure is the same as the tree structure of the FT diagram expressed by ruled lines and character strings, but to make the tree structure easier to see, click the folder illustration displayed on the left side of the event with lower events. Then, it becomes possible to fold or expand the subordinate events.

<Editor 22>
The editing unit 22 has a function of correcting the tree structure on the display unit 4 while viewing the tree structure of the FT diagram displayed on the display unit 4. When the user changes the tree structure of the FT diagram on the display unit 4 by operating the operation unit 5, the editing unit 22 reflects the changed content in the XML data.

The following describes typical editing functions.

-Addition of subordinate events-
FIG. 7 shows a state in which a lower event is added to the top event. The left side in the figure is the display content of the display unit 4, and the right side in the figure is the XML data corresponding thereto. Further, the upper side in the figure shows a state before editing, and the lower side in the figure shows a state after editing (the same applies to FIGS. 8 to 10).

When the user selects the top event on the display unit 4, the editing unit 22 displays an editing menu (not shown) on the display unit 4. The edit menu includes “Add”, and when the user selects it, a window for inputting event attributes opens. When the user inputs an attribute such as a label attribute, the editing unit 22 causes the display unit 4 to display <event> below the top event.

When such an editing operation is performed on the display unit 4, the editing unit 22 reflects the content in the XML data in real time, and an element of <event> is added to the XML data as shown on the right side in the figure. The Since <event> is a subordinate event of the top event, the element of <event> is arranged under the top event start tag <FaultTreeNode>. In this example, the top event end tag </ FaultTreeNode> is omitted.

-Deletion of lower events-
FIG. 8 shows a state in which a lower event is deleted.

When the user selects <Event> on the display unit 4, the editing unit 22 displays an editing menu (not shown) on the display unit 4. The edit menu includes “delete”, and when the user selects this, the editing unit 22 deletes <event> in the display unit 4.

When such an editing operation is performed on the display unit 4, the editing unit 22 reflects the content in the XML data in real time, and the element of <event> is deleted from the XML data as shown on the right side in the figure. The

-Movement of events-
FIG. 9 shows a state where the lower event is moved.

In this example, “event A”, “event B”, and “event C” are arranged in the same row below the top event. When the user selects “event A” which is one of them, and drags and drops it on “event B”, the editing unit 22 changes “event A” to “event B” on the display unit 4. Move down.

When such an editing operation is performed on the display unit 4, the editing unit 22 reflects the contents in the XML data in real time, and as shown on the right side in the figure, the element of “event A” is “ It is moved between the start tag <FaultTreeNode> and the end tag </ FaultTreeNode> of “event B”.

-Copy event-
FIG. 10 shows a state when a lower event is copied.

In this example, “event B” and “event C” are arranged in the same row below the top event, and “event A” is arranged below “event B”. When the user selects “Event B” on the display unit 4, the editing unit 22 causes the display unit 4 to display an editing menu (not shown). The editing menu includes “Copy” and “Paste”. When the user selects “Copy” and subsequently selects “Event C” and selects “Paste”, the editing unit 22 displays the display unit. 4, “event B” and “event A” are moved below “event C”.

When such an editing operation is performed on the display unit 4, the editing unit 22 reflects the contents in the XML data in real time, and, as shown on the right side in the figure, in the XML data, the <EventC> <FaultTreeNode > And an end tag </ FaultTreeNode> are added elements of “event B” and “event A”.

The editing function described here is a part of the function of the editing unit 22, but similarly for other functions, when the tree structure of the FT diagram is changed on the display unit 4, the changed content is changed to XML. Reflected in the data in real time.

Therefore, when editing the XML data, the user does not need to be aware of the XML tag and the description method. If the tree structure displayed on the display unit 4 is edited on the display unit 4, the XML data can be easily rewritten. it can.

Note that, here, the XML data obtained by the import process has been described as being edited, but it is also possible to create new XML data by the editing unit 22 without importing.

<Event analysis unit 23>
The event analysis unit 23 has a function of analyzing a unit of physical quantity and a failure value state from the label attribute of each event and adding a unit attribute and a qstate attribute to each event.

FIG. 11 is a flowchart showing the processing contents (program contents) of the event analysis unit 23. The processing contents of the event analysis unit 23 will be described with reference to this.

First, the event analysis unit 23 extracts all events from the XML data and adds their label attributes to the event list in S21. The event list is text data for the work of this analysis.

In S22, the event analysis unit 23 determines whether the event list is empty. If the event list is empty, the process ends. If the event list includes an event, the process proceeds to S23.

In S23, the event analysis unit 23 sets the event at the top of the list as a target event that is an event to be analyzed, and sets the content as a target character string.

In S24, the event analysis unit 23 searches for a fault value term from the rear side of the target character string as shown in FIG. The search is performed by matching with the term dictionary using the term dictionary shown in FIG. The fault value term is a term that indicates what state the physical quantity included in the event will cause the failure.For example, if the event is `` high voltage '', it is `` high '', `` length '' If the event is “short”, “short” becomes the fault value term.

In S25, the event analysis unit 23 determines whether a fault value term has been found. If a fault value term is found, the process proceeds to S26, and if not, the process proceeds to S28.

In S26, referring to the term dictionary shown in FIG. 13, the fault value state attribute corresponding to the found fault value term is read, and this is set as the qstate attribute of the event to be analyzed. The qstate attribute is, for example, “+” if “high”, and “−” if “short”.

In S27, the event analysis unit 23 deletes the fault value term from the target character string.

In S28, as shown in FIG. 12, the event analysis unit 23 further searches for a physical quantity term from the rear side of the target character string. For the search, the term dictionary shown in FIG. 14 is used, and a physical quantity term is searched by matching with the term dictionary. The physical quantity term is, for example, “voltage” if the event is “high voltage”, and “length” if the event is “short”.

In S29, the event analysis unit 23 determines whether a physical quantity term has been found. If a physical quantity term is found, the process proceeds to S30, and if not, the process proceeds to S31.

In S30, the event analysis unit 23 refers to the term dictionary shown in FIG. 14, reads the unit of the discovered physical quantity term, and sets this as the unit attribute of the event to be analyzed. The attribute of the physical quantity term is, for example, “V” for “voltage” and “m” for “length”.

In S31, the event at the top of the list is deleted, and the process returns to S22.

The processing of S22 to S30 is repeated until the event list is determined to be empty in S22, and finally the unit attribute and qstate attribute are set for all the events in the list.

<Consistency verification unit 24>
The consistency verification unit 24 verifies whether or not the lower event is appropriately developed based on the physical quantity relationship between the upper event and the lower event in the XML data before or after editing, and each event based on the verification result. Has a function to set the verification attribute.

FIG. 15 is a flowchart showing the processing contents (program contents) of the consistency verification unit 24. The processing content of the consistency verification unit 24 will be described with reference to this.

First, the consistency verification unit 24 determines in S41 whether the event to be verified is a basic event. A basic event is a subordinate event that does not have a subordinate event. If the event to be verified is a basic event, there is no point in verifying the consistency. Therefore, the process proceeds to S42, and the verification attribute of the event to be verified is set to 0 indicating “unverified”. If the event to be verified is not a basic event, the process proceeds to S43.

In S43, the consistency verification unit 24 determines whether any of the following is established.
-The event to be verified does not include physical quantities.
-None of the sub-events of the event to be verified contains physics.

If any one of them is satisfied, the consistency cannot be verified, so that the process proceeds to S44, and the verification attribute of the verification target event is set to -1 indicating that it cannot be determined. . If neither is established, the process proceeds to S45.

In S45, regarding the physical quantity of the event to be verified and the physical quantity of the subordinate event, it is determined whether any of the following is satisfied.
-The unit of the physical quantity of the event to be verified can be expressed by adding or subtracting the unit of the physical quantity of the lower event. That is, the physical quantity of the event to be verified and the physical quantity of the lower event are the same unit.
The unit of the physical quantity of the event to be verified can be expressed by multiplication / division or power multiplication of the unit of the physical quantity of the lower event. That is, the unit of the physical quantity of the event to be verified can be expressed using the unit of the physical quantity of the lower event.

If any of them is established, there is a possibility that consistency is achieved (expansion of lower events is appropriately performed), and the process proceeds to S47 for further verification. Otherwise, the consistency is not achieved (the lower event is not properly expanded), so the process proceeds to S46, and the verification attribute of the verification target event is set to 3 indicating “inconsistency”. .

In S47, it is determined whether an event whose physical quantity is unknown is included in the lower level events. If an event with an unknown physical quantity is included in the lower level event, even if a positive determination is made in S45, there is a possibility that consistency is not achieved. Therefore, the process proceeds to S48, and the verification target event The verification attribute is set to 2 indicating that there is a “possibility of inconsistency”. If not, the consistency is achieved (the lower event is appropriately expanded), the process proceeds to S49, and the verification attribute of the verification target event is “consistent”. Is set.

This process is performed for all events included in the XML data, and the verification attribute is set for all events.

FIG. 16 shows the display on the display unit 4 and the XML data before and after the consistency verification.

By performing the consistency verification, the value of the verification attribute of each event is set, and the tree structure displayed on the display unit 4 is an illustration showing the verification result, for example, “match” indicates a circle, “invalid” A “match” is displayed on the right side of each event, and a “hyphen” is displayed on the right side of each event.

As a result, the user can easily know the possibility that the expansion of the sub-event has not been properly performed and the location where the expansion has not been appropriately performed, and can refer to it when correcting the FT diagram. .

<Export unit 25>
The export unit 25 has a function of converting the XML data edited by the editing unit 22 into a data format of spreadsheet software.

FIG. 17 is a flowchart showing the processing contents (program contents) of the export unit 25. The processing contents of the export unit 25 will be described with reference to this.

First, the export unit 25 determines whether a top event is included in the XML data in S51. If the top event is not included, the process ends. If the top event is included, the process proceeds to S52.

In S52, the export unit 25 prepares an empty sheet of spreadsheet software, and sets a predetermined cell at the upper left of the sheet as an editing target cell. Furthermore, the top event of the XML data is set as the target event.

In S53, the export unit 25 writes the contents of the label attribute of the target event in the edit target cell and surrounds the cell with a ruled line.

In S54, the export unit 25 determines whether there is a lower event in the target event. If there is a lower event, the process proceeds to S55, and if not, the process proceeds to S56.

In S55, the export unit 25 changes the editing target cell to a cell on the right side by a predetermined cell, and draws a ruled line extending to the cell. When the relationship between the target event and the lower event is a logical product, the character “AND” is written in the blank cell located above the ruled line. Then, the target event is changed to the lower event.

Then, the process returns to S53, and the export unit 25 writes the contents of the label attribute of the target event in the edit target cell and surrounds the cell with a ruled line.

S53 to S55 are repeated while a lower event exists, and if it is determined that there is no lower event, the process proceeds to S56.

In S56, the export unit 25 determines whether the same event exists in the target event. If the same event exists, the process proceeds to S57, and if not, the process proceeds to S58.

In S57, the export unit 25 changes the cell to be edited to a cell lower by a predetermined cell, and draws a ruled line extending to the cell. Then, the target event is changed to the same event.

S53 to S57 are repeated while an event in the same row exists, and if it is determined that there is no event in the same row, the process proceeds to S58.

In S58, the export unit 25 moves the editing target cell to the cell corresponding to the upper event and changes the target event to the upper event corresponding to the cell.

In S59, the export unit 25 determines whether the target event is a top event. If it is not a top event, the process returns to S56, where it is further determined whether there is an event that is the same as the target event, and if it is determined that it is a top event, the process ends.

Through the above processing, XML data is converted into the spreadsheet software data format.

FIG. 18 shows a state in which the XML data is converted into the data format of the spreadsheet software by the export unit 25.

According to the above processing, first, “the loss of transmission by the belt wheel is large”, which is the content of the label attribute of the top event, is written in a predetermined cell at the upper left of the spreadsheet sheet, and the cell is surrounded by a ruled line. ((1) in the figure).

Next, a ruled line is drawn from the cell at the top event to the cell to the right of the three cells, and the label attribute of the lower event “Large slip amount” is written in the cell, and the cell is surrounded by the ruled line (in the figure) (2)).

Next, a ruled line is drawn to the cell two cells below the cell where “slip amount is large” is written, and “high frictional force” which is the content of the label attribute of the same-line event is written to the cell, The cell is surrounded by a ruled line ((3) in the figure).

Similarly, cells in which “the drag force is large”, “the belt tension is large”, and “the friction coefficient is large” are written, and ruled lines connecting these cells are created ((4) and (5) in the figure). ).

The FT diagram is created on the spreadsheet sheet as described above. The created data can be transferred to a server or personal computer outside the apparatus via the input / output unit.

The embodiment of the present invention has been described above, but the above embodiment is merely one example of application of the present invention, and the technical scope of the present invention is limited to the specific configuration of the above embodiment. is not.

The present application claims priority based on Japanese Patent Application Nos. 2011-213325 and 2011-212326 filed with the Japan Patent Office on September 27, 2011. The entire contents of these applications are incorporated herein by reference. Embedded in the book.

Claims

FT diagram creation support device,
An editing unit that edits first data describing a tree structure of an FT diagram in a markup language, and thereby generates second data;
An export unit for expressing the tree structure of the FT diagram by ruled lines and character strings on a sheet of spreadsheet software based on the second data, thereby generating third data;
An FT diagram creation support apparatus characterized by comprising:
An FT diagram creation support apparatus according to claim 1,
A consistency verification unit that acquires a physical quantity of each event from the first or second data and verifies consistency of the first or second data based on a relationship between a physical quantity of a higher event and a physical quantity of a lower event; An FT diagram creation support apparatus, further comprising:
An FT diagram creation support device according to claim 1 or 2,
With a display,
The editing unit displays the FT diagram on the display unit based on the first data, and when the correction of the FT diagram is instructed on the display unit, the contents of the correction are converted into the first data. Reflect, thereby generating the second data,
FT diagram creation support device characterized by the above.
On the computer,
An editing processing function for editing the first data describing the tree structure of the FT diagram in a markup language, thereby generating the second data;
An export function for expressing the tree structure of the FT diagram by ruled lines and character strings on a sheet of spreadsheet software based on the second data, thereby generating third data;
A program to realize
The program according to claim 4,
The computer further acquires the physical quantity of each event from the first or second data, and verifies the consistency of the first or second data based on the relationship between the physical quantity of the upper event and the physical quantity of the lower event. A program for realizing the integrity verification function.
The program according to claim 4 or 5, wherein
The editing function displays the FT diagram on the display unit of the computer based on the first data, and when the correction of the FT diagram is instructed on the display unit, the contents of the correction are displayed on the first unit. A program that reflects data and thereby generates the second data.