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:

Dangerous Situation in the European Electric Power System Caused by "frozen" Measurements

Measurements of power flow (Watts in export or import) are very crucial for Load Frequency Controller … wrong (i.e., “frozen”!) measurements have caused almost a big blackout in Europe in January 2019.
What happened: the measurement of power of the lines between two transmission systems (Germany – Austria) were frozen when the export value of 723 MW from Germany to Austria was measured (which was a result of 34 GW wind power generation in Germany). Later the wind power generation decreased to 4 GW … and the measurement (as input to the controller) many hours later still used the input value of 723 MW !!! In such a meshed power network it is unlikely that such a value is constant …

Oops … something went absolutely wrong!

Report by exception (on a value change as used for the above measurement) is great … as long as there are changes figured out and reported. A frozen value does not cause a change and thus no new value will be reported … No receiver should expect that the export power is constant (723 MW) for days!! The sensors may have worked fine … but the software and communication failed … on both sides (sender and receiver). A receiver should not trust that the software and communication is working fine all time.
Here are some measures to monitor the communication (by the receiver) to figure out if the communication is OK:

1. Ping (in case of TCP/IP) (if no response after some time: raise flag)
2. TCP Keep-alive (if no keep-alive message in t bigger keep-alive: raise flag)
3. Polling by receiver (if no response after some time: raise flag)
4. Periodic reporting (if no report in t greater period: raise flag)
5. In case of no message received in a configured time period (in case of using IEC 61850 Reporting) the receiver should check if the report control block is enabled and is using the correct configuration values like trigger option, …
6. Check if the sequence of received values are plausible
7. Use redundant systems (comm, …)
8. …

Check out the official Entso-E report (with links to more details):

https://www.entsoe.eu/news/2019/05/28/entso-e-technical-report-on-the-january-2019-significant-frequency-deviations-in-continental-europe/

This reminds me on the Boeing 737 MAX disaster … maybe a programmer left the vendor of the load frequency controller and hired with Boeing … I am kidding.

How many programmer or people that configure power control systems and communication systems that lack experience with complex systems like a plane or a power system. Where are the “grey-hair” experts that would tell you in minutes how to … ? They may enjoy the beach with warm water and sun shine – relax and spend the pension for ...

It is not sufficient to have no ideas – one should also be unable to implement them.

I expect that more of these problems will hit the street once we have far more control, monitoring and communication in the smart(er) grids of medium and low voltage. Note that the problem in January 2019 occurred at transmission level!! … where more resources (higher budgets) are available (in the past).

Have a great weekend – with power.

The Energy Lab 2.0 in Karlsruhe (Germany)

Karlsruhe (Germany, the hometown of Karlheinz Schwarz) is known (among others) for supporting the German Energiewende: The KIT and NettedAutomation GmbH

NettedAutomation is deeply involved in the dissemination of IEC 61850 all over the world. Now I see big investments in Energy related R&D projects in Germany. One of the most crucial activities is the new “Energy Lab 2.0” in Karlsruhe.

Energy Lab 2.0 – The Smart Energiewende Platform
New Research Facility Links Producers with Storage Systems and Consumers –
Investment Totaling EUR 22 Million

“ … The project is embedded in the overall energy strategy of the Helmholtz Association. For the Energy Lab 2.0, the partners plan to build a simulation and control center and a network of energy technology facilities on KIT Campus North, an electrolysis test center at Forschungszentrum Jülich, and a facility for testing power-to-heat concepts at the German Aerospace Center, Stuttgart, by 2018.
The energy platform will link characteristic components for power, heat, and synthesis gas production with various energy storage technologies and consumers. For this purpose, large facilities existing at KIT will be integrated into the Energy Lab 2.0: The solar power storage park, the bioliq pilot facility, and selected energy consumers on KIT Campus North. Electrical, electrochemical, and chemical storage systems as well as a load- and fuel-flexible gas turbine with
current generator will be newly constructed and are planned to complement the network. A simulation and control center at KIT will integrate all network components of KIT and the partners in a smart energy system using information and communication technologies.
This infrastructure facility is the first of its type in Europe. …”

More to come. Stay tuned.

Click HERE for a more comprehensive description [pdf].

The German Energiewende Needs Communication – Government Pushes for Metering Infrastructure

The German government has published a draft that comprises several proposals for new (to be modified existing) laws:

Digitalisierung Energiewende: BMWi eröffnet Konsultation zu intelligenten Messsystemen

Click HERE for the current draft and related information.

The draft talks a lot about remote monitoring and control. E.g., “Zur Gewährleistung der Fernsteuerbarkeit von Anlagen im Sinne des Absatz 1 Nummer 1 Buchstabe b) ist es insbesondere erforderlich, dass neben der Abrufung der Ist-Einspeisung gemäß Absatz 1 Nummer 1 Buchstabe c) auch eine ferngesteuerte Reduzierung der Einspeiseleistung der Anlage über das intelligente Messsystem erfolgen kann …”

Germany Survived the Solar Eclipse 2015 on March 20

