New account
Write to us


FAQ 2018-04-11T09:48:51+02:00
Is the no-tool detector used for preventing or controlling purposes (detection of cause)? 2018-06-19T14:47:05+02:00

In accordance with AIAG approach (detectability table), this detector controls the cause from DET=2. It is not preventive – it does not prevent non-assembly of the tool but detects this problem instead.

Can I overstate SEV in comparison to DFMEA in PFMEA? 2018-06-19T15:02:22+02:00

Generally speaking, SEV values in PFMEA must arise directly from DFMEA. For sure you cannot understate SEV values. The only result of overstating SEV in PFMEA is that during the process analysis the effect for the internal process emerges (e.g. the operator may cut himself/herself), and this kind of effects are not considered by a constructor with regard to DFMEA. Therefore in DFMEA the specific fault may have SEV=4, that is insignificant effects for the user, but in the process (PFMEA) cause the operator to cut himself/herself, that is SEV=10.

Do I need to enter fault effects for internal customer, or it is optional only? 2018-06-19T15:01:49+02:00

Practical use of the requirements stipulated in the AIAG and VDA manuals show a range of customers, starting from internal customers and ending up with final user (for more about this, see CSRs of particular OEM customers).

How to transfer implemented improvements during another FMEA revision? 2018-06-19T15:00:24+02:00

Implemented actions are transferred to the taken-actions column. In turn new actions add a new line with actions entered in the same or other fault cause.

When to enter new RPN values – after actions have been planed or implemented? 2018-06-19T14:59:49+02:00

New RPN values are entered in two cases:

a) When actions are recommended – you enter the goal you wish to achieve.

b) When actions are implemented – you enter the real result of the actions after efficacy has been assessed (the goal is not always achieved!)

Does OCC mean existence of fault or cause? 2018-06-19T14:59:15+02:00

OCC stands for occurrence which means occurrence of fault cause.

How to describe controlling actions when we have complete protection of fault cause and OCC=1? 2018-06-19T14:58:25+02:00

In accordance with AIAG terminology, you can describe detection as:
Detection assured through prevention (1)”.

Is it necessary to enter effects in the form of increased internal defectiveness if it is the result of the inspection? 2018-06-19T14:57:36+02:00

The general rule is that when you describe effects of the failure, you should assume that it goes through internal and external processes without any control, and „goes” towards the final customer. If the failure does not cause the process to stop  (e.g. because it is impossible to mount a part due to too small diameter of the hole), you should not describe the so-called internal effects (in the process). Such approach prevents the risk analysis from showing all problems which may be relevant to the company adopting FMEA. For this reason it is a „good practice” to enter an internal effect (for the company) in the form of increased defectiveness,  a need to repair, etc. In this case FMEA will demonstrate problems arising from a specific failure more comprehensively.

Is it possible to lower SEV in PMEA? 2018-06-19T14:46:30+02:00

If lowering arises from previous high internal effects which had an impact on the ultimate value in SEV column, then the answer is yes; nevertheless two cases are taken into consideration:

  1. DFMEA was not available and Unknown Function (10) was entered; during further revisions there was an update to include available data from the existing DFMEA.
  2. During tests and validation, previously assessed effects turned out to be too strict and thus overstated SEV value.

Please remember: at present the ultimate SEV value in PFMEA is affected by results from at least three effect fields: internal, external and user.