Condition Based Maintenance: when equipment data should trigger maintenance work

Condition based maintenance (CBM) is a maintenance strategy in which service work is triggered by the actual condition of an asset rather than by a fixed calendar. CBM combines condition monitoring data, alert thresholds and defined response procedures so that work is carried out before a functional failure occurs.

In practice, CBM answers one question: does the technical condition of this asset show that action is needed now? When vibration, temperature, oil quality, ultrasound or another parameter crosses a defined threshold, the system raises an alert, an inspection or a work order. That lets a maintenance team cut unnecessary interventions while still reacting earlier than a purely reactive model allows.

What is Condition Based Maintenance?

In CBM, the decision to perform maintenance follows from data about the technical condition of the asset, not from elapsed time or accumulated running hours.

The underlying principle is simple: intervene when the condition of the equipment justifies it. Unlike time-based maintenance, CBM does not assume an automatic replacement or overhaul after a set number of days, operating hours or cycles. The intervention happens when a measurement shows deterioration, an exceeded warning threshold, or an approach to the limit of safe operation.

CBM can draw on data from:

• vibration sensors;
• thermal imaging cameras;
• oil analysis;
• ultrasound testing;
• temperature measurements;
• pressure measurements;
• current and voltage measurements;
• scheduled inspections;
• operator rounds;
• SCADA, DCS or IoT systems;
• a maintenance management system;
• an industrial data platform.

What matters in CBM is not collecting data but connecting data to a decision. Every measurement should lead to a specific response: continued observation, an inspection, parts staging, planned repair, a restriction on how the asset runs, or a revision of the alert threshold.

How does CBM work?

CBM follows a defined sequence: measure condition, establish a baseline, set thresholds, monitor, alert, and act.

A typical process looks like this:

condition measurement → baseline → warning threshold → monitoring → alert → decision → work order → verification of the result

In practice, a CBM process covers several stages:

Stage	What happens	Example
Data collection	A system or a technician measures a condition parameter	Bearing vibration, cabinet temperature, particle count in oil
Baseline definition	The normal operating level of the asset is established	Typical vibration level at a given load
Threshold setting	Warning and critical levels are defined	Alert when vibration rises above the agreed limit
Monitoring	Data is collected periodically or continuously	An online sensor or a route-based handheld measurement
Alert	A threshold is crossed or the trend deteriorates	Notification sent to the maintenance team
Action	The team inspects, repairs or replaces the component	Bearing replaced during a planned shutdown
Validation	The team confirms that condition returned to normal	Vibration drops after the component is replaced

CBM depends on a well-defined alert threshold. The threshold can come from a technical standard, a manufacturer recommendation, historical data, the measured baseline or a statistical analysis. Set it too low and the programme generates false alarms. Set it too high and deterioration is detected too late.

Where CBM sits in the maintenance strategy hierarchy

CBM sits between preventive and predictive maintenance. It is more data-driven than a fixed calendar, but usually simpler than full failure forecasting. In the terminology of EN 13306, CBM formally belongs to preventive maintenance – the spectrum below describes the maturity of the approach, not mutually exclusive categories.

Maintenance strategies can be read as a maturity spectrum:

reactive maintenance → preventive / time-based maintenance → condition based maintenance → predictive maintenance

Strategy	Trigger for action	Character
Reactive maintenance	Failure or a visible fault	Action after the fact
Preventive maintenance	A schedule based on time, usage or cycles	Planned action before failure
Condition based maintenance (CBM)	A condition threshold crossed or condition deteriorating	Action based on current condition
Predictive maintenance (PdM)	Forecast risk of a future failure	Action based on a prediction

CBM does not replace every other strategy. It fits assets whose deterioration can actually be measured. For some components, time-based maintenance, mandatory statutory inspections, run-to-failure or a design change that removes the root cause will remain the better answer.

The P-F curve: the action window in CBM

The P-F curve describes how an asset deteriorates from the first detectable symptom of a potential failure through to functional failure – the loss of the required function.

Point P marks the potential failure: the earliest moment at which deterioration can be detected with the chosen monitoring technique. Point F marks the functional failure: the moment at which the asset can no longer deliver its required function.

The span between point P and point F is the P-F interval. That interval is the window in which CBM should trigger action.

point P → detectable deterioration → CBM action window → point F → loss of function

For example:

