Amendment 1 - Communication networks and systems for power utility automation - Part 4: System and project management

Amendement 1 - Réseaux et systèmes de communication pour l'automatisation des systèmes électriques - Partie 4: Gestion du système et gestion de projet

General Information

Status
Published
Publication Date
02-Nov-2020
Current Stage
PPUB - Publication issued
Completion Date
03-Nov-2020
Ref Project

Buy Standard

Standard
IEC 61850-4:2011/AMD1:2020 - Amendment 1 - Communication networks and systems for power utility automation - Part 4: System and project management
English and French language
36 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

IEC 61850-4
Edition 2.0 2020-11
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
A MENDMENT 1
AM ENDEMENT 1
Communication networks and systems for power utility automation –
Part 4: System and project management
Réseaux et systèmes de communication pour l'automatisation des systèmes
électriques –
Partie 4: Gestion du système et gestion de projet
IEC 61850-4:2011-04/AMD1:2020-11(en-fr)
---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2020 IEC, Geneva, Switzerland

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form

or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from

either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC

copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or

your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite

ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie

et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur. Si vous avez des

questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez

les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC

The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes

International Standards for all electrical, electronic and related technologies.
About IEC publications

The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the

latest edition, a corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform Electropedia - www.electropedia.org

The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,

variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English

committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.

and withdrawn publications. Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished

Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary

details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and

once a month by email. French extracted from the Terms and definitions clause of

IEC publications issued between 2002 and 2015. Some

IEC Customer Service Centre - webstore.iec.ch/csc entries have been collected from earlier publications of IEC

If you wish to give us your feedback on this publication or TC 37, 77, 86 and CISPR.

need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
A propos de l'IEC

La Commission Electrotechnique Internationale (IEC) est la première organisation mondiale qui élabore et publie des

Normes internationales pour tout ce qui a trait à l'électricité, à l'électronique et aux technologies apparentées.

A propos des publications IEC

Le contenu technique des publications IEC est constamment revu. Veuillez vous assurer que vous possédez l’édition la

plus récente, un corrigendum ou amendement peut avoir été publié.
Recherche de publications IEC - Electropedia - www.electropedia.org

webstore.iec.ch/advsearchform Le premier dictionnaire d'électrotechnologie en ligne au

La recherche avancée permet de trouver des publications IEC monde, avec plus de 22 000 articles terminologiques en

en utilisant différents critères (numéro de référence, texte, anglais et en français, ainsi que les termes équivalents dans

comité d’études,…). Elle donne aussi des informations sur les 16 langues additionnelles. Egalement appelé Vocabulaire

projets et les publications remplacées ou retirées. Electrotechnique International (IEV) en ligne.

IEC Just Published - webstore.iec.ch/justpublished Glossaire IEC - std.iec.ch/glossary

Restez informé sur les nouvelles publications IEC. Just 67 000 entrées terminologiques électrotechniques, en anglais

Published détaille les nouvelles publications parues. et en français, extraites des articles Termes et définitions des

Disponible en ligne et une fois par mois par email. publications IEC parues entre 2002 et 2015. Plus certaines

entrées antérieures extraites des publications des CE 37, 77,
Service Clients - webstore.iec.ch/csc 86 et CISPR de l'IEC.
Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
---------------------- Page: 2 ----------------------
IEC 61850-4
Edition 2.0 2020-11
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
A MENDMENT 1
AM ENDEMENT 1
Communication networks and systems for power utility automation –
Part 4: System and project management
Réseaux et systèmes de communication pour l'automatisation des systèmes
électriques –
Partie 4: Gestion du système et gestion de projet
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 33.200 ISBN 978-2-8322-8925-9

Warning! Make sure that you obtained this publication from an authorized distributor.

Attention! Veuillez vous assurer que vous avez obtenu cette publication via un distributeur agréé.

® Registered trademark of the International Electrotechnical Commission
Marque déposée de la Commission Electrotechnique Internationale
---------------------- Page: 3 ----------------------
– 2 – IEC 61850-4:2011/AMD1:2020
© IEC 2020
FOREWORD

