Showing posts with label JSON. Show all posts
Showing posts with label JSON. Show all posts

Friday, November 6, 2026

The Demo of the IEC 61850-8-3 (WebSocket) is now Ready for You to Explore

First: The IEC 61850-8-3 Committee Draft (57/2980/CD)

Specific Communication Service Mapping (SCSM) – Mapping to Direct Message Specification (DMS), JSON Encoding Rules, and WebSockets

was out for comments in September and October 2026. The comments are mainly editorial ... the comments show high support of the draft ... no critical comment!

The Demo of the IEC 61850-8-3 (WebSocket, as an alternative to MMS) solution provided in the context of the Netbeheer's RTI 2 (Real-Time Interface 2) PoC is now Ready for You to Explore!

Here is the announcement I received today:

Hi everyone,
An exciting milestone to share!
I'm happy to announce that the RTI demo has officially been merged into the main branch of the Netbeheer Nederland iec61850-websocket repository!
But that's not all! To make deploying and exploring the demo as easy as possible, we've also created a dedicated repository:
With this repository, you can set up a fully functional demo environment locally using only Docker — no development environment required!
This makes the RTI demo much more accessible, allowing everyone to explore and experiment with it independently.
What can you expect?
Once the demo is up and running, you'll see an environment featuring:

​
Explore IEC 61850 operations yourself
Navigate to the Traffic menu to explore the IEC 61850 communication and operations in action.
Here, you can:

Currently, one playbook is included, providing an easy and interactive way to experience how the RTI demo works.
And this is just the beginning! The demo already includes many more features (like data-models, Oauth2-security) and capabilities than we can cover in this single email. I encourage everyone to explore the environment and discover what's possible.
What's next? Bringing the demo into the physical world!
Over the coming month, we'll be putting the finishing touches on the physical part of the demo, built around Raspberry Pis.
This will take us beyond a fully virtual demonstration, allowing IEC 61850 operations to interact with actual physical devices and making the results directly visible in the real world.
Curious about what such an integration might look like? Here's a sneak peek: dr-ssd1306 – Raspberry Pi Demand Response Demo
A big thank you to everyone involved!
A special thanks to everyone who contributed to making this milestone possible! Whether through development, testing, reviewing, sharing ideas, or providing valuable feedback, your efforts and collaboration have helped bring the RTI demo to where it is today.
Give it a try!
With this milestone, we've not only integrated the RTI demo into the main development branch but also significantly lowered the barrier to getting started.
Fire up Docker, explore the demo, and experience firsthand how secure IEC 61850 communication works between a System Operator and Customers as Flexibility Service Providers!
Enjoy exploring! Feedback, ideas, and suggestions for future improvements are, of course, very welcome.

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 ...

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.

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.

Saturday, March 29, 2025

40 Years Ago I Started Contributing To The MAP/MMS Standardization In Detroit (MI)

I have contributed to the MAP/MMS Standardization (Manufacturing Automation Protocols/Manufacturing Message Specification) from the very beginning. I was working for Siemens in the group dealing with communication solutions for process control and factory automation. In February 1985 I attended the first time a meeting of the MAP project at the GM TechCenter in Warren (Michigan, USA). As you can see, the first day was a very cold day (1985-02-14) with a lot of fresh snow:

I looked still young (40 years younger than today) ... 32 years old and father of four children.


The approach of MAP/MMS was very new ... even today a lot of people have difficulties with MMS ... especially because of using ASN.1 BER as the encoding notation for all messages exchanged according to IEC 61850 - Client/Server and Publisher/Subscriber messages!!

In 1993 I got also involved in the new IEC TC 57 project TASE.2 (Telecontrol Application Service Element 2) based on MMS ... called ICCP (Intercontrol Center Communication Protocol):

I attended the following meeting in Loveland (Colorado, USA):

30 years ago (March 1995) the IEC TC 57 decided to start a new project: IEC 61850 based on the EPRI UCA 2.0 Specification ... also using MMS/ASN.1/BER ... I got involved in UCA and IEC 61850 starting with the second IEC TC 57 WG 10 meeting end of 1995.

Many people in the electrical power world have complained since then that MMS/ASN.1/BER is toooo ... too much of ... and as a result many have departed from the approach.

I have suggested many times to use web services ... JSON encoding instead of ASN.1/BER and XML ... most people ignored the use of web services ... I guess it will come in the near future.

In many of the following standardization groups I have supported modern communication approaches ... in some cases it took some time ... or still is awaiting for a push:




Monday, February 26, 2024

Mapping of IEC 61850 Models and Information Exchange Services to JSON, HTTP, and MQTT

After I published two sketch videos on IEC 61850 information exchange services and the mapping to MMS, I discuss simple interface options for the last meters between a device that implements the role of IEC 61850 server, GOOSE publisher, and GOOSE subscriber, and the underlying huge world of a myriad of other controllers.

The standard series IEC 61850 and IEC 61400-25 (Wind Power Plants) provide a comprehensive set of standardized information or device models (Logical Nodes, Data Objects, Data Attributes, ...) for a wide range of use cases in the electric power domain (protection, automation, supervision, monitoring, control, ...) and for general applications beyond the electrical world. By the way, tell me where electricity is not a crucial resource in factories, buildings, petrochemical plants, homes, ... it is all over ... required 24/7. These series also comprise information exchange mechanisms like Reporting, Logging, Control, GOOSE, Sampled Values, ... mapped mainly to MMS in IEC 61850-8-1 ... other mappings like mappings to XML and XMPP in IEC 61850-8-2 or MMS, Web Services, IEC 60870-5-104, DNP3, OPC XML DA, ... in IEC 61400-25-4. The most crucial part of IEC 61850 and IEC 61400-25 is the System Configuration Language (SCL, IEC 61850-6).

