IEC TS 61850-7-7:2018

IEC TS 61850-7-7 ®
Edition 1.0 2018-03
TECHNICAL
SPECIFICATION
colour
inside
Communication networks and systems for power utility automation –
Part 7-7: Machine-processable format of IEC 61850-related data models for tools

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 21 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.

IEC publications search - webstore.iec.ch/advsearchform IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 67 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
IEC TS 61850-7-7 ®
Edition 1.0 2018-03
TECHNICAL
SPECIFICATION
colour
inside
Communication networks and systems for power utility automation –

Part 7-7: Machine-processable format of IEC 61850-related data models for tools

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 33.200 ISBN 978-2-8322-5443-1

– 2 – IEC TS 61850-7-7:2018 © IEC 2018
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
1.1 General . 7
1.2 Namespace name and version . 7
1.3 Code Component distribution . 8
2 Normative references . 9
3 Terms and definitions . 9
4 Abbreviated terms. 10
5 Use cases . 10
5.1 Generation of SCL data type templates for system specification . 10
5.1.1 Description of the use case . 10
5.1.2 Technical details . 12
5.1.3 Information exchanged . 13
5.2 Generation of SCL data type templates for ICD files . 13
5.2.1 Description of the use case . 13
5.2.2 Technical details . 15
5.2.3 Information exchanged . 16
5.3 Validation of data model conformity . 16
5.3.1 Description of the use case . 16
5.3.2 Diagrams of use case . 17
5.3.3 Technical details . 18
5.4 Definition of private data model extensions by following the rules of the
standard . 19
5.4.1 Description of the use case . 19
5.4.2 Diagrams of use case . 20
5.4.3 Technical details . 21
5.4.4 Information exchanged . 22
5.5 Supporting the IEC 61850 data model change management . 22
5.5.1 Description of the use case . 22
5.5.2 Diagrams of use case . 24
5.5.3 Technical details . 26
5.5.4 Information exchanged . 27
5.5.5 Common terms and definitions . 28
6 Namespace file breakdown . 28
6.1 General . 28
6.2 Namespace dependencies . 28
6.3 Namespace types . 30
6.3.1 General. 30
6.3.2 Core namespace . 30
6.3.3 Domain namespace . 30
6.3.4 Technical report namespace . 30
6.3.5 Private namespace . 31
7 Overview of the format . 31
7.1 General . 31
7.2 File types . 31

7.2.1 NSD . 31
7.2.2 SNSD . 35
7.2.3 AppNS . 36
7.2.4 NSDoc . 37
7.3 NSD usage convention . 37
7.3.1 General. 37
7.3.2 Element identification . 38
7.3.3 Inheritance and extension . 38
7.3.4 DataObject parameterization . 39
7.3.5 CDC variants . 40
7.4 Naming convention . 40
7.4.1 File extension . 40
7.4.2 File name . 40
7.5 Example . 41
7.5.1 General. 41
7.5.2 NSD file example . 41
7.5.3 SNSD file example . 41
7.5.4 AppNS file example . 42
7.5.5 NSDoc file example . 42
8 File usage . 42
8.1 General . 42
8.2 System specification creation . 42
8.3 Manufacturer IED creation . 43
8.4 Creation of a non-standard name space . 43
8.5 IED data model validation . 44
8.6 Data model update management . 44
Annex A (normative) Schema NSD.xsd . 45
Schema IECCopyright.xsd . 68

Figure 1 – Generation of SCL data type templates for system specification diagrams . 12
Figure 2 – Generation of SCL data type templates for ICD files diagrams . 15
Figure 3 – Validation of data model conformity diagrams . 18
Figure 4 – Definition of private data model extensions by following the rules of the
standard diagrams . 21
Figure 5 – Supporting the IEC 61850 data model change management . 25
Figure 6 – Namespace dependencies . 29
Figure 7 – Service Namespace usage . 30
Figure 8 – Abstract LNClass hierarchy example . 34
Figure 9 – Specification type creation example . 43

– 4 – IEC TS 61850-7-7:2018 © IEC 2018
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
COMMUNICATION NETWORKS AND
SYSTEMS FOR POWER UTILITY AUTOMATION –

