JP2007323219A - Fmea support method, apparatus, program and medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an FMEA (Failure Mode and Effects Analysis) support method and its apparatus that can ensure exhaustivity of failure modes and failure effects, provide input support even when new failure modes and new parts are input, and easily suppress word fluctuations. <P>SOLUTION: The FMEA support apparatus, which ensures the reliability of a product by predicting possible failures and extracting effects on the product and the causes of the failures, has function model data consisting of a function expansion representing functions implemented by the product and a part list, and an FMEA execution means having a failure mode input means for inputting failure mode nodes in relation to the function nodes, a failure effect node input means for inputting failure effect nodes in relation to the function nodes and a related part input means for presenting candidates for parts related to the failure modes. The input of failure modes based on the function expansion and part list for the product easily ensures exhaustivity of failure modes. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an information processing method for supporting FMEA work of a product, an apparatus therefor, a support program therefor, and a medium therefor.

  FMEA is an abbreviation for Failure Mode and Effects Analysis, which is called failure mode and its effect analysis in Japanese. This work is a kind of reliability analysis, and its purpose is to ensure product reliability at the development stage. A general FMEA result is a sheet as shown in FIG. 2 (hereinafter referred to as FMEA sheet). In other words, the work for creating the FMEA sheet is FMEA itself.

  FIG. 2 shows an example of an FMEA sheet for a flashlight. There are various types of FMEA sheets depending on the manufacturer, the field of manufacturing, project management, etc. Basically, the parts, functions, failure modes, effects of failures, influences, failure causes, occurrence rates, design management, There are items of detection rate and importance. Here, one line of the FMEA sheet is referred to as an FMEA record.

  The part column is a part of the target product, and is a target part of the FMEA record to be described. For example, the first FMEA record in FIG. 2 is a description of the part “battery” that constitutes the flashlight.

  The function column describes the function that the part is responsible for. In this example, the function of “supplying electricity from the battery to the miniature bulb” is raised.

  The failure mode column describes the state when the target component fails. In this example, a failure state of “no electricity supply” is described.

  The failure impact column describes the impact of the product as a whole on the user's standpoint, depending on the failure mode. This example describes the effect of a flashlight that “does not brighten”.

  The failure cause column describes the cause of the failure mode. Here, “battery exhaustion” is described as the cause of the failure.

  The design management column describes what measures should be taken in designing and manufacturing in order to prevent the failure. Here, “confirmation of remaining battery power” is described.

  The impact level is a numerical value that describes how severe the impact of the failure is on the product function. The occurrence rate describes how much the cause of failure is likely to occur by numerical values. The detection rate is a numerical value that describes how many causes of failure can be found by design management.

  Usually, the degree of influence, incidence, and detection rate describe the rank. For example, the rank is defined such that the rate of occurrence is 1 for 400, and 4 for one. This rank is determined according to the standard in the automobile industry, for example, and is evaluated in 10 stages. In each rank, 10 is the most serious, the incidence is high, and the detection is difficult.

  Importance is the product of impact, incidence, and detection rate. The above-described rank definition indicates that the greater the importance, the more important the other FMEA records, and the higher priority should be given to design and manufacturing measures.

  FIG. 3 shows a procedure for creating a conventional FMEA sheet. This procedure is disclosed in [Non-Patent Document 1].

  First, a target product is determined (step 301). Next, a target part is determined and described in the part column (step 302). Next, the practitioner considers the function required for the component in his / her head and describes it in the function column (step 303). Next, the practitioner considers the failure mode in his / her head and writes it in the failure mode column (step 304). Next, the influence on the product when the failure mode occurs is described in the failure influence column, and the influence degree is evaluated and described in the influence column (step 305). Next, the cause of the failure when the failure mode occurs is described in the failure cause column, and the failure occurrence rate is evaluated and described in the occurrence rate column (step 306). Next, a design management method is considered and described in the design management column, and the detection rate is evaluated and described in the detection rate column (step 307). Next, the importance is calculated and described (step 308). Up to this point, one FMEA record can be described. The user determines whether enough FMEA records have been described. If not, return to step 302 and repeat. If it is determined that it is sufficient, the process ends.