This amendment has been prepared by IEC technical committee 57: Power systems 2 manage-

ment and associated information exchange.
The text of this amendment is based on the following documents:
FDIS Report on voting
57/2256/FDIS 57/2271/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://web-

store.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.

_____________
---------------------- Page: 4 ----------------------
IEC 61850-4:2011/AMD1:2020 – 3 –
© IEC 2020
1 Scope

Replace the existing text of the first paragraph of the scope with the following new text:

This part of IEC 61850 applies to projects associated with processes near automation systems

of power utilities (UAS, utility automation system), such as substation automation systems

(SAS). It defines the system and project management for UAS with communication between

intelligent electronic devices (IEDs) in the substation respective plant and the related system

requirements.
2 Normative references
Replace the existing reference to IEC 61850-6 with the following new reference:

IEC 61850-6, Communication networks and systems for power utility automation – Part 6: Con-

figuration description language for communication in power utility automation systems related

to IEDs
Delete the references to IEC 81346-1 and IEC 81346-2.
4 Abbreviations
Add the following new abbreviations:
icd IED capability description file
ICT IED configuration tool
iid instantiated IED description file
scd substation configuration description file
SCT system configuration tool
sed system exchange description file
ssd system specification description file
5 Engineering requirements
5.3.4 IED configuration tool

Replace the existing text of the fifth paragraph of 5.3.4 with the following new text:

The tool’s data input module supports the interactive input of parameters as well as the import

of the system description as created by means of the system configuration tool. The structure

of input data should be technically oriented towards the process architecture, i.e. structured

according to the hierarchical approach to substation, voltage level, bay, equipment and function.

Replace the existing text of the first bullet with the following new text:
– process (e.g. substation or line) identification;
Add the following new subclause after 5.3.5:
5.3.6 Engineering tool workflow
5.3.6.1 From system specification to project description
Typical use case: one centralised SCT working with several ICT (see Figure 12).
---------------------- Page: 5 ----------------------
– 4 – IEC 61850-4:2011/AMD1:2020
© IEC 2020
Figure 12 – Engineering workflow steps from system to project

Step 1: System Specification Tool (SST) creates an ssd file according to IEC 61850-6.

Step 2a: IED Configurator Tool (ICT) creates an icd file according to IEC 61850-6.

Step 2b: ICT creates an iid file according to part 6.

Step 3: System Configuration Tool (SCT) creates an scd file, using previous files: ssd, icd

and/or iid.

Step 4: This SCD is used by an ICT to finalize configuration and publish an cid file to its related

IED (configuration of dataflow).

The fourth step is the last except if the scd contents requires modifications from the

ICT, which shall be transferred to the SCT in order to publish a updated scd. Then it

is replaced by step 5 hereafter.

Step 5: ICT updates the IED description based on the further IED configuration needs and on

system configuration needs provided by SCT in step 3. The ICT exports to the SCT
the updated configuration description via the iid file.

Step 6: SCT publishes a updated scd file taking into account information described by previous

IID.

Step 7: ICT publishes the updated cid file to send to the IED, using the scd published on step 6.

5.3.6.2 Change of system tool

Use case: considering an SCT A has to be replaced by an SCT B. The context is transferred

with an scd exported from the SCT A.

The creation of the project with SCT A is similar to the previous use case and is

assumed to be done before the replacement of SCT A as classical project engineer-

ing as shown in Figure 13.

NOTE Changing an SCT is always done with the purpose of updating / upgrading the system configuration with

features that previous SCT does not support.
---------------------- Page: 6 ----------------------
IEC 61850-4:2011/AMD1:2020 – 5 –
© IEC 2020
Figure 13 – Change of system tool first stage
Step 1: System Specification Tool (SST) creates an ssd.
Step 2a: IED Configurator Tool (ICT) creates an icd.
Step 2b: ICT creates an iid as a first instantiation.
Step 3: SCT creates an scd, using previous files: ssd, icd and iid.
Step 4: ICTs create iid using the scd issued on step 3.

