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.

January 29, 2024 | Justin Clark

Equipment Troubleshooting Strategy

equipment troubleshooting stsrategy

So you want to prove how this machine failed?

equipment troubleshooting strategy

What is your equipment troubleshooting strategy? You’re going to lose evidence if you don’t gather your data in a logical sequence. Think disassembling a 24-cylinder emergency diesel engine only to discover you need to inspect piston rings 12 and 19 which are in that unlabeled pile over there. Would have been nice to know the information we needed BEFORE tearing it apart, cleaning all the software, and losing installation and configuration.

After you’ve narrowed down what you need to prove using the Equifactor® tools, you need a plan.

When you’re proving the exact failure mode and failure agent a machine experienced, you’ll be tracking a lot of steps and many different procedures, tests, and checks. Here’s a troubleshooting sequence planning spreadsheet for download.

This table is designed to be used to prepare for troubleshooting from an Equifactor® table, but anyone can use this method to ensure nothing gets missed or lost.

For every

list every associated

equipment troubleshooting strategy

remaining after your initial narrow-down.

The most common cause of equipment failure? Sloppy maintenance or troubleshooting! Remember the shut-down procedures, test points, installation checks, and tuning, and startup maintenance you’ll need to remember. Don’t create new problems by failing to plan!

Improve your Equipment Troubleshooting Strategy

To learn how to use the troubleshooting sequence and the rest of the Equifactor® troubleshooting process, register for the Equifactor® Pre-Summit Course and the Maintenance and Reliability Best Practice Learning Track at the TapRooT® Global Summit on Root Cause Analysis!

Categories
Equipment Reliability / Equifactor®
-->
Show Comments

Leave a Reply

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