Showing posts with label sampled value. Show all posts
Showing posts with label sampled value. Show all posts

Monday, November 2, 2026

Deploying IEC 61850 Process Bus and vPAC at the UK’s Largest GridHub (Dorman Point 400 kV Substation)

UK’s largest electricity transmission substation is designed to handle up to 3.2 GW of throughput ... the planned 400 kV facility ... will be build on IEC 61850 instead relying on 200 km multi-core copper control cabling ... wow.

Bruno Silveras LinkedIn post ...

Bruno Silveira reported today many details in his LinkedIn document (November 02, 2026):

Deploying IEC 61850 Process Bus and vPAC at the UK’s Largest GridHub (Dorman Point 400 kV Substation)

Excerpt:

"National Grid Electricity Transmission (NGET) has secured 73.3 acres at Dorman Point within the Teesworks industrial zone in Redcar to develop what is projected to be the UK’s largest electricity transmission substation.Designed to handle up to 3.2 GW of throughput, the planned 400 kV facility will serve as the electrical backbone for hyperscale AI data centres, offshore wind landings, and industrial decarbonisation projects across Teesside.

Delivering transmission capacity of this scale under ambitious energisation targets (targeted for initial operations by late 2029) exposes the limits of legacy substation engineering. A traditional hardwired design across dozens of 400 kV feeder, transformer, and busbar bays would demand hundreds of kilometres of copper multi-core cabling, sprawling relay buildings, and months of point-to-point physical commissioning.

Applying a modern, software-defined architecture, combining an IEC61850 Station Bus, a redundant Process Bus, and Virtualised Protection, Automation, and Control (vPAC), fundamentally transforms the civil footprint, project timeline, and operational lifecycle of the Dorman Pointasset. ..."

Some 30 years after the start of the standardization project IEC 61850 we can see the change in applied technologies and standards for our electric power delivery systems ... more to come.

Tuesday, August 11, 2026

How IEC 61850 Leverages Mine Thermal Energy Storage

Bruno Silveira posted on LinkedIn an very interesting article about using IEC 61850 to a full extend!

He shows, that decarbonizing regional energy networks requires coupling thermal district networks directly with electrical distribution grids.

Excerpt: "To maximize operational responsiveness without jeopardizing critical grid stability or operational technology (OT) security, MTES (Mine Thermal Energy Storage) assets must interface directly with modern IEC 61850 Substation Automation Systems (SAS)."

This is the right view of applications being part of the electrical system: either as source or sink of electrical power!! Currents and voltages are the crucial ingredients of the energy storage systems ... electric storage or electric or ... whatever. Always the same need: coupling storage networks directly with electrical distribution grids.

It does not make sense to decouple power systems from big(ger) applications.

Click HERE for his article with an overview.

Monday, August 3, 2026

Is IEC 61850 an old Standard?

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

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

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

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

The standard series IEC 61850 has many aspects to consider: 

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

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

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

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

Monday, July 6, 2026

IEEE P3416, Relay Test Sets, and the IEC 61850 View

My dear friend Andrea Bonetti (Megger), Chair of IEC TC 95 (measuring relays, protection equipment, and protection functions) and Vice Chair of IEEE P3416 (relay test set for ...), has recently published a paper on the IEEE P3416 project together with Cord Mempel (Omicron), Hong Wang (State Grid Corporation of China), Jinlei Xing (Schneider Electric), Jun Verzosa (Doble), Thierry Bardou (Schneider Electric) and Xicai Zhao (NARI Electric).

The paper is titled
IEEE P3416 as a Bridge Between IEEE/IEC Protection Testing Methodologies and Relay Test Set Capability 

It was presented at IEEE GPECOM 2026 in Naples and it is now available on IEEEXplore.

The work on IEEE P3416 is progressing, and hopefully the project can be finalized by the end of 2026.

I am not a protection engineer. For protection topics I usually refer to Andrea, who is deeply involved in IEC TC 95 work on measuring relays and protection equipment. My own interest is mainly from the IEC 61850 point of view: what does this project mean for digital substations, communication, interoperability, test systems and engineering?

