Showing posts sorted by date for query 8-3. Sort by relevance Show all posts
Showing posts sorted by date for query 8-3. Sort by relevance Show all posts

Tuesday, September 8, 2026

What is IEC 61850-8-1 MMS Compared to IEC 61850-8-3 DMS?

The paper "The Standard Message Specification for Industrial Automation Systems ISO 9506 (MMS)" has been downloaded 6,691 times from the ResearchGate ... seems to be an interesting document. 

Now, since we are working on a new protocol standard for IEC 61850-7-2 Client/Server communication (IEC 61850-8-3, DMS, Direct Message Specification), the question is: What is the difference between MMS and DMS?

Here are some answers:

DMS will be an alternative protocol for MMS ... with WebSocket connectivity, ASN.1 message schema, ASN.1 JER JSON encoding, ... very simple ... a straight forward from IEC 61850-7-2 ACSI (abstract messages) to concrete messages ... 1:1 ... no tricks ...

There are a few crucial aspects: (1) MMS as a standard that needs outdated OSI upper layers, (2) MMS is very complex and does not easily fit for IEC 61850-7-2 ACSI ... needs a tricks mapping to MMS in IEC 61850-8-1, (3) DMS communicates over WebSockets (bidirectional), (4) DMS uses JSON for message encoding (or DER binary) many tools are available, (5) the message schema of DMS is far simpler than the MMS message schema ... even both are using ASN.1 as schema notation, (6) MMS is not a good friend of many experts, (7) the Proof of Concept for RTI2 (Netherlands DSOs) is the basis for IEC 61850-8-3 ... and available at GitHub ...

From an system point of view (engineering, SCL, Models, abstract services, ... application functions, ...) there is no difference between the two protocols. From a smart implementation point of view the "stacks" could have an API that is independent of the protocols. There needs to be a tiny layer that decides if, e.g., a Report (with the payload from the application models) is wrapped with MMS or DMS ... for DMS there are two options: JER (JSON) and DER (binary) ... from a DMS stack point of view there is one line of code (!!) that is needed to encode in JSON or binary ...

Of course, the MMS message syntax and encoding are not compatible with DMS message syntax and encoding. BUT: they both carry the same payload!! ... thanks to the huge list of standardized "Signals" (models).

Both solutions run on TCP/IP ... there may be multi-protocol IEDs available some time down the road ... as we see today that many IEDs are supporting multiple protocols ... 

People asked me: Why did you not have this solution developed earlier?!? I developed something with my granddaughter when she did her Bachelor at KIT ... check my blog with some historical discussions

Saturday, September 5, 2026

IEC published the Committee Draft (57/2980/CD) on IEC 61850-8-3

The next step of the publication of IEC 61850-8-3 has been reached

Yesterday (2026-09-04) IEC published the Committee Draft (57/2980/CD) on

"Communication networks and systems for power utility automation –
Part 8-3: Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS), JSON Encoding Rules, and WebSockets
"

The commenting period closes on 2026-10-30 ... very soon.

All experts that are members of the IEC TC 57 National Committees can access the document and provide comments online.

My experience with the editing processing tool (OSD - Online Standards Development) is very positive: After I finished the editing on Monday (2026-08-31) IEC could easily publish the CD ... the document follows automatically the format of IEC ... because it is an IEC (ISO) tool ... perfect.

The crucial definition is the ASN.1 message schema that is used to code and decode messages (see see below for a link to the ASN.1 schema used in the RTI2 open-source software):



The committee draft (57/2980/CD) is based on the Netherlands Netbeheers Proof of Concept for RTI2 (real-time interface). Netbeheer is supporting the implementation as open-source software under GitHub. The message syntax of the committee draft is the latest ASN.1 module. The ASN.1 version at GitHub is a pre-version of the official version:
General: https://github.com/Netbeheer-Nederland/iec61850-websocket

Wednesday, August 12, 2026

Sample of an IEC 61850-8-3 request-response message sequence using JSON

The standard IEC 61850-8-3 under preparation will use ASN.1 JER (JSON) encoding. In order to understand, what that means check the following message sequence of the service (copied from the Wireshark trace, without WebSocket, TCP/IP, ... headers).

Note that you can use the Open Source Software of the PoC (Proof of Concept) to let client and server exchange real messages ... enjoy!

