Definition Error-Proofing vs. Mistake-Proofing - Differences

[David McGan]

I freqently see the terms "error-proofing" and "mistake-proofing" used in various contexts, with what I perceive as interchangeable definitions.

I know there are various degrees of "error/mistake" proofing (i.e. prevent from being made vs automatic detection if made / prevent from being moved to the next operation, etc).

My question is: Is there any real difference between the terms or should I assume that either can be used to connote the same concept?

While this might on the surface seem "much ado about nothing," serious discussions have arisen in the past over what is the appropriate terminology.

 

[jmp4429]

I’m pretty sure the two are interchangeable terms for exactly the same thing. However, I would not consider detection of the defect to be true “error proofing.” Error proofing should prevent the error in the first place.

 

[Jim Wynne]

I’m pretty sure the two are interchangeable terms for exactly the same thing. However, I would not consider detection of the defect to be true “error proofing.” Error proofing should prevent the error in the first place.

I agree; the terms are interchangeable, but automated inspection isn't error-proofing. An argument could be made, though, for some sort of thing that prevents further processing of defective material. The error being prevented isn't the defect iteself, but adding value to defective material.

 

[Craig H.]

I agree; the terms are interchangeable, but automated inspection isn't error-proofing. An argument could be made, though, for some sort of thing that prevents further processing of defective material. The error being prevented isn't the defect iteself, but adding value to defective material.

Jim, I'd have to say that I agree that MAYBE an argument could be made that inspection is error proofing, but I will gladly provide the other side to that argument. Semantics, I guess, but if the mistake can be prevented, it is much better than to have a wiz-bang inspection doohickey to spit the bad product out.

JMHO

 

[Miner]

Shigeo Shingo, who popularized the methods, made the following distinction:

Mistake-proofing - done to the PROCESS to prevent mistakes from occurring, stop the error from further processing, warn that the error has occurred, etc.

Error-proofing - done to the DESIGN to prevent assembly errors. Examples include adding design features to prevent upside-down, backwards or reversed assembly; using snap-together features to eliminate fasteners (eliminating missing, incorrect, high/low torque).

However, most people using the terms do not know this distinction and do use them interchangeably.

 

[Jim Wynne]

Jim, I'd have to say that I agree that MAYBE an argument could be made that inspection is error proofing, but I will gladly provide the other side to that argument. Semantics, I guess, but if the mistake can be prevented, it is much better than to have a wiz-bang inspection doohickey to spit the bad product out.

JMHO

I don't disagree, Craig. Prevention is better. But I think that if you're dealing with a specific human error, and the process has been optimized (i.e., it's making product as well as can be expected) then use of a device that prevents further processing (or shipment) of defectives might reasonably be referred to as error-proofing.