Showing posts with label SCL. Show all posts
Showing posts with label SCL. Show all posts

Thursday, November 19, 2026

How Events could Issue Reports according to IEC 61850

Reporting in IEC 61850 is a very powerful and efficient service model to inform monitoring and other systems (SCADA, RTU, ...) about changes in the power delivery (and any other) system. The flow of information reported by an IEC 61850 Server is as described in the following three services:

Unsolicited Reporting based on events (Report by exception, buffered Reporting, buffer time)

Appl.<--Client<--Report<--Server:Report Control Block<--DataSet<-DataAttributes<--process

Requested Report (General Interrogation, gi, all values according to DataSet)

Appl.-->Client-->Request Report-->Server:Report Control Block<--DataSet<-DataAttributes<--process
Appl.<--Client<--Report<--Server

Periodic Reporting (Integrity reporting, all values according to DataSet)

Appl.<--Client<--Report<--Server:Report Control Block<--DataSet<-DataAttributes<--process

The reporting services are impacted by four definitions/configurations:

  1. Abstract reporting service model in IEC 61850-7-2
  2. Data Attributes of Logical Nodes (IED Instances, Type Templates) - SCL describing the semantic (context) of the data and its relation to the application and physics ...
  3. Report Control Block (RCB) Configuration - SCL
  4. Mapping to MMS (IEC 61850-8-1) and DMS (IEC 61850-8-3)

Explanation of crucial details:

  • report by exception - A DataSet with n Members (DataAttributes), only the value of the Member that shows a change or update will be reported ... means: short messages
  • buffer time - same as above, but (during buffer time) collect all events after the first event happened ... send them together in one message
  • buffered Reporting - buffer all reports in the server as long as no communication is available ... when communication is available, client can request buffered events.
  • Trigger Option attribute of DataAttributes: dchg (Data Change), dupd (Data Update), qchg (Quality Change) - possible trigger options
  • TriggerConditions in Report Control Blocks: data-change, quality-change, data-update, integrity, general-interrogation - which conditions are monitored by a specific RCB
  • ReasonForInclusionInReport in Report messages: data-change, quality-change, data-update, integrity, general-interrogation - which condition did issue sending the report
  • Services and ReportControl elements in SCL - all details how a specific IED (in the sense of SCL ... it is a kind of a virtual device) uses reporting ... many combinations are possible ... not all combinations are valid ...

Here we have the chicken and egg problem: If you don't know what you need, it is hard to recommend what you should do. If you don't know what IEC 61850 reporting offers, it is hard to decide which features you want to use.

I have seen many people struggling with reporting ... 

In case you want to understand the possible features of reporting, please contact me ... to tap my experience.

By the way, IEC 61850-8-3 (DMS) simplifies the syntax of the report message explicitly ... people appreciate it very much ...

Thursday, October 29, 2026

OPC UA is About to Follow IEC 61850 in its Energy Initiative

The standard series IEC 61850 has already helped globally for more than 20 years to improve (with a broad approach) the power system engineering, system and device configuration, information modelling, and information sharing ... helping to reach a high level of reuse-ability and getting more resilient systems ... keeping the power flowing and the grass green.

Many years after it became obvious that IEC 61850 uses such a broad approach, the time has come that the OPC Foundation tries to benefit from the big success of IEC 61850!! Really!

According to the OPC Foundation Energy Initiative [7 page PDF] standardized "Semantic Information Models of Energy-related Systems ..." are planned to use IEC 61850! Wow!

Excerpt: 

"In 2024. OPC UA has started to look at the whole energy market to help simplify, standardize and improve the resilience of connection points. Not only among the five major energy components but also within. ... One important standard that is widely used in substations, wind farms, solar array and other large utility size installations is the IEC 61850. The OPC UA Wind and Solar PV Operations and Monitoring (SPOM) working group, together with the IEC 61850-20 working group has started mapping the 61850 models to OPC UA models ...

THE CHALLENGE: FRAGMENTED ENERGY DATA

Many factories lack a consistent way to collect and analyze energy data from machines, devices, and production systems. Different communication technologies and proprietary interfaces often prevent seamless integration of energy information. Without standardized data structures and semantics, companies struggle to gain a clear overview of their energy usage. This makes it difficult to identify optimization potential, implement coordinated energy-saving measures, ..."

For exactly these reasons, the electric power industry started in the year 1995 to develop the standard series IEC 61850! The struggle is reduced since IEC 61850 touched the road.

