Root Cause + Thinking = The Best Way to Solve Problems

Root Cause + Thinking = The Best Way to Solve Problems

Torbjorn Idhammar President, IDCON INC


Root Cause Confusion?

There is a lot of confusion between diagram, tools, software and company names for?root cause. This newsletter will help you understand that it’s not the about tools you decide to use but rather how you engage your team in thinking about problems at your plant, mine or mill.?

When clients ask us for a?reliability and maintenance assessment, one aspect we review is their process for eliminating problems. We ask an open ended question “How do you eliminate problems in the plant/mill/mine?” and we’ll get answers like “We use Apollo”, “We use 5 why”, “we use Prologic”, “we use histograms”…you get the picture. They are talking about the tools they use not the process they follow.

The tool you use doesn’t matter, it’s the process.

There’s nothing wrong with using a tool to help you document, but sometimes we think because we use this amazing tool, it’s the process but it really isn’t.

The #1 most important part of the root cause process...

The heart of solving problems is the thinking process. Then, you need to have a problem solving method. IDCON developed a method called?Root Cause Problem Elimination it’s follows the basic steps of Root Cause Failure Analysis with a key difference…you aren’t just documenting the problem you are implementing the solution. And you are getting much deeper into why problems happen. Here’s a great article about the?3 main causes that create problems at plants. Very simply put they are:

  • Technical
  • Human
  • Process?

What we find is that one may lead to the other. Here’s an example of how these three are connected. The example is that production was stopped due to a failed component.

The 3 layers of root causes. Technical, Human factor and Work Process

?

Watch the video for more information!


The next step in your problem-solving process...

Then you need to decide on the documentation method or tool. IDCON cautions against using Fishbone…if you want to know why, here’s an article where Tor discusses IDCON's thoughts about?Fishbone diagrams.


Fishbone diagram used for root cause failure analysis (RCFA). It’s not as effective as a cause-and-effect map.


8-Step Root Cause Problem Elimination Process

When you are developing your process for solving your most pressing problems be it equipment, process or production there are 8 steps that you should follow. When we provide training or consulting to clients in the RCPE process we go into detail of each of these steps.??Get trained in Root Cause Problem Elimination.

  1. Determine your triggers
  2. Collect the data- physical evidence; What, where, when, changes in time, similar object
  3. Write a problem statement
  4. Determine the possible causes. Use tools like a How-Can diagram, etc Then collect more data on the possible causes to eliminate causes
  5. Select most likely cause
  6. Determine solutions to the most likely cause
  7. Select solution
  8. Eliminate the problem


UPCOMING TRAINING - It's not too late to sign up!

CLICK TO REGISTER

Managing Maintenance Workshop - NEXT WEEK!

September 10-11, 2024??????????? 8AM-4PM

Embassy Suites @ PDX

7900 NE 82nd Ave

Portland, OR 97220

$1,495/person; includes course materials, lunch, and breaks

Can't attend in person? Join us remotely using Zoom. Zoom participants receive a $100 credit.

REGISTER HERE

Calvin Cox Jr.

Sr Reliability Engineer, CWI

1 个月

Highly recommend RCPE process for RCFAs.

要查看或添加评论,请登录

社区洞察

其他会员也浏览了