During the last days and months there were a lot of discussions and news about a possible blackout during the Solar Eclipse 2015 today. The operators (and the nature) were quite well prepared for the event.

Lesson 1 learned: Nature and Operators did a good job!

Is there another lesson learned? Sure!

Due to the fact that the universe is not made by human beings, we could predict the movement of the sun, the moon and the earth … and thanks to mathematics we could calculate the impact of the sun on a sunny day like today …

Source: ENTSO-E; click HERE for further details provided by ENTSO-E.

The first maximum of PV power feed-in of 13.3 GW was at 9:45 h today. One hour later the minimum feed-in was 5.1 GW at 10:45 h.

Source: SMA, click HERE for the online data (then select March 20, 2015).

Between 10:45 h and 11:45 h the feed-in grew by 11,7 GW. That means 195 MW per minute or 3,25 MW per second. The maximum of the day was 20.3 GW at 12:45 h.

Source: SMA, click HERE for the online data (then select March 20, 2015).

Note that the forecast was very accurate, as can be seen in the following diagram:

Source: TransnetBW; click HERE for the online data.

The forecast of March 13, 2015 (one week before) was some 700 MW higher than the actual value for 13:00 h, as can be seen in the following figure:

Source: TransnetBW; click HERE for the online data.

The transmission companies have spent a lot of money to get a very precise forecast for today – and it worked fine. But these efforts were taken because it was a remarkable day. The forecast may become better – they are still modeling the physical world with laws set by the creator of the nature. The future power system will be impacted by more man-made “laws” that focus more on profit than on physics.

How many power plants have been used today to control the frequency and balance the load and generation? Maybe a few hundred. These power plants are well equipped with remote terminal units and communicate through IEC 60870-5-101 (and some with -104).

The control center are able to control remotely in the context of schedules plant for the day.

Another question is: What if we have to control Millions of decentralized resources (in some years)? What if we have not only 40+ GW Wind Power and 50+ GW PV power installed?? Who will provide the needed schedules for millions of feed-in points? Who and how will we control millions of these resources?

And how will we guarantee that the needed communication links between millions of intelligent devices will operate in a disaster situation? Note: TODAYs Solar Eclipse was far away from a disaster!

And what happens if somebody manipulates the information and information exchange? Even if we limit the active control commands to a very few or forbid them at all. We need to exchange at least situational information: current, frequency, voltage, power factor, or … Who guarantees that the values exchanged can be trusted?

Can we then trust that we know all communication connections that end in a power plant? You would be surprised if you would start to list the communication assets. As an expert recently said: “I have had the same experience as … with respect to finding "unknown" remote access connectivity at almost every facility I have assessed. These include dial-up modems, wireless access points, and network interface cards that IT and Corporate Engineering did not know existed.” Somebody else said: “At another facility we were told that external connections were always unplugged, but we were able to call the equipment at the phone number we saw posted.”

The future of our power delivery system is dependent on millions (instead of hundreds) of power resources, and on human beings that may loose the control over the communication infrastructure or that may compromise the communication and control systems.

Lesson 2 (to be learned by all): Take the communication, secure communication, control, secure control, impact of the physics on the power system and other aspects MORE SERIOUS! Think always how to apply standards – I mean real standards like IEC 60870-5-104, IEC 61400-25, IEC 61850, or DNP3.

There is a lot to be accomplished at the engineering level! Power is more than Euros and Dollars … let’s do the job together. We need you all.

All people that have read to this end will agree with me (at least in general).

Thanks for taking your (spare!?) time.

MegaWatt Needs Smarter Megabit/s

What do we need? Huge countries need many MWatt (unit of power) to survive. To get the power whenever we want to use it, we need more “Smart Mbit/s” (“smart” data transfer rate in Mega bit per second). That means: more communicating devices … maybe tens of Millions in some time down the road. What do 1,000 MegaWatt (= 1 GW) and 1,000 Mbit/s (= 1 Gbit/s) have in common? These are huge numbers! And more: We need them both in the near future! The crucial issue is here: One needs the other. Zero GW means Zero Gbit/s and Zero Gbit/s means Zero GW.

Yes, you got it! The two are becoming increasingly interdependent!

There is (mainly) ONE medium to carry power: wires. There are hundreds or even thousands of media to communicate information! Guess you could not count them all. In order to keep the cost for the future power delivery system reasonably low, we could and should think of preventing the proliferation of communication systems. Guess you agree. But: Which solutions are worth to use? No doubt: IEC 61850, IEC 60870-5-104, DNP3, Modbus, … are those that would do a good job!

I would be very happy to have as many communication systems as we have power delivery systems: DC 24V, DC 48V, 3 phase AC 110V/60Hz, 3 phase AC 240V/50 Hz, … and a few more.

Clark Gellings (one of the world’s leading experts on the electricity system, ERPI Palo Alto) talked in a podcast about “The Future of the Power Grid”. He talks about crucial aspects of the future power systems. Key issues (from my point of view) are summarized in the following three points:

Question:
“So what are a few of the things that will have to happen between now and 50 years from now to make your vision of the grid a reality?

