Substation Configuration Language (SCL) is the standardized, XML-based file format specified by IEC 61850-6 for the formal description of substation automation systems. It captures the complete engineering lifecycle, defining the functional capabilities of Intelligent Electronic Devices (IEDs) , the communication network topology, and the single-line diagram of the primary switchyard equipment in a vendor-agnostic, machine-readable schema.
Glossary
Substation Configuration Language (SCL)

What is Substation Configuration Language (SCL)?
Substation Configuration Language (SCL) is the XML-based language defined by IEC 61850-6 used to formally describe the configuration of substation automation systems, including IED capabilities, communication networks, and system topology.
SCL enables seamless data exchange between engineering tools from different manufacturers by defining distinct file types, including ICD (IED Capability Description), SSD (System Specification Description), SCD (Substation Configuration Description), and CID (Configured IED Description). This structured methodology eliminates manual data entry errors, automates the binding of Logical Nodes to physical equipment, and ensures consistent configuration of GOOSE and Sampled Values communication across the entire substation project lifecycle.
Core Characteristics of SCL
The XML-based language used to formally describe the configuration of substation automation systems, ensuring interoperability between engineering tools and intelligent electronic devices.
XML-Based Schema Definition
SCL is defined using XML Schema (XSD), providing a rigorous, machine-validatable syntax for substation configuration. This ensures that every SCL file—whether describing a single IED or an entire Substation Automation System (SAS)—conforms to a strict structural contract. The schema enforces correct nesting of elements like Substation, VoltageLevel, Bay, and Equipment, preventing syntax errors before engineering begins. Tools can automatically validate files against the IEC 61850-6 schema, guaranteeing syntactic interoperability between vendors.
Hierarchical Substation Modeling
SCL represents the physical power system as a strict hierarchy:
- Substation: The top-level container for the entire facility.
- VoltageLevel: Groups equipment at a common nominal voltage.
- Bay: A logical grouping of primary equipment within a voltage level, such as a line feeder or transformer bay.
- Equipment: Individual primary apparatus like circuit breakers (XCBR), disconnectors (XSWI), and instrument transformers. This structure mirrors the physical topology, allowing engineers to map Logical Nodes directly to the equipment they protect or control.
IED Capability Description (ICD)
An ICD file is a specific SCL file type that describes the complete functional capability of a single Intelligent Electronic Device (IED) type. It declares:
- The IED's physical communication ports and IP configuration.
- Every Logical Device and Logical Node it contains.
- All supported GOOSE and Sampled Values (SV) publishing and subscribing capabilities.
- Pre-configured datasets and report control blocks. The ICD serves as a template; it contains no system-specific binding to other IEDs or primary equipment.
System Specification Description (SSD)
The SSD file captures the formal specification of the substation's primary equipment and required automation functions before any IED is selected. It contains:
- The complete single-line diagram topology using the hierarchical structure.
- Logical Nodes placed on primary equipment to specify required protection and control functions (e.g., a PDIS for distance protection on a line).
- No IED-specific information. The SSD represents the 'what is needed' view, which is later mapped to the 'what is provided' view in ICD files during system configuration.
System Configuration Description (SCD)
The SCD file is the master configuration document for the entire Substation Automation System. A system configurator tool generates it by importing all relevant ICD files and the SSD, then binding them together. The SCD contains:
- The complete communication network topology, including switch configurations and IP subnets.
- The full binding of GOOSE publishers to subscribers across different IEDs.
- The mapping of every Logical Node instance to a specific IED and primary equipment.
- All configured report control blocks for SCADA communication. The SCD is the single source of truth from which IED-specific configuration files are derived.
Communication Network Engineering
SCL formally models the station communication network within the Communication section. This includes:
- Subnet: Defines a logical network segment, typically a VLAN.
- ConnectedAP: The access point of an IED on a subnet, specifying its IP address and subnet mask.
- GSE (Generic Substation Event): Defines the multicast MAC address, APPID, and VLAN priority for GOOSE messages.
- SMV (Sampled Measured Values): Defines the multicast parameters for Sampled Values streams. This formal description allows network switches to be pre-configured and ensures deterministic, real-time performance.
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.
Frequently Asked Questions
Clear answers to the most common questions about Substation Configuration Language, the XML-based backbone of IEC 61850 system engineering.
Substation Configuration Language (SCL) is the XML-based language defined by IEC 61850-6 used to formally describe the configuration of substation automation systems. It works by providing a standardized, machine-readable format to represent the entire substation automation lifecycle—from the functional specification of an Intelligent Electronic Device (IED) to the communication network topology and the binding of logical functions to physical equipment. SCL enables seamless data exchange between engineering tools from different vendors, eliminating manual transcription errors. The language defines a strict schema with specific file types (ICD, SSD, SCD, CID) that each represent a different stage of the engineering process, ensuring that a protection engineer's design intent is accurately translated into a configured, interoperable system.
Related Terms
Mastering Substation Configuration Language requires understanding its relationship with the core communication protocols, data models, and hardware elements defined by the IEC 61850 standard.
IEC 61850 Data Model & Logical Nodes
SCL files formally describe the Logical Nodes (LNs) and data objects that reside within IEDs. Each LN represents a specific function, such as a circuit breaker (XCBR) or distance protection (PDIS). The SCL configuration binds these abstract data models to physical devices and communication services.
- Defines the functional hierarchy: Physical Device > Logical Device > Logical Node > Data Object
- SCL enforces the standardized naming and semantic constraints of the IEC 61850-7-4 data model
- Enables interoperability by ensuring every vendor's IED exposes data in a predictable, machine-readable structure
GOOSE & Sampled Values Communication
SCL configures the high-speed, publisher-subscriber communication mechanisms that replace traditional copper wiring. GOOSE messages transmit binary tripping and interlocking signals, while Sampled Values (SV) stream digitized current and voltage measurements across the Process Bus.
- SCL defines the
Communicationsection specifying VLAN IDs, MAC addresses, and APPIDs for each GOOSE/SV control block - The
Inputssection in an IED's SCL file maps incoming GOOSE/SV streams to internal virtual inputs, replacing physical wiring diagrams - Enables deterministic, multicast Ethernet communication with sub-millisecond latency for protection schemes
Intelligent Electronic Devices (IEDs)
An Intelligent Electronic Device (IED) is the physical microprocessor-based controller whose capabilities are described by an ICD (IED Capability Description) file. SCL provides the XML schema to instantiate and configure these devices within the complete substation automation system.
- The ICD file lists all Logical Nodes, data sets, and control blocks a device can support
- System integrators use SCL tools to configure IEDs by creating CID (Configured IED Description) files
- SCL manages the binding of IED functions to specific network interfaces and time synchronization sources like PTP
System Specification & Topology
The SSD (System Specification Description) file captures the single-line diagram and functional requirements of the substation independent of any specific vendor hardware. SCL links this logical specification to the physical topology and concrete IED implementations.
- Defines the primary equipment topology: transformers, circuit breakers, disconnectors, and their electrical connections
- Specifies required Logical Nodes and their functional assignments to bays and voltage levels
- The SCD (Substation Configuration Description) file merges all ICD and SSD files into a single, comprehensive system-wide configuration
Engineering Workflow & File Types
The IEC 61850-6 standard defines a formal engineering process using distinct SCL file types that evolve through the project lifecycle, from specification to commissioning.
- SSD (System Specification Description): Functional requirements and single-line diagram
- ICD (IED Capability Description): Vendor-provided template of an IED's maximum capabilities
- SCD (Substation Configuration Description): The master configuration file for the entire substation
- CID (Configured IED Description): The specific configuration file loaded directly into an IED
- SED (System Exchange Description): A subset of SCD used to exchange configuration data between projects or stakeholders
Cybersecurity & IEC 62351
SCL configurations must align with IEC 62351 security standards to protect substation communications from cyber threats. SCL files define the security policies applied to GOOSE, SV, and MMS protocols.
- Specifies authentication and integrity mechanisms for real-time GOOSE/SV messages
- Configures Role-Based Access Control (RBAC) for MMS client-server connections
- Defines key management parameters and certificate authorities for secure communication
- SCL tools must validate that security configurations do not violate latency constraints for protection-class traffic

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