Mostrando las entradas con la etiqueta PDCA. Mostrar todas las entradas
Mostrando las entradas con la etiqueta PDCA. Mostrar todas las entradas

viernes, 13 de marzo de 2015

Zero Defects (無欠陥)– Part 2 of 3- San-Gen-Shugi methodology (Genba ,Genbutsu & Genjitsu.)

I have considered to describe on this article the San-Gen-Shugi methodology, which underlies the breakthrough approach for Problem Solving.

San-Gen-Shugi – Genba ,Genbutsu & Genjitsu.

San (three), Gen (reality) what you actually see in front of you and Shugi (principle).

San-Gen-Shugi (Principle of three realities) has three elements as shown below.

·      Gen-ba means, "Real Place”: Go to the shop floor to understand the reality.
·      Gen-butsu means, "Real Part": Look at the real part or the real services provided and analyze it while focusing on the facts.
·      Gen-jitsu means, "Real Facts": Present conclusions using real data for a better understanding of what is actually happening in the field.
Fig


Principle of Genchi Genbutsu.

Taiichi Ohno ; always promoted the principle of Genchi Genbutsu which means “Go and see for yourself”

There is no substitute for direct observation.
In many Organizations the employees try to solve problems (for example, why a machine is unreliable) by thinking about the problem and devising hypotheses that haven’t checked on the field. Toyota gets their employees to recognize the importance of direct observation.
Fig.


Managers should coach, not fix.
Each worker looks for ways to improve the quality applying Problem Solving PDCA, and the manager’s role becomes one of involving the team in identifying the problems and not doing all the work himself.
The TPS lends itself to Deming’s writings about Leadership who understood that traditional supervisory activities are reactive rather than proactive. Many managers to pay a great deal of attention to reports and data which tell them what happened yesterday, last week, last month, or last year. Often such reports highlight the things that have gone wrong. Deming has compared this to attempting to drive a car by looking only in the rear-view mirror. Because of this, he observed that, “A supervisor is an auditor of failure, while a leader listens and learns, studies and understands and works to improve the system.” He also noted that “One important characteristic of a leader is that he will forgive a mistake – there will be mistakes.”
Fig


On real Manufacturing world; the Engineers Team Support and Managers should work more like Dr. Gregory House rather than Dr. G , the difference is obvious Dr. House is fighting to save his patients , identifying how to solve pathological enigmas and in other hand Dr. G is analyzing why the patient has already dead.



If the organization wants solve problems and reach Zero Defect, the reaction time should be immediate ASAP.

For that purpose the Manufacturing Lines must be adapted with: Andons lights to call for assistance, Jidoka for Auto stops can be added, Defects Tables (Genbutsu Tables) and Defects Red Bins to avoid mix the Defects parts and Good parts, and also avoid the Defects Parts been Reworked.
The Standard Work for Problem Solving includes a clear Escalation path for problems assistance, next to the line and very visible, the Problem Solving template to use etc.
Fig.



Do not rework is critical for problem solving, to establish this rule is basic for a Zero Defect implementation, actually this is an important behavior that you may take in your account, if the Management have a real support for Lean Manufacturing they must be agree on this, otherwise the Management are just looking for Lean Fake and don’t have real intention to fix the problems.

The Team members must be conscious about the Defects; the Lean Managers should look for different ways to make them understand what a Defects means.
Fig.


The Management Roll in Problem Solving.

The management has the main roll on Problem Solving; maybe this is the most critical difference between Toyota and other Organizations, unfortunately in most of the organization the Management delegates this responsibility to lower levels.

       Quality management method
  1. Do you understand the defect condition?
  2. If yes, did you define the correct method – to set up Defects Table to control the condition?
  3. If yes, did you fully utilized Defects Table?
  4. How to fully utilize the Defects Table? – Any defect must display in Defects Table managers and engineers shall check Defect Table every one hour, engineer must use 5why to analyze and resolve the problem immediately
  5. Check if defects reduced
  6. If defect number close to 0
  7. If the same defect code happen again, the machine should be able to stop automatically until the leader or technician resolve the problem, operator not allow to reset the machine, which is PoKa-Yoke method to prevent the defect happen again.


       If you want to become a Problem Solving Master - Do not assume or talk only or if not, you become a fortune teller:
  1. Do you understand the problem?
  2. If yes, do you understand the method to change or correct?
  3. If yes, did you follow the method to do?
  4. If yes, did you confirm the achievement? 
  5. If yes, did you monitor if the abnormal still there?
  6. If the abnormal confirmed does not exist anymore, did you Yokoten the method to other lines?
  7. If you did Yokoten, did you monitor if the good condition maintain?
  8. Until you do till the item 7, you become an honest person a Real Problem Solving Master, or if not, you are assuming the situation can be better, then you will become a fortune teller.

Metrics to Zero Defects.

       MTBF : Mean Time Between Failure
       MTBR: Mean Time Between Response
       MTBRC: Mean Time Between Rood Cause
       MTBPS: Mean Time Between Permanent Solution (Pokayoke)
       Top Defects – Solve one per day
       Time to attend Red Light – 10 sec max.
       Time to implement Quality Alert:
       Customer defects finding  - 1 day
       Internal defects top finding – 1 hr
       Zero Defects per line – No ppm´s  No % yield



