Root Cause Analysis
Six Sigma – iSixSigma › Forums › Old Forums › General › Root Cause Analysis
- This topic has 13 replies, 11 voices, and was last updated 15 years, 8 months ago by
Savage.
-
AuthorPosts
-
May 3, 2006 at 3:30 pm #43296
Can anyone help me find a good resource for a root cause analysis procedure? I have been reading up on some but I didn’t find any generic process for RCA. I know at GE, they use a software called Apollo. Does anyone know of any other RCA softwares out there.
AJ0May 3, 2006 at 4:13 pm #137174
Dr. Eugene JacquescoleyParticipant@Dr.-Eugene-JacquescoleyInclude @Dr.-Eugene-Jacquescoley in your post and this person will
be notified via email.AJ,What is your ultimate goal of pursuing RCA?E
0May 3, 2006 at 4:26 pm #137176My ultimate goal is to create a standard procedure for our Quality Group to utilize RCA for their issues. Currently there is no set standard for RCA in our three quality divisions. I would like to form one process.
0May 3, 2006 at 4:37 pm #137180
Eugene JacquescoleyParticipant@Eugene-JacquescoleyInclude @Eugene-Jacquescoley in your post and this person will
be notified via email.A.J.,
Are you familiar with the “Balacing Loop” or “Reinforcing Loop” approaches. E0May 3, 2006 at 4:46 pm #137183No, i’m not. I’m all ears.
0May 3, 2006 at 5:01 pm #137184
Dr. Eugene JacquescoleyParticipant@Dr.-Eugene-JacquescoleyInclude @Dr.-Eugene-Jacquescoley in your post and this person will
be notified via email.A.J.,As you may be aware, Root Cause Analysis (RCA) or what some of us like coin “Systems Thinking” is required when an unwanted situation which consumes resources and tends to happen in a repeated fashion then there is a possibility that it might be beneficial to figure out what is really causing this situation to occur and remove it so the situation does not occur again. This is generally referred to as Root Cause Analysis, finding the real cause of the problem and dealing with it rather than simply continuing to deal with the symptoms.When attempting to find the root cause, consider this. When a certain fix or process fails, that fail structure may comprise of a balancing loop which is intended to achieve a particular result, yet the result is foiled by an insidious reinforcing loop (Harvard University,2000; MIT, 2003). These two loops interact in such a way that the desired result initially produced by the balancing loop is, after some delay, negated by the actions of the reinforcing loop.The internal balancing loop operates in the standard balancing loop fashion. The action that adds to the migration of the current state toward the desired state also influences, after some delay, some unexpected consequences. These unexpected consequences subsequently impede the migration of the current state in the intended direction.What makes this structure so annoying is that the time delay associated with the unexpected consequences may be such that it is most difficult to really see what’s happening. The fact that it is a reinforcing loop means that its impact may initially be small and only grows to be noticed over time. You fix a problem and think things are fine, then days, weeks, or even months later the same problem is back again. And, with the hectic nature of organizations, who can remember what happened months ago (Ballinger, 2000 & 2004).The most effective strategy in this particular scenario is advanced planning.
0May 3, 2006 at 5:06 pm #137185
Dr.Eugene JacquescoleyParticipant@Dr.Eugene-JacquescoleyInclude @Dr.Eugene-Jacquescoley in your post and this person will
be notified via email.A.J., By the way, Sigma XL 4.21 can address any issue that deals with Failure Mode & Effects Analysis (FMEA). Before you incorporate this technology, you must understand the Cause and Effect.E
0May 4, 2006 at 5:23 am #137210
R.M.ParkhiParticipant@R.M.ParkhiInclude @R.M.Parkhi in your post and this person will
be notified via email.Dear Sir,
How to find the root-cause is very well explained in the book ‘ The World Class Quality ‘ authored by Mr. Keki Bhote ( publishers American Management Association ). The book has many case studies.
With regards,
R.M.Parkhi0May 4, 2006 at 11:41 am #137220
KWalkerParticipant@KWalkerInclude @KWalker in your post and this person will
be notified via email.You may also want to look into a Root Cause called TOPS-8D. I believe it was originally developed by Ford, and is also used by GE. I used it as the basis for our process here, and it’s pretty straightforward. One key concept is that after brainstorming, you bound the problem, and try to group ideas so they can be eliminated in bunches, rather than having to develop supporting / refuting evidence for each one individually. Whatever you do, make your process relies on objective evidence, not things like “it’s per standard practice or procedure” that people tend to fall back on to shorten the list quickly, not objectively
0May 4, 2006 at 4:37 pm #137251
Ted NewtonMember@Ted-NewtonInclude @Ted-Newton in your post and this person will
be notified via email.I recently purchased a great little book “The Root Cause Analysis Handbook:A Simplified Approach to Identifying, Correcting and Reporting Workplace Errors” by Max Ammerman from GOAL/QPC (http://www.goalqpc.com). I have not seen any software related to this process but would be interested in learning more about such software if it exists.
0December 20, 2006 at 10:02 pm #149349
Paul RichardsonParticipant@Paul-RichardsonInclude @Paul-Richardson in your post and this person will
be notified via email.Apollo root cause analysis is a pretty good method and has software to go with it.
Paul0December 21, 2006 at 5:44 pm #149399
The ForceMember@The-ForceInclude @The-Force in your post and this person will
be notified via email.You can utilize the Global 8 Disciplines of Problem Solving — it will fit your needed RCA procedure
0December 21, 2006 at 5:52 pm #149400You are responding to posts from May. I would hope that person found an answer and moved on, so should you.
0December 21, 2006 at 6:00 pm #149401The Force wasn’t with him today.
0 -
AuthorPosts
The forum ‘General’ is closed to new topics and replies.