Element of the P-F curve	Meaning
Point P	The first detectable symptom of deterioration
P-F interval	The time available to respond before functional failure
Point F	Loss of the asset’s required function
Warning threshold	The level at which the team should plan an intervention
Critical threshold	The level at which a fast response is required

The monitoring technique chosen determines how long that action window is. Oil analysis can reveal gearbox deterioration earlier than a temperature rise. Vibration analysis can identify a bearing problem earlier than a visual inspection. Thermography can find an overheating electrical connection before any damage occurs.

Where the P-F interval is long, periodic route-based measurement with a handheld instrument may be sufficient. Where it is short, continuous online monitoring and a fast, pre-agreed response procedure are usually necessary.

CBM versus time-based maintenance

Time-based maintenance (TBM) works to a fixed interval of calendar time or running hours. CBM acts when the data shows that the condition of the equipment has deteriorated.

Dimension	Condition based maintenance (CBM)	Time-based maintenance (TBM)
Trigger	Condition data crosses a threshold or shows deterioration	A fixed interval of time, operating hours or cycles
Data required	Condition monitoring, sensors, measurements, trend analysis	A calendar, an hour counter, a schedule
Timing of the intervention	When the technical condition justifies it	Regardless of the current technical condition
Risk of over-maintenance	Lower, because the work follows the condition	Higher, because components may be replaced too early
Risk of reacting too late	Low, provided monitoring covers the relevant failure mode	Possible, if the interval is set too long
Cost profile	Higher up-front cost, lower risk of unnecessary work	Lower up-front cost, potentially higher running cost
Failure types addressed	Those with detectable symptoms of deterioration	Including those whose condition cannot be monitored
Skills required	Data interpretation, thresholds, diagnostics	Standard planning and execution of work
Best fit	Critical, high-cost assets with measurable deterioration	Simple assets, mandatory inspections, failures without reliable precursors

CBM helps avoid replacing parts that are still in good condition. That does not make TBM redundant. Some work still has to happen on a fixed cycle for legal, safety, warranty, hygiene, calibration or process-availability reasons.

CBM versus predictive maintenance

CBM and predictive maintenance both use asset condition data, but they answer different questions. CBM asks: is the condition already bad? PdM asks: when will the condition become bad?

CBM is normally built on thresholds, trends and current condition. Predictive maintenance (PdM) adds a layer of analytics – historical models, machine learning or time-series forecasting – to estimate when a failure will occur or how much useful life remains.

Dimension	CBM	PdM
Trigger	Current condition crosses a threshold or shows deterioration	Forecast future condition based on a trend or a model
Core question	Is the condition already unacceptable?	When will the condition become unacceptable?
Analytics	Thresholds, trends, alerts, diagnostic interpretation	ML models, regression, Weibull analysis, time-series forecasting
Lead time	From threshold breach to functional failure	From forecast to predicted failure, often longer
Data required	Condition data, baselines, thresholds	Condition data, failure history, operating context, historical records
Complexity	Moderate	High
Infrastructure	Sensors, measurements, alerts, CMMS	Sensors, data platform, analytics engine, models
Relationship	The foundation for, or the stage before, PdM	An extension of CBM with forecasting

In everyday use the terms CBM and PdM are often treated as interchangeable. The technical distinction is worth keeping: CBM triggers work once deterioration has been detected, while PdM attempts to predict a future failure or the optimal moment to intervene.

Condition monitoring techniques used in CBM

CBM relies on condition monitoring techniques that detect deterioration before a functional failure occurs.

The most widely used techniques are vibration analysis, thermography, oil analysis and ultrasonic testing. The choice should follow from the failure mode, the type of equipment and the length of the P-F interval.

Vibration analysis

Vibration analysis is one of the core CBM techniques for rotating machinery.

It is applied to pumps, motors, fans, gearboxes, compressors, turbines and bearings. Vibration measurement can reveal imbalance, misalignment, mechanical looseness, bearing damage, gear defects or resonance.

Typical measurements include:

• vibration velocity;
• acceleration;
• displacement;
• frequency spectrum;
• signal envelope;
• trend over time;
• comparison against the baseline.

In a CBM programme, vibration analysis can trigger an inspection or a work order when the vibration level crosses the warning threshold or when the trend indicates progressive deterioration.

Thermography

Thermography uses infrared imaging to detect overheating, uneven temperature distribution and thermal anomalies.

It is typically applied to:

• electrical cabinets;
• cable connections;
• bearings;
• motors;
• heat exchangers;
• insulation;
• steam systems;
• HVAC installations.

In CBM, thermography can identify a hot spot, an overload, a loose connection, a cooling problem, insulation deterioration or increased friction. The threshold is usually expressed as a temperature difference against a reference point or against an inspection standard.

Oil analysis

Oil analysis assesses both the condition of the lubricant and the condition of the system it lubricates.

It can cover:

• viscosity;
• water content;
• particle count;
• contaminants;
• wear metals;
• oxidation;
• additive depletion;
• acidity;
• cleanliness expressed in ISO codes.

Oil analysis is particularly valuable for gearboxes, hydraulic systems, turbines, compressors and engines. In CBM it can trigger an oil change, filtration, a gear-tooth inspection, a seal check or a diagnostic search for the source of contamination.

Ultrasonic testing

Ultrasonic testing detects high-frequency signals associated with friction, turbulence, leaks, electrical discharge or early-stage bearing damage.

It is used for:

• compressed-air leaks;
• steam traps;
• valves;
• bearings;
• vacuum systems;
• electrical switchgear;
• corona discharge;
• sealing problems.

In CBM, ultrasound is useful where symptoms are not yet visible in temperature or vibration data, or where a leak has to be located quickly.

Examples of condition based maintenance

A usable CBM example always names four things: the asset, the monitoring technique, the response threshold and the maintenance action.

Example	Sector	Monitoring technique	CBM trigger	Action
Pump bearing replacement	Manufacturing	Vibration analysis	Vibration level crosses the agreed warning threshold, e.g. 4.5 mm/s for the relevant machine class	Bearing replacement planned for the next scheduled shutdown
Electrical cabinet inspection	Facility management / manufacturing	Thermography	A hot spot more than 20 °C warmer than the reference point	Connections checked and retightened, faulty device replaced
Gearbox oil change	Mining / heavy industry	Oil analysis	Particle count or wear metals rise above the agreed limit	Oil change, filtration, gear-tooth inspection
Steam trap replacement	Process industry	Ultrasonic testing	Ultrasound signal indicates blow-through or a trap stuck open	Trap replaced and the avoided energy loss quantified
Motor diagnostics	Discrete manufacturing	Motor current signature analysis	Change in the current spectrum or rising asymmetry against the baseline	Motor inspection, check of drive and load conditions
Compressor monitoring	Process industry	Vibration, temperature, pressure	Simultaneous rise in bearing vibration and temperature	Planned intervention ahead of functional failure

Thresholds have to be set for the specific asset, machine class, operating conditions, applicable standards, manufacturer guidance and measurement history. For rotating machinery, the reference point for vibration evaluation zones is the ISO 20816 series (which supersedes ISO 10816). The same vibration level can mean one thing on a small auxiliary pump and something quite different on a critical process compressor.

How to implement CBM step by step

A CBM rollout should start from asset criticality and failure modes, not from the choice of sensors.

Step	Description	Key activities
1	Assess asset criticality	Rank assets by safety exposure, production impact, cost of failure and availability of redundancy
2	Identify failure modes	Review failure history, run an FMEA, interview maintenance and production staff
3	Select monitoring techniques	Match vibration, thermography, oil, ultrasound or other techniques to the failure mode
4	Deploy sensors or instruments	Online sensors for critical assets, route-based measurement for the rest
5	Establish baselines	Collect data under normal operating conditions, accounting for load and speed
6	Set thresholds	Define warning and critical levels from standards, manufacturer guidance, history or statistics
7	Integrate with the maintenance process	Link each alert to a work order, a named owner and a defined response procedure
8	Train the team	Data interpretation, tool handling, escalation rules, threshold adjustment
9	Improve continuously	Review false alarms, update thresholds, extend coverage and measure the results

CBM should never run as a standalone alerting system with no owner. Every alert needs a process behind it: who reviews it, how quickly they respond, how they classify the risk, what work order they raise and how they confirm the action worked.

The data CBM requires

CBM needs condition data, operating context, baselines, thresholds, failure history and reliable measurement quality.

Data type	Why it matters
Condition data	Vibration, temperature, oil, ultrasound, pressure, current, process parameters
Operating context	Load, speed, ambient temperature, operating mode, production shift
Baseline data	The reference point for normal operation of the asset
Threshold data	Warning and critical levels
Failure history	Evidence of which symptoms actually preceded past failures
Work order history	What was done, and what effect it had
Spare parts data	Availability of the parts needed to respond to an alert
Data quality	Fixed measurement points, calibration, correct sensor mounting