Clark Gellings’ answer:
Well, first, we’re going to need communications standards that allow devices to talk to one another, so that we don’t have the problem we have now. For example, in buildings, the electronics that are being used have as many as 28 different communications architectures. And so one building technology that might control some new thermal storage unit you have may not be able to talk to another device in that building.

Number two, the computer system that would control these millions of nodes in any given region of the United States, they don’t exist. I mean, we can control tens of thousands of nodes, and we do now, but we’re going to need to control millions of nodes. So that’s another area of development.

And thirdly, technology. For example, power electronics to fully be able to control, in a very fluid way, the power systems, even to the point of doing things like having the system self-heal, or taking action so as to mitigate from an outage that it sees, even before necessarily the outage has occurred.”

… sounds very expensive!? Not that much … listen to Clark Gellings.

Click HERE to listen to the podcast, find a link to download the mp3, and read the content.

Anyway, the 28 different communication architectures in the building automation he mentions are not so bad - compared to the factory automation with hundreds of solutions!

why not use the IEC 61158 (solutions)? Because it has too many!

IEC 61850 is about to unify most of them (at least at the near-process level where we find the Millions of signals to be shared between Millions of smart devices). And to provide smarter mechanisms to share information.

I hope we can convert more Mbit/s into “Smart Mbit/s”: using them in a smart way. Using smart communication mechanisms (like IEC 61850) will require less bandwidth and smart power systems will need less MW.

Report on the big South-Western US Blackout on September 08, 2011

Some 6 months after the big blackout in the Pacific Southwest, leading to cascading outages and leaving approximately 2.7 million customers without power in parts of Arizona, Southern California, and Baja California, and Mexico, a comprehensive report has been published.

The Key Findings, Causes, and Recommendations are as follows:

“The September 8, 2011, event showed that the system was not being operated in a secure N-1 state. This failure stemmed primarily from weaknesses in two broad areas—operations planning and real-time situational awareness—which, if done properly, would have allowed system operators to proactively operate the system in a secure N-1 state during normal system conditions and to restore the system to a secure N-1 state as soon as possible, but no longer than 30 minutes. Without adequate planning and situational awareness, entities responsible for operating and overseeing the transmission system could not ensure reliable operations within System Operating Limits (SOLs) or prevent cascading outages in the event of a single contingency. As demonstrated in Appendix C, inadequate situational awareness and planning were also identified as causes of the 2003 blackout that affected an estimated 50 million people in the United States and Canada.”

One of the crucial needs for real-time operations is the availability of real-time INFORMATION – to become aware of the situation at the level of the electrical process, primary equipment, secondary functions, and distributed power resources! This requires real-time information exchange which seems to have not been properly installed, available or used. One challenge is to handle the many vendor and user specific communication protocols. It is very surprising that even at the power transmission level the awareness seems to be showing gaps. The situational awareness (supported by real-time information exchange) at the high voltage levels is one of the most crucial issues in power systems!

So, what is the situation in the implementation of real-time information exchange systems in the lower voltage levels? Hm … IEC 61850 installed all over would definitely help to get a good awareness of the situation of the system – allowing to proactively operate the system.

More standard based communication (IEC 61850, DNP3, …) to come.

Read complete power outage report.

Smart Grid Last Mile Infrastructure

20 experts from 15 companies have drafted an architecture for “A Standardized and Flexible IPv6 Architecture for Field Area Networks”.

The “paper is intended to provide a synthetic and holistic view of open standards Internet Protocol version 6 (IPv6) based architecture for Smart Grid Last Mile Infrastructures in support of a number of advanced Smart Grid
applications (meter readout, demand-response, telemetry, and grid monitoring and automation) and its benefit as a true Multi-Services platform. … provide an efficient, flexible, secure, and multi-service network based on open standards.”

IEC TC 57 standards like CIM, IEC 61850, and IEC 610870, as well as DNP3, IEEE 1888, and Modbus are understood as crucial application standards.

Click HERE for the above architecture.

What is IEEE 1888? A new IEEE project …

Standard for Ubiquitous Green Community Control Network Protocol

Click HERE for some background information
Click HERE for the PAR
Click HERE to visit the project website.

I hope that the experts involved in the project IEEE 1888 will rely on standards like CIM, IEC 61850, and IEC 610870, … Hope that the energy automation market is smarter than the industrial automation market: keeping the number of protocol solutions very low!! The industrial automation domain has a lot of headaches with the proliferation of the many many protocols (100+)!!

Details of NEW Hirschmann RSP and Embedded Switches With IEC-Standard Redundancy and IEEE 1588 disclosed

The recently announced new Ethernet Switches from Hirschmann that support redundancy protocols are now officially disclosed.

With Hirschmann™ RSP Switches, Which Support the New IEC-Standard Redundancy Protocols (PRP, HSR), Networks Can Now be Built for the First Time With Genuinely Uninterrupted Data Communication.

The Advantages at a Glance