With IEC 61850-8-3 (web-based communication using WebSockets, JSON and DER encodings) a new and modern information sharing is underway - while preserving the rest of IEC 61850 (engineering, configuration, models, ...) unchanged.

It is also interesting to see how the wind industry that developed the standard series IEC 61400-25 (Wind Turbines) has understood that the deviation from IEC 61850 as it happened in the first two editions of IEC 61400-25-2 (models) was not a good idea. The third edition of IEC 61400-25-2 will be harmonized with IEC 61850 (The ORIGINAL).

Congratulation for using THE ORIGINAL! ... always use the original IEC 61850 ... if possible ...

Saturday, October 24, 2026

CDV Just Published: IEC 61400-25-2 Edition 3 - Wind Power Plants - Information Models

Just published: the Committee Draft for Vote (CDV) of the 3rd edition of the Standard for Wind turbines - IEC 61400-25-2: Communications for monitoring and control of wind power plants - Information models 

IEC 61400-25-2 ED3, 88/1199/CDV for Public Commenting (157 pages) 

DATE OF CIRCULATION: 2026-10-16
CLOSING DATE FOR VOTING: 2027-01-08

Excerpt from the Foreword:

"This edition includes the following significant technical changes with respect to the previous edition: 

The harmonization of IEC 61400-25-2 with IEC 61850 in term of data modelling and document structure. The IEC 61400-25-2 Edition 3 is auto-generated from the reference UML model, following the process set-up in TC57 and described in IEC TS 61850-1-2. A benefit of this process is that this document is provided with Code Components, including the NSD.

Common data classes (CDC) specific to the wind power domain have been removed and replaced by existing CDCs from the IEC 61850-7-3:2011+AMD1:2020 to follow the rules set in IEC TS 61850-1-2. ..."

I highly appreciate that this 3rd edition compared to the first two editions is really harmonized with the original standard IEC 61850 - which was the base for the IEC 61400-25-2 ... BUT the group decided some 20+ years ago to be (for good reasons) "special" ... unfortunately I (and a few other experts) were not able to convince that the real benefit would be to just use the IEC 61850 as a base and just extend models for wind turbines. 

IEC awarded me with the IEC 1906 Award vor my involvement in IEC 61850 AND the adoption for wind turbines:


Congratulation for this step forward to reach a harmonious set of information models published by IEC 61850 AND IEC 61400-25-2 !!!

All other "tools" like SCL configuration language, services, protocols like IEC 61850-8-1 ad IEC 61850-8-3 (Websockets, JSON encoded messages; in preparation) ... can be used also for the wind turbines. The need for an extra comprehensive mapping of the models to OPC UA is ... !?

Wednesday, September 23, 2026

Update on Traffic Engineering with IEC 61850

The other day I have discussed Traffic Engineering with IEC 61850. In a second post today I showed how SCL can be used to validate incoming messages.

Now I will show you in the analogy of traffic control how limits on the street are signaled. Fotos by Karlheinz Schwarz. 

First example Maximum Load Limit on a bridge: 


Second example with three limits: one vehicle at a time, max gross weight, and max speed:


Third example: max Tunnel hight 4,00 Meter

I guess you understand that IEC 61850 SCL can be used to configure signals for limits ... 

Enjoy. 

Cyberattacks Targeting OT Systems and IEC 61850

According to Security Week, "Hackers targeted operational technology (OT) systems at two private water utilities in Colorado in late August, apparently attempting to cause disruptions.

Few technical details are available, but it seems the attackers targeted industrial control systems (ICS) at the water utilities, which serve fewer than 200 people. 

A spokesperson for Colorado Governor Jared Polis told The Denver Post [paywalled] that the attackers changed equipment settings, disabled remote access and alarms, and altered pumping cycles. However, the disruptions were brief and did not affect water services or public safety."

I highly recommend small and all electric power utilities to pay attention to this situation and improve the cyber-security of the power system devices like SCADA, control, protection, RTUs, ... changing equipment settings could cause dangerous situations like blackouts, ... 

IEC 61850 information models can play an important role when somebody wants to change settings of a process control signal. The other day I used the IEDScout from Omicron to limit the setting value of a CDC=APC (Analogue Setting) structured setting. I set the maxVal to 1,000 (in the server) and tried with a second instance of IEDScout as a client to set the process value to Oper.ctlVal > maxVal ... the server responds with an MMS Write-Error and a Report "Inconsistent-parameters". The server did not accept a value outside of the maxVal and minVal. The process value did not change at all!