Condition data has to be read together with operating context. A rise in vibration under higher load means something different from the same rise at constant load. Equipment temperature depends partly on ambient temperature. Pressure and flow shift with the process mode.

An industrial data platform can consolidate data from sensors, production systems, the CMMS, quality and energy. Analytics then help surface trends, deviations and anomalies, and the relationships between asset condition and production context.

The benefits of CBM

CBM reduces unnecessary maintenance work while still catching deterioration earlier than a reactive model would.

The main benefits:

Benefit	Mechanism
Fewer unplanned stoppages	Deterioration is detected before functional failure
Longer component life	Parts are replaced when their condition justifies it
Lower cost of unnecessary work	Fewer overhauls performed only because a date has passed
Better spare parts management	Parts can be ordered when the data signals a coming need
Improved safety	Early detection of overheating, cracking, leaks or degradation
Better use of resources	The team works on assets that genuinely need attention
Decisions grounded in data	Priorities follow measurement, not only the schedule
Higher asset availability	Less time in unnecessary service and fewer functional failures

CBM can improve availability as a component of OEE (Overall Equipment Effectiveness). It can also extend MTBF (Mean Time Between Failures) and shorten MTTR (Mean Time To Repair), because more work is planned and less of it is done under breakdown conditions.

CBM often exposes energy losses as a side effect – compressed-air leaks, failed steam traps, overheating electrical connections or equipment running in a degraded state.

The limitations of CBM

CBM is not the right strategy for every asset or every failure mode. It works best where deterioration is measurable before the function is lost.

Typical limitations:

Limitation	What it means
Up-front cost	Sensors, instruments, data infrastructure and threshold configuration all have to be funded
Not every failure is detectable	Some failures are sudden and have no measurable precursor
Skills requirement	Interpreting the data requires trained people
False alarms	Over-sensitive thresholds lead to alarm fatigue
Thresholds set too high	Over-permissive thresholds delay the response
Data requirements	Stable acquisition, transmission and measurement history are essential
Coverage gaps	CBM does not replace statutory inspections or all time-based work
Organisational change	The team has to move from following a schedule to deciding on condition

CBM should be deployed selectively. Where a failure has no detectable symptom, the P-F interval is very short and the cost of failure is low, a simpler strategy is usually sufficient. Where the asset is critical and deterioration is measurable, CBM can become a core part of the maintenance programme.

CBM and the seven types of maintenance

CBM is one maintenance strategy among several. In the broader taxonomy it sits alongside reactive, preventive and predictive maintenance, RCM, TPM and proactive maintenance.

Type of maintenance	Characteristics
Reactive maintenance	Repair after a failure has occurred
Preventive maintenance	Work performed to a schedule or usage interval
Condition based maintenance (CBM)	Work triggered by condition data
Predictive maintenance (PdM)	Work planned on a forecast of a future failure
Reliability-Centered Maintenance (RCM)	A method for selecting the right strategy per failure mode
Total Productive Maintenance (TPM)	An organisational approach that engages operators and the wider business
Proactive maintenance	Eliminating root causes, often through a design or process change

RCM can identify CBM as the appropriate strategy for a specific failure mode, provided the deterioration is detectable and acting on condition is justified both technically and commercially.

ISO 17359 and the related standards

ISO 17359, Condition monitoring and diagnostics of machines – General guidelines, sets out the general principles for building a condition monitoring programme.

In a CBM context, the standard brings structure to:

• asset selection;
• selection of monitoring techniques;
• definition of measurement procedures;
• establishing baselines;
• setting thresholds;
• conducting diagnostics;
• documenting results;
• improving the programme.

Related standards include ISO 13373 for vibration condition monitoring and diagnostics, ISO 13379-1 for data interpretation and diagnostic techniques, and ISO 13381-1 for prognostics and remaining useful life estimation.

Standards do not replace engineering judgement. What they do is keep a condition monitoring programme consistent, repeatable and auditable.

Integrating CBM with a CMMS, data and analytics

CBM only works when condition measurement is connected to the maintenance process. An alert should lead to a decision, and that decision to a work order or another defined action.

A CMMS (Computerized Maintenance Management System) handles work orders, schedules, repair history, spare parts and job statuses. In a CBM programme it can receive alerts, raise work orders, assign ownership and document the response.