• Extensive range of redundancy methods: PRP, HSR, PRP/HSR Red Box, MRP, Fast MRP, RSTP
• Precise synchronization compliant with IEEE 1588v2
• Enhanced security mechanisms: authentication, radius, role based access, port security, SSHv2, HTTPS and SFTP, plus others currently in preparation.
• Fast device replacement, comprehensive logging and storage of all configuration data, plus operating software updates via SD card
• High level of vibration resistance
• Broad immunity to electrostatic discharges and magnetic fields
• Temperature range from -40°C to +70°C
• Power supply 24/36/48 V DC or 60/120/250 V DC and 110/230 V AC
• Strong and compact metal housing

Click HERE for the technical Brochure [pdf, English]
Click HERE for the technical Brochure [pdf, Deutsch]

The New Embedded Ethernet EES20 and EES25 Switches from Hirschmann™ Combine the Functional Scope of a Powerful Managed Switch With Interruption-free Redundancy Protocols and Precise Synchronization.

• This module allows automation equipment to be extended to include state-of-the-art switch technology with very little effort
• The additional network functionality gives the equipment sustained competitive
  advantages
• Development process and time-to-market are significantly shortened thanks to
  Embedded Ethernet

Click HERE for the technical Brochure [pdf, Englich]
Click HERE for the technical Bochure [pdf, Deutsch]

IEC 61850 Editions – Help to Prevent Confusions

After my recent Newsletter on IEC 61850 many experts visited the blog post of the first discussion on Editions which summarizes:

BUT there will be not an EDITION 2 of the standard SERIES IEC 61850 per se!! Various parts (of the first 16 parts) will be revised and extended and then published tagged as EDITION 2.

New parts will be published with the tag EDITION 1, e.g., IEC 61850-80-1 (Guideline to exchanging information from a CDC-based data model using IEC 60870-5-101 or IEC 60870-5-104) - IEC/TS 61850-80-1, Edition 1.0, 2008-12

Click HERE for the complete post.

There are a lot of confusions when people talk about Editions of IEC 61850.

In a new paper it is reported: “Edition 2.0 of IEC 61850 Standard has been released considering valid technical issues and future aspects of protocol usage. … compares the IEC 61850 Edition 2.0 specification to its predecessor Edition 1.0.”

Click HERE for that paper.

There is hope that experts will use more precise language when it comes to editions of the many parts of IEC 61850 and related documents.

In addition to the question of the Edition of the standard there is another question, when it comes to the Devices that implement IEC 61850: Does this or that Device conform to IEC 61850 Edition 1 or Edition 2?

Since there is NO EDITION 2 of the STANDARD, a Device could NOT be characterized as an IEC 61850 Edition 2 Device!!

We have to differentiate the various aspects of the Standard: Which Logical Nodes, Common Data Classes, Services, which subset of the Configuration Language Edition 2, et cetera are implemented.

Edition 2 of any part of IEC 61850 can mean the following:

1. (Usually: Most) Definitions of parts tagged Edition 1 have been taken over in the same parts tagged Edition 2 without any change.
2. (Some) Definitions of parts tagged Edition 1 have been taken over in parts tagged Edition 2 with fixes or minor changes. During the tissue process the parts tagged Edition 1 have already been “fixed” to some extend.
3. (Less or more) New Definitions have been added in parts tagged Edition 2. [Service tracking in IEC 61850-7-2, many new LNs in IEC 61850-7-4, …]
4. (Some) Definitions of parts tagged Edition 1 have been moved to parts tagged Edition 2 without changes. [e.g., LN STMP from IEC 61850-7-410 Ed1 to IEC 61850-7-4 Ed2; Substitution has been moved from IEC 61850-7-2 Ed1 to IEC 61850-7-3 Ed2, …] 

A Device A that implements those definitions from several parts tagged Edition 1 that have not changed in Edition 2 of these parts is compliant to edition 2 of these parts without any modifications! If a Device B implements some new features of one or more parts tagged Edition 2, then these new features have to be listed in some detail to understand the situation. Some detail means that the implemented features per part tagged Edition 1 and/or Edition 2 have to be listed.

Examples:

1. A Device may just implement a new LN from Edition 2 of part IEC 61850-7-2; the other definitions are used as defined in Edition 1 of the other parts like IEC 61850-7-3, 7-2, 8-1, … So, is this an Edition 1 or Edition 2 Device? Both! But we better do NOT TAG a Device being Edition 1 or Edition 2. It’s a Device implementing the services according to the PICS of part IEC 61850-7-2 Edition 1 (the subset used may be unchanged in Edition 2), IEC 61850-8-1 Edition 1, … and the STMP LN of IEC 61850-7-4 Edition 2.).
2. The same Device could be understood as implementing the STMP LN according to a part that is tagged Edition1: The STMP LN is still officially published in IEC 61850-7-410 Edition 1. Edition 2 of 7-410 will not have the STMP LN any more – it is already moved to 7-4 Edition 2.

Users should not wait until a Device or the Communication Stack is compliant to Edition 2 of the Standard IEC 61850!! You will never get such a Device because there is NO Edition 2 of IEC 61850. You may want to use one or the other new service of IEC 61850-7-2 Edition 2 (like Service tracking of control block services) or a new LN from IEC 61850-7-2 Edition 2 or from IEC 61850-7-420 Edition 1 or IEC 61850-90-7 Edition 1 …

