Poka-yoke

Poka-yoke (ポカヨケ, [poka yoke]) is a Japanese term that means "mistake-proofing" or "inadvertent error prevention". A poka-yoke is any mechanism in any 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]

Etymology

Poka-yoke was originally baka-yoke, but as this means "fool-proofing" (or "idiot-proofing") the name was changed to the milder poka-yoke. Poka-yoke is derived from poka o yokeru (ポカを除ける), a term in shogi and igo referring to avoiding an unthinkably bad move.

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]

  1. The contact method identifies product defects by testing the product's shape, size, color, or other physical attributes.
  2. The fixed-value (or constant number) method alerts the operator if a certain number of movements are not made.
  3. 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.

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:

  1. Identification of the need
  2. Identification of possible mistakes
  3. Management of mistakes before satisfying the need

This approach can be used to emphasize the technical aspect of finding effective solutions during brainstorming sessions.

Benefits of poka-yoke implementation

A typical feature of poka-yoke solutions is that they don't let an error in a process happen. Other advantages include:[9]

  • Less time spent on training workers;
  • Elimination of many operations related to quality control;
  • Unburdening of operators from repetitive operations;
  • Promotion of the work improvement-oriented approach and actions;
  • A reduced number of rejects;
  • Immediate action when a problem occurs;
  • 100% built-in quality control;
  • Preventing bad products from reaching customers;
  • Detecting mistakes as they occur;
  • Eliminating defects before they occur.
gollark: Java 7 used to be able to, but mods need 8 now, but 9 somehow breaks the launcher because of course it does.
gollark: bcachefs looks interesting, but isn't actually in the kernel yet.
gollark: I overresearch current filesystem benchmarks *every time* I set up a Linux system and really need to stop doing it.
gollark: I mostly just use f2fs these days.
gollark: There are probably mods with fishes on older versions.

See also

References
  1. Robinson, Harry (1997). "Using Poka-Yoke Techniques for Early Defect Detection". Archived from the original on December 27, 2014. Retrieved May 4, 2009.
  2. Shingo, Shigeo; Dillon, Andrew (1989). A study of the Toyota production system from an industrial engineering viewpoint. Portland, OR: Productivity Press. ISBN 0-915299-17-8. OCLC 19740349.
  3. John R. Grout, Brian T. Downs. "A Brief Tutorial on Mistake-proofing, Poka-Yoke, and ZQC". MistakeProofing.com. Retrieved May 4, 2009.
  4. H Robinson. "Using Poka-Yoke techniques for early defect detection". Archived from the original on December 27, 2014. Retrieved June 18, 2012.
  5. "The Sayings of Shigeo Shingo: Key Strategies for Plant Improvement". QualityCoach.Net. Archived from the original on January 28, 2014. Retrieved August 20, 2012.
  6. "Poka Yoke or Mistake Proofing :: Overview". The Quality Portal. Retrieved May 5, 2009.
  7. Nikkan Kogyo Shimbun (1988). Poka-yoke: improving product quality by preventing defects. Productivity Press. p. 111. ISBN 978-0-915299-31-7.
  8. 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
  9. Misiurek, Bartosz (2016). Standardized Work with TWI: Eliminating Human Errors in Production and Service Processes. New York: Productivity Press. ISBN 9781498737548.

Further reading
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.