Professional Documents
Culture Documents
SC B5
Klaus-Peter BRAND
protection and automation (Switzerland), 2
Christoph BRUNNER
from Ivan de MESMAEKER 1 (Switzerland), 3
Ivan de MESMAEKER
(Switzerland)
1. I. de M ESMAEKER , Chairman of SC B5
2. Klaus-Peter B RAND , IEC expert
3. Christoph BRUNNER , IEC expert
SC B5
tion (values according the common double cept. Besides the basic services to access the
point indication: off, on, intermediate-state, data model (individual read or write of data),
bad-state) and another attribute ctlVal for the more elaborated services are defined. As an
opening and closing command (values: off, on). example, for the SCADA application, event
The Logical Nodes, the data and the attributes driven transmission of data is essential. In IEC
including their names and semantic interpre- 61850, the report service is defined for that pur-
tation are defined by the standard. pose. The report service is not accessing indi-
vidual data, but group of data called dataset.
Logical Nodes are grouped in Logical The details of the event driven transmission are
Devices. Example: Logical Device Tampa_Pro- defined in the report configuration block. An
tection for a comprehensive two zone distance event causing a transmission may be a change
protection using one Logical Node PDIS per of a binary value, the crossing of a predefined
zone (PPDIS1 and PDIS2 in Figure 2). By alarm limit or the expiration of a cycle time.
enabling or disabling a Logical Device, it is pos- Based on the report configuration block and
sible to enable and disable the contained the related dataset, reports are sent to the
group of Logical Nodes together. client. Including the time tag of the event as
part of the dataset, event lists can be created.
Logical Devices are implemented in phys- For that purpose, the IED is typically synchro-
ical devices (IEDs). There is some actual infor- nized with accuracy in the order of 1 ms.
mation needed not only about the Logical
Nodes and Logical Devices but also about the Applications
complete IED like the status of the common A typical application of SCADA is the cre-
power supply. This information is modeled in ation of alarm lists and event lists. Today, the
the Logical Node LPHD, which has to be pro- data content of the alarm lists and event lists
vided in each Logical Device (see Figure 2). is specified through signal lists. With IEC
61850, datasets used together with the report
service can be used for that purpose. As an
example, a utility may specify a dataset per IED
that contains all data for the alarm list.
If the functions exchanging the information The information exchange between these
are located in different IEDs, the information logical nodes is also modeled as data. The data
exchange may be done using copper wiring is part of the logical node that is the source of
with contacts and auxiliary relays or using serial the information exchange. As an example, the
communication. This information exchange logical node PTRC has a data Tr with an
is a horizontal communication between devices attribute general representing the trip output
at the same hierarchical level (Figure 3). of the protection device for a general trip. That
signal is not only used to operate the breaker,
Theoretically, the information exchange but it is used as well to trigger e.g. the breaker
could take place using the client-server com- failure function (see Figure 4 and Figure 5).
munication. However, client-server communi-
cation is using the full seven-layer stack and is For the exchange of this type of (binary)
therefore relatively time consuming. An appro- information over serial communication, IEC
priate communication concept used is a pub- 61850 introduces a specific information
lisher-subscriber communication. The publisher exchange service called GOOSE (Generic
is distributing the information over the com- Object Oriented Substation Event) based on
munication network; the subscriber may receive the publisher-subscriber concept. The con-
the information according his needs. In IEC tent of a GOOSE message is defined with a
61850 publisher-subscriber communication is dataset (similar like for the report model
not using confirmed services and is therefore described above). The GOOSE message is
transmitted over a reduced communication sent as a multicast message over the com-
stack resulting in a very short transmission time. munication network. That means that multi-
ple devices can receive the message and
retrieve the information required from the
message. The communication service is not
confirmed; instead, the message is repeated
several times.
SC B5
tion, depending if the exchange of informa- clause 3.2. In case the concerned breaker does
tion is between devices inside the bay or not open, the breaker failure function may
between devices placed in different bays. RBRF.OpIn) and, without success send
retrip (R
a trip to all surrounding breakers. This is mod-
Exchange of information inside the bay: eled with the data RBRF.OpEx.
A typical example is the exchange of infor-
mation between Logical Device Distance Pro-
tection containing instances of LN PDIS per
zone and the LN PTRC ( and the Logical Device
Recloser containing the LN RREC (, in case
these both functions are installed in separate
devices (Figure 4).
SC B5
approach can deal with variable communica- if both voltages (the one at line side and the
tion delays, as they are inevitable when using one at bus side) are nearly identical (amplitude,
a network topology for the communication. phase frequency) allowing a switch on without
excessive stress. The bus voltage is normally
The message with the sampled values is not available per bay but only once per bus
typically transmitted as a multicast message zone on which the line will be connected. This
that means the same telegram can be bus zone voltage can be taken from the cor-
received by multiple receiving devices. As for responding voltage transformer at the bus and
the GOSSE message the content of the mes- introduced to the device where the syn-
sage is defined with a dataset. chrocheck function is placed. Using IEC 61850
the samples representing the bus voltage can
Applications be sent over the serial link to the synchrocheck
A typical application for the process con- function installed in the line bay where the
nection is the information transfer between reclosing should take place.
instrument transformers, protection devices and
circuit breakers. This information transfer is time How to use IEC 61850 for
critical. It has a direct impact on the reaction substation automation design
time of the protection function. The acceptable
transmission delay is in the range of 3 s [7]. Introduction to SCL
Substation automation design is a series of
The analog waveform of current and volt- steps from the specification up to the commis-
age is transmitted as a stream of samples as sioning of a project specific system. To show
described in clause 4.2. In order to fulfill the IEC 61850 is used in this process we have first to
requirements for the protection functions, the introduce shortly the Substation Configuration
synchronization accuracy for the sampling description Language (SCL) provided by the
needs to be in the range of 14 s (e.g. phase standard for this process. SCL was introduced
relationship of currents for differential protec- for a comprehensive description of the complete
tion, phase relationship between current and SA system supporting the goal interoperability
voltage for fault locator and distance protec- of the standard. SCL allows describing the
tion). To achieve that synchronization accuracy, single line diagram,
a dedicated synchronization network is cur- function allocation to the single line dia-
rently required. gram,
function allocation to devices,
To simplify the synchronization of samples data as being mandatory and optional
from all phases all relevant TCTRs and TVTRs according to IEC 61850 (optional if needed or
may be implemented in a common Logical provided),
Device called Merging Unit (MU). One or many data as being extended according to the
of theses Logical Devices are implemented extension rules (should be avoided but may be
in a common Physical Device sometimes con- needed),
fusingly called MU also. the services provided and used,
connection in the communication system,
The samples are used as current and volt- setting of all configuration parameters as
age input e.g. for protection. The trip from the defined in IEC 61850,
protection device to the circuit breaker IED defaults values of for all operational
XCBR.pos.ctl ) can be transmitted over the
(X parameters as defined in IEC 61850.
same communication network using the
GOOSE concept introduced in clause 3.2. The SCL is based on the eXtended Mark-
up Language (XML), known also from the
Another interesting example is the syn- description of Web pages, with an XML Schema
chrocheck function. In case of reclosing (auto- defining the semantic use of XML in the
Since the data model of IEC 61850 is The SSD file is used to describe the single line
defined function oriented, i.e. according to the diagram and the allocated functions (feeder block
functional needs but not based on certain diagram). The optional data that need to be sup-
implementation in devices, a function oriented ported can also be described in the SSD file. This
specification facilitates the translation to an replaces the traditional signal list, the elements
IEC 61850 based SA system. All data defined of a signal list being the data of logical nodes. Up
as mandator y are provided according to the to now, the signal list is not only used to describe
data model in IEC 61850. If the user needs data the complete information content, but also to
declared as optional this has to be specified. describe the data flow. In IEC 61850, the data
If data are needed which are not specified in flow is implemented through communication ser-
the standard, they have to be listed for pos- vices like report or GOOSE where the content is
sible extensions. defined by data sets being a group of data.
SC B5
of the system integrator. He has more respon- single line diagram, and part of the data model
sibilities in the multi-vendor environment pos- by the SSD file.
sible with IEC 61850. He has to consider not Any selected IED if IEC 61850 compli-
only the direct impact of IEC 61850 but also ant has to have an IED Capability Description
all boundary conditions regarding environ- (ICD) file including its potential data model.
ment, performance, etc. as summarized in A system co nfi guratio n tool will take
p.17. The system integrator may be part of the all these files written according to SCL and
main provider or of the utility, but he has to merge these by the system engineering pro-
have the know-how and experience for this job cess to a Substation Configuration Description
and, very important, powerful tools compliant (SCD) file.
with IEC 61850. Note that the standard is not If the ICDs are properly selected, the data
defining tools but by SCL standardized infor- of all IEDs represented by the ICD files have
mation (see further) to be used by proprietary to fit with the data in the SSD file. Since the
tools. data in the models represent only the source
or client part, the data have to be configured
Any system integration tools needs the in data sets for the transmission by the appro-
SSD file and the ICD files of all devices of the priate services (e.g. Report, GOOSE) and in
system. The output is the Substation Config- so-called input sections of the SCL file, since
uration Description (SCD) file. For maintenance the receiver side has to be informed where the
and future system modifications the SCD files data needed for the functions coming from.
have to be archived as part of the project doc- All data changes caused by the promo-
umentation. tion of the IEDs from the shelf to integrated
system components, i.e. in minimum some
Product and system engineering with addressing information, have to be down-
compatible tools loaded to the IEDs.
Since the functions are not standardized,
device specific tools will remain at least for the The formal SCL description will result in a
next time. They are depending mostly on the consistent data exchange, allow exchanges
function algorithms and their implementation between compliant tools independent from
in the IEDs. If they are in series with the system the supplier and, finally, in a machine-readable
configuration tool they have be IEC 61850 com- documentation of the data and communica-
pliant, i.e. to be able to export and import SCL tion structure of the SA system. Any extension
files if applicable. The complete engineering or update in the future will not start from the
process is schematically shown in Figure 7. scratch but from the archived SCD file.
System per for mance testing The primary equipment as a whole needs
To check the performance classes as changing once every 30 60 years but may be
defined in the mandatory part IEC 61850-5 for extended during the life cycle time of the sub-
the device in a system (system conformance) station. One of the most important aspects
independent from a project, the IEDs may be during the life cycle time is the facility for
tested in a test system with reasonable data extensions or the refurbishment of existing
traffic in the background. parts of the SA system. In this respect it is to
be considered that the replacement of an IED
The Factor y Acceptance Test may be needed because of maintenance rea-
The factory acceptance test (FAT) has to son (failure of the equipment) or because of
prove that the SA system as far as assembled in needs for a performance upgrade. In most
one factory fulfills the given specification of the cases the new coming in IED is not identical
customer. The prerequisite is that all compo- with the previous one, additional engineering
nents are conformant with IEC 61850 and that and testing works are needed.
the all SCL files used in engineering, especially With IEC 61850 the whole system descrip-
the resulting SCD file is available. With some tion and data remain available as formally pro-
minor exceptions for systems on MV level, the vided in the SCD file. This is part of the doc-
switchgear will not be available for the FAT. The umentation the user has received with the
missing switchgear and other missing parts have system delivery and has to be updated for any
to be simulated. For an IEC 61850 based sys- change in the system e.g. change of the event
tem appropriate simulators having serial inter- list. Using this documentation and taking over
faces according to the standard can easily do data coming from new devices or from new
this. If the system has also an IEC 61850 process functions to be introduced in the system, the
bus simulators may be plugged in to the bus system integrator can perform the required
representing the switchgear. Quasi-standard- extensions much easier than in the past.
ized or project specific switchgear plugs are
replaced by the standardized process bus inter- A practical issue is the extension of a new
face. Note that also devices monitoring the tests bay to an existing SA system, which is
SC B5
IEC 61850 in order to have the advantages set less communication architecture for utilities.
by the standard for the life cycle of a substa- Since IEC 61850 has high impact on the
tion automation system. For this reasons exten- investment and operation of power systems,
sion scenarios are very important but gener- the utilities will consider the standard very
ally individual per substation. actively same as the suppliers.
Physical Devices and as external nameplate for [2] IEC 60870-5-104 Telecontrol equipment
and systems - Part 5-104: Transmission protocols -
switchgear also. Network access for IEC 60870-5-101 using standard
transport profiles
Outlook and conclusions [3] IEC 60870-5-103 Telecontrol equipment
and systems Part 5-103: Transmission protocols
Companion standard for the informative interface
The Standard IEC 61850 covers all aspects
of protection equipment
related to the communication inside substa-
[4] IEC 61850 Communication networks and
tion. It supports important issues as the nam- systems in substations (www.iec.ch)
ing and the engineering capabilities but also [5] IEC 61850-7-2 Communication networks and
conformity, testing, etc. It is a comprehensive systems in substations Part 7-2: Basic communica-
tion structure for substation and feeder equipment
approach for the conception of the substation
Abstract communication service interface (ACSI)
automation and protection with serial com-
[6] IEC 61850-7-4 Communication networks
munication. It doesnt mean that all delivered and systems in substations Part 7-4: Basic com-
systems will have the same quality inde- munication structure for substation and feeder
pendently of the manufacturer because archi- equipment Compatible logical node classes and
data classes
tecture remains free (architecture of the com-
[7] IEC 61850-7-3 Communication networks
munication system as well as location of the and systems in substations Part 7-3: Basic com-
different functionality) as well as the quality of munication structure for substation and feeder
each function involved (e.g. protection func- equipment Common data classes
tions). The first experiences done by manu- [8] IEC 61850-5 Communication networks and
systems in substations Part 5: Communication
facturers and utilities have now to confirm if
requirements for functions and device models
the expectations are fulfilled and if some exten-
[9] K.P. Brand et al., Conformance Testing
sions inside the standard will be needed. Guidelines for Communication in Substations, Cigr
Report 34-01 Ref. No. 180, August 2002
Besides the mentioned maintenance of the [10] IEC 61850-10 Communication networks and
standard for communication within substations, systems in substations - Part 10: Conformance testing
activities have been started or are envisaged to [11] K.P.Brand, V.Lohmann, W.Wimmer Sub-
station Automation Handbook, UAC 2003, ISBN 3-
use IEC 61850 also outside the substation. Within 85759-951-5, 2003 (www.uac.ch)
IEC, there exists already working groups using the [12] K.P.Brand, M.Janssen The specification of
standard in wind power, hydro-power and dis- IEC 61850 based Substation Automation Systems
tributed energy resources (DER). The feasibility Paper presented at the DistribuTECH 2005, January
25-27, San Diego
of IEC 61850 for the link to the NCC has been
[13] CIGRE SC B5, WG11 The introduction of
proven, a harmonization between the data model IEC 61850 and its impact on protection and automa-
of IEC 61850 and the CIM model on Network tion within substations, work started in 2003, report
Level is in progress. New work items to use IEC to be scheduled for 2005/2006
61850 for communication between both ends of [14] K.P. Brand, C. Brunner, W. Wimmer Design
of IEC 61850 based Substation Automation Systems
a line protection (protection application) are in
according to customer requirements, Paper B5-103
preparation. The IEC TC57 WG10 takes care to of the B5 Session at CIGRE Plenary Meeting, Paris,
the common data model, the user group UCA 2004, 8 pages