A typical data flow:

sensors and inspections → data platform → threshold rules / analytics → alert → CMMS → work order → execution → condition validation

Integration with a data platform makes it possible to combine condition data with production, quality, energy, alarms and work order history. Analytics then support threshold tuning, trend assessment, alarm classification and evaluation of whether the interventions actually worked.

Smart RDM can act as the layer that links asset condition data with production, energy, quality and maintenance data. Framed that way, CBM stops being a separate alarm system and becomes part of a wider operational process: from detecting deterioration through to the decision, the action and the confirmation of the result.

The tooling and vendor landscape in 2026

The CBM market spans EAM and CMMS systems, vibration monitoring solutions, diagnostic tools, condition monitoring services, and data and analytics platforms. The table below is intended as a neutral overview, not a ranking.

Vendor or source	Scope	Typical context
IBM Maximo	Enterprise asset management platform with support for condition monitoring data and CBM processes	Multi-site and enterprise organisations
ReliablePlant	Industry knowledge source covering maintenance strategy, CBM and good practice	Education, methodology, practical material
Metrix, Bently Nevada	Vibration monitoring and machinery protection systems for rotating equipment	Heavy industry, power generation, critical machines
MaintainX	Mobile CMMS supporting work orders, reporting and condition-triggered processes	Maintenance teams and frontline operations
AdvancedTech	Condition monitoring solutions and services, plus CBM implementation support	Diagnostics, consulting, condition monitoring
Smart RDM	Industrial data and operational analytics platform integrating condition monitoring data with maintenance processes	Plants that need CBM tied to production, energy, quality and operational decisions

Not every tool plays the same role. A CMMS runs the work order process, a condition monitoring system supplies the measurements, a data platform integrates the sources, and analytics help interpret trends and set priorities.

The most common mistakes in a CBM rollout

The single most common mistake is installing sensors before defining failure modes, thresholds and the response process.

Typical problems:

• selecting assets without assessing criticality;
• monitoring parameters unrelated to the real failure modes;
• no baseline for normal operation;
• alert thresholds set too low;
• alert thresholds set too high;
• no threshold revision once data has accumulated;
• alerts not linked to work orders;
• no ownership of alarm interpretation;
• too many alerts to handle;
• no measurement of whether CBM is working;
• ignoring load and operating-mode context;
• treating CBM as a full replacement for preventive maintenance;
• no training for technicians and analysts.

A good CBM rollout starts with three questions: which failures do we want to detect, how early can we detect them, and what will we do once we have? Sensors, platforms and dashboards come after that, not before.

How to measure whether CBM is working

Measure CBM by its effect on availability, failures, cost, response quality and the stability of the maintenance process itself.

Example KPIs:

KPI	What it shows
Failures detected before functional failure	Whether CBM genuinely catches deterioration in advance
Share of alerts leading to a confirmed fault	The quality of the thresholds and the accuracy of the diagnostics
Number of false alarms	Exposure to alarm fatigue
MTBF	Whether assets run longer between failures
MTTR	Whether planned interventions shorten repair times
Asset availability	Whether less time is lost to downtime
Spare parts cost	Whether replacement is better matched to condition
Share of planned work	Whether less work is done in breakdown mode
Time from alert to action	Whether the organisation responds inside the P-F interval
Number of avoided stoppages	Whether alerts translate into an operational result

These KPIs have to be read together. Alert volume on its own proves nothing. The value of CBM appears when alerts are accurate, actionable, and lead to work completed before functional failure.

FAQ

What is condition based maintenance?

Condition based maintenance is a maintenance strategy in which service work is carried out when data about the equipment shows deteriorating condition or an approaching failure.

CBM does not run on the calendar alone. It uses condition monitoring, alert thresholds, trends and defined response procedures.

What does CBM mean in maintenance?

CBM stands for condition based maintenance.

The acronym describes an approach in which the technical condition of the asset determines when to intervene. If a parameter crosses a threshold or a trend shows deterioration, the maintenance team acts.

How does CBM differ from time-based maintenance?

Time-based maintenance runs to a fixed schedule – every 30 days, or every 500 operating hours, for example. CBM acts when condition data shows that an intervention is needed.

Put simply: TBM asks whether the due date has passed, while CBM asks whether the condition of the equipment justifies the work.

How does CBM differ from predictive maintenance?