This possibility is a standardized (kind of "security") function incorporated into the CDC=APC !!!

Sure, the maxVal and minVal should be blocked for online changes! That could be configured in the CSL file as well.

So, IEC 61850 and especially SCL provide more than just a communication configuration ... many function related definitions are defined for the various common data classes!!

Let me know in case you want to further discuss this.

P.S.: After I published the above post I came across the following LinkedIn post   

CVE-2025-6625 — Improper Input Validation
> Crafted FTP command can take the controller offline
> CVSS 7.5 — network reachable, no auth, availability hit
> Energy, water, manufacturing fleets still run these PACs

Input VALIDATION is a crucial issue ... YES!

P.S2.: I just read another post on LinkedIn regarding DNP3 message validation. Interesting.

P.S3: Update

Monday, August 17, 2026

IEC 61850 for Newbees - Traffic Engineering with IEC 61850-6 (SCL)

I agree: The standard series IEC 61850 is quite comprehensive ... some believe it is complex. Ok. What can I do to help you getting a better understanding? I will try to help you. 

Today I will show how IEC 61850-6 (SCL, System Configuration Language) can be used for traffic engineering - traffic means: "signals" are communicated back an forth: analogue measurements, status measurements, control, configuration, event-driven reports, event-driven logs, ... start and stop of event recorder, trip-signals, ... in IEC 61850 "signals" are named and a binding of an instance to the application process (e.g., Bay1 Circuit Breaker 2) is specified ...

I am using a brief prose language ... this description could be transformed to an SCL compliant (machine processable ) XML file.

The many "signals" are travelling from a source to a destination ... let's say the following valid (allowed) routes are:

  1. A->B,
  2. B->A,
  3. V->A,
  4. A->C, 
  5. D->E, 
  6. R->S, 
  7. R->A

Each letter is representing a source or destination of the "signal" flow. The "->" is representing one of the specific "signals" standardized in IEC 61850. In the first route A sends an operate to B and B is reporting back to A a changed status information ...

In SCL we can configure now for each route in detail the sources, destinations, strongly typed "signals", communication services, ... The SCL compliant System Configuration Description (SCD) would list all details on all routes ... 

The source knows by the SCD document which "signal" is to be sent (when and how) to which destination. The destination knows by the SCD document which "signal" it receives (from which device, when and how).

What else can we do with the SCD file?

  1. A tool could check if all source and destination (devices) are specified ... a source A is configured to send a signal to B ... Is B at all specified? Maybe it was forgotten.
  2. A tool could check if for all source and destination devices the addresses are configured. 
  3. Another tool could check if all traveling "signals" (messages) are specified in the SCD document. A "signal" that travels during online operation from X to B (here X tries to connect to B) is not specified and thus NOT ALOWED. The tool could rase the red flag telling the system engineer that an unknown device X is active on the network. 
  4. ... many other possibilities are listed in the following figures from my seminar slides (some 10+) years old.


I hope you got an impression what IEC 61850-6 (SCL) could provide.
SCL is the backbone of IEC 61850!
Check HERE for a crucial use-case for SCL (cyber security ...).
Let me know if you have a question on this post.
P.S: Update

Tuesday, August 11, 2026

Siemens PCS7 (TIA) PowerControl Station Gateway connects PLCs with IEC 61850 IEDs

In a post earlier today I wrote: "It does not make sense to decouple power systems from big(ger) applications." ... this reminded me to discuss another use case ... factory automation to substation ...

Siemens offers PLCs with the PCS7 family. They have developed gateways that bring the substation closer to the power user ... 

PCS 7 PowerControl Station Gateway connection of a SIPROTEC 5 protection device (speaking IEC 61850!)

The brochure states at the beginning: "In addition to the demanding process automation requirements in many industrial plants, it is also necessary to integrate the medium-voltage power supply switchgear into a complete automation system.

Components of such plants are electrical consumers with high energy requirements (factories, chemocal plants, ...). Individual consumers are monitored and controlled via protection devices, also known as IEDs (intelligent electronic devices)."

So, my statement on the post earlier today has been confirmed! 

The same is available for the integration of a substation into a Siemens TIA (Totally Integrated Automation) ... TIA Station Gateway: excerpt of that page:

"With the new IEC 61850 server functionality, you can extend your station gateway integration allowing you to reliably publish process data directly to IEC 61850 clients via GOOSE Publisher or MMS polling and reporting with a high degree of performance. Whether protection systems, instrumentation and control or automation environments: The publisher ensures that events are quickly transferred and facilitates fixed data models and the highest degree of interoperability."

WOW.

Monday, August 10, 2026

IEC 61850 covers applications inside substations AND beyond substations

IEC 61850 is applicable for general automation applications as well as for electric power delivery systems. The following lists give an impression of what kind of domains are taken into account so far ... more to come:

Information models and exchange for

  • real-time and near real-time applications  (pub/sub: GOOSE, Sampled Values)
  • protection
  • monitoring, supervision, and control (client/server TCP/IP and WebSocket)
  • substation and feeder equipment
  • substation-to-substation
  • substation-to-control centre
  • power plant-to-control centre
  • distributed generation
  • distributed energy resources
  • micro grids
  • metering
  • power quality
  • condition monitoring
  • hydro, steam, gas power plants
  • wind generation plants
  • data centers
  • …

System Configuration and engineering

  • System Configuration Language (SCL)
  • Basic Application Profiles
  • top-down-engineering (model-based engineering)
  • - …

These lists demonstrate that the standard series IEC 61850 covers applications inside substations AND beyond substations. One crucial question remains: What are the logical nodes and data objects ... from which parts of the standard series IEC 61850 are required for a specific application domain?
The answer is here: ask me.

HERE you can find a sample model for an IEC 61850 Profile for Distributed Energy Resources Supporting IEEE 1547 [pdf] ... quite interesting ...

You may search the web for MICS (IEC 61850 model implementation conformance Statement) ... 

Note that substations are very crucial components of the interconnected electric energy systems.

Let me know if you need some help.

Tuesday, August 4, 2026

How are IEC 61850 Information Models related to Functions?

The common understanding of information is crucial for the understanding of the related functions that produce, consume, and exchange the information. Information is always "bound" to functions ... no function - no information.

Let's have a look at this function: 

Supervision of a temperature value ... report an alarm to a well known entity when the temperature change rate reaches a value of xyz ... this is the FUNCTION. Now we model it with IEC 61850:

The temperature supervision is modeled in the logical node MySTMP1. We use the data objects Tmp (reported every x minutes), RteAlm (reported when the value of the RteAlmSet is reached, e.g., 0.5 K/s).

This "function" is described in an SCL document ... here the MySTMP1 is bound to a topology (SSD), e.g., room temperature in building so-and-so, the reports are sent to the SCADA system mySCADA-client, ... the factory acceptance test can more or less be automated based on the SCL document.

The IEC 61850 STMP logical node model follows the temperature supervision function!! 

The function was there well before IEC 61850 was born!

IEC 61850 standardizes the information shared with a real function.

The following diagram shows the basic modelling approach in IEC 61850:

  • IEC 61850-7-2 defines the foundation
  • IEC 61850-7-3 defines the common data classes: MV for measurements, SPS for single point status, and ASG for analogue sessings.
  • IEC 61850-7-4 defines the logical node and data object classes.

More details will follow ... stay tuned.


The real challenge with IEC 61850 is: You likely get the feeling when you start reading hundreds of pages: 
unable to see the wood for the trees.

Let me know if you need help ... after 30 years I can support you.

Monday, August 3, 2026

Is IEC 61850 an old Standard?

What do you think? It depends ... IEC 61850 is a standard series of many parts ... published in different years ...

The other day I was reading that somebody on LinkedIn beliefs that IEC 61850 is old ... Oops. Here is what I answered:

I was involved in the development of MMS (ISO 9506, starting mid 1980s), later in ICCP (TASE.2, IEC 60870-6, using MMS), then IEC 61850 (starting 1995, using as well the "old" MMS). 

The AC interconnected power systems have been developed more than 130 years ago ... and improved since then ... AND: Yet we do not complain that they are OLD. They have done a great job. Old wine may be better than young wine ... or?

The standard series IEC 61850 has many aspects to consider: 

  • System Configuration Language (SCL, IEC 61850-6) is brand new! 
  • GOOSE and sampled values are brand new! 
  • The many standard "signals" like MMXU.Hz for frequency measurement are old in the sense that frequency is a physical given.
  • There is something we may call "old": the use of the "old" MMS as the protocol for client/server communication according to IEC 61850-8-1 (-8-2). ok.
  • There is an alternative new web-based solution under way: IEC 61850-8-3 (a new protocol for client/server in IEC 61850 ... WebSocket transport, ASN.1 message schema, ASN.1 JSON encoding rules, and ASN.1 DER encoding rules).