JP 2003-036278 A “Reference: Katsushige Onodera, Practical FMEA Method”

  Thus, when implementing FMEA, it is important to ensure the completeness in the failure mode extraction (step 304). If there is a leak in failure mode extraction, there is a high possibility that the related functions will not be satisfied, and reliability cannot be ensured. In FMEA, in order to prevent this, after inputting a function for each part (step 303), a failure mode is input in consideration of a failure as a loss of the function. However, the functions of parts and the input of failure modes depend on the idea of the designer, and it is difficult to ensure completeness. Inexperienced designers are likely to leak. Even veteran designers can expect to have a biased idea in their particular field. The functions that the parts are responsible for are functions for realizing the functions of the entire product, and it is difficult to ensure completeness without considering the relationship between the functions desired to be realized in the entire product and the parts.

  In addition, there is a problem that word fluctuation occurs when inputting to the FMEA sheet. For example, when FMEA for a pump is performed, the effect of a failure may be written as “no boost” at some locations, or “unboostable” or “unboostable” at some locations. . Even though they have the same meaning, if they are expressed differently, people who looked at the FMEA sheet later will be confused as to whether the effect is the same event or a different event. There is a problem that can not be. The same event must have the same expression and the same influence. The same applies to the failure mode and the cause of failure. In order to solve this problem manually, it is necessary to check whether the same event has already been described every time the failure mode, the influence of the failure, and the cause of the failure are entered, which is very time-consuming.

  In the technique disclosed in Patent Document 1 as a conventional technique, already input FMEA sheets are stored in a database, and can be retrieved from the database at the time of creation and used for input. However, even in this technique, the completeness of the failure mode is as long as it is input to the database. In addition, when a new failure mode that is not in the database is input and when a new part is input, there is no relevant data in the database, so sufficient support cannot be provided. For example, in this technique, the influence of the failure is searched from the part and the failure mode, but if the failure mode is new or the part is new, no search result is obtained. Also, the failure mode is to be searched from the part, but if the part is new, no search result is obtained. In addition, the functions of the product and the necessary functions of the parts are entered manually, and the problem of language fluctuation cannot be solved.

  Thus, in the prior art, the mechanism for ensuring the completeness of the failure mode and the influence of the failure is not sufficient.

  Also, the support for inputting a new failure mode or a new part has not been sufficient.

  Furthermore, there has been a problem that requires a great deal of labor to prevent fluctuations in the language.

  The object of the present invention is to provide a mechanism for ensuring the completeness of failure modes and the effects of failure, and can provide input support even when new failure modes and new parts are input, and can easily suppress fluctuations in words. An FMEA support method that can be used, an apparatus thereof, and a support program medium.

  In order to achieve the above object, the present invention is to realize a product in an FMEA support apparatus that supports FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product. And FMEA execution means having input means for associating FMEA items with the function model data.

  Furthermore, in order to achieve the above object, the present invention provides an FMEA support apparatus that supports FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product. Function model data composed of function development and parts list expressing the function to be realized by the product, failure mode input means for inputting the failure mode node in association with the function node, and failure influencing node in association with the function node A failure influence node input means for inputting the information and a related parts input means for presenting candidate parts related to the failure mode are provided.

  Furthermore, in order to achieve the above object, the present invention provides an FMEA support method for supporting FMEA which predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product. It is characterized by storing function model data composed of a function expansion expressing a function to be realized and a parts list, and associating FMEA items with the function model data.

  Furthermore, in order to achieve the above-mentioned problem, the present invention provides an FMEA support method for supporting FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to secure the reliability of the product. Stores function model data consisting of function development and parts list that expresses the function to be realized by the product, inputs the failure mode node in association with the function node, and inputs the influence node of the failure in association with the function node And presenting candidate parts related to the failure mode.

