IEC 61850-6:2009/AMD2:2024

IEC 61850-6 ®
Edition 2.0 2024-11
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
AMENDMENT 2
AMENDEMENT 2
Communication networks and systems for power utility automation –
Part 6: Configuration description language for communication in power utility
automation systems related to IEDs

Réseaux et systèmes de communication pour l'automatisation des systèmes
électriques –
Partie 6: Langage de description de configuration pour la communication dans
les systèmes d'automatisation des systèmes électriques, entre les dispositifs
électroniques intelligents (IED)
IEC 61850-6:2009-12/AMD2:2024-11(en-fr)

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 Secretariat 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 IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews, graphical symbols and the glossary.
committee, …). It also gives information on projects, replaced With a subscription you will always have access to up to date
and withdrawn publications. content tailored to your needs.

IEC Just Published - webstore.iec.ch/justpublished
Electropedia - www.electropedia.org
Stay up to date on all new IEC publications. Just Published
The world's leading online dictionary on electrotechnology,
details all new publications released. Available online and once
containing more than 22 500 terminological entries in English
a month by email.
and French, with equivalent terms in 25 additional languages.

Also known as the International Electrotechnical Vocabulary
IEC Customer Service Centre - webstore.iec.ch/csc
(IEV) online.
If you wish to give us your feedback on this publication or 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 -  IEC Products & Services Portal - products.iec.ch
webstore.iec.ch/advsearchform Découvrez notre puissant moteur de recherche et consultez
La recherche avancée permet de trouver des publications IEC gratuitement tous les aperçus des publications, symboles
en utilisant différents critères (numéro de référence, texte, graphiques et le glossaire. Avec un abonnement, vous aurez
comité d’études, …). Elle donne aussi des informations sur les toujours accès à un contenu à jour adapté à vos besoins.
projets et les publications remplacées ou retirées.

Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
Le premier dictionnaire d'électrotechnologie en ligne au monde,
Restez informé sur les nouvelles publications IEC. Just
avec plus de 22 500 articles terminologiques en anglais et en
Published détaille les nouvelles publications parues.
français, ainsi que les termes équivalents dans 25 langues
Disponible en ligne et une fois par mois par email.
additionnelles. Egalement appelé Vocabulaire

Electrotechnique International (IEV) en ligne.
Service Clients - webstore.iec.ch/csc

Si vous désirez nous donner des commentaires sur cette
publication ou si vous avez des questions contactez-nous:
sales@iec.ch.
IEC 61850-6 ®
Edition 2.0 2024-11
INTERNATIONAL
STANDARD
NORME
INTERNATIONALE
colour
inside
AMENDMENT 2
AMENDEMENT 2
Communication networks and systems for power utility automation –

Part 6: Configuration description language for communication in power utility

automation systems related to IEDs

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

électriques –
Partie 6: Langage de description de configuration pour la communication dans

les systèmes d'automatisation des systèmes électriques, entre les dispositifs

électroniques intelligents (IED)

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
COMMISSION
ELECTROTECHNIQUE
INTERNATIONALE
ICS 33.200  ISBN 978-2-8322-4248-3

– 2 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
COMMUNICATION NETWORKS AND SYSTEMS
FOR POWER UTILITY AUTOMATION –

Part 6: Configuration description language for communication
in power utility automation systems related to IEDs

AMENDMENT 2
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). [IEC/IEC and ISO] [takes/take] no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, IEC had not received
notice of (a) patent(s), which may be required to implement this document. However, implementers are cautioned
that this may not represent the latest information, which may be obtained from the patent database available at
https://patents.iec.ch or www.iso.org/patents. IEC shall not be held responsible for identifying any or all such
patent rights.
Amendment 2 to IEC 61850-6:2009 has been prepared by IEC technical committee 57: Power
systems management and associated information exchange.
This second amendment constitutes a technical revision.
The main changes with respect to IEC 61850-6:2009+AMD1:2018 are as follows:
a) functional extensions concerning the engineering process to improve files exchange
followup, SCL elements identification and control configuration handling, added;