If you want to learn why the Netherlands DSOs initiated the IEC 61850-8-3, check HERE.

A great reply says: "The transport choice is what stands out: MMS was never reachable from a browser, WebSocket with JSON encoding is, which changes what client tooling can be without an install."

There are other brand new parts of IEC 61850 just published, e.g., IEC 61850-7-410 for hydro, gas, and steam power plants.

Monday, July 13, 2026

IEC 61850 for Battery Energy Storage Systems (BESS)

With the growth of planning and installation of BESS the question is discussed, how IEC 61850 could contribute. A lot!

Have a look at three posters that depict the architecture of an electric system that includes batteries ... with some comments from me:

Poster 1
Poster 2
Poster 3

See also a paper on the use of IEC 61850-7-420 (DER) from the year 2014.

Communication networks and systems for power utility automation –
Part 7-420: Basic communication structure –
Distributed energy resources and distribution automation logical nodes

Preview of IEC 61850-7-420 (2021).

A few excerpts:


The DER storage Logical Nodes in IEC 61850-7-420 have hundreds of Data Objects ... see just a few:



IEC TC 57 offers a name space document listing the syntax of all logical nodes and data objects:

That (light) name space is an xml document with 5520 lines !!! The light name space contains the syntax of the models ... the textual semantic is missing ... comes with the purchase of the standard IEC 61850-7-420.

I am confident that IEC 61850 offers the most crucial information models for BESS.

Wednesday, July 8, 2026

Are WebSockets the future for real-time communication?

WebSockets provide a way for web browsers and cloud apps to talk directly to devices for automation and monitoring. A WebSockets create a two-way open communication channel. It wraps messages (according to various message schema, e.g. in ASN.1 notation) in web-friendly formats like JSON. This bypasses strict firewall rules without needing complex, heavy software.

WebSockets are used in many solutions like OPC UA, OpenADR, ... and soon in IEC 61850-8-3 (alternative for MMS). 

How do WebSockets perform in a PLC environment where usually special industrial communication protocols are used? An interesting paper discusses this question:

"Latency Analysis of WebSocket and Industrial Protocols ..."

WebSockets are likely to becoming the future standardized web-based "carrier". 

The Netherlands Distribution Service Operator have shown with a PoC (proof of concept, now used for the definition of IEC 61850-8-3) that standardized (!) WebSockets can exchange IEC 61850 standard(!) messages containing data values produced and consumed by the huge amount of standardized (!) IEC 61850 models, configured by a standardized configuration (!) language (SCL, IEC 61850-6), and encoded in a standard (!) JSON format.

Background information can be found in my video

Feedback on LinkedIn: "This presentation made everything much clearer! But seriously, using WebSockets as a transport for industrial protocols is a really good idea."

Saturday, August 30, 2025

IEC 61850 in Cyber Secure Environments - New Comprehensive Seminar

Due to my family situation (nursing my beloved wife from 2017 to 2022) I had to slow down my training activities. This year I was asked by several senior experts if it would be possible to resume the training.

As a result of discussions with friends of mine, we updated our previous course program and offer a brand new 5-day comprehensive public seminar for Automation, Protection, Monitoring, Engineering, Configuration (SCL), SCADA, Smart Grids, RTU, Gateways, … cyber physical security in electrical systems of any industrial plant … it is available for you and your people.

The reason for the update: We want to do more than teaching the theory of IEC 6850 and demonstrate single IEDs … we want to let our practice talk for your practice. The new training will start in March 2026. Taking the experience with many crucial applications of IEC 61850 into account we offer a new program for a 5-day course conducted by four (4) real experts.

09.-13. March 2026, Karlsruhe (Germany)
21.-25. September 2026, Karlsruhe (Germany)

Click HERE for more details on dates, location, and registration information.

Thursday, January 9, 2025

Why Do We Need IEC 61850 (SCL) Based System Configuration Descriptions?