From that perspective, IEEE P3416 is very interesting.

Andrea and I have conducted many seminars in Europe, Asia, Asia Pacific, ... and we are offering together a training in Karlsruhe (Germany) soon.

Protection testing is no longer only a question of injecting analogue currents and voltages into a relay and checking whether the relay trips. This is still important, of course, especially because many conventional substations and many conventional relays will remain in service for many years. But the world of protection testing is changing. In IEC 61850-based systems, the interface to the protection function may include Sampled Values, GOOSE messages, time synchronization and digital engineering information.

This is where the link to IEC TS 60255-216-1 becomes important.

IEC TS 60255-216-1 deals with protection functions using digital communication as input and output. In practical terms, this includes protection functions subscribing to Sampled Value streams instead of receiving conventional analogue inputs, subscribing to GOOSE messages such as breaker position or breaker failure signals, publishing GOOSE messages such as trip signals, and using time synchronization messages.

This is a very important step. IEC 61850 defines the communication and information exchange mechanisms. IEC 60255-216-1 applies these mechanisms to protection functions. IEEE P3416 then looks at the test sets and tools that are needed to test such protection functions in a reliable, repeatable and documented way.

For an IEC 61850 person, this is the interesting bridge.

A relay test set in the digital substation is not only a current and voltage source. It may also need to publish Sampled Values, subscribe to GOOSE, publish GOOSE, handle timing correctly, use engineering information, support test libraries, automate test sequences and generate clear reports. The test set becomes part of the digital testing environment.

This also shows why cooperation between IEC and IEEE experts is so important. Protection experts, communication experts, test-equipment experts and standardization experts must understand each other. IEC 61850 alone does not define how a protection function shall perform. IEC 60255 alone does not define the full communication system. IEEE P3416 alone does not define the protection algorithms. But together, these activities help users, manufacturers and test-equipment suppliers to build systems that can really interoperate.

Andrea often says that if experts do not interoperate, power systems will not interoperate either. This is exactly the point here ... and everywhere.

IEEE P3416 may look like a guide about relay test sets. But from the IEC 61850 point of view, it is more than that. It is part of the transition from conventional protection testing to digital protection testing. It connects test equipment with protection-function requirements, IEC 61850 communication, Sampled Values, GOOSE, time synchronization, test automation, reporting and calibration.

This is why I think IEEE P3416 is a project worth following closely — also for the IEC 61850 community.

Enjoy IEC 61850!

Friday, May 3, 2024

Some Hints On Static And Dynamic Reporting According To IEC 61850

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

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

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

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

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

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

A nice summary can be found here:

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

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

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

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

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

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

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

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

Do you want have a problem - no problem!

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

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, February 23, 2024

Second Sketch (Video) on Some Basics: The Mapping of IEC 61850 to MMS

IEC 61850 is well accepted globally in the power utility domain. One key issue has always been discussed and criticized: The mapping of the information models (Logical Devices, Logical Nodes, Data Objects ... ) and information exchange services to MMS (Manufacturing Message Specification defined in the standards ISO 9506-1 and ISO 9506-2, developed in the 1980s).

This video (58 minutes) explains the concepts of the mapping to MMS ... ASN.1, ASN.1 BER ... MMS for GOOSE and Sampled Values !?

Click HERE to access the video.

I will continue to produce more sketches (videos) and make them available through Screencast.

I look forward to your feedback.

Enjoy.

Tuesday, November 28, 2023

Up-to-Date IEC 61850 Trial Tools Available From InfoTech (Poland)

Have you ever tried to send or receive messages according to IEC 61850 or IEC 61400-25: Operate, Report, Get, ... GOOSE, Sampled Values, ... try the following updated trial tools ... from InfoTech (Poland) 

Use of Sampled Value Publisher (Sender) according to IEC 61850-9-2LE:


Window for various parameter that can be modified and applied:

Wireshark trace of a SV message:


Access several presentations and the link for the trial versions:

Client/Server, GOOSE Sender & Receiver, SV Sender & Receiver

visualization on a flow diagram and on-line monitoring of GOOSE based on SCD file as input

Simulator of a network of server IEDs based on SCL files (ICD/CID/IID/SCD)  +  creator/editor of ICD

Overview of the Library which we license as source code or as derived binary DLLs for PC/MS Windows

This is the link to the trial version of all tools

Enjoy.

Wednesday, May 20, 2020

Sampled Values and IEC 61850-9-2 LE: What is it?

The other day I received the following email:

Dear Mr. Karlheinz Schwarz,
I am sorry to disturb you. My name is XXX and I am a researcher from YYY. I would like to ask some questions to you regarding the standard IEC 61850-9-2LE.

1) May I know the status of IEC 61850-9-2LE? Is the standard will be obsolete or remain as it this?

2) Can I get some explanations from you about the differences between IEC 61850-9-2, IEC 61850-9-2LE and IEC 61869-9?

I really appreciate your kindness and time to answer my questions above.
Thank you & best regards,
-------------------------------
I have a very good friend that I asked to answer for me. Her is his answer:
Dear Karlheinz, 
Sure I can do my best for that.
Thanks for this opportunity.
Dear XXX, please see my attempt to answer.
Your questions are our everyday’s questions, and my answers need to be taken with “common sense”, reasonability and not as law, where somebody is right and somebody is wrong.
This is the best I can say.
The IEC 61850-9-2 Light Edition (LE)  is NOT a standard.  It is an UCA profile; a sort of gentlemen agreement (followed by everybody so far), where in principle the dataset carried by the SV Message (Sampled Values message) is fixed to 4 voltages and 4 currents.
The sampling frequency is 80 samples per period (4000 Hz for 50 Hz systems and 4800 Hz for 60 Hz systems).
The length of the SV message is fixed (in terms of bytes)
The quality string has one “extra bit” (the 14th bit, for derived or measured of the analog quantity) compared with a “normal quality string” of IEC 61850 and also IEC 61869 series, of 13 bits.
The time synchronization is 1-PPS
There is formally no support for PTP time synch (typical of “Edition 2” of IEC 61850 standard. LE is “edition 1”)
There is formally no support for “SIMULATION” mechanism (typical od “Edition 2 “ of IEC 61850 standard; LE is “edition 1”)
And many others.
TO MY EXPERIENCE:
It is commonly understood (and you have to make sure it is commonly understood also by the people working in your projects: suppliers, consultants, utility engineers etc) that:
- 9-2 LE supports Simulation mechanisms
- 9-2 LE supports PTP as time synch (be careful that PTP is actually IEC 61850-9-3: 2016 )
Even if formally this is not strictly in line with the UCA specification for “LE”.
So, IEC 61850-9-2LE (written by UCA working group) is a profile of IEC 61850-9-2 (written by the IEC committee TC 57)
And today it is the only “standard” that is implemented and in service for process bus applications.

IEC 61869-9 (and also -6 and also soon the -13) are parts of the IEC 61869 series, written by the IEC committee TC 38 (Instrument Transformer). 
So they have to do with the Merging Units, they are also profiles somehow, and also many other requirements, that you need to fulfill if you want to have a Merging Unit according to IEC standards.
To my opinion, no matter what IEC 61850 says in general, if you do a Merging Unit and follow IEC, you should follow IEC 61869 series.
In principle, the IEC 6185069-9 standards are often associated to:
  • “Dynamic” dataset. This means that not only 4 U and 4 I will be transmitted. I can transmit just  one voltage, or 25 currents, or 6 voltages and 3 currents.. This is done from SCL.
  • Sampling frequency of 4800 Hz, no matter the power system frequency (50 Hz or 60 Hz).
  • PTP time synchronization (for MU)
  • 2 samples per SV message (so called ASDU). “LE” has only one sample per message (one ASDU per message)