© IEC 2024
b) provision of clarifications and corrections. Issues that require clarification are published in
a database available at https://iec61850.tissue-db.com/. Arising incompatibilities are listed
in 8.2.3.
The text of this Amendment is based on the following documents:
Draft Report on voting
57/2711/FDIS 57/2733/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this Amendment is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications/.
A list of all the parts in the IEC 61850 series, under the general title Communication networks
and systems for power utility automation, can be found on the IEC website.
This IEC standard includes Code Components i.e. components that are intended to be directly
processed by a computer. Such content is any text found between the markers BEGINS> and , or otherwise is clearly labelled in this standard as a Code
Component. In the current version of this document, such indication is made at the beginning
of Annex A which identifies the list of XSD files and refers to the code component definition in
section 1.3.
The purchase of this IEC standard carries a copyright license for the purchaser to sell software
containing Code Components from this standard directly to end users and to end users via
distributors, subject to IEC software licensing conditions, which can be found at:
http://www.iec.ch/CCv1.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
IMPORTANT – The "colour inside" logo on the cover page of this document 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 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
INTRODUCTION
This amendment and consolidated edition bring two distinct sets of changes:
1) Resolved Interop Issues (covered by the table below) which have already followed the
technical issues (Tissues) process as described in IEC 61850-1 and have reached the green
"status".
2) Resolved Editorial Tissues which may have led to interoperability issues.
The resolutions of these issues which led to these changes are described in greater detail in
the Tissue database hosted at https://iec61850.tissue-db.com/.
The only new features compared to the previous IEC 61850-6:2009+AMD1:2018 are the
introduction of the UUID to identify elements and files, the modelling of controls binding from a
client perspective, and the definition of translated labels for elements which may be represented
in any user interface. Apart from this, this amendment strictly respects the scope of the original
edition.
Technical issues summary
N°, Subject, Clause and Paragraph are as they appear on the Tissue database hosted at
https://iec61850.tissue-db.com/ where all technical issues have been stored from the origin of
IEC 61850.
"Subject" defines very briefly the topic under focus.

© IEC 2024
The Tissues which have been considered are:
N° Subject Clause Paragraph
1590 RCB: Offline changes increment ConfRev by 10000? 9.3.8 Table 23
1647 SDO@count definition inconsistent 9.5.3 Table 44
1648 DA@count definition needs restriction 9.5.4.1 Table 47
1669 Incorrect example of header 9.1 1
1672 Allow connection Server and ServerAt to the same 9.3.2 Below Table 50
SCL.Subnetwork
1674 Harmonization with 62351-6 9.3.2 Services Element
1675 SCSM support capability - Harmonization with 62351-6 9.3.2 Services
1683 ICD file for IED functionality spanning for multiple VL and BAY 9.2.1 The name value is also a
global identification of
1708 Presence of Sample Mode field not controllable through 9.3.11 Smv Options element
SmvOpts
1729 Incorrect SCL example in (informative) Annex D.2 2
1734 Improved schema validation A.5 1
1740 Exceptions of enumeration types for IEC 61850-7-4 9.5.6 last in 9.5.6
1745 Definition of type and id in DataTypeTemplates not consistent 9.5.6 Table 49
1768 Server associate-request has no SCL parameters 9.3.2 Table 11
1771 SCL Services ReportControl max vs. Indexed 9.3.8 8
1774 Missing description of KDC 9.3.2 4
1786 Downgrade of SCD Exports not Mandatory Annex G Table G.2
1787 There is no clear mapping of all 7-2 ACSI type to SCL basic 9.5.4.2 1
types
1808 Please clarify if ix first index is 0 or 1 9.3.6 Data Table 19 and Table 20
object (DOI)
definition
1813 Typo "Valkind" 9.5.4.1 Table 46
1816 Add SICS statement for xsi:type usage in P elements 9.4.3 7
Annex G Table G.1 and G.2
1818 Clarification of ExtRef attributes usage 9.3.13 Table 51
1823 Clarify iedType attribute usage in DataTypeTemplates 9.5.1 2
1831 ldInst reference should concretized 9.3.7 Table 22
1832 SICS I45 not clear enough Annex G Table G.1
1833 Service SettingGroups.ConfSG clarification 9.3.2 Table 11
1834 SICS I211 text not inline with Service section Annex G Table G.1
1839 Not clear definition of lnInst to LN0 type elements 9.3.5 5
1843 SCT handle different OriginalSclXxx and SCL 9.3.2 G.1
version/revision/release
I.4.3.3
1854 SupSubscription 9.3.2 Table 11
1885 sAddr length I.5.3.5 1
1886 Part 6 – Typo in Abbreviation 4 ICT