IEC 61850 has been developed in the late 1990's mainly by protocol experts and protection engineers - results are well done and applied all-over. Later IEC 61850-6 (SCL - Substation System Configuration Language) was in the focus. Now, 30 years later the industry has learned that the System Configuration Description goes far beyond information models and communication networks and services - AND PROTOCOLS. The crucial aspect is about a COMPLETE description of the WHOLE system ... from device independent descriptions of Functions and Function Models applying a Top-Down-Modeling-Approach. Work towards this approach is going on in several projects, e.g., IEC 61850-90-30 (IEC 61850 90-30 – IEC 61850 Function Modeling in SCL). A nice description from Jörg Reuter (Helinks) can be found HERE from the pacworld magazine. IEC 61850 based aspects is - of course - just one (crucial) aspect of a system. There are more aspects ... like Hardware, Software, Cybersecurity, Operation, ...

In addition to getting a complete system specification based on SCL to get a running IEC 61850 based system that does the job you want to have ... there is another crucial aspect: Engineers may be happy to use a complete SCD file to configure everything and then forget the SCD file ... don't forget it BUT keep it up-to-date and NEVER EVER make any change in the system without updating the SCL based System Description! 

You may need the complete and updated SCD file to help you "protecting" yourself in case there is a damage or an accident ... when "a fleet of well dressed lawyers who will use the lack of that document to make you all look guilty after ..." may arrive immediately after ... as Jake Brodsky (a well known engineer) just published in an article about "Industrial Cybersecurity “Gatekeeping”" ... worth to read.

Here is one excerpt from his article: "Take the time to find out where the important documents are such as the Standard Operating Procedures, the chemical Safety Data Sheets, and especially the Control System Narrative documents are located. If you can’t find the control system narrative documents, stop. Get someone to agree to write them with you. This is effectively your contract with the engineers, technicians, and operators that indicates in plain language what is supposed to happen normally and in most upset conditions. If you’re operating without that living document you will all be fodder for a fleet of well dressed lawyers who will use the lack of that document to make you all look guilty after an accident."

What could be done to get and maintain such complete descriptions of various aspects of a system? Do we need more lawyers, politicians, engineers, ... ? 

I am kidding (just a bit): "Hire a lawyer to escort you when you have an interview for a new position as a responsible engineer in a utility or ... in order to figure out (by the right questions of the lawyer) that the company applies with what Jake Brodsky recommends!"

What we really need is more engineers ... gray-hair experts that know a lot about the systems ... that could write down what the systems do and how they work ... and that could train the young people ... BUT: it isn't easy to convince the management to let the engineers learn from the experienced, gray-hair experts ... gray-hair engineers could lead the horses to the water - but they cannot make to drink it. 

What do you think? Let me know!

Friday, May 3, 2024

Some Hints On Static And Dynamic Reporting According To IEC 61850

Let me briefly help to understand the term dynamic and static regarding reporting:

Every report control block must be “created” in an SCL file – no way to create a report control block with a service.

Several report control block attributes can be configured in an SCL file or set (overwritten) by a (MMS) service.

A data set can be “created” in an SCL file or by the optional service CreateDataSet.

The term “dynamic” could apply to the setting/overwriting of report control block attributes, and the creation of data sets.

In one case with a Gateway from a well known vendor (as a client) I have seen that the client always defines the data sets dynamically!! And links a given report control block to that created data set. If a server does not support the service CreateDataSet, then you get into trouble …

A nice summary can be found here:

https://wiki.lfenergy.org/pages/viewpage.action?pageId=56380504

For operational functions (protection, control, …) the only dynamical services that should be allowed are to enable or disable the report control blocks. This should be configured in the corresponding SCL file for an IED by setting the attributes to “Conf”:

<ReportSettings cbName="Conf" datSet="Conf" rptID="Conf" optFields="Conf" bufTime="Conf" trgOps="Conf" intgPd="Conf" resvTms="true" owner="true" />

Example of a device from a well known vendor I received the other day:

<ReportSettings cbName="Conf" datSet="Dyn" rptID="Dyn" optFields="Dyn" bufTime="Dyn" trgOps="Dyn" intgPd="Dyn" resvTms="true" owner="true" />

Dynamic setting or overwriting of control block attributes or creation of a data set by a service could cause a lot of troubles!! Client and server should not allow it!  A well known RTU (client) overwrites dynamically a report control block attribute (in the server) immediately after it has connected to the server … that should not be accepted.

