Maybe this is a use of Equifactor(R) that you’ve never thought of before…
You have been assigned to a team that has been tasked with installing a new air compressor that will be used as part of a new manufacturing process. Your specific job is to determine what preventive and predictive maintenance activities you will require for the new compressor. Where do you get this type of information?
You can start with the manufacturer’s recommendations, but we all know this is a pretty coarse set of guidelines. Wouldn’t it be nice if you knew how the compressor could possibly fail before it was installed? You could then design your PM and PdM requirements to look for these failure pathways.
As a TapRooT(R) user, you remember that Equifactor(R) is normally used to troubleshoot specific equipment failures and aid in your root cause analysis. But what if we use Equifactor(R) to list ALL POSSIBLE equipment faults, and then design our monitoring systems to look for these faults? In fact, you decide you can use Equifactor(R) to:
1. Determine what vibration monitoring is required to look for the listed symptoms
2. List what preventive maintenance may be required to prevent the failures from occurring
3. Update the operating procedures to keep the equipment operating conditions away from common failure modes
4. Design an operator training program to teach your people to look for specific incipient failure conditions
5. Include the gear in your company’s lube oil analysis program
6. Conduct an RCM analysis to see what maintenance is really required, based on known Equifactor(R) failure modes
and you are just getting warmed up!
It is tough to set up your CBM system to try to minimize your maintenance workload if you don’t know what maintenance is required in the first place. Take a look at how you would normally set up these types of programs for new equipment, and see how Equifactor(R) can be used as yet one more tool to make your life easier.