___________
– 6 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
1 Scope
Replace the existing text of Subclauses 1.2 and 1.3 of IEC 61850-6:2009+AMD1:2018 with the
following new Subclauses 1.2, 1.3 and 1.4:
1.2 Published versions of the standard and related namespace names
The table below provides a reference between all published editions, amendments or corrigenda
of this document and the full name of the namespace.
Edition Publication date Webstore Namespace
Edition 1.0 2004-03 IEC 61850-6:2004 IEC 61850-6:2003
Edition 2.0 2009-12 IEC 61850-6:2009 IEC 61850-6:2007B
Amendment 1 of Edition 2.0 2018 IEC 61850-6:2009/AMD1:2018 IEC 61850-6:2007B4
Edition 2.1 2018 IEC 61850-6:2009+AMD1:2018 CSV IEC 61850-6:2007B4
Amendment 2 of Edition 2.0 2024 IEC 61850-6:2009/AMD2:2023 IEC 61850-6:2007C5
Edition 2.2 2024 IEC 61850-6:2009+AMD2:2023 CSV IEC 61850-6:2007C5

1.3 Identification of the namespace
The namespace associated with this document is an XML schema (XSD) for the System
Configuration Language (SCL). The parameters which are identifying the namespace are
provided in Table 53:
Table 53 – Attributes of the IEC 61850-6 XML namespace
Attribute Content
Namespace nameplate
Namespace Identifier (xmlns) http://www.iec.ch/61850/2003/SCL
Version 2007
Revision C
Release 5
XSD version header attribute 2007C5
Code Component Name IEC_61850-6.SCL.2007C5.Full

1.4 Code Component distribution
Each Code Component is a ZIP package containing the electronic representation of the Code
Component itself, with a file describing the content of the package (IECManifest.xml).
The life cycle of a code component is not restricted to the life cycle of the related publication.
The publication life cycle goes through two stages, Version (corresponding to an edition) and
Revision (corresponding to an amendment). A third publication stage (Release) allow
publication of Code Component in case of urgent fixes of InterOp Tissues, thus without need to
publish an amendment.
Consequently, new releases of the Code Component may be released, which supersedes the
previous release, and will be distributed through the IEC TC57 web site at:
https://www.iec.ch/tc57/supportdocuments
The latest version/release of the code component will be found by selecting the file for the code
component with the highest value for VersionStateInfo, e.g. IEC_61850-
6.SCL.{VersionStateInfo}.full.zip.