getLogicalDeviceDirectory

    { "request": {

            "associateId": "cp1",
            "invokeId": 1,
            "service": {
                "getLogicalDeviceDirectory": {
                    "ldName": "LD0"
                }}}}

    { "response": {
            "associateId": "cp1",
            "invokeId": 1,
            "service": {
                "getLogicalDeviceDirectory": {
                    "lnName": [
                        "LLN0",
                        "LPHD1",
                        "DWMX1",
                        "DGEN1",
                        "MMXU1"
                    ]}}}}

setDataValues

   {"request": {
            "associateId": "cp1",
            "invokeId": 56,
            "service": {
                "setDataValues": {
                    "ref": {
                        "ref": "LD0/LLN0.Mod.ctlModel",
                        "fc": "cf"
                    },
                    "dataAttrVal": [
                        {
                            "data": {
                                "enumerated": "2"
                           }} ]}} }

    {"response": {
            "associateId": "cp1",
            "invokeId": 56,
            "service": {
                "setDataValues": null
            }}}
    
Any question? Guess there is likely no need to ask, what this is ...

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.

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, June 6, 2026

Free ASN.1 Browser for IEC 61850-8-3 ASN.1 Module from RTI2 PoC

If you want to browse easily the ASN.1 message schema for the new project IEC 61850-8-3 (DSM) underway, check out this free browser: 


A preliminary asn.1 module for IEC 61850-8-3 (from PoC of RTI2) is available for download:

This is how it looks like:


and ...


The schema is very simple compared to MMS for IEC 61850-8-1.
Let us know if you have any question.

Thursday, June 4, 2026

Extended Video on IEC 61850-8-3 Available - Example Messages

 An extended version of the video on  

IEC 61850-8-3
Communication networks and systems for power utility automation –
Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS), JSON Encoding Rules, and WebSockets 

is available. I have added some five minutes ... total time is 23 minutes.

I have added mainly two examples of services for IEC 61850-8-1 (MMS) and IEC 61850-8-3 (DMS):


The figure above shows how a client can get the list of logical nodes from the server with MMS ... and with DMS:


Details can be watched in the video ... enjoy.

Saturday, May 16, 2026

IEC 61850 Series for Any Automation Domain using Electric Power (two Examples)

The standard series IEC 61850 is applicable for simple applications and huge systems. The standard is not restricted to a specific domain. Like electric power is everywhere. So could IEC 61850 be everywhere.

I have discussed this briefly in the context of a LinkedIn post.

Now it's time to discuss briefly two simple applications ... just looking at the two models ... without further explanations.

The German FNN Steuerbox

The Steuerbox is mainly providing schedules for the interface between the grid and the power user:


This model is defined for a special use-case: Steuern (remote control). No need for an engineering tool ... it is just a fixed model ...

The Netherlands RTI (Real-Time Interface) for power generation (> 1 MW)


... this is a fixed model with some details:

The RTI models and services are currently using IEC 61850-8-1 (MMS) communication (RTI 1). The RTI 2 will finally use the IEC 61850-8-3 (DMS) once it is specified. A Task Force has started to specify the new standard in May 2026.
The fixed models allow for a high level of interoperability. The central systems (representing the IEC 61850 clients) can communicate with and IED following these specifications. In the case of the FNN Steuerbox it has been proven that the client application could talk to all steuerboxes in the field without paying attention to which vendors device it is talking to.
REAL INTEROPPERABILITY !!

Wednesday, May 13, 2026

Why is there an Need for an Additional Service Mapping in IEC 61850 (IEC 61850-8-3)?

The two service mappings for IEC 61850 are IEC 61850-8-1 (MMS) and IEC 61850-8-2 (MMS/XML). The mapping IEC 61850-8-1 is in operation from the first days when IEC 61850 was implemented and used ... all over ... in millions of devices and thousands of systems. Ok ... perfect.

Why is there an need for an additional service mapping in IEC 61850 (IEC 61850-8-3)? 

Simply because of the complex and tricky mapping to MMS (Manufacturing Message Specification, ISO 9506). 

IEC 61850-8-3
Communication networks and systems for power utility automation –
Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS), JSON Encoding Rules, and WebSockets 

In order to explain details of the new approach to be used for the new work item proposal IEC 61850-8-3 I have produced a 17 minute video (updated version 2026-06-04, 23 minutes).

It is likely that this will become a major shift in the use of IEC 61850.

