Poka-Yoke Technique, Methodology & Design Publication History POKA-YOKE Technique, Methodology & Design
Poka-Yoke Technique, Methodology & Design Publication History POKA-YOKE Technique, Methodology & Design
net/publication/304656076
CITATIONS READS
3 29,503
3 authors:
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
Critical Component Failure in Thermal Power Station by using MCDM View project
All content following this page was uploaded by Dr. Ajay Verma on 01 July 2016.
Publication History
Received: 29 April 2016
Accepted: 26 May 2016
Published: 1 July 2016
Citation
Rajan kumar, Dwivedi RK, Ajay Verma. Poka-yoke technique, methodology & design. Indian Journal of Engineering, 2016,
13(33), 362-370
Page | 362
POKA-YOKE TECHNIQUE, METHODOLOGY & DESIGN
ABSTRACT: Poka-yoke is a concept in total quality management which is related to restricting errors at
cradle itself. It deals with "error proofing", fail-safing or "mistake-proofing". A poka-yoke is idea generation or
mechanism development in a total productive management process that helps operator to avoid (yokeru)
mistakes (poka). The concept Poka-yoke was produced, and established by Japanese engineer Shigeo Shingo for
the Toyota Production System. The Poka-Yoke is an innovative technique for to keep away human error at
work. The technique starts by analysing the process for potential problems, categorising parts by the
characteristics of dimension, shape & size & weight, detecting process deviation from nominal procedures and
norms. The original idea overduepoka-yoke is to respect the intellect of workers. Poka-yokes are for freeing
worker’s time and mind to pursue more creative and value adding activities.
I. INTRODUCTION
In today’s competitive world any organisation has to manufacture high quality, defect free products at optimum
cost. The new culture of the total quality management, total productive management into the manufacturing as
well as service sector gave birth to new ways to improve quality of products. By using various tools of TQM
like KAIZEN, 6 sigma, JIT, JIDCO, POKA YOKE, FMS & etc. other technique. organisation is intended to
develop qualityculture.[2,6] The paper is intended to focus basic concept of poka yoke, types of poka yoke
system, ways to achieve simple poka yoke mechanism. It is also covers practical study work done by various
Page | 363
feedback and action take place at the error stage"[Shingo, 1986, p. 82].[4]During actual manufacturing of any
product there are too many very simple and monotonous steps which are carried out by operators. These are
monotonous work operations result in to mental fatigue and lack of interest in work which ultimately causes
silly mistakes of operators and we know that human is prone to errors even though he doesn’t want it. [5]To
avoid these simple mistakes by poka-yoke concept play important role. By implementing some simple solutions
we can avoid mistakes. The long term achievement of poka- yoke gives output of saving time and we release the
work pressure on mind of worker. We can use creativity and innovative skills of workers for more creative
operations instead of increasing pressure for monotonous activities This involvement of everyone in
organisation is basic need to rise roots of quality culture in the organisation.
1. Guide pin: Guide pins are often used as a means of ensuring the accuracy with which machined parts
are stacked on top of one another. They may also be used as a means of correctly aligning one
component of a two-part system with the other. The pin may actually come in the form of a bolt with a
tapered end or even in the shape of a bullet with the corresponding piece containing metal or
plasticized grommets at every contact point. The grommets would allow the guide pins to penetrate the
secondary component in order to ensure the accurate configuration of the two parts being put together.
2. Blinking light and alarm: modular design with sturdy housing for all indoor and outdoor
applications in tough conditions wherever machine status needs to be displayed and warning signals
given
3. Limit Switch: A limit switch is an electromechanical device that consists of a actuator mechanically
linked with a set of contacts. When any object comes into contact with the actuator, the device operates
the contacts to make or break an electrical connection. Limit switches are used in a different type of
applications and environments because of their ruggedness, ease of installation, and reliability of
operation. Limit Switch can determine the presence / absence, passing, positioning, and end of travel of
an object. Limit switch were first used to define the limit of travel of an object; hence the name "Limit
Switch".
4. Sensor: A sensor is a transducer whose purpose is to sense (that is, to detect) some characteristic of its
environs. It detects events or changes in quantities and provides a corresponding output, generally as an
electrical or optical signal; for example, a thermocouple converts temperature to an output voltage. But
a mercury-in-glass thermometer is also a sensor;
Sensing devise are traditionally used in poka-yoke
i. Physical contact device
ii. Energy sensing device
Page | 364
Fig-1; sensing object interrupt the light
Fig-2-Vibration sensor
Page | 365
Fig-3;cost& zero defects relation
Page | 366
6. Implement
7. Monitor and sign off
Identify Problem
Observation at workstation
Implementation Plan
Implement
Fig-4; Methodology
Page | 367
Fig-5 ;Poka-Yoke System design
Page | 368
6. Pressure relief valves are used in hydraulic circuit to prevent damage to system due to high pressure. In case
of high pressure the excess oil bleed off through check valve to the reservoir. It is control poka yoke system.
7. Check list is used to confirm that all subcomponents in assembly are assembled. It is control poka yoke
system.[2]
X CONCLUSION
To err is human nature so we can’t blame human being for each and every mistake. As like err, Intelligence is
also human nature so we can dominate preceding nature by next nature. Poka yoke is just a face of that
intelligence. We can avoid all the mistakes at the source itself by using above mentioned methodology. About
mistake proofing we can say that it is a system for organizing work that eliminates any chances of error by new
user is also. It also allow user to function without mistake or prevent error that are about to occur. In order to
implement quality management system successfully each activity should aim towards excellence. Poka yoke is
one of the most important tools in TQM (total quality management). Efficaciouspoka yoke results in increased
productivity with minimum waste (waste due to rework, scraps) because we are sure about the quality of
product, as mistakes are blocked at source itself. There may be any practical limitations in poka yoke but we
have to overcome all that for achieving the aim of product manufacturing “Fault, Waste & Delay” all of them
zero. In one decisionPoka-yoke(Mistake proofing) is launching preventive actions for systematic movement on
the success ladder of QMS with higher level of performance and productivity of system with high quality
products at minimum cost.
REFERENCES
[1]. M. Dudek-Burlikowska*, D. Szewieczek, “The Poka-Yoke method as an improving quality tool of
operations in the process”; Journal of Achievements in Materials and Manufacturing Engineering VOLUME
36ISSUE 1 September 2009
[2]. StewartAnderson,“Poka-Yoke: Mistake-Proofing as a Preventive Action”; THE INFORMED Outlook
Reprint: March 2002Volume7, Number 3
[3]. PAUL DVORAK Senior Editor; “Poka-yoke designs make assemblies mistake proof”;
http://www.penton.com/md MARCH 10, 1998MACHINE DESIGN
[4]. John R. Grout, and Brian T. Downs; “A Brief Tutorial on Mistake-proofing, Poka-Yoke, and ZQC”; Lean
Business Solutions UnitedStates
[5]. “Lean Six Sigma Operational - Delegate Workbook”; Mistake Proofing techniques; The British Standards
Institution;SSG06101ENUK - MP/Issue 1.1/ September 2008
[6]. Anil S. Badiger, R. Gandhinathan, V. N. Gaitonde, Rajesh S. Jangaler“Implementation of Kaizen and Poka-
yoke to Enhance Overall Equipment Performance - A case study”
[7]. Spath P L. Reducing errors through work system improvements. In: Spath PL, ed. Error reduction in health
care.Chicago: AHA Press, 2000. 202
[8]. Senders J W, Senders S J. Failure mode and effects analysis in medicine. In: Cohen MR, ed.
Medicationerrors: causes, prevention, and risk management. Sudbury, MA: Jones and Bartlett, 1999. 3.6
[9]. Anon Word Net Search 2.1. Word net.Princeton.Edu/Perl/web
[10]. Ulrich K T, Eppinger S D. Product design and development. 2nd ed. Boston: Irwin McGraw‐Hill, 1995
[11]. Stewart D M, Melnyk S A. Effective process improvement developing poka‐yoke processes. Production
[12]. S. Abrahão, E. Insfran, J.A. Carsí, M. Genero, Evaluating requirements modeling methods based on user
perceptions: a family of experiments, Information Sciences 181 (2011) 3356–3378.
[13]. I.F. Alexander, R. Stevens, Writing Better Requirements, Pearson Education Limited, Boston, 2002.
[14] .E. di Bella, A. Sillitti, G. Succi, A multivariate classification of open source developers, Information
Sciences 221 (2013) 72–83.
[15]. R. Bloomfield, J. Bowers, L. Emmet, S. Viller, PERE: Evaluation and improvement of dependable
processes, Proceedings of Safecomp (1996).
[16]. L. Chung, J. do Prado Leite, On non-functional requirements in software engineering, Conceptual
Modeling: Foundations and Applications (2009) 363–379.
[17]. T. Fawcett, An introduction to ROC analysis, Pattern Recognition Letters 27 (2006) 861–874.
[18]. B. Fields, M. Harrison, P. Wright, THEA: Human Error Analysis for Requirements Definition. Technical
Report YCS 294, University of York, 1997.
[19]. D. Firesmith, Common requirements problems, their negative consequences, and industry best practices to
help solve them, Journal of Object Technology 6 (1) (2007) 17–33.
[20]. Y. Freund, R.E. Schapire, A decision-theoretic generalization of on-line learning and an application to
boosting, Journal of Computer and System Sciences 55 (1) (1997) 119–139.
[21]. M. Glinz, On non-functional requirements, in: 15th IEEE International Requirements, Engineering
Conference RE’07, 2007, pp. 21–26.
Page | 369
[23]. D. Heckerman, Bayesian networks for data mining, Data Mining and Knowledge Discovery 1 (1997) 79–
119.
[24]. M. Jarke, P. Loucopoulos, K. Lyytinen, J. Mylopoulos, W. Robinson, The brave new world of design
requirements, Information Systems 36 (7) (2011)
992–1008.
[25]. H. Kaiya, M. Saeki, Using domain ontology as domain knowledge for requirements elicitation, in: 14th
IEEE International Requirements, Engineering
Conference, 2006, pp. 189–198.
[26].G. Kotonya, I. Sommerville, Requirements engineering with viewpoints, Software Engineering Journal 11
(1) (1996) 5–18.
[27]. G. Kotonya, I. Sommerville, Requirements Engineering: Processes and Techniques, J. Wiley, New York,
1998.
[28] .S. Lauesen, O. Vinter, Preventing requirement defects: an experiment in process improvement,
Requirements Engineering 6 (2001) 37–50.
[29]. P. Li, G. Chen, L. Dai, Fuzzy logic-based approach for identifying the risk importance of human error,
Safety Science 48 (2010) 902–913.
[30]. R. Likert, A technique for the measurement of attitudes, Archives of Psychology (1932) 140.
[31]. C. Lopez, J.L. Salmeron, Dynamic risks modelling in ERP maintenance projects with FCM, Information
Sciences (2012), http://dx.doi.org/10.1016/j.ins.2012.05.026.
[32]. A.A. Malik, B. Boehm, Quantifying requirements elaboration to improve early software cost estimation,
Information Sciences 181 (2011) 2747–2760.
[33].K. Mu, J. Hong, Z. Jin, W. Liu, From inconsistency handling to non-canonical
Page | 370