Showing posts with label XML. Show all posts
Showing posts with label XML. Show all posts

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

Wednesday, May 21, 2025

The German FNN Steuerbox Version 1.4 (official) is available for just 39 Euro!

The officially published FNN Steuerbox specification (in German only) is available for immediate download (of a personalized pdf) ... if you pay 39 Euro ... really affordable!

The Steuerbox uses a subset of IEC 61850 models and services ... there are three documents related to the Steuerbox available:

https://www.vde-verlag.de/schnellsuche/?suchbegriff=lastenheft+steuerbox 


The document contains a link (on the last page) to additional material: ICD File, certificate and settings XSDs ... WOW ...


This is one of the great news: to get the material for almost free!

In the History element of the ICD file you can see that my granddaughter Jana and I have been involved ...  

Enjoy

Thursday, November 18, 2021

Four Additional Light Namespace Documents For IEC 61850 Series Are Available For Free Access

 Please note that the following four namespace documents have been published the other day:


Click HERE to access these four and the other 22 name space documents.

  1. IEC 61850-90-9: Object models for electrical energy storage
  2. IEC 61850-90-4: Network engineering guidelines for substations
  3. IEC 61850-90-11: Methodologies for modelling of logics for IEC 61850 based applications
  4. IEC 61850-7-420: Communications systems for distributed energy resources (DER) - Logical nodes

Enjoy!

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

Saturday, July 14, 2018

IEC TC 57 just published FDIS IEC 61850-8-2 (Mapping to XMPP)


IEC TC 57 just published FDIS IEC 61850-8-2 (Mapping to XMPP) - 253 pages !

(57/2020/FDIS)

Voting ends: 2018-08-24

Part 8-2: Specific communication service mapping (SCSM)
– Mapping to Extensible Messaging Presence Protocol (XMPP)

The long wait for a second SCSM is over!

The new mapping of IEC 61850 describes a specific communication service mapping
(SCSM) over the Extensible Messaging and Presence Protocol (XMPP), providing detailed
information on how to create and exchange concrete communication messages that
implement abstract services and models specified in IEC 61850-7-4, IEC 61850-7-3, and
IEC 61850-7-2.

Note that the MMS messages (defined using ASN.1) are used in IEC 61850-8-1 AND -8-2 ! The only crucial difference between the two message and model mappings (in 8-1 and 8-2) is this:

8-1 uses BER (Basic Encoding Rule) for the messages on the wire, while 8-2 uses (XER (XML Encoding Rule). The complexity of the MMS messages is the same in both mappings - because the structure and how to build messages and how to carry the 7-2 services and 7-x models are the same!

The challenges to implement 8-2 message mapping are more or less the same as with 8-1. Note that the messages in XER are far longer than with BER.

There is - of course - a difference between the two: The transport of messages in 8-2 uses XMPP.

Some may argue, that there are more tools available for XER than for BER. Ok.

IEC 61850-8-2 is far away from something simple and easy to implement and use - especially when you need only a few simple services and models.


Saturday, October 28, 2017

Wow: IEC Goes XML and PSON

IEC provides access to crucial standardized information by modern web technologies:
The content of the Electropedia (The World's Online Electrotechnical Vocabulary) is now made accessible by XML documents and PSON (REST) through the opendata gateway.
“A json version of all subject areas (or IEV parts) in the Electropedia is available by calling the REST endpoint: “ https://opendata-api.iec.ch/v1/opendata/areas/ 



I expect that the PSON option will be made available for the complete vocabulary soon.
Enjoy!
More to come!

Sunday, September 17, 2017

First Document of Series IEC 61850 Published as Edition 2.1 FDIS

IEC TC 57 has just published the FDIS of IEC 61850-6/AMD1 ED2:

Amendment 1 – Communication networks and systems for power utility automation –
Part 6: Configuration description language for communication in power utility automation systems related to IEDs

The voting ends: 2017-10-27

Amendment 1 means finally Part 6 Edition 2.1:

The present FDIS reflects amendment 1 to IEC 61850-6 Ed. 2. TC 57 WG 10 has also developed a so-called consolidated edition 2.1 based on the present amendment and the existing Edition 2. The consolidated edition is circulated in parallel under reference 57/1919/INF, so that national committees can see the implementation of the amendment in the existing edition.
Once the present FDIS is approved, the consolidated edition will be published together with the amendment under reference IEC 61850-6 Ed. 2.1.

Machine processable Schema available!!

Note that the Schemata for Edition 1 and 2 of part 6 could be downloaded from the IEC Website:



The availability of the machine readable schemata is a very great progress in getting IEC 61850 applied in more and new application domains. More to come.

Congratulation!

Friday, May 5, 2017

IEC TC 57 published Draft for Machine-Processable Models

IEC TC 57 has just published (57/1870/CD) the first draft improving the applicability of IEC 61850:

Communication networks and systems for power utility automation –
Part 7-7: Basic communication structure –
Machine-processable format of IEC 61850-related data models for tools

This Technical Specification of IEC 61850 specifies a way to model the code components of IEC 61850 data model (e.g., the tables describing logical nodes, common data classes, structured data attributes, and enumerations) in an XML format that can be imported and interpreted by tools. The following main use cases shall be supported:

  • Generation of SCL data type templates for system specification or ICD files. One sub-use case is the generation of LNodeTypes for replacing GGIO.
  • Validation of SCL data type templates.
  • Definition of private extensions by following the rules of the standard.
  • Adapting rapidly the whole engineering chain as soon as a new version of IEC 61850 data model (an addendum, a corrigenda or a Tissue) affects the content of the standard.
  • Provide tool-neutral textual help to users of tools on the data model contents.
  • Supporting multi-language publication, i.e., enabling the expression of the data model in different languages, through a machine processable format.

The purpose of this proposal is limited to the publication of the XML format which should support the data model part of any IEC 61850 related standard. The publication of code components themselves will be part of the related IEC 61850 part.

Comments are expected by 2017-07-28.

This a major step forward. Especially because the "cleaned-up" models of all parts to be published as Edition 2.1 of the corresponding parts could be understood as the real Edition 2 of the parts that contain models!

Thursday, March 23, 2017

ASCII Text, XML, SCL, Models, and Errors All Over

IEC 61850 makes use of ASCII text, XML, SCL, and comprehensive Information Models. At any level you may find errors. How to figure out, e.g., if a DataSet member references a FCDA that is not available in any Logical Node model?

I run through the following inconsistency:
There is a DOType "SPG_0" defined that contains a fc="SP"(bottom).
The DO "SetPt19" uses this DOType with fc="SP" (above)
The marked DataSet member FCDA refers to DO "SetPt19" with fc="ST".



This reference is not correct - there is no DO "SetPt19" with fc="ST" !! How does a stack react when it has to parse such a wrong model? Hmm!

It took me some time to figure out what the issue was when I loaded the file onto a HMS Gateway with WEB-PLC:



In the meantime I have checked the wrong file with six (well known) IEC 61850 tools - NONE of them complained about this inconsistency.
The SystemCorp stack complained, because it was not able to find the referenced object to implement the model! WOW!

This example confirms what I always tell people in my courses: Develop your own simple tools for finding errors in the "ASCII Text" - it is just a simple search you need ... I am not saying that the many tools on the market are useless!! No way! But many simple checks could be done with simple tools. Even tool developer may not have a clue what kind of checks would be helpful.
In this case it would have been quite easy to check (ASCII search and comparison) all members of all DataSets and check in the Logical Node models if there is a DataObject that matches with the reference in the DataSet. Such a ASCII text search would have resulted in something like: Did not find an fc="ST" for the object "SetPt19".

It is that easy! Believe me.

My experiences with this and many other issues are one of the core topics in my courses.
Click HERE for courses in German in Karlsruhe/Germany.

Tuesday, March 21, 2017

BIG Data, Smart Data, or Fake Data

Do you trust the process data you rely on for decisions to be made for many different applications? Hmm! It may be - I hope you could trust the data.

BBC just published a crucial paper with the title:
"How fake data could lead to failed crops and other woes"

Click HERE for the paper.

I guess this has been said many times - not yet by everybody.
What is most important: You have to do something to protect the data you (or your device) produce - so that the receiver can trust that the data are not FAKE data.

Maybe we extend the quality details defined in IEC 61850-7-3:
overflow
outOfRange
badReference
oscillatory
failure
oldData
inconsistent
inaccurate
fake (extended)

I am kidding ... sure.

Do you know that IEC 61850 does not define any measure to protect the data while they are on rest or travel? It's true - no crucial definitions on security. This is intended.
The series IEC 62351 defines many very crucial measures and describes how to apply them to power systems and IEC 61850 refers to IEC 62351:
IEC/TS 62351 - Power systems management and associated information exchange - Data and communications security:
Part 1: Introduction to security issues
Part 2: Glossary of terms
Part 3: Profiles Including TCP/IP
Part 4: Security for profiles including MMS
Part 5: Security for IEC 60870-5 and derivatives
Part 6: Security for IEC 61850 profiles
Part 7: Objects for Network Management
Part 8: Role-Based Access Control
Part 9: Key Management
Part 10: Security Architecture
Part 11: Security for XML Files
Part 12: Resilience and Security Recommendations for Power Systems with DER
Part 13: Guidelines on what security topics should be covered in standards and specifications

Check an overview from part 13:



Click HERE for the source of published parts of IEC 62351.
An excellent source of hints in German can be found at GAI NetConsult (Berlin).

You should do more than buying and reading the various parts of IEC 62351 - You should implement many of the crucial measures defined in these documents,

Good luck!

Thursday, August 25, 2016

How to Exchange a Voltage Measurement with IEC 61850?

As discussed before you will find a reasonable example to learn the benefits of applying IEC 61850.
Let's look at a voltage measurement:



According to IEC Electropedia we find many names for the same semantic: voltage, Spannung, spenning, ... Ok. These help humans to understand what we are talking about. But what about machines (controllers, SCADA systems, ..)?
They have to use a data type (int16, int32, float32, ...) and a reference (address ...) for a specific protocol like Modbus. Each vendor will likely use different types and addresses.
What's about the scale in applications that use integer? Is the scale known when you read the value of a voltage? Do you know the offset or the multiplier (V, kV, mV, ...)?
How do you know where the measurement is taken in the electrical system (location in the single line diagram)?
Answers to these questions may be found in a set of documents sitting on a shelf or on someones computer - hard to find out if the owner is on vacation.
With IEC 61850 we have a model that could be implemented so that all these details are always accessible online from each device that is a source of measurements:



Phase A voltage has a standard name "MMXU.PhV.phsA" with the value, quality, timestamp, units, and scale. These names are used all over in any IEC 61850 device.

IEC 61850 services allow to retrieve the MMXU model and read the values:



The device has all information to interpret the voltage value for phase A.

Finally we need to know where the value is measured in the single line diagram. IEC 61850-6 (SCL) provides the solution specified as an SCL file (simplified SSD - Substation Specification Description):


The above voltage could be designated as follows:
MySub_400kV_3A63_BayFunction_ABC/ACMMXU1.PhV.phsA

The value is located in the device "BayController". The device is communication wise identified by an IP Address.

This information really exposes all information needed to interpret a measurement. 
Note that this name needs not to be communicated when the value is reported cyclically or issued by a limit change.The report message could only carry the value, quality and timestamp.
The SCL file has all information to configure the whole system and the devices.
Any question?
Hope you have learned this: IEC 61850 goes very far beyond a protocol! We only need the protocol when we retrieve the selfdescription or read out or report the values.
And: the nice thing is that any device that implements the standard uses the same model, configuration, and services. What else do we need?

If we would apply just a protocol like Modbus then most of the information exposed (directly from the device) through the standard IEC 61850 would have to be stored in paper docs or excel sheets ... 

Saturday, July 23, 2016

IEC TC 57 Published FDIS IEC 62351-11 Security for XML Documents

Have you ever seen a multi MegaByte XML file used for system or device configurations, COMTRADE, COMFEDE, or other purposes? I have big SCL files that represent real substation specifications. What happens if one (1) single character is removed or changed by somebody ...? A change of a single character can have very severe consequences!
In order to secure XML Files in the context of IEC and other standards organizations, IEC TC 57 just published the document:
57/1753/FDIS: Power systems management and associated information exchange – Data and communications security – IEC 62351-11: Security for XML Documents

Voting closes 2016-09-02

IEC 62351-11 specifies schema, procedures, and algorithms for securing XML documents that are used within the scope of the IEC as well as documents in other domains (e.g. IEEE, proprietary, etc.). This part is intended to be referenced by standards if secure exchanges are required, unless there is an agreement between parties in order to use other recognized secure exchange mechanisms. It utilizes well-known W3C standards for XML document security and provides profiling of these standards and additional extensions.

Wednesday, February 3, 2016

XML Documents and Pretty Print with Notepad++

Dear All,

I guess you have seen this kind of XML documents quite often in conjunction with SCL Documents:


One way is to use the online tool "Pretty Print".

There is a more convenient way: Use the "Pretty Print" Plugin tool that comes with Notepad++ (you have to install it with the Plugin Manager):


This will result in a Pretty Clean XML Document:


Wow!
Enjoy the plugin!

Mapping of IEC 61850-7-x to XMPP: Nice Paper in PACWorld Magazine

The XMPP technology (Extensible Messaging and Presence Protocol) has been selected as the communication solution to address the Smart Grid specific challenges and use cases, which deviate from a typical substation automation use case.

The additional mapping will be published as IEC 61850-8-2.

A nice overview can be found in a paper published recently in the PACWorld magazine:

Click HERE for the full paper.

Note that from a message encoding point of view the MMS-ASN.1-BER messages are mapped directly to ASN.1-XER coded messages. The ASN.1 Tag numbers are mapped to XML Element names. The whole message schema is the same in both mappings.

Tuesday, August 4, 2015

SCL Schema Accessibility in the near future

The SCL schema is published as part of the delivery of edition 1 and edition 2 of part 6. The publication of a Technical Corrigendum to IEC 61850-6 Ed. 1 and Ed. 2 is under way.

To provide an easier way to retrieve the latest version of the Schema a new possibility to access the Schema from the IEC Website is proposed in the document (57/1604/DC): Latest version of SCL schema and planned publication of a Technical Corrigendum to IEC 61850-6 Ed. 1 and Ed. 2.

This process is already proposed for the first corrigenda of part 6 and from Edition 2.1 onwards.

Please note: Currently the following valid schema files are currently used for conformance testing of IEC 61850:

- For Edition 1 of IEC 61850-6: SCL 1.7
- For Edition 2 of IEC 61850-6: SCL.2007B

Thursday, June 11, 2015

XMPP - IEC 61850-8-2 Defines Additional Communication Mapping

IEC TC 57 has published a first draft for an additional mapping of IEC 61850 information models and communication messages.

IEC 61850-8-2 (57/1583/CD):
Communication networks and systems for power utility automation - Part 8-2: Specific Communication Service Mapping (SCSM) – Mapping to Extensible Messaging Presence Protocol (XMPP)

Closing date for comments is 2015-09-11

The new mapping defines (relies on) the following definitions:

Service mapping (unchanged)
The abstract (client-server) services of IEC 61850-7-2 are mapped to MMS as defined in the existing IEC 61850-8-1 Ed2.

Message Encoding (new concrete encoding)
The encoding of the messages uses ASN.1 XER (XML encoding rule) – in addition to ASN.1 BER according to IEC 61850-8-1 Ed2. The encoding defines an XML schema – contained in the draft.

Model mapping (unchanged)
As in IEC 61850-8-1 Ed2. This applies to the flattening of the object identification and adding Functional Constraint (FC=ST or MX) in the path name and using “$” for “.”:

Bay5_MMXU1$MX$Hz$mag$i

Underlying Transport (new T-Profile)
The transport (exchange) of the XER encoded messages uses a new approach: using XMPP.

This new transport mechanism and encoding will be used between all kinds of utility Distributed Energy Resource devices and related power management systems, over any communication infrastructure including public networks.

The coming IEC 61850-8-2 can be understood as an (encoding and transport) extension of the existing IEC 61850-8-1.

It is very crucial that most parts of implementations and tools can be re-used! Re-Use is one of the basic approaches used in IEC 61850! Don’t start always from scratch – use what is available and add something.

So, to read the frequency of Bay5 is almost the same .. using the reference
“Bay5_MMXU1$MX$Hz$mag$i”
encoded in ASN.1 BER (IEC 61850-8-1) and in ASN.1 XER (IEC 61850-8-2).

See also example of encoding.

A second document explains the needs and background for an additional mapping:

IEC 61850-80-3 TR (57/1584/DTR):
Communication networks and systems for power utility automation -
Part 80-3: Mapping to Web protocols – Requirements and technical choices

It describes the requirements and the technical principles for a new specific communication service mapping (SCSM) based on Web Protocols.
For more information about the candidate technologies which have been analyzed but not selected as well as about the selection process used for choosing the technology, national committees are invited to consult document 57/1585/INF which is circulated in parallel:

Accompanying document to 57/1584/DTR, Proposed IEC TR 61850-80-3

It mainly describes the technical solutions which have been investigated but finally not selected for the SCSM of the IEC 61850 based on Web Protocols.

  1. IEC 61400-25-4 Annex A (Web services)
  2. DPWS (Devices Profile for Web Services)
  3. REST (Representational State Transfer)
  4. XML messaging over Websocket
  5. ACSI XML Messaging
  6. OPC UA

The finally chosen solution  “MMS XER payload over XMPP as transport” was recognized after several years of work as the preferred solution – especially from a fast time-to-market point of view.

What does XMPP provide?

XMPP (RFC 6120) is a middleware messaging and presence protocol supporting decentralized architectures and provides:

  • Registering resources in publicly reachable servers
  • Resolving resources based on names
  • Security (authentication, integrity, confidentiality) for the communication with the XMPP server

This fits well to the information models defined in IEC 61850.

Friday, June 5, 2015

IEC 62351-11: Draft on Securing XML files

XML (a notation for structured documents) is used in many standards published by IEC TC 57 (Power systems management and associated information exchange). IEC 61850-6 (SCL) is one of these parts that rely on XML and XML schema.

A small change in an SCL file may have a crucial impact of the content of the whole file.  There is a need to secure such files.

IEC TC 57 just published the first CDV:

IEC 62351-11 Ed.1 (57/1562/CDV)

Power systems management and associated information exchange - Data and communications security -
Part 11: Security for XML files

The 62351-11 extensions provide the capability to provide:

  • Header information: the header contains information relevant to the creation of the secured document such as the Date and Time of the when the IEC 62351-11 document was created.
  • A choice of encapsulating the original XML document in an encrypted (Encrypted) or non-encrypted (nonEncrypted) format. If encryption is chosen, there is a mechanism provided to express the information required to actually perform encryption in an interoperable manner (EncryptionInfo).
  • AccessControl: a mechanism to express access control information regarding information contained in the original XML document.
  • Body: is used to contain the original XML document that is being encapsulated.
  • Signature: a signature that can be used for the purposes of authentication and tamper detection.

What do you think about security? It is important! How many time and money have you and your colleagues or your management spent for making systems more secure? One Euro or 1000 Euro?

When it comes to costs – then people are behaving different.

Be more serious about security.

Tuesday, April 28, 2015

Draft IEC 61850-8-2 SCSM – Mapping to XER and XMPP

Some 20 years after the first draft IEC 61850-8-2 SCSM (Mapping to Profibus FMS) we could expect the real IEC 61850-8-2 to be available by end of 2015.

The draft 8-2 provides an additional mapping of the messages of MMS by XER (XML Encoding Rule) and XMPP.

The MMS messages for IEC 61850-8-2 (above TCP/TLS/XMPP) are just differently encoded as in IEC 61850-8-1, as can be seen by the following example:

image

ASN.1 BER uses a binary encoding that produces less overhead compared to XER. But there will be many benefits provided by IEC 61850-8-2.

According to a presentation by Siemens during the Hanover Fair 2015, these are the main conclusions:

  1. It provides a secure and powerful communication for public networks considering end-to-middle and end-to-end security relations
  2. IEC 61850-8-2 is intended to use for power management and demand response of DER (distributed energy resources)
  3. In 2015 the IEC TC57 working group WG17 will finalize and publish this new specification

Click HERE for the full presentation [pdf, 3 MB]

Monday, August 4, 2014

MMS & ASN.1 & XER & XMPP selected as the second SCSM of IEC 61850

The second SCSM for the ACSI Client-Server information exchange service models will be the mapping of the ACSI service models to MMS ASN.1 XER and XMPP. IEC TC 57 just released the 122 page document 57/1497/DC:

Draft IEC 61850-80-3 TR, Communication networks and systems for power utility automation – Part 80-
3: Mapping to web protocols – Requirement analysis and technology assessment

The document mainly lists the crucial needs and why the mapping to “MMS ASN.1 XER and XMPP” has been chosen to be published as IEC 61850-8-2 soon.

Chapter 7 presents the future SCSM 8-2, including an overview of the main selected technology: XMPP.

The following goals have been particularly considered for the definition of this SCSM:

  • Identify a single profile supporting all the services required by the domains and defined today in ACSI.
  • Cover the full life cycle of a IEC 61850 system, in collaboration with the System Management work in WG10 (from configuration, through conformance testing, down to maintenance). For this purpose, the present document may recommend some changes in other parts of IEC 61850 like part 6, part 10, etc.
  • Deploy cyber-security to ensure a secure environment (in conjunction with IEC TC 57 WG 15 work).
  • Propose rules for cohabitation with other mappings such as IEC 61850-8-1 and IEC 61850-9-2, and possibly recommend communication profiles depending on specific application context (pole-top equipment, inside DER, connection of DER, …).

Check with your national IEC TC 57 mirror committee for a copy of the above mentioned document.

Congratulation for the tremendous success of the web service mapping team!!! Great work!

That means: IEC 61850 will be the preferred solution in substations and many applications outside!!

Tuesday, May 13, 2014

Web Services for IEC 61850: MMS/XER over XMPP?

Some 18 months ago I have reported on a standardization project within IEC TC 57 defining web services as a second SCSM (Specific Communication Service Mapping) for IEC 61850. In the meantime it seems very likely that a mapping to XMPP (Extensible Messaging and Presence Protocol) will be used as the only mapping in the future IEC 61850-8-2.

The secretary of IEC TC 57 has presented a slide (slide 5) with the following requirements during a public event at the Hannover Messe 2014:

  • “Part 8-2 Specific communication service mapping (SCSM) – Mappings to web protocols
  • Comply with the new edition of IEC 61850-7-1, IEC 61850-7-2, IEC 61850-7-3, and IEC 61850-7-4
  • Support the existing application data model defined in IEC 61850-7-410, 7-420 and 61400-25-2
  • Identify which web services specification should be considered to deploy cyber-security, in conjunction with IEC TC 57 WG 15 work
  • complementary to the existing SCSM (8-1), not competing”

He reported on the status of work: “Konsens bei XMPP als Lösung” (consensus to apply XMPP as solution).

Click HERE for the complete presentation of the secretary of IEC TC 57 during the Hannover Messe 2014 [German, pdf]

MMS messages encoded in XML (XER – XML Encoding Rules for ASN.1, ISO 8825-4) may be used as payload of the XMPP messages.

What would that mean for IEC 61850-8-1 (MMS ASN.1 BER encoded messaging) implementations? First: the 8-1 solutions would continue to be used. Second: an additional ASN.1 encoding rule would add some software at the encoding layer … and finally the addition of the “transport or middle layer” XMMP would offer a new “transport mechanism”. That’s it.

This way most of the IEC 61850 related software (API, datasets, reporting, logging, control, system configuration language, modeling and models, …) would be used unchanged!

By the way, using ASN.1 XER in addition to BER has been proposed and discussed some 20 years ago within ISO TC 184 SC5 WG2. It was too early.

Since MMS is independent of encoding, there seems to be no (technical) question to using XER.