Step 5: SCT publishes a new scd taking into account information described by previous iid.

Hereafter the second stage, the SCT B uses the scd provided by the SCT A as shown in

Figure 14.
Figure 14 – Change of system tool second stage

Step 6: SCD to be transferred by SCT A to SCT B. Even if that does not appear on the

scheme, it is strongly recommended to also transfer the latest version of all icd files.

Step 7: SCT B updates the scd, using previous scd created by SCT A (previous step).

Step 8: ICTs create iid using the scd issued on step 7.
Step 9: SCT publishes a new scd.
---------------------- Page: 7 ----------------------
– 6 – IEC 61850-4:2011/AMD1:2020
© IEC 2020
Step 10: ICTs create cid using the scd previously created.
5.3.6.3 Interaction between projects

Use case: considering 2 different configuration projects managed by 2 SCT A and B (The

2 configuration projects may cover one or multiple UAS). One IED (e.g. IED 2)

regards both projects. The cid intended to the IED 2 shall take into account both

contexts. The final step is the publishing of the cid.

Hereafter, the first stage consists of the publishing of the SCD, as shown in Figure 15.

Figure 15 – interaction between projects, first stage
Step 1: System Specification Tool (SST) creates an ssd.
Step 2a: IED 1 Configurator Tool creates an icd.
Step 2b: IED 2 Configuration Tool creates an iid as a first instantiation.

Step 3: SCT creates an SCD 1+2, describing both IED 1 and IED 2 and using previous files:

ssd, icd and iid.
Step 4: ICTs create iid using the scd issued on step 3.

Step 5: SCT publishes a new scd 1+2 taking into account information described by previous

IID.

Hereafter, the second stage consists in using part of the scd 1+2, that is involved in the com-

munication of a second project, as shown in Figure 16.
---------------------- Page: 8 ----------------------
IEC 61850-4:2011/AMD1:2020 – 7 –
© IEC 2020
Figure 16 – interaction between projects, second stage

Step 6: SCT A creates an sed 2r, which gives only required information on the IED 2 needed

for the engineering of the second project. (therefore “reduced IED 2”)

Step 7: SCT B creates an scd 3+4+2r’, using the sed 2r created by sct A (previous step) and

taking into account its own context.
Step 8: ICTs create iid using the scd 3+4+2r’.

Step 9: SCT B creates a new sed 2r’ taking into account IED 2 in the SCT B context.

Step 10: SCT A creates a new scd 1+2’ using the sed 2r’ to integrate dataflow modifications of

IED 2 coming from the sct B.
Step 11: ICTs create cid using the scd previously created.
5.5 Scalability
Replace the existing text of the first bullet with the following new text:

– task (transmission/distribution/power plant/DER/… networks) and voltage range (medium,

high or ultra high voltage) of the substation;
5.7 Standard documentation
Replace the existing text of the first paragraph with the following new text:

The standard documentation is the description of the device and the functions of one IED or the

UAS product family of a manufacturer which is universally valid and which is not changed for

purposes of specific projects (refer to CIGRE – TB628 – Documentation requirements through-

out the lifecycle of Digital Substation Automation Systems – B5-39).
---------------------- Page: 9 ----------------------
– 8 – IEC 61850-4:2011/AMD1:2020
© IEC 2020
Add the following new text after 5.8:
5.9 System testing and engineering

Functional testing of the system, especially for maintenance testing, but also during FAT and

SAT, requires the preparation of the system configuration to support testing.

The testing concept must be defined by the user at an early stage of the project, since this

comes with additional requirements impacting the system design and configuration, see

IEC 61850-10-3.
6 System life cycle
6.1 Requirements of product versions
Replace the existing text of 6.1 with the following new text:

The life cycles of an UAS and its IEDs are subject to differences of the manufacturer’s and the

customer’s point of view, as shown in Figure 17:

– the manufacturer’s product life cycle contains the period between the start of production

and the discontinuation of the UAS product family;

– the customer’s system life cycle contains the period between the site commissioning of the

first system installation, often based on several UAS product families, and the decommis-

sioning of the latest system installation. The system installation may be carried out by a