CBM triggers work when the current condition crosses a threshold or shows deterioration. Predictive maintenance uses data and models to forecast when a failure will occur or what the future condition will be.

CBM can be treated as the foundation for, or the stage before, PdM. Both rely on condition monitoring, but PdM adds a forecasting layer.

What is the P-F curve?

The P-F curve describes asset deterioration from point P – the first detectable symptom of a potential failure – through to point F, the functional failure.

The P-F interval is the time in which the organisation can respond. CBM works inside that window: it detects deteriorating condition and triggers action before the function is lost.

Which techniques does CBM use?

CBM uses condition monitoring techniques such as vibration analysis, thermography, oil analysis, ultrasonic testing, motor current signature analysis, and temperature, pressure and other diagnostic measurements.

The choice depends on the asset type and the failure mode. Bearings, gearboxes and electrical switchgear each call for different data.

What is an example of CBM?

A typical example is vibration monitoring on a pump. When the vibration level crosses the agreed warning threshold, the system raises an alert and the team plans an inspection or a bearing replacement for the next shutdown.

The action follows the actual deterioration of the equipment, not a date in the calendar.

How do you implement CBM?

A CBM rollout covers asset criticality assessment, failure mode identification, selection of monitoring techniques, installation of sensors or instruments, baseline establishment, threshold setting, CMMS integration, team training and continuous improvement.

The decisive step is linking each alert to a specific maintenance action.

What data does CBM need?

CBM needs asset condition data, operating context, baselines, warning and critical thresholds, failure history, work order history, spare parts data and information on measurement quality.

Data should be collected repeatably, from the same measurement points and under comparable operating conditions.

What are the benefits of CBM?

The benefits include fewer unplanned stoppages, fewer unnecessary overhauls, longer component life, better spare parts management, improved safety, better use of resources and decisions grounded in data.

CBM can also improve asset availability, MTBF and MTTR, provided alerts lead to effective work completed before functional failure.

What are the limitations of CBM?

CBM requires investment in measurement, data and skills. Not every failure has a detectable symptom, and badly set thresholds produce either false alarms or a response that comes too late.

CBM does not replace every other strategy. Some work still has to be done on a time basis, for regulatory reasons, or reactively.

What are the seven types of maintenance?

The seven types are usually listed as reactive, preventive, condition based, predictive, reliability-centered, total productive and proactive maintenance.

CBM sits in that spectrum between preventive and predictive maintenance. It uses condition data but does not always require full predictive modelling.

Does CBM require online sensors?

Not always. CBM can be built on online sensors or on periodic measurements taken with handheld instruments.

Continuous monitoring is the better choice for critical assets with a short P-F interval. For less critical assets with a longer P-F interval, periodic measurement is often sufficient.

Does CBM improve OEE?

CBM can improve availability – one of the three components of OEE – by reducing unplanned downtime and allowing interventions to be planned.

It does not replace a full OEE analysis. Its effect is concentrated on asset availability and the stability of equipment operation.

Is CBM part of RCM?

Yes. CBM can be one of the strategies selected within an RCM analysis.

RCM examines functions, failure modes and consequences, then selects the appropriate maintenance task. Where deterioration is detectable and acting on condition is justified, RCM can point to CBM as the right approach.

Sources

1. ISO 17359 – Condition monitoring and diagnostics of machines: general guidelines.
2. ISO 13373 – Vibration condition monitoring and diagnostics of machines.
3. ISO 13379-1 – Data interpretation and diagnostics techniques: general guidelines.
4. ISO 13381-1 – Prognostics and remaining useful life estimation: general guidelines.
5. ISO 20816 – Measurement and evaluation of machine vibration (supersedes ISO 10816).
6. EN 13306 – Maintenance terminology.
7. ISO 18434-1 and ISO 18434-2 – Condition monitoring and diagnostics of machines: thermography (general procedures, and image interpretation and diagnostics).
8. ISO 29821 – Condition monitoring and diagnostics of machines: ultrasound – general guidelines, procedures and validation.
9. ISO 14830-1 – Tribology-based monitoring and diagnostics: general requirements and guidelines (analysis of lubricating oils, hydraulic fluids and greases).
10. ISO 13372 – Condition monitoring and diagnostics of machines: vocabulary.
11. Smart RDM internal material on industrial data, asset monitoring, thresholds, alerts and operational analytics (own source, not peer reviewed).