Part 7-7: Machine-processable format
of IEC 61850-related data models for tools

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
The main task of IEC technical committees is to prepare International Standards. In
exceptional circumstances, a technical committee may propose the publication of a technical
specification when
• the required support cannot be obtained for the publication of an International Standard,
despite repeated efforts, or
• the subject is still under technical development or where, for any other reason, there is the
future but no immediate possibility of an agreement on an International Standard.
Technical specifications are subject to review within three years of publication to decide
whether they can be transformed into International Standards.
Technical Specification IEC TS 61850-7-7 has been prepared by IEC technical committee 57:
Power systems management and associated information exchange.

The text of this technical specification is based on the following documents:
Enquiry draft Report on voting
57/1925/DTS 57/1956/RVDTS
Full information on the voting for the approval of this technical specification can be found in
the report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 61850 series, published under the general title Communication
networks and systems for power utility automation, can be found on the IEC website.
This IEC standard includes Code Components i.e. components that are intended to be directly
processed by a computer. Such content is any text found between the markers BEGINS> and , or otherwise is clearly labeled in this standard as a Code
Component.
The purchase of this IEC standard carries a copyright license for the purchaser to sell
software containing Code Components from this standard directly to end users and to end
users via distributors, subject to IEC software licensing conditions, which can be found at:
http://www.iec.ch/CCv1.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC website under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be
• transformed into an International standard,
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – IEC TS 61850-7-7:2018 © IEC 2018
INTRODUCTION
Year after year the IEC 61850 data models are extended both in depth with hundreds of new
data items, and in width with tens of new parts.
In order to foster an active tool market with good quality, and at the end to improve IEC 61850
interoperability, a machine-processable file, describing data model related parts of the
standard as input, is needed. This is the purpose of the new language Name Space Definition
(NSD) defined by this part of IEC 61850.
This will avoid the need for any engineering tool related to the IEC 61850 data models to get
the content of the standard manually entered, with a high risk of mistakes. This will also help
to easily spread any corrections to the data model, as requested to reach interoperability.
Tool vendors will be able to integrate NSD in their tools to distribute the standard data models
directly to end users.
COMMUNICATION NETWORKS AND
SYSTEMS FOR POWER UTILITY AUTOMATION –

Part 7-7: Machine-processable format
of IEC 61850-related data models for tools

1 Scope
1.1 General
This part of IEC 61850, which is a Technical Specification, specifies a way to model the code
components of IEC 61850 data model (e.g., the tables describing logical nodes, common data
classes, structured data attributes, and enumerations) in an XML format that can be imported
and interpreted by tools. The following main use cases are supported:
• Generation of SCL data type templates for system specification or ICD files.
• Validation of SCL data type templates.
• Definition of private extensions by following the rules of the standard.
• Adapting rapidly the whole engineering chain as soon as a new version of IEC 61850 data
model (an addendum, a corrigenda or a Tissue) affects the content of the standard.
• Provide tool-neutral textual help to users of tools on the data model contents.
• Supporting multi-language publication, i.e., enabling the expression of the data model in
different languages, through a machine processable format.
The purpose of this proposal is limited to the publication of the XML format which should
support the data model part of any IEC 61850 related standard. The publication of code
components themselves will be part of the related IEC 61850 part.
1.2 Namespace name and version
The new namespace name and version section is mandatory for any IEC 61850 namespace
(as defined by IEC 61850-7-1:2011).
The parameters which identify this new release of the NSD namespace
xmlns:nsd="http://www.iec.ch/61850/2016/NSD" are:
• Namespace Version: 2017
• Namespace Revision: A
• Namespace Release: 1
• Namespace release date: 2017/08/28

Edition Publication date Webstore Namespace
Edition 1.0 2017-?? IEC 61850-7-7:2017 IEC 61850-7-7:2017A

