Condition-Based Maintenance (CBM) is a predictive maintenance strategy that schedules repair or replacement actions exclusively upon the detection of objective evidence of decreasing physical performance or an incipient failure mode. Unlike time-based preventive maintenance, CBM relies on continuous or periodic monitoring of real-time sensor data—such as vibration, temperature, or dissolved gas levels—to assess the actual condition of an asset, ensuring intervention occurs only when necessary.
Glossary
Condition-Based Maintenance (CBM)

What is Condition-Based Maintenance (CBM)?
A maintenance strategy that uses real-time sensor data and diagnostic indicators to schedule repairs only when evidence of decreasing equipment performance or incipient failure is detected.
The core mechanism involves establishing diagnostic thresholds for specific failure indicators, such as the rate of hydrogen generation in transformer oil. When sensor telemetry breaches these pre-defined limits, a maintenance work order is triggered. This approach maximizes asset Remaining Useful Life (RUL) while minimizing unnecessary invasive inspections, directly reducing operational expenditure and preventing catastrophic failure in critical infrastructure like high-voltage transformers.
Key Characteristics of CBM
Condition-Based Maintenance (CBM) is a predictive strategy that relies on real-time sensor data to trigger maintenance actions only when measurable indicators of impending failure are detected, eliminating unnecessary scheduled interventions.
Real-Time Condition Monitoring
CBM relies on continuous data acquisition from permanently installed sensors or portable diagnostic tools. For transformers, this includes:
- Online DGA monitors measuring hydrogen, acetylene, and ethylene in real time
- Fiber optic temperature sensors embedded in windings for direct hot-spot measurement
- Partial discharge sensors detecting ultrasonic and transient earth voltage signals
- Load tap changer monitors tracking motor current signatures and contact wear The data is streamed via IEC 61850 MMS protocols to centralized SCADA systems, enabling 24/7 visibility into asset health without manual inspections.
Threshold-Based Alerting Logic
CBM systems trigger work orders when diagnostic parameters cross predefined alarm thresholds established by standards like IEC 60599 and IEEE C57.104. Key alerting mechanisms include:
- Absolute gas limits: e.g., hydrogen exceeding 100 ppm signals thermal fault
- Rate-of-change alarms: acetylene increasing >10 ppm/day indicates active arcing
- Gas ratio triggers: Duval Triangle zones flagging D1 or D2 discharge faults
- Temperature differentials: winding hot-spot exceeding 110°C accelerates cellulose aging These thresholds are configured with hysteresis bands to prevent alarm flooding during transient conditions like load surges.
Diagnostic Fault Classification
When sensor data crosses thresholds, CBM employs diagnostic interpretation methods to classify the specific failure mode before dispatching crews. Common techniques include:
- Duval Triangle analysis plotting CH4, C2H4, and C2H2 ratios to distinguish thermal faults from electrical discharges
- Rogers Ratio method using four gas ratios to identify overheating, partial discharge, or arcing
- Key Gas method correlating dominant gas species to fault types (e.g., acetylene = arcing)
- Machine learning classifiers like Random Forest and XGBoost trained on historical DGA failure labels Accurate classification ensures the right repair team and spare parts are mobilized.
Prognostic Remaining Useful Life Estimation
Advanced CBM extends beyond detection to prognostics—forecasting how long an asset can operate before failure. Key methodologies include:
- Weibull distribution modeling of transformer population failure data to estimate hazard rates
- Degree of Polymerization (DP) trending to project when paper insulation reaches end-of-life (DP < 200)
- LSTM neural networks forecasting future dissolved gas trajectories from historical time-series
- Physics-informed neural networks (PINNs) constraining predictions with thermodynamic heat transfer equations RUL estimates enable risk-based maintenance scheduling, allowing operators to defer repairs during peak demand seasons.
Integration with SCADA and Work Management
CBM is not a standalone function—it must integrate with enterprise operational systems to close the loop from detection to action. Integration touchpoints include:
- IEC 61850 MMS mapping of DGA monitor data points to standardized logical nodes for SCADA ingestion
- CMMS (Computerized Maintenance Management System) APIs that auto-generate work orders from threshold violations
- Historian databases like OSIsoft PI storing long-term trend data for forensic analysis
- Mobile workforce apps pushing diagnostic reports and fault classifications to field technicians This integration eliminates manual data transcription and reduces mean time to repair (MTTR).
Edge-Based Anomaly Detection
Modern CBM architectures deploy edge AI inference directly on substation gateways to reduce latency and bandwidth. Edge capabilities include:
- Autoencoder neural networks trained on normal transformer behavior, flagging anomalies via reconstruction error
- Sensor drift compensation algorithms correcting DGA monitor calibration degradation without cloud connectivity
- Local alarm processing that triggers breaker trip signals within milliseconds for critical faults
- Federated learning enabling model improvement across utility fleets without centralizing sensitive operational data Edge processing ensures CBM remains functional during communication outages, critical for remote substations with unreliable connectivity.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about implementing and optimizing condition-based maintenance strategies for critical power infrastructure.
Condition-Based Maintenance (CBM) is a maintenance strategy that uses real-time sensor data and diagnostic indicators to schedule repairs only when evidence of decreasing equipment performance or incipient failure is detected. Unlike time-based preventive maintenance, which replaces components on a fixed calendar schedule regardless of actual condition, CBM relies on measured physical parameters—such as dissolved gas concentrations, thermal profiles, and partial discharge activity—to trigger interventions. The key distinction from predictive maintenance (PdM) lies in temporal scope: CBM operates on current or near-real-time condition thresholds (e.g., acetylene exceeds 5 ppm, triggering an alarm), while predictive maintenance employs time-series forecasting and remaining useful life (RUL) models to project future degradation trajectories and estimate when a failure threshold will be crossed. In practice, CBM forms the foundational data layer upon which predictive algorithms are built, with CBM answering "what is happening now" and PdM answering "what will happen and when."
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
CBM vs. Other Maintenance Strategies
A comparison of Condition-Based Maintenance against traditional time-based and reactive approaches for transformer asset management.
| Feature | Condition-Based Maintenance | Time-Based Maintenance | Reactive Maintenance |
|---|---|---|---|
Trigger for Action | Real-time sensor data and diagnostic indicators | Fixed calendar or operational intervals | Equipment failure or breakdown |
Data Dependency | Continuous DGA, thermal, and electrical monitoring | Historical MTBF statistics | None required |
Unplanned Downtime Reduction | 85-95% | 30-50% | 0% |
Implementation Cost | $15,000-50,000 per transformer | $2,000-5,000 per year | $0 upfront |
Remaining Useful Life Visibility | |||
Catastrophic Failure Prevention | |||
Maintenance Labor Efficiency | 40-60% reduction vs. time-based | Baseline | 3-5x emergency labor premium |
Typical Asset Lifespan Extension | 15-25% | 5-10% | 0% |
Related Terms
Condition-Based Maintenance relies on a constellation of diagnostic, prognostic, and analytical techniques. These related concepts form the technical foundation for detecting incipient faults and estimating remaining useful life in transformer assets.
Dissolved Gas Analysis (DGA)
The primary diagnostic input for transformer CBM. DGA measures fault gases dissolved in insulating oil to identify thermal and electrical faults. Key gases include hydrogen, acetylene, ethylene, and methane. Online DGA monitors provide the continuous data stream that triggers CBM alerts when gas levels or gassing rates exceed thresholds defined in IEC 60599.
Remaining Useful Life (RUL)
The prognostic endpoint of any CBM program. RUL estimates the operational time remaining before a transformer reaches a predefined failure threshold. Calculated using Weibull distribution models or time-series forecasting with LSTMs, RUL transforms raw condition data into actionable maintenance scheduling decisions.
Online DGA Monitor
The hardware backbone of real-time CBM. These permanently installed multi-gas sensors provide continuous dissolved gas readings without manual oil sampling. Modern monitors measure up to 9 fault gases plus moisture. Data is transmitted via IEC 61850 MMS protocols to SCADA systems for centralized alarming and trending.
Digital Twin
A dynamic virtual replica synchronized with real-time sensor data. Digital twins simulate transformer thermal behavior using IEEE C57.91 models to calculate hot-spot temperature and predict insulation aging. They enable CBM programs to run stress-test scenarios without risking the physical asset.
Health Index
A composite scoring methodology that aggregates multiple diagnostic inputs into a single condition ranking. Health indices weight factors including:
- DGA results and gas ratios
- Degree of Polymerization (DP) of paper insulation
- Tan Delta dielectric loss measurements
- Load history and age Utilities use health indices to prioritize maintenance across entire transformer fleets.
Explainable AI (XAI)
Interpretability methods applied to CBM machine learning models. Techniques like SHAP and LIME generate feature attribution scores that explain why a model flagged a specific transformer. This transparency is critical for asset managers who must justify maintenance expenditures based on algorithmic recommendations.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us