Enjoy!

Tuesday, March 24, 2026

The PAC World Magazine Reports From the 30 Year Anniversary of IEC 61850 in September 2025

The 30 year anniversary of IEC 61850 in September 2025 was a big success.

The report mentions me: "The presentations were bracketed by the first one from Karlheinz Schwarz about how all of this started in the past Millenium ..."

I am very thankful for the invitation by Dr. Fred Steinhauser (Omicron) to speak about the history ... 

Click HERE for the Report in the PACW.

Click HERE for more photos and a link to my "Millenium" presentation.

When browsing the Web, I see many more papers, reports, posts, ... on IEC 61850 for substations and for applications beyond substations.

More to come: With IEC 61850-8-3

Wednesday, March 18, 2026

New Work Item Proposal on IEC 61850-8-3 has been accepted by 95 % of the TC 57 National Committees

In December 2025 the NWIP (57/2866/NP - proposed project number: IEC 61850-8-3) was published for voting and comments:
https://blog.nettedautomation.com/2025/12/long-awaited-christmas-gift-for-smarter.html

Today we are happy that the NWIP has been approved by IEC - only one country disagreed in the voting process.

IEC 61850-8-3
Communication networks and systems for power utility automation –
Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS), JSON Encoding Rules, and WebSockets
 

The result of this work will very likely change the usability of IEC 61850 outside substations.

Stay tuned to follow the progress.

In order to explain details of the new approach to be used for the new work item proposal IEC 61850-8-3 I have produced a 17 minute video (2026-05-13).

Monday, March 16, 2026

IEC 61850: Work-around for MMS

Very interesting paper just published ... presenting a work-around for MMS ;-)

Integration Method for IEC 61850 into Legacy and Modern PLC Systems

I am a little bit surprised ... when I worked for Siemens (Karlsruhe) I published two papers in the year 1991 (35 years ago!) expecting that MMS could be implemented into a PLC:

Click HERE for the paper “Bridging MAP to Ethernet” [PDF, 720 KB, 1991]

Click HERE for the paper “Fieldbus standardization: Another way to go” [PDF, 720 KB, 1991].

Today we know that MMS could be integrated into PLCs ... 

Gateways work always - definitely.

The expected new work on IEC 61850-8-3 (another mapping than to MMS) would change the situation tremendously:

Communication networks and systems for power utility automation –
Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS),
JSON Encoding Rules, and WebSockets 

Click HERE for more information on the planned project.

Wednesday, February 18, 2026

IEC 61850: Realtime Interface Version 2.0 - Why This Matters

Netbeheer (the Netherlands organization of Distribution System Operator) published the Realtime Interface version 1.0 (RTI 1) in 2024.

The revised specification (named RTI 2) has been developed last year and proposed to IEC TC 57 as an additional solution for communication of IEC 61850 information (New Work Item Proposal IEC 61850-8-3).

The one page list of good reasons for the new solution 

The combination of IEC 61850 data model / services and WebSocket protocol
Why this matters

can be found here.

See also:
https://blog.nettedautomation.com/2025/12/long-awaited-christmas-gift-for-smarter.html

Monday, December 15, 2025

Long Awaited Christmas Gift For Smart(er) Grids - IEC 61850-8-3 is on its Way

In order to explain details of the new approach to be used for the new work item proposal IEC 61850-8-3 I have produced a 17 minute video. (2026-05-13)

IEC TC 57 just published a long awaited and crucial new work item proposal: 

57/2866/NP - proposed project number: 61850-8-3

Communication networks and systems for power utility automation –
Specific Communication Service Mapping (SCSM) –
Mapping to Direct Message Specification (DMS),
JSON Encoding Rules, and WebSockets 

Closing date for voting on the NP: 2026-03-06

"IEC 61850-8-3 Ed.1 defines the direct mapping of the client/server services of the ACSI (Abstract Communication Service Interface) defined in IEC 61850-7-2. Direct mapping means that for every abstract client/server service of the ACSI a concrete message schema (for the request and the response) is defined in ASN.1 (Abstract Syntax Notation One). ...

The encoding of the messages according to IEC 61850-8-3 is using the ASN.1 JER (JSON Encoding Rule, ISO/IEC 8825-8:2021). The messages are exchanged through WebSocket (RFC 6455, The WebSocket Protocol). WebSocket is a communication protocol that enables a persistent, full-duplex communication channel over a single TCP connection, allowing both the client and server to send data to each other at any time. This differs from the standard HTTP request-response model, making it ideal for real-time applications."