It could have a big impact on testing, e.g., you expect that a report (or GOOSE, SMV) message has a structure defined by a data set “X with 5 members” (according to the SCL file) … but you receive a message with 3 members (from data set Y) only … because somebody has overwritten the attribute “DatSet” of the report (GOOSE, SMV) control block. 

IEC 61850 is very flexible … to cause trouble … if you want to trust, that the device is 100% as shown in the SCL file, then NO dynamic modifications should be allowed!

Do you want have a problem - no problem!

By the way, Andrea Bonetti wrote the other day: "It is a good practice followed by the majority of the TSOs that do write their own IEC 61850 specification (sort of “dynamic reports are not allowed unless for testing/debugging”). It is also mentioned in IEC TS 63266:2023 (Representation of communication in power utility automation)."

Tuesday, February 27, 2024

What is an IED (Intelligent Electronic Device)?

IEC 61850 deals a lot with IEDs. But: What is an IED?

First you can check with two documents of the series IEC 61850:

IEC 61850-1 - Intelligent Electronic Device (IED)
any device incorporating one or more processors with the capability of receiving or sending data/control from or to an external source (for example, electronic multifunktional meters, digital relays, controllers)

IEC 61850-1 - Physical Device (PD)
equivalent to an IED as used in the context of this standard

IEC 61850-5 - Intelligent electronic device (IED)
device incorporating one or more processors with the capability to execute application 
functions, store data locally in a memory and exchange data with other IEDs (sources or sinks) over a digital link