Furthermore, in order to achieve the above-mentioned problem, the present invention is a program for FMEA support that supports FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product. The program performs FMEA support by constructing function model data composed of function development expressing a function to be realized by a product and a parts list, and input means for associating FMEA items using the function model data. It is a feature.

  Furthermore, in order to achieve the above-mentioned problems, the present invention predicts a possible failure and extracts the influence on the product and the cause of the failure, thereby performing FMEA support for supporting FMEA that attempts to ensure the reliability of the product. , Function model data composed of function development and parts list expressing the function to be realized by the product, failure mode input means for inputting the failure mode node in association with the function node, and failure failure in association with the function node. FMEA support is performed by constructing a failure influence node input means for inputting an influence node and a related part input means for presenting candidate parts related to the failure mode.

  According to the present invention, it is easy to ensure the completeness of the failure mode by inputting the failure mode while viewing the function development of the product and the parts list.

  Further, even when a new failure mode or a new part is input, an appropriate FMEA item input candidate can be indicated, and the effort of FMEA implementation can be saved.

  In addition, since input candidates are always indicated by new data, it is also effective when FMEA is reviewed.

Moreover, since the same node in the function model data 101 is used for the same failure effect, failure mode, failure cause, and design management, words are less likely to fluctuate. As a result, it becomes easy to set the same influence degree, occurrence rate, and detection rate to the same event, and it is possible to save the effort of performing FMEA.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[Description of configuration]
FIG. 1 shows a configuration example of system processing according to the present invention. These configuration examples are realized, for example, in a device configuration shown in FIG.

  The function model data 101 is data that mainly describes the relationship between product functions and parts. Data relating to FMEA input by this system is also stored in this functional model data.

FMEA execution means 102 accepts user input from user input means 104,
A means for performing FMEA is provided.

  The display unit 103 displays information necessary for the user to execute FMEA.

  User input and processing in FMEA execution means 102 are once held in the internal memory. The FMEA sheet output means 105 outputs the contents of the internal memory as an FMEA sheet when there is an output instruction from the user.

  The FMEA execution unit 102 includes a failure mode node input unit 106, a failure influence node input unit 107, a related component input unit 108, a failure cause data input unit 109, and a design management data input unit 110. The failure mode node input means 106 is a means for inputting the failure mode in association with the function node in the function model data 101.

  The failure influence node input means 107 is a means for inputting a failure influence node in association with a function node in the function model data 101.

  The related component input means 108 is a means for inputting a related component node in association with the failure mode node in the function model data 101.

  Failure cause data input means 109 is means for inputting failure cause data in association with a component node in the function model data 101.

  Design management data input means 110 is means for inputting design management data in association with the cause of failure in the function model data 101.

  Next, the function model data 101 will be described with reference to FIG.

  FIG. 4 represents the function model data 101 using a flashlight as an example. The function model data 101 includes a function expansion unit 401 and a parts list unit 402.

The function expansion unit 401 expresses a function for realizing the function of the product in a stepwise manner. Each element is called a function node 403. The product name 404 is inserted in the highest-level function node for convenience. The two functional nodes “brighten the object” and “make it held by hand”, which are lower nodes of the highest node, are the functions that the flashlight is trying to realize. Functional nodes are further expanded below each functional node. The failure mode node 405 is a special case of a function node and is described below a certain function node. Similarly, the failure affected node 406 is a special case of a functional node, and is described below a certain functional node.

