SIST EN 61850-7-1:2012/A1:2020

SLOVENSKI STANDARD
01-december-2020
Komunikacijska omrežja in sistemi za avtomatizacijo porabe (električne) energije -
7-1. del: Osnovna komunikacijska struktura - Načela in modeli - Dopolnilo A1
Communication networks and systems for power utility automation - Part 7-1: Basic
communication structure - Principles and models
Kommunikationsnetze und -systeme für die Automatisierung in der elektrischen
Energieversorgung - Teil 7-1: Grundlegende Kommunikationsstruktur - Grundsätze und
Modelle
Réseaux et systèmes de communication pour l'automatisation des systèmes électriques
- Partie 7-1: Structure de communication de base - Principes et modèles
Ta slovenski standard je istoveten z: EN 61850-7-1:2011/A1:2020
ICS:
29.240.30 Krmilna oprema za Control equipment for electric
elektroenergetske sisteme power systems
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 61850-7-1:2011/A1

NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2020
ICS 33.200
English Version
Communication networks and systems for power utility
automation - Part 7-1: Basic communication structure -
Principles and models
(IEC 61850-7-1:2011/A1:2020)
Réseaux et systèmes de communication pour Kommunikationsnetze und -systeme für die
l'automatisation des systèmes électriques - Partie 7-1: Automatisierung in der elektrischen Energieversorgung -
Structure de communication de base - Principes et modèles Teil 7-1: Grundlegende Kommunikationsstruktur -
(IEC 61850-7-1:2011/A1:2020) Grundsätze und Modelle
(IEC 61850-7-1:2011/A1:2020)
This amendment A1 modifies the European Standard EN 61850-7-1:2011; it was approved by CENELEC on 2020-10-05. CENELEC
members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this amendment the
status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This amendment exists in three official versions (English, French, German). A version in any other language made by translation under the
responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as
the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Turkey and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2020 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 61850-7-1:2011/A1:2020 E

European foreword
The text of document 57/2201/FDIS, future IEC 61850-7-1/A1, prepared by IEC/TC 57 “Power
systems management and associated information exchange” was submitted to the IEC-CENELEC
parallel vote and approved by CENELEC as EN 61850-7-1:2011/A1:2020.
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2021-07-05
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2023-10-05
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
This document has been prepared under a mandate given to CENELEC by the European Commission
and the European Free Trade Association.
Endorsement notice
The text of the International Standard IEC 61850-7-1:2011/A1:2020 was approved by CENELEC as a
European Standard without any modification.
Remove the following reference:
IEC 61400 series NOTE Harmonized in EN 61400 series.

IEC 61850-7-1 ®
Edition 2.0 2020-08
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
A MENDMENT 1
AM ENDEMENT 1
Communication networks and systems for power utility automation –

Part 7-1: Basic communication structure – Principles and models

Réseaux et systèmes de communication pour l'automatisation des systèmes

électriques –
Partie 7-1: Structure de communication de base – Principes et modèles

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 33.200 ISBN 978-2-8322-8481-0

– 2 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
FOREWORD
This amendment has been prepared by IEC technical committee 57: Power systems
management and associated information exchange.
The text of this amendment is based on the following documents:
FDIS Report on voting
57/2201/FDIS 57/2221/RVD
Full information on the voting for the approval of this amendment can be found in the report
on voting indicated in the above table.
The committee has decided that the contents of this amendment and the base publication will
remain unchanged until the stability date indicated on the IEC website under
"http://webstore.iec.ch" in the data related to the specific publication. At this date, the
publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
_____________
4 Abbreviated terms
Add the following new terms to the list of abbreviated terms:
MICS Model implementation conformance statement
PICS Protocol implementation conformance statement
SICS SCL implementation conformance statement
5 Overview of the IEC 61850 series concepts
5.3 The information models of substation automation systems
Add, at the end of the third paragraph below Figure 3, the following new footnote:
There is one exception: the proxy/gateway application. For details, refer to 8.2.3 Gateways and proxies.

IEC 61850-7-1:2011/AMD1:2020 – 3 –
© IEC 2020
5.4 Applications modelled by logical nodes defined in IEC 61850-7-4
Figure 4 – Logical node information categories
Replace existing Figure 4 with the following new figure:

5.5 The semantic is attached to data
Figure 6 – Position information depicted as a tree (conceptual)
Replace existing Figure 6 with the following new figure:

– 4 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Replace the first table of Subclause 5.5 with the following new table:
Attribute Attribute type FC TrgOp (Value/value range) Description PresCond
name
stVal DpStatusKind ST dchg Status value of the controllable data object. M
ctlModel CtlModelKind CF dchg Control model as defined in IEC 61850-7-2 M
that reflects the behaviour of the
controllable data object.
Below this table, replace the last item of the dashed list with the following new item:
– the presence conditions, e.g. mandatory (M) or optional (O). These conditions specify
presence of elements in a given context (one LN, or one CDC, or one data attribute type,
or one data object for dataNs) and are specified in IEC 61850-7-2.
After the dashed list, replace the first paragraph and the following table with the following new
paragraph:
The data attribute names are standardised (i.e., they are reserved) names that have a specific
semantic in the context of the IEC 61850 series. The semantic of all data attribute names is
defined in IEC 61850-7-3.
IEC 61850-7-1:2011/AMD1:2020 – 5 –
© IEC 2020
6 Modelling approach of the IEC 61850 series
6.2 Creating information models by stepwise composition
Table 2 – Logical node class XCBR (conceptual)
Replace existing Table 2 with the following new table:
Descriptions
External equipment name plate
Name plate of the logical node
Controls
Switch position (see below for details)
Block opening
Block closing
Charger motor enabled
Control authority at station level. Switches between station and higher level.
…
Status information
Mode
Behaviour
Health
External equipment health
Operation counter
Local operation (Indicates the switchover between local and remote operation;
local =TRUE, remote =FALSE)
Circuit breaker operating capability
Point on wave switching capability
Circuit breaker operating capability when fully charged
…
Replace the existing table below Figure 11 with the following new table:
Data object
Explanation
name
... ...
Pos (controllable) Circuit breaker/switch position.
... ...
6.4.2 Output model
6.4.2.1 Control model concept
Figure 14 – Output model (step 1) (conceptual)
Replace existing Figure 14 with the following new figure:

– 6 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Figure 14 – Output model (step 1) (conceptual)

6.4.2.2 GSE and SMV model concept
Add the following new text after the paragraph below Figure 16:
The act of receiving GOOSE and SMV messages by an IED is called subscription. How to
define subscriptions by means of configuration tools is given in the normative Annex H.
6.4.2.4 Setting data and setting group control block
Table 3 – Excerpt of integer status setting
Replace existing Table 3 by the following new table:
ING class
Attribute Attribute FC TrgOp Value/value range PresCond
name type
DataAttribute for configuration, description and extension
setting
setVal INT32 SP dchg The value of the status setting. AtMostOne
setVal INT32 SG, SE The value of the status setting. AtMostOne
configuration, description and extension
minVal INT32 CF dchg Minimum setting for 'setVal'. O
maxVal INT32 CF dchg Maximum setting for 'setVal'. O
stepSize INT32U CF dchg (range=[1.(maxVal-minVal)]) Step between the O
individual values of 'setVal'.
units Unit CF dchg Unit for 'setVal', 'minVal', 'maxVal', 'stepSize'. O
d VISIBLE DC Textual description of the data. In case it is used within O
STRING255 the CDC LPL, the description refers to the logical node.
... ... ...  ...
IEC 61850-7-1:2011/AMD1:2020 – 7 –
© IEC 2020
6.4.3 Input model
6.4.3.2 Data attribute value processing, monitoring and event detection
Replace the last sentence of the second paragraph with the following new sentence:
The value of mag shall be updated to the current value of instMag when the value has
changed according to the value of the configuration parameters db and dbRef of this data.
Replace Figure 19 and the subsequent paragraph with the following new figure and text:

Figure 19 – Range and deadbanded value (conceptual)
The value of the deadband configuration db shall represent the percentage of the deadband
reference dbRef in units of 0,001 % (fixed deadband). A value of dbRef of 0 means that the
value db shall represent the percentage of the last transmitted values in units of 0,001 %.
This allows for a deadband calculation that is related to the last refreshed value (variable
deadband).
Figure 20 – Input model for analogue values (step 2) (conceptual)
Replace existing Figure 20 with the following new figure:

– 8 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Remove the fourth paragraph below Figure 20.
6.4.3.3.2 Data reporting
Replace existing Table 4 with the following new table:
Table 4 – Comparison of the data access methods
Retrieval Time-critical Can lose Multiple Last change Typical client
method information changes (of clients to receive of data stored (but not
exchange sequence) information by exclusive)
Polling NO YES YES – Browser
(GetDataValues)
Unbuffered YES YES NO – Real-time GUI
Reporting
Buffered YES NO NO Server Data
Reporting concentrator
Log (used for NO NO YES Server Engineering
SOE logging) stations
Replace the existing paragraph before Figure 23 with the following new text:

IEC 61850-7-1:2011/AMD1:2020 – 9 –
© IEC 2020
The basic buffered reporting mechanism is shown in Figure 23. The buffered and unbuffered
reporting starts with the reservation of the report control block by the client, followed by
configuration of the report control block, including the verification that the report control block
parameters are meeting the needs of the client. The reporting to the client starts with setting
the enable buffer attribute to TRUE; setting to FALSE stops the reporting to the client.
Before the last sentence of the first paragraph below Figure 23 add the following new
sentence.
The buffering is independent from the reporting being enabled or not.
6.4.3.4 Peer-to-peer data value publishing
Replace the last paragraph of 6.4.3.4 by the new following new text:
Which event triggers the publishing of values as well as how often and how fast the values
are to be published is a matter of the requirements of the function being implemented.
6.4.4 Model for statistical and historical statistical data
Figure 28 – Conceptual model of statistical and historical statistical data (1)
Replace existing Figure 28 with the following new figure:

– 10 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Replace the penultimate paragraph before Figure 29 with the following new text:

The lower part of the figure shows the conceptual model of the historical statistical data. In
this model, the values are calculated periodically (in this case the maximum values with
calculation mode set to PERIOD) and are stored in sequence in a log. The calculation in the
example starts at midnight of 2004-10-03. The interval is 1 h. After the first hour, the first log
entry is written. After the second hour, the second entry contains the value of the second
hour. After 5 h, the log contains the values of the last three hours (intervals 02-03, 03-04, 04-
05). The expiration of the statistical calculation is indicated by the “event” ClcExp set to TRUE
and at this moment the statistical values that have the trigger option dupd are logged even if

IEC 61850-7-1:2011/AMD1:2020 – 11 –
© IEC 2020
the values have not changed. The same concept can be applied to the reporting of statistical
data.
Remove the last paragraph of Subclause 6.4.4.
6.4.5 Model for system functions
6.4.5.1 General
Remove the last two sentences of Subclause 6.4.5.1.
6.4.5.5 GOOSE and SMV supervision
Add the following new text at the end of Subclause 6.4.5.5:
The normative Annex G describes the configuration flow with regards to these supervision
logical nodes.
7 Application view
7.3 Mode and behaviour of a logical node
Replace “on-blocked” by “blocked” in the first paragraph below Figure 37.
7.7 Data used for logical node inputs/outputs blocking (operational blocking)
Figure 39 – Data used for logical node inputs/outputs blocking (IEC 61850-7-4)
Replace existing Figure 39 by the following new figure:

7.7.2 Blocking incoming commands
Add, at the end of the last paragraph of Subclause 7.7.2, the following new text:

– 12 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
or CmdBlk itself.
7.7.3 Blocking process outputs
Replace the existing text of Subclause 7.7.3 by the following new text:
The data Mod (Mode) is used to put an LN in different modes. The mode test/blocked (Beh=
test/blocked or Beh=blocked) shall be interpreted as the mode which explicitly disables any
physical outputs having an effect on the process. For example, when
XCBR.Beh = test/blocked or blocked, the physical outputs for closing/opening the breaker do
not operate and the breaker does not close or open respectively.
7.7.4 Blocking oscillating inputs
Replace the title of 7.7.4 with the following new text:
Blocking the communication of status outputs updates
Replace the first sentence of 7.7.4 with the following new text:
An operator, or an automatic function, may block the update of the value of communication
outputs (e.g. updates related to oscillating inputs).
7.8 Data used for testing
7.8.2 Multicast signals used for simulation
Replace the third paragraph of 7.8.2 with the following new text:
To allow the IED1 to process the simulated GOOSE 1 message instead of the actual GOOSE
message, the data Sim.stVal in the LN LPHD1 shall be set to TRUE. The process of the
simulated message only takes effect upon receiving the first simulated message. This will
remain as such until Sim.stVal is set back to ‘FALSE’. The processing of the simulated
message is made on a per GOOSE/SMV basis, i.e. the other signals, GOOSE 2 and GOOSE
3, are normally processed by the IED1. Note that the switching between normal signals and
simulated signals shall be done for the entire IED. In the example, this means that if a new
simulated GOOSE 2 signal appears, it will replace the actual GOOSE 2 signal. The preceding
example does not imply any specific sequence with regards to connecting the simulation
device and setting the data Sim.stVal to TRUE. Different sequences may be used. However, a
state machine diagram can be found in Figure 80 and Figure 81 that describes the different
states involved and illustrates the supervision of GOOSE/SV subscription with regards to the
active subscription state resp. the subscription to simulated stream. The affected Data
Objects are defined in the Logical Nodes LGOS and LSVS in IEC 61850-7-4.
Add, at the end of the third paragraph of 7.8.2, the following new Figures 80 and 81:

IEC 61850-7-1:2011/AMD1:2020 – 13 –
© IEC 2020
Figure 80 – GOOSE subscription supervision state machine

Figure 81 – SV subscription supervision state machine
7.8.3 Input signals used for testing
Figure 41 – Example of input signals used for testing
Replace existing Figure 41 with the following new figure:

– 14 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Add the following new text at the end of the last paragraph of 7.8.3:
The signal specified in setTstRef, the associated control block srcTstCB shall be consistent
and relate to a fully configured (i.e. including the communication configuration when
necessary) control block in the SCD file.
7.8.4 Test mode
Figure 42 – Test mode example
Replace existing Figure 42 by the following new figure:

Replace the last paragraph of Subclause 7.8.4 with the following new text:

IEC 61850-7-1:2011/AMD1:2020 – 15 –
© IEC 2020
The detailed requirements for the different states of Mod/Beh can be found in IEC 61850-7-4.
8 Device view
8.2 Second modelling step – logical device model
8.2.1 The logical device concepts
Replace the second paragraph below Figure 44 with the following new text:
In the example of Figure 45, logical device “LD1” contains three logical nodes: LLN0, LPHD
and LN, the latter representing an application specific LN as defined in the IEC 61850-7-x
series. The logical node zero (LLN0) represents common data of the logical device. For
example, the mode of LLN0 is used to control the mode of the whole logical device and, as a
result, the mode of every logical node being part of the logical device. The logical node
physical device (LPHD) represents common data of the physical device hosting the logical
device. LLN0 shall be defined in every logical device while LPHD shall be defined in at least
one logical device. There exist many other system logical nodes (Group L) belonging to the
IED, e.g. LTRK which allows tracking of service parameters for a server within the IED or
LTIM which serves for diverse configurations regarding the local time of an IED. Figure 45
shows an example of a good practice. The logical device called “SYS” groups all system
logical nodes belonging to the same IED. Note that these system logical nodes could also be
spread in a hierarchy of logical devices (see 8.2.5).
8.2.3 Gateways and proxies
Replace the existing text of Subclause 8.2.3, including Figure 47, with the following new text
and figures:
Gateways are network interconnection devices that translate protocols to other protocols. For
example, gateways may convert non IEC 61850 data into IEC 61850 data.
Proxies are special devices that mirror logical devices located in other IEC 61850 physical
devices. Hence, these logical devices are, from a functional point of view, transparent. They
can be identified independently of their location (in a separate device connected to the
network or in a proxy device).
Logical devices allows for the building of proxies and/or gateways.
Figure 47 shows how a physical device is mapped to a device acting as a proxy and/or a
gateway. In the figure, LN refers to an application specific LN as defined in the IEC 61850-7-x
series.
The logical device IED1LD1 is “copied” to the proxy/gateway. The LPHD of IED1LD1 in the
proxy/gateway represents the physical device IED1.
Logical devices that mirror logical devices of other physical devices shall provide a LPHD that
represents the remote physical device on which the original LD resides (e.g., IED1LD1).
These logical devices shall have the data LPHD.Proxy.stVal of the LPHD set to TRUE.
Logical devices that do not mirror logical devices of other physical devices shall provide a
LPHD that represents the physical device on which they reside. In Figure 47, this logical
device is PXY_GTW1LD1, which shall be implemented to represent the information about the
proxy/gateway itself. The logical nodes LLN0 and LPHD of this logical device shall represent
information about the proxy/gateway device. The logical device may also contain domain
specific logical nodes.
– 16 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
In the example, the physical device IED2 is also proxied by the proxy/gateway. The device
contains a hierarchy of logical devices. In this case, the LPHD that represents the remote
physical device in the proxy/gateway is declared only at the root of the hierarchy.
Figure 47 also shows how non IEC 61850 external physical devices are mapped to the
proxy/gateway device. IED3LD1 is used to represent the information related to the non
IEC 61850 physical device IED3. The LPHD of IED3LD1 represents the physical device IED3.
The data supplied by IED3 is mapped to different logical nodes into IED3LD1.

