Back to research

Condition-Based vs Time-Based Maintenance for Transformer APM

How utilities can move from calendar-driven transformer maintenance to condition-based, evidence-led APM workflows using agentic AI, human review, and standards-aware diagnostics.

Condition-based maintenanceTime-based maintenanceTransformer APMUtility maintenanceAgentic AI APMPower transformer sustainabilityIEEE C57.152CIGRE TB 962
Utility transformer maintenance team comparing diagnostic trends and maintenance schedules beside a power transformer substation

Transformer maintenance has historically relied on a blend of fixed intervals, field experience, diagnostic testing, and emergency response. Time-based maintenance is still useful. It creates discipline, protects minimum inspection cycles, and supports safety routines. But for critical transformer fleets, calendar maintenance alone is not enough.

Condition-based maintenance changes the operating question from “what is due this month?” to “which transformer evidence says a decision is needed now?” That shift is especially important for utilities, TSOs, DSOs, renewable operators, industrial plants, and oil and gas facilities that manage high-value power transformers with different ages, duty cycles, loading histories, and consequence profiles.

GridAPM Ai is designed around this shift: using agentic AI to turn diagnostic evidence into human-reviewed APM decisions that maintenance teams can trust.

Why time-based maintenance still matters

Time-based maintenance gives transformer teams a baseline operating rhythm. It can define inspection intervals, oil sampling schedules, periodic testing, cooling-system checks, bushing inspections, and safety routines. It is also useful when data quality is low or when an organization is building its first structured transformer maintenance program.

The limitation is that transformer risk does not follow the calendar. A lightly loaded transformer with stable oil results may not need the same intensity of review as a similar unit showing gas generation acceleration, changing moisture behavior, cooling constraints, or repeat maintenance findings. Conversely, a transformer that is not “due” for inspection may need engineering review because its condition changed.

CIGRE maintenance guidance, including TB 962 and the earlier TB 445, frames transformer maintenance as a reliability, availability, and condition-management discipline rather than a simple calendar exercise.

What condition-based maintenance adds

Condition-based maintenance uses evidence to decide what should be inspected, tested, monitored, repaired, refurbished, or escalated. For power transformers, that evidence can include:

  • Dissolved gas analysis and gas generation rates.
  • Oil quality and moisture context.
  • Partial discharge and PRPD evidence.
  • SFRA, winding resistance, turns ratio, insulation resistance, and power factor results.
  • Thermal loading, hot-spot estimates, ambient conditions, and cooling state.
  • Bushing, tap changer, protection, and auxiliary system records.
  • Inspection photos, field notes, and prior work orders.
  • Asset criticality, network consequence, spare availability, and outage windows.

IEEE C57.152 is a strong source anchor because it describes diagnostic field tests for fluid-filled transformers and emphasizes that results from multiple tests should be interpreted together. IEEE C57.104 and IEC 60422 support the oil and DGA evidence layer that many transformer teams already use.

A practical CBM operating model

GridAPM workflow

From calendar maintenance to evidence-led APM

Condition-based maintenance works best when it does not erase time-based discipline. It adds evidence triggers, risk context, and human-reviewed work packages.

1 Calendar baseline

Keep required inspection, sampling, safety, and compliance intervals as the minimum operating rhythm.

2 Condition trigger

Detect DGA acceleration, oil quality movement, thermal stress, PD activity, SFRA change, or repeat field findings.

3 Agentic evidence pack

AI agents assemble provenance, trend context, asset history, missing data, and likely maintenance paths.

4 Engineer-approved action

Maintenance teams approve monitoring, additional testing, work orders, outage planning, or lifecycle review.

Human-in-the-loop: GridAPM does not treat a condition trigger as an automatic work order. The output is a reviewable maintenance case for engineering approval.

Where agentic AI fits

Agentic AI is useful when the task is bounded and auditable. In a transformer CBM workflow, an agent should not autonomously dispatch crews or change equipment settings. It should perform structured work that engineers would otherwise do manually:

  • Retrieve the latest and historical transformer records.
  • Identify which diagnostic streams changed.
  • Compare DGA and oil evidence against relevant context.
  • Find missing test conditions, stale records, or contradictory evidence.
  • Draft a maintenance case with confidence notes.
  • Prepare an EAM or CMMS work-package draft after approval.

That is why GridAPM treats AI as workflow intelligence, not black-box autonomy.

Why this matters for sustainability and climate

Condition-based maintenance is also a sustainability strategy. When teams can distinguish between “continue monitoring,” “treat oil,” “repair cooling,” “perform additional testing,” “plan refurbishment,” and “evaluate replacement,” they can avoid purely reactive decisions. Extending useful transformer life, reducing emergency work, and making replacement decisions with better lifecycle context all support sustainable APM.

ISO 55000:2024 is relevant because transformer teams are not only maintaining equipment. They are managing asset value over life cycles. CIGRE TB 858 is also important because health indices should support focused maintenance, refurbishment, and replacement outcomes rather than exist as isolated scores.

A strong pilot question

The best first pilot question is narrow:

Which transformer maintenance decisions are slow today because evidence is scattered across reports, spreadsheets, test exports, and work-order history?

That question usually reveals the best GridAPM pilot scope. It may be DGA trend review, oil quality and moisture, PRPD triage, SFRA change management, health-index transparency, or work-order preparation. The outcome is not “AI replaces maintenance planning.” The outcome is a repeatable way to move from condition evidence to engineer-approved maintenance decisions.

Request a GridAPM pilot to evaluate a condition-based maintenance workflow for your transformer fleet.

Sources and standards referenced

Frequently asked questions

Should transformer teams replace time-based maintenance with condition-based maintenance?

Not entirely. A practical transformer APM program usually keeps safety, compliance, and inspection intervals while using condition evidence to prioritize additional testing, investigation, and maintenance actions.

How does agentic AI help condition-based maintenance?

Agentic AI can assemble transformer evidence, compare trends, identify missing context, draft a maintenance case, and route recommendations to engineers for review before any work package is approved.

What evidence supports condition-based transformer maintenance?

Useful evidence includes DGA trends, oil quality, partial discharge, SFRA, thermal loading, bushing records, inspection findings, work orders, criticality, and known site constraints.

Share your fleet profile and diagnostic workflow.

GridAPM will propose a focused evaluation path for agentic AI, health index, lifecycle context, and sustainable maintenance planning.