IED (Intelligent Electronic Device)

What an IED Is

An intelligent electronic device is a microprocessor-based controller that monitors, protects, and controls power system equipment. The term covers a range of devices: protective relays that detect faults and trip breakers, automation controllers that execute sequencing logic, generator controllers that manage load sharing and synchronization, and power quality meters that track system health.

What distinguishes an IED from a simple relay or meter is programmability. Each device runs firmware that can be configured with custom protection settings, logic equations, communication mappings, and automation sequences. A single feeder protection relay might contain overcurrent elements, reclosing logic, GOOSE publish/subscribe configuration, and Modbus register maps — all of which require engineering configuration specific to its role in the system.

Why Multi-Vendor IED Programming Matters

A typical Tier III/IV data center protection system uses IEDs from multiple manufacturers. Protective relays come from one vendor (often SEL or ABB), generator controllers from another (Woodward or CAT), metering from a third (Electro Industries or Eaton), and automation controllers that tie everything together. Each manufacturer uses its own programming environment, configuration file format, and communication stack.

The coordination challenge is not programming any single device — it is programming all of them to work together. Protection settings on the feeder relays must coordinate with generator protection settings. Automation sequences in the RTAC must match the generator controller’s load-sharing parameters. GOOSE messaging between relays requires matched publish/subscribe datasets across devices from different vendors.

When a prime contractor hires one subcontractor per vendor platform, the seams between vendors become coordination gaps. Each sub programs their devices correctly in isolation, but nobody owns the integration between platforms. These gaps surface during commissioning as failed functional tests, unexpected protection trips, and schedule-consuming troubleshooting.

What IED Programming Involves

IED programming for a data center protection system includes:

Protection settings — time-current coordination curves, pickup values, time delays, and zone-selective interlocking configuration. These settings derive from the protection coordination study and must be validated as a coordinated system, not device by device.

Communication configuration — IEC 61850 GOOSE datasets, Modbus register maps, DNP3 point lists, and SNMP trap definitions. Each IED’s communication configuration determines what data it shares, with whom, and at what priority.

Automation logic — sequencing for generator start/stop, bus transfer, load shedding, and fault recovery. Logic runs in automation controllers (like the SEL RTAC) but depends on inputs from protection relays and generator controllers across the system.

Configuration management — every IED has a settings file that must be version-controlled, documented, and reproducible. A protection system with 100+ IEDs generates hundreds of configuration files across multiple vendor-specific formats.

Multi-Vendor IED Scope?

One Team Across Every Platform

We program across eight manufacturer platforms within a single coordinated P&C scope — no seams between vendors.

Book a Scoping Call See Our Services

The Scale in Data Center Systems

A single Tier III/IV data center complex can require well over 100 IEDs across its protection, control, metering, and automation systems. The device count scales with the number of protection zones, generator sets, distribution buses, and automatic transfer switches in the facility.

Programming these devices individually is labor. Programming them as a coordinated system is engineering. The difference shows up at commissioning: individually correct devices that do not coordinate produce functional test failures, and those failures appear in the final weeks before energization when schedule pressure is highest.

Related reading: Multi-Vendor Relay Integration covers the cross-platform coordination methodology. Our technical approach explains the distributed control architecture that coordinates IEDs across vendor boundaries.