But it is of course much more than that.
What about protection relays/protection functions?
TC 95 is responsible for protection functions in IEC.
In principle it  is TC 95 / MT 4 (Maintenance Team 4) that takes care of functional standards for protection functions (IEC 60255-121:2014 for distance protection for example). Other maintenance teams take care of protection related standards like EMC etc.
Recently TC 95 has started a new working group (WG 2) that considers IEC 61850 for protection applications. A Technical Report is on its way and parts of that technical report will be implemented in the so called IEC 60255-1xx series, for protection relays.
But this is not ready yet and all of this needs to be considered with extreme care and communication among all the involved parts in a project.
I work as well as consultant for IEC 61850 applications in relay protection. Mainly for TSOs, since many years. Please have a look at this paper, written by many of us active in TC 95 / WG2. I think it will help you to better understand.
If you are interested in what TC 95 / WG2 does, you are more than welcome to contact me and I’ll help you in joining “our” activities.
For your understanding, there is a high dialog between TC 95, TC 38 and TC 17 (circuit breakers) for making the use of IEC 61850 more interoperable not only at “data level” but also at “functional level”, at least for protection applications.
For metering or power quality applications, for example, I don’t know what to say.
I hope this helps you.
Karlheinz, your extra comments are always welcome.
My best regards
Andrea Bonetti
Just passed

 Fachtagung Schutz- und Leittechnik 2020 , Berlin, 18-19 February 2020

Mr. Andrea Bonetti MSEE
Senior Application Specialist Relay Protection and IEC 61850
Active member of IEC TC 95 / MT 4 ”Measuring relays and protection equipment” since 2006.
Megger Sweden AB
andrea.bonetti@megger.com
Rinkebyvägen 19, SE-182 36 Danderyd (Stockholm)
Sweden

Tuesday, May 12, 2020

New GOOSE and Sampled Values Performance Test Platform

GridClone developed a new GOOSE and Sampled Values Performance Test Platform:

SIMFLEX IEC 61850 PT Platform

It is a solution for testing GOOSE and Sample Values time performance, functional behavior and conformance to the standard.

Applications:
  • Inspect GOOSE/SV behavior on microsecond level
  • Simulate multiple GOOSE and SV Streams
  • Execute (pre)conformance, detail and functional testing
Benefits:
  • One solution for GOOSE/SV and MMS testing
  • Demystify process bus complex behavior
  • Ready to integrate fully automated platform
Values:
  • Building trust in Digital Substation by testing it
  • Resolve GOOSE/SV issues in system design phase
  • Maximize level of details and minimize testing time
Click HERE for more information.

Wednesday, August 28, 2019

IEC 61850 Sampled Values and GOOSE Messages Reduce Complexity and Cost

Synaptec Ltd (a spin-out technology company from the University of Strathclyde, UK) developed a distributed electrical sensing technology platform using IEC 61850. The approach allows measured values from up to 50 current transformers to be acquired passively using a single optical fibre core over a distance of up to 50 km. These measured values can then be utilised as part of centralised PAC schemes, or communicated to traditional PAC devices for analysis via IEC 61850-9-2 / 61869-9. By centralising current measurements, this method eliminates the need of having multiple protection relays at each line ends, complex time synchronisation systems at measurement points, and complex telecommunications equipment among the distributed PAC devices.

Click HERE for downloading the 12 page paper (Differential protection of multi-ended transmission circuits using passive distributed current sensors) describing the application and approach to solve a very crucial challenge.

Another paper (Implementation of centralised, numerical busbar protection using distributed photonic current sensors) describes the design and testing of the first centralised busbar protection scheme that makes use of distributed photonic current sensors and IEC 61850. By utilising distributed, passive sensors which are interrogated purely using standard optical fibre, the requirement for active units in the substation yard is completely eliminated. Additionally, the use of copper wiring from CTs to measurement units may be eliminated. The scheme, designed and built for Statnett by Synaptec, will be installed and trialled at Statnett’s Furuset R&D substation near Oslo, Norway. A prototype centralised busbar protection algorithm, validated with the University of Strathclyde, will run on the central merger unit to prove the principle of centralised busbar protection using a single active IED.