The namespace version relates to the edition of the standard: here namespace version 2017
refers to the first edition of this document.
Then, the revision relates to amendments if any: as for the current version of this document,
revision A corresponds to the original edition, without amendment. For the first amendment,
the revision will be B, etc.
– 8 – IEC TS 61850-7-7:2018 © IEC 2018
Finally, namespace release indicates an update of the related code component (if any)
without publication of a new version or revision of the current document. This could be used
for internal release of the code component during development of a new version of the
document, or to provide fixes of interoperability tissues without need to enter into a full
document update process.
The namespace release date is used for information purpose, to indicate when the
namespace has been created.
1.3 Code Component distribution
The Code Components included in this document are also available as electronic machine
readable files at:
http://www.iec.ch/public/TC57/supportdocuments/IEC_61850-7-7.2017.NSD.2017A.full.zip
The Code Component(s) included in this document are potentially subject to maintenance
works and the latest release is available in the repository located at:
http://www.iec.ch/TC57/supportdocuments
The latest version/release of the document will be found by selecting the file IEC_61850-7-
7.2017.NSD.{VersionStateInfo}.full.zip with the filed VersionStateInfo of the highest value.
Each Code Component is a ZIP package containing the electronic representation of the Code
Component itself, with a file describing the content of the package (IECManifest.xml).
The IECManifest contains different sections giving information on:
– The copyright notice
– The identification of the code component
– The publication related to the code component
– The list of the electronic files which compose the code component
– An optional list of history files to track changes during the evolution process of the code
component
The IECManifest related to this publication is:
xsi:schemaLocation="http://www.iec.ch/CC/2017/IECManifest IECManifest.xsd">


COPYRIGHT (c) IEC, 2017. This version of this XSD is part of IEC 61850-7-7:2017; see the IEC 61850-
7-7:2017 for full legal notices. In case of any differences between the here-below code and the IEC published content, the here-
below definition supersedes the IEC publication; it may contain updates. See history files. The whole document has to be taken
into account to have a full description of this code component.
See www.iec.ch/CCv1 for copyright details.

IEC License






startingVersion="NSD.XSD.v0.3" endingVersion="NSD.XSD.v1.0"/>
startingVersion="NSD.XSD.v1.0" endingVersion="NSD.XSD.v1.1"/>
startingVersion="NSD.XSD.v1.1" endingVersion="NSD.XSD.2017A"/>



The package is identified using the following naming rule:
{RefStandard}.{CodeComponentName}.{VersionRevision}.{LightFull}{PublicationStage}.zip
For current publication, the Code Component package name is:
IEC_61850-7-7.2017.NSD.2017A.full.zip
The life cycle of a code component is not restricted to the life cycle of the related publication.
The publication life cycle goes through two stages, Version (corresponding to an edition) and
Revision (corresponding to an amendment). A third publication stage (Release) allows
publication of Code Component without need to publish an amendment.
This is useful when InterOp Tissues need to be fixed. Then a new release of the Code
Component will be released, which supersedes the previous release, and distributed through
the IEC web site.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements of this document. For dated references, only the edition
cited applies. For undated references, the latest edition of the referenced document (including
any amendments) applies.
IEC TS 61850-2, Communication networks and systems in substations – Part 2: Glossary
IEC 61850-6, Communication networks and systems for power utility automation – Part 6:
Configuration description language for communication in electrical substations related to IEDs
IEC 61850-7-1, Communication networks and systems for power utility automation – Part 7-1:
Basic communication structure – Principles and models
IEC 61850-7-2, Communication networks and systems for power utility automation – Part 7-2:
Basic information and communication structure – Abstract communication service interface
(ACSI)
IEC 61850-7-3, Communication networks and systems for power utility automation – Part 7-3:
Basic communication structure – Common data classes
IEC 61850-7-4, Communication networks and systems for power utility automation – Part 7-4:
Basic communication structure – Compatible logical node classes and data object classes
IEC 61850-8-1, Communication networks and systems for power utility automation – Part 8-1:
Specific communication service mapping (SCSM) – Mappings to MMS (ISO 9506-1 and ISO
9506-2) and to ISO/IEC 8802-3
ISO 639-1:2002, Codes for the representation of names of languages – Part 1: Alpha-2 code
3 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC TS 61850-2 and the
following apply.
– 10 – IEC TS 61850-7-7:2018 © IEC 2018
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
data model
hierarchical structure of data and the related services used to define functions and devices in
IEC 61850
Note 1 to entry: The IEC 61850 standard series defines the core data model in IEC 61850-7-2, IEC 61850-7-3 and
IEC 61850-7-4, which is also the data model related to Substations. Other domains (like DER, Hydro, Wind, etc.)
could define their own data model based on IEC 61850 core data model to be able to use IEC 61850 core parts as
a common layer.
3.2
namespace
identification of a data model of a specific part of the standard
Note 1 to entry: This definition will be used in this document when a specific data model has to be represented.
Note 2 to entry: The W3C consortium has also defined the concept of namespace for XML documents to identify
the kind of elements which could be used in a file. This is typically the namespace used to identify an XML schema,
as per IEC 61850-6 usage. This is not the definition used within this document.
4 Abbreviated terms
In general, the glossary and abbreviated terms defined in IEC 61850-2 apply. The following
abbreviated terms are either exclusive to this document or particularly useful for
understanding this document and are repeated here for convenience.
CDC Common Data Class
DO Data Object
DA Data Attribute
LN Logical Node
NSD Name Space Definition
SCL System Configuration description Language
UML Unified Modeling Language
XML Extensible Markup Language
XSD XML Schema Definition
5 Use cases
5.1 Generation of SCL data type templates for system specification
5.1.1 Description of the use case
5.1.1.1 Name of use case
Use case identification
ID Domain(s) Name of use case
Administration Use machine readable format to generate SCL data type templates
for system specification
5.1.1.2 Narrative of use case
Narrative of use case
Short description – max 3 sentences
User take the namespace NSD corresponding to its needs and create data type templates
based on it.
Complete description
This use case describes how a Machine Processable file user can take benefit of the NSD
publication to create datatype templates from the standard description and allow creation of
an SSD for the specification of the process.
The Figure 1 presents the use case and the corresponding sequence diagram.

