How Many and Which Information Models are defined in IEC 61850?

I guess you have heard that IEC 61850 defines a lot of Information Models. Yes, You are right.

The models are managed exclusively by the corresponding working groups with the Enterprise Architect UML Tool (the UML data base is for internal use only). The model version:

UML model of 61850 (wg10built6-wg18built3-wg17built5-jwg25built2-tc17built1-tc38built1.eap)

comprises the following number of Logical Node Classes, Data Objects (Attributes), Enumerations and Abbreviations:



An excerpt from the UML modes looks like this:



The UML Model is the single source data base that is used for the extensions and maintenance of the model, as well as the generation of Word or PDF documents ... The PDF documents are sold by IEC and other organizations.

You may complain that the standards are not for free ... hmm ... BUT look: You can download the various Code Components for free.

Click HERE for the Code Component for IEC_61850-7-4.NSD.2007A2.light.zip (IEC 61850-7-4 2007A2 NSD light, see the IEC 61850-7-4:2010 for full legal notices). The full version has additionally the semantic descriptions of the models.

Example of Enumeration:


Example of excerpt of LN Class MMU:



Click HERE to see the list of all Code Components as per today ... more to come soon.

To my understanding you can model many required information generated and consumed by a huge number of applications in almost all application domains of automation in the electrical system and beyond.

As the above example of MMXU shows, you can use this LN Class wherever you have 3 phase AC system!! In a building heating system for the electrical values of a compressor or a fan or a pump or ... the blue sky is the limit for the applications.

Click HERE to learn about crucial details discussing the LN Class MMXU and how it can be applied ... you may have never expected this comprehensiveness of the MMXU.

Note that the 3 phase system was first (more than 100 years ago) - then we have put a facade in front of the measurement function which exposes the measurements as data objects of the class MMXU. The application has driven the class - not vice versa.

The current edition 2.1 models defined in IEC 61850-7-3 and 7-3 are listed in the contents tables of the preview documents. The following Preview documents (free access) for models of the edition 2.1 consolidated versions are available:

Preview IEC 61850-7-3 Edition 2.1
Preview IEC 61850-7-4 Edition 2.1

Example of 7-4 from the preview:



In case you find any error in the standards, please visit the Tissue Database:
https://iec61850.tissue-db.com/parts.mspx

WOW -- IEC 61850 Models Publically Available for Download

After long time, IEC has accepted to provide free online access to the IEC 61850 Models!!

Congratulation!

Excerpt from 57/2023/INF (2018-07-13):

"With IEC 61850-7-7, a machine processable format for the distribution of IEC 61850 data models has been defined. Based on that, in the future, all IEC 61850 models will be as well available in this format as namespace files (NSD files).
The namespace files are code components, that are intended to be directly processed by a computer. The purchase of the associated IEC standard carries a copyright license for the purchaser to sell software containing Code Components from this standard to end users either directly or via distributors, subject to IEC software licensing conditions, which can be found at: http://www.iec.ch/CCv1. ..."

Screenshot from the TC 57 Supporting Documents page:



Click HERE to get to the above page.

Draft TR IEC 61850-7-6 published: Guideline for definition of Basic Application Profiles (BAPs) using IEC 61850

IEC TC 57 just published the 68 page draft Technical Report IEC 61850-7-6:

57/1986/DTR

Communication networks and systems for power utility automation –
Part 7-6: Guideline for definition of Basic Application Profiles (BAPs) using IEC 61850

Voting closes 2018-06-08.

"The IEC 61850 standard series offers a broad basis for communication networks and systems in power utility automation. Due to its broad coverage of power utility automation applications, it is up to the standard’s user (utility, vendor, system integrator…) to pick and choose specific options from the standard in order to meet the requirements of the intended objective. As a consequence, implementations of IEC 61850 represent specific subsets of the standard.
In the context of standards the term “profile” is commonly used to describe a subset of an entity (e.g. standard, model, rules).
Accordingly an IEC 61850 standard profile contain a selection of data models (mandatory elements), communication services applicable and relevant engineering conventions (based on the Substation Configuration Language SCL defined in IEC 61850-6) for an application function of a specific use case in the domain of power utility automation.
Depending on the scope and objective different profile types can be distinguished:

• User profile – defined subset that is valid for a specific user / organization (e.g. utility)
• Product / Device profile – implemented subset in a specific vendor product /device
• Domain profile – defined subset for a specific domain and relevant use cases (e.g. monitoring of substation)
• Application / function profile - subset covering a specific application or function (e.g. substation interlocking)

These profile types target on reducing complexity and facilitate interoperability for their specific scope and during engineering and device / substation lifetime. In order to achieve both these goals - a properly defined profile and appropriate implementations (processes, tools, products) that support the profile are required."

Note that IEC 61850 is not that complex - but it is very comprehensive!!
Comprehensiveness with regard to:

1. Number of parts: some 50 inclusing drafts
2. Number of Logical Nodes
3. Number of Data Objects
4. Configuration language
5. Number of task forces working on new stuff
6. Number of applications that can be covered
7. ...

The most crucial challenge is this: How can I find what may be of interest for my application? I hope somebody will do a good job in preparing an overview of models published and under preparation.
Let me know if you are aware of some good document or website ...

IEC 61850: Usage of XML Schemata for Model Name Space Definitions

One of the crucial challenges in dealing with IEC 61850 is the sheer unlimited amount of Models (Logical Nodes, Data Objects, Data Attributes, Data Attribute Types, ... and related Services). How to manage these? How to figure out which model was valid last year, which model details are currently valid, ... questions, questions ...
What are the answers to these questions? Simply: good documentation of content, modifications, extensions, and changes.
The IEC TC 57 WG 10 has published a document that defines the rules for model content of IEC 61850 based core data model in IEC 61850-7-2, IEC 61850-7-3 and IEC 61850-7-4. Other domains (like DER, Hydro, Wind, etc.) could define their own data model based on IEC 61850 core data model to be able to use IEC 61850 core parts as a common layer.

The published 70 page document 57/1925/DTS contains the new draft rules:

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

The voting and commenting period closes 2017-12-15

"Year after year the IEC 61850 data models are extended both in depth with hundreds of new data items, and in width with tens of new parts.
In order to foster an active tool market with good quality, and at the end to improve IEC 61850 interoperability, we need a machine-processable file describing data model related parts of the standard as input. This is the purpose the new language Name Space Definition (NSD) defined by this part of IEC 61850.
This will avoid the need for any engineering tool related to the IEC 61850 data models to get the content of the standard manually entered, with the highest risk of mistakes. This will also help spreading easily any corrections to the data model, as requested to reach interoperability. Tool vendors will be able to integrate NSD in their tools to distribute the standard data models directly to end users."

This new document seems to be crucial for all experts that deal with models and their implementation in Tools and IEDs.

IEC 61850-90-9 Models for Electrical Energy Storage Systems

IEC 61850 Part 90-9: Use of IEC 61850 for Electrical Energy Storage Systems is progressing these days. The latest draft describes the basic functions of Electric Energy Storage System (EESS) and the information model of the interface to integrate EESS in intelligent grids and establish the necessary communication with standardised data objects. The next official draft is expected to be published soon.
This draft  is  connected  with  IEC 61850-7-420,  as  well  as  IEC 61850-7-4:2010, explaining how the control system and other functions in a battery based electric energy storage unit utilizes logical nodes and information  exchange services  within the IEC 61850 framework to specify the information exchanged between functions as well as information that individual functions need and generate. The first Edition of IEC 61850-7-420 provides an information model for batteries which was derived from the proposed data objects of part 7-4. Those data objects follow the requirements of batteries that are supposed to be used in substations as an auxiliary power system and as backup power supplies. For this purpose it was sufficient to only model the discharge function. Therefore it is necessary to prepare new logical nodes to be applicable for grid connected electrical energy storage systems.
This draft provides necessary information within 61850 based object model in order to model functions of a battery based electrical energy storage system as a DER unit. For intelligently operated and/or automated grids, storing energy for optimising the grid operation is a core function. Therefore shorter periods of storing energy with charging and discharging capability is also an indispensable function. Charging and discharging operations need to be modelled thoroughly and are in the focus of this technical report.

