Selecting Transformer Accessories for Remote Condition Monitoring

Transformer remote condition monitoring should begin with the operational decision an owner needs to make, not with a catalogue of sensors. Choose accessories after defining the transformer construction, the condition or state to observe, the user of the data, the interface to the control system, and the action that follows an alarm.

A useful scope may combine measured trends with existing device contacts, but neither automatically diagnoses a fault or changes a protection scheme. The approved transformer drawings, OEM instructions, protection and control drawings, site automation architecture, and responsible engineering authority establish the final arrangement.

Part 1. What decision should transformer remote condition monitoring support?

Start by naming the decision the remote information must support. It may be an operator’s need to recognize an abnormal state, a maintenance team’s need to compare condition evidence over time, or an asset planner’s need to prioritize a review. Those uses need different data, timing, ownership, and escalation arrangements.

IEEE C57.143 frames online monitoring around identifying relevant parameters, sensor application, risk/benefit, and monitoring-system application. It does not provide a universal interpretation rule, so a project should document what each selected point is expected to show and what evidence is needed before action.

The CIGRE transformer-monitoring model breaks the asset into functional subsystems, possible failures, measurable indicators, and data inputs. That sequence helps avoid buying a device simply because it is available in a catalogue.

Part 2. Which accessory type fits the signal and action path?

Remote monitoring commonly combines continuous measurements and discrete states. A temperature sensor may provide a changing value for trending, while an existing gauge, relay, or switch may offer an alarm contact that changes state at a configured condition. They should be specified as different kinds of evidence.

Treat an alarm contact as separate from a trip command, and do not use a gateway as a substitute for an approved protection path. The project’s protection and control drawings decide whether a contact is annunciated, recorded, used in an interlock, or connected to another protective function.

For a temperature trend, request the measurement that can preserve the required context instead of only a common alarm contact. Conversely, retaining an existing alarm indication does not mean a new analogue channel has the same operational meaning.

Important: Keep monitoring and protection responsibilities separately documented. The CIGRE monitoring framework treats data preparation, interpretation, and action as linked stages, while the approved protection scheme remains the authority for protective action; source context: CIGRE transformer monitoring guide summary.

Part 3. How should temperature monitoring be defined before selecting a device?

Before selecting a temperature accessory, define the context that must remain with the evidence. A top-oil measurement, a winding-temperature indication or model, ambient temperature, load, and cooling state can answer different questions. The RFQ should identify the intended thermal evidence rather than treating every temperature accessory as interchangeable.

IEC 60076-7 describes loading and thermal-ageing guidance using load, cooling-medium temperature, and time-varying operation. That does not mean a generic alarm value can be copied into every project; it means the conditions used to interpret a thermal point must be specified.

Part 4. When are oil level, pressure, and gas signals relevant?

Oil level, pressure, and gas-related accessories belong to the actual liquid, preservation, and protective arrangement. They are not a universal remote-monitoring bundle. Confirm whether the offered transformer has the relevant tank, conservator or sealed arrangement, pressure devices, sampling/monitoring provisions, and approved maintenance plan.

CIGRE’s maintenance guide includes oil preservation systems, gauges, indicators, protection relays, and sensing devices in transformer maintenance. The monitoring guide also treats oil containment and preservation as a distinct subsystem. Use those categories to ask what is physically fitted and what a remote point can legitimately represent.

For broader liquid-document context, see JUBANG’s transformer oil-testing evidence. Keep the tank, bushing, OLTC, and any other liquid compartment clearly identified; a result or contact from one boundary should not be assumed to represent another.

Part 5. What should be monitored around OLTC and cooling equipment?

OLTC and cooling equipment deserve separate scope because they are separate subsystems with their own fitted mechanisms, controls, maintenance records, and failure modes. A transformer without an OLTC does not need an OLTC point list, and a cooling arrangement without remotely usable status points cannot be represented honestly as a complete remote-condition system.

The CIGRE maintenance material includes both on-load and de-energized tap changers, cooling systems, and sensing/monitoring devices. A buyer should therefore request the actual equipment arrangement before choosing which states or measurements enter the remote point schedule.

The related JUBANG OLTC selection and maintenance context helps distinguish tap-changing duty from a monitoring request. It does not establish an OLTC-monitoring configuration for a particular transformer.

Part 6. What must the SCADA and cybersecurity interface specify?

The remote interface should be selected from the owner’s automation architecture, not from a device label alone. Define the point list, units, timestamps, quality flags, event treatment, protocol, gateway boundary, network ownership, remote-access method, and loss-of-communications behavior before selecting a controller or communications accessory.

IEC 61850 describes standardized data models, engineering language, and communication services for utility automation. A project may use that framework or another owner-approved interface, but interoperability still depends on the agreed point model and engineering responsibility.

IEC 62351 describes security technologies for power-system communications, including role-based access, key management, and security-event logging. The ISA/IEC 62443 framework adds a risk-based industrial-control-system perspective. Neither reference removes the need for the owner’s project-specific security architecture.

Part 7. Who owns the data, alarms, and response process?

Remote condition monitoring succeeds only when raw points become assigned work. CIGRE describes data preparation, interpretation, and recommendations or action as linked stages. The buyer should name who validates data quality, who sees the alarm, who can request a site inspection, and who can authorize any operational or maintenance decision.