5.1.1.3 General remarks
General remarks
The creation of a data model for a process specification shall follow rules from standard
definitions of IEC 61850-7-2, IEC 61850-7-3, IEC 61850-7-4 or derived data models for other
domains (like Wind farm with IEC 61400-25-2).
This creation is done manually by checking against the standard in paper format. This is
source of errors.
Usage of NSD will allow for a tool to have the list of LNClass and CDCs available in a
standard to allow user to use them as input to its definition.

5.1.1.4 Diagrams of use case
Diagram of use case
The primary use case
uc Use Case 1
System Boundary
Tissue reporter
Machine processable
files
Generation of SCL data type
Publication manager
templates for system specification
Support IEC data model
User's specification tool
change
Namspace delegate(NOw)
Machine processable
file users
IED
Generation of SCL data
type templates
User's
Model manager (MM)
engineering tool
– 12 – IEC TS 61850-7-7:2018 © IEC 2018
sd Use Case 1
Machine processable User's specification tool
NSD Host
file users
(from Standard users)
(from Standard users)
GetNSDList(): List
RetrieveNSD(NSD_ID): NSD file
CreateEnumType(Id, Desc)
AddEnumVal(Ord, Value, Desc)
CreateDAType(Id, Desc)
AddBDA(Name, bType, type, Desc)
CreateDOType(Id, CDC, Desc)
AddSDO_DA(Name, Type, Desc)
CreateLNodeType(Id, Class, Desc)
AddDO(Name,
Type, Desc)
CreateProcessDataModel()
Publish SSD()
Figure 1 – Generation of SCL data type templates for system specification diagrams
5.1.2 Technical details
5.1.2.1 Actors: People, systems, applications, databases, the power system, and
other stakeholders
Actors
Grouping (community) Group description

Actor name Actor type Actor description Further
see actor list see actor list see actor list information
specific to this
use case
Machine readable people user of machine readable file,
file users
involved in system engineering
User’s
system engineering system of the IED specification
engineering Machine readable file users tool
system
5.1.2.2 Preconditions, assumptions, post condition, events
Use case conditions
Actor/System/Information/Contract Triggering Pre- Assumption
event conditions
NSD Host  The latest NSD of the
IEC 61850 namespaces are
hosted on the NSD host.
5.1.3 Information exchanged
Information exchanged
Name of Description of information Requirements to
information exchanged information data
exchanged R-ID
NSD_ID Identifier of an NSD, based on the
namespace identifier based on the
publication number, version and
revision
NSD list List of available NSD on the NSD
Host with a description
NSD file The file representing a Namespace
data model to be used by a tool