The draft lists several use-cases found in the real world:

UC1 Retrieve current status and capabilities of EESS
UC2 Set charging power to EESS
UC3 Set discharging power to EESS
UC4 Set Operating mode/ schedule  to EESS
UC5 EESS Alarm / Asset Monitoring

UC1 current capability /status information as an example:

1-2-1 EESS Generic Status Reporting
•  ES-DER on or off
•  Storage available or not available
•  Inverter/converter active power output
•  Inverter/converter reactive output
•  Storage remaining capacity (% and/or kW）
•  Storage Free capacity (% and/or kW）

1-2-2 EESS inverter /converter status
•  Current connect mode:  connected or disconnected at its ECP
•  Inverter on, off, and/or in stand-by status: inverter is switched on (operating), off
(not able to operate), or in stand-by
•  mode, e.g. capable of operating but currently not operating
•  DC current level available for operation:　there is sufficient current to operate
•  Value of the output power setpoint
•  Value of the output reactive power setpoint
•  Value of the power factor setpoint as angle (optional)
•  Value of the frequency setpoint (optional)

1-2-3 EESS (battery) internal status
 •  Amp-hour capacity rating
•  Nominal voltage of battery
•  Maximum battery discharge current
•  Maximum battery charge voltage
•  High and　Low battery voltage alarm level
•  Rate of output battery voltage change
•  Internal battery voltage
•  Internal battery current
•  State of charge (energy % of maximum charge level)
•  Reserve (Minimum energy charge level allowed, % of maximum charge level)
•  Available Energy (State of charge – Reserve)
•  Type of battery

1-2-4 Power measurements
•  Total Active Power (Total P): Value, High and Low Limits
•  Total Reactive Power (Total Q): Value, High and Low Limits
•  Average Power factor (Total PF): Value, High and Low Limits, and averaging time
•  Phase to ground voltages (VL1ER, …): Value, High and Low Limits

More to come ...

Machine-processable Format of IEC 61850-related Data Models

IEC TC 57 proposes a new work item (57/1768/NP) IEC 61850-7-7:

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 (proposed 61850-7-7)

Closing date for voting: 2016-11-25

This technical specification will define an XML schema for describing the code components of the data model parts of IEC 61850, to be used as input for tools (typically engineering or specification tools).

In order to foster an active tool market with good quality, and at the end to improve IEC 61850 interoperability, the market needs a machine-processable file describing data model related parts of the standard as input.
This will avoid the need for any engineering tool related to the IEC 61850 datamodel to get the content of the standard manually entered, with the highest risk of mistakes.

The NP comes with a 150 page draft.

New Draft IEC TR 61850-7-500 Just Published - Typical Use Cases

IEC TC 57 has just published a very interesting document (75+ page Draft Report) - 57/1701/DC:
IEC TR 61850-7-500 – Use of logical nodes for modelling applications and related concepts and guidelines for substations

The draft provides examples and hints on how to use IEC 61850 for substation automation, protection and SCADA. Sample excerpt of content:

This document is crucial to understand use cases of the standard for substation applications.
Note that the examples given are showing just some possible applications. In practice there will be other use cases - depending on the philosophy of a specific utility. The use cases are not standardized!
In case a utility is looking for exchangeability of IEDs from different vendors, it has to specify the SCD file to a very high degree!
Recently I had a meeting with experts from a big transmission utility: They have reached a level of system specification in order to allow interoperability AND exchangeability of IEDs from multiple vendors! To get there: You need to request something more than just "IEC 61850".

What is an IEC 61850 Data Model – Come and See

Data or device modeling is a crucial feature of IEC 61850 and IEC 61400-25. You may have seen many different approaches to explain how such a model looks like. Some five years ago I used these Russian dolls (matryoshka doll):

An IED contains a lot of “inner” objects.

 

Today I have thought that another approach may help you to understand the IEC 61850 approach:

What do you think? This and more will be explained in detail during my comprehensive – most liked – courses.

Out-Of-Range Quality Flag and Reporting Quality-Change Event

In addition to the following two discussions that contain a view on measured values:

What Does Complexity of a Protocol Mean-
Are you prepared for the Solar Eclipse 2015 on March 20-

I will now look into the possibility to automatically monitor and report the limit violation of a measured value using standard configuration of IEC 61850 Information Models (LN STMP1), Data Sets and Report Control.

There are two options to report the temperature value reaching the maximum possible value: using the quality information of the “Tmp.q” (configured by the configuration of the “max” value in “rangeC”) or the “Alm” (configured by “TmpAlmSpt”) as depicted in the following figure:

We need to configure a Data Set and a Report Control Block for each case. In case of using “q” we have to communicate and interpret the “q” value “questionable and out of range” (which is a bit pattern!). In case of using the alarm data object “Alm” we just send and receive a simple Boolean value “True”. There is no need to interpret a bit pattern.

For machines it should be no big difference to analyze a bit pattern or a Boolean value.

Both approaches would provide the information that a measured value is higher than a specific limit (max or alarm limit). Which one you would like is up to you.

It is recommended that for specific domains it is specified in a “profile” document, which option to use. Maybe you want to use both: the “q” for asset management and the “Alm” for Automation functions to automatically start a cooling system. The “Alm” could easily be used for GOOSE messaging to inform a wide range of subscribers of the alarm …

The nice thing is that you can easily configure the multiple options just by SCL !! No programming needed – if the values of “q” and “Alm” are provided by the application.

Lesson learned: First define your need – then design the behavior of your Report and GOOSE messaging. If you don’t know what you want to accomplish, no standard can help you.

Are you prepared for the Solar Eclipse 2015 on March 20?

Why raise such a question on this blog that is about standards like IEC 60870-5-104 and IEC 61850 …? These are two good questions. Let’s discuss them briefly.

The Solar Eclipse 2015 and its impact on the power transmission system is discussed these days. The crucial issue is the minute-to-minute power gradient that may exceed between minus 400 MW/minute and plus 700 MW/minute; the highest gradient occurs when the PV in-feed returns at the end of the phase. This gradient may be managed by the TSO or not – who knows. We know it at lunch time on March 20, 2015.

There are many recommendations on the web, how to get prepared: having water, food, … for up to 10 days or so … I hope we will not need these.

@Question 2:

There is a need for the TSOs (just four in Germany!) to relay on good measurements from all-over in the grid and secure control possibilities to manage power plant in-feeds and substations. I guess they have good communication systems they can trust. These systems have been developed over many decades. They are tested and run reliably. Still. But what happens in future where we will have hundreds or millions of technical systems (embedded controllers …) that contribute to the system view and management?? Is this an issue at all?

Yes, it is a crucial issue. Let me discuss the following real-life incident reported last week:

A gateway in a virtual power plant provides the measured load on the network connection point of a CHP (combined heat and power) system. Normally the CHP feeds power into the network. But all in a sudden the VPP/TSO received a signal telling them a jump of the load from 0 MW to 600 MW!! Should the control center responsible for that part of the grid act or not? Hm. If this would be a real jump then it would have to react.

(Un)Fortunately the 600 MW jump was just a jump in the Value communicated!! It was caused by an error in the gateway (RTU kind of device). Was this value plausible? No. Because the CHP could just feed-in – not draw that much power from the grid.

With IEC 61850 in place we could easily expose the limits of power production and load. The logical node MMXU could be used for the limits in which a value is valid:

Data Object TotW of class MV (measured value) - Total active power (total P)

could provide the actual value, quality, range and the limits in the details provided through the MV CDC:

instMag.f	AnalogueValue coded as floating point
q	Quality
range	ENUMERATED normal|high|low|high-high|low-low (out of range would change quality value)
rangeC	RangeConfig: hhLim hLim lLim llLim min max

min: the min (minimum) attribute shall represent the minimum process measurement for which values of i or f are considered within process limits. If the value is lower, q shall be set accordingly (validity = questionable, detailQual = outOfRange).

max: the max (maximum) attribute shall represent the maximum process measurement for which values of i or f are considered within process limits. If the value is higher, q shall be set accordingly (validity = questionable, detailQual = outOfRange).

In our case, the TotW for the CHP generator may be limited between 0 W (min) and 35 kW (max). A value of “minus 600” MW would have to be flagged as questionable and outOfRange !! Negative values and values higher than 35 kW would be flagged out of range!

The receiver (a control center) could check the limits of the values (either by reading the range configuration online by a service or getting it from the corresponding SCL file). It could figure out that the range is 0-35 kW. Even if the gateway (RTU) would send “minus 600” MW (load) … the CC could understand that this is a bad value – recommended not to use.

The meta-data of the measured value serve as a means to help interpreting the plausibility of a value communicated.

IEC 61850 models add very useful information to help (a bit) keeping the power flowing. There are many other physical issues to take into account … but information and information exchange plays a crucial role!

VHPready Signal MMXU1.TotW.instMag – versus IOA 113

Signals configured in IEC 61850 and configured in IEC 60870-5-104 look quite different.

The following figure shows the same signal (Current electric Power – Aktuell erzeugte elektrische Leistung) in IEC 61850 (left) and IEC 60870-5-104 (right):

The IEC 61850 model exposes the value, quaity and timestamp as well as the semantic (TotalWatt). The total watt of what? Of the “Current electric Power – Aktuell erzeigte elektrische Leistung” as described in the DC (description of the signal).

On the other side we have the information object address (IOA = 113) that carries the same value in IEC 60870-5-104. What does the value 3456 mean? No idea in IEC 60870-5-104. You have to know upfront what 113 means. IEC 61850 stores the meaning in the device (model).

In the above case we see also the IOA=113 in the description (DC) of the IEC 61850 model. It is a text string attached to the DC attribute.

IEC 61850 Series is Growing to a Total of 45 Parts

IEC 61850 (Communication networks and systems for power utility automation) is a unique standards series providing a consistent set of standards, draft standards and other IEC publications.

A total of 45 parts cover many application domains in the Power Delivery System. An additional five (5) parts are published under the number IEC 61400-25 (extensions of IEC 61850 for Wind Power).

Document types of IEC:
IS = Standard
TR = Technical Report
TS = Technical Specification

21 Parts are already officially published. 24 draft parts are under preparation. Several drafts will be officially published in 2015.

The list of all documents:

  

In order to keep the crucial contents (mainly models and services) of these parts consistent, IEC TC 57 WG 10, 17, and 18 have done a tremendous work in converting the crucial contents into UML documents. This allows to extend and maintain the models with support of tools. In future we will see standard documents automatically derived from the UML Models.

Congratulation to all people contributing to this great standard series IEC 61850!

Some 20 years after the IEC TC 57 has decided (in 1995) to write a new standard for substation protection and automation, we see a lot of interest in many different application domains.

In case you need help to understand the many different parts and how they could contribute to solve needs you are faced with today and tomorrow – let me know please.

Even IEC 61850 is a huge Standard Series – it must be accompanied by REAL APPLICATIONS and underlying network infrastructure. The 7 ISO/OSI layers are just a foundation for IEC 61850 – both together are used by applications:

The applications of IEC 61850 can range from a simple polling of a temperature measurement up to comprehensive Schedules to manage distributed energy resources.

By the way: Te cake was very tasty!

What does IEC 61850 mean for Power Systems?

A lot. There are many different approaches to describe the benefits. You can start with the System Specification Description (SSD according to part IEC 61850-6, SCL) and go down to the signals and communication. Or you can describe it bottom-up. I like the bottom-up approach:

1. Take a signal (e.g. Voltage phase A in kV) coming trough a serial Modbus (Address 12122) by polling into an IEC 61850 Server device
2. Give it a NAME (MyMMXU1.PhV.phsA) based on a STANDARDIZED Structure (Logical Node MMXU), and
3. Use the protocol (MMS, ISO 9506) to just poll the current value with a MMS Read.

We may have 10 bays with each providing the voltage phase A: then we could model this as follows:
Bay1MMXU1.PhV.phsA
Bay2MMXU1.PhV.phsA
Bay3MMXU1.PhV.phsA
...
Bay10MMXU1.PhV.phsA

That's some basic benefit ... for a first “"brief introduction”.

In addition (there are many other features to look at), e.g.:

1. MMS allows to retrieve the Signal List (device model comprising all logical nodes ...) ...
2. The system configuration language (SCL) allows to carry the "signal list" in form of an XML file ...
3. SCL could carry the complete signal flow between any device in a system: who has which signal to offer, who needs which signal, how are signals carried between the many devices (real-time, non-realtime ...) ...
4. SCL could carry the single line diagram (topology) of an electrical system ...
5. SCL could carry how the information is related to the single line diagram ...
6. …

So, does IEC 61850 add to the complexity of power systems? No that much! See also:

http://blog.iec61850.com/2014/10/does-iec-61850-add-complexity-for.html

Be aware: There is more than IEC 61850 that has to be learned, understood and managed!

IEC 61850 – How to use the Standard in Substations?

The German mirror committee of IEC TC 57 (DKE K 952) is quite active in supporting IEC 61850 and helping the utility industry to discuss the application of IEC 61850 and provide feedback to the international standardization. Congratulation to all experts that have contributed to that work for many years! Well done!
The final documents of the modeling and engineering group provide a great inside view into the many use cases of IEC 61850 in protection and substation automation. The crucial results are written in English, too. Four out of seven topics are published in English:

1. Überblick [DE] / Overview [EN]
2. Engineeringprozess [DE] / Engineering Process [EN]
3. Engineeringwerkzeuge [DE]
4. Modellierungsrichtlinie [DE] / Modeling Guide [EN]
5. Mustermodellierung [DE]
6. Applikationsbeschreibungen [DE] / Application Description [EN]
7. Weitere Applikationen [DE]

Click HERE to access the above documents. The pdf documents are free to download.
Enjoy.

IEC 60870-5-104 and IEC 61850 for Vattenfall’s VHP-Ready (Virtual Heat and Power Ready) Version 3.0

Vattenfall Europe Wärme AG has published Version 3.0 (October 2012) of their technical specification for virtual power plants: VHP-READY – Virtual Heat & Power Ready. This version comprises a complete profile of models for use of both standards. A detailed list of Signals respective Logical Nodes and Data Objects has been specified.

The new version specifies the use of IEC 60870-5-104 and IEC 61850:

• IEC 60870-5-104 or IEC 61850 / 61850-7-420 (two options)
• TCP/IP
• SSL/TLS
• SNTP/NTP

Download the complete specification version 3.0 [German only, pdf, 670 KB].

This specification is exactly what the market needs to do: Specify in some level of details what is required for a typical application!

Congratulation to Vattenfall to lead the market (to a great extent) in preparing and presenting a publicly available specification of a profile for virtual power plants based on two international Standards: IEC 60870-5-104 and IEC 61850 (IEC 61850-7-420).

IEC 61400-25 is based on IEC 61850

During the year 2012 I have received more often the question about the relation between IEC 61400-25 and IEC 61850.

The most crucial issue in understanding IEC 61400-25 is this: The standard series IEC 61400-25 is based on the series IEC 61850 (mainly part 7-x, 8-1). A lot of definitions and basics defined in IEC 61850 are not repeated in IEC 61400-25. The part 6 (Configuration language) is not referenced in IEC 61400-25 at all and so on.

Could part IEC 61850-6 be used for IEC 61400-25? Yes, it could be used in almost all implementations of IEC 61400-25. Why? Because usually the implementation of the communication uses the mapping to MMS according to IEC 61850-8-1 which is referenced in IEC 61400-25-4.

To really understand IEC 61400-25, one needs to have a very good basic understanding of IEC 61850.

The standard IEC 61850 could be understood as extended IEC 61850 information models. There are a few special definitions in IEC 61400-25-2 which deviate partly from IEC 61850-7-3 and 7-4.

Example: LN WGEN – Generator

That model comprises among other data objects the objects for 3 phase currents and voltages for the stator and for the rotor:

The argument why the electrical measurements are contained in the LN WGEN is simple: The Generator generates voltages and currents … so these measurements are an integral part of the generator! Full stop. In IEC 68150 the modeling approach is to find the smallest parts of information to be exchanged by a function to be modeled.

The electrical measurements in IEC 61850-7-4 are contained in the LN MMXU. To indicate the use for the stator or rotor could be indicated by a prefix in the instance name: Sta_MMXU.A and Rtr_MMXU.A.

Note how the instance names are build (according to IEC 61850-7-2 Edition 2):

 
 
During the ongoing maintenance work on the first five parts of IEC 61400-25 it could be expected that the information models of IEC 61400-25-2 and IEC 61850-7-x will be harmonized as much as possible.

Note that the models may be different – there may be two model, but there is only one real world. The real world does not change depending on models! On the other side, models should be harmonized to a high degree … to prevent confusion. I have seen models implemented for a wind turbine that use MMXU instead of the models in WTUR.

The key issue is: different people and groups have different understanding of modeling!

Video with brief Introduction to IEC 61850 and IEC 61400-25

IEC 61850 and IEC 61400-25 comprise some 25 documents. Part IEC 61850-7-1 contains some basic modeling concepts that may help to get a few ideas what IEC 61850 is about. I guess that just a few people have read that part. In my training courses with almost 3.000 attendees I have gained a lot of experience on how to explain the basic concepts. In 2011 I have conducted more than 30 training sessions (from one to 12 days). Today I am starting a new service to the industry: providing videos that explain basics with animated up-to-date slides.

The first video is a brief presentation of the key concepts of IEC 61850 (one slide): modeling methods, models, configuration language, communication, and mappings. The demonstration shows how these concepts are used to compose a system. Of course, this slide is just showing the basics of a “small system”. This slide is part of the introduction of my commercial training curses.

Please click on the start button to see the video – in order to see it in the full screen, click again on the video and select the full screen button.

I hope you will enjoy this video!
Your feedback to Karlheinz Schwarz would be appreciated.

Modeling Circuit Breakers for Single and Three Phases

Models for switchgear are defined in IEC 61850-7-4 Edition 2. The model defines several aspects like controlling and monitoring of real circuit breaker switchgear:

XCBR excerpt of model:

XCBR represents usually one (1 phase) circuit breaker. In some special cases it may represent all three (3 phase) circuit breaker. If you want to trip all three CBs of a 3-phase system, you have to define an instance 1 for that purpose: e.g., All_XCBR1.

In case you want to model the case to trip a single phase CB, you have to model 3 instances of XCBR, e.g., A_XCBR1, B_XCBR2, C-XCBR3.

The data object XCBR.SumSwARs represents the “Sum of switched amperes, resettable”. What to do when you want to model the SumSwARs of all three phases?

I saw this model the other day: extended data objects:SumSwARs1, SumSwARs2, SumSwARs3 … for Phase A, B, and C in a single XCBR instance:

From a general modeling point of view this could be done (it is not wrong!) – But it is highly recommended not to do! Since a XCBR is usually representing a single CB then we need 1 instance per phase. A_XCBR1 would represent the sum of switched amperes of Phase A. The All-XCBR1 (see above) could represent the sum of switched amperes of all 3 CBs.

Building the 21st Century Grid – The White House reports today

On June 13, 2011, the White House will hold an event on "Building the 21st Century Grid." Starting at 10 a.m., the event can be watched live at http://www.whitehouse.gov/live.

Federal Smart Grid Initiatives highlights key government-sponsored programs and activities related to the development and modernization of the electric grid in the United States.

One of the four pillars of the future grid is:

Unlock the innovation potential in the electricity sector with a continued focus on open standards.

I hope that the electric power industry will follow a few open standards instead of a myriad of solutions. Could you imagine a situation were each state or county would have a different frequency and voltage of the electric system!??

There are two main standards: 230V/50Hz and 110V/60Hz … but there should be one standard to exchange information (measurements and statuses, …). The MMXU (a measurement model of 3 phase electrical system defined in the open standard IEC 61850-7-4) could be used for any kind of 3 phase system.

Click HERE for some more models.

If you are interested you may watch the event today.

IEC 61850 provides a lot for the Smart Electrification

The recently published IEC white paper :

Coping with the Energy Challenge
The IEC’s role from 2010 to 2030
Smart electrification – The key to energy efficiency

discusses the need of standards! No surprise, or?

Click HERE to download the white paper [pdf, 1,9 MB]

The paper concludes on page 51:

"The standards should cover connection (especially of fluctuating sources), stability, “intelligence” (required functions of the IT applications controlling the grid), and minimum systemic efficiency as well as how to measure it. Aspects to deal with include balancing demand and generation, power quality, harmonic current emissions, voltage flicker, voltage fluctuation and islanding prevention. The standards should allow for the necessary differences in approach and choices made in different countries; thus some of the resulting publications may be non-normative.
In order to facilitate implementation, the MSB [IEC Market Strategy Board] further recommends the IEC and cooperating organizations to organize a public symposium on what the necessary standards and other IEC publications on the “smart grid” should contain."

The paper states at very beginning:

"As the first IEC President, Lord Kelvin, always said: “If you cannot measure it, you cannot improve it!”. This statement is especially true here: without measurement you can’t credibly demonstrate energy efficiency improvements. The IEC provides and will continue to provide many of the measuring standards that are the basis for benchmarking, energy audits and compliance assessments."

The edition 2 of IEC 61850-7-4 (Information models) covers already many models of these measurements:

5.10 Logical nodes for metering and measurement LN Group: M
5.10.2 LN: Environmental information Name: MENV
5.10.3 LN: Flicker measurement name Name: MFLK
5.10.4 LN: Harmonics or interharmonics Name: MHAI
5.10.5 LN: Non-phase-related harmonics or interharmonics Name: MHAN
5.10.6 LN: Hydrological information Name: MHYD
5.10.7 LN: DC measurement Name: MMDC
5.10.8 LN: Meteorological information Name: MMET
5.10.9 LN: Metering Name: MMTN
5.10.10 LN: Metering Name: MMTR
5.10.11 LN: Non-phase-related measurement Name: MMXN
5.10.12 LN: Measurement Name: MMXU
5.10.13 LN: Sequence and imbalance Name: MSQI
5.10.14 LN: Metering statistics Name: MSTA

5.12 Logical nodes for power quality events LN Group: Q
5.12.2 LN: Frequency variation Name: QFVR
5.12.3 LN: Current transient Name: QITR
5.12.4 LN: Current unbalance variation Name: QIUB
5.12.5 LN: Voltage transient Name: QVTR
5.12.6 LN: Voltage unbalance variation Name: QVUB
5.12.7 LN: Voltage variation Name: QVVR

Click HERE for the preview of IEC 61850-7-4 (first 20 pages) to see the complete list of Logical Nodes defined.

If there is any (measurement) information found in real electrical system not yet modeled and standardized, you can define extension according to well defined extension rules in IEC 61850-7-1 (name space concept).

There is no need to define another series of (information models and information exchange) standards for electrical grids.