Always list some details what has been implemented from the various parts tagged Edition 1 or Edition 2 – if you want to prevent confusion. 

Additional discussions on this topic will follow – time permitted.

Stay tuned.

Distribution Company Vector’s Ten-Years Plan for IEC 61850

Vector Limited is the electric power distribution company in the Auckland (New Zealand) area. The company publishes every year an Asset Management Plan (AMP) – informing the public and others what the company is planning to do with their assets. The current plan covers a ten year planning period from 1 April 2011 to 31 March 2021.

One goal of the current AMP is to demonstrate innovation and efficiency improvements. What does this mean related to IEC 61850? A lot in the past and in the future:

• Vector’s substation automation system is based on resilient optical
  Ethernet local area network running IEC 61850 compliant IEDs.
• Vector’s current standard for internal and external communication systems is IEC 61850 standard. DNP3 is also used as an interim solution.
• At present over 50% of Vector’s primary substation are equipped with IEC 61850 compliant IEDs.
• Vector has been running an annual RTU replacement programme for a number of years, and is currently replacing approximately 10 RTUs per region per annum. To replace conventional RTUs, two approved solutions have been used, traditional RTUs with a migration path to IEC 61850, and fully compliant IEC 61850 solutions.
• …

Click HERE for the current plan (2011-2021) [PDF, 10 MB]

Use-Cases for Distributed Photovoltaic and Storage Systems

EPRI (Electric Power Research Institute, Palo Alto, USA) has been active in the research and development of the electrical power delivery systems. Just remember the projects UCA 1.0 (Utility Communication Architecture) and UCA 2.0. Both projects have contributed to the IEC TC 57 (Power System Management) and influenced several crucial standard series like the CIM, IEC 60870-6 TASE.2 and IEC 61850.

The work on the “Utility Communication Architecture” is going on in various IEC TC 57 projects and EPRI is still contributing to this process (especially to the definition of IEC 6185-90-7 - Object models for photovoltaic, storage, and other DER inverters). A very interesting EPRI report looks into the “Uses for Distributed Photovoltaic and Storage Systems”. The report lists and discusses briefly the following use-cases:

• Energy Generation
• Local Energy Storage to Compensate for Photovoltaic Intermittency
• Use of Energy Storage for Arbitrage Benefit
• Use of Local Energy Storage to Maximize Photovoltaic Generation Value
• Energy Storage for Customer or Community Backup Power
• Energy Storage to Reduce or Limit Peak Loading on the Utility System
• Energy Storage for Load Following
• Energy Storage to Reduce Customer Peak Demand
• Energy Storage for Local Power Quality Control
• System Stabilization – Transient Watt Modulation with Line Frequency
• System Stabilization - Transient Watt Modulation with Line Voltage
• Var Production for Voltage Regulation
• Var Production for Voltage Stabilization
• Var Production for Power Factor Management
• Var Compensation for Intermittent Generation
• Connect/Disconnect from Grid – Non Islanding
• Connect/Disconnect from Grid – Islanding
• On/Off Control of PV and/or Storage Inverter
• Adjusting Maximum Generation Level
• Metering Energy from Photovoltaic or Storage Device
• State Monitoring
• Event Reporting by Exception
• Event Logging

Click HERE for the 44 page report on use cases.
Click HERE for an overview about IEC 61850-90-7.

In an up-to-date publication of the German VDI nachrichten it is reported about storage possibilities on 2011-10-28 that:

• The capacity of all German pumped-storage hydropower plants would provide power for 1 hour.
• The capacity of 42 million German cars would last for 24 hours.
• The capacity of the German oil and gas storages would last at least for 2 months.
• The storage of “Wind or PV Power” (Converting Electricity to Natural Gas) is also an option.

Click HERE for an R&D report on Converting Electricity to Natural Gas.

Whatever the energy Mix will be – there is a crucial need for information and communication systems supporting the future power delivery system!

The good news is that there is no need to develop standards for information and communication systems from scratch! There are sufficient standards available, implemented and tested so that the power industry can straight use them: IEC 60870-6 TASE.2, CIM, IEC 61850, IEC 61400-25, …

“Visit” a U.S. Power Grid Control Center

The New York Times provides some information about the work in Control Centers of the U.S. Power Grid … quite interesting information.

Click HERE for the article.

If you want to apply for a job managing the North American power grid, you have to answer communication related questions like this (from NERC):

6. Standard COM-001-1, encourages “redundant and diversely routed” telecommunications facilities. Why "would “diversely routed” facilities be encouraged?

1. So communications can be simultaneously sent and received over the redundant paths.
2. So as not to create a monopoly for one particular telecommunication service.
3. So more neighboring systems can tie into the telecommunications network
4. So one specific problem could not eliminate redundant facilities

If you would answer with 2. … you may … hmmm … ;-)

Click HERE for this and more questions.

Power Outage in the South-West – Controlling Huge Power Systems is a Challenge

A huge interconnected power system follows 100 per cent the rules of laws like the Kirchhoff's Law and others. The Physics of the electrical system does not care about share-holder value, regulation and de-regulation – it is a law that can’t be changed by lawyers and bank managers!