© IEC 2024
The code component associated to this document is an XML schema file (XSD). It is available
as a full version only. It is freely accessible on the IEC website for download at
https://www.iec.ch/tc57/supportdocuments, but the usage remains under the licensing
conditions.
In case of any differences between the downloadable code component and the IEC pdf
published content, the downloadable code component is the valid one; it may be subject to
updates. See included history files.
2 Normative references
Add the following new normative references:
IEC 62351-4, Power systems management and associated information exchange – Data and
communications security – Part 4: Profiles including MMS and derivatives
IEC 62351-6, Power systems management and associated information exchange – Data and
communications security – Part 6: Security for IEC 61850
IEC 62351-9, Power systems management and associated information exchange – Data and
communications security – Part 9: Cyber security key management for power system equipment
ISO/IEC 9834-8, Information technology – Procedures for the operation of object identifier
registration authorities – Part 8: Generation of universally unique identifiers (UUIDs) and their
use in object identifiers
4 Abbreviations
Replace the following existing abbreviation:
ICT IED Configuration Tool
Add the following new abbreviations:
SST System Specification Tool
UUID Universally Unique Identifier
5 Intended engineering process with SCL
5.3 Use of SCL in the engineering process
Add the following new text before Figure 1:
The System Specification Tool (SST) is an implementation independent system level tool that
shall be able to create a full system topology without the need to integrate real devices. It
produces a System specification file to be used by the System Configurator as a base for a new
system or as a template.
– 8 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
6 The SCL object model
6.1 General
Add the following new text after the twelfth paragraph of Subclause 6.1:
In addition to the full path used to identify any object in the SCL by its name, the SCL introduces
the UUID (Universal Unique Identifier) which can be used to identify objects independently of
their name which can evolve all along the lifecycle of a system. The reference to a UUID can
be inside the SCL file itself or outside to be used during the external process, not only dealing
with SCL files (e.g. as per requirement from IEC 61850-6-2 for human machine interface
engineering).
7 SCL description file types
Replace the first bullet of the second paragraph with the following new text:
• Data exchange from the IED configurator to the system configurator (corresponding to items
b) and c) of 5.1). This file describes the functional and engineering capabilities of an IED
type. It shall contain exactly one IED section for the IED type whose capabilities are
described. The IED name shall be TEMPLATE. Furthermore, the file shall contain the
needed data type templates inclusive logical node type definitions, and may contain an
optional process, line or substation section, where the highest-level name shall be
TEMPLATE. When importing the file into an SCT, the hierarchy of elements named
TEMPLATE is used to identify the first named element to be instantiate in the project, and
all elements with a name different than TEMPLATE are considered to be instantiable, based
on the name. If a process TEMPLATE is defined, the binding of logical node instances to
primary equipment indicates a predefined functionality. Any process in which this IED shall
be used must match an appropriate process topology part (example: a CSWI LN bound to
an equipment of type CBR is only allowed to control a circuit breaker; a CILO bound to a
line disconnector implements the interlocking logic for a line disconnector). There might be
an optional Communication section defining possible default addresses of the IED. A
specific SCSM might make this mandatory for some address parts.
The file extension shall be ICD for IED Capability Description.
Replace the third bullet of the second paragraph with the following new text:
• Data exchange from a system specification tool to the system configurator. This file
describes the single line diagram and functions of the substation and the required logical
nodes. It shall contain a process section which may be composed of Substation, Process
and/or Line elements, and may contain the needed data type templates and logical node
type definitions. If logical nodes allocated to the Substation section are not already allocated
to an IED, the IED name reference (value of iedName attribute of the LNode element) shall
be None. If an LN in the substation section is not bound to an IED and also has no logical
node type defined, then only the mandatory part of this LN according to IEC 61850-7-4 is
specified. If part of the SA system is already known, this might optionally be contained in
IED and Communication sections.
The file extension shall be SSD for System Specification Description.

© IEC 2024
8 SCL language
Figure 9 – UML diagram overview of SCL schema
Replace existing Figure 9 with the following new figure:

IEC
8.3 SCL language extensions
8.3.5 XML name spaces
Add the following new text before the Notes:
Other parts of IEC 61850 also define extensions of the SCL using specific XML Namespace,
stored in a dedicated Private section. This is the case for technical specifications (e.g.
IEC 61850-80-1 for mapping to IEC 60870-5-101 or −104) or technical reports (e.g. IEC 61850-
90-30 for SCL function modelling). In the case of technical reports, the XML extension
introduces an experimental new feature which may be included later in the SCL namespace
itself. In this context, the extension may contain references to SCL elements. In the case where
users want to use this extension, they will have to be aware that all tools implied in the
engineering have to support this extension to maintain the SCL references (e.g. when an
extended element references a Bay, when the Bay name is updated, all references shall be
updated even within the private extensions introduced by technical reports).
8.3.6 Private data
Add the following Note at the end of Subclause 8.3.6:
NOTE Due to the engineering process as described in Clause 5 IED configurators are allowed to put Private
elements into the IED section, the related ConnectedAP section and the DataTypeTemplate section for types used
by the IED.
– 10 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
8.5 Object and signal designation
8.5.2 Object designations in an object hierarchy
Add the following new text and XML schema extract at the end of Subclause 8.5.2:
The designation of objects which are also intended to be displayed in any kind of user interface
can have a list of labels by the mean of the element Labels which will contain a list of Label
elements which are textual elements with a lang attribute allowing to identify the language of
the label, allowing translation, and also an optional id attribute allowing to create different labels
for different purpose for the same element. The language attribute is following the RFC 1766
Language Tags (i.e. it can be "en", "en-US", "fr", "fr-FR", …).
Here is the XML schema definition of labels

















