An Intelligent Electronic Device (IED) is a microprocessor-based controller for power system equipment, such as a circuit breaker, transformer, or capacitor bank, that executes advanced local protection and control logic. Unlike simple remote terminal units, an IED integrates multiple functions—protection, monitoring, control, and metering—into a single device, processing analog voltage and current inputs to make autonomous trip decisions based on configurable setpoints.
Glossary
Intelligent Electronic Device (IED)

What is an Intelligent Electronic Device (IED)?
A foundational component of modern digital substations, the Intelligent Electronic Device replaces legacy electromechanical relays with a compact, microprocessor-based controller capable of executing complex protection logic and high-speed peer-to-peer communication.
IEDs communicate horizontally with other devices using high-speed, deterministic protocols like IEC 61850 GOOSE (Generic Object Oriented Substation Event), enabling peer-to-peer messaging for functions such as breaker failure protection and busbar blocking schemes. This networked architecture replaces hardwired copper connections with virtual logic, significantly reducing wiring complexity while providing rich operational data to the Supervisory Control and Data Acquisition (SCADA) system.
Core Characteristics of IEDs
Intelligent Electronic Devices are the autonomous, microprocessor-based building blocks of the modern digital substation, defined by their ability to execute local logic and communicate in real-time.
Microprocessor-Based Local Intelligence
An IED is fundamentally a digital computer integrated into a power system apparatus. Unlike electromechanical relays, it uses a microprocessor to execute complex protection and control algorithms. This enables advanced functions like time-overcurrent curve shaping, directional element logic, and reclosing sequences that are impossible with analog components. The firmware can be updated to adapt to changing grid codes without hardware replacement.
High-Speed Peer-to-Peer Communication
IEDs communicate horizontally using protocols like IEC 61850 GOOSE (Generic Object Oriented Substation Event). This replaces traditional copper wiring for interlocking and tripping signals with multicast Ethernet frames. A single IED can publish a trip signal to multiple subscribers simultaneously, enabling distributed busbar protection and breaker failure initiation in under 3 milliseconds, dramatically reducing wiring complexity and enabling virtualized protection schemes.
Analog Signal Acquisition & Conditioning
IEDs interface directly with instrument transformers, digitizing high-current and high-voltage waveforms via Analog-to-Digital Converters (ADCs). They sample at rates of 80–256 samples per cycle to accurately capture harmonic content and transient phenomena. Internal anti-aliasing filters and digital signal processors (DSPs) extract phasor magnitudes, symmetrical components, and frequency in real-time, forming the basis for all metering and protection calculations.
IEC 61850 Data Modeling & Interoperability
IEDs self-describe their capabilities using the IEC 61850 data model, which structures functions into Logical Nodes (LNs) like XCBR (circuit breaker) or PDIS (distance protection). This semantic standardization allows an IED from one vendor to be seamlessly integrated into a system engineered by another. The Substation Configuration Language (SCL) files define the entire system topology and data flow, enabling automated engineering and validation.
Disturbance Recording & Sequence of Events
Every IED functions as a high-resolution fault recorder. It captures pre-trigger and post-trigger waveform data (in COMTRADE format) and timestamps all binary state changes with 1-millisecond accuracy using an IEEE 1588 (PTP) or IRIG-B time source. This creates a forensic-grade Sequence of Events (SOE) log, allowing protection engineers to reconstruct grid disturbances with absolute temporal precision for post-mortem analysis.
Cybersecurity & Role-Based Access Control
Modern IEDs are network-connected cyber assets requiring robust security. They implement IEC 62351 standards, enforcing role-based access control (RBAC) for all engineering and operational commands. Features include TLS-encrypted communication, Syslog event reporting to SIEM systems, and secure firmware signing to prevent unauthorized code execution. Physical security is augmented by sealable access ports and tamper-detection alarms.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about microprocessor-based controllers in modern substation automation.
An Intelligent Electronic Device (IED) is a microprocessor-based controller that performs protection, control, monitoring, and communication functions for power system equipment. Unlike simple electromechanical relays, an IED digitizes analog voltage and current inputs through internal analog-to-digital converters (ADCs), applies digital signal processing algorithms to compute phasor quantities, and executes programmable logic to make trip or control decisions. The device continuously samples waveforms at high rates—typically 64 to 256 samples per cycle—and compares derived values against configurable setpoints. When a fault condition is detected, the IED issues a trip command to the associated circuit breaker via binary outputs. Simultaneously, it timestamps all events using an internal clock synchronized to an IEEE 1588 Precision Time Protocol (PTP) or IRIG-B time source, creating a Sequence of Events (SOE) record with 1-millisecond or better resolution. Modern IEDs communicate over IEC 61850 Ethernet-based protocols, publishing GOOSE (Generic Object Oriented Substation Event) messages for peer-to-peer protection schemes and MMS (Manufacturing Message Specification) reports to supervisory SCADA systems.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Explore the core components and standards that define the operational environment of Intelligent Electronic Devices in modern substation automation.
Substation Configuration Language (SCL)
An XML-based language defined in IEC 61850-6 used to formally describe the capabilities, logical topology, and communication configuration of IEDs. The Substation Configuration Description (SCD) file aggregates all IED Capability Descriptions (ICD) and the system specification to define the complete data flow. This enables vendor-agnostic engineering and automated verification of signal mappings between protection and control devices.
Logical Node Abstraction
A core concept of IEC 61850 where physical device functions are decomposed into standardized virtual objects called Logical Nodes. For example, a distance protection function is represented by the PDIS logical node, while a circuit breaker is modeled as XCBR. This abstraction layer decouples the application logic from the physical hardware, allowing an IED to expose its data model in a semantically consistent way regardless of the manufacturer.
Merging Unit & Process Bus
A merging unit is a device located in the switchyard that digitizes analog signals from instrument transformers and publishes them as Sampled Values (SV) onto a fiber-optic process bus. IEDs subscribe to these streams, eliminating dedicated copper wiring for CT/VT circuits. This architecture, defined in IEC 61850-9-2, reduces cabling complexity and enables a fully digital, interoperable substation where multiple IEDs can share a single set of instrument transformers.
IED Cyber Security (IEC 62351)
The IEC 62351 standard defines security measures for power system communication protocols, directly impacting IED hardening. It mandates role-based access control (RBAC) for MMS connections, digital signatures for GOOSE messages to prevent spoofing, and TLS encryption for external telecontrol links. Modern IEDs implement these controls to prevent unauthorized tripping commands and ensure the integrity of time-critical protection signals.
Time Synchronization (IEEE 1588 PTP)
Precision Time Protocol (PTP) defined in IEEE 1588v2 provides sub-microsecond clock synchronization across the substation network, which is critical for IED functions like synchrophasor measurement and sampled value alignment. Unlike legacy IRIG-B, PTP operates over the same Ethernet fabric used for GOOSE and MMS, achieving 1 microsecond or better accuracy required for Class T4 instrument transformers and wide-area protection schemes.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us