CMRT
CMRT
CMRT
1. Equipment Inspections
2. Clean Equipment Regularly to Minimize Dirt and Dust.
3. Lubricate Rotating/moving Parts to Prevent Premature Wear.
4. Check Machinery Power to Optimize Energy Efficiency.
5. Repair or Replace Equipment Before It Fails.
There is no “one size fits all” maintenance checklist; rather, the perfect one depends on
what type of equipment or facility you’re using in the first place. Preventive
maintenance checklists can be divided into the following categories.
• Equipment and machines
• Buildings and facilities
• Vehicles and fleets
How to Create a Preventive Maintenance Checklist
Creating your own checklists is a process involving data, best practices, and
tailoring it to the needs of your business. Fortunately, you don’t have to start
from scratch. Here are some tips for developing your own PM checklist:
1. Have a Clear Objective.
2. Audit Your Equipment.
3. Note Any Applicable Standards and Regulations.
4. Select Assets.
5. Outline PM Tasks for Each Asset.
6. Offer Clear Instructions for Checklist Items.
7. Train Your Personnel.
8. Track the Results and Adjust.
A PREVENTIVE MAINTENANCE CHECKLIST
Some of the Benefits of Preventive Maintenance
1. Extended asset Life.
2. AnMaintenance.
Reduce Efficient and Productive Maintenance Activity
3. Boost Productivity.
4. Reduce Unplanned downtime.
PREDICTIVE MAINTENANCE PdM/ CONDITION BASED MAINTENANCE
(CBM)
• Vibration analysis
• Infrared (IR) thermography.
• Acoustic / Ultrasonic — sound level measurements.
• Oil analysis.
• Electrical — amperage plus other data.
• Shock Pulse Method (SPM).
• Partial discharge & Corona detection.
• Operational performance data — pressure, temperature, flowrates, etc.
Vibration Analysis
Vibration monitoring might be considered the “grandfather” of condition/predictive
maintenance, and it provides the foundation for most facilities’ CBM programs.
Vibration usually indicates trouble in the machine. Machine and structures vibrate in
response to one or more pulsating forces that may be due to imbalance, misalignment,
etc. The magnitude of vibration is dependent on the force and properties of the system,
both of which may depend on speed.
Four Fundamental characteristics of Vibration
• (a.) Frequency.
• (b.) Period.
• (c.) Amplitude.
• (d.) Phase.
3 Key measures used to evaluate the magnitude of vibrations are:
• Displacement
• Velocity
• Acceleration.
The three areas are not unrelated. Changes in lubricant condition and
contamination, if not corrected, will lead to machine wear.
Lubricant Condition: Bad lubricating oil is either discarded or reconditioned
through filtering or by replacing additives.
Standard Analytical Test Types Lubricating oil and hydraulic fluid analysis
should proceed from simple, subjective techniques such as visual and odour
examination through more sophisticated techniques. The more sophisticated tests
should be performed when conditions indicate the need for additional information
and based on asset criticality.
1. Visual and Odour
2. Viscosity
3. Water (Moisture) Test
4. Wear Particle Count
5. Total Acid Number (TAN)
6. Total Base Number (TBN)
7. Spectrometric Metals Analysis
8. Infrared Spectroscopy
9. Analytical Ferrography
10. Foaming
11. Rust Prevention
12. Rotating Bomb Oxidation Test (RBOT)
13. Sampling and Frequency
14. Oil Contamination Program
A basic oil contamination control program can be implemented in
three steps:
30
Technologies Limitations
The technologies discussed earlier can be divided into two categories:
• Energized: These technologies can safely provide information on energized systems
and require the system be energized and operational. They include IRT, Ultrasonics,
Motor Current Readings, Starting Current, Motor Current Spectrum Analysis, RF,
Power Factor, and Harmonic Distortion.
31
The following are various NDT techniques.
• Radiography.
• Ultrasonic Testing (Imaging).
• Magnetic Particle Testing (MPT).
• Hydrostatic Testing.
• Eddy Current Testing.
Why Have a PdM (CBM) Program.
Condition Based Maintenance can:
• Warn of most problems in time to minimize unexpected failure, the risk and consequences of
collateral damage, and adverse impact on safety, operations, and the environment. It will
reduce the number of pre-emptive corrective actions.
• Increase equipment utilization and life; minimize disruption to mission and schedule. It will
decrease asset and process downtime, resulting in increased availability.
• Reduce maintenance costs — both parts and labour.
• Reduce a significant amount of calendar / run-based preventive maintenance.
• Minimize cost and hazard to an asset that result from unnecessary overhauls, disassembles,
and PM inspections.
• Increase the likelihood that components operate to optimum lifetime. In some cases,
replacement prior to end-of-life is more efficient for meeting operational requirements and
optimum cost.
• Reduce requirements for emergency spare parts.
• Increase awareness of asset condition.
• Provide vital information for continuous improvement, work, and logistic planning.
• Improve worker safety.
• Increase energy savings
33
However, CBM cannot:
• Eliminate defects and problems, or stop assets from deteriorating.
• Eliminate all preventive maintenance.
• Reliably and effectively warn of fatigue failures.
• Reduce personnel or produce a major decrease in lifetime maintenance costs without a
commitment to eliminating defects and chronic problems.
CBM is not a “silver bullet.” Some potential failures, such as fatigue, or uniform wear on a
blower fan are not easily detected with condition measurements. In other cases, sensors
may not be able to survive in the environment; measurements to assess condition may be
overly difficult and may require major asset modifications.
34
TROUBLESHOOTING AND ANALYSIS
35
FAILURE: Failure is not doing what we say we are going to do. Failure of our
equipment is the equipment not doing what we designed it to do when we
need it. Asset is unable to operate at all, Unable to operate at rate, Unable to
meet quality standards, Unable to meet E, H, & S standards. The only way we
can eliminate or reduce failures is by understanding how equipment fails. We
can then learn and develop ways to predict, prevent, and eliminate failures.
37
HOW IS MAINTENANCE TROUBLESHOOTING USUALLY DONE
Tell me if you’ve heard this story before. An asset breaks down and no one knows why.
You talk to the operator, read some manuals, and check your notes about the asset. You
try a couple of things to get the machine up and working again with no luck. Before
you can try a third or fourth possible solution, you get called away to another
emergency, with the asset still out of commission.
This is often how the process happens when performing maintenance troubleshooting,
especially when a facility relies on paper records or Excel spreadsheets. The process is
based on collecting as much information as possible from as many sources as possible
to identify the most likely cause of the unexpected breakdown. You can never go wrong
when you gather information, but it’s the way that information is gathered that can turn
troubleshooting from a necessity to a nightmare
38
Why does maintenance troubleshooting matter
39
Stacking the Deck
40
Maintenance troubleshooting tips
The following are just a few ways your operation can improve its troubleshooting
techniques to conquer chaos and take control of its maintenance.
b) Create in-depth asset histories: Information is the fuel that powers exceptional
maintenance troubleshooting for maintenance. Knowing how a particular asset
has worked and failed for hundreds of others is a good place to start a repair.
That’s why manuals are a useful tool when implementing troubleshooting
maintenance techniques. However, each asset, facility, and operation is different,
which means asset machine failure doesn’t always follow the script. Detailed
notes on an asset’s history can open up a dead end and lead you to a solution
much more quickly.
41
Failure Codes: provide a consistent method to describe why an asset failed. Failure codes
are built on three actions: Listing all possible problems, all possible causes, and all
possible solutions. This process records key aspects of a failure according to predefined
categories, like misalignment or corrosion.
Failure codes are useful when maintenance troubleshooting because technicians can
immediately see common failure codes, determine the best solution, and implement it
quickly. Failure codes can also be used to uncover a common problem among a group of
assets and determine a long-term solution.
42
d) Build detailed task lists: Exceptional maintenance troubleshooting requires solid planning and
foresight. Clear processes provide a blueprint for technicians so they can quickly identify
problems and implement more effective solutions.
e) Make additional information accessible: We’ve said it before and we’ll say it again; great
maintenance troubleshooting techniques are often the result of great information. However, if that
information is difficult to access, you will lose any advantage it provides. That is why it is crucial
for your operation to not only create a large resource centre, but to also make it highly accessible.
43
Using CMMS software for maintenance troubleshooting
If it sounds like a lot of work to gather, organize, analyze and circulate all the
information needed to be successful at maintenance troubleshooting, you’re not
wrong. Without the proper tools, this process can be a heavy lift for
overwhelmed maintenance teams. Maintenance software is one tool that can
help ease the load every step of the way. A digital platform, such as a CMMS,
takes care of crunching the numbers, organizing data and making it available
wherever and whenever, so you can focus on using that information to make
great decisions and troubleshoot more effectively.
44
MTBF: MTBF calculates the average period between two breakdowns. In other words,
it’s a measure of reliability—how long an asset typically works until it goes caput.
MTBF Formula:
45
For example, let’s say you have 10 identical pumps at your facility. The
pumps operated for 100 hours each over the course of a year, totalling 1,000.
The pumps failed 16 times in total over that year. This means that the mean
time between failures for these pumps is 62.5 hours.
46
How to Improve MTBF
1. Improve PM Process
2. Conduct a RC Analysis
47
MTTF: Mean time to fail (MTTF) measures the average time from when a non-repairable
asset begins operating to when it fails. The key phrase is ‘non-repairable asset.’ MTTF
calculates the entire lifespan of equipment. When it fails, it’s replaced. This is how MTTF
differs from MTBF — the former deals with assets that aren’t repairable and the latter
deals with assets that are repairable. There are a number of reasons an asset might not be
repaired, but the most common rationale is that it costs less and takes less time to replace
the asset.
MTTF is calculated by dividing the number of hours assets have operated by
the total number of assets being tracked.
For example, three identical fans run for a total of 60 hours. The MTTF for
these fans would be calculated by dividing 60 by three for a total of 20 hours.
This calculation can tell you many things—the most valuable being how often
maintenance is required and when to purchase inventory.
48
MTTD: Mean time to defect (MTTD) measures the average time between identifiable
issues that lead to equipment failure. An asset can continue to run after a defect is
discovered. That’s what makes MTTD and MTBF different: MTTD is a prelude to
failure, while MTBF is the state of failure.
Depending on the asset and its failure modes, there are a number of techniques
that can be used to gauge an asset’s condition and delay failure.
1. Lubricant Sampling and Analysis
2. Corrosion Monitoring
3. Motor Current Analysis
4. Acoustic Emissions Detection (e.g., ultrasound)
5. Vibration Measurement and Analysis
6. IR Thermography
7. Process Parameter Trending (e.g., flows, rates, pressures, temperatures, etc.)
8. Process Control Instrumentation (measurement and trending)
9. Visual Inspection (look, listen and feel).
How to use the P-F curve to improve maintenance
A maintenance record is also useful to reference when deciding if you should replace
your assets with updated versions and the best time to replace them. The data recorded
over time unveils patterns of failure, expenditure, and repair. This can be used to make
better decisions that will save on costs and time
Equipment maintenance Log
How to create a great equipment maintenance log
Getting accurate, reliable data from an equipment maintenance log starts with
how you build it. The way you structure your maintenance logs is going to
depend on a variety of factors that are specific to your team and facility, but
any log should keep three key questions in mind:
1. What asset and maintenance information do you need most?
2. How detailed does the information need to be?
3. Who is going to be using this information and how?
Generally, this breaks down into two sections: Information about the asset and
information about maintenance work.
56
How to create a great equipment maintenance log
Best practice is to start with asset information at the top. This can include:
• Equipment name
• Serial number
• Purchase date
• Date in service
57
How to create a great equipment maintenance log
Then describe the work that was done on the equipment:
•
Date of maintenance task
•
Brief description of the task
•
Name of the person who performed the work
•
Date of the next scheduled maintenance
•
Additional observations, notes, or comments
Simplicity is your best friend here. Don’t make it hard for technicians to complete the
log.
It’s best to keep your descriptions short and have all the key details laid out plainly,
58
How to create a great equipment maintenance log
• Above all, make sure you have a process that ensures accuracy. There are three
simple rules that will help you keep the data in your logs are as accurate as
possible:
1. Use a standard template for every asset. Equipment should be tracked and measured
from the same baseline to avoid errors and make data analysis easier.
2. Keep your logs in a designated location. Bonus points for making them available on
a digital plaform for quick access and a lower risk of damaging or losing them.
3. Create a routine for exchanging logs between shift changes. Keep everyone in the
loop on completed or outstanding work, problems, safety risks, and other useful
information.
59
How to maintain maintenance logs
How you maintain a maintenance log depends on if you’re doing it by hand or using
maintenance log software. If you’re manually maintaining maintenance logs like in a
spreadsheet, here are three tips:
1. Create a standardized template for each asset you want to track. Ideally, you want to
try to keep these templates as consistent as possible to streamline your process.
2. Designate a single place to keep the records, so they are easy to find by all
maintenance workers.
3. Define the process for how equipment maintenance logs should be exchanged and
communicated between workers during shift changes.
If you’re using software to create a maintenance schedule, maintenance workers need
to know how the tool works and who they should go to if they have questions. The
best way to maintain logs, in this case, is to create a standard process for entering data
to ensure it is entered consistently and in the same format.
60
Six ways to use the data in equipment maintenance logs
61
How to get data from an equipment maintenance log
Knowing the failure rate for a failure code can help you do the following:
1. Optimize PM intervals
2. Assess the desirability of additional PM tasks.
3. Eliminate unnecessary PM tasks.
4. Improve failure response.
5. Improve work practices.
How many CMMS failure codes should you have?
The whole point of having failure codes is to provide your technicians with an easy
way to quickly analyze and categorize equipment failures, problems and faults. For this
reason, effective and accurate code lists are required to identify trends.
On the one hand, having too few failure codes does not enable the level of data analysis
needed, or it results in meaningless, nonspecific data. On the other hand, if there are too
many options, technicians could suffer from “choice overload”, resulting in a number
of “Miscellaneous” or “Other” codes being assigned, which will again render the data
meaningless. Ideally, you should aim for 20-30 failure codes. Thankfully, pop-up
CMMS tables eliminate the need to memorize codes.
Who should develop failure codes?
Failure codes should, above all else, be easily available and understandable to the people who
request work, to the maintenance personnel that complete the work, and to the engineers who
need to understand what is occurring in the field. For that reason, developing failure codes
requires an integrated approach with these three groups, especially if there is a desire to do some
sort of wide-ranging analysis. Ultimately, the codes have to allow the field personnel a relatively
painless way to provide the information that the engineers need. Unless that occurs, the end
product will not be used.
In general, CMMS failure codes are collected for the purpose of failure modes effects analysis
(FMEA). Analysis, in turn, provides knowledge of patterns in equipment failure with respect to
other external and internal factors. There are endless applications of having knowledge like this,
but in general, it can be used to improve reliability, system availability, and ultimately, the
company’s bottom line.
Example of a failure codes?
Overall equipment effectiveness
What is overall equipment effectiveness:
Overall equipment effectiveness (OEE) is like
a performance review for assets. It measures
how well an asset is doing its job. In a
manufacturing facility, an asset’s job is to
make things, and OEE is a tool for determining
how well an asset makes those things. In doing
so, it tells you a lot about the efficiency of
your manufacturing process and where it can
be improved
The OEE formula
OEE = Availability x Performance x Quality
The most common way to calculate OEE is by multiplying three factors: asset
availability, asset performance, and production quality.
Developed as part of the Toyota Production System and prevalent in Lean methodologies
today, the 5 Whys method involves asking ‘why’ repeatedly to uncover successive layers of
a problem.
• First, you look at a problem and ask why it happened. Once you answer the first
question, you ask why that happened. Repeat this process five times in total and you will
have typically found your true root cause.
• The 5 Whys is one of the simplest root cause analysis tools available, and is useful for
straightforward problems that don’t require advanced statistics. Let’s look at a detailed
example of how to apply this method and what to do with findings to keep the problem
from coming back.
• Problem Statement
• Why 1
• Why 2
• Why 3
• Why 4
• Why 5
Acting on the 5 Whys
With root cause analysis complete, you can both solve the problem today and take steps
to stop it from happening again.
At this point, you might take steps such as:
• Having the process engineer that developed the standard work instructions change
them to reflect the correct servicing of this machine
• Adding the problem to a failure mode and effects analysis (FMEA) or a control
plan to determine if it needs more attention
• Creating an audit question based on the correction to verify the change is in place
and working
Fishbone Diagram
A fishbone diagram sorts possible causes into various categories that branch off from
the original problem. Also called a cause-and-effect or Ishakawa diagram, a fishbone
diagram may have multiple sub-causes branching off of each identified category. When
tasked with solving a problem, brainstorming potential causes is a good place to start.
However, without a way to organize the information visually, it can be hard to see how
different facets of the problem interact. One visual method of root cause analysis that
helps do just that is the fishbone diagram.
This method allows you to visualize and organize potential causes of a problem into a
useable framework for solving it. Here we look at the basics of how a fishbone diagram
works, as well as some examples of how to apply it in your facility.
Ishikawa diagrams/ fish bone diagrams/cause and effect/ fishikawa diagram
Process to Make an Ishikawa Diagram
To make an Ishikawa Diagram, a group will need a white board, flip chart, and some marking pens.
1. Choosing Variables: The first step in creating a scatter plot is choosing your
independent and dependent variables.
2. Measuring Variables and Organizing Data: Now that you have chosen your
variables, it’s time to measure them, either via observing the process or pulling
data from a digital source such as part measurement system, maintenance system
or mobile audit software.
3. Building Your scatter Plot: Once you have your data collected, building the scatter
plot and evaluating correlation is easy in a spreadsheet. In our example, you are looking
at how many work orders happened at each temperature. That means temperature goes
on your x-axis and number of work orders goes on your y-axis.
4. Evaluating the result: In this example, we have a clear pattern. It is obvious that the
data points trend upward. This means that there is a direct correlation between the
temperature of the part and the number of work orders that are cut against the conveyor.
This is solid evidence supporting your hypothesis that the heat of the parts is causing
damage.
FMEA
FMEA is a structured, empirical approach to understanding the potential impact of
something going wrong in a process. Each individual opportunity to go wrong is called
a failure mode. Each failure mode is assessed for three factors: severity (S), occurrence
(O), and detection (D). These scores combine to produce a Risk Priority
Number (RPN), and that score is the ranking system that you use to determine which
problems to focus on first.