The electrical power in every homes outlet is understood as a given – as sun shine and rain!! It is just here.

Two weeks after the power outage in the South-Western, it is likely that missing communication at the level of humans had a big impact on the stability of the power system.

Click HERE for some more details.

Click HERE for a discussion if the regulation or the de-regulation of the power market had a huge impact on the power outage.

Whatever people’s interpretation is: the electrical system is an electrical system that cannot be cheated.

I’m wondering why the control systems involved in providing a stable power system in the South-West seemed to not have all crucial information about the power system exchanged between all technical systems (parties) involved. There is a standard available for many years that would allow to exchange all real-time information needed to control the power system: IEC 60870-6 TASE.2 (ICCP).

There is one lesson we have to learn: The information systems could also not change the Kirchoff’s and other laws. The electrical system is an electrical system for the last 100+ years and for the future …

IEC 61850 for Substations Only?

The title and scope of IEC 61850 was for many years very restricted:

2001 – 2009: Communication networks and systems in substations

2010 – … : Communication networks and systems for power utility automation

The new title and scope is still too restrictive! The working group wanted to change to “… for automation”. This was not accepted by the IEC Central Office. IEC deals with electro-technical matters. The term “automation” was understood as to broad.

From a content point of view IEC 61850 could be used all over where measurements and status information needs to be communicated – in any application domain. Even if you are just monitoring a process or system (no control need) you can use IEC 61850 models, messages and configuration tools.

The Model “STMP” (temperature supervision logical node) can be used wherever a temperature measurement is taken: Temperature of a transformer, of a room, ambient temperature or your body temperature. When the “STMP.Tmp.mag” value reached the configured limit (Alarm limit or Trip limit) an report or a GOOSE message may be issued.

By the way, IEC 61850 has rules how to define extended logical nodes and data objects. All values can be communicated the Ethernet and TCP/IP based information exchange methods.

Experts pointing to the scope “substations” are not up-to-date. Those arguing that IEC 61850 is for “power utility automation” only may not like to accept that IEC 61850 is very generic or common – applicable in a wide range of applications.

The title and scope are just “toner on paper”.

Progress in Smart Grid Deployment – Too slow?

Many people all over expect that the Electric Power Delivery system will be changed to become smarter over night. A system that has been build over a period of 20, 50, …. 100+ years cannot be changed in short time! The change is likely to occur in steps over several decades – may be for ever.

Peter Fox Penner (US consultant) has summarized what is going on in the process of change. He concludes: “… Taken together, the trends discussed here show that the smart grid is expanding and developing, even if the most successful entities and programs are surprising. More importantly, these trends illustrate the evolutionary nature of smart grid development. Arguments that the smart grid is moving too slowly underestimate the scale and complexity of rebuilding our entire grid. Utilities are tasked with deploying a complex series of infrastructure investments that must work in harmony with their current (already smart) systems, use innovative pricing that customers support, and produce a net benefit. Under these conditions, slow and steady wins the race. We can expect smart grid development to occur in stages over decades, ultimately transforming the power industry into a very different business.”

Click HERE for his report in the IEEE Smart Grid Newsletter.

When we talk about the pace of change in the information technology in industrial automation we should not get nervous when we see the slow progress! How long did it take to get Gigabit/s Ethernet for substation environments developed … and accepted!? New approaches in Automation take often decades before they are accepted and used.

Click HERE for a brief discussion on Ethernet and Tokenbus … written decades ago.

The future for standards is quite bright. When a utility decides to deploy information technology for the next 10 or 20 years it will likely chose a stable standard – so that there is no need to change the solution every 4 or 5 years … when manufacturers have developed a new solution.

MMS (Manufacturing Message Specification, ISO 9506, used in IEC 61850-8-1 to define the message encoding) has been developed in the late eighties (80s !) – some 25 years ago. Web services are understood by some people as an option for messaging – more up-to-date. I have seen a Report message of a simple state change message using IEC 61400-25-2 Web Services the other day. The length of the XML coded Report message was some 850 octets !! A Report message encoded with MMS/ASN.1 BER (as per IEC 61850-8-1) is really shorter: by a factor of about 10 !!

Don’t hurry. Take your time. Rome hasn’t be built over night!

I usually sate in my seminars that the deployment of IEC 61850 happens too fast – users often do not have any clue what they got installed. They got it because it was cheaper than xyz. All in a sudden they have several substations with hundreds of IEDs communicating with IEC 61850 – and many (may be almost all) utility engineers have to struggle with this new way to do protection and automation. Many of them have started to get training in IEC 61850 … and you?

Don’t start slow and slow down fast ;-)

Just start – there is something to learn!

Germany Increases Energy Research by 75 percent to 3.5 Billion Euros

The German government announced the other day that it will spend much more research money into the development of a clean energy delivery system. The government will spend 3.500.000.000 Euros ($4.9 billion) into research for renewable generation, higher energy efficiency, energy storage and grid-technology in the next three years (2011-2014).

Click HERE for the press release [in German only]