The component list unit 402 includes component nodes as elements. Each part node is a part that constitutes a product, and corresponds to a part targeted for FMEA. Here, "bean bulb"
Three items of “battery” and “housing” are input. The component node is associated with the related function node. In FIG. 4, this relationship is indicated by a broken line connecting the component node and the function node. For example, it is shown that the component node “battery” is associated with the function nodes “supplying electricity from the battery to the miniature bulb” and “composing an electric circuit”.

  Failure cause data 408 is associated with the component node. The “battery” node in FIG. 4 is associated with two failure cause data of “battery dead” and “voltage drop”. Although not shown in FIG. 4, design management data can be associated with failure cause data.

  The failure mode node includes a plurality of confirmed FMEA record data. The confirmed FMEA record is data for holding user input data when FMEA is performed.

  FIG. 5 shows an example of the confirmed FMEA record. This confirmed FMEA record shows a data item 501 and a data example 502.

  FIG. 7 illustrates a display example of the display on the display unit 103. This shows a part of the interface with the user in FMEA implementation.

  The display includes a function expansion display unit 701, a component list display unit 702, an FMEA input unit 703, buttons that trigger various inputs (new failure mode input button 711, new component input button 712, failure cause input button 713, FMEA output Button 714).

  The function expansion display unit 701 and the parts list display unit 702 are parts for displaying the function model data 101.

  The FMEA input unit 703 displays data regarding the failure mode node selected by the function expansion display unit 701. If the selected node is not a failure mode node, nothing is displayed. The FMEA input unit 703 includes a confirmed FMEA record display unit 704, a function / failure mode display unit 705, a failure effect editing unit 706, a related part editing unit 707, a failure cause data editing unit 708, a design management data editing unit 709, and an input confirmation. Button 710. Each role and function will be described when the FMEA implementation procedure described later is described.

  Buttons serving as triggers for various inputs (new failure mode input button 711, new component input button 712, failure cause input button 713, FMEA output button 714) will also be described when the FMEA implementation procedure described later is described.

  FIG. 12 shows an example of a device configuration for performing the system processing of the present invention.

  In the device configuration shown in FIG. 12, the procedure for the user to execute FMEA using the function model data 101 and the input from the user and obtain the FMEA sheet will be described with reference to FIG. In the description, the data example shown in FIG. 4 is used.

Central processing unit 1201 includes FMEA execution means 102. The external storage device 1202 includes function model data 101. Further, the FMEA sheet output by the FMEA sheet output means 105 is held. The internal memory 1203 holds user data input by the user input unit 104 and data being processed by the FMEA execution unit 102. A display 1204 is a device corresponding to the display means 103. A keyboard 1205 and a mouse 1206 are devices for accepting user input and instructions in the user input means 104.

  Next, an input example of a new failure mode using the device configuration example of the present invention will be described using the flowchart of FIG.

  The user first reads the function model data of the product to be FMEA into the FMEA execution means 102 (step 601). Thereby, the function model of the target product is displayed on the function expansion display unit 701 and the component list display unit 702 in FIG.

  Next, the user selects a function node corresponding to the function for which the failure mode is to be examined from the function expansion display unit 701 (step 602). Here, for example, it is assumed that the function node “supply electricity from the battery to the miniature bulb” is selected.

  Next, the user inputs a new failure mode using the failure mode node input means 106 (step 603). The new failure mode is input by, for example, pressing an input button 711 for a new failure mode to open an input dialog as shown in FIG. For example, the failure mode “low power supply” is input. As a result, the function node “supplying electricity from the battery to the miniature bulb” is associated with two failure modes “no supply of electricity” and “low supply of electricity”.

  After step 603, the FMEA input unit 703 displays data regarding the newly input failure mode. The function / failure mode display portion 705 displays the input failure mode and the function node associated with it. Further, the failure influence node input unit 107 estimates the influence of the failure due to the inputted failure mode, and lists it in the failure influence editing unit 706. Similarly, the related component input unit 108 estimates the component nodes related to the failure mode that has been input, and lists them in the related component editing unit 707.

  The list of failure effects can be obtained by processing as follows. The failure influence node input means 107 checks the inputted failure mode node itself and its upper function node to check whether or not the failure influence node is related. If there is an association, it is listed up in the failure effect editing unit 706. For example, the function nodes “supply electricity from a battery to a miniature bulb”, “supply electricity”, “brighten an object”, and “flashlight” are examined here. Then, two failure effect nodes “not brighten” and “light is weak” related to the function node “lighten the object” are listed and displayed on the failure effect editing unit 706.

