Condition-based maintenance (CBM) is a strategy that monitors the actual condition of an asset to decide what maintenance needs to be done. CBM dictates that maintenance should only be performed when specific indicators show decreasing performance or upcoming failure. Checking a machine for these indicators may include non-invasive measurements, visual inspection, performance data, and scheduled tests. Condition data can then be gathered at specific intervals or continuously (as is done when a machine has internal sensors). Condition-based maintenance can be applied to mission-critical and non-mission-critical assets.
Condition-based maintenance aims to monitor and spot upcoming equipment failure so maintenance can be proactively scheduled when needed–and not before. Asset conditions need to trigger maintenance within a long enough time before failure, so work can be finished before the asset fails or performance falls below the optimal level.
For condition-based maintenance to succeed, several other elements of your maintenance operation need to be in place. That includes having a scheduled maintenance strategy that allows you to inspect and spot anomalies in equipment and trigger timely follow-up work orders. If you want to take the next step and predict which work orders will lead to asset failure, check out what AI-powered work order reports (opens in new tab) can do for you. It’s also essential to have the right parts and supplies on hand when problems in performance are identified, and work is created. Read more about forecasting your parts using historical data and artificial intelligence (opens in new tab).
A condition-based maintenance (CBM) workflow outlines the steps to manage CBM activities. It provides a structured approach to effectively monitor equipment conditions, analyze data, and perform maintenance actions based on the equipment's health. Here's an example of a typical workflow for condition-based maintenance for Fiix:
As shown in the example above, Asset A has a series of sensors and tags connected to it. The data from these sensors and tags get aggregated and streamed to an API and the cloud (in this case, a CMMS). At that point, an AI sets up a training period to understand the baselines of the asset. Generally, the training takes some time, and this step takes about one week with Fiix's CMMS. From here, the AI predicts risks and then displays the them on a dashboard for the asset and, lastly, creates a maintenance task and work order for the asset if required.
Condition-based maintenance (CBM) and predictive maintenance (PdM) share some similarities but are used in different ways and for different purposes. Below is a table that illustrates some of the differences:
Condition-based maintenance (CBM)
Predictive maintenance (PdM)
Use case
CBM involves monitoring the current condition of equipment or systems using various sensors, measurements, and data collection techniques. Maintenance actions are then scheduled based on the observed condition or predetermined thresholds.
PdM uses advanced data analysis techniques and predictive models to estimate when maintenance should be performed. It combines real-time and/or historical data with algorithms to predict equipment failure or performance degradation.
Data utilization
CBM relies on real-time or periodic measurements and observations of the equipment's health and performance parameters. This data is used to make decisions about maintenance actions.
PdM utilizes historical and real-time data, including sensor data, maintenance records, and other relevant information. Advanced analytics and machine learning algorithms are applied to this data to predict future failures or performance issues.
Maintenance triggers
Specific condition indicators or thresholds typically trigger maintenance actions in CBM. For example, maintenance might be scheduled when a certain vibration level is reached, or a particular parameter falls outside a predefined range.
Maintenance actions are triggered based on predictions or estimates of future equipment failure or performance degradation. Algorithms analyze data patterns and identify trends that indicate the need for maintenance.
Time and cost efficiency
CBM aims to optimize maintenance efforts by performing maintenance activities only when a problem is clearly indicated. This can reduce unnecessary maintenance and associated costs.
PdM aims to minimize unplanned downtime by predicting equipment failures in advance. By addressing issues before they lead to failure, PdM can improve overall uptime and reduce maintenance costs.
In addition to these differences, it's essential to understand that the predictive maintenance workflow in a CMMS is very different from the condition-based workflow.
A predictive maintenance (PdM) workflow typically involves several stages to implement the strategy effectively. Here's an example of a typical workflow for predictive-based maintenance for Fiix:
As shown in the example above, Asset B has a series of sensors and tags connected to it. The sensor and tag data then gets linked to thresholds that the maintenance manager (or other maintenance personnel) defines. From here, if the meter for a specific sensor or tag is over (or under) the set threshold, the information is sent through the API into the cloud (in this case, a CMMS). When this data is sent into the CMMS, a trigger may (or may not) occur based on the data. If the trigger indicates an issue with Asset B, a maintenance task is created, and a work order is assigned to fix the problem.
Motor vehicles come with a manufacturer-recommended interval for oil replacements. These intervals are based on manufacturers’ analysis, years of performance data, and experience. However, this interval is based on an average or best guess rather than the actual condition of the oil in any specific vehicle. The idea behind condition-based maintenance is to replace the oil only when a replacement is needed and not on a predetermined schedule.
Oil analysis can perform an additional function in the example of industrial equipment. By looking at the type, size, and shape of the metal particulates that are suspended in the oil, the health of the equipment it is lubricating can also be determined.
Learn how Fiix syncs with your systems so you can focus on maintaining your equipment (opens in new tab)
Vibration analysis
Infrared
Ultrasonic
Acoustic
Oil analysis
Electrical
Operational performance
There are various types of condition-based monitoring techniques. Here are a few common examples:
Two different methods can collect data:
Critical systems that require considerable upfront capital investment or could affect the quality of the product produced need up-to-the-minute data collection. More expensive systems have built-in intelligence to self-monitor in real time. For example, sensors throughout an aircraft monitor numerous systems in flight and on the ground to help identify issues before they become life-threatening. Typically, CBM is not used for non-critical systems, and spot readings will suffice.
Discover how Fiix OT integrations optimizes' your assets based on real-time data (opens in new tab)
Creating a condition-based maintenance (CBM) program involves several key steps. Here's a general framework to guide you through the process:
Use this information to refine and improve the CBM program over time, adjusting the monitoring techniques, thresholds, or maintenance strategies as needed.
There may be some challenges to effectively running a condition-based maintenance program, and they are important to understand in order to overcome:
Discover how to combine data and storytelling to get your maintenance project approved (opens in new tab)
Join the Fiixer community to get insight from experts into CBM (opens in new tab)
When carried out correctly, condition-based maintenance is a minimally disruptive form of maintenance that lessens overhead costs, risk to workers, and downtime due to unexpected breakdowns. Maintenance managers should be aware, however, that setting up a CBM program can be costly, and the changes required to set up the strategy could be met with resistance or confusion. At the end of the day, this strategy requires a great deal of expertise to analyze the data and condition information presented.
Leverage the cloud to work together, better in the new connected age of maintenance and asset management.