5.2 Generation of SCL data type templates for ICD files
5.2.1 Description of the use case
5.2.1.1 Name of use case
Use case identification
ID Domain(s) Name of use case
Administration Use machine readable format to generate SCL data type templates
for ICD files
5.2.1.2 Narrative of use case
Narrative of use case
Short description – max 3 sentences
User take the namespace NSD corresponding to its needs and create data type templates
based on it.
Complete description
This use case describes how a Machine Processable file user can take benefit of the NSD
publication to create datatype templates from the standard description and allow creation of
an ICD for a specific IED.
The Figure 2 presents the use case and the corresponding sequence diagram.

– 14 – IEC TS 61850-7-7:2018 © IEC 2018
5.2.1.3 General remarks
General remarks
The creation of a data model for an implementation in a device shall follow rules from the
standard definition of IEC 61850-7-2, IEC 61850-7-3, IEC 61850-7-4 or derived data models
for other domains (like Wind farm with IEC 61400-25-2).
This creation is done manually by checking against the standard in paper format. This is
source of errors.
Usage of NSD will allow for a tool to have the list of LNClass and CDCs available in a
standard to allow user to use them as input to its definition.

5.2.1.4 Diagrams of use case
Diagram of use case
The primary use case
uc Use Case 2
IED
Machine processable
file users
Generation of SCL data
type templates
User's
engineering tool
sd Use Case 2
Machine processable User's
file users NSD Host IED Factory engineering tool
(from Standard users) (from Standard users)
GetNSDList(): List
RetrieveNSD(NSD_ID): NSD file
CreateEnumType(Id, Desc)
AddEnumVal(Ord, Value, Desc)
CreateDAType(Id, Desc)
AddBDA(Name, bType, type, Desc)
CreateDOType(Id, CDC, Desc)
AddSDO_DA(Name, Type, Desc)
CreateLNodeType(Id, Class, Desc)
AddDO(Name, Type, Desc)
CreateIEDDataModel()
PublishICD()
Figure 2 – Generation of SCL data type templates for ICD files diagrams
5.2.2 Technical details
5.2.2.1 Actors: People, systems, applications, databases, the power system, and
other stakeholders
Actors
Grouping (community) Group description

Actor name Actor type Actor description Further
see Actor list see Actor list see Actor list information
specific to this
use case
Machine readable people user of machine readable file,
file users involved in system engineering
User’s system engineering system of the IED engineering
engineering Machine readable file users tool
system
– 16 – IEC TS 61850-7-7:2018 © IEC 2018
5.2.2.2 Preconditions, assumptions, post condition, events
Use case conditions
Actor/System/Information/Contract Triggering Pre- Assumption
event conditions
NSD Host  The latest NSD of the
IEC 61850 namespaces are
hosted on the NSD host.
5.2.3 Information exchanged
Information exchanged
Name of Description of information Requirements to
information exchanged information data
exchanged R-ID
NSD_ID Identifier of an NSD, based on the
namespace identifier based on the
publication number, version and
revision
NSD list List of available NSD on the NSD
Host with a description
NSD file The file representing a Namespace
data model to be used by a tool

5.3 Validation of data model conformity
5.3.1 Description of the use case
5.3.1.1 Name of use case
Use case identification
ID Domain(s) Name of use case
Administration Use machine readable format to validate conformity of a data
model to the standard
5.3.1.2 Narrative of use case
Narrative of use case
Short description – max 3 sentences
User takes the namespace NSD and SCL schema to validate syntactically and semantically a
data model
Complete description
This use case describes how a Machine Processable file user can take benefit of the NSD
publication to validate the conformity of a given Data Model created with a IED Configuration
Tool or manually edited.
The validation process includes
– Syntax validation of the SCL file against the IEC 61850-6 schema
– A semantic validation
For instance:
– Is the description of an LNodeType conforms to the LN NSD content?
– Are all mandatory DOs (resp. DAs) present in a LNodeType (resp. DOType)?
– Etc.
The Figure 3 presents the use case and the corresponding sequence diagram.