system integrator who is different from the product manufacturer.
Figure 17 – Two meanings of the system life cycle

During the life cycle of the UAS and its IEDs, a number of changes and extensions are required

for various reasons:
– functional improvements and extensions;
– technology changes in the hardware;
---------------------- Page: 10 ----------------------
IEC 61850-4:2011/AMD1:2020 – 9 –
© IEC 2020
– correction of recognized problems.

These changes can lead updating IED versions of hardware, software or even engineering tools.

Different use cases are identified and developed later (ref. backward compatibility).

Whatever the use case, the manufacturer is obliged to provide identification of the IED versions

(software, firmware, hardware, configuration, revision):

– in the case of IED software or the supporting tools software, the version information is

available in a self identifying manner (for example, on display or PC);

– for the hardware, the version information is available at IED level (either physically or by

tool);

– if the functionality has changed or a function has been removed, a new configuration

compatibility list shall be distributed.

The co-ordination of the manufacturer’s and the customer’s life cycles requires that new ver-

sions of the IEDs with identical model numbers shall comply with the following rules.

a) The hardware shall be compatible. All interfaces must perform the same function in the

same places. The sizes of the boards and the devices must be identical.

b) The functional changes from the previous version of the product software shall be declared.

This includes any impact on IEC 61850 interface of the device. This information will help the

customer knowing the impact on their IEC 61850 system using this device.

c) The supporting tools shall be downward compatible, which means that the new version of

the supporting tool shall serve all existing versions of the same product family.

The manufacturer has to inform the customer about all of the functional changes and extensions

that are carried out between the last production release and most recent production release.

From an UAS system maintenance perspective identical or backwards compatible products are

preferred for replacement of failed parts. In case that functionally but not engineering wise

compatible products are used in this case, a re-engineering of a part of the UAS might be

necessary.
Add the following new text after 6.3:
6.4 Backward compatibility
6.4.1 General

As mentioned in 6.3, the life cycle of an UAS and its IEDs involve several changes. These may

come from:

– the manufacturer for including improvements, new functionalities and-or bugs correction;

– the customer for taking into account extensions or new requirements;
– the new edition of the standard.

This chapter deals with replacement or extension whatever the component is provided by the

same or a different manufacturer. It scrutinizes, through four use cases, taking into account

what is standardize in the actual IEC 61850 SCL configuration process what can be the en-

countered issues.
Considering the system is operated, the utilities point of view is highlighted.

NOTE 1 If the backward compatibility is not possible following standard advice, a mitigation plan shall be supplied

by the manufacturer.

NOTE 2 If for any reason, the backward compatibility of the standard itself must be broken, the mitigation solutions

has to be handled by the SCT as described in Part 6 annex I.
---------------------- Page: 11 ----------------------
– 10 – IEC 61850-4:2011/AMD1:2020
© IEC 2020

NOTE 3 It is understood that Edition 1 is a special case not considered. The discussion is about future Editions/Im-

plementations.
6.4.2 Components

– New IED: replaces an IED for any reason or is an extension of an existing system;

– Clients: IEDs which are only client or subscriber of the new IED, which means the commu-

nication between station and bay level (ref. to 61850-5: IF1 and IF6) or between bay and

process level (ref. to 61850-5: IF4 and IF5);

– Interacting IEDs: IEDs which are server or publisher for the new IED. Typically means the

communication at the bay level, within the bay or between bays (ref. to 61850-5: IF3 and

IF8).
– Other IEDs: every IEDs, which do not have any relation with the new IED.

– Configuration Tools: means SCT (System Configuration Tool) possibly ICT (IED Configura-

tion Tool).
6.4.3 Use cases
Four use cases are identified:
No new functionalities required.
1) Replacement of one IED with one coming from the same manufacturer (UC1);
2) Replacement of one IED with one coming a different manufacturer (UC2);
3) Extension with addition of one IED into an existing system (UC3);
New functionalities required:
1) Extension of the system with new functionalities (UC4).

