How to Set Up a Condition-Based Maintenance Program With VIE
Condition-based maintenance is not a new idea. It is a decades-old operational concept that most transformer fleets have never been able to implement at scale because the continuous monitoring data required to support condition-based decisions did not exist. Time-based schedules persisted not because they were optimal, but because they were the best available tool given what could be measured.
VIE produces continuous data for every monitored transformer. That changes what is operationally possible. This article explains how to build a condition-based maintenance program around it.
Step 1: Let the Baseline Establish Itself
The first month of VIE monitoring is the baseline period. Do not configure alert thresholds during this window. The analytics engine is learning the relationship between each transformer's operating conditions and its vibration signature. Setting thresholds before that relationship is established produces alerts that reflect normal operating variation rather than genuine anomalies.
During the baseline period, review the incoming data in myVIE to familiarize yourself with what each unit's normal pattern looks like. Different transformers produce different baseline values even when both are healthy. A unit operating at higher average load will show different absolute metric values than a lightly loaded unit at the same facility. Both can be healthy. The diagnostic value is in each unit's trend relative to its own baseline, not in comparison to the other.
VIE's application engineers review the initial data with the customer's team after the first health report. That review is the right moment to discuss what the baselines are showing and how to set appropriate alert thresholds for the specific fleet.
Step 2: Configure a Three-Tier Alert Protocol
Once baselines are established, configure alert thresholds that sort the fleet into three response tiers:
Green (stable): Metrics are within their normal baseline range and not trending toward a threshold. No action required. Continue monitoring.
Yellow (watch): One or more metrics are trending toward a threshold or have crossed a watch-level threshold. The recommended response is to schedule a confirmatory test within 90 days. The specific test depends on which metric is trending — winding health metrics call for a MEGGER test, oil health metrics call for an oil lab test, and so on. See [When VIE Flags a Problem: What to Do Next] for the full action map by metric type.
Red (expedite): A metric has crossed a flagged threshold, or a coincident indicator (Impact Metric or Thermal Metric) is elevated. The recommended response is to expedite inspection or confirmatory testing. Do not defer to the next scheduled review cycle.
These tiers are not binary switches. A transformer can move from green to yellow and back to green if the trending metric stabilizes. A metric that crosses yellow and then continues rising moves to red. The protocol is continuous, not event-driven.
Step 3: Assign Response Ownership
A condition-based maintenance program only works if someone is accountable for acting on each tier. Define who reviews myVIE alerts and what their authority is to schedule tests or escalate to inspection.
For most organizations, a practical structure is:
- Daily or weekly: A reliability engineer or asset manager reviews the fleet overview in myVIE. Yellow and red items are noted.
- Within five business days of a yellow flag: The responsible engineer schedules the appropriate confirmatory test.
- Within 24 to 48 hours of a red flag: The responsible engineer escalates for expedited inspection scheduling.
This does not require a dedicated monitoring team. It requires that someone has the dashboard in their daily workflow and the authority to initiate a test order without a lengthy approval chain.
Step 4: Link Field Observations to the Asset Record
Condition-based maintenance improves over time as the team builds familiarity with each unit's behavior. That familiarity is only durable if it is captured in the platform rather than held in individual technicians' heads.
When a field visit produces a relevant observation — a cooling fin was blocked and cleaned, a through-fault occurred on the network, an oil sample was taken and sent to the lab — record it as a note on the asset in myVIE. When lab results come back, enter the findings alongside the metric trend that prompted the test. When a metric flag is reviewed and the decision is to continue monitoring rather than act, document the rationale.
Over time, the asset record in myVIE becomes an institutional memory of each transformer's condition history. When a technician who knows a unit well retires, that knowledge does not leave with them.
Step 5: Review and Adjust Annually
Condition-based maintenance programs improve with experience. After the first year of operation, review the alert threshold configuration against the actual patterns the fleet has shown. Thresholds that generated yellow flags on every significant load swing may need adjustment. Thresholds that held stable while the metrics were trending toward a fault condition before flagging may need to be more sensitive.
The goal is a threshold configuration that produces actionable alerts — neither so sensitive that the alert volume exceeds the team's capacity to respond, nor so conservative that developing conditions reach red before the yellow flag appears.
VIE's application engineers can support this annual review. They have visibility into the fleet data and can identify patterns that are characteristic of specific failure modes versus normal operating variation.