Click HERE for downloading the paper.

Click HERE for the Synaptec news (Norwegian TSO Statnett innovates with Synaptec technologies):

With one system able to instrument 50 locations synchronously, 6 busbar feeders will be independently and simultaneously protected by one system, with capacity to spare for novel temperature and vibration monitoring of nearby HV assets, such as transformers.

The development and the applications show that the standard series IEC 61850 has all the "tools" helping to keep the power flowing and the grass green - at all voltage levels.

Monday, July 1, 2019

IEC TC 57 Just Published Amendment 1 of FDIS of IEC 61850-9-2

The following FDIS has been published last week:
57/2112/FDIS

Amendment 1 – Communication networks and systems for power utility automation – Part 9-2: Specific communication service mapping (SCSM) – Sampled values over ISO/IEC 8802-3

The ballot closes: 2019-08-09

Compared to the second edition, this first revision of the second edition:

a) updates the normative references
b) adds a synchronization clause (Clause 9); adds references to IEC 61588:2009 and
IEC/IEEE 61850-9-3 for SV synchronization;
c) modifies physical layer specification in T-Profile;
d) modifies MSVCB components (Table 9 and Table 10);
e) deprecates usage of USVCB;
f) modifies encoding for the transmission of the sampled value buffer (Table 14);
g) adds Table 20;
h) adds Table 21;
i) adds Annex C related to possible backward compatibility issues between revisions of this
standard;
j) provides clarifications and corrections to the second edition of IEC 61850-9-2, based on the
tissues = { 1349, 1272, 1055, 944, 863 }.

Saturday, March 2, 2019

IEC TC 57 Just Published Draft IEC 61850-90-20 On Redundancy

IEC TC 57 just published the first Draft IEC 61850-90-20 on System Redundancy:

57/2080A/DC
IEC TR 61850-90-20 ED1
Communication networks and systems for power utility automation –
Part 90-20: Guideline to redundancy systems

Excerpt from the Introduction:

"The paper “CIGRE B5-109: Redundancy challenges on IEC 61850 systems and Migration
Paths for IEC 61850 Substation Communication Networks” introduce redundancy concepts as
follows
“Device redundancy of substation control units may be required in order to increase the availability of the substation automation system at the station level. System level redundancy is achieved by hot-hot or hot-standby configuration of duplicated station units that need to exchange information to ensure data consistency as well as coordinated and safe operation.
IEC 61850 communications in redundant configuration of duplicated clients faces challenges how to ensure that database in both central station control units are synchronized and that no events are lost during the switchover from the primary to secondary IEC 61850 client.”
A proposed redundancy system consists of two IED entities forming a logic IED. One or more lower level IEDs, e.g. merging units or circuit breaker, delivering the input data for the IED entities and getting results from the IED entities. One or more higher level clients receives output data from the IED entities for supervision or HMI.
Additionally, a higher level IED might exist, which supervises the state of the redundant system. In this context this concerns especially the state of the IED entities, so that a failed IED can be detected and repaired before the second IED fails.
The communication between the redundant system application and the lower level IEDs takes place with IEC 61850, mainly based on IEC 61850-8-1(MMS) reporting and commands, for time critical functions with IEC 61850-8-1(GOOSE) and IEC 61850-9-2(SV).
The communication to station level clients based on IEC 61850 is typically MMS based for supervision, commands and settings configuration changes. Since MMS is acknowledged service, server and client are aware of each other and the client supervises the servers. If both redundant system IEDs are hot, the client might select which of them it takes for executing a service request."

The TC57 P-members are invited to submit comments to this draft by 2019-03-29 at the latest.

Please note:
The application domains that need redundant systems may be crucial (for some high voltage systems) but may not be applicable for most systems in the energy delivery domain. This document is really of interest for a small, special group of experts ... not everybody interested in using IEC 61850 for exchanging some signals may need to check that draft document.
One challenge with IEC 61850 is: Which subset out of a big standard series do I need to understand for my application - that means: YOU HAVE TO KNOW YOUR APPLICATION !!