Please contact your national IEC TC 57 committee for a copy of the NP.

The main differences between IEC 61850-8-1/8-2 and 8-3 are shown in the following table:


and here:


Enjoy!

Click HERE for additional information that discusses the need for a modern messaging solution ...

I look forward to continuing the editing work of this new part of IEC 61850. This closes the circle of my contribution to communication protocols: starting in the mid 1980s with MMS (base for IEC 61850-8-1/8-2) and now (40+ years later) involved in a modern approach using web technologies ... Wow ...

This NP is the result of a Proof of Concept (PoC) initiated and managed by the Netherlands Distribution System Operators (Netbeheer). I played a little role in the implementation of this PoC. The PoC demonstrated the great benefit that can be harvested from the solution!

It is very likely that this part IEC 61850-8-3 (once it is finished) will accelerate the application of IEC 61850 outside the substation domain. I have discussed IEC 61850 outside of substations for many years ... Let me know what you think.

I wish you a merry Christmas and the best for the year 2026.

Thursday, October 9, 2025

The 30 Year Anniversary of IEC 61850 at Omicron in Klaus (Austria) on September 24, 2025, was a BIG success

The IEC 61850 Community has celebrated the 30 Year Anniversary at Omicron in Klaus (Austria) on September 24, 2025, was really a BIG success. Thanks to everybody that contributed to this success: Omicron employees, IEC TC 57 management, IEC TC 57 WG 10 and WG 19 members, many old friends from all-over. Some photos are already posted at LinkedIn ...
I was asked to tell the IEC 61850 Community the history of the standardization process starting in the 1980s with the fight Tokenbus versus Ethernet, MMS versus FMS, ... x versus y, ...
Click HERE to download my presentation [pdf, 6 MB] 
You can see me on the stage during my presentation:


The event was a great opportunity to meet people I have not met for years, e.g., George Schimmel (Tamarack, later TMW):


I guess I met George the first time in 1985 at the GM Techcenter in Warren (Michigan) ... MAP project.
René Troost and Alain Stuivenvolt from The Netherlands are so smart that they were able to move the stack of 7 layers of the Tower of Hanoi from one stick to another - well done.


On the group photo you find me in the first row/center:


I am still wondering that a lot of experts talk about IEC 61850 as a standard for substations! We are shaping more than the future of digital substations ... after the "Klaus Agreement" (see meeting minutes of the Task Force IEC 61850-8-3) we expect that IEC 61850 will be shaping the future of electric power systems far beyond substations as I discussed some 20 years ago: 
Check HERE a paper on this topic I published in the year 2008.

Some Hints on the use of Wireshark for IEC 61850-8-1 (MMS)

Please note the following preferences ... and have fun:

Version I used today:






Set the mms filter so see mms/IEC61850 only:





In case the MMS server is using a different port number: e.g., 12001 instead of standard port 102:

Analyze/Decode/ set other port number accordingly:












Check if presentation users context is correct:









Analyzing MMS/ASN.1/BER is sometimes tricky ... here is an example I figured out the other day ... if the length of a value is three (3) octets then the ASN.1 BER encoded message should indicate a length of 3 ... not 2 ... one single error in the length could damage the communication ...




Tuesday, March 3, 2020

IEC 61850 Edition 2.1 of Core Documents Published

The other day IEC TC 57 has published five more parts as Edition 2.1 - it took several years to get there! But finally it was successful.

I would call these Edition 2.1 documents simply the real Edition 2 documents.

First of all, what does Edition 2.1 mean?

