Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

May 19, 2020 | Ken Reed

Equipment Troubleshooting – Don’t Forget Root Cause Analysis

I’ve read through many different troubleshooting philosophies and general methods when it comes to equipment troubleshooting.  Depending on the type of equipment (electronic equipment, rotating machinery, etc.), there can be different ways of narrowing down and then fixing those failures.  For example, in electronic troubleshooting, you can use either linear or half-split methods to arrive at the actual failed component.

Here is an example: How (and why!) you should troubleshoot large construction equipment.

Equipment troubleshooting should also include human performance root cause analysis.

One thing that IS common to many of these methods is that, although they may list “root cause analysis” in their troubleshooting methodology, very few actually dig down to understand the human interaction with the equipment.  I’ve found that very few pieces of gear actually just break.  If a motor quickly fails when being used properly, it probably is not a very good motor, and that manufacturer would not stay in business very long.  Equipment that fails almost always does so because a human has done something to it:

  • Installed it wrong
  • Operated it outside its design limits
  • Shut is down wrong
  • Did the wrong maintenance on it
  • Bought the wrong equipment
  • Aligned it improperly
  • etc.

Your corrective action should not simply say, “Replace the failed bearing.”  It needs to look at how the human negatively affected the performance of that bearing, and then correct that issue.  When doing a root cause analysis, it is critical to look at these human interactions and interfaces to ensure that we find, understand, and correct the actual human performance issues that lead to failure.  The combination of the Equifactor® equipment troubleshooting module with the rest of the TapRooT® System digs down to these issues and puts effective corrective actions in place.

How can you get started?

Improve equipment troubleshooting at your facility today! Buy the book or attend an upcoming course.

 

Categories
Equipment Reliability / Equifactor®, Root Cause Analysis
-->
Show Comments

Leave a Reply

Your email address will not be published. Required fields are marked *