A list of related parts can be obtained by processing as follows. The related component input means 108 checks the input failure mode node itself and its upper function node, and checks whether or not the component node is related. If there is an association, the associated part editing unit 707 is listed. For example, here is a function node "Supplying electricity from a battery to a miniature bulb"
Check "supplying electricity", "brightening objects", and "flashlight". Then, the two component nodes “battery” and “bean bulb” associated with the function node “supply electricity from the battery to the mini bulb” are listed and displayed on the related component editing unit 707.

  Next, the user inputs the influence of the failure using the failure influence node input means 107 (step 604). Specifically, the selection is made from the failure influence editing unit 706. Here, if an appropriate item is not listed in the failure influence editing unit 706, it can be newly input.

  Before the FMEA is performed, the failure influence is input by selecting a related function node from the function model data 101 and inputting it as a failure influence node in the lower level, and in the middle of the FMEA execution procedure shown in FIG. It is also possible to input by pressing a new creation button in the failure influence editing section 706. The input is performed from a failure influence input screen as shown in FIG. 9, and the failure influence and the influence degree are input. When the influence of the failure is input from the new creation button, the higher-order function node is traced from the failure mode being input, and is associated with the function node of the second layer from the highest level. In this example, a failure influence node is created as a lower node of the function node “brighten the object”.

  Next, the user inputs related parts using the related parts input means 108 (step 605). Specifically, selection is made from the component nodes listed in the related component editing unit 707. Here, if an appropriate component is not listed in the related component editing unit 707, it can be newly input.

  There are two cases where an appropriate part is not listed, that is, in the parts list display section 702 but not in the related parts editing section 707, and not in the parts list display section 702. In the former case, the component node is associated with the failure mode node being input. In the latter case, a new component input button 712 is pressed to create a component node, and similarly, the component node and the failure mode node being input are associated with each other.

  When a related part is selected from the related part editing unit 707, the cause of failure of the input failure mode is listed by the failure cause data input unit 109 and displayed on the failure cause data editing unit 708. Since the failure cause data is data associated with the component node, the failure cause data related to the component selected by the related component editing unit 707 may be listed.

Next, the user inputs failure cause data using the failure cause data input means 109 (step 606). Specifically, an appropriate failure cause is selected from the failure cause data editing unit 708. Here, if an appropriate failure cause is not listed in the failure cause data editing unit 708, it can be newly entered.

  The failure cause data is input before the FMEA is performed by selecting a related part node from the function model data 101 and inputting the failure cause data as an attribute thereof, and in the middle of the FMEA implementation procedure shown in FIG. It is also possible to input by pressing a new creation button in the cause data editing unit 708. Input is performed from a failure cause data input screen as shown in FIG. 10, and failure cause data and an occurrence rate are input. When failure cause data is input from the new creation button, it is associated with the component selected by the related component editing unit 707.

  When the failure cause data is selected from the failure cause data editing unit 708, the design management data input unit 110 lists the design management items of the input failure mode in the design management data editing unit 709. Since the design management data is data related to the failure cause data, the design management data related to the failure cause data selected by the failure cause data editing unit 708 may be listed.

  Next, design management data is input using the design management data input means 110 (step 607). Specifically, design management data is selected from the design management data input means 110. If appropriate design management data is not listed in the design management data input means 110, it can be newly input.

  The design management data is input by pressing a new creation button in the design management data editing unit 709 during the FMEA implementation procedure shown in FIG. Input is performed from a design management data input screen as shown in FIG. 11, and design management data and a detection rate are input. The design management data is associated with the failure cause data selected by the failure cause data editing unit 708.

  At this stage, the necessary items for the FMEA record are available. The user confirms the content and presses the input confirmation button 710 (step 608). As a result, the input FMEA record data is associated with the failure mode node as confirmed FMEA record data having the contents shown in FIG. At the same time, it is displayed on the confirmed FMEA record display unit 704.

  Next, the user determines whether or not input has been completed for all FMEA records (step 609). Here, in the function expansion display unit 701, it is considered that FMEA has been sufficiently implemented or not yet sufficient by checking whether or not an appropriate failure mode node is in the lower level for each function node. It is possible to determine whether there is a possible failure mode.

  If it is determined that the input of the FMEA record is insufficient and it is determined that the input has not ended, the process returns to the selection of the functional node to be examined (step 602) and the input of the FMEA record is continued. There may be a case where a plurality of influences, parts, failure cause data, and design management data are considered in one failure mode. At this time, after pressing the input confirmation button 710 (step 608), the process may return to the selection of the failure influence (step 604) without repeating the process until step 302, and the confirmation button (step 608) may be repeated.

  If it is determined that the input of the FMEA record is sufficient and it is determined that the input has been completed, the user presses the FMEA output button 714 to output the FMEA sheet (step 610).

