One line in a switchgear specification can add a year to a project or nothing at all, depending on what was meant by it. It is usually written as six words and left there.
IEC 61850 is titled Communication networks and systems for power utility automation. It is a series of parts, and the parts do genuinely different jobs. Writing the number alone into a specification selects all of them and none of them at once.
Three services, three different projects
What a supplier has to build depends entirely on which of the three communication services is required.
| Service | What it does | What it costs you |
|---|---|---|
| Client–server reporting | An IED publishes measurements, status and events to a station computer or gateway on request or on change. | Modest. This is what most “61850 compliant” specifications actually want. |
| GOOSE | Fast peer-to-peer messaging between IEDs, used for interlocking, blocking and trip signals in place of hard wiring. | Significant. It replaces copper with an engineering artifact, and the network design becomes protection-critical. |
| Sampled values | Digitized current and voltage samples on the wire, replacing the analogue secondary circuits from the instrument transformers. | Highest. Part 9-2, edition 2.1 of 12 February 2020, maps sampled values directly onto an Ethernet link, paired with Part 8-1. It also brings a hard time-synchronization requirement with it. |
The deliverable is a file, and somebody has to own it
IEC 61850-6 defines the configuration description language — a file format for describing communication-related IED configurations, covering IED parameters, communication system configuration, switchyard structure and the relations between them. Its stated purpose is to let engineering tools from different manufacturers exchange capability and system descriptions. The current consolidated edition is 2.2, published 27 November 2024.
In practice this is the part that decides whether a project runs. The family of SCL files — the IED capability description produced by each device maker, the system specification produced by the designer, and the configured system description that binds them together — is the engineering. Three questions settle it, and all three belong in the enquiry:
- Who produces the configured system description? The switchgear manufacturer, the system integrator, or the utility’s own engineering team. If this is unstated, every party will have assumed one of the others.
- Who owns it afterwards? An SCL file that lives only inside a vendor’s tool is a maintenance liability on a twenty-five year asset.
- What is handed over, and in what form? Native tool project files are not a substitute for valid SCL.
The parts worth naming
A usable specification names the parts it relies on rather than the series. The ones that normally matter on a switchgear package are Part 6 for the configuration language, Part 7 for the data model and the logical nodes that represent a breaker, a switch, a measurement or a control, and Part 8-1 for the mapping that carries client–server services and GOOSE. Part 9-2 joins them only if sampled values are in scope, and brings with it a time synchronization requirement that a precision time protocol power utility profile is written to satisfy.
The data model is the quiet one. Logical nodes give a breaker, an interlock or a three-phase measurement the same name and the same structure regardless of who made the device, and that is the whole point of the standard. It is also where a project can be undone by local habit: a tag naming convention imposed on top of the model, inconsistently, produces a system that is standards-compliant and unreadable.
What to put in the enquiry
| Specify | Rather than |
|---|---|
| Which services are required: reporting, GOOSE, sampled values | “IEC 61850 compliant” |
| The SCL deliverables and who produces each | Assuming the integrator will handle it |
| Conformance certificates per IED, with their edition and issuing facility | A vendor statement of compliance |
| Integration testing of the configured scheme at FAT | Testing the primary equipment and commissioning the comms on site |
| Network architecture and redundancy, and who owns the switches | Leaving the network outside the switchgear scope |
| Time synchronization source, accuracy and profile | Nothing, which is what usually appears |
Where we stand
Where a project specifies IEC 61850, we settle the three questions above at enquiry stage rather than at commissioning: which services are in scope, who produces and owns the configuration files, and what is tested together before the equipment ships. IED conformance evidence is provided per device with its edition and issuing facility named. Our smart grid infrastructure page sets out the ranges this applies to, and the documentation register carries the standards with their references.