5.3.1.3 General remarks
General remarks
The existing data model to be validated shall follow rules from standard definition of
IEC 61850-7-2, IEC 61850-7-3, IEC 61850-7-4 or derived data models for other domains (like
Wind farm with IEC 61400-25-2).
This creation is done either by use of a configuration tool or done manually by checking
against the standard in paper format. It can be optionally manually edited to solve some found
issues. In any circumstances this process is prone to errors and the final result should be
checked to verify its conformity.
The syntactic conformity is checked thanks to the IEC 61850-6 schema. To check the
semantic conformity (excluding private extensions) the validation tool will make use of the
NSD files.
5.3.2 Diagrams of use case
Diagram of use case
The primary use case
uc Use Cases 3
User's
engineering tool
(from
Standard
users)
Validation of data model
conformity
Machine processable
file users
(from
Standard
users)
– 18 – IEC TS 61850-7-7:2018 © IEC 2018
sd Use Cases 3
Machine processable User's
NSD Host
file users engineering tool
(from Standard users) (from Standard users)
send(XSDSchemaVersion)
retrieveSCLSchema(XSDSchemaVersion): XSD_files
getNSDList(): NSD_List
sendNSDID(NSD_ID)
retrieveNSD(NSD_ID): NSD_file
sendSCLFile(SCL_file)
sendValidationReport(ValidationReport)

Figure 3 – Validation of data model conformity diagrams
5.3.3 Technical details
5.3.3.1 Actors: People, systems, applications, databases, the power system, and
other stakeholders
Actors
Grouping (community) Group description

Actor name Actor type Actor description Further
see Actor list see Actor list see Actor list information
specific to this
use case
Machine people user of machine readable file,
processable file involved in system engineering
users
User’s system engineering system of the IED Conformity
engineering tool Machine processable file users Validation tool

5.3.3.2 Preconditions, assumptions, post condition, events
Use case conditions
Actor/System/Information/Contract Triggering Pre- Assumption
event conditions
NSD Host  The latest NSD of the
IEC 61850 namespaces are
hosted on the NSD host.
And the latest SCL Schema
User’s engineering tool  For validation process it is
assumed that all the
validation semantic rules
are documented
5.3.3.3 Information exchanged
Information exchanged
Name of information Description of information Requirements to
exchanged exchanged information data
R-ID
NSD_ID Identifier of an NSD, based on the
namespace identifier based on the
publication number, version and
revision
NSD_list List of available NSD on the NSD
Host with a description
NSD_file The file representing a Namespace
data model to be used by a tool
XSDSchemaVersion The last version of WG10 7-6 SCL
XSD Schema
XSD_files The XSD SCL Files As provided by IEC
If allows to publish a
syntactic validation in the
validation report
SCL_file The SCL file to be validated
ValidationReport The file which is the result of the All the validations according
validation process of the to documented specified
DataModelFile rules
5.4 Definition of private data model extensions by following the rules of the standard
5.4.1 Description of the use case
5.4.1.1 Name of use case
Use Case identification
ID Domain(s) Name of use case
Administration Use machine readable format to create extension namespace for a
manufacturer specific data model

– 20 – IEC TS 61850-7-7:2018 © IEC 2018
5.4.1.2 Narrative of use case
Narrative of use case
Short description – max 3 sentences
User takes the namespace NSD corresponding to its needs and extend existing LNClass, or
create new LNClass. Then user is able to add new DataObject based on standard CDC.
Complete description
This use case describes how a manufacturer model manager can take benefit of the NSD
publication to create a private extension of a standard namespace by extending standard
LNClass or by creating new LNClass.
For extended or new LNClass, user will create new DataObject based on standard CDC.
User is also able to create private enumeration for new DataObject.
Then user will be able to define its own namespace ID and create the NSD file for its private
extension, known as private namespace.
The Figure 4 presents the use case and the corresponding sequence diagram.

5.4.1.3 General remarks
General remarks
A private namespace is an NSD file used to represent specific data model of a manufacturer
device.
The creation of a private namespace shall follow rules from standard definition of IEC 61850-
7-1. A private namespace is allowed only to extend existing LNClass or create new LNClass
(with a different name than existing LNclass) and add DataObject to them. Creations or
modifications of CDC, ConstructedAttribue or BasicTypes are forbidden. Enumerations can be
created for DataObjects added into private namespace.
A new DataObject shall not reuse an existing DataObject name if semantic is different.
standard NSD will help in searching
...