When the FMEA output button 714 is pressed, the FMEA sheet output unit 105 outputs the FMEA sheet by the following process. The FMEA sheet output means 105 checks whether or not confirmed FMEA record data exists for all failure mode nodes included in the function model data 101. If it exists, it is stored in the internal memory. When all the failure mode nodes have been examined, the order of the items is rearranged according to the format of the FMEA sheet as shown in FIG. In particular,
“Function node” of FMEA record data is changed to “Function” of FMEA sheet format.
Change the “failure mode node” of FMEA record data to “failure mode” of FMEA sheet format.
“Failure impact node” in FMEA record data is changed to “Failure impact” in FMEA sheet format.
Change the “influence” of FMEA record data to “influence” of FMEA sheet format.
“Related parts” of FMEA record data is changed to “Parts” of FMEA sheet format.
“Failure cause data” in FMEA record data is changed to “Cause of failure” in FMEA sheet format.
Change the “occurrence rate” of FMEA record data to the “occurrence rate” of FMEA sheet format.
“Design management data” of FMEA record data is changed to “Design management” of FMEA sheet format.
The “detection rate” of the FMEA record data is made to correspond to the “detection rate” of the FMEA sheet format. Finally, the importance is calculated by multiplying the influence, the occurrence rate, and the detection rate, and is described in the “importance” of the FMEA sheet format.

  Next, FMEA records are rearranged and output in an appropriate order. The output destination can be either the external storage device 1202 or the display 1204.

  The order of rearrangement is usually grouped for each part, and in the following, they are usually grouped in the order of failure mode, effect of failure, and cause of failure. Since the items to be preferentially taken are points with high importance, it is convenient for the designer to rearrange them in descending order of importance.

  According to the above-mentioned embodiment, even if it is input of a new failure mode and no FMEA record related to the failure mode “low power supply” has been input by any user so far, appropriate support to the user Can be realized.

  Next, a case where there are new parts will be described. If it is known before FMEA implementation that there is a new part that is not included in the functional model data 101, a part node is created and related functions are selected before selecting a functional node to be examined (step 602). Associate with a node. Further, if an event that causes a failure of the part is predicted and input as a cause of the failure, the trouble of performing FMEA can be further saved. The part node input and failure cause data input have been described above.

  For example, a case where a new component “switch” is considered in the data shown in FIG. 4 will be described. First, the user presses a new part input button 712 and inputs a new part “switch”. Next, the function node is associated. This can be associated, for example, by dragging the mouse or the like from the “switch” to the function node “configure electric circuit” on the screen shown in FIG.

  Next, the user performs FMEA according to the FMEA execution procedure shown in FIG. 6 and outputs an FMEA sheet.

  According to the above embodiment, at this time, even if the “switch” is a new part and no FMEA record related to the “switch” has been input by any user so far, in steps 603, 604, 605, 606. Appropriate input candidates can be displayed on the FMEA input unit 703. As a result, it is shown that even if it is an input of a new failure mode and no failure mode “less electricity supply” has been input by any user, appropriate support can be provided to the user.

  Next, a case where the existing failure mode is reviewed will be described. In the new failure mode input (step 603) of the embodiment described for the input of the new failure mode described above, the user does not always need to input a new failure mode. It is also possible to select the failure mode “no power supply” that has already been input in association with the function node “supply electricity from the battery to the miniature light bulb”, and to confirm or correct the content.

  At this time, if a new failure effect, part, failure cause, and design management have been entered after the failure mode to be reviewed, the newly added portion is also displayed in the corresponding column in the FMEA input unit 703. The

  This makes it possible to implement and review FMEA while always reflecting new data. This is effective when FMEA is implemented by a plurality of different people, or when reviewing the same FMEA over time.

  A specific apparatus for carrying out the present invention can be realized by a general-purpose computer system composed of devices as shown in FIG. 12 and a processing program operating on the general-purpose computer system, but is configured as a dedicated apparatus. It is also possible.

  When a processing program is added to such a general-purpose computer system, the processing program is recorded on a medium such as a magnetic disk 1301 shown in FIG. 13 or a CD-ROM 1401 shown in FIG. , And read by an optical reading device such as a magnetic disk reading device or a CD-ROM provided in the central processing unit 1201 and loaded into the internal memory 1203. When the processing program delivered through the communication network is captured by the input unit and realized, it can be repeatedly used by storing the stored processing program in a storage medium such as a magnetic disk.

  As described in the above embodiments of the present invention, according to the present invention, it is easy to ensure the completeness of the failure mode by inputting the failure mode while looking at the product function development and the parts list. .

  Further, even when a new failure mode or a new part is input, an appropriate FMEA item input candidate can be indicated, and the effort of FMEA implementation can be saved.

  In addition, since input candidates are always indicated by new data, it is also effective when FMEA is reviewed.