It is very likely that a reasonable part of this money will be spend for the IT infrastructure needed for the many applications of future power delivery system. There are at least two stable solutions that have to be taken into account: (1) the electrical system (A.C. and D.C.) and (2) the IP infrastructure. The future power system will be based on these corner stones. The electrical system will be supported by myriads of new intelligent controllers of the power resources (renewable, storage, …) and new controllers of the grid (transmission and distribution) – and many of the controllers need to work (communicate over Ethernet and TCP/IP) together and being supervised by other controllers, which are part of the overall control of the power system …

The international standard series IEC 61850, IEC 61400-25, IEC 61968/70 (CIM), IEC 60870-6 (ICCP), … are here to help that the dream of the German government becomes true. Without these standards, the future power delivery system would be a nightmare with hundreds of proprietary communication solutions.

Many more companies in Germany and Europe are starting to put their hands on the standards IEC 61850 and IEC 61400-25 to be prepared for the future power delivery system in 2011. More than 20 companies will have received an in-house course on IEC 61850 and other IEC standards by Karlheinz Schwarz by end of 2011, and he will have run about an additional 10 public courses this year.

There is a lot to be done – let’s get started or continue dealing with the IT infrastructure using IEC standards.

Of course: The IT infrastructure is just a vehicle for the future power delivery system. There is much more to do than to communicate. By applying already available standards it saves a lot of R&D money that should better be spend on questions like, “What does demand response really mean?”

Click HERE for a nice paper that discusses questions like: “What happens with the electrical system if a huge number of customers start their dishwashers, washing machines, stoves, AC, … at the same time after a real-time price information has been received by the consumers?” Could they behave in a way to cause power outages? May be …

The Parts of IEC 61850 – Status 2011-06

The status (2011-07-15) of the various parts of IEC 61850 is as follows (blue means: Edition 2 of the corresponding document):

System Aspects

1 Introduction and Overview
2 Glossary
3 General Requirements (EMC, …)
4 System and Project Management
5 Comm. Requirements for Functions and Device Models (reaction time …)

Configuration

6 Configuration Language for electrical Substation IED’s (App., IEDs, System, …)

Abstract Communication Services

7-1 Principles and Models
7-2 Abstract Communication Services (ACSI)

Mapping to real Communication Networks (SCSM)

8-1 Mapping to MMS and ISO/IEC 8802-3
9-2 Sampled Values over ISO/IEC 8802-3

Testing

10 Conformance Testing
10-2 Interoperability test for hydro equipments based on IEC 61850

Data Models und usage of models

7-3 Common Data Classes
7-4 Compatible Logical Node and Data Classes
7-410 Hydroelectric power plants
7-420 Distributed energy resources (DER)
7-5 Usage of information models SAS
7-500 Use of LN to model functions (SAS)
7-510 Use of LN (hydro power plants)
7-520 Use of LN (DER)
7-10 Web-based access to the IEC 61850 models

Use-cases and network infrastructure

80-1 Guideline … CDC-based data model using IEC 60870-5-101 or IEC 60870-5-104

90-1 Using IEC 61850 for SS-SS communication
90-2 Using IEC 61850 for SS-CC communication
90-3 Using IEC 61850 for Condition Monitoring
90-4 Network Engineering Guidelines
90-5 Exchange of synchrophasor information
90-6 Use of IEC 61850 for Distribution Automation
90-7 Object Models for PV, Storage … inverters, …
90-8 Object Models for Electrical Transportation
90-9 Object Models for Batteries

The number of Information Models are:

7-3 Common Data Classes [40]
7-4 Compatible Logical Node / Data Classes [158 LN /982 DO]
7-410 Hydroelectric power plants [ 63/350]
7-420 Distributed energy resources (DER) [ 50/450]
90-3 Using IEC 61850 for Condition Monitoring [?]
90-5 Exchange of synchrophasor information [?]
90-6 Use of IEC 61850 for Distribution Automation [?]
90-7 Object Models for PV, Storage … (important!) [5/50]
90-8 Object Models for Electrical Transportation [?]
90-9 Object Models for Batteries [?]
61400-25-2 Wind Turbines [16/250]

The four Keep-alives in IEC 61850

IEC 61850 uses several mechanisms to monitor the communication between two devices (Client/Server) or between a publisher and many subscribers and to monitor functions – in order to increase the overall reliability of the information exchange.

The four mechanisms allow to check connected devices and determine whether the connection and the devices are still up and running or not. Reactions on failures are a local matter of applications.

The two mechanisms for Client/Server are:

• Keep-alive in TCP connections (used by MMS) [RFC 1122]
• Reporting of Report Control Block attribute “IntgPd” [ACSI, 7-2]

The two mechanisms for Publisher/Subscriber (Layer 2 multicast) are:

• Time-Allowed-to-Live in GOOSE messages (next message in) [8-1]
• Sample Rate in SMV message (sampled measured value) [ACSI,7-2]

The following figure shows how Integrity Period (communicated in a Report message) could be used to cyclically inform the client that the Reporting mechanism is up and running. Integrity Period is often used in cases where events happen very seldom and where the client wants to have a “heart beat” from the reporting server.