IEC 61850-7-1:2011/AMD1:2020 – 17 –
© IEC 2020
Figure 47 – Logical devices in proxies or gateways

– 18 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Figure 79 shows the same example using the functional naming of the logical devices. One
can see that it is possible to make the names of the proxied logical devices exactly the same
as the ones in the source logical devices. This is possible as long as the respective access
points (Server of the Proxy and original Server) are not connected to the same network: the
name of the logical device shall be unique within the scope of a network.

Figure 79 – Logical devices in proxies or gateways (functional naming)

IEC 61850-7-1:2011/AMD1:2020 – 19 –
© IEC 2020
8.2.4 Logical devices for monitoring external device health
Figure 48 – Logical devices for monitoring external device health
Replace existing Figure 48 with the following new figure:

8.2.5 Logical devices management hierarchy
In the second paragraph of Subclause 8.2.5, replace “object reference setting group” with
“object reference setting”.
Replace the third and fourth items in the dashed list with the following new text:
– the logical node class LPHD shall be present in any root logical device, i.e. any LD where
the LLN0 does not contain a data object GrRef. It may also be present at other levels of
the hierarchy,
– a proxy LD shall only be present at the root logical device, applying to all other level of the
associated hierarchy,
9 Communication view
9.2 The service models of the IEC 61850 series
Table 5 – ACSI models and services
Replace, in Table 5, the row "Transmission of sampled values" with the following new row.

– 20 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Transmission of Fast and cyclic transfer of samples, for example, of Multicast SVC:
sampled values instrument transformers. SendMSVMessage
GetMSVCBValues
SetMSVCBValues
GetMsvReference
GetMSVElementNumber
9.6 Logical nodes communicate with logical nodes
Figure 60 – Logical nodes communicate with logical nodes
Replace existing Figure 60 with the following new figure:

Replace the last paragraph of Subclause 9.6 with the following new text:
Note that the SCL configuration language (see IEC 61850-6) allows the configuration of the
data flow between LNs using elements “ExtRef” (see Annex H).

IEC 61850-7-1:2011/AMD1:2020 – 21 –
© IEC 2020
11 Relationships between IEC 61850-7-2, IEC 61850-7-3 and IEC 61850-7-4
11.2 Example 1 – Logical node and data object class
Replace the first paragraph of Subclause 11.2 with the following new text:
Table 6 shows an example of a list of data object classes for a circuit breaker. The name of
the circuit breaker class is "XCBR". The data object classes that make up the circuit breaker
are grouped into four categories (descriptions, status information, controls, and settings).
Each category comprises some data object classes, for example, "Mode" and “Switch
position”. These data object classes are referenced by their data object name: "Mod" and
"Pos". To be more precise, each data object class also has a common data class, defining the
details, i.e. the attributes of the data object class. The last column specifies the presence
conditions that can be applicable to the data object class, i.e. whether this data object class is
mandatory (M), optional (O), in some cases forbidden (F) or can be instantiated many times
(multi). This column specifies two contexts for the presence conditions: nds for the common
context of Non Derived Statistical case and ds for the specific context where the LN instance
is derived from another one (Derived Statistical). Refer to IEC 61850-7-4 for a detailed
explanation. It follows that for each data object two presence conditions are expressed, one
object in case of nds context and a second in case of ds context. For example, the data object
Pos is mandatory (M) in the nds context and forbidden in the ds context (F).
Replace existing Table 6 by the following new table:

– 22 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Table 6 – Logical node circuit breaker
Logical Node: Circuit breaker Name: XCBR
Data object Class Data object Common Data Class (CDC) PresCond
Name nds/ds
Descriptions
Name plate of the logical node. NamPlt LPL – Logical node name plate MONamPlt/
MONamPlt
Name plate of external (electrical, mechanical EEName DPL – Device name plate O/F
or communication) equipment to which the
logical node is associated.
Controllable Data
(controllable) Operating mode of the domain Mod ENC – Controllable integer status O/O
logical node that may be changed by operator.
Processing of the quality status ('q') of the
received data is the prerequisite for correct
interpretation of the operating mode.
(controllable) Circuit breaker/switch position. Pos DPC – Controllable Double Point M/F
(controllable) If TRUE, 'open' action has been BlkOpn SPC – Controllable single point M/F
blocked; can be set from another logical node.
Operating capability ('XCBR.CBOpCap' and
'XSWI.SwOpCap' for circuit breaker and switch,
respectively) does not reflect the blocked
opening.
(controllable) If TRUE, 'close' action has been BlkCls SPC – Controllable single point M/F
blocked; can be set from another logical node.
Operating capability ('XCBR.CBOpCap' and
'XSWI.SwOpCap' for circuit breaker and switch,
respectively) does not reflect the blocked
closing.
(controllable) If TRUE, the charger motor, used ChMotEna SPC – Controllable single point O/F
to prevent overload of the power supply after a
busbar trip, has been enabled.
(controllable) If TRUE, control authority is at LocSta SPC – Controllable single point O/F
station level and control from remote is
disabled; otherwise control from remote is
allowed.
Status information
Read-only value, describing the behaviour of a Beh ENS – Integer status M/M
domain logical node. It depends on the current
operating mode of the logical node
('DomainLN.Mod'), and the current operating
mode of the logical device that contains it
('LLN0.Mod'). Processing of the quality status
('q') of the received data is the prerequisite for
correct interpretation of 'DomainLN.Beh'.
Reflects the state of the logical node related Health ENS – Integer status O/O
hardware and software. More detailed
information related to the source of the problem
may be provided by specific attribute of the
logical node.
If TRUE, the control behaviour is allowed at this Loc SPS – Single point status M/F
level.
State of external (electrical, mechanical or EEHealth ENS – Integer status O/F
communication) equipment to which the logical
node is associated.
Count of operations; not resettable from OpCnt INS – Integer status M/O
remote, but may be reset from local.
If TRUE, the operation has been switched (from LocKey SPS – Single point status O/F
remote) to local. This changeover is always
done locally with a physical key or toggle
switch, which may have a set of contacts from
which the position can be read.

IEC 61850-7-1:2011/AMD1:2020 – 23 –
© IEC 2020
Logical Node: Circuit breaker Name: XCBR
Data object Class Data object Common Data Class (CDC) PresCond
Name nds/ds
Physical capability of the circuit breaker to CBOpCap ENS – Integer status
O/F
operate, which reflects the available energy in
the drive.
Point on wave switching capability POWCap ENS – Integer status
O/F
Operation capability available when the switch MaxOpCap ENS – Integer status
O/O
mechanism is fully charged, as the maximum
number of close-open cycles to be performed.
For example when one close-open cycle can be
performed, 'MaxOpCap'=1.
Setting information
Closing time of the breaker. The time is used to CBTmms ING – Integer setting O/F
compensate for the breaker closing time, i.e.,
the closing command will be given a defined
time before phase coincidence. This is a
property of the breaker that is subject to
ageing.
Replace existing Table 7 by the following new table:

– 24 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
Table 7 – Controllable double point (DPC)
cdcId = DPC, UML class name = DPC
Attribute Attribute type FC TrgOp (Value/Value range) Description PresCond
name
DataAttribute for status
origin Originator ST See 'SPC.origin'. O
ctlNum INT8U ST See 'SPC.ctlNum'. O
stVal DpStatusKind ST dchg Status value of the controllable data object. M
q Quality ST qchg Quality of the value in 'stVal'. M
t Timestamp ST Timestamp of the last change of the value in any M
of 'stVal' or 'q'.
stSeld BOOLEAN ST dchg See 'SPC.stSeld'. MOsbo
DataAttribute for control mirror
opRcvd BOOLEAN OR dchg inherited from: ControlTestingCDC O
opOk BOOLEAN OR dchg inherited from: ControlTestingCDC O
tOpOk Timestamp OR inherited from: ControlTestingCDC O
DataAttribute for substitution and blocked
subEna BOOLEAN SV inherited from: SubstitutionCDC MFsubst
subVal DpStatusKind SV Value used to substitute 'stVal'. MFsubst
subQ Quality SV inherited from: SubstitutionCDC MFsubst
subID VisString64 SV inherited from: SubstitutionCDC MFsubst
blkEna BOOLEAN BL inherited from: SubstitutionCDC O
DataAttribute for configuration, description and extension
pulseConfig PulseConfig CF dchg See 'SPC.pulseConfig'. O
ctlModel CtlModelKind CF dchg See 'SPC.ctlModel'. M
sboTimeout INT32U CF dchg See 'SPC.sboTimeout'. MOsbo
sboClass SboClassKind CF dchg (default=operate-once) See 'SPC.sboClass'. O
operTimeout INT32U CF dchg See 'SPC.operTimeout'. MOenhanced
d VisString255 DC inherited from: BasePrimitiveCDC O
dU Unicode255 DC inherited from: BasePrimitiveCDC O
cdcName VisString255 EX inherited from: BasePrimitiveCDC O
dataNs VisString255 EX inherited from: BasePrimitiveCDC MOdataNs
Parameters for control services
ctlVal BOOLEAN  Service parameter that determines the control
activity ('FALSE' for off, 'TRUE' for on).