Moreover, since the same node in the function model data 101 is used for the same failure effect, failure mode, failure cause, and design management, words are less likely to fluctuate. As a result, it becomes easy to set the same influence degree, occurrence rate, and detection rate to the same event, and it is possible to save the effort of performing FMEA.

  The present invention relates to an information processing method, an apparatus, a support program, and a medium thereof that support FMEA work of a product. With the support of FMEA work, the reliability of the product is ensured at the development stage during product development. Can be realized.

It is a figure which shows the structural example of this invention. It is a figure which shows a general FMEA sheet. It is a figure which shows the procedure of general FMEA implementation. It is a figure explaining functional model data. It is a figure explaining the data structure of a definite FMEA record. It is a figure explaining the FMEA implementation procedure by this invention. It is a figure which shows the screen in the Example of this invention. It is a figure which shows a failure mode input screen. It is a figure which shows the influence input screen of a failure. It is a figure which shows a failure cause data input screen. It is a figure which shows a design management data input screen. It is a figure explaining an apparatus structure. Magnetic disk. CD-ROM.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 ... Functional model data, 102 ... FMEA execution means, 103 ... Display means, 104 ... User input means, 105 ... FMEA sheet output means, 106 ... Failure mode node input means, 107 ... Failure influence node input means, 108 ... Related Component input means 109 ... Failure cause data input means 110 ... Design management data input means 301 ... Determination of target product 302 ... Determination of target part 303 ... Description of function required for part 304 Description of failure mode, 305 Description of influence of failure and evaluation of degree of influence, 306. Description of cause of failure and evaluation of occurrence rate, 307 ... Description of design management and evaluation of detection rate, 308 ... Calculation of importance, 309 ... FMEA record input end determination, 401 ... Function deployment section, 402 ... Parts list section, 403 ... Function node, 404 ... Product name, 405 ... Disabled mode node, 406 ... influence node failure, 407 ... part node, 408 ... failure causes data, 501 ... confirm FMEA record data item,
502 ... Confirmed FMEA record data example, 601 ... Read function model data of target product, 602 ... Selection of function node to be examined, 603 ... Input of new failure mode, 604 ... Selection of influence of failure, 605 ... Selection of related parts, 606 ... Selection of cause of failure, 607 ... Selection of design management, 608 ... Confirm button, 609 ... Determination of completion of FMEA record input,
610 ... Output of FMEA sheet, 701 ... Function expansion display section, 702 ... Parts list display section, 703 ... FMEA input section, 704 ... Confirmed FMEA record display section, 705 ... Function / failure mode display section, 706 ... Edit effect of failure , 707 ... Related part editing part, 708 ... Failure cause data editing part, 709 ... Design management data editing part, 710 ... Input confirmation button, 711 ... New failure mode input button, 712 ... New part input button, 713 ... Failure cause Input button, 714 ... FMEA output button, 1201 ... Central processing unit, 1202 ... External storage device, 1203 ... Internal memory, 1204 ... Display, 1205 ... Keyboard, 1206 ... Mouse, 1301 ... Magnetic disk, 1401 ... CD-ROM.

Claims (12)

In an FMEA support apparatus that supports FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product,
Function model data composed of function development and parts list expressing the function to be realized by the product,
FMEA execution means having input means for associating FMEA items with the functional model data;
FMEA support device characterized by comprising: The FMEA support apparatus according to claim 1,
The FMEA support apparatus, wherein the input means includes failure mode input means for inputting a failure mode node in association with a function node. The FMEA support apparatus according to claim 2,
The FMEA support apparatus according to claim 1, wherein the input means includes failure influence node input means for inputting a failure influence node in association with a function node. The FMEA support apparatus according to claim 3,
The FMEA support apparatus according to claim 1, wherein the input means includes related part input means for presenting candidate parts related to the failure mode. In an FMEA support apparatus that supports FMEA that attempts to ensure the reliability of a product by predicting a possible failure and extracting the influence on the product and the cause of the failure,
Function model data composed of function development and parts list expressing the function to be realized by the product,
A failure mode input means for inputting a failure mode node in association with a function node;
A failure influence node input means for inputting a failure influence node in association with a functional node;
An FMEA support apparatus, comprising: a related part input unit that presents a candidate for a part related to a failure mode. The FMEA support apparatus according to claim 5, wherein
An FMEA support apparatus, comprising: a display unit having a function expanded on a display; a part list display unit; and an FMEA input unit. In an FMEA support method that supports FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product,
Storing function model data composed of function development and parts list expressing the function that the product is trying to realize;
An FMEA support method, wherein FMEA items are associated with the functional model data. In an FMEA support method for supporting FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product,
Stores function model data consisting of function development and parts list that expresses the function to be realized by the product,
Entering a failure mode node in association with a functional node;
Enter the affected node of the failure in association with the functional node,
A method for supporting FMEA, comprising presenting candidate parts related to a failure mode. In a program that performs FMEA support that supports FMEA that predicts a possible failure and extracts the influence on the product and the cause of the failure to ensure the reliability of the product,
The program includes function model data composed of a function development and a parts list expressing functions to be realized by the product,
A program for supporting FMEA by constructing input means for associating FMEA items using the functional model data.   A program medium storing the program of claim 9 in an electromagnetic or optical medium. In a program that supports FMEA that supports FMEA that tries to ensure the reliability of the product by predicting the possible failure and extracting the influence on the product and the cause of the failure,
Function model data composed of function development and parts list expressing the function to be realized by the product,
A failure mode input means for inputting a failure mode node in association with a function node;
A failure influence node input means for inputting a failure influence node in association with a functional node;
A program for supporting FMEA by constructing related component input means for presenting candidate components related to the failure mode. A program medium storing the program of claim 11 in an electromagnetic or optical medium.

Images