View attachment 25776
Yes so let's consider the following hypothetical Failure Chain:
Too high pressure on the machine -> Too low Thickness -> Too high sound levels
For this failure chain, I could have detection actions aiming at:
- Controlling the pressure (at the Cause level)
- Controlling the Thickness (at the Mode level)
- Controlling the Sound (at the Effect level)
Since the Detection Actions column only has two options (Cause & Mode). What do I do with the 3rd one (Detection Action on Effect) ?
The 3rd column that you mention does not seem to appear above and I do not think it is featured in any of the 4th edition templates.
At any rate, a high pressure on the machine produces low thickness (product) and this results on high sound levels (due to low thickness), correct?
Function: to produce the part
Req: thickness [mm] (product)
Failure mode: low thickness (product)
Cause: low pressure in the machine (wrong setup? sensor malfunction? calibration off?)
Effects: high sound level (I assume this is the effect on the end user)
You are right to address detections of the cause and/or failure mode. You have an alarm for low pressure, or close loop control, or you have setup sheets, 1st piece check, variable/attribute gauging, and so on.
IMHO it makes no sense to discuss detection of the effect, being that the effect is what the end user (in this case) perceives or experiences. As such, the product is out there in the field. A detection of this would be through a complaint.
I would question the reason and value of including this detection type in the template.
Has anyone ever seen detection of the effect in the
FMEA literature?