Add the following new Subclause 8.5.6:
8.5.6 Universal Unique Identifier
A UUID shall be generated following specification of ISO/IEC 9834-8. This document will not
detail the different algorithms to generate a UUID; this is covered by ISO/IEC 9834-8.
The UUID is optionally available for each SCL element represented by a name or which needs
to be referenced to give the possibility to have a fixed identifier independent of the textual name.
If the usage of the UUID is required by a tool, the UUID will be generated by the tool which is
creating or instantiating the element for the first time in the context of the usage and shall
remain unmodified for the duration of the lifetime of the element.
Different tools may need to generate an UUID for their own needs, but depending on the
engineering step, it may be considered as a template UUID or instance UUID. Different cases
may apply, as per the following examples.
By nature, every instance UUID in a SCL shall be unique. This is not the case for template
UUID, that could be instantiated several times to reference a UUID defined in an imported file
referenced by an SclFileReference element as per definition in 9.1.
An ICT which is creating an element in an ICD (e.g. for an LN) will create a UUID which may
be used later by the ICT. On instantiation of the IED in a SCD, the SCT will generate a new
instance UUID in the context of the SCD and the existing ICD UUID is to be considered as a
template UUID, thus the SCT will have to keep the ICD UUID as a template UUID, to allow
comparison with the ICD if needed, by the SCT or the ICT. If the IED is preconfigured by the
ICT (an IID is directly created by the ICT instead of an ICD), then the instance UUIDs are
directly created by the ICT and preserved by SCT after import.

© IEC 2024
When an ICT imports an SCD, the UUID present in the SCD shall be preserved. If the ICT adds
new elements in the datamodel of the IED, it shall create a UUID for the new elements.
The SST creates a system specification with its own UUID. When The SCT is creating a
substation based on an SSD, if a UUID has been generated by the SST assigned to the
substation, then the SCT will have to know how to use the original UUID, depending on the use
case. If the specification is used as a base for the new project (i.e. the specification is already
a project specification) the SCT keeps this UUID in the project for the duration of the lifetime of
the substation. If the specification is used as a template (i.e. the specification is a piece of
project, like a bay, reusable in different projects), the SCT will keep the original UUID from the
SSD as a template UUID to allow recognition of the original SSD elements by the SST/SCT.
The rules will be detailed in the relevant parts of the document. Each element which can be
referenced will have a UUID and may have a template UUID if its creation was based on the
instantiation of a template element identified with a unique identifier. In addition, all possible
referring elements will have an optional UUID reference attribute indicating the UUID of the
referred element (an instance or a template), when defined. A UUID may also be used within
ObjectReference to substitute part of the reference.
When a UUID is not defined, the naming reference shall be used, and when a UUID is defined,
the UUID reference as well as the naming reference shall be used and coherency of the file has
to be guaranteed by all SCTs.
The UUID attributes are defined as group of attributes defining both uuid and templateUuid
attribute used in all other elements.
Here is the XML schema definition of UUID attributes group:




– 12 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
9 The SCL syntax elements
9.1 Header
Figure 14 – UML diagram of Header section
Replace existing Figure 14 with the following new figure:

Replace the XML Schema extract following Figure 14 by the following new extract:



























