Starting with the new FMEA “on a green field” is challenging. It is better to take an existing analysis, or parts of it, and modify them accordingly. Thus, Generic and Family FMEA come into play. These are quite common terms, especially since the release of the harmonized methodology. How do these two approaches differ and how do we implement them in the EISOD X system?
Generic (basic) FMEA is the general basis for creating a specific analysis. There can be several cornerstones, e.g. for different process steps. It is permissible to generalize knowledge, requirements, functions and actions so that the same description can be used as a basis for different products. It is assumed that a particular product’s FMEA contains a reference to a generic FMEA, or that the generic FMEA becomes a basis that is further modified according to the particular product.
The family FMEA, on the other hand, is specific from the beginning and represents an analysis for several similar (related products). Minor differences of these products must then be resolved in a separate analysis, or otherwise appropriately incorporated into the family FMEA.
We use both of these approaches in the EISOD X system. When creating a new analysis, we can copy the existing FMEA of a related product, including maintaining all links. This means, that e.g. by modifying a specific failure function in one analysis, this failure function will automatically change in the related FMEA. However, the user always has the option whether to maintain the connection for this particular function (family FMEA principle) or to cancel it and modify each occurrence separately (generic FMEA principle).
Furthermore, there is the possibility, in accordance with the principle of generic FMEA, to “compose” an analysis for a specific product from generally described process steps, or specific steps from other analyzes. Basically, it is a matter of copy/paste, when in a few clicks we transfer a whole group of process elements, functions, failures and actions, which are interconnected, but after copying are no longer bound to the source FMEA.
Does the FMEA issue seem too complicated to you? Contact us, we will be happy to explain everything and display online for you.