IEC 61850 for Modern Power Automation
IEC 61850 is not just a protocol; it is an international standard defining communication architectures for Intelligent Electronic Devices (IEDs) in electrical substations. Its primary goal is to ensure interoperability, allowing devices from different manufacturers to exchange information and perform integrated functions without proprietary converters.
The Core Philosophy: Object-Oriented Modeling
Traditional protocols (like DNP3 or Modbus) use a “flat” structure where data is accessed via register numbers or point addresses. IEC 61850 uses a hierarchical, object-oriented model that attaches meaning (semantics) to data.
The Hierarchy:
- Physical Device (IED): The actual hardware (e.g., a protection relay).
- Logical Device (LD): A virtual grouping of functions within an IED (e.g., “Protection” or “Control”).
- Logical Node (LN): The smallest functional entity (e.g., XCBR for a circuit breaker or MMXU for measurement).
- Data Object (DO): Specific info within a node (e.g., Pos for position).
- Data Attribute (DA): Detailed properties (e.g., stVal for status value or t for timestamp).
Example of Semantic Naming: Bay12Unit2/XCBR1.Pos.stVal clearly identifies the status value of the first circuit breaker in Unit 2 of Bay 12.
2. Three Primary Communication Mechanisms
IEC 61850 separates the data model from the communication technology, allowing the standard to adapt to new network advancements without changing the way data is described.
- MMS (Manufacturing Message Specification):
- Model: Client-Server.
- Purpose: Supervisory functions, SCADA communication, and file transfers (like disturbance records).
- Stack: Mapped to TCP/IP over Ethernet, ensuring reliable, routable delivery.
- GOOSE (Generic Object Oriented Substation Event):
- Model: Publisher-Subscriber.
- Purpose: Time-critical protection signals (e.g., trips, interlocking).
- Speed: Mapped directly to Layer 2 Ethernet to achieve speeds under 4 ms.
- Sampled Values (SV):
- Purpose: Streaming high-speed digitized measurement samples from Merging Units (MU) to protection relays.
- Mechanism: Cyclic multicast over Ethernet, replacing traditional analog copper wiring.
3. SCL: The Engineering Language
The Substation Configuration Language (SCL) is an XML-based format used to describe everything about a substation’s configuration. It ensures that tools from different vendors can share configuration data.
Key SCL File Types:
- ICD (IED Capability Description): Provided by the manufacturer; describes what an IED can do.
- SSD (System Specification Description): Describes the substation structure and required functions (the “blueprint”).
- SCD (Substation Configuration Description): The master file containing the complete substation configuration (IEDs, communication, and topology).
- CID (Configured IED Description): The final file loaded into a specific physical IED to make it work.
4. Why Use IEC 61850?
- Reduced Costs: Replaces miles of copper wiring with fiber optic “Station” and “Process” buses.
- Flexibility: Adding new functions often only requires a software configuration change rather than new physical wires.
- Self-Description: Clients can “interrogate” a device to learn its data structure automatically.
- Future-Proof: The separation of models from protocols means the logic remains valid even as network hardware evolves.
In the IEC 61850 standard, Substation Configuration Language (SCL) is an XML-based language defined in Part 6 that provides a formal, standardized way to describe a digital substation’s architecture, communication parameters, and device capabilities. By using a common file format, SCL eliminates the reliance on proprietary vendor formats, significantly simplifying the engineering and integration process.
How SCL files simplify configuration management is detailed below:
1. Eliminating Manual Mapping and Point Lists
Traditional protocols (like DNP3 or Modbus) require engineers to manually enter and match register addresses (e.g., AI 27 or DI 52), a process that is time-consuming and prone to human error. SCL replaces this with functional naming; instead of an anonymous address, a point is identified by its power system context, such as Device/XCBR.Pos.stVal for a breaker position. This allows configuration tools to automatically retrieve and map data points without manual intervention.
2. A Standardized Engineering Workflow
SCL simplifies management by defining a clear chain of file types that move a project from design to operation:
- SSD (System Specification Description): Allows designers to specify the substation structure and required functions (single-line diagram) before any physical hardware is even selected.
- ICD (IED Capability Description): Provided by manufacturers to describe exactly what an Intelligent Electronic Device (IED) is capable of.
- SCD (Substation Configuration Description): Serves as the master configuration file and “single source of truth” for the entire substation, combining all IED configurations, communication parameters (IP and MAC addresses), and the substation topology.
- CID (Configured IED Description): The finalized file exported from the SCD and loaded into a physical IED to make it work in the substation.
3. Enhanced Interoperability and Tool Selection
Because SCL is standardized, it enables interoperability between tools from different manufacturers. A system integrator can use a single “System Configuration Tool” to design the entire network and then export project-specific files (IID or SCD) that third-party “IED Configuration Tools” can import for detailed device settings. This gives utilities the flexibility to choose the best equipment for their needs without being locked into a single vendor’s ecosystem.
4. Simplified Maintenance and Troubleshooting
SCL files simplify the ongoing management of a substation throughout its life cycle:
- Consistency Checks: Configuration tools can use SCL to automatically detect and prevent configuration inconsistencies between distributed functions.
- Rapid Diagnostics: Interpretation tools can compare real-world online Ethernet traffic against the “as-built” design in the SCD file to immediately identify misconfigurations or communication failures.
- Versioning: SCL supports version identification and revision indices, making it easier to track changes and manage firmware updates across thousands of data points.
- Virtualization: The SCL-based descriptions allow for the creation of virtualized protection and control environments where software images can be easily replicated or updated.
In the IEC 61850 standard, SCL (Substation Configuration Language) uses different file types to manage the engineering process from initial design to device commissioning. While both SCD and CID files are XML-based and essential for configuration, they differ fundamentally in their scope and application within the substation workflow.
SCD: Substation Configuration Description
The SCD file is the master configuration file for the entire substation automation system.
- Scope: It provides a complete, system-wide description. It contains the entire substation’s electrical topology (the single-line diagram), all IED (Intelligent Electronic Device) configurations, and every communication parameter (IP addresses, GOOSE multicast addresses, and report control blocks).
- Creation: It is generated by a System Configuration Tool (SCT). This tool imports the capabilities of various devices (via ICD files) and integrates them into a unified system design.
- Purpose: The SCD serves as the “single source of truth” for the substation. It is used to define how data flows between different IEDs (e.g., GOOSE subscriptions) and is the reference document for testing and commissioning the entire system.
CID: Configured IED Description
The CID file is a finalized configuration file for a single, specific physical IED.
- Scope: It is essentially a subset of the master SCD file, stripped down to only include the information that the specific device needs to know to operate. It includes that IED’s specific addresses, its finalized data model, and all project-specific settings.
- Creation: It is generated by a vendor-specific IED Configuration Tool (such as ABB PCM600 or Siemens DIGSI). This tool typically imports the relevant data from the SCD file and adds any required vendor-specific parameters.
- Purpose: The CID is the file that makes the IED work. It is downloaded directly into the physical device during the commissioning phase. Once loaded, the IED reads the CID to configure its MMS server, GOOSE publisher/subscriber settings, and internal logic.
Key Differences at a Glance
| Feature | SCD File | CID File |
|---|---|---|
| Full Name | Substation Configuration Description | Configured IED Description |
| Focus | The entire substation | A single physical IED |
| Created By | System Configuration Tool | IED Configuration Tool |
| Contents | Entire topology, all IEDs, all comms | Subset of SCD + specific device settings |
| Primary Use | System integration and reference | Downloaded to physical device for operation |
In the standard engineering workflow, the flow of information always moves from the master design toward the individual device: ICD (Capability) → SCD (Substation Master) → CID (Final Device Config).