Many applications use only a very small set of models (a few measurements, control signals, and status signals), a small set of information exchange services, and a simple subset of SCL. Critic comes from experts of various domains: Why do I need to have a complex and comprehensive IEC 61850 stack to implement a simple subset of these standard series? Is there another solution? The wind power plant people developing and maintaining IEC 61400-25 believing that five (5) mappings would help in this regard - really? So, the discussion is still going on. 

A very simple solution has been implemented in various projects: Notation of a subset of the information models and the payload of the messages in JSON. The exchange services could be mapped to various transport mechanisms like MQTT or HTTP ...

This approach would KEEP the models as they are - NO mapping required, just another notation (JSON instead of MMS named Variables etc.). Even SCL could be used.

Whenever there is a need to communicate from a device that plays the role of an IEC 61850 server, GOOSE publisher, GOOSE subscriber, to an underlying (likely simple) device (for the last meters) the decision usually is to use some other communication stacks from a set of 100+ solutions like CAN, Modbus, many fieldbusses, EEBUS, Sunspec, ... and private digital solutions, or even wires only ...

Any of these need to MAP from one standard to another standard, e.g., map MyIED/myMMXU1.Hz.mag.f (measurement of frequency) to register 2246 in one application and to 9817 in another ... hm, that is feasible BUT means a lot of configuration and documentation ... outside the definitions and tools provided by IEC 61850. 

A more reasonable approach would be to use JSON, e.g., to define a DataSet (semantically equivalent to IEC 61850 and MMS) and the report message payload as shown in the figure below:













Please check a couple of blog posts published a few years ago for more details and discussions:

https://blog.nettedautomation.com/2019/07/iec-61850-8-2-versus-iec-61850-8-1.html

https://blog.nettedautomation.com/search?q=mqtt

https://blog.nettedautomation.com/2019/10/iec-61850-for-monitoring-data-private.html

Unfortunately the Beck IPC com.tom Web PLCs with support of IEC 61850, ... disappeared ...
Please let me know your opinion ...

Friday, November 1, 2019

IEC TC 57 WG19 proposes CIM Profiles to JSON schema Mapping

IEC TC 57 WG is discussing the use of JSON for transferring message payload

DRAFT 62361-104:
POWER SYSTEMS MANAGEMENT AND ASSOCIATED INFORMATION
EXCHANGE – INTEROPERABILITY IN THE LONG TERM –

Part 104: CIM Profiles to JSON schema Mapping

The introduction says:

"This standard is one of the IEC 62361 series which define standards that may be used by all
Working Groups within TC57. These standards address areas of interest that impact multiple
standards and provide consistency for implementations.
This part 104 describes a mapping from CIM profiles to IETF JSON schemas and defines the
rules that CIM JSON message payloads must adhere to.
The principle objective of this part 104 is to facilitate the exchange of information in the form of
JSON documents whose semantics are defined by the IEC CIM and whose syntax is defined by
an IETF JSON schema. ..."

JSON is applicable for encoding of CIM (IEC 61968/70) message payload and - as I believe - also for IEC 61850 message payload!

By the way: The post on "IEC 61850-8-2 Versus IEC 61850-8-1" discussing the use of JSON in addition to MMS/ASN.1/BER and MMS/ASN.1/XER has been visited 2,000 times since July 5, 2019 --> or 16 times per day.

Click HERE for additional discussion on the use of JSON ...

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

Wednesday, August 28, 2019

Why Is It So Easy To Map IEC 61850 Signals to JSON Objects?

IEC 61850 defines Device Models for the exchange of information between any two or more entities. The Models are structured as unique branches of a tree.That means:

Each path from the Device (Root) to 
any node or leave of the trees is unique

The signals are composed of an access reference (LDName/LNName.DOI. ...) and the value that corresponds with the path.

Example of two leaves:
LDName/Tran1STMP1.Tmp.mag.f = 23.5 (Temperature value)
LDName/Tran1STMP1.Tmp.units.SIUnit = °C (Temperature engineering units)

These are key-value pairs that could easily map to JSON Objects:

"LDName/Tran1STMP1.Tmp.mag.f " : "23.5"
"LDName/Tran1STMP1.Tmp.units.SIUnit" : °C

These JSON objects are

  • Light-weight
  • Language independent
  • Easy to process with Python, ...
  • Text based and human readable 
  • JSON Schemas could support automatic (syntax and semantic) checks
  • JSON is supported by many controllers
The controller of our PV inverter from Fronius has an http/JSON interface. The following request (lines 1-3) returns many common inverter data (line 21ff):



Lesson learned: Controller in inverter could easily provide an http/JSON interface.

The Device Model is a virtual model that could be configured using the SCL (System Configuration Language, IEC 61850-6). The Device Model is implemented in an IED and could be accessed to get the self-description, read, write, send/receive reports, publish/subscribe, ...

An IEC 61850 Server hosted by an IED could easily map the model to JSON objects that may be communicated with MQTT, HTTP, ...

The mapping to JSON is quite easy. It could be implemented by a simple automatic process that parses the model (SCL/XML), searches for the paths and concatenates the names from the root to the leaves to get the reference! AND: the mapping preserves the semantic - the meaning represented by the path name.

The mappings of IEC 61850 Models to IEC 60870-5-104, DNP3 or Modbus would result in messages that have lost the semantic of the signals. These solutions have mainly numbers as reference - these numbers have no meaning in the communication.