Replace existing Figure 64 by the following new figure:

IEC 61850-7-1:2011/AMD1:2020 – 25 –
© IEC 2020
Figure 64 – Instances of a Data object class (conceptual)
Replace the second paragraph following Figure 64 with the following new text:
The conditions in the last column of the Data object class Pos are as follows (excerpt of
IEC 61850-7-2 shown):
Replace the existing table following the second paragraph after Figure 64 by the following
new table:
Abbreviation Condition
M Attribute is mandatory
O Attribute is optional
MOsbo Element is mandatory if declared control model supports 'sbo-with-normal-security' or 'sbo-
with-enhanced-security', otherwise optional and value is of no impact.
MFsubst Element is mandatory if substitution is supported (for substitution, see IEC 61850-7-2),
otherwise forbidden.
MOenhanced Element is mandatory if declared control model supports 'direct-with-enhanced-security' or
'sbo-with-enhanced-security', otherwise optional and value is of no impact.
MOdataNs Element is mandatory if the namespace of its data object deviates from the namespace of its
logical node, otherwise optional. See IEC 61850-7-1 for use of namespace.
... ...
12 Formal specification method
12.2 Class modelling
12.2.1 Overview
Replace the second paragraph of Subclause 12.2.1 with the following new text:
Figure 66 depicts the class model of the IEC 61850-7-x series. The generic model on the left
is defined in IEC 61850-7-2. The GenServer class, which represents the external behaviour of

– 26 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
a device, is composed of (1 to n) GenLogicalDevice classes. GenLogicalDevice classes
comprise two or more GenLogicalNode classes (2 to n).
Figure 66 – Abstract data model example for IEC 61850-7-x
Replace existing Figure 66 with the following new figure:

12.2.2 Common data class
Table 9 – Single point status common data class (SPS)
Replace existing Table 9 with the following new table:

IEC 61850-7-1:2011/AMD1:2020 – 27 –
© IEC 2020
cdcId = SPS, UML class name = SPS
Attribute name Attribute type FC TrgOp (Value/Value range) Description PresCond
DataAttribute for status
stVal BOOLEAN ST dchg Value of the data. M
q Quality ST qchg Quality of the value in 'stVal'. M
t Timestamp ST Timestamp of the last change of M
the value in any of 'stVal' or 'q'.
DataAttribute for substitution and blocked
subEna BOOLEAN SV inherited from: SubstitutionCDC MFsubst
subVal BOOLEAN SV Value used to substitute 'stVal'. MFsubst
subQ Quality SV inherited from: SubstitutionCDC MFsubst
subID VisString64 SV inherited from: SubstitutionCDC MFsubst
blkEna BOOLEAN BL inherited from: SubstitutionCDC O
DataAttribute for configuration, description and extension
d VisString255 DC inherited from: BasePrimitiveCDC O
dU Unicode255 DC inherited from: BasePrimitiveCDC O
cdcName VisString255 EX inherited from: BasePrimitiveCDC O
dataNs VisString255 EX inherited from: BasePrimitiveCDC MOdataNs

Replace the existing second and third paragraphs of Subclause 12.2.2 with the following new
text:
The first column represents the name of the attribute, the second specifies the attribute type.
An attribute that is composed of several components is defined as depicted in the example of
Table 10 (excerpt of Quality class from IEC 61850-7-2).
The components of the Quality (for example, validity or detailQual) are data attribute
components. The attribute types of the data attribute components (for example, PACKED
LIST or CODED ENUM) are defined in IEC 61850-7-2. An excerpt of detailQual from
IEC 61850-7-2 is given in Table 16.
Table 10 – Quality components attribute definition
Replace existing Table 10 with the following new table:

– 28 – IEC 61850-7-1:2011/AMD1:2020
© IEC 2020
atId = Quality
Attribute name Attribute type (Value/Value range) Description PresCond
validity ValidityKind Validity of the value, as condensed information for the client. In M
case this value is not 'good', some reasons may be found in the
'detailQual'.
detailQual DetailQual Describes some reasons in case 'validity' is not 'good'. M
source SourceKind (default=process) Defines the source of a value. M
NOTE 1 Substitution may be done locally or via the
communication services. In the second case, specific attributes
with a FC=SV are used.
NOTE 2 There are various means to clear a substitution. As an
example, a substitution that was done following an invalid
condition may be cleared automatically if the invalid condition is
cleared. However, this is a local issue and therefore not within the
scope of this standard.
test BOOLEAN (default=FALSE) If TRUE, the value is a test value. The M
processing of the test quality in the client shall be as described in
IEC 61850-7-4. This bit shall be completely independent from the
other bits within the quality descriptor.
operatorBlocked BOOLEAN (default=FALSE) If TRUE, further update of the value has been M
blocked by an operator. The value shall be the information that
was acquired before blocking. If this flag is set, then the
'detailQual.oldData' shall also be set.
The operator shall use the data attribute 'CDC.blkEna' to block the
update of the value.
NOTE Both an operator as well as an automatic function may
freeze communication updating as well as input updating. In both
cases, 'detailQual.oldData' will be set. If the blocking is done by an
operator, then this flag is set additionally, and an operator activity
is required to clear the condition.
EXAMPLE An operator may freeze the update of an input, to
save the old value before the auxiliary supply is switched off.

Delete the paragraph following Table 10 and add the following new Table 16 after Table 10:

IEC 61850-7-1:2011/AMD1:2020 – 29 –
© IEC 2020
Table 16 – Attributes of DetailQual
datId = DetailQual
Attribute Attribute (Value/Value range) Description PresCond
name type
overflow BOOLEAN (default=FALSE) If TRUE, the value of the attribute to which the quality M
has been associated is beyond the capability of being represented
properly (used for measurand information only).
EXAMPLE A measured value may exceed the range that may be
represented by the selected data type, for example the data type is a 16-
bit unsigned integer and the value exceeds 65 535.
(default=FALSE) If TRUE, the attribute to which the quality has been
outOfRange BOOLEAN M
associated is beyond a predefined range of values. The server shall
decide if validity shall be set to invalid or questionable (used for
measurand information only).
EXAMPLE A measured value may exceed a predefined range, however
the selected data type can still represent the value, for example the data
type is a 16-bit unsigned integer, the predefined range is 0 to 40 000, if
the value is between 40 001 and 65 535 it is considered to be out of
range.
badReference BOOLEAN (default=FALSE) If TRUE, the value may not be a correct value due to a M
reference being out of calibration. The server shall decide if validity shall
be set to invalid or questionable (used for measurand information and
binary counter information only).
oscillatory BOOLEAN (default=FALSE) To prevent overloading of event driven communication M
channels, it is desirable to detect and suppress oscillating (fast
changing) binary inputs. If a signal changes in a defined time twice in the
same direction (from 0 to 1 or from 1 to 0), then it shall be defined as an
oscillation and this attribute shall be set to TRUE. If a configured number
of transient changes is detected, they shall be suppressed. In this time,
the 'Quality.validity' shall be set to 'questionable'. If the signal is still in
the oscillating state after the defined number of changes, the value shall
be left in the state it was in when this flag was set. In this case, the
'Quality.validity' shall be changed from 'questionable' to 'invalid' and kept
so as long as the signal is oscillating.
If the configuration is such that all transient changes should be
suppressed, the 'Quality.validity' shall be set immediately to 'invalid' and
this flag to TRUE (used for status information only).
failure BOOLEAN (default=FALSE) If TRUE, a supervision function has detected an M
internal or external failure.
oldData BOOLEAN (default=FALSE) If TRUE, an update is not made during a specific time M
interval. The value may be an old value that may have changed in the
meantime. This specific time interval may be defined by an allowed-age
attribute.
NOTE "Fail silent" errors, where the equipment stops sending data, will
cause setting this flag to TRUE. In this case, the last received
information was correct.
inconsistent BOOLEAN (default=FALSE) If TRUE, an evaluation function has detected an M
inconsistency.
inaccurate BOOLEAN (default=FALSE) If TRUE, the value does not meet the stated accuracy M
of the source.
EXAMPLE The measured value of power factor may be noisy
(inaccurate) when the current is very small.

Add the following new text aft
...