False alarms and bad data need a documented path too. A sensor issue, lost communications, incorrect point mapping, changed equipment configuration, or unusual but valid operating condition can all create a signal that needs validation. Suppressing, resetting, or reclassifying an alarm without ownership can remove useful evidence or create a hidden risk.

Part 8. What should an RFQ include, and when is JUBANG a fit?

An RFQ should allow the supplier and owner to evaluate the monitoring scope against the actual transformer, accessories, and automation system. A request for “remote monitoring” without construction, signals, interfaces, and response ownership leaves the most important decisions undefined.

RFQ input checklist

• Transformer identification, construction, duty, criticality, approved drawings, and accessory schedule.
• Monitoring objectives, named users, decisions to be supported, and required response timeframe.
• Existing instruments, relay contacts, protection devices, local panels, and control drawings.
• Requested temperature evidence: oil, winding indication or model where applicable, load, ambient, and cooling context.
• Oil-level, pressure, preservation, gas, and leakage categories only where the construction and maintenance plan make them applicable.
• OLTC type and fitted states, plus cooling fan, pump, cabinet, and control status where fitted.
• Point list with each signal’s source, unit or state, normal state, timestamp, quality indication, event history, receiving system, and action owner.
• Sensor versus alarm-contact treatment, including approved protection and control boundaries.
• SCADA, gateway, protocol, network, remote-access, data-retention, and export requirements.
• Cybersecurity zones, roles, authentication, key management, logging, patching, incident ownership, and change control.
• Alarm matrix, validation steps, false-alarm procedure, escalation path, service boundaries, tests, documentation, spares, and acceptance authority.

JUBANG may be a relevant contact when a buyer is defining a 6–10 kV oil-immersed power transformer scope or a 35 kV oil-immersed transformer package alongside its project documents. The transformer and accessory schedules then need to coordinate with the defined monitoring objective.

Send the scoped information through an OEM/ODM transformer consultation after reviewing the related installation and pre-energization guide where installation responsibilities affect the available points and wiring boundary.

Fit boundary

This article does not establish that JUBANG supplies a monitoring device, configures SCADA, provides cybersecurity services, interprets an alarm, approves a protection action, diagnoses a transformer, or accepts a monitoring system. It is not a substitute for transformer drawings, OEM manuals, approved protection and control drawings, the owner’s automation and cybersecurity architecture, or the responsible engineering decision.

FAQ

What is transformer remote condition monitoring?

Transformer remote condition monitoring collects selected measurements and states so defined users can review condition or operating evidence away from the transformer. The useful scope begins with the decision, data user, and response path; a dashboard alone does not diagnose a fault or authorize action.

Should every transformer have the same monitoring accessories?

No. The appropriate scope depends on construction, criticality, operating duty, existing instruments, maintenance plan, automation architecture, and the decision the data must support. Select categories only after confirming the transformer and subsystem boundaries.

What is the difference between a sensor and an alarm contact?

A sensor normally supplies a measured value for trending or contextual review. An alarm contact normally reports a discrete configured state from a fitted instrument or relay. The approved protection and control drawings determine what either signal means and what action, if any, follows.

Which temperature inputs matter for remote condition monitoring?

The required inputs depend on the monitoring objective. Top-oil temperature, a winding indication or model where applicable, load, ambient conditions, and cooling state may need to be considered together. Specify the intended evidence and interpretation process rather than relying on one value.

Are oil level, pressure, and gas monitors needed on every transformer?

No. They are relevant only where the transformer construction, existing accessories, liquid arrangement, and maintenance plan support them. Confirm the applicable compartment, device function, data path, and response boundary before adding a point.

Does an OLTC need separate monitoring?

An OLTC can require its own scope because it is a separate subsystem with its own drive, contacts, maintenance records, and possible liquid boundary. Confirm that an OLTC is fitted, identify the actual type and available points, then define the operational use for each requested signal.

What cooling-system information should reach SCADA?

Request only states or measurements that are physically fitted and useful to the owner, such as project-defined fan or pump status, control mode, failure contact, or temperature context. Keep the motor-control and protection interfaces under their approved drawings.

Can transformer monitoring data go to SCADA?

Yes, when the point list, data model, protocol, gateway boundary, timestamps, quality handling, network path, and ownership are defined for the owner’s system. The communications design should also state what happens if the remote connection is lost.

How should remote-monitoring cybersecurity be specified?

Specify the owner’s risk-based architecture: network zones and conduits, authorized roles, authentication, key management, remote-access approval, logging, patching, incident ownership, and configuration control. IEC 62351 and ISA/IEC 62443 provide useful security frameworks, but project requirements determine the implementation.

Who responds when a transformer monitoring alarm appears?

The owner should assign a recipient, acknowledgement process, data-quality validation step, escalation route, record, and closure authority. A remote alarm should prompt the defined review process; it is not by itself an instruction to trip, repair, or replace equipment.

References

1. Monitoring application scope: IEEE C57.143-2024
2. Transformer maintenance and monitored subsystems: CIGRE TB 445 Guide for Transformer Maintenance
3. Monitoring objectives, data, and alarm response: CIGRE Guide on Transformer Intelligent Condition Monitoring Systems
4. Thermal and loading context: IEC 60076-7 overview
5. Utility-automation interoperability: IEC 61850 overview
6. Power-system communications security: IEC 62351 cybersecurity overview
7. Industrial-control-system security: ISA/IEC 62443 series