What Is an IED (Intelligent Electronic Device)?

Back to Blog

What Sits Inside the Box

IED is a deliberately broad term for the microprocessor-based devices that replaced electromechanical relays and hardwired panels. A protection relay that trips a breaker on a fault, a bay controller that handles switching and interlocking, a merging unit that digitizes instrument-transformer signals, a power-quality meter - all are IEDs. What they share is embedded intelligence: they measure, decide, act, log, and communicate rather than simply passing a signal through.

Compared with a general-purpose RTU or PLC, an IED is usually purpose-built for a substation function and ships with that function's logic already engineered. A distance relay knows about impedance zones; a bay controller knows about switching sequences and interlocks. This specialization is why a substation is described as a collection of IEDs rather than a set of generic controllers.

How an IED Hosts the IEC 61850 Model

IEC 61850 gives every IED a standardized way to expose what it does. The physical IED hosts one or more logical devices, each grouping logical nodes that model individual functions. A client browses this model to read data, enable reports, and issue control, all over MMS. The IED's capabilities are described in an SCL file, so integration works from a machine-readable model rather than device-specific manuals.

Because the model is standardized, IEDs from different vendors interoperate on the same network - a breaker's XCBR node looks the same regardless of who built the relay. This interoperability, built on a common model hosted by every IED, is the whole promise of the IEC 61850 standard and the reason substation automation moved to it.

Specifying an IED for a Bay

An IED specification starts with the protection and control functions the bay needs, usually written as ANSI device numbers: overcurrent (50/51), distance (21), differential (87), breaker failure (50BF), reclosing (79), and so on. From there the hardware must match the bay: the number and type of CT and VT inputs, binary inputs for breaker and disconnector status, output contacts for trip and close duty, and the auxiliary supply available in the panel. Every one of those counts is site-specific and comes from the bay's single-line and wiring design, not from a default.

The communication side of the specification matters as much as protection. Define which IEC 61850 edition the device must support, which communication services (reporting, GOOSE publication and subscription, time sync), how many Ethernet ports it needs and whether network redundancy such as PRP or HSR (IEC 62439-3) is required by the station design. Ask for evidence of conformance testing rather than a datasheet checkbox, and confirm the vendor supplies a proper ICD capability file - integration effort depends heavily on the quality of that file.

Commissioning: From SCL File to Live Bay

IEC 61850 commissioning is file-driven. The vendor's ICD describes what the IED can do; the system integrator combines the ICDs into an SCD describing the whole substation - datasets, report control blocks, GOOSE links, addressing; and the per-device configuration extracted from that flows back into each relay. The various SCL files are therefore not documentation of the engineering - they are the engineering, and version-controlling them is as important as version-controlling relay settings.

On site, commissioning follows a consistent sequence: confirm each IED's network addressing and its place on the station bus and process bus, establish time synchronization (SNTP, or PTP per IEEE 1588 where high-precision timestamping is required) and verify every device agrees on time, then verify data flow layer by layer - point-to-point signal checks from primary equipment to IED, then reports up to the station level, then any GOOSE exchanges between IEDs. Timestamp agreement deserves particular attention, because event records from multiple IEDs are only useful in a disturbance investigation if their clocks were actually aligned.

Testing Without Tripping the Plant

Testing a device whose job is to trip breakers requires deliberate isolation. Edition 2 of IEC 61850 formalizes this with the Mod/Beh test states and the simulation flag: an IED placed in test mode marks its outputs accordingly, and subscribers can be set to accept simulated GOOSE messages instead of live ones, so a function can be exercised end to end without operating primary plant. Secondary injection - driving the IED's CT and VT inputs from a test set - remains the standard way to prove protection logic, pickup levels, and timing against the setting file.

The hazards are real: a trip contact left connected during injection, a test switch not restored, or a simulated message still accepted after testing are all classic causes of unwanted operations. This is work for qualified protection personnel under the site's isolation and permit procedures, with a restoration checklist that returns every test switch, mode setting, and simulation flag to its normal state and verifies it. The IED's own event log is a useful final check - it records mode changes and operations, so reviewing it after testing confirms the device left the test session in the state the paperwork says it did.

Getting IED Data Beyond the Substation

IEDs generate far more information than protection trips: measurements, breaker wear counters, event records, and self-supervision status. Getting that data to operations usually involves a substation gateway or data concentrator that reads the IEDs over MMS reporting and republishes a selected subset to the wider SCADA or telemetry system over a WAN-friendly protocol such as DNP3 or IEC 60870-5-104. The engineering decision is what to forward: operational measurements and statuses for the control room, plus the health and supervision points that tell maintenance an IED, a communications link, or a battery system needs attention.

The self-supervision data deserves more respect than it usually gets. A modern IED continuously monitors its own hardware, its communications, and often the trip-circuit continuity; a watchdog or supervision alarm from a relay is an early warning that a protection function may not operate when called upon. Forwarding those points to the operations platform, trending them, and alarming on them turns the IED fleet into its own condition-monitoring system - which is exactly the kind of intelligence that separates an IED from the electromechanical device it replaced.

Frequently Asked Questions