SIST EN 61850-6:2010/A1:2018
(Amendment)Communication networks and systems for power utility automation - Part 6: Configuration description language for communication in electrical substations related to IEDs
Communication networks and systems for power utility automation - Part 6: Configuration description language for communication in electrical substations related to IEDs
Kommunikationsnetze und -systeme für die Automatisierung in der elektrischen Energieversorgung - Teil 6: Sprache für die Beschreibung der Konfiguration für die Kommunikation in Stationen mit intelligenten elektronischen Geräten (IED)
Systèmes et réseaux de communication pour l'automatisation des services de distribution d'énergie - Partie 6: Langage pour la description de configuration pour la communication dans les postes électriques, entre les dispositifs électroniques intelligents (IED)
Komunikacijska omrežja in sistemi v postajah - 6. del: Jezik za opisovanje konfiguracije za komunikacijo v postajah z inteligentnimi elektronskimi napravami (IED) - Dopolnilo A1
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 61850-6:2010/A1:2018
01-december-2018
Komunikacijska omrežja in sistemi v postajah - 6. del: Jezik za opisovanje
konfiguracije za komunikacijo v postajah z inteligentnimi elektronskimi napravami
(IED) - Dopolnilo A1
Communication networks and systems for power utility automation - Part 6: Configuration
description language for communication in electrical substations related to IEDs
Kommunikationsnetze und -systeme für die Automatisierung in der elektrischen
Energieversorgung - Teil 6: Sprache für die Beschreibung der Konfiguration für die
Kommunikation in Stationen mit intelligenten elektronischen Geräten (IED)
Systèmes et réseaux de communication pour l'automatisation des services de
distribution d'énergie - Partie 6: Langage pour la description de configuration pour la
communication dans les postes électriques, entre les dispositifs électroniques intelligents
(IED)
Ta slovenski standard je istoveten z: EN 61850-6:2010/A1:2018
ICS:
29.240.30 Krmilna oprema za Control equipment for electric
elektroenergetske sisteme power systems
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
SIST EN 61850-6:2010/A1:2018 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 61850-6:2010/A1:2018
---------------------- Page: 2 ----------------------
SIST EN 61850-6:2010/A1:2018
EUROPEAN STANDARD EN 61850-6:2010/A1
NORME EUROPÉENNE
EUROPÄISCHE NORM
October 2018
ICS 33.200
English Version
Communication networks and systems for power utility
automation - Part 6: Configuration description language for
communication in power utility automation systems related to
IEDs
(IEC 61850-6:2009/A1:2018)
Systèmes et réseaux de communication pour Kommunikationsnetze und -systeme für die
l'automatisation des services de distribution d'énergie - Automatisierung in der elektrischen Energieversorgung -
Partie 6: Langage pour la description de configuration pour Teil 6: Sprache für die Beschreibung der Konfiguration für
la communication dans les postes électriques, entre les die Kommunikation in Stationen mit intelligenten
dispositifs électroniques intelligents (IED) elektronischen Geräten (IED)
(IEC 61850-6:2009/A1:2018) (IEC 61850-6:2009/A1:2018)
This amendment A1 modifies the European Standard EN 61850-6:2010; it was approved by CENELEC on 2018-07-12. 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, 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
© 2018 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 61850-6:2010/A1:2018 E
---------------------- Page: 3 ----------------------
SIST EN 61850-6:2010/A1:2018
EN 61850-6:2010/A1:2018 (E)
European foreword
The text of document 57/1918/FDIS, future edition 2 of IEC 61850-6/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-6:2010/A1:2018.
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2019-04-12
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2021-07-12
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-6:2009/A1:2018 was approved by CENELEC as a
European Standard without any modification.
2
---------------------- Page: 4 ----------------------
SIST EN 61850-6:2010/A1:2018
EN 61850-6:2010/A1:2018 (E)
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
NOTE 1 Where an International Publication has been modified by common modifications, indicated by (mod), the relevant
EN/HD applies.
NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu.
Add the following references:
Publication Year Title EN/HD Year
IEC 61850-4 - Communication networks and systems EN 61850-4 -
for power utility automation -- Part 4:
System and project management
IEC/IEEE 61850-9-3 - Communication networks and systems - -
for power utility automation - Part 9-3:
Precision time protocol profile for power
utility automation
Replace the existing reference to IEC 61850-7-1 with the following new reference:
Publication Year Title EN/HD Year
IEC 61850-7-1 2011 Communication networks and systems for EN 61850-7-1 2011
power utility automation -- Part 7-1: Basic
communication structure - Principles and
models
3
---------------------- Page: 5 ----------------------
SIST EN 61850-6:2010/A1:2018
---------------------- Page: 6 ----------------------
SIST EN 61850-6:2010/A1:2018
IEC 61850-6
®
Edition 2.0 2018-06
INTERNATIONAL
STANDARD
colour
inside
AMENDMENT 1
Communication networks and systems for power utility automation –
Part 6: Configuration description language for communication in power utility
automation systems related to IEDs
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 33.200 ISBN 978-2-8322-5033-4
Warning! Make sure that you obtained this publication from an authorized distributor.
® Registered trademark of the International Electrotechnical Commission
---------------------- Page: 7 ----------------------
SIST EN 61850-6:2010/A1:2018
– 2 – IEC 61850-6:2009/AMD1:2018
IEC 2018
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/1918/FDIS 57/1940/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.
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
and , or otherwise is clearly labeled in this standard as a
Code Component.
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.
If any updates are required to the published code component that needs to apply immediately
and can not wait for an amendment (i.e. fixing a major problem), a new release of the Code
Component will be issued and distributed through the IEC WebSite. Any new release of the
Code Component related to this part will supersede any previously published Code
Component including the one published within the current document.
The Code Component(s) included in this IEC standard are a set of .xsd. This Code
Component is published through the IEC WebSite; for details see 1.3 of the present
IEC standard.
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 web site 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.
---------------------- Page: 8 ----------------------
SIST EN 61850-6:2010/A1:2018
IEC 61850-6:2009/AMD1:2018 – 3 –
IEC 2018
INTRODUCTION
This Amendment 1 aims to amend the original content of IEC 61850-6:2009 and to correct its
content in order ensure a better interoperability of the components implementing it.
This Amendment 1 brings two distinct sets of changes
1) Resolved Interop Issues (covered by Clause 3 of this Amendment 1) 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 (Technical Issues) (covered by Clause 4 of this Amendment
1) which may have lead to interoperability issues.
The resolutions of these issues which lead to these changes are described in greater detail in
the Tissue database hosted at http://tissue.iec61850.com.
The only new features compared to the original IEC 61850-6:2009 are the inclusion of the
Process and Line elements supporting other application areas than substations, and
necessary enhancements to fully support the amended communication related parts. Apart
from this this Amendment 1 strictly respects the scope of the original edition.
Because some of the corrected issues may have a widespread impact on many pages of the
original standard, a complete consolidation of these changes into IEC 61850-6:2009 is
circulated through the reference 57/xxxx/INF, which reflects the content of IEC 61850-6:2009
as amended by this Amendment 1.
Technical issues summary
N°, Subject, Cat, Clause and Paragraph are as they appear on the Tissue database hosted at
http://tissue.iec61850.com where all technical issues have been stored from the origin of
IEC 61850.
“Subject” defines very briefly the topic under focus.
“Cat” defines whether this has been considered as an Interoperability Issue (IntOp2) or just a
need for amending IEC 61850-6:2009.
The Tissues which have been considered in this Amendment 1 are:
N° Subject Cat Clause Paragraph
658 Tracking related features IntOp2 Annex A
660 XML encoding header repeat Ed2 Annex A.4
FCDA element cannot be a
663 IntOp2 9.3.7 Table 22
"functionally constrained logical node"
668 Modeling of autotransformer IntOp2 9.2.4
678, 699 DO type description table Ed2 Table 43
687 ResvTms attribute at the SGCB Ed2 9.3.12
719 ConfDataSet maxAttributes defineds IntOp2 9.3.2 Table 11
FCDA elements in data set
721 Log element name IntOp2 9.3.5
731 SCL example inconsistent Ed2 9.3.4§
752 Input section naming Ed2 9.3.13
768 bType VisString65 is missing IntOp2 Annex A
779 Relative object references IntOp2 9.5.4.1
---------------------- Page: 9 ----------------------
SIST EN 61850-6:2010/A1:2018
– 4 – IEC 61850-6:2009/AMD1:2018
IEC 2018
N° Subject Cat Clause Paragraph
787 SICS I45 inconsistency Ed2 Annex G
788 SICS S56 from optional to mandatory IntOp2 Annex G
789 (822) ConfLdName for services applies to IntOp2 9.3.2 Table 11
client and server
804 valKind and IED versus system IntOp2 9.5.4.1
configurator
806 Max length of log name incosnsten to Ed2 Annex A SCL_BaseSimpleTypes
part 7-2
807 Indicate if ‘owner’ is present in RCB Ed2 9.3.2 Table 11
823 valKind for structured data attributes IntOp2 9.5.4.1
824 Short addresses at structured data IntOp2 9.3.6, 9.5.4.1
attributes
825 Floating point values IntOp2 9.5.4.1 Table 45
845 SGCB ResvTms IntOp2 9.3.2 Table 11
853 SBO and ProtNs IntOp2 9.5.5
855 recursive SubFunction Ed2 9.2.7
856 Voltage level frequency and phases Ed2 9.2.2
857 Function/SubFunction for primary Ed2 9.2.4
equipment
873 Examples for “curvpts” Ed2 9.3.6 end of paragraph
886 Missing 8-1 P-Types Ed2 Annex A
901 tServices at Ap and at IED Ed2 9.3.2 below Table 12
936 SupSubscription parameter usage is IntOp2 9.3.2 Table 11
difficult
948 Enumeration (string) value format IntOp2 9.5.6
949 type of LN inst is ambiguous Ed2 9.3.5 Table 17
1118 RptEnabled definition Ed2 9.3.8
1147 Filehandling service capability Ed2 9.3.2 Table 11
1195 Typographical error Ed2 9.3.2
1208 IP V6 address format IntOp2 Annex A.5
1284 SCSM mapping may require a Ed2 7
communication section in an ICD file
1298 How to differentiate preconfigured Ed2 9.3.2 Table 11
Report data sets from those generated
by the system tool
1304 Error in SCL object model Ed2 Figure 6
1318 SSD will not validate against XSD Ed2 9.2.6 Note 2
1328 Limitation of the size of identifiers IntOp2 9.5.2, 9.5.3, 9.5.6
1354 Changes to SICS Ed2 Annex G
1359 Replace “c37_238” with “61850-9-3” Ed2 9.3.2
1365 Need to tighten up the XSD in regards IntOp2 9.2.6 3
to IED name usage
1395 Client LN attributes IntOp2 9.3.8
1396 The use and configuration flow of Ed2 9.3.2 Table 11
LGOS and LSVS is Unclear
1397 Subscription limitation visible in IxD file Ed2 Annex G
1398 originalSclVersion management in SCT Ed2 9.3.2
1402 Extref during engineering Ed2 9.3.13, Annex
H(new)
---------------------- Page: 10 ----------------------
SIST EN 61850-6:2010/A1:2018
IEC 61850-6:2009/AMD1:2018 – 5 –
IEC 2018
N° Subject Cat Clause Paragraph
1415 SICS-S110 IID import mandatory Ed2 Annex G Table G.2
1419 Support of ldName on other IEDs Ed2 Annex G Table G.1
1434 Add capability to change nofASDU is Ed2 9.3.2 Table 11
missing
1444 Need to support fixed and SCT Ed2
controlled data sets
1445 ConfReportControl and a fixed Ed2 9.3.2 Table 11
reportSettings
1447 Restriction on EnumTypes in SCL Ed2
1448 Not possible to determine the Ed2
restriction on number of BRCBs if
rptMod=both
1450 originalSclXxx computation rules IntOp2 9.3.2
1457 Multiple DOI nodes with the same Ed2
name
1458 New ExtRef attributes for later binding Ed2
---------------------- Page: 11 ----------------------
SIST EN 61850-6:2010/A1:2018
– 6 – IEC 61850-6:2009/AMD1:2018
IEC 2018
INTRODUCTION
Add, after the first paragraph of the Introduction, the following new paragraph:
While this part describes the language to describe the configuration of IEC 61850 systems,
other parts of the standard describe how to configure the system and possible restrictions.
Therefore implementations claiming conformance to this standard shall take into account
constraints from the other normative references. Some references to the other parts have
been included for the purpose of clarification but these references are not all inclusive.
1 Scope
Replace the existing text of the Scope with the following new text:
1.1 General
This part of IEC 61850 specifies a file format for describing communication-related IED
(Intelligent Electronic Device) configurations and IED parameters, communication system
configurations, switch yard (function) structures, and the relations between them. The main
purpose of this format is to exchange IED capability descriptions, and SA system descriptions
between IED engineering tools and the system engineering tool(s) of different manufacturers
in a compatible way.
The defined language is called System Configuration description Language (SCL). The IED
and communication system model in SCL is according to IEC 61850-5 and IEC 61850-7-x.
SCSM specific extensions or usage rules may be required in the appropriate parts.
The configuration language is based on the Extensible Markup Language (XML) version 1.0
(see XML references in Clause 2).
This standard does not specify individual implementations or products using the language, nor
does it constrain the implementation of entities and interfaces within a computer system. This
part of the standard does not specify the download format of configuration data to an IED,
although it could be used for part of the configuration data.
1.2 Namespace name and version
This new section is mandatory for any IEC 61850 namespace (as defined by
IEC 61850-7-1:2011).
The parameters which are identifying this new release of the SCL namespace
xmlns:scl="http://www.iec.ch/61850/2003/SCL" are:
• Namespace Version: 2007
• Namespace Revision: B
• Namespace Release: 4
• Namespace release date: 2018/01/22
---------------------- Page: 12 ----------------------
SIST EN 61850-6:2010/A1:2018
IEC 61850-6:2009/AMD1:2018 – 7 –
IEC 2018
The table below provides an overview of all published versions of this 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 2018 IEC 61850-6:2009/AMD1:2018 IEC 61850-6:2007B4
2.0
Edition 2.1 2018 IEC 61850-6:2009+AMD1:2018 CSV IEC 61850-6:2007B4
1.3 Code Component distribution
The Code Components included in this IEC standard are also available as electronic machine
readable file at:
http://www.iec.ch/tc57/supportdocuments/IEC_61850-6.2018.SCL.2007B4.full.zip
The Code Component(s) included in this IEC standard are potentially subject to maintenance
works and user shall select the latest release in the repository located at:
http://www.iec.ch/tc57/supportdocuments
The latest version/release of the document will be found by selecting the file
IEC_61850-6.2018.SCL.{VersionStateInfo}.full.zip with the filed VersionStateInfo of the
highest value.
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 IECManifest contains different sections giving information on:
– The copyright notice
– The identification of the code component
– The publication related to the code component
– The list of the electronic files which compose the code component
– An optional list of history files to track changes during the evolution process of the
code component
The IECManifest related to this publication is:
COPYRIGHT (c) IEC, 2017. This version of this XSD is part of IEC 61850-
6:2009/AMD1:2018; see the IEC 61850-6:2009/AMD1:2018 for full legal notices. In case of any differences
between the here-below code and the IEC published content, the here-below defintion supersedes the IEC
publication; it may contain updates. See history files. The whole document has to be taken into account to have a
full description of this code component.
See www.iec.ch/CCv1 for copyright details.
IEC License
content="full" date="2018-01-22">
---------------------- Page: 13 ----------------------
SIST EN 61850-6:2010/A1:2018
– 8 – IEC 61850-6:2009/AMD1:2018
IEC 2018
startingVersion="SCL.XSD.v2007B" endingVersion="SCL.XSD.v2007B4"/>
The package is identified using the following naming rule:
{RefStandard}.{CodeComponentName}.{VersionRevision}.{LightFull}{PublicationStage}.zip
For current publication, the Code Component package name is:
IEC_61850-6.2018.SCL.2007B4.full.zip
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 without need to publish an amendment.
This is useful when InterOp Tissues need to be fixed. Then a new release of the Code
Component will be released, which supersedes the previous release, and distributed through
the IEC TC57 web site.
2 Normative references
Add the following two new references:
IEC 61850-4, Communication networks and systems for power utility automation – Part 4:
System and project management
IEC IEEE 61850-9-3, Communication networks and systems for power utility automation –
Part 9-3: Precision time protocol profile for power utility automation
Replace the existing reference to IEC 61850-7-1 with the following new reference:
IEC 61850-7-1:2011, Communication networks and systems for power utility automation –
Part 7-1: Basic communication structure – Principles and models
5 Intended engineering process with SCL
5.3 Use of SCL in the engineering process
Add, after the first sentence of the second paragraph of 5.3, the following new sentence:
Clause 10 provides more details about the engineering rights of the tool roles.
6 The SCL object model
6.1 General
Replace the existing text of the first numbered point in the fifth paragraph by the following:
1) Substation / Line / Process: this part describes the primary process related functions and
devices like switch yard, respectively any primary process in the functional view according
to IEC 81346-1, electrical connections on single line level (topology), and the designation
of equipment and functions;
---------------------- Page: 14 ----------------------
SIST EN 61850-6:2010/A1:2018
IEC 61850-6:2009/AMD1:2018 – 9 –
IEC 2018
Replace existing Figure 6 with the following new Figure 6:
1
Functional/substation structure
Function Subfunction
1 Product / IED structure
Communication structure
1
Transformer
Substation
1 1
SubEquipment
Equipment
1
1 Phase
Voltage
1
1
Bay
level 1
0.2
1
1
CBR DIS VTR
Terminal
1
ConnectivityNode
1
0.*
LNode Data
1 1.*
0.*
Client access points
0.*
1
1.* 1
AccessPoint
0,1 Server LDevice
1
1.*
1
1.*
1.*
1
0,1
Router
1
Subnetwork
IED
0,1
Clock
IEC
Figure 6 – SCL Substation object model
6.2 The substation model
Replace the existing title and text of Subclause 6.2 with the following new title and text:
6.2 The process model
The process model (upper part of Figure 6 for substations) is an object hierarchy based on
the functional structure of the primary process. A special primary process is the Substation,
which has its own SCL element. Another is the Line, which connects electrically bays of
substations. The generic Process element shall be used to model any additionally needed
structuring levels of a power grid above the substation and for all other primary processes.
Although each object is self-contained, its reference designation is derived from its place in
the hierarchy. Because LNs perform functions within the complete context of the Process /
Substation respective Line hierarchy, they can be attached as functional objects at each
function level. Typically, a switch controller LN is attached to a switching device, while a
measuring LN is attached to the bay, which delivers the measurands, and transformer-related
LNs are attached to the appropriate transformer.
NOTE 1 In the CIM model measurands are allocated to primary device terminals. This is a topological allocation,
while the allocation in SCL in first line serves functional naming. However, if the single line topology is modelled
completely, by means of the transformers (VTR, CTR) and their data acquisition nodes (TVTR, TCTR) also some
primary device terminal in the topology can be found to which the measurands belong according to the CIM model.
The purpose of the process model is
• to relate a logical node and its function to a function of or at the primary process (process
part or substation part or line part or equipment or subequipment);
• to derive a functional designation for the logical node from the process structure.
---------------------- Page: 15 ----------------------
SIST EN 61850-6:2010/A1:2018
– 10 – IEC 61850-6:2009/AMD1:2018
IEC 2018
The following objects of the functional structure (in hierarchical order) are used in the SCL
model, for power networks analogue to the CIM model for energy management systems. More
background information on these terms can be found in IEC 61850-2:
Process the whole or part of the primary process handled by the automation
system, which is no substation. Can be parts of the power grid containing
several substations, or complete other primary processes like power
plants.
Line a line connecting several substations.
Substation the object identifying a whole substation.
VoltageLevel an identifiable, electrically connected substation part having an identical
voltage level.
Bay an identifiable part or subfunction of the switch yard (substation) within
one voltage level.
Equipment an apparatus within the switch yard, for example circuit breaker,
disconnector, voltage transformer, power transformer winding etc. The
single line diagram of a switch yard shows the electrical connections
between these primary devices. Connectivity node objects model these
connections. Therefore, each primary device can contain at its terminals
references to the connectivity nodes to which it is connected. At single line
level, one or two terminals (connections) per equipment are normally
sufficient.
SubEquipment a part of an Equipment, which might especially be one phase of a three-
phase equipment.
ConnectivityNode the (electrical) connectivity node object connecting different primary
devices. Typical connectivity node examples are: connecting nodes within
a bay, bus bars connecting several bays in the same voltage level, lines
connecting bays in different substations. See also Equipment above.
Terminal an electrical connection point of a primary apparatus at single line level. A
terminal can be connected to a ConnectivityNode. Within SCL terminals
can be explicitly named, or exist implicitly.
Function allows additional functions at substation, voltage level or bay level, either
independent from the basic switch yard functionality like fire fighting or
building supervision, or as part of the switch yard like main 1 protection
and main 2 protection.
SubFunction a hierarchical subpart of a Function or SubFunction, e.g. earth fault
protection as subpart of the main 1 function.
EqFunction allows additional functions at or below Equipment level, e.g. redundant
functions on the same equipment.
EqSubFunction a hierarchical subpart of an EqFunction or EqSubFunction.
The PowerTransformer is a special equipment, which can hierarchically be located below
Substation, VoltageLevel or Bay. It contains Transformer windings as equipment, which might
again have a relation to a tap changer.
NOTE 2 Observe that the hierarchical structure is used for functional designations. If substructures of bays are
needed, this can be introduced by appropriate structured bay names. If, for example, a bay B1 is structured into
sub-bays SB1 and SB2, this would in the SCL model lead to two bays named B1.SB1 and B1.SB2. If logical nodes
are also attached to the B1 structure level, then B1 can be introduced as a third bay.
NOTE 3 In the CIM model the bay level is optional, while in SCL it is mandatory. However, if the bay level
structuring is not needed, a whole voltage level can be considered to be one bay. The only restriction here is that
the SCL syntax demands at least one character as name on each level, so that in this case the voltage level name
needs a
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.