The configuration of the DataSet and the Report Control Block is usually provided by a SCL file. In the case of SystemCorp’s IEC 61850 API it is easily be done by uploading the corresponding SCL File to the IED, e.g., the Beck IPC IEC61850@CHIP.

Click HERE to evaluate the “Keep-Alives” with Reporting and GOOSE and real software running under Windows.

Click HERE in case you are looking for education and training about the possibilities, philosophy, and details of IEC 61850 and IEC 61400-25.

I have educated more than 2.500 people from more than 60 countries and more than 600 companies. More to come … see you soon.

What is a Stack?

The term Stack has many meanings, flavors,  … ask 10 experts and you may get 11 definitions. People talk about an IEC 61850 stack, an OPC UA stack, .... What do these mean? Are they comparable?

Let’s start with the general definition:

According to the Wikipedia: “The protocol stack is an implementation of a computer networking protocol suite. The terms are often used interchangeably. Strictly speaking, the suite is the definition of the protocols, and the stack is the software implementation of them.”

So, the software that processes the protocols is called the (protocol) stack.

With regards to IEC 61850 this can mean many things: Session, Presentation, ACSE, MMS, ACSI, MMS-SCSM, Model management and configuration language, API to the application, … let’s have a look at the server side of the communication:

	“Protocol” aspects	Remarks and Explanations
1	API to application	Control of Server SW, local services for read, write, events, control, … “Protocol” that defines how the application can communicate with the underlying IEC 61850 software.
2	Models, model management and model and ACSI configuration language	Describe the server’s information model and binding to application (LDs, LNs, DO, DA, …) Be aware that LNs have also services and protocols (see below for LN GLOG). The information models has to be organized in the IED’s software (including retrieving the self-description of the model)
3	ACSI (Abstract Communication Service Interface)	The (protocol) software has to implement the services Association control, retrieve self-description (Server, Client, Publisher, Subscriber, LD, LN, DO, DA, ControlBlocks, …), Get, Set, DataSet services, Reporting (events), Logging (events; historian), GOOSE, Sampled Values, Control, File services, time synchronization, … The implementation of the protocols that define the dynamical behavior of the services are one of the crucial parts of IEC 61850.
4	MMS SCSM	The ACSI services use MMS to carry the payload between client and server. MMS provides the serialization of (service) messages. Example: A Buffered Report Control Block is a quite comprehensive “Service” model with a set of service parameters (for control block attributes). The state machine of the Control Block requires a bit of a software!
5	MMS	Simple classes like NamedVariables, NamedDataSets, Journal, … Message schema (encoding using ASN.1)
6	ACSE	Kind of a remote procedure call
7	Presentation	Concrete encoding: ASN.1 BER
8	Session	Session between client and server
9	RFC 1006	Binding OSI upper layers to TCP
10	Security	Security according to IEC 62351 … TLS
11	TCP/IP	you know …!!
12	Lower layers	…

Note: GOOSE and Sampled Value messages are mapped directly to Ethernet!

What is the Logical Node GLOG? An application or a model with services and protocol (messages)? The GLOG is a standardized application that defines a model, services and a protocol! Guess you did not expect this … others may not agree with me …

IEC 61850-7-4 Edition 2 defines:

“5.7.4 LN: Generic log Name: GLOG
The LN GLOG refers to a function which allows to log not only changed data itself but also any related data being defined in the settings of LN GLOG. The logging is started by the changed data object (TrgRef1) or by the operator (LogTrg). The logged data are identified by the references to the related source data objects in the data model.” This in short the state machine of the GLOG service model and protocol (in abstract terms). The GLOG communicates with a client via services and a protocol …

The logged Data Values will be stored in an IEC 61850 Log … it can be queried by services from a client.

Let’s come back to our question, what is implemented in a stack?

Stacks from different vendors may be for free, may be reasonable priced, or may be expensive! What does this mean? Almost nothing! Because the CRUCIAL question is: WHAT would you get for your Euros or Dollars?

A stack of vendor X may cover the implementation described under bullets 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10.

A stack of vendor Y may cover only 5, 6, 7, 8, 9, and 10.

The difference is tremendous: The efforts to implement the requirements listed in bullets 1, 2, 3, and 4 are (to my experience) likely more than 90 … 95 per cent of what needs to be implemented with regard to IEC 61850!

If you hear something like “the stack so-and-so is cheaper …” listen twice and then think about what you have heart three times and ask what that stack really provides four times AND ASK PEOPLE WITH EXPERIENCES WHAT IS LEFT FOR YOU TO DO to get a compliant IED !!! I have talked to many experts that were surprised that it took sooo long … and cost sooooo … much to get a compliant IED.

When it comes to the comparison of OPC UA and IEC 61850: Listen very carefully, and ask questions … and then … and then you may understand the difference from a standard and from an implementation point of view.

Click HERE if you want to experience what could be provided by a specific stack providing integrated software for issues 1 to 10 … with little left for you [German].
A workshop in English may be set up when you are interested … let Beck IPC know that you would attend a workshop in English.