NOTE In the following sections, to avoid designating some particular editions of IED 61850 devices (e.g. Ed1 system

with an added Ed 2 device), the Ed n and Ed n+m designations will be used to cover all possibilities (eg ED 2 system

with added Ed 3 device, or even Ed3 system with Ed 5 device ect). What matter here is Ed n+m has later edition

than Ed n.
6.4.4 Impacts
6.4.4.1 General

Depending on whether it is a new release (i.e. interoperability tissues have been implemented)

or a new version/revision (i.e. new edition of the standard), the three following possible impacts

are studied for each component previously listed:

– changing or modifying the configuration, which means in creating an updated SCD file and

potentially a new CID;
– upgrading the firmware of IED(s);
– upgrading the SCT and, other ICT.

The table shown in Figure 18 is used to detail which impact are acceptable or not:

---------------------- Page: 12 ----------------------
IEC 61850-4:2011/AMD1:2020 – 11 –
© IEC 2020
IEC 61850 Configuration Upgrade Upgrade IEC 61850 con-
impact (which part of Firmware of device figuration Tool (upgrade
the .scd shall be up- of ICT for devices / up-
dated) grade of SCT for entire
system)
a b
New IED
NA NA
Client (s)
Interacting
IEDs
Other IEDs
Entire 61850
c d
NA NA
System
a new IED does not need firmware upgrade as it is new
a new IED comes with a new ICT already upgraded

entire system configuration update (all IEDs) is covered by selecting all the others in this column (New IED +

Client(s) + Interacting IEDs + Other IEDs)

entire system firmware upgrade (all IEDs) is covered by selecting all the others in this column (Client(s) + Inter-

acting IEDs + Other IEDs)

Selected case ( : dark blue filling) means needed. If any, “x” is a number that refers to an explanation.

Partially selected case ( : light blue filling) means needed under certain condition. If any, “y” is a number that

refers to an explanation.

Non-selected case (blank) means there shall be no impact (e.g An IED not concerned by new features shall not be

affected).
Figure 18 – Template table of acceptable impacts
6.4.4.2 First use case (UC1)

Replacement of one IED with a new one coming from the same vendor, with equal behaviour,

without any impact on system configuration, as shown in Figure 19.

In that case, the vendor shall be able to provide a way to configure the new IED (especially the

data model) that mirrors the older device configuration (event if the new device supports a

newer edition of IEC 61850)
---------------------- Page: 13 ----------------------
– 12 – IEC 61850-4:2011/AMD1:2020
© IEC 2020
Figure 19 – Backward compatibility first use case
Before After
UAS Version Ed.n Ed.n
Replacement with one device with the same
Event Device failure from vendor A.
behaviour.
IED IEC 61850 Ed.n
Ed.n+m configured and acting like an Ed.n
Edition supported
Vendor A A
Clarification New functionalities not required.

The new IED can be integrated without a need for re-engineering (e.g. no bug correction or

no Interop issues correction needed), it is required that the Ed.n .scd file can be used to

load the new IED with no impact on the system, i.e.:
Requirements • No impact on other IEDs
• No impact on ICTs
• No impact on SCT

A device in a system in IEC 61850 edition n (all IEDs are edition n) has to be changed: the new device may be a

newer edition of IEC 61850: that is what n+m means.
Example: Edition 1 system where an edition 2.1 device is added.
IEC 61850 Configuration Upgrade Upgrade IEC 61850
impact Firmware of device configuration Tool
New IED NA NA
Client (s)
Interacting IEDs
Other IEDs
Entire 61850
NA NA
System
No impact is accepted.
---------------------- Page: 14 ----------------------
IEC 61850-4:2011/AMD1:2020 – 13 –
© IEC 2020
6.4.4.3 Second use case (UC2)

Replacement of one IED with a new one coming from a different or same vendor, with equal

behaviour, with impact on system configuration, as shown in Figure 20.

We assume in the use case that the new IED has a different data model than the older device.

In order to support the same data flow (i.e make the system behave as previously), the system