Saturday, February 9, 2019

Difference between IEC 60870-5-104 and IEC 61850

There seems to be a growing interest to understand what the difference is between IEC 60870-5-104 and IEC 61850. There have been many discussions, complaints, and frustrations ... no wonder.Here is what I have answered to somebody this week:

Dear xxx,

I guess I got it ... you are analyzing the communication inside a station ... to the IEDs (protection, control, ...).

The IEC 60870-5-104 plus a lot of utility or project specific (signal) engineering will do the job – has done it for decades.

The engineering is the key issue when comparing the two standards … if you can compare them at all!!

IEC 61850 offers a lot more than 104 or DNP3 …



From a message overhead point of view, you can say, that both are more or less the same ... because they use both Ethernet and TCP/IP. There is no benefit to use one or the other.
It is likely that IED vendors will mainly focus on IEC 61850 ... and may get rid of 104 in the long run.
I have always said that utilities using 104 in all substations should continue to use it – until they build new substations or do major refurbishments. There is no need to replace a running 104 solution with IEC 61850 ...
Another issue is: To use GOOSE for interlocking … to get rid of copper … or use it for tripping … and use sampled values some time down the road.
Finally there is an issue with manpower: If the utility has senior experts in 104 close to retirement … they should wait until they have retired. Yes! I have seen many old engineers not willing to learn something completely new!!
Click HERE for a detailed comparison written by domain experts.
Hope that helps a bit more.
Best Regards,
Karlheinz

Monday, September 17, 2018

Technical Report Considering Protection IEDs with Digital Inputs and Output under way


The IEC TC 95 Ad Hoc Working Group 3 (AHG3 meeting in Nanjing this week) 


is discussing the scope of a new document with the following Scope;

This Technical Report aims at considering protection IEDs with digital inputs and output complying with IEC 61850 and IEC 61869 standards, in particular 
  1. subscribing streams of digital Sampled Values (SV) representing energizing inputs of the protection function.
  2. subscribing GOOSE and/or reports by the protection function (eg. cb position, cb failure).
  3. publishing GOOSE messages (e.g. trip orders).
  4. subscribing time synchronization information.
On this base, this document will give recommendations and guidelines concerning requirements and testing of protection IED with digital inputs and outputs within TC95.

Requirements regarding characteristics of the communication network are not within the scope of this Technical Report. Delays and jitter due to the network have to be taken into account by network engineering. Figure 1 below shows the functional chain of a protection function.  This Technical Report only considers the data received and publish by the protection IED as shown in figure below. 

More to come ...

Friday, December 29, 2017

New Merging Unit Development Kit

A new Merging Unit Development Kit based on the NovTech IoT Smart Grid Platform with Intel Cyclone V SoC Core is available for your next project.
Utility companies are adapting their infrastructures to support bidirectional energy flow to handle the emergence of DER (Distributed Energy Resources) via microgrids, photovoltaic panels, and local energy storage. As distributed energy generation increases, new intelligence of sensors, measurement and protection equipment will be required to process data at the edge. Also with the increase in variable DER, it is more challenging for substations to deliver sinusoidal and predictable steady-state voltage and current. Utility companies rely on substation metering of secondary voltage (VT) and current transformer (CT) circuits to detect performance issues and to provide vital information in real time to distributed digital protection nodes.

To satisfy this need, SystemCORP and Intel developed an IEC 61850-9-2LE compliant merging unit solution in form of a demonstrator/development platform.

This development kit consists of 6 parts:

  1. NovTech IoT Octopus Smart Grid IoT Platform
  2. SystemCORP VT/CT Interface board
  3. SystemCORP IEC 61850-9-2LE Sample Value software stack (PIS-11) on ARM Cortex A9 core 1
  4. SystemCORP IEC standard 61850 server/client software stack (PIS-10) on ARM Cortex A9 core 2 (optional)
  5. Flexibilis embedded FPGA analogue front-end IP core
  6. Flexibilis Ethernet PRP/HSR FPGA IP core (optional) 