Œ Change ATTITUDE : San Gen Shugi

. . .Applying “Genjitsu” means being realistic, not idealistic.  “Genba” means going out on the shopfloor to discover the real root causes of problems.  And “Genbutsu” refers to real parts, and the way of dealing with non-conformance. 
We must use non-conformance parts to learn how to improve and achieve Total Quality.    

I have only two methodologies:  my eyes and my legs.  These are all I need to see, to judge, to consider, to decide.  This is the basis of “SanGenShugi”. . .
(Kazuo Kawashima, June, 2002)

We should follow the advice of Sensei Taiichi Ohno and look on "facts"..... 




I hope this help you in your next Problem Solving Event…..

sábado, 28 de febrero de 2015

Zero Defects (無欠陥) – Part 1 of 3 - Five Elements of Production and the Five W’s and one H.

This article is intended to describe the sequence for Root Cause analysis, from the point of view of Sensei Shigeo Shingo and is based on my own experiences as an instructor of TPS continuous Improvement also.


Its not intended to describe how a template must be filled or completed, the scope is more conceptual, it talks about the interrelation of the tools Ishikawa diagram, 5 W’ 1 H & the 5 whys?


Write about Zero Defects is not simple, so I have divided in 3 parts and this is the first one.

The below diagram is basic when determining the root cause of a problem. This Diagram, was first described by Sensei Shigeo Shingo in his book; Zero Quality Control: Source Inspection and the Pokayoke System.

Five Elements of Production and the Five W’s and one H.

Fig.


It is very common for beginners in the method of problem-solving, wanting to go directly to the solution, without investing a reasonable time analyzing and finding the true root cause of the problem. Usually when I wonder what part is the most important for problem-solving over 90% of people answer Pokayoke, however are in error and without discrediting the importance of implant a good Pokayoke, the most important thing is to find the root cause problems, however it is extremely difficult.

In my experience this tools sequence have gave me good results, starting from Problem definition, 5W & 1 H, followed by Ishikawa Diagram until answer the 5 Whys that demystify the Root Cause

Five W’s  one H.
Fig.


It’s an Information Gathering method; that helps to define the problem, with data and facts.
5W1H (what, where, when, who, how, why) is a method of asking questions about a process or a problem taken up for improvement. Four of the W’s (who, what, where, when) and the one H is used to comprehend for details, analyze inferences and judgment to get to the fundamental facts and guide statements to get to the abstraction. The last W (why) is often asked five times so that one can drill down to get to the core of a problem.

However many times is not easy to answer directly and we may get stuck in one question Why?.
In other worlds just after the problem have defined and the question Why? Is prompted the team may be in blank, not clue at all; for that situations we should use the Cause and Effect Diagram or Ishikawa Diagram, to discriminate all the possible causes and find the answer, that immediately will carry on a new question, Why?... and so on.


Ishikawa diagram.

Fig.


Depict the Causes of a specific event Common uses of the Ishikawa diagram are Product Design and Quality Defect prevention, to identify potential factors causing an overall effect. Each cause or reason for imperfection is a source of variation. Causes are usually grouped into major categories to identify these sources of variation.
Causes;
Causes in the often categorized, such as to the 5 M's, described below. Cause-and-effect diagrams can reveal key relationships among various variables, and the possible causes provide additional insight into process behavior.
Causes can be derived from brainstorming sessions. These groups can then be labeled as categories of the fishbone. They will typically be one of the traditional categories mentioned above but may be something unique to the application in a specific case. Causes can be traced back to root causes with the 5 Whys technique.

Typical categories are

The 5 Ms (used in manufacturing industry)
    Machine (technology)
    Method (process)
    Material (Includes Raw Material, Consumables and Information.)
    Man Power (physical work)/Mind Power (brain work):Kaizens, Suggestions
    Measurement (Inspection)

The original 5 Ms used by the Toyota Production System have been expanded by some to include the following and are referred to as the 8 Ms. However, this is not globally recognized. It has been suggested to return to the roots of the tools and to keep the teaching simple while recognizing the original intent; most programs do not address the 8Ms.
       Milieu/Mother Nature(Environment)
       Management/Money Power
       Maintenance

The categories typically include
       People: Anyone involved with the process
       Methods: How the process is performed and the specific requirements for doing it, such as policies, procedures, rules, regulations and laws
       Machines: Any equipment, computers, tools, etc. required to accomplish the job
       Materials: Raw materials, parts, pens, paper, etc. used to produce the final product
       Measurements: Data generated from the process that are used to evaluate its quality
       Environment: The conditions, such as location, time, temperature, and culture in which the process operates.

5 Why’s
The 5 why’s typically refers to the practice of asking, five times, why the failure has occurred in order to get to the root cause/causes of the problem. There can be more than one cause to a problem as well. In an organizational context, generally, root cause analysis is carried out by a team of persons related to the problem.
No special technique is required.

Fig.




However in the practice it’s not easy, and like I have mentioned before, there are situations when the team do not have the answers and they will need to do an Ishikawa diagram.


Lets see this example.
As you see the Ishikawa Diagram was used at the right moment, to demystify the answer or answers.

I hope this help you in your next problem-solving event.