Many years after these definitions have been published, we have different views on the term IED:
Physical IED (in the context of IEC 61850 and IEC 61400-25) - any physical device incorporating one or more processors with the capability of exchanging information (derived from IEC 61850 information models and exchanged with IEC 61850 services for client/server and publisher/subscriber) with other physical device(s). The semantic, the coding and decoding of the exchanged information (messages) follows the standard series.
IED Configuration (in the context of IEC 61850 and IEC 61400-25) - formal description (section in the SCL according to part 6) of the IEC 61850 information models linked to the IEC 61850 information exchange roles client, server, publisher, or subscriber, and the signal flow between physical IEDs.
IED Role (in the context of IEC 61850 and IEC 61400-25) - implementation of the IED Configuration: implementation of the IEC 61850 information model plus implementation of any combination of the following information exchange roles: client, server, publisher, or subscriber.
A Physical IED can host any combination of IED Roles.
Note: A gateway may host a server role to an up-link (first SCL file plus a client role and a subscriber role (both configured in a second SCL file) to the underlying Physical IEDs.
Please note that in SCL a Server configuration comprises the models including the DataSets, Report Control Blocks, GOOSE Control Blocks, SV Control Blocks, and Log Control Blocks:







From a communication point of view GOOSE and SV publisher and subscriber are NOT part of the client/server communication ... 
I hope this definition will help to reduce the disconnects in the communication of the experts.
Let me know what you think.

Saturday, August 12, 2023

IEC CDV files available for Public Commenting - circulation date 2023-08-11

 Dear Friends of IEC standards, I just remember you that IEC lets you comment on published CDVs (Committe Draft for Vote) ... 

Click HERE for general rules, :

IEC Public Commenting

Help shape international standards if you have the requisite technical expertise. Public commenting on draft IEC Standards is open for a two month period

Currently the following IEC 61850 document is open for comments ... you have to login with your IEC account or register for an account:

57/2602/CDV 

IEC 61850-6/AMD2 ED2: Amendment 2 -
Communication networks and systems for power utility automation -
Part 6: Configuration description language for communication in electrical substations related to IEDs 

CLOSING DATE FOR VOTING: 2023-11-03

Please take your time to review the document ... You may agree with me that part 6 (SCL) is a crucial part of the series IEC 61850!

Monday, February 15, 2021

IEC 61850 To Help Securing Process Automation Systems

A Hacker Tried to Poison a Florida City's Water Supply ... the attacker upped sodium hydroxide levels in the Oldsmar, Florida, water supply to extremely dangerous levels ... Within seconds, the intruder was attempting to change the water supply's levels of sodium hydroxide, also known as lye or caustic soda, moving the setting from 100 parts per million to 11,100 parts per million. 

Click HERE for a news report.

How could that happen? Who knows!

There are a lot of discussions complaining about missing security measures like VPN, etc.

Independent of the communication security it is a big mistake that the value could be set to such a BIG number: 11,100 ppm.

IEC 61850 could help to prevent such a situation by applying Analogue Setting model:














At the City of Oldsmar water treatment facility, the "maxVal" of Sodium Hydroxide injection may have been limited to 500 ppm ... as a consequence, there would be no way to configure this to 11,000 ppm.

And: in case somebody changed the value at all, the setMag would change and dchg would become true issuing a report or log entry ...

With the SCL (System Configuration Language, IEC 61850) it could also be configured (in SCL notation) that a particular configuration value could not be changed at all (Fix), changed by a service (Dyn), or changed by SCL only (Conf).

For Input signals there are many specific configuration attributes defined ... 

It is very difficult to convince programmers, managers, R&D people, any other group ... to apply the IEC 61850 Tool.

Hope that will slowly change ... 

Additional discussion by Jake Brodsky click HERE ... summarizing: "... The more self integrity features we include, the more reasonable process limits that we include, the safer we will be."


Tuesday, July 28, 2020

IEDScout 5.00 Available - One of the Most Crucial Test Tools for IEC 61850

IEDScout is a well known test tool for most of the needed support in the communication with IEC 61850 compliant devices.
Omicron has released the version 5.00 ... providing crucial extensions compared to version 4.2:



IEDScout is a versatile software tool for working with IEC 61850 devices. With Version 5.0, IEDScout offers a new level of cyber security and powerful simulation utilizing the new MBX1/RBX1 hardware.
Additional improvements are:

  • IEDScout now supports function-related naming for logical devices
  • The icon set has been updated to provide a smooth user experience when used together with StationScout/StationGuard.
  • When writing data to an IED, IEDScout will now automatically update the “t” attribute of the data object.
  • Improved screen scaling for better readability on high resolution screens.
  • License information is now available in the configuration dialog.
  • OMICRON’s IEC 61850 library has been updated to include the latest developments in standardization and improve interoperability.
  • The usability of IEDScout is continuously improved based on expert reviews and customer feedback.
  • Several smaller tweaks and bug fixes improve overall performance and stability.

Click HERE for more information on IEDScout 5.0

Saturday, March 7, 2020

IEC 61850 Is Very Crucial For Semantic Models And Interoperability

IEC 61850 provides a huge number of generic and specific semantic models ... Logical Nodes, Data Objects, Common Data Classes, Instance-Information, Topology Information, Information Exchange, Communication, Protocols, ...

Can you please show me an easy to understand example! Here you are!

The following figure shows how (meta) model information is added to a simple voltage measurement (right upper corner). The value is wrapped with a data object model comprising with many attributes like instCVal.mag.i or units ...
The logical device and and logical node instance information is added next. Finally the semantic of the information exchange (report model) is applied to the value - sure, there is a data set involved as well (not shown here).
All this information (general and specific (instance) semantic) could be described in an SCL document (using an XML based SCL schema). Note that some configuration information, e.g., engineering unit (kV), may be contained in the SCL document only. The device needs to process implicitly the voltage in kV. A device may allow to use the SCL document to configure the device to expose the voltage in V ... or mV ... A client (SCADA or ...) may read out the model at runtime (including the engineering unit, if that is implemented as a model attribute) or may just read locally the SCL document and get the engineering unit from the file. Note: the SCL document is the main document for the models and configuration ... keep it safe!! And check the online read model against the SCL file from time to time to compare the two in order to figure out any change!


Further in our example we have a simple bay topology with electrical equipment like generator, switch gears, voltage and current sensors. This topology could be engineered and documented with the SCL (System Configuration Language) - an XML schema for a whole system. The equipment is assigned to specific information models (MMXU.PhV.phsA. ...).
The system engineering could be managed, e.g., with the Helinks STS Tool. An easy to use tool.
The generic Information Model, e.g., MMXU (defined in IEC 61850-7-4) is concatenated with the application designation (MyGenSets/Gen11).


The various levels of semantics of the Message elements are:
  1. Model Instance: Hierarchical Identification of the specific Model of Semantics (in SCL) 
  2. Message Elements: Service Type, Identification, Value, Quality, and Timestamp (ACSI - Abstract Services)
  3. Message Instance: Service Type, Instance of Identification, of Value, of Quality, and of Timestamp (Report)
  4. Message semantic (ACSI mapped to MMS)
The modeling approach of IEC 61850 could be applied in most automation domains ... especially when electric power is applied.

Let me know please if there is a similar standard model defined for automation systems that may compete with IEC 61850 and IEC 61400-25.