Click HERE for more information.

Wednesday, March 22, 2017

GridEx: The Smart Tool to Test Your IEC 61850 Network

FMTP (From Minus to Plus, Sweden) has gained a lot of positive feedback from experts using the GridEx Tool around the globe. GridEx built-in intelligence based on 30 years combined field experience in Protection Control with IEC 61850.

The new Test Tool looks very ruggedized:




The standalone tool provides many very crucial functions for simplifying the test and operation of automation systems based on IEC 61850. Here is one example function:

Click HERE for more details on the GridEx.

Monday, November 21, 2016

NEW HW: IEC 61850-9-2 LE Sampled Value Publisher

The SystemCorp "IEC 61850-9-2 LE Sampled Value Publisher" is a hardware platform for specific sampled value publisher applications for the Smart Grid IoT Platform from Novtech using the Altera (now part of Intel) dual core ARM/FPGA Cyclone V SoC.
This Smart Grid IoT Platform provides eight high precision analogue inputs. The A/D converter is directly controlled by the FPGA producing the sampling rate required for the SV publisher,   which is implemented in one ARM core.
The Sampled Values are published at a rate of 4000 frames per second for a grid frequency of 50Hz and 4800 frames per second for 60 Hz.
An eight channel VT/CT interface module is also available from SystemCORP Embedded technology allowing a direct connection of the Smart Grid IoT Platform to 110 V VTs and 5 A CTs.





Click HERE for downloading a two page description and additional information [pdf, 390 KB].

Saturday, July 2, 2016

FMTP and NettedAutomation announce Seminar Dates for 2017

Due to the request from power engineers FMTP and NettedAutomation have scheduled several dates for public training courses in 2017:

2016
19-23 September 2016 in Stockholm, Sweden [EN]
10-13 Oktober 2016 in Karlsruhe, Germany [EN]
07-09 Dezember 2016 in Karlsruhe, Germany [DE]

2017
30 January 2017 in San Diego, CA USA (just prior to the DistribuTECH 2017) [EN]
14-17 March 2017 in Stockholm, Sweden [EN]
04-07 April 2017 in Karlsruhe, Germany [EN]
19-22 September 2017 in Stockholm, Sweden [EN]
10-13 Oktober 2017 in Karlsruhe, Germany [EN]

Keep tuned to this blog to receive the latest in the domain power system protection and automation. Tap the experience of more than 230 training courses:
Plan your training for Fall 2016 and 2017 now!
Click HERE for further details.
Click HERE to contact us per email in case you have any question.

Sunday, June 12, 2016

Three New CDVs of IEC 61850 Edition 2 Amendments published

IEC TC 57 just published three new CDVs for Edition 2 documents:

57/1707/CDV
IEC 61850-7-2 A1 Ed.2: Amendment 1 to IEC 61850-7-2 Ed.2: Communication networks and systems for power utility automation - Part 7-2: Basic information and communication structure - Abstract communication service interface (ACSI)
The Amendment solves issues that have been reported and discussed in recent years. Some 50 of them are documented in the Tissue Database for part 7-2.

57/1708/CDV
IEC 61850-7-3 A1 Ed.2: Amendment 1 to IEC 61850-7-3 Ed.2: Communication networks and systems for power utility automation - Part 7-3: Basic communication structure - Common data classes
The Amendment solves issues that have been reported and discussed in recent years. Some 45 of them are documented in the Tissue Database for part 7-3.

57/1709/CDV
IEC 61850-9-2 A1 Ed.2: Amendment 1 to IEC 61850-9-2 Ed.2: Communication networks and systems for power utility automation - Part 9-2: Specific communication service mapping (SCSM) - Sampled values over ISO/IEC 8802-3
The Amendment solves issues that have been reported and discussed in recent years.

All three documents can be accessed publicly.

Please take some time to review both documents.
The documents should be available online for reading and for comments.
Check HERE for the access and for providing comments.