configuration shall be updated.
Figure 20 – Backward compatibility second use case
Before After
UAS Version Ed.n Ed.n
Replacement with one device with the same
Event Device failure from vendor A.
behaviour.
IED Ed.n
Ed.n+m
Vendor A B
Clarification New functionalities not required.

A new ICT is required for creating a new configuration to download. The more flexible the

new IED is, the more similar the data model will look like.
Requirements
Changes to clients (CBs, Datasets) are to be expected.
Example: Edition 1 system where an edition 2.1 device is added.
---------------------- Page: 15 ----------------------
– 14 – IEC 61850-4:2011/AMD1:2020
© IEC 2020
Expectations
IEC 61850 Configuration Upgrade Upgrade IEC 61850 con-
impact Firmware of device figuration Tool
New IED 2 NA NA
Client (s) 2
Interacting
IEDs
Other IEDs
Entire
61850 Sys- NA NA 1
tem

1) As the new Data model is not the same and has more information, the .scd must be updated and, for this, a new

version of SCT is required to manage the new IEC 61850 edition of the new IED. The SCT shall provide config-

uration files in both editions. Refer to IEC 61850-6:2009/AMD1:2018, Annex I for detailed workflow.

2) As the data model changed, the FCDA of new device’s DataSet are different for FCDA of older device that imply

update of Extref in other devices.
6.4.4.4 Third use case (UC3)

Extension with addition of one IED into an existing system to support new UAS functionality, as

shown in Figure 21.

The added IED will have to exchange information with clients and maybe other IEDs. A new .scd

will be needed.
Figure 21 – Backward compatibility third use case
---------------------- Page: 16 ----------------------
IEC 61850-4:2011/AMD1:2020 – 15 –
© IEC 2020
Before After
UAS Version Ed.n Ed.n
Event Need new UAS functionality Addition of a device.
IED Ed. n+m
Vendor A or B

Clarification New functionalities defined in Ed. n+m are not required within the system.

Requirements A new ICT(or new ICT version) will be introduced for the new IED.
Expectations
IEC 61850 Configuration Upgrade Upgrade IEC 61850
impact Firmware of device configuration Tool
New IED 2 NA NA
Client (s) 2
Interacting IEDs 2
Other IEDs
Entire 61850
NA NA 1
System

1) The .scd must be updated and, for this, a new version of SCT is needed in order to support new IEC 61850 edition

of the new device. The SCT shall provide configuration files in both editions. Refer to IEC 61850-

6:2009/AMD1:2018, Annex I for detailed workflow.

The configuration of each IED communicating with the new one needs to be updated.

6.4.4.5 Fourth use case (UC4)

Extension of the system possibly with new UAS functionalities requiring new IEC 61850 edition,

as shown in Figure 22.
Figure 22 – Backward compatibility fourth use case
---------------------- Page: 17 ----------------------
– 16 – IEC 61850-4:2011/AMD1:2020
© IEC 2020
Before After
UAS Version Ed.n Ed.n+m
Event Primary System extension need New IEDs added to support UAS Extension
UAS Extension
IEDs Ed.n only Mixed system Ed.n and Ed.n+m
Vendor any

Clarification New functionalities defined in Ed. n+m are required within the system.

If new extension (new IED as well) comes from another vendor, a new ICT could be re-

quired for creating a new configuration to download. The more flexible is the new IED, the

Requirements more similar the data model will look like. If not, changes to clients (CBs, Datasets) are to

be expected.
Expectations
IEC 61850 Configuration Upgrade Upgrade IEC 61850
impact Firmware of device configuration Tool
New IED 2 NA NA
Client (s) 2 3 3
Interacting IEDs 2 3 3
Other IEDs
Entire 61850
NA NA 1
System

1) The .scd must be updated and, for this, a new version of SCT is needed in order to support new IEC 61850 edition

of the new device. The SCT shall provide configuration files in both editions. Refer to IEC 61850-

6:2009/AMD1:2018, Annex I for detailed workflow.
2) For all interacting IEDs and clients, the configuration must be updated.

3) Firmware and ICT upgrade are needed if interacting IEDs or Clients of previous edition of the standard need to

interface with new features of edition n+m. In this case this part
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.