© IEC 2024
Table 3 – Attributes of the Header element
Add the following new rows at the end of Table 3:
fileType The type of file which has been created (ICD, IID, CID, SSD, SCD, SED or future
types). Optional
uuid A unique identifier generated on creation of the first version of the file or on
creation of the project used to identify the file, with different version and revision.
Mandatory
baseUuid The unique identifier of the original file when derived files are generated from this
file (i.e. SED files created from a system SCD file).

Add the following new text, table and figures after Table 3:
The file is uniquely identified by a UUID which shall be generated by the tool creating the first
version of the file and shall not be altered by any other tool. When a new version of the same
file is created, the UUID remains the same, and only the version/revision shall be updated. This
will allow the tracking of files during the engineering of systems by identifying the UUID with
the version and revision.
A file UUID shall not be shared by different files (different type of file or same type but for
different purpose). It is up to the tool to determine if a file is a new version of a previous file or
a new file with a new UUID.
When multiple files can be created from the same file, the baseUuid attribute is used to identify
the original file. This will be used when SED files are created for the same SCD. In this case,
the uuid attribute will be a new one specific to the SED, and baseUuid will be the UUID of the
system file (i.e. the one found in the SCD). This concept could be used in the future for new
kind of files.
The element type tSclFileUUIDReference is used, depending on the context where it is
declared, and has the following syntax:


Definition of a reference to an SCL file by its UUID with an associated version revision,
corresponding to the definition of an SCL file header












The attributes fileUuid, version and revision of a file reference are the one of the Header of the
referenced file.
The attributes of the tSclFileUUIDReference element are defined in Table 54.

– 14 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
Table 54 – Attributes of the tSclFileUUIDReference element
Attribute Description
name
fileUuid The unique identifier attached to the referenced file if defined. Optional.
fileName The name of the file used on import. Optional.
fileType The type of file which has been used (ICD, IID, CID, SSD, SCD, SED or future types). It
depends on the step of the process and is mandatory.
version The specific version of the imported SCL file.
revision The specific revision of the imported SCL file.
when The date when the file has been imported. Optional.

Restrictions
• At least fileUuid or fileName shall be provided in an SCL File reference.
When a file is an SSD or an SCD, the Header element can reference SSD, SCD and/or SED
files which has been used to create the SCL file. An SCD can be a reference of another SCD
during transfer of a project from one tool to another one. This includes all imported files, even
partial SCL files. The newly imported files shall be appended to the end of the list. The history
will be represented by the ordering of the element.
For this the Header element has an optional element SourceFiles with the following structure
to reference the SCL file:




maxOccurs="unbounded"/>




On creation of a project for specification (SSD) or configuration (SCD) an existing file could be
used. Then, if it is decided to continue a previous project, the SourceFiles of the imported file
will be kept, otherwise the imported file will be considered as a SourceFile, and the previous
files will be cleaned up and the imported file will be identified as a SourceFile itself.
The reference between SCL files may be defined at Header and/or IED level (see 9.3.2). The
different cases of SCL file reference are summarized in Figure 25 and Figure 26.

© IEC 2024
Figure 25 – SCL file references

Figure 26 – IED file references
An IID file representing a proxy gateway may contain multiple SCD references, one for each
functionality of the gateway, representing each system when the system engineering is done
by separate projects. One functionality is the client part of the gateway attached to the
substation network (LAN), and another functionality is the server part of the gateway attached
to the remote network (WAN).
– 16 – IEC 61850-6:2009/AMD2:2024
© IEC 2024
Replace the existing XML Schema extract and seventh paragraph of 9.1 (before Table 4) with
the following new schema and text:


Allows an unrestricted mixture of character content and element content and
attributes from any namespace other than the target namespace, along with the 6 following attributes: Version, Revision, When,
Who, What, and Why















The history contains several history item entries. Each item identifies a (previously) approved
version of this SCL file by means of the attributes described in Table 4. A text within the items
can be used to explain further details to this version, and the list of SourceFiles used to create
current version may also be indicated, by moving the list of SourceFiles from the header to the
Hitem. The global history of the imported files is known by the current list in Header element
and the sum of the list in Hitem.
Replace the existing text of the eighth paragraph of Subclause 9.1 with the following new text:
The following example shows a header without history: