75b41c86-5865-4ec0-8614-f3affdcde169 (1)

CDV 61850-6 IEC:2002 1 57/WG10
CDV2R8Draft IEC 61850-6
Communication Networks and Systems in Substations
Part 6: Configuration description language for communication in

electrical substations related to IEDs
Editors Note:
This version considers all language related comments and proposed additions to CD1
The CIM (IEC61970) related parts are preliminary, until the needed CIM model revision is ac-
cepted by WG13.
The examples in appendix F: the first one is not tested, T1-1 not adapted and completed;
This will be done until 14. September.
Please send any comments for inclusion into the CDV until latest 14. September 2002.
Version 8CDV, August 2002

CDV 61850-6 IEC:2002 2 57/WG10
CONTENTS
1 SCOPE ........................................................................................................................................................... 5
2 NORMATIVE REFERENCES ................................................................................................................... 6
3 DEFINITIONS .............................................................................................................................................. 7
4 ABBREVIATIONS ....................................................................................................................................... 8
5 INTENDED ENGINEERING PROCESS WITH SCL ............................................................................. 9
6 THE SCL OBJECT MODEL .................................................................................................................... 12

6.1 THE SUBSTATION MODEL ....................................................................................................................... 15
6.2 THE PRODUCT (IED) MODEL .................................................................................................................. 16
6.3 THE COMMUNICATION SYSTEM MODEL .................................................................................................. 17
7 CONFIGURATION DESCRIPTION FILES........................................................................................... 18
8 THE SCL LANGUAGE ............................................................................................................................. 19

8.1 SPECIFICATION METHOD ........................................................................................................................ 19
8.2 PRIVATE DATA....................................................................................................................................... 19
8.3 SCL LANGUAGE EXTENSIONS ................................................................................................................ 20
8.4 GENERAL STRUCTURE ............................................................................................................................ 21
8.5 OBJECT AND SIGNAL DESIGNATION........................................................................................................ 22
9 THE SCL SYNTAX ELEMENTS............................................................................................................. 26
9.1 HEADER ................................................................................................................................................. 26
9.2 SUBSTATION DESCRIPTION ..................................................................................................................... 27
9.3 IED DESCRIPTION .................................................................................................................................. 33
9.4 COMMUNICATION SYSTEM DESCRIPTION ................................................................................................ 46
9.5 LNODETYPE DEFINITIONS ...................................................................................................................... 49
ANNEX A (NORMATIVE) SCL SYNTAX XML SCHEMA DEFINITION
ANNEX B (NORMATIVE) EXTENSION SYNTAX FOR DRAWING LAYOUT COORDINATES
ANNEX C (NORMATIVE) RELATION BETWEEN SCL AND IEC 61970-301 (CIM)
ANNEX D (NORMATIVE) EXTENSION SYNTAX FOR MAINTENANCE
ANNEX E (INFORMATIVE) SCL DATA TYPE DEFINITION
ANNEX F (INFORMATIVE) EXAMPLES

CDV 61850-6 IEC:2002 3 57/WG10
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
COMMUNICATION NETWORKS AND SYSTEMS IN SUBSTATIONS
Part 6: Configuration description language for communication

in electrical substations related to IEDs
FOREWORD
1) The IEC (International Electrotechnical Commission) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of the IEC is to promote inter-
national co-operation on all questions concerning standardization in the electrical and electronic fields. To this
end and in addition to other activities, the IEC publishes International Standards. 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. The IEC collaborates closely with the International Organization for Standardi-
zation (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of the IEC on technical matters express, as nearly as possible, an interna-
tional consensus of opinion on the relevant subjects since each technical committee has representation from
all interested National Committees.
3) The documents produced have the form of recommendations for international use and are published in the
form of standards, technical reports or guides and they are accepted by the National Committees in that sense.
4) In order to promote international unification, IEC National Committees undertake to apply IEC International
Standards transparently to the maximum extent possible in their national and regional standards. Any diver-
gence between the IEC Standard and the corresponding national or regional standard shall be clearly indicated
in the latter.
5) The IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with one of its standards.
6) Attention is drawn to the possibility that some of the elements of this International Standard may be the subject
of patent rights. The IEC shall not be held responsible for identifying any or all such patent rights.
The International Standard IEC 61850-6 has been prepared by WG 10, 11, and 12 of IEC
technical committee 57: Communication networks and systems in substations.

CDV 61850-6 IEC:2002 4 57/WG10
INTRODUCTION
Part 6 of this standard specifies a description language for configurations of electrical sub-
station IEDs. This language is called Substation Configuration description Language (SCL). It
is used to describe IED configurations and communication systems according to parts 5 and
7-x of this standard. It allows the formal description of the relations between the substation
automation system and the substation (switchyard). At the application level the switchyard
topology itself and the relation of the switchyard structure to the SAS functions (logical
nodes) configured on the IEDs can be described.
SCL allows the description of an IED configuration to be passed to a communication and ap-
plication system engineering tool, and to pass back the whole system configuration descrip-
tion to the IED configuration tool in a compatible way. Its main purpose is to allow the inter-
operable exchange of communication system configuration data between an IED configura-
tion tool and a system configuration tool of different manufacturers.
The parts 8-x and 9-x of this standard, which are concerned with mappings of parts 7-x to
specific communication stacks, may extend these definitions according to their need with ad-
ditional parts, or just by restrictions on the way the values of objects have to be used.
The relative position of this part of the standard in the context of other parts is depicted in
Figure 1.
61850-7-4
Data Objects for Substation
Applications
61850-7-3
Attributes and Attribute Class
Definitions for Substations
61850-7-2
Abstract Communication
Service Interface (ACSI)
61850-7-1
Communication Reference
Model
61850-6
Substation Configuration
Language
61850-5
Communication Requirements
Figure 1 - Relative position of this part within IEC 61850

CDV 61850-6 IEC:2002 5 57/WG10
COMMUNICATION NETWORKS AND SYSTEMS IN SUBSTATIONS
Part 6: Configuration description language for communication

in electrical substations related to IEDs
1 Scope
This part 6 of IEC 61850 specifies a file format for describing communication related IED
configurations and IED parameters, communication system configurations, switchyard (func-
tion) structures, and the relations between them. The main purpose of this format is to ex-
change 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 substation configuration description language (SCL). The IED
and communication system model in SCL is according to parts 5 and 7-x of this standard.
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.
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.

CDV 61850-6 IEC:2002 6 57/WG10
2 Normative References
The following normative documents contain provisions that, through reference in this text,
constitute provisions of this International Standard. At the time of publication, the editions in-
dicated were valid. All normative documents are subject to revision, and parties to agree-
ments based on this International Standard are encouraged to investigate the possibility of
applying the most recent editions of the normative documents indicated below. Members of
IEC and ISO maintain registers of currently valid International Standards.
W3C, Extensible Markup Language (XML) 1.0, http://www.w3.org/TR/2000/REC-xml-

20001006
W3C, Name spaces in XML, http://www.w3.org/TR/1999/REC-xml-names-19990114
W3C, XML Schema Part 0: Primer, http://www.w3.org/TR/2001/REC-xmlschema-0-20010502
W3C, XML Schema Part 1: Structures, http://www.w3.org/TR/2001/REC-xmlschema-1-

20010502
W3C, XML Schema Part 2: Data Types, http://www.w3.org/TR/2001/REC-xmlschema-2-

20010502/
RFC 1953, GZIP file format specification version 4.3, http://www.ietf.org/rfc/rfc1952.txt
IEC 61850-5, Communication networks and systems in substations Part 5: Communication

Requirements for functions and device models
IEC 61850-7-1, Communication networks and systems in substations Part Basic communi-
cation structure for substations and feeder equipment Principles and models
cation structure for substations and feeder equipment Abstract communication service in-
terface(ACSI)
cation structure for substations and feeder equipment Common data classes
cation structure for substations and feeder equipment Compatible logical node classes and
data classes
IEC 61850-8-1, Communication networks and systems in substations Part 8-1: Specific
Communication Service Mapping (SCSM) Mapping to MMS(ISO/IEC 9506 Part 1 and Part
2)
Communication Service Mapping (SCSM) Serial unidirectional multidrop point to point link
Communication Service Mapping (SCSM) Mapping on a IEEE 802.3 based process bus
IEC 61346-1: 1996, Industrial systems, Installation and equipment and industrial products
Structuring principles and reference designations Part 1: Basic rules

CDV 61850-6 IEC:2002 7 57/WG10
3 Definitions
In general the glossary defined in part 2 of this standard apply. The following definitions are
used in this part additionally or with some added semantics:
3.1
Access point
a communication access point to an IED. This may be a serial port, an Ethernet connection,
or a client or server address dependent on the used stack. Each access point of an IED to a
communication bus is uniquely identified. Each server has exactly one (logical) access point.
3.2
Subnetwork
a communication system connection between IEDs with serial communication facilities. All
devices connected to a subnetwork can directly communicate to each other, without an inter-
vening router. Routers or gateways can connect subnetworks.
3.3
Device
any physical device, not only IEDs as in the other parts of IEC 61850. In the context of a
switchyard these are primary apparatuses like transformers and circuit breakers, in the con-
text of substation automation all IEDs.
3.4
Connectivity node (ConNode)
a connectivity node is a connection point between terminals of primary devices which has the
only task to connect them electrically with no resistance; e.g. a bus bar as connectivity node
connects bus bar disconnectors. The connection to a device is done at a device terminal. A
connectivity node can connect an arbitrary number of terminals (devices).
3.5
Subdevice
a part of a PrimaryDevice, which might especially be a phase of a three-phase device

CDV 61850-6 IEC:2002 8 57/WG10
4 Abbreviations
In general the glossary and abbreviations defined in part 2 of this standard apply. The fol-
lowing abbreviations are particularly useful for understanding this part and are repeated here
for convenience.
CIM Common Information Model of IEC 61970-301
DO DATA in IEC61850-7-2, Data object class or instance, depending on context
DTD Document Type Definition
SCL Substation Configuration description Language
UML Unified Modelling Language according to Booch / Jacobson / Rumbaugh
URI Universal Resource Identifier
XML Extensible Markup Language

CDV 61850-6 IEC:2002 9 57/WG10
5 Intended engineering process with SCL
Engineering of a Substation Automation system may start either with the allocation of func-
tionally pre-configured devices to switchyard parts / products / functions, or with the design of
the process functionality, where the allocation of functions to physical devices is made later
based on functional capabilities of devices and their configuration capabilities. Often a mixed
approach is preferred: a typical process part such as a line bay is pre-engineered, and then
the result is used within the process functionality as often as needed. For SCL this means,
that it must be capable of describing:
1. Pre-configured IEDs with a fixed number of logical nodes (LNs), but with no binding to a
specific process - only may be a relation to a very general process function part.
2. Pre-configured IEDs with a pre-configured semantic for a process part of a certain struc-
ture, e.g. a double busbar GIS line feeder.
3. Complete process configuration with all IEDs bound to individual process functions and
primary equipment, enhanced by the access control object definitions (access allow-
ances) for all possible clients.
4. As item 3 above, but additionally all predefined associations and client server connec-
tions between logical nodes on data level. This is needed if an IED is not capable of dy-
namically building associations or reporting connections (either on client or on server
side).
The last case is the complete case. Both case 3 and 4 are the result after SAS engineering,
while cases 1 and 2 are possible results after IED pre-engineering.
The scope of SCL as defined in this document is clearly restricted to these purposes:
1. IED capability description (points 1 and 2 above)

2. System description (points 3 and 4 above)
for the purpose of system communication engineering and description of the engineered
system communication for the device engineering tools in a standardised way.
The resulting object model however could also be the base for other engineering tasks, either
directly, or with some additions. Therefore, and because of additional needs of SCSMs, this
standard considers the language as defined here as the core model, and defines, how exten-
sions of this core model for SCSMs as well as other (engineering) purposes can be done in a
standardised way.
Figure 2 explains the usage of SCL data exchange in the above mentioned engineering proc-
ess. The grey shaded boxes above the dashed line indicate where SCL files are used. The
box IED capabilities corresponds to a result of steps 1 and 2 above, the other box to steps 3
respective 4 above.
The IED configurator is a manufacturer specific tool that shall be able to import / export data
(e.g. files) defined by this part of the standard. It provides IED specific settings and gener-
ates IED specific configuration files, or it loads the IED configuration into the IED.
An IED shall only be considered compatible in the sense of this standard series, if

CDV 61850-6 IEC:2002 10 57/WG10
It is accompanied either by an SCL file describing its capabilities, or by a tool, which can
generate this file from the IED.
It can use a system SCL file to set its communication configuration, as far as setting is
possible at all (i.e. as a minimum its needed addresses), ot it is accompanied by a tool
which can import a system SCL file to set these parameters to the IED.
The System configurator is an IED independent system level tool that shall be able to import /
export data (e.g. files) defined by this part of the standard. It imports configuration files from
several IEDs, as needed for system level engineering, and used by the configuration engi-
neer to add system information shared by different IEDs. Then the system configurator gen-
erates a substation related configuration file as defined by this part of the standard, which
may be fed back to the IED configurator for system related IED configuration.
IED Capabilities
(LN, DO)
IED Database System Con-
figurator
Association
Pre-configured exchanges
Relationship to primary topology
Engineering
Workstation IED Confi-
gurator
File Transfer (REMOTE)

File Transfer
(LOCAL)
Substation Gate-
way IEC 61850
Service
IED IED IED IED
Figure 2 - Reference model for information flow during the configuration process
The part below the dashed line of Figure 2 indicates the ways in which IED configuration data
produced by means of the IED configurator can be brought into the IED. This can be done
By local file transfer from an engineering workstation connected locally to the IED. This
file transfer is outside the scope of this standard.
By remote file transfer e.g. by the file transfer method of this standard. The file format is
not defined within this standard, but naturally SCL format is a possible choice.

CDV 61850-6 IEC:2002 11 57/WG10
By access services to parameter and configuration data defined according to this stan-
dard. In this case the standardised methods according to part 7 shall be used.

CDV 61850-6 IEC:2002 12 57/WG10
6 The SCL object model
The SCL in its full scope describes a model of
The primary system structure: which primary apparatus functions are used, and how the
apparatuses are connected. This results in a designation of all covered switchgear as
substation automation functions, structured according to IEC 61346-1.
The communication system: how IEDs are connected to subnetworks and networks, and
at which of their communication access points (communication ports).
The application level communication: How data is grouped into data sets for sending, how
IEDs trigger the sending and which service they choose, which input data from other IEDs
is needed.
Each IED: which logical devices are configured on each IED, which logical nodes of which
class and type belong to each logical device, and which reports with which data and
which (pre-configured) associations are available; which data shall be logged.
Instantiable logical node (LN) type definitions. The logical nodes as defined in part 7 have
mandatory, optional and user defined (external) data (DO) as well as optional services,
and are therefore not instantiable. In this document instantiable LNTypes are defined,
which contain as template the really available DOs and services.
The relations between instantiated logical nodes and their hosting IEDs on one side and
the switchyard (function) parts on the other side.
Note: SCL allows the specification of user defined DOs as extension of standard LN classes as well as completely
user defined LNs according to the rules of parts 7-4. This means, that the appropriate name space attributes shall
be defined in the logical node types.
An SCL file describes an instance of the model in a special way. However its semantic can
only be fully understood by reference to the model itself. This clause therefore describes the
model by using UML notation. The next clauses then define how an instance of the model is
formally described in SCL.
The UML object model is contained in figure 3. Note that it is not complete from the modelling
sense, i.e. it does not show any superclasses from which the used classes may be derived. It
restricts to those concrete object types that are used within SCL, in case of the substation
structure mainly for the purpose of functional designation. Further it does not contain the lev-
els below Data (DOs), which are defined e.g. in 7-2.
The object model has three basic object levels:
Substation: the switchyard devices (process devices), their connection on single line level
(topology), and the designation of devices and functions are described. The designations
are constructed according to the functional structure of IEC 61346.
Product: this stands for all SAS product-related objects like IEDs and logical nodes.
Communication: this contains communication related object types like subnetworks and
communication access points, and describes the communication connections between
IEDs respective indirectly between logical nodes as clients and servers.

CDV 61850-6 IEC:2002 13 57/WG10
Additionally the logical node type section allows specifying in a type oriented (i.e. reusable)
way which data and attributes are really existing on an IED. A logical node type is an instan-
tiable template of the data of a logical node.
More model details contained in SCL, e.g. the structure within the logical nodes, are de-
scribed in parts 7-x.
The substation object level and the product object level in itself form hierarchies, which are
used for naming and can be mapped to the functional and product structures according to
IEC 61346. The communication object level model just contains the communication connec-
tion relations of devices to subnetworks, between subnetworks by means of routers, and the
placement of master clocks at the subnetworks for time synchronisation. The modelling of
gateways is not considered here it is a local issue of the appropriate gateway logical node.
Nevertheless, it is recommended that a gateway from another protocol to IEC61850 models
all IEDs below as IEC61850 logical devices.
As can be easily seen from Figure 3, the logical node (abbreviated as LN or LNode) is the
transition object, which is used to connect the different structures. This means that the LN as
a product also has a functional aspect within the switchyard functionality and a communica-
tion aspect within the substation automation system.
The substation functional objects as well as the product related objects are hierarchically
structured. Each higher level object consists of lower level objects. This hierarchy is reflected
in the designation structure of the objects according to IEC 61346-1. The function structure of
IEC 61346-1 shall be used for the substation objects, while its product structure should be
used for IED designation and structure.
In SCL it is foreseen that within each structure two kinds of designation are possible:
A name is used as (hierarchical part of) a technical key to designate the object. Each
object within a hierarchy has an attribute Nam, which contains its reference part within
the hierarchy. Technical keys are used in technical documentation for building and main-
taining the system, or for automatic processing of engineering related information. This
designation is also used in SCL to describe links between different model objects. In this
case, as far as possible the attribute containing the link gets a name of the form <Tar-
gettype>Nam, e.g. DONam for a link to a Data object. This Nam relates to and mostly is
identical to what is called Name in part 7-2.
A description part is used as (hierarchical part of) an operator related object identifica-
tion. An object within a hierarchy has an attribute Desc, which contains its textual de-
scription part within the hierarchy. Textual identifications are for example used in operator
interfaces and operator manuals.
A reference (Ref) within SCL is, as defined in 7-2, a unique identification of an object, con-
taining as a path the concatenation of all names in the hierarchy levels above until the level
of the object. For forming names, also the term Instance with abbreviation Inst is used. It is a
part of a name, making it unique within this level (see examples later on).
The following clauses describe the different parts of the model, their meaning and respective
usage. Object attributes are mentioned here only if necessary for the understanding of the
model. Further object attributes are described later in the SCL definition. Further model de-
tails belonging to parts 7-x and especially explained in 7-1 and 7-2 are purposely not shown
here. The name model of the switch yard functionality however is only found in this part, and
therefore shown as far as used within this part.

CDV 61850-6 IEC:2002 14 57/WG10
Substation 1 1 1
1 Voltage Bay PrimaryDevice Subdevice
1 level Phase
1 1 1
1 0..5
Terminal CBR
1 DIS
ConNode
VTR
1
0..*
LNode Data
associations 1 1..*
1 1..* 1
1
IED AccessPoint 1 Server LDevice
1 1..* 1..* 0,1 1..*
1 Router Functional / substation structure
0,1
Subnetwork Product / IED structure
0,1 Clock
Communication structure
Figure 3 - SCL object model
The following Figure 4 shows an instance of this model: a simple example of a SA system
used for a switchyard. The naming is performed according to IEC 61346. The switchyard has
a 110kV voltage level E1. It is a double bus bar system with two line bays =E1Q1 and =E1Q3,
and a bus coupler =E1Q2. The IEDs are already assigned to switchyard functionality (e.g. the
bay controller -E1Q1SB1 as a product is assigned to bay =E1Q1, and its LN CSWI1 controls
the circuit breaker =E1Q1QA1 via the LN XCBR1 on the IED -E1Q1QA1B1). Observe that in
IEC 61346 terms here the bay is a transition object, i.e. it has a function (= sign, at switch-
yard level), and it is considered to be as product a part of the switch yard. Figure 4 shows
with the sign only the product-related designation. The functional name (at switchyard
level) is not repeated. The station level communication subnetwork is named W1. There are
additional three subnetworks at process level (W2, W3, W4). Access points are seen in the
picture, but their designations are not shown. Also logical devices and servers are not shown
in the picture. This means especially that dynamic connections like associations are not
shown.

CDV 61850-6 IEC:2002 15 57/WG10
-AA1
-P1
-SA1
-W1 logical bus

-E1Q1 -E1Q2 -E1Q3
-SB1 -BP1 -SB1 -SB1 -BP1
Control Protection Control Control Protection
IED IED IED IED IED
-CSWI1 -PIOC1 -CSWI1 -CSWI1 -PIOC1
-W2 process bus -W3 process bus -W4 process bus
=QB2
-B1 =QB1 =QA1 =QB2 =QB2
-B1
PISA PISA
=QA1
-XCBR1 -B1 PISA =QA1
-XCBR1
=QC1 =QE1 -XMEA1 -XCBR1 =QC1 =QE1 -XMEA1
-XMEA1, 2
Figure 4 - Example configuration
6.1 The substation model
The substation model (upper part of Figure 3) is an object hierarchy based on the functional
structure of the substation. 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 substation, they can be attached as lower level functional objects on each sub-
station 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.
The purpose of the substation model is
To relate a logical node to a substation function (substation part or primary device or

subdevice)
To derive a functional designation for the logical node from the substation structure
The following substation objects of the functional structure (in hierarchical order) are used in
the SCL model. More background information on these words can be found in the glossary
[IEC 61850-2]:
Substation: the object identifying a whole substation.
Voltage level: an identifiable substation part having an identical voltage. If this name
structure part is not needed (e.g. for a transformer, or a non electrical part
of the substation), then an empty designation string (name) for this level is
used, and no voltage value specified.
Bay: an identifiable part or subfunction of the switchyard (substation) within one

voltage level. Especially the transformer is a bay, which may either be

CDV 61850-6 IEC:2002 16 57/WG10
contained completely in one voltage level, or preferably outside a voltage

level, i.e. within a voltage level with empty designation string and no voltage
specified.
Device an apparatus within the switchyard, e.g. circuit breaker, disconnector, volt-
age transformer, power transformer winding etc. The single line diagram of
a switchyard shows the electrical connection of these primary devices.
Connectivity node objects model these connections. Therefore, each pri-
mary device can contain via terminals links to the connectivity nodes to
which it is connected. At single line level normally one or two terminals
(connections) are sufficient.
Subdevice a part of a primary Device, which might especially be a phase of a three-

phase device.
ConNode the (electrical) connectivity node object connecting different primary de-
vices. Typical connectivity node examples are: connecting nodes within a
bay (BayNode), bus bars connecting several bays in the same voltage level,
lines connecting bays in different substations. See also Device above.
Note: observe that the hierarchical structure is mainly used for functional designations. In case that substructures
of bays are needed, this can be introduced by appropriate bay names. IF e.g. a bay B1 shall be 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
shall be attached also to the B1 structure level, then B1 can be introduced as a third bay.
6.2 The product (IED) model
Products consisting of hardware or software implement the functions of the switchyard. The
scope of SCL from the product side only covers the hardware devices (called IEDs) that form
the substation automation system, and therefore restrict the model to them. Primary devices
as products are outside the scope of SCL, only their functional side is modelled by the sub-
station structure for functional naming purpose.
IED a substation automation device performing SA functions by means of LNs. It

is normally communicating via a communication system with other IEDs in
the SAS. Access point objects form the connection between an IED and
subnetworks (communication buses) in the communication system.
Server a communication entity within an IED according to part 7 of this standard. It

allows access via the communication system and its only access point to
the data of the logical devices and logical nodes contained in the server.
LDevice a logical device (LD) according to part 7-2 of this standard, that is con-
tained in a server of an IED.
LNode a logical node (LN) according to parts 5 and 7-2 of this standard contained
in a logical device of an IED. The LN contains Data (DO), which other Logi-
cal Nodes request, and it may need DOs contained in other LNs to perform
its function. The offered DOs (server capability) are described in SCL. The
needed DOs (LN client side) are related to the function implementation and
therefore determined by the IED configuration tool respective the engineer.
SCL allows optionally to describe them, so that a data flow on data level
between LNs can be modelled.
DO the DATA contained in the LNs according to part 7 of this standard.
This part of the standard introduces additionally

CDV 61850-6 IEC:2002 17 57/WG10
a Router function on an IED. This is a function of the communication network, therefore it

is described in the next subclause.
a Clock function to indicate where a subnetwork master clock is located.
6.3 The Communication system model
The communication model is, in contrast to the others, not a hierarchical model. It models the
logically possible connections between IEDs at and across subnetworks by means of access
points. A subnetwork is seen on this description level only as a connecting node between ac-
cess points, not as a physical structure. A logical device of an IED is connected to a subnet-
work by means of an access point, which may be a physical port or a logical address (server)
of the IED. Client LNs use the address attribute of the access point to build up associations
to servers on other IEDs containing logical devices respective to their contained LNs.
Although subnetworks only model logically possible connections, a correlation to the physical
structure can be built up by appropriate naming of subnetworks and access points, and by
the relation of access points to (one or more) physical connection points. The access points
are the matching elements (transition objects) of both this communication model and the
physical implementation of the communication system. The description and maintenance of
the physical structure is out of the scope of the core SCL.
Subnetwork a connecting node for direct (link layer) communication between access
points. It might contain routing on bridge level, but not on network level. All
access points connected to a subnetwork can communicate with all others
on the same subnetwork with the same protocol. SCSMs may define re-
strictions to this e.g. if the stack implements a master-slave bus. The sub-
network as used here is a logical concept. Several logical subnetworks with
different higher layer protocol could e.g. be used on the same physical bus
to allow mixing of higher level protocols on the same physical (lower)
layer(s).
Access point a communication access point of the logical device(s) of an IED to a sub-
network. There is at most one connection between a logical device and a
subnetwork on this logical modelling level. An access point may, however,
serve several logical devices, and the logical nodes contained in a logical
device may, as clients, use several access points to connect to different
subnetworks. Typically a switch controller LN may get data as a client from
a process bus (part 9-x of this standard), and provide data as a server to
the inter bay bus (part 8-1 of this standard). In the terminology of part 7 an
access point may be used by a server, a client, or by both. Further the
same (logical) access point might support different physical access ports,
e.g. an Ethernet connection and a serial PPP based connection to the same
higher level (TCP/IP) access point and same server.
Router Normally Clients connected to a subnetwork have only access to servers

connected to that subnetwork. The router function extends access to serv-
ers connected to another subnetwork at another access point of that IED
which hosts the router function. However, a router restricts the access to
those services which use a networking layer, all other services like GSE,
sampled values and time synchronisation messages are not allowed to
cross it.
Clock a master clock at this subnetwork, which is used to synchronize the internal
clocks of all (other) IEDs connected to this subnetwork.

CDV 61850-6 IEC:2002 18 57/WG10
7 Configuration Description Files

Configuration description files are used to exchange the configuration data between different tools,
possibly from different manufacturers. As already mentioned in section 5 (see also figure 2), there are
at least two kinds of configuration files to be distinguished for the data exchange between tools. This
is done by means of different file extensions. Nevertheless the contents of each file shall obey the
rules of the Substation Configuration Language SCL defined in the next section. Each file should
contain a version and revision number to distinguish different versions of the same file. This means
that each tool has to keep the version and revision number information of the last file exported, or read
back the last existing file to find out its version.
Note: The version identifies versions of the SCL file, not versions of the data models used within the tools. This is
a private issue of the tools.
The following types of SCL files are distinguished:
Data exchange from the IED configurator tool to the system tool (corresponding to points 1 and 2
of clause 5). This file describes the capabilities of an IED. It shall contain exactly one IED section
for the IED whose capabilities are described. Further it shall contain the needed logical node type
definition, and may contain an optional substation section.
The file extension shall be .ICD for IED Configuration Description.
Data exchange from the system configurator tool to IED configurator tools (corresponding to
points 3 and 4 of clause 5). This file contains all IEDs, a communication configuration section and
a substation description section.
The file extension shall be .SCD for Substation Configuration Description.
The IED Configuration Description file again may be used in different ways.
If the name of the IED (Ref attribute, see next clause) is left blank, then this is a file for a device
type, i.e. it describes the capabilities of a certain device type, and can be used as a start of engi-
neering for each device of this type. This file does not contain a communication system section,
but may contain an optional substation section that has the substation and voltage level names
(Ref attributes) undefined, i.e. set to an empty string.
If the name of the IED is given, this refers to an instantiated IED within a project. In this case the
communication section contains the current address of the IED. The substation section related to
this IED may be present and have name values assigned according to the project specific names.

CDV 61850-6 IEC:2002 19 57/WG10
8 The SCL language
The SCL language is based on XML (see normative references).
8.1 Specification method
The XML language contains a method to define the allowed vocabulary of XML document
types, the Document Type Definition (DTD). The later developed XML Schema is an en-
hancement to DTD which additionally allows to define data types and data type dependent
value coding. The XML Schema language can express more details syntactically, and is
therefore used here for the normative syntax definition of SCL. The appropriate XML Schema
definition is enhanced by appropriate (incomplete) examples illustrating the use of the spe-
cific feature defined, and additional written requirements, restrictions, and relations to the
object model, which shall be used or checked by the application reading or building an SCL
file. The complete normative XML schema definition is contained in the appendix.
In the following schema definition parts it is assumed that the SCL Schema definition file
starts as follows:
<?xml version="1.0" encoding="UTF-8"?>


<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDe-
fault="qualified">
and then ends with
</xs:schema>
The basic XML syntax is itself specified in a special form of extended Backus - Naur form
(EBNF). In certain cases reference is taken to elements defined there, by indicating them as
XML-EBNF elements.
In some cases the data format of values is important. Wherever possible, here the data type
coding (lexical presentations) of the XML Schema shall be used. If not explicitly said, all ele-
ment values are XML Schema strings, and all attribute values are of the XML Schema type
normalizedString, i.e. they are not allowed to contain tab, carriage return and line feed char-
acters. Further restrictions may be stated either in this document or in other parts of this
standard, mostly parts 7, 8 and 9. If any XML schema data type is used, it is referenced with
the prefix xs:, e.g. xs:decimal for decimal number coding. For convenience an overview about
coding of the most types used in SCL is given in Table 2 Data type mapping
8.2 Private Data
Private data entities appear on several levels of the SCL. The contents of these XML ele-
ments is, as seen from the SCL, transparent text (XML format CDATA). If the Private part
shall contain XML data, then this has to be bracketed with <![CDATA[ at the start, and ]]> at
the end.
Private data for different purpose can be distinguished by the value of its Type attribute.
The handling within tools shall be as follows:
The private data is owned by a tool / tool category. The owner is allowed to modify its con-
tents, and normally is the only one able to interpret the data. All other tools which read pri-
vate data have to preserve (store) its contents on SCL import, and regenerate it if an SCL file
containing this part is produced / exported.

CDV 61850-6 IEC:2002 20 57/WG10
The appropriate IED Configurator tool owns all private data within IED sections. The System
configurator tool owns all other private data (on top level, within the substation part, and
within the communication part). Only the LNodeType section might contain Private data from
the IED tool to which it belongs, as well as from the system configurator tool. Therefore Pri-
vate data for different purpose here shall be distinguished by the value of its Type attribute. If
manufacturers use it, this Type attribute value should start with a manufacturer specific string
part.
8.3 SCL Language extensions
Extensions of the data model with semantically new LNs and DOs are covered by the rules
stated in part 7-x for extensions, and by the SCL approach as a meta language to the data
model, i.e. data model element identifications do not appear in the language syntax itself.
The name scope of logical node classes, DATA and CDC attributes are described in SCL by
stating the appropriate name space values within the appropriate DATA attributes.
The core SCL as defined here is designed for a specific purpose described in clause 5. It can
however be used with smaller or bigger extensions like additional attributes for additional
(engineering) tasks. Further it leaves some communication stack dependent definitions to the
SCSMs. Therefore the following describes SCL extension possibilities.
8.3.1 Additional semantics to existing syntax elements
Some language elements of SCL like Desc have a weakly defined semantic, some like the
parameter P have purposely been left open. An SCSM shall or a further standard can define
(additional) semantics to these elements. This can be done e.g. by defining a Type value for
a P parameter with an own semantic.
8.3.2 Data type constraints
The usage of XML schema based data types allows already on the syntactic level to further
restrict the range of some values. A restriction shall use one of the allowed subtypes of the
types defined in this core language.
8.3.3 XML name spaces
For all tag elements (sub-)tags and attributes can be added. These shall however belong to a
defined XML name space with a defined semantics for all these elements. The used name
spaces shall be defined at the main tag (SCL). For private name spaces the used internal
name space abbreviation shall start with the character e. An example of a standard extension
for single line or communication diagram layouts is given in the appendix. The name space
URI of this version of the core SCL (which is normally used as default name space in case
additional elements are used in an SCD or ICD file) is xmlns:scl =
http://www.iec.ch/61850/scl001.
All tools compliant to this standard shall be able to import an SCL file with name space defi-
nitions, at least for the core SCL as the default name space. Name spaces other than the
SCL core, which are not understood by the tool, shall be ignored by it. This means especially,
that an IED tool which exports data in its own name space to an ICD file, can NOT expect
that this information is contained resp. preserved in a SCD file coming from the system con-
figurator tool.
8.3.4 Private parts
For small manufacturer or project specific extensions the Private parts can be used (see 8.2).
The advantage of private parts is that the data content is preserved at data exchange be-
tween tools.

CDV 61850-6 IEC:2002 21 57/WG10
8.3.5 Another XML syntax
Naturally a completely new standardised or private XML based syntax can be used to extend
the SCL data model with additional objects or attributes. In this case references to the ob-
jects contained in the SCL model shall be defined in this new XML file, and the naming phi-
losophy of this standard shall be followed to be able to identify the objects. An example for
the CIM model of IEC 61970-301 is given in the appendix.
8.4 General structure
An SCL - XML document starts with the XML-EBNF element prolog, and continues then with
elements as defined in the following XML schema definition part. The whole SCL definition
part is contained in the SCL element:
<xs:element name="SCL">
<xs:complexType>
<xs:sequence>
<xs:element ref="Header"/>
<xs:choice maxOccurs="unbounded">
<xs:element ref="Substation"/>
<xs:element ref="Communication"/>
<xs:element ref="IED"/>
<xs:element ref="LNodeType"/>
<xs:element ref="Enumtype"/>
</xs:choice>
<xs:element ref="Private" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
The SCL element shall contain a header section, and at least one of the sections Substation,
IED, LNodeType, Communication, which are further explained below. Each of these sections
except the header may appear more than once. At the end a Private section may follow which
belongs to the system configurator tool.
<xs:element name="Private">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="Type" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
The format of the contents of the private section is free. The Type attribute allows a possible
distinction between different Private parts already at SCL level
The prolog shall contain the identification of the XML version to allow automatic detection of
the character coding used. UTF-8 coding is the preferred coding. In case that verification
against a DTD is wanted a reference to a DTD definition file can be added. The preferred way
of validation is against the schema definition, which is identified by namespace and location
at the SCL element tag.
An example SCL file as defined above looks as follows:
<?xml version="1.0" encoding=UTF-8?>

<!DOCTYPE SCL SYSTEM "Mypath/scl-01.dtd">


CDV 61850-6 IEC:2002 22 57/WG10
<SCL xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.iec.ch/61850/scl001"
xs:noNamespaceSchemaLocation="Mypath/scl-001.xsd">

</SCL>
The DOCTYPE specification shall not be used, if a schema verification can be performed by
the file user. In this case the xs:noNamespaceSchemaLocation references the place where
the schema definition file is located. A complete XML schema file for the core SCL is con-
tained in the annex.
8.5 Object and Signal designation
The SCL model allows two kinds of object designation:
1. A technical key which is used on engineering drawings and for signal identifications. This
is contained in attribute Nam as identification of each object. If this value is used as ref-
erence to an object it is contained in an attribute name starting with a string denoting the
reference target object type, and ending with the string Namf. The technical key is used
within SCL for referencing other objects.
2. A user oriented textual designation. This is contained in attribute Desc. Attributes are not
allowed to contain carriage return, line feed or tab characters.
Further a general description tag Text can be used to add descriptive textual data. The
meaning of this data is purposely not specified further. Each tool shall preserve imported text
data for export.
8.5.1 Object designations in an object hierarchy
In case of the hierarchically structured objects of the substation structure and the product
structure, both Nam and Desc attribute for each object contain only that part which identifies
the object within this level of the hierarchy. Their value may be an empty string, e.g. if there
is only one object within the hierarchy level, and the hierarchy level shall not be visible in the
name. The full object reference consists of the concatenation of all name parts of higher hi-
erarchy levels up to this level. It is up to the configuring engineer to ensure that the refer-
ences are unique after concatenation. This shall be reached by using a designation (syntax)
convention as specified in IEC 61346. This means especially, that all levels can be directly
concatenated, if the higher level ends with a number and the lower level starts with an alpha
character else an intervening character, preferably a dot (.), shall be put between them. In
case that the name is the empty string, no delimiting character is needed at this level. Other
separation characters may be specified for name mapping in SCSMs or according to
IEC61346.
Transition objects, i.e. objects appearing in more than one hierarchical structure, may be
designated by several references, one in each structure. In the case of SCL this applies es-
pecially to LNs, which are in the substation functional structure as well as in the IED product
structure.
8.5.2 Signal identifications to be used in the communication system
According to part 7 signal identifications are built from the following parts (Figure 5):
1. A User defined part identifying the logical device LD in the process (LDName).
2. A (function related) part to distinguish several LNs of the same class within the same IED
/ LD (LN-Prefix).

CDV 61850-6 IEC:2002 23 57/WG10
3. The standardised LN class name and the LN instance Id, which distinguishes several LNs
of the same class and prefix within the same IED.
4. A signal identification consisting of data and attribute name as defined in the standard.
defined in 7-3 defined in 7-4
configurable
LDName LNName DataName DataAttributeName

LN-Prefix LN class name LN-Instance-ID
Part 1 Part 2 Part 3 Part 4
Figure 5 Elements of the signal identification as defined in IEC 61850-7-2
Name parts 2 and 3 above together form the LN name and distinguish different LN instances
within the same LD of an IED. Both can be used freely. A function related LN-Prefix is pref-
erably used during functional engineering, or to bind an instantiated LN to some process se-
mantics. The instance Id of part 3 shall be used to distinguish instantiated LNs which are not
(already) bound to a process semantic (e.g. a CSWI which is not bound to some specific
switch type).
The mapping of these signal name parts to actual signal names is stack and mapping related
and therefore contained in parts 8 and 9 of this standard. From the SCL point of view, it is
sufficient to determine the contents of these parts for a specific SAS. However, parts 8 and 9
may contain further restrictions on length and contents of name parts.
The LNodeTypes definition section of the SCL and the standardised names as defined in part
7-3 and 7-4 of this standard define the possible values for name parts 3 and 4. The LN in-
stance Id and the prefix are defined in the IED section of the SCL.
For name parts 1 and 2 there are two options (see also Figure 6 and Figure 7). For both a
separation of part two into an IED name (reference) IEDNam and a LD instance name LDInst
within this IED is used.
1. Function related naming: Part 1 is the name of the object of the substation section, to
which the LN is attached. If it is a PrimaryDevice, use the name parts from Substation
name to Bay name as part 1, and use the PrimaryDevice name (followed eventually by a
Subdevice name) as part 2. Concatenate the IED LD Inst to part 1 (Figure 6). In case that
LNs are attached to higher levels than the bay level, naturally the part 1 has to be short-
ened appropriately, and the part 2 stays empty, or can be used for the level where the LN
is attached to.

CDV 61850-6 IEC:2002 24 57/WG10
LDName LNName
IED Section:
Attribute Inst of element LN
Substation section: IED section : Substation section:

Attribute Nam of element substation & Attribute Inst of element Attribute Nam of element Device
of element VoltageLevel & LDevice & of element Subdevice
of element Bay
Header:
NameStructure="FuncName"
Figure 6 Elements of the signal name using functional naming
2. Product related naming: Part 1 is the name of the IED in the IED (product) section, on
which the LN is configured, concatenated with the LD Instance Id. Part 2 stays as prede-
fined within the IED (Figure 7).
LDName LNName
Predefined by IED
IED Section:
Attribute Inst of element LN
IED Section: IED Section: Header:

Attribute Nam of element Attribute Inst of element NameStructure="IEDName"
IED LDevice
Figure 7 Elements of the signal name using product naming
The SCL model leaves both options open, but allows the header part to specify if option 1
(functional naming) or option 2 (product naming) is taken for signal naming at communication
time. It is recommended to use the LN instance Id in such a way that the LN class and LN in-
stance ID together are always unique. This allows the way of naming (with / without prefix) to

CDV 61850-6 IEC:2002 25 57/WG10
be changed at a later time, and even to later replace preconfigured prefixes by prefixes re-
lated to the functional structure.
8.5.3 Naming example
Figure 8 below shows an example of an IED with LNs, which control a circuit breaker QA1.
The naming is chosen according to IEC 61346. In this example the IED as a product has the
same higher level product designation part according to the bay (-E1Q1) as the controlled
circuit breaker QA1 has in its functional designation (=E1Q1QA1). The figure shows the re-
sulting references within different structures, and the resulting LN reference for communica-
tion.
Voltage level E1 In the substation structure

this CBR is identified as
=E1Q1QA1
Bay Q1
QA1
In the substation structure
this LN is identified as
SB1
IED =E1Q1LD2QA1CSWI2
LN1 LN2 LN1 LN2 In the IED (product)
structure
LD1 LD2 this LN is identified as
Access point S1 -E1Q1SB1LD2CSWI2
Station bus
W1
In the communication structure

In theIED structurethis LD
this connection is identified as
is identified as
W1E1Q1SB1S1
-E1Q1SB1LD2
Figure 8 - Names within different structures of the object model
If now data objects of LN2 of LN class CSWI within LD2 shall be named with names from the
function structure, then the LN reference according to part 7-2 would be
E1Q1LD2/QA1CSWI2. If the reference shall be taken from the product structure, it would be
E1Q1SB1LD2/CSWI2. Observe that the whole name in each case shall be unique within the
system, which is the case for both names above. However, in case of the functional name the
LD reference E1Q1LD2 alone is not necessarily unique within the system (only within the
IED), because there could be another IED within bay E1Q1 having an LD2. Only the relation
of E1Q1QA1CSWI2 to the IED E1Q1SB1 in the model allows finding the correct IED for this
LD, and E1Q1LD2 then identifies uniquely the LD within this IED.
Note: if the reference is taken from the functional structure, and if there could be several IEDs within the functional
part before the LD name part, it is recommended that the LDs are identified with names from the functional struc-
ture. If, for example, there are protection and control IEDs within the same bay, the LD name part could identify
the protection and control subfunctionswithin the bay.
Note: if already a LN prefix is used at a preconfigured IED, then this shall always be taken as name part. In case
of functional naming the engineering process has to assure that the prefix and the device / subdevice identification
are identical.

CDV 61850-6 IEC:2002 26 57/WG10
9 The SCL syntax elements
9.1 Header
The header serves to identify an SCL configuration file and its version, and to specify options
for the mapping of names to signals.
<xs:element name="Header">
<xs:complexType>
<xs:sequence>
<xs:element ref="History" minOccurs="0"/>
<xs:element ref="Text" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="Ref" type="xs:string" use="required"/>
<xs:attribute name="Version" type="xs:string"/>
<xs:attribute name="Revision" type="xs:string" default=""/>
<xs:attribute name="ToolId" type="xs:string" default=""/>
<xs:attribute name="NameStructure" use="required">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="FuncName"/>
<xs:enumeration value="IEDName"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
Ref a reference identifying this SCL file

Version the version of this SCL configuration file
Revision the revision of this SCL configuration file
ToolId the manufacturer specific identification of the tool that was used to create
the SCL file
NameStructure element indicating if communication system signal names are built from
the substation function structure (FuncName) or from the IED product
structure (IEDName)
Note: the attribute Ref is mandatory, while Revision is by default the empty string meaning the original revision of
the configuration.
<xs:element name="Text" type="xs:string"/>
Note: the Text syntax element for describing text will be used in several places.
The revision history is optional. The same syntax can be used also for other documents re-
quiring a revision history. If present, it should have the following form:
<xs:element name="History">
<xs:complexType>
<xs:sequence maxOccurs="unbounded">
<xs:element ref="Hitem"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Hitem">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="Version" type="xs:string"
use="required"/>

CDV 61850-6 IEC:2002 27 57/WG10
<xs:attribute name="Revision" type="xs:string"

use="required"/>
<xs:attribute name="When" type="xs:string" use="required"/>
<xs:attribute name="Who" type="xs:string"/>
<xs:attribute name="What" type="xs:string"/>
<xs:attribute name="Why" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
The History contains several history item entries. Each item identifies a (previously) approved
version of this SCL file. A text within the items can be used to explain further details to this
version.
Version the version of this history entry

Revision the revision of this history entry
When date when the version / revision was released
Who who made / approved this version / revision
What what has been changed since the last approval
Why why the change has happened.
The following shows a completely filled header example without history, where the signal
names are taken from the substation function structure:
<Header Ref=1KHL1000546 Version=1 Revision=

ToolId=MySystemTool V1.2 NameStructure=FuncName>My SA Project
</Header>
9.2 Substation description
The substation section serves to describe the functional structure of a substation, and to
identify the primary devices and their electrical connections. For an industrial process or to
describe whole power networks it is possible to have several Substation sections, one for
each substation served by the SAS.
Note that the Nam attribute is always mandatory, although it may have an empty string as a
value, e.g. if there is only one object within the appropriate hierarchy level. This Nam value is
also a reference of the substation, because it shall be unique for all substations contained in
the SCL file.
If the Desc attribute is missing, it gets as default value an empty string.
Logical nodes (LNode) can be attached at each level of the structure. Logical node instances
at the same level shall have different identifications.
<xs:element name="Substation">
<xs:complexType>
<xs:sequence>
<xs:element ref="LNode" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="VoltageLevel" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Nam" type="xs:string"/>
<xs:attribute name="Desc" type="xs:string"/>
</xs:complexType>
</xs:element>

CDV 61850-6 IEC:2002 28 57/WG10
The Private element here and in all following hierarchical levels allow the system configurator
tool to add private data to the appropriate objects. The syntax definition of Private is in the
SCL subclause.
9.2.1 Voltage level

<xs:element name="VoltageLevel">
<xs:complexType>
<xs:sequence>
<xs:element ref="Bay" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Voltage" type="xs:string"/>
</xs:complexType>
</xs:element>
The voltage level attributes are as follows

Nam a name identifying this voltage level
Desc a descriptive text for this voltage level
Voltage the voltage, a decimal number followed by the unit (e.g. 110kV)
9.2.2 Bay level

<xs:element name="Bay">
<xs:complexType>
<xs:sequence>
<xs:element ref="ConNode" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="Device" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="Private" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
The ConNode element allows to explicitely define connectivity nodes within this bay, and also
to attach logical nodes to them. Its text part can be used to contain some freely usable de-
scription. Its Nam attribute identifies the ConNode instance within the bay.
<xs:element name="ConNode">
<xs:complexType>
<xs:sequence>
</xs:sequence>
<xs:attribute name="Nam" type="xs:string" use="required"/>
<xs:attribute name="Desc" type="xs:string" />
</xs:complexType>
</xs:element>
Note: If a bus bar does not contain any primary devices it can be modelled as a bay that only contains connectivity
nodes.
Note: a transformer is modelled as a bay. Its VoltageLevel might have the empty string as Nam, if the transformer
shall be outside any voltage level.

CDV 61850-6 IEC:2002 29 57/WG10
9.2.3 Primary device level

<xs:element name="Device">
<xs:complexType>
<xs:sequence>
<xs:element ref="Connection" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="Subdevice" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Desc" type="xs:string" />
<xs:attribute name="Type" type="xs:NMTOKEN" use="required"/>
</xs:complexType>
</xs:element>
Connections within the SCL model the substation topology on the level of a single line, i.e.
the number of phases and special connections between phases are not considered here. The
maximum number of possible connections to connectivity nodes depends on the terminals
available for a device function type. The following type codes for attribute Type are selected
according to part 7-4 of this standard as far as possible:
Type code Meaning Number of terminals

(connections to differ-
ent connectivity nodes)
CBR Circuit breaker 2
DIS Disconnector or earthing switch 2
VTR Voltage transformer 1
CTR Current transformer 2
PTW Power transformer winding 1
GEN Generator 1
CAP Capacitor bank 1/2
REA Reactor 1/2
CON Converter 1/2
MOT Motor 1
EFN Earth fault neutralizer (Peterson coil) 1
PSH Power shunt 2
BAT Battery 1

CDV 61850-6 IEC:2002 30 57/WG10
BSH Bushing 2
CAB Power cable 2
GIL Gas insulated line 2
LIN Power overhead line or line segment; 2

line segments connected by connec-
tivity nodes form a line. A line seg-
ment within a substation could be
used to attach e.g. special LNs, or
physical line properties. For a GIS
line segment also GIL could be used
instead.
RRC Rotating reactive component 1
SAR Surge arrestor 1
TCF Thyristor controlled frequency con- 2

verter
TCR Thyristor controlled reactive compo- 2

nent
IFL Infeeding line; substation limiting 1

object; models a possibly infeeding
power network line outside the sub-
station at the single line border
Table 1 Primary apparatus device type codes
Additionally private types may be used. To allow compatibility with future enhancements of
this standard, they shall start with character E.
A connection definition contains the reference to one connectivity node to which the device is
connected (ConNode in our model of figure 3), and optionally the name of the device terminal
which connects to this connectivity node. The reference is hierarchically structured. In SCL
only the node name part CNodeNam is mandatory, all other parts are optional. If they are not
present they get the value of the appropriate hierarchy levels. This means that if only the
node part CNodeNam is defined, it is a node in the same Substation / Voltage level / Bay as
the device itself.
<xs:element name="Connection">
<xs:complexType>
<xs:attribute name="CNodeNam" type="xs:string" use="required"/>
<xs:attribute name="Terminal" type="xs:string"/>
<xs:attribute name="BayNam" type="xs:string"/>
<xs:attribute name="VLNam" type="xs:string"/>
<xs:attribute name="SSNam" type="xs:string"/>
</xs:complexType>
</xs:element>
The attribute meaning in detail:

CDV 61850-6 IEC:2002 31 57/WG10
CNodeNam the node identification within the bay

Terminal the device terminal which connects to the connec-
tivity node
BayNam the bay name (e.g. to bus bar)
VLNam the voltage level name
SSNam the substation name (e.g. for lines to other substa-
tions)
Device terminals are in general only needed if the device polarizes the power flow, i.e. the
connections are not interchangeable. If the terminal attribute is left empty, but a terminal
designation needed, then the default is the device identification (SSNam VLNam BayNam
DevNam) together with the connectivity node identification. If the connected connectivity
node is in the same bay, then CNodeNam is sufficient as identification, else the terminal has
to be identified additionally by the full connectivity node reference.
There is one predefined connectivity node with CNodeRef GROUNDED. This is used to
model earth potential. Thus an earthing switch is an isolator (type DIS) that is connected on
one side to the connectivity node GROUNDED. It is up to the tool to decide if GROUNDED is
one single node for the whole substation, or a separate node at each place where connected,
or something in between e.g. per bay or voltage level.
9.2.4 Subdevice level
Subdevices are parts of the primary devices, like a pump is part of a switch, or like a phase
of a switch is a part of the whole switch. Especially they allow specifying a phase relation of
LNs.
<xs:element name="Subdevice">
<xs:complexType>
<xs:sequence>
<xs:element ref="LNode" minOccurs="0" maxOccurs ="unbounded"/>
<xs:element ref="Private" minOccurs="0" maxOccurs ="unbounded"/>
</xs:sequence>
<xs:attribute name="Phase" default="all">
<xs:simpleType>
<xs:enumeration value="A"/>
<xs:enumeration value="B"/>
<xs:enumeration value="C"/>
<xs:enumeration value="N"/>
<xs:enumeration value="all"/>
<xs:enumeration value="none"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
Attribute definition:
Ref the identification of the subdevice relative to the device designa-
tion (e.g. L1, if related to phase A)
Phase The phase to which the subdevice belongs.
The following phase values are allowed: A, B, C, N (neutral), and the empty string (default).
The empty string means that either the subdevice covers all existing phases, or is not related
to any phase.

CDV 61850-6 IEC:2002 32 57/WG10
9.2.5 Substation function logical nodes
The logical node (LN, LNode) defines the SA function part performed at the appropriate level
of the hierarchy. The LNode element identifies the SA function by specifying a logical node
(LN) as defined in parts 5 and 7 of this standard. Desc contains some operator-related text
describing the LN and its usage.
<xs:element name="LNode">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="Text"/>
</xs:sequence>
<xs:attribute name="Inst" type="xs:string"/>
<xs:attribute name="LNClass" type="xs:NMTOKEN" use="required"/>
<xs:attribute name="Prefix" type="xs:string"/>
<xs:attribute name="LDInst" type="xs:string"/>
<xs:attribute name="IEDNam" type="xs:string"/>
</xs:complexType>
</xs:element>
The attribute definitions are
Inst the LNode instance identification
LNClass the LN class as defined in parts 5 and 7
IEDNam the name of the IED which contains the LN
LDInst the LD instance on the IED which contains the LN
Prefix the LNode prefix used in the IED (if needed)
During functional engineering the LNode element defines a (functional) LN instance in the
plant. In this case the IEDNam shall be missing, and Inst then is an arbitrary number, as long
as LNClass and Inst together are unique within the substation object level of the LN. If the
connection of functions to the SAS is needed, IEDNam shall be specified, and Inst together
with LNClass shall be also unique within the IED (and fit to some LN residing on the IED).
Note: for LLN0 the value of Inst is the empty string. In all other cases it is an unsigned number.
The IEDNam identifies the IED on which the LN resides, the LDInst the LD within this IED to
which the LN belongs. LNClass and Inst (meaning the LN instance Id according to part 7)
then identify the logical node within that IED. In case that the IED uses prefixes to identify
semantic binding, also this prefix additionally to Inst identifies the LN. In this way the binding
between the substation function and the SAS is defined.
9.2.6 Substation section example
The following incomplete SCL example contains a substation section with one bay E1Q1,
which contains a circuit breaker QA1 and a disconnector QB1, both electrically connected to-
gether at connectivity node L1. A logical node of type CSWI controls each switch. No link to
IEDs is defined.
<Substation Nam="">
<VoltageLevel Nam="E1">
<Bay Nam="Q1">
<ConNode Nam="L1"/>
<Device Nam="QA1" Type="CBR">
<LNode Inst="1" LNClass="CSWI"/>
<Connection CNodeNam="L1"/>
</Device>
<Device Nam="QB1" Type="DIS">
</Device>
</Bay>

CDV 61850-6 IEC:2002 33 57/WG10
</VoltageLevel>
</Substation>
9.3 IED description
The IED section describes the (pre-) configuration of an IED: its access points, the logical
devices, and logical nodes instantiated on it. Further it defines the capabilities of an IED in
terms of offered communication services and, together with its LNType, instantiated data
(DO). There shall be an IED section for each IED. IED names (Nam attribute) shall be unique
within the file. In case that just the descriptions of pre-configured IEDs are contained in the
file, Nam shall be the empty string to indicate that the IED has not been bound to a place in
the project. The system configurator tool should handle this like an IED type, i.e. a pre - con-
figured product type, from which an arbitrary number of product (hardware) instances can be
produced.
Note: because the IEDNam is unique within a system, it is also a reference.
A special IED function Router is introduced. An IED containing a router function connects
different subnetworks by means of its access points. The router IED may have no logical de-
vices and no logical nodes. In this case it is managed and supervised by a separate network
management system, outside the application scope of this paper. A router is a limiting border
for real time related message types, which are not allowed to cross it:
Time synchronisation messages
GSE messages
Sampled measurement values
All other messages are routed through with some time delay.
Additionally to the stand-alone router IED described above, the router function can reside on
an IED containing additionally clients or servers.
An access point may belong to a server with logical devices, which contain logical nodes. In
this case the server of the access point provides access to the LDs and LNs, while the LNs
as clients may use all IED access points (not only that of the server) to access data (on LNs
on servers) on other IEDs. An access point always has a server, if the IED shall be super-
vised remotely, because the LN0 of the servers logical device is used to supervise the IED.
Only if all LNs on an IED are using an access point as client only, and the IED shall not be
supervised, then an IED without a server is needed. It is recommended that an IED contains
at least one server. An access point without server may then be used to get data from lower
level busses, i.e. a bay unit from process bus. However, this data from the lower level bus
cannot be seen directly on the higher level bus unless a router function also resides on this
IED. The following figure gives a typical example of an IED connected to station bus and pro-
cess bus.
Station bus access point
Server connections
IED
Server
Logical Device Logical Device
Router
LN LN LN
Client connections

CDV 61850-6 IEC:2002 34 57/WG10
Process bus access point

Figure 9 - IED structure and access points
In case that short addresses can or shall be used, it is possible to define a translation of logi-
cal names to short addresses on a data attribute basis.
Note: the usage and meaning of short addresses may be defined in an SCSM (stack mapping). In this case the
system configuration tool handles them. If an SCSM does not define this, the short address related attributes may
be used by the IED tools as reference to its internal addresses. In this case the IED tool handles them. In all other
cases their contents shall be just imported and reexported by all tools.
More about short addresses is found in 9.5.2.1.
The SCL syntax to describe an IED is as follows:

<xs:element name="IED">
<xs:complexType>
<xs:sequence>
<xs:element ref="Services" minOccurs="0"/>
<xs:element ref="AccessPoint" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Manufacturer" type="xs:string"/>
<xs:attribute name="ConfigVersion" type="xs:string"/>
</xs:complexType>
</xs:element>
The attribute definition is

Nam CDATA a reference / name identifying this IED in the SAS
Manufacturer CDATA the manufacturers name
Type CDATA the (manufacturer specific) IED product type
ConfigVersion CDATA > the basic configuration version of this IED configu-
ration.
The IED ConfigVersion above only identifies the IED basic configuration (its capabilities), and
not its individual configuration after instantiation into a project. This is a parameter of the
IED, or of its logical nodes. It shall be contained in an SCL file as attribute value of the attrib-
ute LLN0.NamPlt.configRev.
The services element of the IED defines the available services.
<xs:element name="Services">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="DynAssociation"/>
<xs:element ref="GetDirectory"/>
<xs:element ref="GetDataObjectDefinition"/>
<xs:element ref="DataObjectDirectory"/>
<xs:element ref="GetDataSetValue"/>
<xs:element ref="SetDataSetValue"/>
<xs:element ref="DataSetDirectory"/>
<xs:element ref="ConfDataSet"/>
<xs:element ref="DynDataSet"/>
<xs:element ref="ReadWrite"/>
<xs:element ref="DynReportControl"/>
<xs:element ref="SetControlValue"/>
<xs:element ref="GetControlValue"/>
<xs:element ref="SGEdit"/>
<xs:element ref="GSEDir"/>

CDV 61850-6 IEC:2002 35 57/WG10
<xs:element ref="GOOSE"/>
<xs:element ref="GSSE"/>
<xs:element ref="FileHandling"/>
</xs:choice>
</xs:complexType>
</xs:element>
Appropriate services for control blocks shall be identically implemented for all kinds of control
blocks. Observe that the service definition in an ICD file can be used to describe the maxi-
mum capabilities of a device as well as wanted restrictions (e.g. for security reasons).
Service classes may appear in arbitrary order. If they do not appear, then the services are
not available at the IED. If the same service name appears several times, this is of no mean-
ing. For the meaning of the services please refer to part 7-2.
Note: setting group services belong to the setting group control block. If this control block is available, then also
the setting group service for activating a setting group is available. If editing is possible is decided with the SGEdit
element.
<xs:element name="SGEdit"> <xs:complexType/> </xs:element>
<xs:element name="DynAssociation"> <xs:complexType/> </xs:element>

all services for dynamic building of associations
<xs:element name="DynDataSet"> 

<xs:complexType>
<xs:attribute name="Max" type="xs:integer" use="required"/>
</xs:complexType>
</xs:element>
Max the maximum number of dynamically creatable data sets
<xs:element name="DynReportControl"> dynamic creation of report control blocks

<xs:complexType>
</xs:complexType>
</xs:element>
Max the maximum number of dynamically creatable report control blocks
<xs:element name="GetDirectory"> <xs:complexType/> </xs:element>

read the server , LD and LN directories (all LDs, LNs and DATA of the LNs)
<xs:element name="GetControlValue"> <xs:complexType/> </xs:element>

read control block values
<xs:element name="GetDataObjectDefinition"> <xs:complexType/> </xs:element>
<xs:element name="GetDataSetValue"> <xs:complexType/> </xs:element>
<xs:element name="DataObjectDirectory"> <xs:complexType/> </xs:element>

get the DATA defined in a LN
<xs:element name="SetControlValue"> <xs:complexType/> </xs:element>

change control block values
<xs:element name="SetDataSetValue"> <xs:complexType/> </xs:element>

CDV 61850-6 IEC:2002 36 57/WG10
<xs:element name="DataSetDirectory"> <xs:complexType/> </xs:element>
<xs:element name="GSEDir"> <xs:complexType/> </xs:element>

GSE directory services acc. 7-2
<xs:element name="GOOSE">
<xs:complexType>
<xs:attribute name="Max" type="xs:unsignedInt"/>
</xs:complexType>
</xs:element>
This element shows that the IED can be a GOOSE server and/or client acc 7-2. The Max at-
tribute defines the maximum number of GOOSE control blocks, which are configurable. Max
= 0 means the device is only a GOOSE client.
<xs:element name="GSSE">
<xs:complexType>
<xs:attribute name="Max" type="xs:unsignedInt"/>
</xs:complexType>
</xs:element>
This element shows that the IED can be a binary data GSSE server and/or client acc 7-2. The
Max attribute defines the maximum number of GSSE control blocks, which are configurable.
<xs:element name="ConfDataSet">
<xs:complexType>
<xs:attribute name="Max" type="xs:unsignedInt"
use="required"/>
<xs:attribute name="Modify" default="Yes">
<xs:simpleType>
<xs:enumeration value="Yes"/>
<xs:enumeration value="No"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
If ConfDataSet is not specified, then the value of Max is equal to the number of configured
data sets, and they may be modified. If it is specified, it is possible to configure new data sets
or modify existing ones at configuration time via SCL. The attribute meaning is as follows:
Max the maximum number of data sets possible

Modify (Yes | No) Yes Yes means that preconfigured data sets may be modified
Note: within an IED capability description the maximum numbers specified above must be a guarantied maximum,
i.e. this number must be possible to get also if some dynamic memory allocation allows sometimes to even have
more dynamic data sets at the expense of another category.
<xs:element name="ReadWrite"> <xs:complexType/> </xs:element>

basic data read and write facility; includes GetData, SetData, and the Oper-
ate service, if appropriate data objects exist.
<xs:element name="FileHandling"> <xs:complexType/> </xs:element>

all file handling services
<xs:element name="AccessPoint">
<xs:complexType>
<xs:sequence>
<xs:element ref="Router" minOccurs="0"/>
<xs:element ref="Clock" minOccurs="0"/>

CDV 61850-6 IEC:2002 37 57/WG10
<xs:choice minOccurs="0">
<xs:element ref="Server"/>
<xs:element ref="LN" maxOccurs="unbounded"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="Nam" type="xs:normalizedString"
use="required"/>
</xs:complexType>
</xs:element>
a communication access point of the IED.
The Nam attribute is a reference identifying this IED access point within the IED. Together with the
Nam of the IED this gives a unique reference for the access point within the SA system.
If neither a router, nor a clock, nor a server, nor a LN list is specified, the access point may
only be used by client LNs in the same IED to access the bus to which it is connected. This is
typical for a bay level device with a process bus access point, where the LNs offer their data
via a server to the station bus only.
Project specific access point attributes like the address within a communication system are
contained in the SCL Communication section.
<xs:element name="Router"> <xs:complexType/> </xs:element>

the presence defines this IED to have a router function.
<xs:element name="Clock"> <xs:complexType/> </xs:element>
the presence defines this IED to be a master clock at this bus
Note that
an IED can be a router or a clock only, if it does not contain any other element (especially
server),
a router or clock function may exist additionally on a server access point,
the IED contains only the server this is the normal case.
The IED contains only a LN list these are clients only and can not be supervised, be-
cause no server offers the appropriate data. An additional router or clock function is pos-
sible.
9.3.1 The IED server
<xs:element name="Server">
<xs:complexType>
<xs:sequence>
<xs:element ref="Authentication" minOccurs="0"/>
<xs:element ref="LDevice" maxOccurs="unbounded"/>
<xs:element ref="Association" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="Private" minOccurs="0" maxOc-
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Timout" type="xs:unsignedInt" de-
fault="30"/>
</xs:complexType>
</xs:element>
a communication server of the IED.
The Timeout attribute contains a time out in seconds: if a started transaction (e.g. selection
of a setting group) is not completed within this time, it is cancelled and reset.
The server is identified within the system by the access point to which it belongs. Its commu-
nication wise identification (address) is contained in the SCL communication section.

CDV 61850-6 IEC:2002 38 57/WG10
<xs:element name="Authentication">
<xs:complexType>
<xs:element ref="none"/>
<xs:element ref="password"/>
<xs:element ref="weak"/>
<xs:element ref="strong"/>
<xs:element ref="certificate"/>
</xs:choice>
</xs:complexType>
</xs:element>
The Authentication element defines in case of a device description the authentication possi-
bilities, in case of a device instantiated in a plant the method(s) to be used for authentication.
If the element is missing, this means none (i.e. no authentication). The exact meaning of the
other methods, especially weak and strong, is defined in the stack mappings (SCSMs).
9.3.2 The logical device
The LDevice element defines a logical device of the IED reachable via the access point. It
shall contain at least one LN and the LN0, and may contain pre - configured report, GSE and
SMV definitions.
<xs:element name="LDevice">
<xs:complexType>
<xs:sequence>
<xs:element ref="LN0"/>
<xs:element ref="LN" minOccurs="1" maxOc-
curs="unbounded"/>
<xs:element ref="AccessControl" minOccurs="0"/>
curs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
The attributes have the following meaning:
Inst The identification of the LDevice within the IED; may be an empty string if
only one LDevice exists. The full LD reference according to part 7 contains
an additional part before this Ref (see also chapter 8.5)
Desc optional describing text for the logical device.
9.3.3 LN0 and Data sets

<xs:element name="LN0">
<xs:complexType>
<xs:sequence>
<xs:element ref="DataSet" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="ReportControl" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="LogControl" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="GSEControl" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="SampledValueControl" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="SettingControl" minOccurs="0"/>

CDV 61850-6 IEC:2002 39 57/WG10
<xs:element ref="DO" minOccurs="0" maxOccurs="unbounded"/>

<xs:element ref="Inputs" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="LNType" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
The LN0 attributes have the following meaning:
LNType the instantiable type definition of this logical node, reference to a LNodeType
definition.
The LN0 LNName is always LLN0, so no Inst attribute is needed. For referencing links to LN0, LNInst
shall be the empty string, and LNClass shall be LLN0.
<xs:element name="LN">
<xs:complexType>
<xs:sequence>
<xs:element ref="DataSet" minOccurs="0" maxOc-
curs="unbounded"/>
curs="unbounded"/>
curs="unbounded"/>
<xs:element ref="DO" minOccurs="0" maxOccurs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Inst" type="xs:unsignedInt"/>
<xs:attribute name="LNType" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
The LN attributes have the following meaning:
Inst the LN instance id identifying this LN an unsigned integer.

LNClass the LN class according to part 7 of this standard.
Prefix the LN prefix part
LNType the instantiable type definition of this logical node, reference to a LNodeType
element.
The optional DO elements in a LN definition can be used to define special instance related
values for data objects and their attributes by means of DAI elements per attribute (see DO
definition in 9.5). The DOs referenced here shall however already be defined within the LNo-
deType definition of the LN, referenced with the LNType attribute. The DO elements at this
place for this instance shall NOT define a new DO, which is not contained in the LNodeType.
Example: the pulse length configuration parameter of a DPC CDC, specified with 100 ms in
the LNodeType, is overwritten here with a value of 300 ms for this special DO.
The detailled syntax of the DO element is described in the LNodeType section in 9.5. Only
the DAI variant shall be allowed within an IED, not the variant containing the DA element.
9.3.4 Data set definition

<xs:element name="DataSet">
<xs:complexType>
<xs:sequence>

CDV 61850-6 IEC:2002 40 57/WG10
<xs:element ref="FCDA" maxOccurs="unbounded"/>

</xs:sequence>
</xs:complexType>
</xs:element>
This data set definition of the LN has the following attributes
Nam a name identifying this data set in the LN where it is defined.

Desc an informative text to the data set
<xs:element name="FCDA">
<xs:complexType>
<xs:attribute name="LDInst" type="xs:string" default="" />
<xs:attribute name="Prefix" type="xs:string" default="" />
<xs:attribute name="LNClass" type="xs:NMTOKEN" default="" />
<xs:attribute name="LNInst" type="xs:string" default="" />
<xs:attribute name="DONam" type="xs:string" default="" />
<xs:attribute name="Attr" type="xs:string" default="" />
<xs:attribute name="FC" type="xs:string" default="" />
</xs:complexType>
</xs:element>
The FCDA element defines the name of a functionally constraint data or functionally con-
straint data attribute according to part 7-2 of this IED / LD to be contained in the data set.
The order of the names in the data set is important for the communication messages. The
element has the following attributes:
LDInst the LD where the DO resides; empty means this LD

Prefix Prefix identifying together with LNInst the LN where the DO resides
LNInst Instance Id of the LN where the DO resides
LNClass LN class of the LN where the DO resides
DONam a name identifying the DO (within the LN). A name standardized in part 7. If
DONam is empty, then FC can contain a value, selecting the attribute category of
all DOs of the defined LN.
Attr the attribute if empty (and FC empty) all attributes with characteristic Process
value (ST, MX, SV) are selected.
FC all attributes of this functional constraint are selected. Possible constraint values
see part 7-2 resp. the FC definition in 9.5.
Note: IF Attr and FC both contain a non empty value, then the FC value must be valid for the attribute, else the
SCL file processing shall be stopped. If all attributes of the FCDA are empty, then this corresponds to an empty
string in a GSSE DataLabel definition in all other data sets this is not allowed.
Note: all control blocks, which reference a data set, shall be contained in the same LN as the data set definition.
Therefore the data set reference within all control blocks only contains the LN relative data set name (Nam attrib-
ute at DataSet element above), and not its full name (which should in general also contain the LDInst and LNName
according to part 7-2).
9.3.5 Report Control block
A report control block definition of the LN looks as follows:
<xs:element name="ReportControl">
<xs:complexType>
<xs:sequence>
<xs:element ref="TrgOpEna" minOccurs="0"/>
<xs:element ref="OptFlds" minOccurs="0"/>
<xs:element ref="RptEnabled" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="RCName" type="xs:string" use="required"/>
<xs:attribute name="RptID" type="xs:string" use="required"/>

CDV 61850-6 IEC:2002 41 57/WG10
<xs:attribute name="DatSet" type="xs:string" use="required"/>

<xs:attribute name="ConfRev" type="xs:unsignedInt"
use="required"/>
<xs:attribute name="Buffered" type="xs:boolean" de-
fault="FALSE"/>
<xs:attribute name="BufTim" type="xs:unsignedInt" de-
fault="0"/>
<xs:attribute name="IntgPd" type="xs:unsignedInt" de-
fault="0"/>
</xs:complexType>
</xs:element>
The following attributes are used:
RCName a reference identifying this report control block (part of URCName resp. BRCName
in part 7-2)
DataSet the name (Nam) of the data set to be sent by the report control block
Buffered specifies if reports are buffered or not see part 7-2.
BufTim buffer time see part 7-2
IntgPd integrity period in milliseconds see part 7-2
<xs:element name="TrgOpEna">
<xs:complexType>
<xs:choice maxOccurs="4">
<xs:element ref="dchg"/>
<xs:element ref="qchg"/>
<xs:element ref="dupd"/>
<xs:element ref="period"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="OptFlds">
<xs:complexType>
<xs:element ref="SeqNum"/>
<xs:element ref="TimeStamp"/>
<xs:element ref="DatSet"/>
<xs:element ref="ReasonCode"/>
<xs:element ref="BufOvfl"/>
<xs:element ref="DataRef"/>
<xs:element ref="EntryId"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="RptEnabled">
<xs:complexType>
<xs:sequence>
<xs:element ref="ClientLN" minOccurs="0" maxOc-
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Max" type="xs:unsignedInt" default="1"/>
</xs:complexType>
</xs:element>
The RptEnabled element contains the list of client LNs for which this report is enabled (e.g. at
IED startup on pre-established associations).
The attribute Max defines the maximum number of report control blocks of this type, which
are instantiated at configuration time in the LN (and then used online). According to part 7-2
only one client can use a report control block at a time. This means that if Max>1 is given
here, more than one report control block (RCB) of this type has to be instantiated in the IED.

CDV 61850-6 IEC:2002 42 57/WG10
Observe that for all buffered control blocks a ClientLN must be preconfigured, i.e. Max is
identical to the number of ClientLNs given. If ClientLNs are preconfigured for unbuffered
RCBs, then the Resv attribute of the RCB shall be set to true additionally to the RptEna at-
tribute in the IED. The URCName or BRCName of the control block according to part 7-2
consists of the RCName attribute above followed by a number between 1 and Max. If Cli-
entLNs are defined, the index (position) of the ClientLN in the list contained in the
RptEnabled element is used as this number for this client (the first has index 1). This means
that a report control block definition in SCL has to be considered as a type, and not as an in-
stance.
The ClientLN element defines the name of a LN in the system, which is a client to this report
CB type.
<xs:element name="ClientLN">
<xs:complexType>
<xs:attribute name="IEDNam" type="xs:string" use="required"/>
<xs:attribute name="LDInst" type="xs:string" use="required"/>
<xs:attribute name="LNInst" type="xs:string"/>
<xs:attribute name="LNClass" type="xs:NMTOKEN"
use="required"/>
</xs:complexType>
</xs:element>
It has the following attributes:
IEDNam the name of the IED where the LN resides

LDInst the instance identification of the LD where the LN resides
Prefix the LN prefix
LNInst the instance id of this LN instance of below LN class in the IED.
LNClass the LN class according to part 7 of this standard
Note that to identify a LN within the system here the IED based designation is used, even if
the communication name generation will be based on the substation functional structure. It is
recommended that a tool assures that the defined client is really accessible across the de-
fined communication system.
For pre-established associations the AssociationId corresponding to the referenced LN can

be found in the Association definition section of this IED.
9.3.6 Log Control block
A log control block is defined with the following element:
<xs:element name="LogControl">
<xs:complexType>
<xs:sequence>
<xs:element ref="TrgOpts" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="LCBName" type="xs:string"
use="required"/>
<xs:attribute name="LogRef" type="xs:string" use="required"/>
fault="0"/>
</xs:complexType>
</xs:element>
The meaning of the attributes is mostly identical to the appropriate control block attributes
defined in 7-2.

CDV 61850-6 IEC:2002 43 57/WG10
LCBName the name of this log control block within this LN (LCBName in 7-2)
LogRef the LDInst of the LD within this server which contains the log.
IntgPd the integrity scan period (cycle time) in milliseconds
DatSet the name of the data set whose values shall be logged
9.3.7 GSE control block
The following GSE control element is only allowed in the logical node LLN0.
<xs:element name="GSEControl">
<xs:complexType>
<xs:sequence>
<xs:element ref="IEDNam" minOccurs="0" maxOc-
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="GCName" type="xs:string" use="required"/>
<xs:attribute name="ConfRev" type="xs:unsignedInt"/>
<xs:attribute name="Type" default="GOOSE">
<xs:simpleType>
<xs:enumeration value="GSSE"/>
<xs:enumeration value="GOOSE"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="AppId" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>

GCName a reference identifying this GOOSE control block
Type If format is GSSE, then only single indication and double indication data types are
allowed for the data items referenced in the data set, else all data types are al-
lowed. Note that on stack level each type might be mapped differently to mes-
sage formats.
ConfRev the configuration revision number of this control block
AppId an identification of the application sending the GOOSE message in the system
DatSet the name of the data set to be sent by the GSE control block. For Type=GSSE
the FCDA definitions in this data set shall be interpreted as DataLabels according
to 7-2.
<xs:element name="IEDName" type="xs:string"/> the name of an IED in the system, to

which GSE or SAMPLE data shall be sent
9.3.8 Sampled Value Control block
The following Sampled Value control block element is only allowed in the logical node LLN0.
<xs:element name="SampledValueControl">
<xs:complexType>
<xs:sequence>
<xs:element ref="SmvOpts" minOccurs="0"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="SVCNam" type="xs:string" use="required"/>
<xs:attribute name="ConfRev" type="xs:unsignedInt"/>
<xs:attribute name="SmvId" type="xs:string" use="required"/>
<xs:attribute name="Multicast" type="xs:boolean" default="TRUE"/>

CDV 61850-6 IEC:2002 44 57/WG10

<xs:attribute name="SmpRate" type="xs:unsignedInt"
use="required"/>
</xs:complexType>
</xs:element>
The attributes mean the following:

SVCNam the name of the sampled value control block within this LN
Multicast FALSE indicates Unicast SMV servces only
ConfRev the configuration revision number of this control block
SmvId the communication level Id MsvID for the Sampled value definition for a multicast
CB, the value buffer identification UsvID for a unicast CB.
DatSet the name of the data set whose values shall be sent
SmpRate sample rate as defined in 7-2
If Multicast is FALSE, i.e. this is a Unicast control block, then for each IEDName a control
block instance shall be created, UsvCBNam shall be set to this IEDNam concatenated with
SVCNam above (which might then be empty), and the Resv attribute of the CB initialized to
TRUE. In this case the definition has to be considered a type.
If Multicast is TRUE, then MsvCBNam is set to SVCNam.
The following options can be set:
<xs:element name="SmvOpts">
<xs:complexType>
<xs:element ref="refreshtime"/>
<xs:element ref="samplesynchronised"/>
<xs:element ref="samplerate"/>
</xs:choice>
</xs:complexType>
</xs:element>
The meaning of the options is described in 7-2.
9.3.9 Setting Control Block
The following defines the definition for a setting control block. Note that the SGC name, i.e.
its relative name within the LN0, is SGCB according to 7-2.
<xs:element name="SettingControl">
<xs:complexType>
<xs:sequence>
</xs:sequence>
<xs:attribute name="NumOfSGs" type="xs:unsignedInt"
use="required"/>
<xs:attribute name="ActSG" type="xs:unsignedInt" de-
fault="1"/>
</xs:complexType>
</xs:element>
The attributes are identical to those of the Setting group control block in 7-2.
NumOfSGs the number of setting groups available.

ActSG the number of the setting group to be activated when loading the configu-
ration.

CDV 61850-6 IEC:2002 45 57/WG10
9.3.10 Binding to external signals
The Inputs section defines all external signals, which are needed by the LN logic to fulfill its
function. The section also allows binding the signal to an internal address IntAdr.
<xs:element name="Inputs">
<xs:complexType>
<xs:sequence>
<xs:element ref="ExtRef" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
Each ExtRef element references one external item, either at DO or DA level. If IntAdr is
needed, it has to be used appropriately.
<xs:element name="ExtRef">
<xs:complexType>
use="required"/>
<xs:attribute name="LNInst" type="xs:string" use="required"/>
<xs:attribute name="DONam" type="xs:string" use="required"/>
<xs:attribute name="Attr" type="xs:string"/>
<xs:attribute name="IntAdr" type="xs:string"/>
</xs:complexType>
</xs:element>
IEDNam the name of the IED where the input comes from
LDInst the LD instance name where the input comes from
Prefix the LN prefix
LNClass etc. identification of input item at source
LNInst
DONam
Attr the attribute designating the input. The IED tool should use an empty
value if it has some default binding (IntAdr) for all process input attributes
of a DO inclusive t and q.
IntAdr the internal address to which the input is bound. Only the IED tool shall
use the value. All other tools shall preserve it.
An empty Attr value means the operational value attribute(s) of the DO, i.e. stVal, mVal, etc.
In this case also IntAdr can specify the addresses of all operational attributes in some IED
tool specific way.
If the same data input can be received by the by on different communication services (e.g. by
report and by GOOSE), it is up to the IED or its tool implementation to decide which one shall
be taken.
9.3.11 Associations
<xs:element name="AccessControl"> <xs:complexType mixed="true"/> </xs:element>
an access control definition. Meaning and eventual refinement of the defini-
tion are stack specific issues.

CDV 61850-6 IEC:2002 46 57/WG10
It is recommended that all authorization and access control is done by private implementation
within the interface LNs. In this case no access control definitions are necessary within SCL.
Each association definition defines one pre-configured association between this server and a
client logical node. Two kinds of pre-configuration are possible. Predefined means that this
association is defined, but not yet opened, the client has to open it. Pre-established means,
that the association is defined and considered to be open directly after IED start up.
<xs:element name="Association">
<xs:complexType>
<xs:attribute name="Kind" use="required">
<xs:simpleType>
<xs:enumeration value="pre-established"/>
<xs:enumeration value="predefined"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="AssociationId" type="xs:string"/>
<xs:attribute name="LNInst" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
The attributes mean the following:

Kind the kind of pre-configured association, pre-established or predefined
IEDNam a reference identifying the IED on which the client resides
LDInst the reference to the client logical device
LNClass the Class of the client LN
Prefix
LNInst the reference number of the client LN
AssociationId the Id of a pre-configured association (else empty)
An empty association Id as given by the default value means that the association Id is not yet defined.
For a completed SCL file and a pre-established association the association Id shall be filled, so that
the client LNs and the server can verify it correctly. The same client may use the same association to
different LNs on the same server. Uniqueness requirements as well as value range of the association
Id (e.g. a 32 bit integer, unique at the server, or at server IED and client Id, or system wide) are set up
in the SCSMs.
9.4 Communication system description
This clause describes the direct communication connection possibilities between logical
nodes by means of logical buses and IED access points. The IED sections already describe
which LDs and LNs are reachable across a certain access point. The communication section
now describes which IED access points are connected to a common bus. This is done in a
way that reflects the hierarchical name structure within the IED, which is based on IED rela-
tive names for access points, LDs and LNs.
<xs:element name="Communication">
<xs:complexType>
<xs:sequence>
<xs:element ref="Subnetwork" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>

CDV 61850-6 IEC:2002 47 57/WG10
</xs:element>
<xs:element name="Subnetwork">
<xs:complexType>
<xs:sequence>
<xs:element ref="ConnectedAP" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="Bitrate" type="xs:decimal"/>
</xs:complexType>
</xs:element>
The Text part can be used for free text.
The attributes are defined as follows:
Ref a reference identifying this bus
Bitrate the bit rate used on this subnetwork in MB/s (Megabit per second)
Type the bus protocol type
Protocol types are defined in parts 8 and 9. Those of part 8 start with 8-, those of part 9
with 9- (except if they are identical; in this case part 9 defines the part 8 type to be used).
<xs:element name="ConnectedAP">
<xs:complexType>
<xs:sequence>
<xs:element ref="Address"/>
<xs:element ref="GSE" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="SMV" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="PhysConn" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
The ConnectedAP is the IED access point connected to the bus.
IEDNam a reference identifying the IED

Nam a reference identifying this access point within the IED
<xs:element name="Address">
<xs:complexType>
<xs:sequence>
<xs:element ref="P" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
The Address element defines the address parameters of this access point at this bus. The
different parameters are defined within the contained P elements. The Type attribute if P
identifies the meaning of the value. The meaning of the P parts is depending on the subnet-
work protocol type and therefore specified in the appropriate SCSM. The Access point ad-
dress shall be filled with a unique value at least for server type access points to get a com-
plete SCD description.
<xs:element name="P">

CDV 61850-6 IEC:2002 48 57/WG10
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="Type" type="xs:string" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
The GSE element defines the address for a GSE control block in this IED. It must be at LLN0.
<xs:element name="GSE">
<xs:complexType>
<xs:attribute name="Addr" type="xs:string"/>
<xs:attribute name="CBNam" type="xs:string"/>
<xs:attribute name="Mintime" type="xs: unsignedInt"/>
<xs:attribute name="Maxtime" type="xs: unsignedInt"/>
</xs:complexType>
</xs:element>
LDInst the LD to which the control block belongs
CBNam the identification of the control block within the LD (always in LLN0)
Addr the GOOSE multicast destination address. The format is determined by the
SCSM.
Mintime the maximum allowed sending delay on a data change in ms.
Maxtime the source supervision repetition time in ms (supervision heart beat cycle)
Mintime and Maxtime may influence SCSM parameters. Which and how is defined in the ap-
propriate SCSM.
The SMV element defines the address for a sampled value control block
<xs:element name="SMV">
<xs:complexType>
</xs:complexType>
</xs:element>
The attributes are defined as follows:

LDInst the LD to which the control block belongs
CBNam the identification of the control block within the LD (in LLN0)
Addr the SMV multicast destination address
The element PhysConn defines the type(s) of physical connection for this access point. The parame-
ter values are depending on the type of the physical connection, and their types (meaning) have to be
defined in the stack mapping.
<xs:element name="PhysConn">
<xs:complexType>
<xs:sequence>
</xs:sequence>

CDV 61850-6 IEC:2002 49 57/WG10
</xs:complexType>
</xs:element>
The Type attribute specifies the type of physical connection of this access point to the bus, while the
value then specifies the instance of this type (e.g. Type=Plug, value is BFOC. Allowed types and
values shall be defined in the stack mapping. The P element can be repeated if one value is not suffi-
cient.
The following SCL part shows a communication section with one subnetwork XW1, to which
two IEDs are connected with their access points S1. The Addresses are partly left empty, i.e.
the description is not complete. The PhysConn and address types are just examples.
<Communication>
<Subnetwork Ref="XW1" Type="8-MMS">Station bus
<ConnectedAP IEDNam="E1Q1KA1" Nam="S1">
<Address><P Type="IP">10.0.0.12</P></Address>
</ConnectedAP>
<ConnectedAP IEDNam="E1Q2KA1" Nam="S1">
<Address></Address>
<PhysConn Type="Cable">10BaseT</PhysConn>
<PhysConn Type="Plug">RJ45</PhysConn>
</ConnectedAP>
</Subnetwork>
</Communication>
9.5 LNodeType definitions
This clause defines instantiable logical node types. A logical node type is an instantiable
template of the data of a logical node. It is referenced each time that this instantiable type is
needed within an IED. The LN type names (Ref attribute) together with the IEDType attribute
of the LN type shall be unique within each SCL file. Therefore on generation of the system
SCD file from IED ICD files the names may change to keep uniqueness across all IED defini-
tions. To keep possible semantic information of the type names, it is recommended to use the
IEDType attribute to define the relation of a specific LN type to an IED type. If this is not suf-
ficient, generate a new LN type name by concatenating the IED name (which must be unique
within the file) with the old type name (which must be unique at least per IED). If a LN type
shall be generally valid for several IEDs, then the IEDType attribute shall be defined as
empty string.
The LN type (LNodeType element) contains a list of Data, its attributes, and possible default
values for configuration parameters.
<xs:element name="LNodeType">
<xs:complexType>
<xs:sequence>
<xs:element ref="DO" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="IEDType" type="xs:string"/>
</xs:complexType>
</xs:element>

Ref a reference identifying this LN type within this SCL section; used by the LN attrib-
ute LNType to reference this definition
IEDType the manufacturer IED type to which this LN type belongs.
Desc an additional text describing this LN type

CDV 61850-6 IEC:2002 50 57/WG10
LNClass the LN base class of this type
9.5.1 DATA (DO) definition

<xs:element name="DO">
<xs:complexType>
<xs:sequence>
<xs:choice>
<xs:sequence>
<xs:element ref="CtlService" minOccurs="0"/>
<xs:element ref="Transient" minOccurs="0"/>
<xs:element ref="DA" minOccurs="1" maxOc-
curs="unbounded"/>
</xs:sequence>
<xs:element ref="DAI" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="CDC" type="xs:string" use="required"/>
<xs:attribute name="AccessControl" type="xs:string"/>
</xs:complexType>
</xs:element>
The DO attributes are used as follows:
Nam a standardised DO name e.g. from part 7-4.

CDC the standard type (Common Data Class, CDC) of the data object e.g. as
defined in part 7-3.
AccessControl access control definition for this DO. The empty string (default) means
that the higher-level access control definition applies.
The CtlService only needs to be defined for controllable data objects. Its options correspond
to the ctlModel attribute of the controllable DOs.
<xs:element name="CtlService">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="3">
<xs:element ref="SBO"/>
<xs:element ref="Timed"/>
<xs:element ref="Enhanced"/>
</xs:choice>
</xs:complexType>
</xs:element>
The contained elements mean the following:

SBO allows select before operate
Timed allows timer related service
Enhanced specifies enhanced security mode
Note that several control options (e.g. SBO and Enhanced) may be specified in the LNode-
Type, corresponding to all supported control service classes. If none is specified, only direct
control, or even only status read is possible, depending on the data attributes available. If
only SBO is specified, this means SBO control with normal security, i.e. services Select and
Oper. If SBO and Enhanced is specified, this means SBO control with enhanced security, i.e.
services Select with Value, Oper, Command termination.
The existence of the Transient element indicates that this is transient data as defined for the
appropriate DATA / DO definition. The Transient element itself is empty.

CDV 61850-6 IEC:2002 51 57/WG10
<xs:element name="Transient" />

There are two variants of defining attributes within a DO.
Based on the DA element: this shall be used within a LnodeType definition. Each instan-
tiable atribute except the mandatory attributes t (TimeStamp) and q (Quality) shall be de-
fined in the LnodeType definition with this variant.
Based on the DAI element: this shall be used within an IED definition. It allows to define
IED instance specific attribute values, or override type (typical) values with instance spe-
cific ones. The DAI element can also be mising completely, if nothing instance specific
has to be set.
9.5.2 Data Attribute definition
Each data object has attributes related to it. The DA element defines the attributes and de-
scribes its (default) values. The DAI allows describing instance values for an IED. This can
be used at engineering time by other IEDs / LNs which need to know configuration related
values, e.g. if they have no services to read the values, or the IED does not support their
reading. Alternatively it can be used by the IED itself to set these values, either to offer them
via the communication protocol, or at least consider them in its internal functions.
The DA / DAI element contains just a basic value, i.e. no structure values can be given. In
case of an attribute with a structure like ScaledValueConfig, for each element of the structure
a DA element shall be used. Its Nam attribute then contains the concatenation of attribute
name and its subelement names, separated by a period. Thus the scale factor of a scaled
value configuration is addressed by a name of ScaledValueConfig.iScaleFactor. This means
that all values only have a simple data type.
Part 7 defines the value type for a certain attribute based on the CDC of the DO. The value
coding then has to follow the XML Schema data type definition. The type mapping is as fol-
lows.
Part 7 base type XML Schema (xs) data Value representation
type
INT8, INT16, INT32, integer An integer number , no decimal
INT8U, INT16U, INT32U fraction (99999)
FLOAT32, FLOAT32 decimal A number with or without a decimal

fraction (999.99999).
BOOLEAN boolean false, true or 0, 1
ENUMERATED normalizedString The enumeration element names
as defined in part 7 as string val-
ues.
Octet string Base64Binary Coding according clause 6.8 of
RFC 2045
VisibleString normalizedString A character string without tabs,
linefeeds and carriage return
Table 2 Data type mapping
The meaning of the value for an IED configuration tool can be different depending on the de-
vice capabilities, the functional characteristic of the attribute, and the stage of the engineer-
ing process. The DA attribute Valkind allows specifying this meaning. It is ignored, if no value
is given, and for all cases not specified below (e.g. for the q and t attributes). The following
table explains how it shall be interpreted.
Valkind value Functional con- Engineering process Meaning
straints stage
Spec Non operational (CF, Specification phase The wanted value de-
DC) termined at specification

CDV 61850-6 IEC:2002 52 57/WG10
phase typically in an
SCD file
Conf CF, DC, operational IED template, after This value is not avail-
attribute of a CDC IED engineering able at the IED. The IED
used for settings is engineered such that
this value is used.
RO Operational process IED template The default value for the
state attribute attribute to be used if
q.source is set to de-
faulted not changeable
RO CF, DC, operational IED template, after Read only value at an
attribute of data used IED configuration IED can only be set at
for settings configuration time
Set CF, DC At / after IED configu- A determined setting
ration value. The value is /
shall be set within the
IED.
Set Operational process At / after IED configu- The default value for the
values (except time ration (possibly RO operational attribute, to
and quality) changed to Set) be used if q.source is set
to defaulted
Set Operational setting At / after IED configu- The setting value for the
value (SP, SG for all ration set point
data used as setting)
Table 3 Attribute value kind meaning
This allows e.g. defining IED capabilities (which attributes are available, which are read only),
the default values an IED is delivered with (readable, changeable, or not visible at all), or the
setting values for operative (e.g. protection) parameters.
<xs:element name="DA">
<xs:complexType>
<xs:sequence>
<xs:element ref="Enum" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="Val" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="SAdr" type="xs:string"/>
<xs:attribute name="FC" use="required">
<xs:simpleType>
<xs:enumeration value="ST"/>
<xs:enumeration value="MX"/>
<xs:enumeration value="CO"/>
<xs:enumeration value="SP"/>
<xs:enumeration value="SG"/>
<xs:enumeration value="SE"/>
<xs:enumeration value="SV"/>
<xs:enumeration value="AX"/>
<xs:enumeration value="CF"/>
<xs:enumeration value="DC"/>
<xs:enumeration value="EX"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="TrgOpt" default="none">
<xs:simpleType>

CDV 61850-6 IEC:2002 53 57/WG10
<xs:enumeration value="dchg"/>
<xs:enumeration value="qchg"/>
<xs:enumeration value="dupd"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="BType" use="required">
<xs:simpleType>
<xs:enumeration value="BOOL"/>
<xs:enumeration value="INT8"/>
<xs:enumeration value="INT8U"/>
<xs:enumeration value="FLOAT32"/>
<xs:enumeration value="Enum"/>
<xs:enumeration value="CodedEnum"/>
<xs:enumeration value="VisString32"/>
<xs:enumeration value="Octet64"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="Valkind" default="Set">
<xs:simpleType>
<xs:enumeration value="Spec"/>
<xs:enumeration value="Conf"/>
<xs:enumeration value="RO"/>
<xs:enumeration value="Set"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
The DA element shall be used within the LNodeType definition.

The DAI element contains a subset of the DA attributes, and shall be used within an IED DO
specification in case that some instance specific attribute values shall be set or typical attrib-
ute values overwritten.
<xs:element name="DAI">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element ref="Val"/>
</xs:sequence>
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>

CDV 61850-6 IEC:2002 54 57/WG10

</xs:complexType>
</xs:element>
The meaning of the attributes is as follows:

SAdr an optional short address of this DO attribute
FC specification of the functional characteristic as defined in e.g. 7-3
TrgOpt the (report or log) trigger option used for this attribute
BType the basic data type of this attribute at application level (acc. 7-2)
Valkind the meaning of the value from the engineering phases, if any value is given
Nam the name of the DA attribute whose value is given
Within a LNodeType only the DA variant of the attribute specification is allowed, not the DAI variant.
FC, TrgOpt and BType shall be defined. All instantiable attributes contained within a DO shall be de-
fined.
A special BType is the enumeration (Enum and CodedEnum). In this case also the enumeration val-
ues have to be defined by means of the Enum element.
<xs:element name="Enum">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="Ord" type="xs:unsignedInt"
use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
The Ord attribute contains the order of the values, starting from 0.
The following example defines the stVal attribute of a DPC CDC without value, according to 7-3:
<DA Nam=stVal FC=ST TrgOpt=dchg BType=Enum>
<Enum Ord=0>intermediate-state</Enum>
<Enum Ord=1>off</Enum>
<Enum Ord=2>on</Enum>
<Enum Ord=3>bad-state</Enum>
</DA>
An IED tool shall fill in the value of the functional characteristic FC when exporting an IED description.
For standardised common data class attributes it is defined in part 7-3.
9.5.2.1 Short addresses
The SAdr attribute allows allocating a short address to DO attributes. Short addresses can be
used within the communication to be more efficient either in the communication, or in the
handling of messages at client or server. Further they can be used as IED internal identifica-
tion for the attribute. To be able to use short addresses in the communication,
the stack mapping must allow them and define their meaning,
and the IED must allow them.
The detailed syntax of a short address depends on the stack if the stack defines their usage,
else on the IED tool. SCL foresees a two level hierarchy for short addresses used in commu-
nication:
The communication address of the IED / server / access point
The short address of a data item at attribute level
It is possible to use the short address instead of the (symbolic) IED communication address in case
that the short address is unique system wide, and the stack allows this. Otherwise the short address
scope is private to the IED.

CDV 61850-6 IEC:2002 55 57/WG10
9.5.2.2 Values
The value definition contains a possible value. For attributes with FC = SG the SGroup attribute speci-
fies to which setting group this value belongs. There may be a value for each setting group defined.
The meaning of the value in the engineering process is defined at the DA / DAI level by means of the
Valkind attribute.
<xs:element name="Val">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="SGroup" type="xs:integer"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
SGroup the number of the setting group (if FC is SG) to which this value belongs
The SGroup value used within an IED should be checked against an existing setting group
definition on this IED, where the maximum allowed number is specified (SettingCon-
trol.NumOfSGs). If the SGroup is left empty, then either this attribute is in no setting group
(FC # SG), or the data value (if any) applies to all setting groups.
9.5.2.3 Enumeration types
Enumerations are in general used in more than one LNodeType. Therefore for them an enu-
meration type definition is made.
<xs:element name="Enumtype">
<xs:complexType>
<xs:sequence>
<xs:element ref="Enum" minOccurs="2"/>
</xs:sequence>
</xs:complexType>
</xs:element>
The Ref attribute is the SCL file unique identification of the enumeration type. It is referenced by a DA
definition, in case the basic data type BType is an Enum or codedEnum.
If extensions to an enumeration are made, this shall be considered as a new Enumtype.

CDV 61850-6 IEC:2002 56 57/WG10
Annex A
(normative)
SCL syntax XML Schema Definition
<?xml version="1.0" encoding="UTF-8"?>


<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDe-
fault="qualified">
<xs:element name="AccessControl">
<xs:complexType mixed="true"/>
</xs:element>
<xs:element name="AccessPoint">
<xs:complexType>
<xs:sequence>
<xs:element ref="Router" minOccurs="0"/>
<xs:element ref="Clock" minOccurs="0"/>
<xs:choice minOccurs="0">
<xs:element ref="Server"/>
<xs:element ref="LN" maxOccurs="unbounded"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="Nam" type="xs:normalizedString"
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="Address">
<xs:complexType>
<xs:sequence>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Association">
<xs:complexType>
<xs:attribute name="Kind" use="required">
<xs:simpleType>
<xs:enumeration value="pre-established"/>
<xs:enumeration value="predefined"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="AssociationId" type="xs:string"/>
<xs:attribute name="IEDNam" type="xs:string"
use="required"/>
<xs:attribute name="LDInst" type="xs:string"
use="required"/>
<xs:attribute name="LNInst" type="xs:string"
use="required"/>
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="Authentication">
<xs:complexType>

CDV 61850-6 IEC:2002 57 57/WG10
<xs:element ref="none"/>
<xs:element ref="password"/>
<xs:element ref="weak"/>
<xs:element ref="strong"/>
<xs:element ref="certificate"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="Bay">
<xs:complexType>
<xs:sequence>
<xs:element ref="LNode" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="ConNode" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="Device" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="Private" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="BufOvfl">
<xs:complexType/>
</xs:element>
<xs:element name="ClientLN">
<xs:complexType>
use="required"/>
use="required"/>
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="Clock">
<xs:complexType/>
</xs:element>
<xs:element name="Communication">
<xs:complexType>
<xs:sequence>
<xs:element ref="Subnetwork" maxOccurs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ConNode">
<xs:complexType>
<xs:sequence>
curs="unbounded"/>
curs="unbounded"/>
</xs:sequence>

CDV 61850-6 IEC:2002 58 57/WG10
</xs:complexType>
</xs:element>
<xs:element name="ConfDataSet">
<xs:complexType>
use="required"/>
<xs:attribute name="Modify" default="Yes">
<xs:simpleType>
<xs:enumeration value="Yes"/>
<xs:enumeration value="No"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="ConnectedAP">
<xs:complexType>
<xs:sequence>
<xs:element ref="Address"/>
<xs:element ref="GSE" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="SMV" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="PhysConn" minOccurs="0" maxOc-
curs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="Connection">
<xs:complexType>
<xs:attribute name="CNodeNam" type="xs:string"
use="required"/>
<xs:attribute name="Terminal" type="xs:string"/>
<xs:attribute name="BayNam" type="xs:string"/>
<xs:attribute name="VLNam" type="xs:string"/>
<xs:attribute name="SSNam" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="CtlService">
<xs:complexType>
<xs:element ref="SBO"/>
<xs:element ref="Timed"/>
<xs:element ref="Enhanced"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="DA">
<xs:complexType>
<xs:sequence>
<xs:element ref="Val" minOccurs="0" maxOc-
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="FC" use="required">
<xs:simpleType>

CDV 61850-6 IEC:2002 59 57/WG10
<xs:enumeration value="ST"/>
<xs:enumeration value="MX"/>
<xs:enumeration value="CO"/>
<xs:enumeration value="SP"/>
<xs:enumeration value="SG"/>
<xs:enumeration value="SE"/>
<xs:enumeration value="SV"/>
<xs:enumeration value="AX"/>
<xs:enumeration value="CF"/>
<xs:enumeration value="DC"/>
<xs:enumeration value="EX"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="TrgOpt" default="none">
<xs:simpleType>
<xs:enumeration value="dchg"/>
<xs:enumeration value="qchg"/>
<xs:enumeration value="dupd"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="BType" use="required">
<xs:simpleType>
<xs:enumeration value="BOOL"/>
<xs:enumeration value="Enum"/>
<xs:enumeration value="CodedEnum"/>
<xs:enumeration value="Octet64"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="Enumtype" type="xs:string" />
</xs:complexType>
</xs:element>
<xs:element name="DAI">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element ref="Val"/>

CDV 61850-6 IEC:2002 60 57/WG10
</xs:sequence>
<xs:simpleType>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="DO">
<xs:complexType>
<xs:sequence>
<xs:choice>
<xs:sequence>
<xs:element ref="CtlService" minOccurs="0"/>
<xs:element ref="Transient" minOccurs="0"/>
<xs:element ref="DA" minOccurs="1" maxOc-
curs="unbounded"/>
</xs:sequence>
<xs:element ref="DAI" minOccurs="0" maxOc-
curs="unbounded"/>
</xs:choice>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="CDC" type="xs:string" use="required"/>
<xs:attribute name="AccessControl" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="DatSet">
<xs:complexType/>
</xs:element>
<xs:element name="DataObjectDirectory">
<xs:complexType/>
</xs:element>
<xs:element name="DataRef">
<xs:complexType/>
</xs:element>
<xs:element name="DataSet">
<xs:complexType>
<xs:sequence>
<xs:element ref="FCDA" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="DataSetDirectory">
<xs:complexType/>
</xs:element>
<xs:element name="Device">
<xs:complexType>
<xs:sequence>

CDV 61850-6 IEC:2002 61 57/WG10

curs="unbounded"/>
<xs:element ref="Connection" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="Subdevice" minOccurs="0" maxOc-
curs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Type" type="xs:NMTOKEN" use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="DynAssociation">
<xs:complexType/>
</xs:element>
<xs:element name="DynDataSet">
<xs:complexType>
</xs:complexType>
</xs:element>
<xs:element name="DynReportControl">
<xs:complexType>
</xs:complexType>
</xs:element>
<xs:element name="Enhanced">
<xs:complexType/>
</xs:element>
<xs:element name="EntryId">
<xs:complexType/>
</xs:element>
<xs:element name="Enumtype">
<xs:complexType>
<xs:sequence>
<xs:element ref="Enum" minOccurs="2"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Enum">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="Ord" type="xs:unsignedInt"
use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="ExtRef">
<xs:complexType>
use="required"/>
use="required"/>
use="required"/>
<xs:attribute name="LNInst" type="xs:string"
use="required"/>
<xs:attribute name="DONam" type="xs:string" use="required"/>

CDV 61850-6 IEC:2002 62 57/WG10

<xs:attribute name="IntAdr" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="FCDA">
<xs:complexType>
<xs:attribute name="LNClass" type="xs:NMTOKEN"/>
<xs:attribute name="DONam" type="xs:string"/>
<xs:attribute name="FC" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="FileHandling">
<xs:complexType/>
</xs:element>
<xs:element name="GOOSE">
<xs:complexType>
<xs:attribute name="Max" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="GSE">
<xs:complexType>
<xs:attribute name="Mintime" type="xs:unsignedInt"/>
<xs:attribute name="Maxtime" type="xs:unsignedInt"/>
</xs:complexType>
</xs:element>
<xs:element name="GSEControl">
<xs:complexType>
<xs:sequence>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="GCName" type="xs:string"
use="required"/>
<xs:attribute name="ConfRev" type="xs:string"/>
<xs:attribute name="Type" default="GOOSE">
<xs:simpleType>
<xs:enumeration value="GSSE"/>
<xs:enumeration value="GOOSE"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="AppId" type="xs:string" use="required"/>
<xs:attribute name="DatSet" type="xs:string"
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="GSEDir">
<xs:complexType/>
</xs:element>
<xs:element name="GSSE">
<xs:complexType>
<xs:attribute name="Max" type="xs:integer"/>
</xs:complexType>
</xs:element>

CDV 61850-6 IEC:2002 63 57/WG10
<xs:element name="GetControlValue">
<xs:complexType/>
</xs:element>
<xs:element name="GetDataObjectDefinition">
<xs:complexType/>
</xs:element>
<xs:element name="GetDataSetValue">
<xs:complexType/>
</xs:element>
<xs:element name="GetDirectory">
<xs:complexType/>
</xs:element>
<xs:element name="Header">
<xs:complexType>
<xs:sequence>
<xs:element ref="History" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="Version" type="xs:string"/>
<xs:attribute name="Revision" type="xs:string"/>
<xs:attribute name="ToolId" type="xs:string"/>
<xs:attribute name="NameStructure" use="required">
<xs:simpleType>
<xs:enumeration value="FuncName"/>
<xs:enumeration value="IEDName"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="History">
<xs:complexType>
<xs:sequence maxOccurs="unbounded">
<xs:element ref="Hitem"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Hitem">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="Version" type="xs:string"
use="required"/>
<xs:attribute name="Revision" type="xs:string"
use="required"/>
<xs:attribute name="When" type="xs:string"
use="required"/>
<xs:attribute name="Who" type="xs:string"/>
<xs:attribute name="What" type="xs:string"/>
<xs:attribute name="Why" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="IED">
<xs:complexType>
<xs:sequence>
<xs:element ref="Services" minOccurs="0"/>
<xs:element ref="AccessPoint" maxOccurs="unbounded"/>

CDV 61850-6 IEC:2002 64 57/WG10

curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Manufacturer" type="xs:string"/>
<xs:attribute name="ConfigVersion" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="IEDNam" type="xs:string"/>
<xs:element name="Inputs">
<xs:complexType>
<xs:sequence>
<xs:element ref="ExtRef" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="LDevice">
<xs:complexType>
<xs:sequence>
<xs:element ref="LN0"/>
<xs:element ref="LN" minOccurs="1" maxOc-
curs="unbounded"/>
<xs:element ref="AccessControl" minOccurs="0"/>
curs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="LN">
<xs:complexType>
<xs:sequence>
curs="unbounded"/>
curs="unbounded"/>
curs="unbounded"/>
<xs:element ref="DO" minOccurs="0" maxOc-
curs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Inst" type="xs:unsignedInt"/>
use="required"/>
<xs:attribute name="LNType" type="xs:string"
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="LN0">
<xs:complexType>
<xs:sequence>

CDV 61850-6 IEC:2002 65 57/WG10

curs="unbounded"/>
curs="unbounded"/>
curs="unbounded"/>
<xs:element ref="GSEControl" minOccurs="0" maxOc-
curs="unbounded"/>
<xs:element ref="SampledValueControl" minOccurs="0"
maxOccurs="unbounded"/>
<xs:element ref="SettingControl" minOccurs="0"/>
<xs:element ref="DO" minOccurs="0" maxOc-
curs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="LNType" type="xs:string"
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="LNode">
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element ref="Text"/>
</xs:sequence>
use="required"/>
<xs:attribute name="IEDNam" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="LNodeType">
<xs:complexType>
<xs:sequence>
<xs:element ref="DO" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="IEDType" type="xs:string"/>
<xs:attribute name="LNClass" type="xs:string"
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="Log" type="xs:string"/>
<xs:element name="LogControl">
<xs:complexType>
<xs:sequence>
</xs:sequence>
<xs:attribute name="LCBName" type="xs:string"
use="required"/>
<xs:attribute name="LogEna" type="xs:string" de-
fault="FALSE"/>
<xs:attribute name="IntgPd" type="xs:string" default="0"/>
use="required"/>
<xs:attribute name="LogRef" type="xs:string"
use="required"/>

CDV 61850-6 IEC:2002 66 57/WG10
</xs:complexType>
</xs:element>
<xs:element name="OptFlds">
<xs:complexType>
<xs:element ref="SeqNum"/>
<xs:element ref="TimeStamp"/>
<xs:element ref="DatSet"/>
<xs:element ref="ReasonCode"/>
<xs:element ref="DataRef"/>
<xs:element ref="BufOvfl"/>
<xs:element ref="EntryId"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="P">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="Type" type="xs:string"
use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="PhysConn">
<xs:complexType>
<xs:sequence>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Private">
<xs:complexType>
<xs:simpleContent>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="ReadWrite">
<xs:complexType/>
</xs:element>
<xs:element name="ReasonCode">
<xs:complexType/>
</xs:element>
<xs:element name="ReportControl">
<xs:complexType>
<xs:sequence>
<xs:element ref="OptFlds" minOccurs="0"/>
<xs:element ref="RptEnabled" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="RCName" type="xs:string"
use="required"/>
<xs:attribute name="RptID" type="xs:string" use="required"/>
use="required"/>
<xs:attribute name="ConfRev" type="xs:unsignedInt"
use="required"/>

CDV 61850-6 IEC:2002 67 57/WG10
<xs:attribute name="Buffered" type="xs:boolean" de-

fault="FALSE"/>
<xs:attribute name="BufTim" type="xs:unsignedInt" de-
fault="0"/>
fault="0"/>
</xs:complexType>
</xs:element>
<xs:element name="Router">
<xs:complexType/>
</xs:element>
<xs:element name="RptEnabled">
<xs:complexType>
<xs:sequence>
<xs:element ref="ClientLN" minOccurs="0" maxOc-
curs="unbounded"/>
</xs:sequence>
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="SBO">
<xs:complexType/>
</xs:element>
<xs:element name="SCL">
<xs:complexType>
<xs:sequence>
<xs:element ref="Header"/>
<xs:element ref="Substation"/>
<xs:element ref="IED"/>
<xs:element ref="LNodeType"/>
<xs:element ref="Enumtype"/>
<xs:element ref="Communication"/>
</xs:choice>
curs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="SGEdit">
<xs:complexType/>
</xs:element>
<xs:element name="SMV">
<xs:complexType>
</xs:complexType>
</xs:element>
<xs:element name="SampledValueControl">
<xs:complexType>
<xs:sequence>
<xs:element ref="SmvOpts" minOccurs="0"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="SVCName" type="xs:string"
use="required"/>
<xs:attribute name="ConfRev" type="xs:string"/>
<xs:attribute name="SmvId" type="xs:string" use="required"/>

CDV 61850-6 IEC:2002 68 57/WG10
<xs:attribute name="Multicast" type="xs:boolean" de-

fault="TRUE"/>
use="required"/>
<xs:attribute name="SmpRate" type="xs:unsignedInt"
use="required"/>
</xs:complexType>
</xs:element>
<xs:element name="SeqNum">
<xs:complexType/>
</xs:element>
<xs:element name="Server">
<xs:complexType>
<xs:sequence>
<xs:element ref="Authentication" minOccurs="0"/>
<xs:element ref="LDevice" maxOccurs="unbounded"/>
<xs:element ref="Association" minOccurs="0" maxOc-
curs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Timout" type="xs:string" default="30"/>
<xs:attribute name="SecAPRef" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="Services">
<xs:complexType>
<xs:element ref="DynAssociation"/>
<xs:element ref="GetDirectory"/>
<xs:element ref="GetDataObjectDefinition"/>
<xs:element ref="SGEdit"/>
<xs:element ref="DataObjectDirectory"/>
<xs:element ref="GetDataSetValue"/>
<xs:element ref="SetDataSetValue"/>
<xs:element ref="DataSetDirectory"/>
<xs:element ref="ConfDataSet"/>
<xs:element ref="DynDataSet"/>
<xs:element ref="ReadWrite"/>
<xs:element ref="DynReportControl"/>
<xs:element ref="SetControlValue"/>
<xs:element ref="GetControlValue"/>
<xs:element ref="GSEDir"/>
<xs:element ref="GOOSE"/>
<xs:element ref="GSSE"/>
<xs:element ref="FileHandling"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="SetControlValue">
<xs:complexType/>
</xs:element>
<xs:element name="SetDataSetValue">
<xs:complexType/>
</xs:element>
<xs:element name="SettingControl">
<xs:complexType>
<xs:sequence>
</xs:sequence>
<xs:attribute name="NumOfSGs" type="xs:unsignedInt"
use="required"/>

CDV 61850-6 IEC:2002 69 57/WG10
<xs:attribute name="ActSG" type="xs:unsignedInt" de-

fault="1"/>
</xs:complexType>
</xs:element>
<xs:element name="SmvOpts">
<xs:complexType>
<xs:element ref="refreshtime"/>
<xs:element ref="samplesynchronised"/>
<xs:element ref="samplerate"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="Subdevice">
<xs:complexType>
<xs:sequence>
curs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Phase" default="all">
<xs:simpleType>
<xs:enumeration value="all"/>
<xs:enumeration value="A"/>
<xs:enumeration value="B"/>
<xs:enumeration value="C"/>
<xs:enumeration value="N"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="Subnetwork">
<xs:complexType>
<xs:sequence>
<xs:element ref="ConnectedAP" maxOccurs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Bitrate" type="xs:decimal"/>
</xs:complexType>
</xs:element>
<xs:element name="Substation">
<xs:complexType>
<xs:sequence>
curs="unbounded"/>
<xs:element ref="VoltageLevel" maxOccurs="unbounded"/>
curs="unbounded"/>
</xs:sequence>

CDV 61850-6 IEC:2002 70 57/WG10
</xs:complexType>
</xs:element>
<xs:element name="Text" type="xs:string"/>
<xs:element name="TimeStamp">
<xs:complexType/>
</xs:element>
<xs:element name="Timed">
<xs:complexType/>
</xs:element>
<xs:element name="Transient">
<xs:complexType/>
</xs:element>
<xs:element name="TrgOpEna">
<xs:complexType>
<xs:element ref="dchg"/>
<xs:element ref="qchg"/>
<xs:element ref="dupd"/>
<xs:element ref="period"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="Val">
<xs:complexType>
<xs:simpleContent>
<xs:attribute name="SGroup" type="xs:integer"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="VoltageLevel">
<xs:complexType>
<xs:sequence>
curs="unbounded"/>
<xs:element ref="Bay" maxOccurs="unbounded"/>
curs="unbounded"/>
</xs:sequence>
<xs:attribute name="Voltage" type="xs:string"/>
</xs:complexType>
</xs:element>
<xs:element name="certificate">
<xs:complexType/>
</xs:element>
<xs:element name="dchg">
<xs:complexType/>
</xs:element>
<xs:element name="dupd">
<xs:complexType/>
</xs:element>
<xs:element name="none">
<xs:complexType/>
</xs:element>
<xs:element name="password">
<xs:complexType/>
</xs:element>
<xs:element name="period">
<xs:complexType/>

CDV 61850-6 IEC:2002 71 57/WG10
</xs:element>
<xs:element name="qchg">
<xs:complexType/>
</xs:element>
<xs:element name="refreshtime">
<xs:complexType/>
</xs:element>
<xs:element name="samplerate">
<xs:complexType/>
</xs:element>
<xs:element name="samplesynchronised">
<xs:complexType/>
</xs:element>
<xs:element name="strong">
<xs:complexType/>
</xs:element>
<xs:element name="weak">
<xs:complexType/>
</xs:element>
</xs:schema>

CDV 61850-6 IEC:2002 72 57/WG10
Annex B
(normative)
Extension syntax for drawing layout coordinates
This appendix defines a simple SCL extension to add coordinates to objects, so that they can
be easily shown on a drawing. This is sufficient for a lot of drawing tasks, and serves here as
an example of extension of the core SCL by another name space.
The handling respective drawing of connection relations as well as the packaging of objects
into drawing pages is private, respective a parameter of the interpreting application. Mean-
ingful drawings could be a substation in a substation single line, a bay in a bay single line,
the communication section for a communication configuration drawing.
The coordinate system is a relative x, y - system with coordinates using positive integer num-
bers. The point (0,0) is the upper left point of a drawing plane which is principally open to
downwards and right direction. The unit 1 principally refers to the size of an object. It is pos-
sible to use different object sizes, then 1 is the size of the smallest object. However, then
transport of coordinates between different drawing applications might lead to strange repre-
sentations.
If coordinates are defined at different SCL tag hierarchy levels, then each level contains co-
ordinates relative to the higher level. The absolute coordinate of a lower level is thus calcu-
lated by summing up all higher level coordinates, and the object coordinates themselves. In
case that at a higher level there are no coordinates defined, then (x,y) = (0,0) is assumed.
This is illustrated in the following figure. Here e.g. the bay 3 of substation 1 voltage level 1
has the absolute coordinates (0+1+6, 0+1+4) = (7,5) within a picture showing the substation
1, or even both substations.
0,0 Substation 1
1,1 Voltagelevel 1
2,2 Bay 1
2,4 Bay 2 6,4 Bay 3
1,15 Voltagelevel 2
6,2
3,5
0,20 Substation 2
1,1 6,2
Aditional XML elements:
Only the additional XML attributes x and y for the coordinates in x and y direction are needed
as addition to the SCL elements, which represent drawable objects. Additionally the optional

CDV 61850-6 IEC:2002 73 57/WG10
attribute dir with value horizontal or vertical can optionally give the preferred connection di-
rection of the object. If this attribute is defined for a bay, this means that all contained pri-
mary devices are oriented vertically, except dir is explicitly stated at them. The coordinate
name space shall be http://www.iec.ch/61850/sclcoordinates001.
An appropriate XML schema definition is:
<xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema
xmlns:sxy=http://www.iec.ch/61850/sclcoordinates001
targetNamespace=http://www.iec.ch/61850/sclcoordinates001
attributeFormDefault=qualified>
<xsd:element name=object type=anyType>
<xsd:attribute name=x type=xsd:integer />
<xsd:attribute name=y typexsd:integer />
<xsd:attribute name=dir type=Conndir default= />
</xsd:element>
<xsd:simpleType name=Conndir>
<xsd:restriction base=xsd:string>
<xsd:enumeration value=horizontal/>
<xsd:enumeration value=vertical />
</xsd:restriction<
</xsd:simpleType>
</xsd:schema>
The following gives an SCL example using the coordinates. The device E1Q1QB1 in this ex-
ample will have the coordinates (4, 7) relative to the substation.
<?xml version="1.0"?>
<SCL xmlns:sxy="http://www.iec.ch/61850/sclcoordinates001",
xmlns="http://www.iec.ch/61850/scl001">
<Header Ref="SCL Example" Revision="C" NameStructure="FuncName"/>
<Substation Ref="" sxy:x="0" sxy:y="0">
<VoltageLevel Ref="E1" sxy:x="1" sxy:y="1">
<Bay Ref="Q1" sxy:x="1" sxy:y="1">
<Device Ref="QA1" Type="CBR" sxy:x="2" sxy:y="2">
<LNode Ref="1" LNClass="CSWI"/>
<Connection CNodeRef="L1"/>
<Private Type="MyLayout">X=5 Y=25</Private>
</Device>
<Device Ref="QB1" Type="DIS" sxy:x="2" sxy:y="5"
sxy:dir="vertical">
<Connection CNodeRef="BB1" BayRef="W1"/>
</Device>
</Bay>
</VoltageLevel>
</Substation>
</SCL>

CDV 61850-6 IEC:2002 74 57/WG10
Annex C
(normative)
Relations between SCL and IEC61970-301 (CIM)

This appendix defines the relations between an SCL based model, and the CIM model de-
fined in IEC61970-301 for energy system applications.
The substation structure of the SCL model (Figure 3) with the hierarchy Substation / Voltage
level / Bay / Device corresponds to the substation structure in the CIM core model. The SCL
tranformer modelling by means of transformer windings as device also corresponds to CIM.
The topology connections with connectivity nodes, and with terminals to connect a device to
a connectivity node, also corresponds to the topology description in CIM. So this part of the
models can be structurally mapped to each other.
The CIM model contains also a relation from power system resources, i.e. all structural ob-
jects listed above, to logical nodes. This corresponds to the SCL attachment of logical nodes
with the LNode element to the SCL Substation section elements.
The additional CIM relation of measurand values to logical nodes, and the CIM adoption of
the measurand / measurand value naming conventions according to parts 7-x of this stan-
dard series, allow to relate SCL data objects and attributes to CIM measurand values. This
gives the link to find from the CIM model within the SCL description the IEDs supplying the
measurand values, and the measurand value addressing.
As explained above, the structures of CIM and SCL are prepared to be combined. However,
for a concrete project also the identifying names of the instances must fit together. Naming in
CIM is done with the cim:Name attribute of each power system resource, which corresponds
to the Nam attribute in SCL. However, within SCL Nam shall be a technical key e.g. accord-
ing to IEC61346. Within CIM however often some textual, operator related names are used
as cim:Name values. Therefore for combination of the CIM model part for energy manage-
ment applications with the SCL model part of substation automation systems the following
shall apply:
It shall be specified, if the cim:Name contains the same values / value category then the
scl:Nam.
If the cim:Name coresponds to the scl:Nam, then these two attribute values shall be re-
lated to each other.
If the cim:Name contains an operator related text, then it shall be related to the scl:Desc
attribute, and this attribute shall contain the values related to the cim:Name. It is recom-
mended that the CIM alias name is used to hold the technical key corresponding to the
scl:Nam.
A CIM file containing at least the model parts defined for the Substation section in this stan-
dard, and keeps resp. defines the instance naming rules specified above, is a valid SCL ex-
tension. The appropriate part of the CIM model with definition of the cim namespace at the
SCL element shall be a valid SCL file extension, additional to the SCL substation section.
Note: in case that the CIM class of a logical node also contains a reference to the IED and the logical device
which host the LN instance, with values corresponding to the scl:IEDNam and the scl:LDInst, this CIM extension
can optionally replace the SCL substation section in an SCL file.

CDV 61850-6 IEC:2002 75 57/WG10
Annex D
(normative)
Extension syntax for maintenance

This appendix defines a simple SCL extension to indicate for LNodeType attributes, if they
are defined as mandatory, optional or private. As this is only needed for planning of system
extensions, or by using the SCL syntax as general specification of CDCs, it is considered to
be an extension package.
The name space for this extension package shall be

http://www.iec.ch/61850/sclmaintenance001.
An appropriate XML schema definition is:
<xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema
xmlns:sma=http://www.iec.ch/61850/sclcmaintenance001
targetNamespace=http://www.iec.ch/61850/sclmaintenance001 attributeFormDefault=qualified>
<xsd:element name=object type=anyType>
<xsd:attribute name=MOP type=mop />
</xsd:element>
<xsd:simpleType name=mop>
<xsd:restriction base=xsd:string>
<xsd:enumeration value=M/>
<xsd:enumeration value=O />
<xsd:enumeration value=P />
</xsd:restriction<
</xsd:simpleType>
</xsd:schema>
The MOP value M means mandatory, O means optional, and P means private, i.e. specific to
the manufacturer of the concerned IED type.

CDV 61850-6 IEC:2002 76 57/WG10
Annex E
(informative)
SCL Data Type Definition


<!ELEMENT SCL (Header, (Substation | IED | LNodeType | Communica-

tion)+, Private*)>
<!ELEMENT Header (History?, Text?) > 
<!ATTLIST Header
Ref CDATA #REQUIRED
Version CDATA #IMPLIED
Revision CDATA ""
ToolId CDATA ""
NameStructure (FuncName | IEDName) #REQUIRED>

<!ELEMENT Text (#PCDATA)*> 
<!ELEMENT Private (#PCDATA)*> 
<!ATTLIST Private
Type CDATA "">
<!ELEMENT History (Hitem)+> 
<!ELEMENT Hitem (#PCDATA)*> 
<!ATTLIST Hitem
Version CDATA #REQUIRED
Revision CDATA #REQUIRED
When CDATA #REQUIRED
Who CDATA ""
What CDATA ""
Why CDATA "">
<!ELEMENT Substation (Text?, LNode*, VoltageLevel+ , Private*) >

<!ATTLIST Substation
Nam CDATA ""
Desc CDATA "">
<!ELEMENT VoltageLevel (Text?, LNode*, Bay+, Private* ) >

<!ATTLIST VoltageLevel
Nam CDATA ""
Desc CDATA ""
Voltage CDATA #IMPLIED>
<!ELEMENT Bay (Text?, LNode*, ConNode*, Device*, Private?) >

<!ATTLIST Bay
Nam CDATA ""
Desc CDATA "" >

CDV 61850-6 IEC:2002 77 57/WG10
<!ELEMENT ConNode (Text?, LNode*, Private*) >

<!ATTLIST ConNode
Nam CDATA #REQUIRED
Desc CDATA "">
<!ELEMENT Device (Text?, LNode*, Connection*, Subdevice*, Private* )>

<!ATTLIST Device
Nam CDATA #REQUIRED
Desc CDATA ""
Type NMTOKEN #REQUIRED> 
<!ELEMENT Connection EMPTY>

<!ATTLIST Connection
CNodeNam CDATA #REQUIRED
Terminal CDATA ""
BayNam CDATA #IMPLIED
VLNam CDATA #IMPLIED
SSNam CDATA #IMPLIED > 
<!ELEMENT Subdevice (Text?, LNode*, Private*) >

<!ATTLIST Subdevice
Nam CDATA #REQUIRED
Desc CDATA ""
Phase (all | A | B | C | N | none) "all">
<!ELEMENT LNode (Text)?> 
<!ATTLIST LNode
Inst CDATA ""
LNClass NMTOKEN #REQUIRED
Prefix CDATA ""
LDInst CDATA ""
IEDNam CDATA #IMPLIED> 
<!ELEMENT IED (Text?, Services?, AccessPoint+, Private*) >
<!ATTLIST IED
Nam CDATA ""
Desc CDATA ""
Type CDATA ""
Manufacturer CDATA ""
ConfigVersion CDATA "">
<!ELEMENT Services (DynAssociation | SettingGroups | GetDirectory |

GetDataObjectDefinition | SGEdit
| DataObjectDirectory | GetDataSetValue | SetDataSetValue | Da-
taSetDirectory | ConfDataSet | DynDataSet | ReadWrite
| DynReportControl | SetControlValue | GetControlValue | GSEDir |
GOOSE | GSSE | FileHandling)* >
<!ELEMENT DynAssociation EMPTY> 
<!ELEMENT SettingGroups EMPTY> 
<!ELEMENT GetDirectory EMPTY> 
<!ELEMENT GetDataObjectDefinition EMPTY>
<!ELEMENT DataObjectDirectory EMPTY>
<!ELEMENT GetDataSetValue EMPTY>

CDV 61850-6 IEC:2002 78 57/WG10
<!ELEMENT SetDataSetValue EMPTY>

<!ELEMENT SGEdit EMPTY>
<!ELEMENT DataSetDirectory EMPTY>
<!ELEMENT ConfDataSet EMPTY>
<!ATTLIST ConfDataSet
Max CDATA #REQUIRED
Modify (Yes | No) "Yes" >
<!ELEMENT DynDataSet EMPTY> 
<!ATTLIST DynDataSet
Max CDATA #REQUIRED>
<!ELEMENT DynReportControl EMPTY> 
<!ATTLIST DynReportControl
Max CDATA #REQUIRED>
<!ELEMENT SetControlValue EMPTY> 
<!ELEMENT GetControlValue EMPTY>
<!ELEMENT ReadWrite EMPTY>
<!ELEMENT GSEDir EMPTY>
<!ELEMENT GOOSE EMPTY>
<!ATTLIST GOOSE
Max CDATA "">
<!ELEMENT GSSE EMPTY>
<!ATTLIST GSSE
Max CDATA "">
<!ELEMENT FileHandling EMPTY> 
<!ELEMENT AccessPoint (Text?, Router?, Clock?, (Server | LN+)?) >


<!ATTLIST AccessPoint
Nam CDATA #REQUIRED>
<!ELEMENT Router EMPTY >

<!ELEMENT Clock EMPTY >
<!ELEMENT Server (Text?, Authentication?, LDevice+, Association*, Pri-

vate*)>
<!ATTLIST Server
Timout CDATA "30"
SecAPRef CDATA "">
<!ELEMENT Authentication (none | password | weak | strong | certifi-

cate)+ >
<!ELEMENT none EMPTY>
<!ELEMENT password EMPTY>
<!ELEMENT weak EMPTY>
<!ELEMENT strong EMPTY>
<!ELEMENT certificate EMPTY>
<!ELEMENT LDevice (Text?, LN0, LN*, AccessControl?, Private* ) > 
<!ATTLIST LDevice
Inst CDATA ""
Desc CDATA "">
<!ELEMENT LN0 (Text?,Log?,DataSet*, ReportControl*, LogControl*, GSE-

Control*, SampledValueControl*, SettingControl?, DO*, Inputs?, Pri-
vate* )>
<!ATTLIST LN0
LNType CDATA #REQUIRED>

CDV 61850-6 IEC:2002 79 57/WG10
<!ELEMENT LN (Text?, DataSet*, ReportControl*, LogControl*, DO*, In-

puts?, Private* ) >
<!ATTLIST LN
Inst CDATA ""
Prefix CDATA ""
LNType CDATA #REQUIRED>
<!ELEMENT Log (#PCDATA) >
<!ELEMENT DataSet (Text?, FCDA+) > 
<!ATTLIST DataSet
Nam CDATA #REQUIRED
Desc CDATA "">
<!ELEMENT FCDA EMPTY>

<!ATTLIST FCDA
LDInst CDATA ""
Prefix CDATA ""
LNClass NMTOKEN ""
LNInst CDATA ""
DONam CDATA ""
Attr CDATA ""
FC CDATA "" >
<!ELEMENT ReportControl (Text?, TrgOpEna?, OptFlds?, RptEnabled? ) >

<!ATTLIST ReportControl
RCName CDATA #REQUIRED
RptID CDATA #REQUIRED
DatSet CDATA #REQUIRED
ConfRev CDATA #REQUIRED
Buffered CDATA "FALSE"
BufTim CDATA "0"
IntgPd CDATA "0">
<!ELEMENT RptEnabled (ClientLN* ) >

<!ATTLIST RptEnabled
Max CDATA "1">
<!ELEMENT ClientLN EMPTY>

<!ATTLIST ClientLN
IEDNam CDATA #REQUIRED
LDInst CDATA #REQUIRED
Prefix CDATA ""
LNInst CDATA ""
LNClass NMTOKEN #REQUIRED>
<!ELEMENT Maxno (#PCDATA) >

<!ELEMENT TrgOpEna (dchg | qchg | dupd | period)+>
<!ELEMENT dchg EMPTY>
<!ELEMENT qchg EMPTY>
<!ELEMENT dupd EMPTY>
<!ELEMENT period EMPTY>
<!ELEMENT OptFlds ((SeqNum | TimeStamp | DatSet | ReasonCode | Da-

taRef| BufOvfl | EntryId)+ )>
<!ELEMENT SeqNum EMPTY>
<!ELEMENT TimeStamp EMPTY>
<!ELEMENT DataRef EMPTY>
<!ELEMENT DatSet EMPTY>
<!ELEMENT ReasonCode EMPTY>
<!ELEMENT BufOvfl EMPTY>

CDV 61850-6 IEC:2002 80 57/WG10
<!ELEMENT EntryId EMPTY>
<!ELEMENT LogControl (Text?, TrgOpEna?) > 
<!ATTLIST LogControl
LCBName CDATA #REQUIRED
LogEna CDATA "FALSE"
IntgPd CDATA "0"
DatSet CDATA #REQUIRED>
<!ELEMENT GSEControl (Text?, IEDNam*) > 
<!ATTLIST GSEControl
GCName CDATA #REQUIRED
ConfRev CDATA ""
Type (GSSE | GOOSE) "GOOSE"
AppId CDATA #REQUIRED
DatSet CDATA #REQUIRED>
<!ELEMENT IEDNam (#PCDATA) > 
<!ELEMENT SampledValueControl (Text?, SmvOpts?, IEDNam* ) > 
<!ATTLIST SampledValueControl
SVCName CDATA #REQUIRED
ConfRev CDATA ""
SmvId CDATA #REQUIRED
Multicast CDATA "TRUE"
DatSet CDATA #REQUIRED
SmpRate NMTOKEN #REQUIRED>
<!ELEMENT SmvOpts ( (refreshtime | samplesynchronised | samplerate)+

)>
<!ELEMENT refreshtime EMPTY>
<!ELEMENT samplesynchronised EMPTY>
<!ELEMENT samplerate EMPTY>
<!ELEMENT SettingControl (Text?) >

<!ATTLIST SettingControl
NumOfSGs CDATA #REQUIRED
ActSG CDATA "1">
<!ELEMENT Inputs (Text?, ExtRef+) >

<!ELEMENT ExtRef EMPTY>
<!ATTLIST ExtRef
Prefix CDATA ""
LNInst CDATA #REQUIRED
DONam CDATA #REQUIRED
Attr CDATA ""
IntAdr CDATA "">
<!ELEMENT AccessControl ANY >
<!ELEMENT Association EMPTY>

<!ATTLIST Association
Kind (pre-established | predefined) #REQUIRED
AssociationId CDATA ""

CDV 61850-6 IEC:2002 81 57/WG10
Prefix CDATA ""

LNInst CDATA #REQUIRED
LNClass NMTOKEN #REQUIRED>
<!ELEMENT Communication (Text?, Subnetwork+, Private*) >

<!ELEMENT Subnetwork (Text?, ConnectedAP+, Private* ) >
<!ATTLIST Subnetwork
Nam CDATA #REQUIRED
Bitrate CDATA ""
Type CDATA ""> 
<!ELEMENT GSE EMPTY> 

<!ATTLIST GSE
Addr CDATA ""
LDInst CDATA ""
CBNam CDATA ""
Mintime CDATA ""
Maxtime CDATA "">
<!ELEMENT SMV EMPTY >

<!ATTLIST SMV
Addr CDATA ""
LDInst CDATA ""
CBNam CDATA "">
<!ELEMENT ConnectedAP (Address, GSE*, SMV*, PhysConn*, Private*) > <!-

-the IED access point connected to the bus -->
<!ATTLIST ConnectedAP
Nam CDATA #REQUIRED>
<!ELEMENT Address (P* )>

<!ELEMENT P (#PCDATA)>
<!ATTLIST P
Type CDATA #REQUIRED>
<!ELEMENT PhysConn (P* ) >

<!ATTLIST PhysConn
Type CDATA #REQUIRED>
<!ELEMENT LNodeType (Text?, DO+ ) >

<!ATTLIST LNodeType
Ref CDATA #REQUIRED
IEDType CDATA ""
Desc CDATA ""
LNClass CDATA #REQUIRED>
<!ELEMENT DO (((CtlService?, Transient?, DA*) | DAI*), Private* ) > <!-

-a data object which is contained in the LN type-->
<!ATTLIST DO
Nam CDATA #REQUIRED
CDC CDATA #REQUIRED
AccessControl CDATA "">
<!ELEMENT CtlService (SBO | Timed | Enhanced )* >
<!ELEMENT SBO EMPTY> 

<!ELEMENT Timed EMPTY> 
<!ELEMENT Enhanced EMPTY> 
<!ELEMENT Transient EMPTY>

CDV 61850-6 IEC:2002 82 57/WG10
<!ELEMENT DA (Val*) >

<!ATTLIST DA
SAdr CDATA ""
FC (ST | MX | CO | SP | SG | SE | SV | AX | CF | DC | EX) #REQUIRED
TrgOpt (dchg | qchg | dupd | none) "none"
BType (BOOL | INT8 | INT16 | INT32 | INT8U | INT16U | INT32U | FLOAT32
| FLOAT64 | Enum | CodedEnum | VisString32 | VisString64 | Vis-
String255 | Octet64) #REQUIRED
Valkind (Spec | Conf | RO | Set) "Set"
Enumtype CDATA ""
Nam CDATA #REQUIRED> 
<!ELEMENT Enumtype (Enum+) >

<!ATTLIST Enumtype
Ref CDATA #REQUIRED>
<!ELEMENT Enum (#PCDATA) >

<!ATTLIST Enum
Ord CDATA #REQUIRED>
<!ELEMENT Val (#PCDATA) > 
<!ATTLIST Val
SGroup CDATA "">
<!ELEMENT DAI (Val)* >

<!ATTLIST DAI
SAdr CDATA ""
Valkind (Spec | Conf | RO | Set) "Set"
Nam CDATA #REQUIRED> 

CDV 61850-6 IEC:2002 83 57/WG10
Annex F
(informative)
Examples
D.1 SCL file contents
Below you will find a small example with one substation bay and one IED type just to give an
idea how an SCL file may look like.
<SCL xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.iec.ch/61850/scl001"
xs:noNamespaceSchemaLocation="Mypath/scl-001.xsd">
<Header Ref="SCL Example" Revision="C" NameStructure="IEDName"/>
<Substation Nam="">
<VoltageLevel Nam="E1">
<Bay Ref="Q1">
<Device Nam="QA1" Type="CBR">
</Device>
<Device Nam="QB1" Type="DIS">
<LNode Nam="2" LNClass="CSWI"/>
<Connection CNodeNam="BB1" BayNam="W1"/>
</Device>
</Bay>
</VoltageLevel>
</Substation>
<Communication>
<Subnetwork Ref="W1" Type="8-MMS/TCP">
<Text>Station bus</Text>
<ConnectedAP IEDNam="E1Q1KA1" Nam="S1"><Address/>
</ConnectedAP>
<ConnectedAP IEDNam="E1Q2KA1" Nam="S1"><Address/>
</ConnectedAP>
</Subnetwork>
</Communication>
<IED Nam="E1Q1KA1" Type="MyType">
<AccessPoint Ref="S1">
<Server>
<LDevice Ref="C1">
<LN0 LNType="LN0"/>
<LN Nam="1" LNClass="CSWI" LNType="CSWIa"/>
<LN Nam="2" LNClass="CSWI" LNType="CSWIa">
<DataSet Nam="Positions">
<DOName LNClass="CSWI" LNInst="1" DONam="Pos"/>
<DOName LNClass="CSWI" LNInst="2" DONam="Pos"/>
</DataSet>
<ReportControl Ref="Report1" DataSet="Positions">
<RptEnabled Max=4>
<LNName IEDNam="A1KA1" LDInst="" LNInst="1"
LNClass="IHMI"/>
</RptEnabled>
</ReportControl>
<LogControl Nam="PositionLog" LogRef="C1"
DataSet="Positions">
<TrgOpts><dchg/></TrgOpts>
</LogControl>
</LN>

CDV 61850-6 IEC:2002 84 57/WG10
</LDevice>
<Association Kind="pre-established" IEDRef="AA1KA1"
LDInst="" LNClass="IHMI" LNInst="1"/>
</Server>
</AccessPoint>
</IED>
<IED Nam="" Type="Ibb-PB Router">

<AccessPoint Nam="S1">
<Router/>
</AccessPoint>
<AccessPoint Nam="S2"/>
</IED>
<LNodeType Ref="CSWIa" LNClass="CSWI">
<DO Nam="Pos" Type="DPC">
<CtlService> <SBO/> </CtlService>
<DA Nam=stVal FC=ST TrgOpt=dchg BType=Enum Enumtype=Pos/>
<DA Nam=ctlVal FC=CO TrgOpt=none BType=BOOL />
</DO>
<DO Nam="GrpAl" Type="SPS">
<DA Nam=stVal FC=ST TrgOpt=dchg BType=BOOL>
</DO>
</LNodeType>
<LNodeType Ref="LN0" LNClass="LLN0">
<DO Nam="Mode" Type="INC"/>
<DA Nam=stVal FC=ST TrgOpt=dchg BType=INT32>
</DO>
<DO Nam="Health" Type="ISI"/>
<DA Nam=stVal FC=ST TrgOpt=dchg BType=INT32>
</DO>
</LNodeType>
<Enumtype Ref=Pos>
<Enum Ord=0>intermediate-state</Enum>
<Enum Ord=1>off</Enum>
<Enum Ord=2>on</Enum>
<Enum Ord=3>bad-state</Enum>
</Enumtype>
</SCL>
D2 Complete example
Here a bigger example based on the specification in part 5 section I.1.3.2 of this standard se-
ries is given. The naming of devices is changed however to conform to IEC 61346. Even this
example is not 100% complete, but it illustrates most of the SCL possibilities for system de-
scription, i.e. it is a .SCD file.

CDV 61850-6 IEC:2002 85 57/WG10
Substation configuration
D1Q1 Out of Scope

Example T 1-1
Distance Protection
1 Protection signalling
2 Voltage Levels
Central Functions:
D1 220 kV 10km
Synchrocheck
E1 132 kV
5 Bays
ID01 Buchholz Relay
1 - D1Q1 Feeder with Transformer, CT Overload Protection
2 E1Q2 Feeder with DIS, CBR, CT, VT Transformer-Differential.-Protection 220KV
3 E1Q4 Static Busbar Protection signalling
4 E1Q1 Feeder with DIS, CBR , CT, VT
5 E1Q3 Feeder with DIS, CBR , CT, VT 2 U E02 E1Q2
IE02 132KV
Distance Protection
Voltage Regulator
E1Q4
E1Q1 E1Q3
3
Interlocking Interlocking
E01 Distance Protection Distance Protection
Differential Protection Differential Protection
U E01 U E03
IE03
I
4 5
Figure 10 - T1-1 Substation Configuration
Communication system configuration
D1Q1
Example T 1-1 Out of Scope
Dist Distance Protection

Protection signalling
Single communication bus
Central Functions:
10km
Synchrocheck
IEDs for: 5
Transformer. Dist Distance Protection
11
Combined Bay Unit (Circuit Breaker, 7
ID01
Disconnector, CT and VT). W01
Buchholz Relay
Each Protection. 6 Overload Protection
Central Functions. TDifn Transformer-Differential.-Protection

U E02 8 Voltage Regulation
IE02
No. Name ID
1 Dist E1Q1BP3 (PDIS)
2 Difn E1Q1BP2 (PLDF)
3 Dist E1Q3BP3 (PDIS)
4 Difn E1Q3BP2 (PLDF)
5 Dist D1Q1BP3 (PDIS)
6 TDifn D1Q1BP2 (PTDF) 9 1 10 3
7 Trafo D1T1SB1 Dist Interlocking
Dist Interlocking
8 LV Bay1 E1Q1SB1 Distance Protection Distance Protection
9 LV Bay2 U E01 Difn U E03 Difn Differential Protection
E1Q2SB1 Differential Protection
10 LV Bay2 E1Q3SB1 IE01 2 IE03 4
11 Central D1Q1SB4 (CILO)
Figure 11 - T1-1 Communication Configuration

CDV 61850-6 IEC:2002 86 57/WG10
Transformer IED
D1Q1
Example T 1-1
Single communications bus Central Functions:
10km
IED for: Transformer bay. Synchrocheck
5
No. Name ID
11
7 Trafo Bay1 D1T1 7
ID01
WX01
Buchholz Relay
HV Bay 1 (Transformer bay) 6 Overload Protection
TDifn Transformer-Differential.-Protection
UE02 8
IED Voltage Regulation
7 LD IE02
D1T1SB1
Current LN
Transformer
(D1T1TCTR)
LD
S1 LN
Power transformer 9 10 3
(D1T1YPTR) 1
Dist Interlocking Dist Interlocking
Transformer tap- Distance Protection
change controller Distance Protection
UE01 Difn UE03 Difn Differential Protection
(D1T1CTCC) Differential Protection
Power transformer IE01 2 IE03 4
earth fault neutraliser
(D1T1YEFN)
Power transformer
power shunt
D1T1YPSH)
Figure 12 - T1-1 Transformer bay
SCL file contents
Below is a (not fully completed) SCL file for above example specification.
<!DOCTYPE SCL SYSTEM "scl-001.dtd">
<SCL>
<Header Ref="SCL Example T1-1" Revision="" NameStruc-
ture="IEDName"/>
<Substation Ref="">
<VoltageLevel Ref="D1" Voltage="220kV">
<Bay Nam="Q1">
<LNode Ref="1" LNClass="PDIS" IEDRef="D1Q1KA3"/>
<Device Ref="I1" Type="CTR">
<LNode Ref="1" LNClass="TCTR" LDInst="LD1"
IEDRef="D1Q1KA1"/>
</Device>
<Device Ref="T1" Type="PTR">
<LNode Ref="1" LNClass="PDIF" IEDRef="D1Q1KA2"/>
<LNode Ref="1" LNClass="YPTR" LDInst="LD2"
IEDRef="D1Q1KA1"/>
<Connection CNodeRef="L2" BayRef="Q2" VLRef="E1"/>
</Device>
</Bay>
</VoltageLevel>
<VoltageLevel Ref="E1" Voltage="132kV">
<Bay Ref="Q1">
<LNode Ref="1" LNClass="MMXU" IEDRef="E1Q1KA1"/>

CDV 61850-6 IEC:2002 87 57/WG10
<LNode Ref="1" LNClass="PDIS" IEDRef="E1Q1KA3"/>

<LNode Ref="1" LNClass="PDIF" IEDRef="E1Q1KA2"/>
<Device Ref="QA1" Type="CBR">
<LNode Ref="1" LNClass="CSWI" IEDRef="E1Q1KA1"/>
<LNode Ref="1" LNClass="CILO"/>
</Device>
<Device Ref="QB1" Type="DIS">
<Connection CNodeRef="B1" BayRef="Q4"/>
</Device>
<Device Ref="U1" Type="VTR">
<LNode Ref="1" LNClass="XVTR"/>
</Device>
<LNode Ref="1" LNClass="XCTR"/>
</Device>
</Bay>
<Bay Ref="Q2">
<LNode Ref="1" LNClass="PDIS"/>
<LNode Ref="1" LNClass="PDIF"/>
<LNode Ref="1" LNClass="AVCO"/>
</Device>
</Device>
</Device>
</Device>
</Bay>
<Bay Ref="Q3">
<LNode Ref="1" LNClass="MMXU" IEDRef="E1Q3KA1"/>
<LNode Ref="1" LNClass="PDIS" IEDRef="E1Q3KA3"/>
<LNode Ref="1" LNClass="PDIF" IEDRef="E1Q3KA2"/>
</Device>

CDV 61850-6 IEC:2002 88 57/WG10

</Device>
</Device>
</Device>
</Bay>
</VoltageLevel>
</Substation>
<Communication>
<Subnetwork Ref="WX01" Type="8-MMS/TCP" Bitrate="10" >
<Text>Station bus</Text>

<ConnectedAP IEDRef="E1Q1KA1" Ref="S1">
<Address>
<P Type="IP">10.0.0.12</P>
</Address>
</ConnectedAP>
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>
<ConnectedAP IEDRef="D1Q1KA1" Ref="S1">
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>

<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>
<Address/>
</ConnectedAP>

CDV 61850-6 IEC:2002 89 57/WG10
</Subnetwork>
</Communication>
<IED Ref="E1Q1KA1" Type="">
<Server>
<LDevice Ref="LD1" >
<LN0 Ref="" LNType="LN0">
<DataSet Ref="Positions">
<DOName LNClass="CSWI" LNInst="1" DORef="Pos"/>
</DataSet>

<ReportControl Ref="Report" DataSet="Positions">
<RptEnabled><Max>5</Max>
<LNName IEDRef="A1KA1" LDRef="LD1" LNRef="1"
LNClass="IHMI"/>
</RptEnabled>
</ReportControl>
<LogControl Ref="PositionLog" LogRef="LD1" Da-
taSet="Positions">
<TrgOpts>
<dataChange/>
</TrgOpts>
</LogControl>
</LN0>
<LN Ref="1" LNClass="CSWI" LNType="CSWIa"/>
<LN Ref="1" LNClass="MMXU" LNType="MMXUa"/>
</LDevice>
LDRef="LD1" LNClass="IHMI" LNRef="1"/>
</Server>
</AccessPoint>
</IED>
<Server>
<LDevice>
<LN0 Ref="" LNType="LN0"/>
<LN Ref="1" LNClass="PDIF" LNType="PLDif"/>
</LDevice>
</Server>
</AccessPoint>
</IED>
<Server>
<LDevice>
<LN Ref="1" LNClass="PDIS" LNType="PDISa"/>
</LDevice>
</Server>
</AccessPoint>
</IED>
<IED Ref="E1Q3KA1" Type="Mytype">
<Server>

CDV 61850-6 IEC:2002 90 57/WG10
<LDevice Ref="LD1">
<LN Ref="2" LNClass="CSWI" LNType="CSWIa">
<DataSet Ref="Positions">
</DataSet>
<ReportControl Ref="Report1" DataSet="Positions">
<RptEnabled><Maxno>4</Maxno>
<LNName IEDRef="A1KA1" LDRef="LD1" LNRef="1"
LNClass="IHMI"/>
</RptEnabled>
</ReportControl>
<LogControl Ref="PositionLog" LogRef="1" Da-
taSet="Positions">
<TrgOpts>
<dataChange/>
</TrgOpts>
</LogControl>
</LN>
<LN Ref="1" LNClass="MMXU" LNType="MMXUa"/>
</LDevice>
</Server>
</AccessPoint>
</IED>
<Server>
<LDevice>
<LN Ref="1" LNClass="PDIF" LNType="PLDif"/>
</LDevice>
</Server>
</AccessPoint>
</IED>
<Server>
<LDevice>
</LDevice>
</Server>
</AccessPoint>
</IED>
<IED Ref="D1Q1KA1" Type="">
<Server>
<LDevice Ref="LD1">
<LN Ref="1" LNClass="TCTR" LNType="CTRa"/>
</LDevice>
<LDevice Ref="LD2">
<LN Ref="1" LNClass="YPTR" LNType="PTRa"/>
</LDevice>

CDV 61850-6 IEC:2002 91 57/WG10

</Server>
</AccessPoint>
</IED>
<Server>
<LDevice>
<LN Ref="1" LNClass="PDIF" LNType="PTrDif"/>
</LDevice>
</Server>
</AccessPoint>
</IED>
<Server>
<LDevice>
</LDevice>
</Server>
</AccessPoint>
</IED>
<Server>
<LDevice>
<LN Ref="1" LNClass="CILO" LNType="CILOa"/>
<LN Ref="1" LNClass="RSYN" LNType="RSYNa"/>
</LDevice>
</Server>
</AccessPoint>
</IED>
<LNodeType Ref="LN0" LNClass="LLN0">
<DO Ref="Mode" Type="ISC"/>
<DO Ref="Health" Type="ISI"/>
<DO Ref="Loc" Type="SPS"/>
</LNodeType>
<LNodeType Ref="CSWIa" LNClass="CSWI">
<DO Ref="Pos" Type="DPC">
<CtlService CtlMode="Controllable">
<SBO/>
</CtlService>
<DA Ref="pulseConfig.cmdQual">pulse</DA>
<DA Ref="pulseConfig.onDur">100</DA>
</DO>
<DO Ref="GrAlm" Type="SPS"/>
</LNodeType>
<LNodeType Ref="MMXUa" LNClass="MMXU">

CDV 61850-6 IEC:2002 92 57/WG10
<DO Ref="Mode" Type="ISC">

<CtlService CtlMode="Controllable"/>
</DO>
<DO Ref="Beh" Type="ISI"/>
<DO Ref="Name" Type="PLATE"/>
<DO Ref="Amps" Type="MV"/>
<DO Ref="Volts" Type="MV"/>
</LNodeType>
<LNodeType Ref="PDISa" LNClass="PDIS">
</DO>
<DO Ref="Name" Type="PLATE"/>
<DO Ref="Oper" Type="ACT"/>
<DO Ref="Start" Type="ACT"/>
</LNodeType>
<LNodeType Ref="CILOa" LNClass="CILO">
</DO>
<DO Ref="NamPlt" Type="LPL"/>
<DO Ref="EnaOpen" Type="SPS"/>
<DO Ref="EnaClose" Type="SPS"/>
</LNodeType>
<LNodeType Ref="RSYNa" LNClass="CILO">
</DO>
<DO Ref="Release" Type="SPS"/>
<DO Ref="InBand" Type="SPS"/>
</LNodeType>
<LNodeType Ref="PLDif" LNClass="PDIF">
</DO>
<DO Ref="HeaPlt" Type="LPL"/>
<DO Ref="Op" Type="ACT"/>
<DO Ref="Str" Type="ACT"/>
<DO Ref="ATimCrv" Type="CURVE"/>
</LNodeType>
<LNodeType Ref="PTrDif" LNClass="PDIF">
</DO>
<DO Ref="Oper" Type="ACT"/>
<DO Ref="Start" Type="ACT"/>
<DO Ref="ATimCrv" Type="CURVE"/>
</LNodeType>
<LNodeType Ref="CTRa" LNClass="TCTR">

CDV 61850-6 IEC:2002 93 57/WG10
</DO>
<DO Ref="Amps" Type="MV"/>
</LNodeType>
<LNodeType Ref="PTRa" LNClass="YPTR">
</DO>
<DO Ref="IMTemp" Type="MV"/>
<DO Ref="HPTemp" Type="MV"/>
<DO Ref="HPTTr" Type="SPS"/>
</LNodeType>
</SCL>

75b41c86-5865-4ec0-8614-f3affdcde169 (1)

Uploaded by

Copyright:

Available Formats

75b41c86-5865-4ec0-8614-f3affdcde169 (1)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

75b41c86-5865-4ec0-8614-f3affdcde169 (1)

Uploaded by

Copyright:

Available Formats

CDV 61850-6 IEC:2002 1 57/WG10

CDV2R8Draft IEC 61850-6

Communication Networks and Systems in Substations

Part 6: Configuration description language for communication in

Version 8CDV, August 2002

2 NORMATIVE REFERENCES ................................................................................................................... 6

5 INTENDED ENGINEERING PROCESS WITH SCL ............................................................................. 9

6 THE SCL OBJECT MODEL .................................................................................................................... 12

8 THE SCL LANGUAGE ............................................................................................................................. 19

ANNEX B (NORMATIVE) EXTENSION SYNTAX FOR DRAWING LAYOUT COORDINATES

ANNEX C (NORMATIVE) RELATION BETWEEN SCL AND IEC 61970-301 (CIM)

ANNEX D (NORMATIVE) EXTENSION SYNTAX FOR MAINTENANCE

ANNEX E (INFORMATIVE) SCL DATA TYPE DEFINITION

ANNEX F (INFORMATIVE) EXAMPLES

Version 8CDV, August 2002

INTERNATIONAL ELECTROTECHNICAL COMMISSION

COMMUNICATION NETWORKS AND SYSTEMS IN SUBSTATIONS

Part 6: Configuration description language for communication

Version 8CDV, August 2002

Figure 1 - Relative position of this part within IEC 61850

Version 8CDV, August 2002

COMMUNICATION NETWORKS AND SYSTEMS IN SUBSTATIONS

Part 6: Configuration description language for communication

Version 8CDV, August 2002

W3C, Extensible Markup Language (XML) 1.0, http://www.w3.org/TR/2000/REC-xml-

W3C, Name spaces in XML, http://www.w3.org/TR/1999/REC-xml-names-19990114

W3C, XML Schema Part 0: Primer, http://www.w3.org/TR/2001/REC-xmlschema-0-20010502

W3C, XML Schema Part 1: Structures, http://www.w3.org/TR/2001/REC-xmlschema-1-

W3C, XML Schema Part 2: Data Types, http://www.w3.org/TR/2001/REC-xmlschema-2-

RFC 1953, GZIP file format specification version 4.3, http://www.ietf.org/rfc/rfc1952.txt

IEC 61850-5, Communication networks and systems in substations Part 5: Communication

Version 8CDV, August 2002

Version 8CDV, August 2002

CIM Common Information Model of IEC 61970-301

DO DATA in IEC61850-7-2, Data object class or instance, depending on context

DTD Document Type Definition

SCL Substation Configuration description Language

UML Unified Modelling Language according to Booch / Jacobson / Rumbaugh

URI Universal Resource Identifier

XML Extensible Markup Language

Version 8CDV, August 2002

5 Intended engineering process with SCL

1. IED capability description (points 1 and 2 above)

Version 8CDV, August 2002

File Transfer (REMOTE)

IED IED IED IED

Version 8CDV, August 2002

Version 8CDV, August 2002

6 The SCL object model

The SCL in its full scope describes a model of

The object model has three basic object levels:

Version 8CDV, August 2002

Version 8CDV, August 2002

Figure 3 - SCL object model

Version 8CDV, August 2002

-W1 logical bus

Figure 4 - Example configuration

6.1 The substation model

The purpose of the substation model is

To relate a logical node to a substation function (substation part or primary device or