Poka-yoke
Lua error in package.lua at line 80: module 'strict' not found.
Poka-yoke (ポカヨケ?) [poka yoke] is a Japanese term that means "mistake-proofing". A poka-yoke is any mechanism in a lean manufacturing process that helps an equipment operator avoid (yokeru) mistakes (poka). Its purpose is to eliminate product defects by preventing, correcting, or drawing attention to human errors as they occur.[1] The concept was formalised, and the term adopted, by Shigeo Shingo as part of the Toyota Production System.[2][3] It was originally described as baka-yoke, but as this means "fool-proofing" (or "idiot-proofing") the name was changed to the milder poka-yoke.
Contents
Usage
More broadly, the term can refer to any behavior-shaping constraint designed into a process to prevent incorrect operation by the user.
A simple poka-yoke example is demonstrated when a driver of the car equipped with a manual gearbox must press on the clutch pedal (a process step, therefore a poka-yoke) prior to starting an automobile. The interlock serves to prevent unintended movement of the car. Another example of poka-yoke would be the car equipped with an automatic transmission, which has a switch that requires the car to be in "Park" or "Neutral" before the car can be started (some automatic transmissions require the brake pedal to be depressed as well). These serve as behavior-shaping constraints as the action of "car in Park (or Neutral)" or "foot depressing the clutch/brake pedal" must be performed before the car is allowed to start. The requirement of a depressed brake pedal to shift most of the cars with an automatic transmission from "Park" to any other gear is yet another example of a poka-yoke application. Over time, the driver's behavior is conformed with the requirements by repetition and habit.
History
The term poka-yoke was applied by Shigeo Shingo in the 1960s to industrial processes designed to prevent human errors.[4] Shingo redesigned a process in which factory workers, while assembling a small switch, would often forget to insert the required spring under one of the switch buttons. In the redesigned process, the worker would perform the task in two steps, first preparing the two required springs and placing them in a placeholder, then inserting the springs from the placeholder into the switch. When a spring remained in the placeholder, the workers knew that they had forgotten to insert it and could correct the mistake effortlessly.[5]
Shingo distinguished between the concepts of inevitable human mistakes and defects in the production. Defects occur when the mistakes are allowed to reach the customer. The aim of poka-yoke is to design the process so that mistakes can be detected and corrected immediately, eliminating defects at the source.
Implementation in manufacturing
Poka-yoke can be implemented at any step of a manufacturing process where something can go wrong or an error can be made.[6] For example, a fixture that holds pieces for processing might be modified to only allow pieces to be held in the correct orientation,[7] or a digital counter might track the number of spot welds on each piece to ensure that the worker executes the correct number of welds.[7]
Shigeo Shingo recognized three types of poka-yoke for detecting and preventing errors in a mass production system:[2][6]
- The contact method identifies product defects by testing the product's shape, size, color, or other physical attributes.
- The fixed-value (or constant number) method alerts the operator if a certain number of movements are not made.
- The motion-step (or sequence) method determines whether the prescribed steps of the process have been followed.
Either the operator is alerted when a mistake is about to be made, or the poka-yoke device actually prevents the mistake from being made. In Shingo's lexicon, the former implementation would be called a warning poka-yoke, while the latter would be referred to as a control poka-yoke.[2]
Shingo argued that errors are inevitable in any manufacturing process, but that if appropriate poka-yokes are implemented, then mistakes can be caught quickly and prevented from resulting in defects. By eliminating defects at the source, the cost of mistakes within a company is reduced.[citation needed]
A methodic approach to build up poka-yoke countermeasures has been proposed by the Applied Problem Solving (APS) methodology,[8] which consists of a three-step analysis of the risks to be managed:
- identification of the need
- identification of possible mistakes
- management of mistakes before satisfying the need
This approach can be used to emphasize the technical aspect of finding effective solutions during brainstorming sessions.
See also
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Ivan Fantin (2014). Applied Problem Solving. Method, Applications, Root Causes, Countermeasures, Poka-Yoke and A3. How to make things happen to solve problems. Milan, Italy: Createspace, an Amazon company. ISBN 978-1499122282
Further reading
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