The original edition 2 documents needed some corrections and updates. All crucial corrections et cetera have been documented in the Tissue Database (https://iec61850.tissue-db.com/default.mspx). The solutions provided on the Tissue Database have been used as input to the standardization process and led to amendments number 1 of the corresponding parts. These amendments have been commented and balloted officially by the members of TC 57. These amendments 1 are now the official documents that are amending the edition 2 documents (both are valid for the next years).

In order to make the "edition 2.1" more readable and understandable, there are other documents available: The consolidated parts 2.1 ... comprising the "old" stuff, the fixes and the extensions.




Consolidated Version of part 7-2: https://webstore.iec.ch/publication/66525 :



So: This consolidated version consists of the second edition (2010) and its amendment 1 (2020). Therefore, no need to order the amendment in addition to this publication.

Note: The first Tissues for edition 2.1 have already be posted, e.g., for part 7-2 Edition 2.1:



The following Previews for edition 2.1 consolidated versions are available:

Preview IEC 61850-6 Edition 2.1
Preview IEC 61850-7-2 Edition 2.1
Preview IEC 61850-7-3 Edition 2.1
Preview IEC 61850-7-4 Edition 2.1
Preview IEC 61850-8-1 Edition 2.1
Preview IEC 61850-9-2 Edition 2.1

Note: The name spaces (code components) for the edition 2.1 parts will be available soon - I hope:
Click HERE for the list of available name spaces (code components).

Sunday, October 6, 2019

IEC 61850 For Monitoring Data - Private or Standard?

One of the most crucial issues in the management of energy systems is: HOW TO share or exchange useful information generated by a myriad of sensors and applications needed by hundreds of applications?

Lets assume that lakes of information are generated every second. Usually this information is stored in silos of vendors specific solutions and communicated using one or more vendor specific communication solutions ... as shown in the following sketch drawn by our grandson Jan Oliver:



The expectations to apply IEC 61850 are high! BUT quite often vendors argue, that it is easier to use their private solutions - faster and saves time and costs! This may be true for the first phase of a project - but in the long run and in the view of the life time cost it may be completely opposite.

Three experts from Vattenfall DSO (Sweden; Vincent GLINIEWICZ, David EROL Anders JOHNSSON) have reported at the CIRED conference 2019-06 in Madrid (Spain) from an implementation of a pilot project using IEC 61850 and CIM  with the title:

LEVERAGING INDUSTRY STANDARDS TO BUILD AN ARCHITECTURE FOR ASSET MANAGEMENT AND PREDICTIVE MAINTENANCE

Excerpt from the paper:

"... However the data unfortunately currently often remain unused and unshared outside of the substation or specific silos for various reasons, some technical (e.g. cyber security, system incompatibility), some and organizational (e.g. vendor lock-in, siloed applications and organizations).
Additionally, with an increasing number of use cases requiring access to information, there is a growing number of information flows needed not only between data sources and central level applications but also between these central level applications. Without an IT architecture that allows reuse of information flows, there are legitimate concerns that the opportunities that digitalization promises might be delayed and costly or even worse, not be achievable.
As a result, Vattenfall Eldistribution sees a standard based integration approach as a cost-effective approach that seems to offer in the long run low integration costs and more importantly a greater flexibility, going from supplier specific integrations to a more generic approach. ...

We would also like to highlight some of the deviations from the standards that were observed during this pilot:

The pilot made use of a REST API towards the real time data historian (RTDH in fig. 2), although there was no mention of REST in the 61968-100 standard. One could however expect, given the increasing popularity and use of RESTful services in most industries, that the standard will soon follow and that the mention will be added in a further edition on the standard.
The gateway used in the pilot was a prototype base on a technical report (IEC TR 61850-90-2) [Using IEC 61850 for communication between substations and control centres] which is not yet a standard. This might explain why there doesn’t seem yet to be a complete and robust 61850-90-2 compliant product on offer in the market. Another alternative considered for the pilot gateway was the use of IEC 61850/MMS towards the substation and the use of web services (either RESTful+ JSON or SOAP) to communicate northbound instead of the IEC 61850/MMS used in the pilot. SOA has indeed a robust and well developed architecture for distributed computing, and this should be leveraged. There however did not seem to be any products available on the market. This alternative will be explored in a coming pilot. ..."

The paper concludes:

"Although the pilot was made for a primary substation, the widespread use of the IEC 61850 standards series make the results of this pilot not only applicable for primary substations, but potentially also secondary substations and microgrid.
Following the successful pilot, the next step is to look at how to fully implement and verify the concepts in a real substation and to secure production grade components where prototypes have been used as well as test the architecture through other smart grid use cases."

Click HERE for the full paper.

I have run an UCA/IEC 61850 pilot project with Anders Johnsson some 20 years (!) ago:

Two reports out of this pilot project and other discussions have been published in 2002:

Wind Power Communication
Verification report and recommendation

Click HERE for the Report.

Wind Power Communication - Design & Implementation 
of Test Environment for IEC61850/UCA2

Click HERE for the Report.

Enjoy the reports.

By the way: It took some 20 years to understand that the mapping of IEC 61850 models and communication protocols to MMS (ISO 9506) should be extended by a much easier and simpler mapping to JSON and, e.g., MQTT or http ...

It is not too late for such an additional standardized mapping ... e.g., as IEC 61850-8-3.

It may take another 10 years before this becomes true! Hope it will happen a bit earlier!

Further reading on the subject see discussion of IEC 61850-8-1 versus 8-2 (by 2024-02-25: 4074 visits of the post since July 2019).

Other people have similar ideas and published the following paper:

International Electronical Committee (IEC) 61850
Mapping with Constrained Application Protocol
(CoAP) in Smart Grids Based European
Telecommunications Standard Institute
Machine-to-Machine (M2M) Environment

Monday, March 25, 2019

New TC 57 CDVs For Public Comments Posted

IEC TC 57 has posted two new CDVs for public comments (for everybody to read the document for free):

57/2068/CDV
IEC 62351-3/AMD2 ED1: Amendment 2 - Power systems management and associated information exchange - Data and communications security -
Part 3: Communication network and system security - Profiles including TCP/IP 

57/2069/CDV (67 pages)
IEC 62351-8 ED1: Power systems management and associated information exchange - Data and communications security -
Part 8: Role-based access control 
This effort will transform the existing IEC TS 62351-8 ED1 from an IEC TS (Technical Specification) into an IS (International Standard) ED1
Excerpt from the Scope:
"The scope of this standard is to facilitate role-based access control (RBAC) for power system management. RBAC assigns human users, automated systems, and software applications (called “subjects” in this document) to specified “roles”, and restricts their access to only those resources, which the security policies identify as necessary for their roles.
As electric power systems become more automated and cyber security concerns become more prominent, it is becoming increasingly critical to ensure that access to data (read, write, control, etc.) is restricted. As in many aspects of security, RBAC is not just a technology; it is a way of running a business. RBAC is not a new concept; in fact, it is used by many operating systems to control access to system resources. Specifically, RBAC provides an alternative to the all-or-nothing super-user model in which all subjects have access to all data, including control commands. ..."
Be aware that RBAC is required in systems where multiple clients (in the sense of, e.g., IEC 61850) need to access a server. One use case is where multiple power market participants want to manage a power resource. 

Monday, March 18, 2019

IEC TC 57 Just Published IEC 61850-10-3 on Functional Testing of IEC 61850 Based Systems

IEC TC 57 published 79 page document 57/2082/DC:

IEC TR 61850-10-3 – Communication networks and systems for power utility automation –
Part 10-3: Functional testing of IEC 61850 based systems

Excerpt:
The growing success of the IEC 61850 series calls for guidelines for testing of substations implementing this standard. This technical report aims at producing a practical guide for protection, automation and control (PAC) engineers on best practise for testing of IEC 61850 Edition 2 with Tissues/Ed. 2.1 based devices and systems.
Since the release of the first edition of the IEC 61850 standard in 2002-2005 thousands of substations have been built making use of the new multi-part standard. Most of those systems are more integrated and complex than the previously deployed, making use of multi-function capable IEDs and the rich feature set of IEC 61850. Especially the sending and receiving of protection trips via GOOSE messaging control commands/indications, monitoring and time synchronisation information over the same shared equipment or network will need to drive changes to existing test methods and practices as many of the traditional test boundaries have changed.
Despite the large number of commissioned IEC 61850 substations considerable uncertainty among end-users (system integrators and power utilities) regarding the correct testing procedures still exists. Devices implemented according to the first edition of the standard also utilized a limited part of the test related functionality in the standard. Much of the functionality included in IEC 61850 to allow efficient, functional oriented testing has been clarified and extended in the second edition of IEC 61850 parts, 6, 7-1 to 7-4, 8-1 and 9-2. Therefore, there is a need to help the industry by describing the methods and principles for testing the IEC 61850 based applications.
This Technical Report provides insight into the changing requirements and practice of testing following the introduction of IEC 61850 based devices and systems. One example is the disappearance of so-called ‘hardwired’ connections between substation automation devices.
These connections are replaced by communication networks and this means that traditional simulation and isolation of signals for the purpose of testing is no longer possible.

Comments to this draft are due by 2019-04-19