SIST EN 61850-10:2013/A1:2025

SLOVENSKI STANDARD
01-november-2025
Komunikacijska omrežja in sistemi za avtomatizacijo porabe električne energije -
10. del: Preskušanje skladnosti - Dopolnilo A1 (IEC 61850-10:2012/AMD1:2025)
Communication networks and systems for power utility automation - Part 10:
Conformance testing (IEC 61850-10:2012/AMD1:2025)
Kommunikationsnetze und -systeme für die Automatisierung in der elektrischen
Energieversorgung - Teil 10: Konformitätsprüfung (IEC 61850-10:2012/AMD1:2025)
Réseaux et systèmes de communication pour l'automatisation des systèmes électriques
- Partie 10: Essais de conformité (IEC 61850-10:2012/AMD1:2025)
Ta slovenski standard je istoveten z: EN 61850-10:2013/A1:2025
ICS:
29.240.30 Krmilna oprema za Control equipment for electric
elektroenergetske sisteme power systems
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 61850-10:2013/A1

NORME EUROPÉENNE
EUROPÄISCHE NORM September 2025
ICS 33.200
English Version
Communication networks and systems for power utility
automation - Part 10: Conformance testing
(IEC 61850-10:2012/AMD1:2025)
Réseaux et systèmes de communication pour Kommunikationsnetze und -systeme für die
l'automatisation des systèmes électriques - Partie 10: Automatisierung in der elektrischen Energieversorgung -
Essais de conformité Teil 10: Konformitätsprüfung
(IEC 61850-10:2012/AMD1:2025) (IEC 61850-10:2012/AMD1:2025)
This amendment A1 modifies the European Standard EN 61850-10:2013; it was approved by CENELEC on 2025-09-03. CENELEC
members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this amendment the
status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC
Management Centre or to any CENELEC member.
This amendment exists in three official versions (English, French, German). A version in any other language made by translation under the
responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as
the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the
Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland,
Türkiye and the United Kingdom.

European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2025 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
Ref. No. EN 61850-10:2013/A1:2025 E

European foreword
The text of document 57/2769/FDIS, future edition 2 of IEC 61850-10/AMD1, prepared by TC 57
"Power systems management and associated information exchange" was submitted to the IEC-
CENELEC parallel vote and approved by CENELEC as EN 61850-10:2013/A1:2025.
The following dates are fixed:
• latest date by which the document has to be implemented at national (dop) 2026-09-30
level by publication of an identical national standard or by endorsement
• latest date by which the national standards conflicting with the (dow) 2028-09-30
document have to be withdrawn
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC shall not be held responsible for identifying any or all such patent rights.
Any feedback and questions on this document should be directed to the users’ national committee. A
complete listing of these bodies can be found on the CENELEC website.
Endorsement notice
The text of the International Standard IEC 61850-10:2012/AMD1:2025 was approved by CENELEC as
a European Standard without any modification.
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
NOTE 1  Where an International Publication has been modified by common modifications, indicated by (mod),
the relevant EN/HD applies.
NOTE 2  Up-to-date information on the latest versions of the European Standards listed in this annex is available
here: www.cencenelec.eu.
Add the following references:
Publication Year Title EN/HD Year
IEC 61869-9 2016 Instrument transformers - Part 9: Digital EN IEC 61869-9 2019
interface for instrument transformers
IEC/IEEE 61850-9-3 2016 Communication networks and systems for - -
power utility automation - Part 9-3:
Precision time protocol profile for power
utility automation
Delete the following reference:
Publication Year Title EN/HD Year
IEC 62439-3 2012 Industrial communication networks - High EN 62439-3 2012
availability automation networks - Part 3:
Parallel Redundancy Protocol (PRP) and
High availability Seamless Redundancy
(HSR)
IEC 61850-10 ®
Edition 2.0 2025-07
INTERNATIONAL
STANDARD
AMENDMENT 1
Communication networks and systems for power utility automation -
Part 10: Conformance testing
ICS 33.200  ISBN 978-2-8327-0566-7

IEC 61850-10:2012-12/AMD1:2025-07(en)

IEC 61850-10:2012/AMD1:2025 © IEC 2025
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
Communication networks and systems for power utility automation -
Part 10: Conformance testing
AMENDMENT 1
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC Publication(s)"). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch [and/or]
www.iso.org/patents. IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 1 to IEC 61850-10 has been prepared by IEC technical committee 57: Power
systems management and associated information exchange.
The major changes in this amendment are as follows:
– server device conformance test procedures have been updated; new test cases are: sAss4,
sAss5, sAssN7, sSrv14, sSrv15, sDs15, sSg11.sSg14, sRp15, sRp16, sRp17, sRp23,
sRpN9, sBr29, sBrN9, sBrN10, sGop12, sGos8.15, sGos20.23, sGosN7, sSBOns8, sTm6,
sTm7, sTmP1, sTmP2, sTmP5, sTmPN1;
– client device conformance test procedures have been updated; new test cases are: cAss10,
cAssN8, cAssN9, cSrv10, cSrvN7.cSrvN9, cSg46, cRp14.22, cRp40.46, cBr14.22,
cBr30.32, cBr46, cLog9, cLog46, cLogN4, cGcb46, cSBOns10, cFt16, cMsvcb1, cMsvcb2,
cMsvcb46;
IEC 61850-10:2012/AMD1:2025 © IEC 2025
– sampled values test procedures have been merged into server;
– server IED configuration tool related conformance test procedures have been updated; the
ICD export and SCD import test cases have been merged into server, new test cases are:
tTf4, tTf5;
– System Configuration Tool related conformance test procedures have been updated; new
test cases are: tSieN2, tSce8.10, tSceN2, tDfeN3, tSmo7.9, tSse4.7, tSsi5.6, tSeh7.11;
– GOOSE performance test procedures have been updated; the performance classes have
been updated to align with the performance class definition updates.
The text of this Amendment is based on the following documents:
Draft Report on voting
57/2769/FDIS 57/2797/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this Amendment is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications/.
A list of all parts of IEC 61850 series, under the general title Communication networks and
systems for power utility automation, can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
___________
1 Scope
Add the following new text after the first paragraph of the Scope (before the NOTE):
Cyber security extensions provided by IEC 62351 are conformance tested against the
IEC 62351-100-4 and IEC 62351-100-6.
2 Normative references
Insert the following new normative references:
IEC/IEEE 61850-9-3:2016, Communication networks and systems for power utility automation
– Part 9-3: Precision time protocol profile for power utility
IEC 61850-10:2012/AMD1:2025 © IEC 2025
IEC 61869-9:2016, Instrument transformers – Part 9: Digital interface for instrument
transformers
Remove the following existing normative reference:
IEC 62439-3:2012, Industrial communication networks – High availability automation networks
– Part 3: Parallel Redundancy Protocol (PRP) and High Availability Seamless Redundancy
(HSR)
4 Abbreviated terms
Insert the following new abbreviated term:
PTP Precision Time Protocol
6 Device related conformance testing
Replace the existing text, figures (Figures 2 to 6) and tables (Tables 1 to 71) of Clause 6 with
the following new text, figures and tables:
6.1 Test methodology
Communication testing needs at least two devices to communicate with each other.
Comprehensive interoperability testing of all possible products is not feasible. Therefore, the
test concept shall include test devices, test configurations, and test scenarios. The dynamic
behaviour should be tested properly by using well-defined test cases.
Messages are generated to test the communication capabilities. Hardwired stimuli (contacts,
voltages, currents, etc.) and stimuli coming over a serial link if applicable should be used if
applicable.
Special attention shall be given to communication equipment such as star-couplers, switches,
etc. which shall support all requested features of the standard but not introduce additional
contingencies and limitations. The impact of the communication method (client-server, GOOSE,
SV, etc.) used by the DUT shall be considered properly in the test procedures. Verification of
functional applications (use of GOOSE messages) is not part of a conformance test even if
advanced tools may offer such analysis.
6.2 Conformance test procedures
6.2.1 General
This subclause describes the test procedure requirements, test structure, the abstract test
cases (what is to be tested). The format and a few examples of detailed test procedures (how
to perform the test) are given in Annex A.
6.2.2 Test procedure requirements
The test procedure requirements are:
– The abstract test cases describe what shall be tested, the detailed test procedures describe
how a test engineer, or a test system shall perform the test.
– Test cases include a reference to the applicable paragraph(s) in the referenced
document(s).
– The test results shall be reproducible in the same test lab and in other test labs.
– Support automated testing with minimal human intervention, as far as reasonably possible.
IEC 61850-10:2012/AMD1:2025 © IEC 2025
– The tests shall focus on situations that cannot easily be tested during, for example, a factory
or site acceptance test, and prevent inter-operability risks, for example:
• check behaviour of the device on delayed, lost, double and out of order packets,
• configuration, implementation, operation risks,
• mismatching names, parameters, settings, or data types,
• exceeding certain limits, ranges or timeouts,
• force situations to test negative responses,
• check all (control) state machine paths, and
• force simultaneous control operations from multiple clients.
– The ACSI tests focus on the application layer (mapping).
– The device under test (DUT) is considered as a black box. The I/O and the communication
interface are used for testing.
– The test includes testing the versions, data model and configuration file, and the use of
applicable ISO/IEC 9646 series terminology.
The test procedures shall be formatted as outlined in Figure 2. With this format, the test
procedures document can also be used as test report. A few test procedure examples are
depicted in Annex A.
Figure 2 – Test procedure format
IEC 61850-10:2012/AMD1:2025 © IEC 2025
6.2.3 Test structure
The test cases are structured as follows:
– documentation and version control (IEC 61850-4);
– configuration file (IEC 61850-6);
– data model (IEC 61850-7-3 and IEC 61850-7-4);
– mapping of ACSI models and services (IEC 61850-7-2 and applicable SCSM).
6.2.4 Test cases to test a server device
6.2.4.1 General
This part of the IEC 61850 series specifies the test system architecture and abstract test cases
for server devices. The abstract test cases shall be used for the definition of test procedures to
run in tests.
NOTE The SCSM specific test procedures are provided by test facilities agreed upon by the market participants.
6.2.4.2 Test system architecture to test a server device
In order to be able to perform a server device test, a minimum test set-up is necessary. The
test architecture contains (see Figure 3):
– DUT;
– client simulator to initiate and generate TPAA messages;
– GOOSE simulator to send correct and incorrect GOOSE messages;
– SV simulator to send correct and incorrect SV messages;
– test master to start/stop test cases, start/stop the analyzer and archive test results;
– time master;
– engineering tool to configure the DUT;
– protocol analyzer to store all the network traffic for each test case;
– signal generator to force binary and analogue events, controlled by the test master or test
engineer.
Figure 3 – Test system architecture to test a server device
IEC 61850-10:2012/AMD1:2025 © IEC 2025
The test system shall include documentation regarding test system hardware and test system
software.
6.2.4.3 Documentation and version control test procedure overview
The test cases listed in Table 1 shall apply.
Table 1 – Server documentation test cases
Test case Test case description
Check if the major/minor software version in the PICS documentation and the DUT do match
(IEC 61850-4). PICS shall contain:
• ACSI conformance statement according to IEC 61850-7-2:2010, Annex A
sDoc1
• IEC 61850-9-3 PICS (when supported)
• IEC 61869-9 conformance class a, b, c or d (when supported)
Check if the major/minor software version in the PIXIT documentation and software version of the
sDoc2 DUT does match (IEC 61850-4). PIXIT shall indicate the required information as requested in the
test cases
Check if the major/minor software version in the MICS documentation and software version of the
DUT does match (IEC 61850-4). MICS shall indicate the semantics of all non-standard Logical
sDoc3
Nodes, Data Objects, Data Attributes and enumeration. MICS may contain other items in
additional sections of the MICS.
Check if the major/minor software version in the TICS documentation and software version of the
sDoc4 DUT does match (IEC 61850-4). TICS shall indicate that the mandatory and applicable technical
issues are implemented.
Check the ICD if the server capabilities in the IED "services" section(s) do correspond with the
sDoc5
ACSI services specified in the PICS

6.2.4.4 Configuration file test cases
The test cases listed in Table 2 shall apply.
Table 2 – Server configuration file test cases
Test Test case description
case
sCnf1 Verify the SCL version = "2007", revision = "B", release = "4"
sCnf2 Verify the XML encoding is UTF-8 or utf-8;
sCnf3 Verify that the ICD validates according to SCL schema: version 2007, revision B, release 4
sCnf4 Use the ICT tool to export an ICD file. When ICD is not supported export IID file. Use this file for the
remaining tests. It is not allowed to change this SCL file with general purpose tools such as an XML
editor.
Condition: when the ICD is not fixed
sCnf5
Import the ICD or IID file from sCnf4 into SCT SIMULATOR and generate SCD file as follows:
• update IED name
• change IP/MAC address
• change SubNetwork name
• add DataSet's (when supported)
• add ReportControl's (when supported)
• add GSEControl's (when supported)
• add SampledValueControl's (when supported)
• add data flows (ExtRef's) from other IED's (when noIctBinding=F)
Import the SCD file into the ICT tool and select the IED to be handled from IED's named in the SCD
file by IED name
IEC 61850-10:2012/AMD1:2025 © IEC 2025
Test Test case description
case
sCnf6 Complete the GOOSE and SV subscribe from sCnf5 and export the IID file. Verify that the ExtRef
intAddr does not change when the external binding changes. The intAddr should not contain external
data.
Condition: when GOOSE and/or SV subscribe is supported
sCnf10 Verify the ICD has at most one Substation or Line or Process exists at SCL level and the attribute
"name" is "TEMPLATE".
Condition: when Substation or Line or Process section is present
sCnf11 Verify the ICD has none of the LNode bound to an IED different from "TEMPLATE" or "none"
Condition: when Substation section is present
sCnf20 Verify that the "Communication" element exists:
• IED/Services/DynAssociation or IED/AccessPoint/Services/DynAssociation is declared) and
IED/AccessPoint/ Server is declared or
• LN0/GSEControl element exist or
• LN0/SampledValueControl element exist
sCnf21 For each ConnectedAP/Address element:
Verify that exactly one "P" element with attribute type="OSI-PSEL" with a valid value (non-empty,
even number of characters, maximum 16 characters 0-9,A-F)
Verify that exactly one "P" element with attribute type="OSI-SSEL" with a valid value (non-empty,
even number of characters, maximum 16 characters 0-9,A-F)
Verify that exactly one "P" element with attribute type="OSI-TSEL" with a valid value (non-empty,
even number of characters, maximum 8 characters 0-9,A-F)
(Note that if xsi:type mechanism is used then schema validator can automatically verify the type)
Condition: IED/Services/DynAssociation is declared
sCnf22 Verify that for each accesspoint no more than one "P" element with attribute type="OSI-AP-Title" and
"OSI-AE-Qualifier and "IP" and "IP-SUBNET", "IP-GATEWAY", OSI-NSAP, OSI-AP-Invoke, OSI-AE-
Invoke and DNSName exists. For each of these that exist:
Verify OSI-AP-Title value contains only decimal digits and non-repeating commas
Verify OSI-AE-Qualifier value is decimal representation from 0-65535
Verify IP and IP-SUBNET and IP-GATEWAY contain a "standard dotted-decimal" for Ipv4
Verify Ipv6 and Ipv6-SUBNET and Ipv6-GATEWAY contain a RFC 4291 address with leading zeros
for Ipv6
Verify OSI-AP-Invoke and OSI-AE-Invoke values are between 0 and 65535.
sCnf23 For each GSE element:
Address/P[type=MAC-Address] right digit of first octet is odd (1,3,5,7,9,B,D,F) (multicast).
Address/P[type=VLAN-ID] present
Address/P[type=PRIORITY] present
Address/P[type=APPID] = 0000-3FFF or 8000-BFFF
Condition: when GSE element is present
sCnf24 For each SMV element referencing a SampledValueControl whose attribute multicast=true or missing,
verify Address/P[type=MAC-Address] right digit of first octet is odd (1,3,5,7,9,B,D,F) (multicast)
For each SMV element referencing a SampledValueControl whose attribute multicast=false, verify
Address/P[type=MAC-Address] right digit of first octet is even (0,2,4,6,8,A,C,E) (unicast)
For each SMV element in the ICD:
• Address/P[type=VLAN-ID] present
• Address/P[type=PRIORITY] = present
• Address/P[type=APPID] = 4000-7FFF
Condition: when SMV element is present
sCnf25 Verify the ICD that each Subnetwork/ConnectedAP@iedName is "TEMPLATE"
sCnf26 Verify each Subnetwork/ConnectedAP@apName matches one of IED/AccessPoint@name
IEC 61850-10:2012/AMD1:2025 © IEC 2025
Test Test case description
case
sCnf27 Verify for each GSE element, the GSE@cbName points to a GSEControl within the AccessPoint
pointed to by GSE//@apName and GSE@ldInst.
Condition: when GSE element is present
Verify for each SMV element, the SMV@cbName points to a SampledValueControl within the
sCnf28
AccessPoint pointed to by SMV//@apName and SMV@ldInst.
Condition: when SMV element is present
sCnf29 Verify that at least one SubNetwork type has value "8-MMS" when type is present or type is absent
sCnf40 Verify the ICD has exactly one IED element and that the attribute "name" of the element is
"TEMPLATE"
sCnf41 Verify all FCDA elements reference existing data and that doName and (optional) daName contain
correct references. (ref 61850-6:2010, 9.3.,7 Table 22).
• Verify attributes ldInst, lnClass, doName, and fc are declared.
• Verify attribute lnInst is declared if lnClass is not "LLN0".
• Verify first component of doName references a DO@name and second component (if any)
references a SDO@name within DO referenced by first component
• Verify first component of daName (if present) references a DA@name and other component (if
any) references a BDA@name within structure hierarchy of the DA referenced by first component
• Verify that at most one component of doName/daName contains an index and that ix attribute is
identical to this index (see 61850-6:2010, Table 22). Valid example: lnClass="MHAI" lnInst="1" fc="MX" doName="HA.phsAHar(0)" daName="cVal.mag.f" ix="0" />
sCnf42 Verify DOI/SDI/DAI structures match DataTypeTemplates (DOI@name is valid DO in LD/LN and
DAI@name is a leaf within that DO and SDI@name form hierarchy between DOI and DAI)
sCnf43 Verify that the ICD has none of the ExtRef references IEDs different from TEMPLATE or "@"
Condition: when ExtRef iedName attribute is present
sCnf44 Verify that the ICD has no ClientLN elements exist within ReportControl and no IEDName elements
within GSEControl and SampledValueControl
sCnf45 Verify all GSEControl/SampledValueControl/ReportControl have confRev>0 when datSet is not empty
sCnf46 Verify IED@originalSclVersion, IED@originalSclRevision and IED@originalSclRelease attributes
match corresponding attributes of SCL element (SCL@version, SCL@revision and SCL@release)
sCnf47 Verify multiple identically named DOI/SDI/DAI elements at the same level differ by "ix" attribute
(either different "ix" or "ix" attribute not present).
Condition: when DOI/SDI/DAI ix attribute is present
sCnf48 Verify multiple LLN0.SGCB do not appear in the same logical device hierarchy (defined by
LLN0.GrRef which references the parent logical device)
Condition: when multiple SGCB are present
sCnf49 Verify element "Log" exists only in LLN0
Condition: when Log is present
sCnf50 Verify that the name length of IED, Logical Devices, Logical Nodes, data objects, data attributes,
data sets and control blocks do not exceed the maximum length as specified in IEC 61850-7-2:2010,
22.2 and SCSM
sCnf51 Verify that logical node LPHD is present in each root logical device (IEC 61850-7-1:2010, 8.2.5)
sCnf52 Verify that DUT/tool can import file with GSEControl in multiple LN0
Add one GSEControl to first and last LN0 in the configuration of the device
Condition: Services/GSESettings attribute cbName is not "fix" or absent and multiple Logical Devices
exist and GOOSE max > 1
sCnf60 Verify that the attribute nameLength="64" exists in the IED/Services element
IEC 61850-10:2012/AMD1:2025 © IEC 2025
Test Test case description
case
sCnf61 Verify that the Services section must not contradict existing control block and data sets;
• Nr of DataSet elements <= ConfDataSet.max (if provided).
• Nr of ReportControl instances <= ConfReportControl.max (if provided)
• Nr of Buffered ReportControl instances <= ConfReportControl.maxBuf (if provided)
• Nr of GSEControl <= GOOSE.max (if provided)
• Nr of SMVControl <= SMVsc.max (if provided)
• Nr of LogControl <= ConfLogControl.max (if provided)
• Nr of LGOS instances <= SupSubscription.maxGo (if provided)
• Nr of LSVS instances <= SupSubscription.maxSv (if provided)
sCnf62 Verify the AccessPoint/Services element does not contain the attribute nameLength
Condition: when AccessPoint Services element is present
sCnf63 Verify AccessPoint/Services element does not contain any of the elements ConfLNs, and
ConfLdName
Condition: when AccessPoint Services element is present
sCnf64 Verify that in case SupSubscription is claimed to be supported at least one instance of LGOS or
LSVS must be in the ICD.
Condition: when SupSubscription element is present
sCnf65 Verify that if serviceType=GOOSE is specified for ExtRef the ClientServices.goose=true or
ClientServices rGOOSE=true. For serviceType=SMV the ClientServices.sv=true or
ClientServices.rSV=true
Condition: when serviceType=GOOSE or serviceType=SMV is present
sCnf70 Verify for each DAType/BDA or DOType/DA with attribute "bType"=Struct has attribute "type" whose
value matches DAType@id; does not declare valKind and does not contain a element
sCnf71 Verify for each DAType/BDA or DOType/DA with attribute "bType"=Enum has attribute "type" whose
value matches EnumType@id
sCnf72 Verify type names do not exceed 255 characters, contain no "whitespace" characters and contain
only characters from Basic-Latin and Latin-1-Supplement
sCnf73 Verify that each DOType element contains at least one SDO or DA element
sCnf74 Verify for each DA with FC="CO" (except "SBO") that the associated DAType contains the element
IEC 61850-8-1:2003
Verify for each DA name="SBO" (FC="CO") contains the ProtNS element
NOTE type default value is 8-MMS so it's optional
sCnf75 Verify for each (instance of) DOType/DA[name=ctlModel] whose associated EnumType contains
direct-with-normal-security has in the DOType a DA named "Oper". If ctlModel has valKind=RO and
valImport=missing/false then use the configured ctlModel value instead of EnumType.
Similar for sbo-with-normal-security, Oper, Cancel and SBO
Similar for direct-with-enhanced-security, Oper
Similar for sbo-with-enhanced-security, Oper, Cancel and SBOw
sCnf76 Deprecated same as sMdl18
Verify that element values actually match a value in the corresponding EnumType, "ord" shall
sCnf80
not be used, only EnumVal element values. Ref IEC 61850-6:2010, Table 45.
sCnf81 Verify that elements values match IEC 61850-6:2010, Table "Data type mapping" (if no table
rows then Val element is not allowed at all)
sCnf82 Verify for each LLN0 that if LLN0.NamPlt.lnNs is present it shall have value IEC 61850-7-4:2007B
(and ldNs is valid domain name space), otherwise LLN0.NamPlt.ldNs shall have value IEC 61850-7-
4:2007B.
sCnf83 Verify each ctlModel has an associated element
sCnf84 Verify CDC=ORG references use the ACSI format (with ".", no "$" and no functional constraint) and
that the reference does exist
Condition: when a data object with CDC=ORG is present
IEC 61850-10:2012/AMD1:2025 © IEC 2025
Test Test case description
case
sCnf85 Verify for each Logical Device whose LLN0 does not contain GrRef, the existence of Data Object
LLN0.NamPlt
Verify for each LLN0 which contains the DO NamPlt, the existence and non-null value for Data
Attribute LLN0.NamPlt.configRev
IEC 61869-9 configuration file test cases
sCnf100 Check if the server "ClientServices" capabilities in the ICD "services" section do match with the IED
capabilities:
• sv=true
• maxSMV = supported number of SV streams
Condition: when IEC 61869 SV subscribe is supported
sCnf120 Verify that all LDevice's with an IEC 61869 MSVCB have inst=MUnn where nn are digits.
sCnf121 Verify the existence of LPHD extension Data Objects: NamVariant, NamHzRtg, NamAuxVRtg
(optional), NamHoldRtg and NamMaxDlRtg (table 903) and MaxDl (part 7-4 Ed2 Amd1)
Verify the existence of LPHD.PhyNam data attributes: vendor, model, serNum, hwRev, swRev and d
and that these attributes have valKind read-only.
The effective logical node namespace: lnNs = IEC 61869-9:2016[A]
sCnf122 Verify the existence of TCTR extension Data Objects: NamAccRtg, NamARtg, NamClipRtg (table
905) and Clip, HoldTmms (part 7-4 Ed2 Amd1)
The effective logical node namespace: lnNs= IEC 61869-9:2016[A]
sCnf123 Verify the existence of TVTR extension Data Objects: NamAccRtg, NamVRtg, NamClipRtg (table 907)
and Clip, HoldTmms (part 7-4 Ed2 Amd1)
The effective logical node namespace: lnNs= IEC 61869-9:2016[A]
sCnf124 Verify for the logical nodes TCTR and TVTR naming;
For the backwards compatible configuration: InnATCTR1, InnBTCTR2, InnCTCTR3, InnNTCTR4,
UnnATVTR1, UnnBTVTR2, UnnCTVTR3, UnnNTVTR4
For the preferred rates: InnpTCTRn and UnnpTVTRn, where nn is a number and p is the phase
(IEC 61869-9:2011, 6.903.7 and 6.903.8)
sCnf125 Verify the sampled value control block:
For backward compatible configuration:
– If name is MSVCB01; smpMod=SmpPerPeriod or absent, smpRate=80, confRev=1, nofASDU=1,
smvID=xxxxMUnn01
– If name is MSVCB02; smpMod=SmpPerPeriod or absent, smpRate=256, confRev=1, nofASDU=8,
smvID=xxxxMUnn02
– Name = MSVCBxx smpMod=SmpPerPeriod or absent, smpRate = 96 (the Japanese variant)
where xx is not 01 nor 02
For preferred rates:
– Name = MSVCBxx, smpMod=SmpPerSec where xx is not 01 nor 02
Verify the SmvOpts (IEC 61869:2011, 6.903.1 and IEC 61850-6: Table 31)
– SmvOpt: sampleSynchronized="true" or absent; refreshTime="false" or absent;
sampleRate="false" or absent; dataSet="false" or absent; security="false" or absent
sCnf126 Verify the SV dataset naming and elements
For backward compatible configuration:
PhsMeas1 Dataset elements as specified in clause 6.903.10
For preferred rates:
PhsMeas2.99 (IEC 61869 6.903.10)
Dataset elements sequence shall be i/q/i/q… and current proceeds voltage if both are present. Where
multiple current or multiple voltage members for a common measurement point exist, they shall be
adjacent and in the sequence: A, AB, B, BC, C, CA, N.
The number of current and voltage elements shall match the number in the variant code currently
under test.
IEC 61850-10:2012/AMD1:2025 © IEC 2025
Test Test case description
case
sCnf127 Verify the AmpSv units, offset and scaleFactor attribute values match 61869-9:2011, Table 904, read-
only and not valImport=T
Verify the VolSv units, offset and scaleFactor attribute values match 61869-9:2011, Table 906, read-
only and not valImport=T
sCnf128 Verify that if the device does not supply all samples for the backwards compatible rate(s), 'dummy'
SAV data attributes might be referenced in the data set. To detect the difference between dummy
and real samples in the SCL, the ICD shall have all LN's included but the ones that are not supported
have the LN Mode preconfigured to "Off".
Condition: a not supported channel
sCnf129 Check if the server "SMVSettings" capabilities in the ICD "services" section does match:
• SamplesPerSec is present
• SmpRate is present
• SecPerSamples is absent
• kdaParticipant / McSecurity is false or absent
• pdcTimeStamp is false or absent
• synchSrcId is absent/false/true (IEC 61850-9-2:2011/AMD1:2020)

6.2.4.5 Data model test cases
The test cases listed in Table 3 shall apply.
Table 3 – Server data model test cases
Test case Test case description
sMdl1 Verify presence of mandatory data objects for each LN type and data attributes for each DO
type. Passed when all objects/attributes are present
sMdl2 Verify presence of conditional presence true data objects for each LN type and data
attributes for each DO type. Passed when all objects/attributes are present
sMdl3 Verify non-presence of conditional presence false data objects for each LN type and data
attributes for each DO type. Passed when these objects/attributes are not present
sMdl4 Verify data model mapping according to applicable SCSM concerning name length and object
expansion. Passed when mapping is according to applicable SCSM
sMdl5 Verify data model mapping according to applicable SCSM concerning organisation of
functional components.
sMdl6 Verify data model mapping according to applicable SCSM concerning naming of control
blocks and logs. Passed when mapping is according to applicable SCSM.
sMdl7 Verify type of all data objects for each LN type and all data attributes for each DO type.
Passed when type of all objects/attributes do match with the IEC 61850-7-3, IEC 61850-7-4
and the applicable SCSM
sMdl8 Verify that the enum types and values from the SCL and in the device are in specified range.
Passed when all enum types and values match the 2007B.nsd.
sMdl9 Check if manufacturer specific data model extensions are implemented according to the
extension rules in IEC 61850-7-1:2010, Clause 14.
sMdl10 Check if the order of the data attributes with the same functional constraint of the DO type
match with IEC 61850-7-3. Passed when all attributes are in matching order
sMdl11 Moved to sCnf50
sMdl12 Check that the rules for multiple data object instantiation are kept (IEC 61850-7-1:2010,14.6,
IEC 61850-7-4)
sMdl13 Moved to sCnf82
sMdl14 Check the correct use of name spaces for non-substation power utility applications like for
example Hydro and DER; Condition: when non-substation name space is used
IEC 61850-10:2012/AMD1:2025 © IEC 2025
Test case Test case description
sMdl15 Check if the SCL configuration file used to configure the DUT corresponds with the actual
data object references, data types, data sets and pre-configured data values (settings)
exposed by the DUT on the network.
sMdl16 Change one parameter/setting with valImport=True of each configurable data type and FC
(FC can be DC, CF or SP) using the SCT SIMULATOR
Change one parameter/setting when valImport=False or absent of each configurable data
type and FC (FC can be DC, CF or SP) using the supplied IED configuration tool
Check the updated online parameter/setting values correspond with the configured values in
the SCL.
Document the tested parameters in the test report.
Condition when a parameter/setting is configurable
sMdl17 Check the "ldName" naming structure when supported. All online object references (including
data sets, control block references and object references – CDC ORG) shall start with the
"LDevice ldName" value instead of the "IED name" + "LDevice inst"
Condition when Services ConfLdName is present
sMdl18 Verify that the indicated trigger option: is conformant with the
IEC 61850-7-3 standardized Trigger Option.
sMdl19 Configure IED attribute name in server resulting in a 64-character MMS domain name for the
longest ldInst and verify online domain name agrees with configuration.
sMdl20 If ICD/IID file contains any valKind=Conf: Verify that online data model does not contain
empty data structures as a result of all contained attributes being valKind=Conf
sMdl21 Modify some LN prefix / instance number in the SCD file, reconfigure the IED and load onto
the IED. Browse the IED data model and check that changes are in,
Condition: when Services ConfLNs fixPrefix=false or fixLnInst=false
sMdl22 Verify that at least one Logical Device has LPHDx.Proxy=false.
Verify each tracking Data Object in LTRK (example: SpcTrk) appears in at most one LTRK
Logical Node in all Logical Devices which have LPHDx.Proxy=false.
For Logical Device with LPHDx.Proxy=true, no tests are required
sMdl23 Modify valKind from Set to RO in the SCD file, reconfigure the IED and load onto the IED.
Browse the IED data model and check that the attributes are readonly.
Condition: when Services ValueHandling setToRO=true, SICS-I211
sMdl24 Import a master clock device in the SCD file, reconfigure the IED and load onto the IED.
Check that the IED synch to the master clock.
Condition: SICS-I24 out-of-scope need clarification
sMdl25 Instantiate 2 new LGOS in the SCD file (IEC 61850-6:2009, Annex G) one from a GOOSE
control block from a logical device with ldName and one without. Reconfigure the IED and
load onto the IED. Browse the IED data model and check that the LGOS is present.
Condition: when Services SupSubscription maxGo>0
sMdl26 Instantiate a new LSVS in the SCD file (IEC TR 61850-6:2016, Annex G) one from a Sampled
Value control block from a logical device with ldName and one without. Reconfigure the IED
and load onto the IED. Browse the IED data model and check that the LSVS is present.
Condition: when Services SupSubscription maxSv>0
sMdl27 Verify that the IED can subscribe to a GOOSE published at the connectedAP of ServerAt
accesspoint of another IED
Condition: when GOOSE subscribe is supported

IEC 61850-10:2012/AMD1:2025 © IEC 2025
6.2.4.6 Mapping of ACSI models and services test cases
Test items shall be grouped together in tables. The tables shall reflect the applicable service
models specified in Figure 3 of IEC 61850-7-2:2010:
– application association (sAss);
– server, Logical device, Logical node, Data, and Data Attribute model (sSrv);
– data set model (sDs);
– service tracking (sTrk);
– substitution model (sSub);
– setting group model (sSg);
– unbuffered report control model (sRp);
– buffered report control model (sBr);
– log control model (sLog);
– generic object oriented substation events (sGop and sGos);
– control model (sCtl);
– time and time synchronisation model (sTm);
– file transfer model (sFt);
– Samples Values publishing (sSvp);
– Samples Values subscribing (sSvs).
Test cases are defined for each ACSI model and services in the following categories:
• positive = verification of normal conditions, typically resulting in response+
• negative = verification of abnormal conditions, typically resulting in response–
A test case is mandatory when the applicable ACSI model and ACSI service is supported by
the DUT. This is specified in the PICS according to IEC 61850-7-2:2010, Annex A. The test
result interpretation (passed/failed) depends on the declared IED capabilities e.g. in the ICD
file as well as on the test result.
6.2.4.7 Application association model
6.2.4.7.1 Positive test cases
The test cases listed in Table 4 shall apply.
Table 4 – Association positive test cases
Test case Test case description
sAss1 Associate and client-release a TPAA association (IEC 61850-7-2:2010, 8.3.2)
sAss2 Associate and client-abort TPAA association (IEC 61850-7-2:2010, 8.3.2)
sAss3 Associate with maximum number of clients simultaneously (PIXIT)
sAss4 Verify the negotiation of MMS initiate parameters
sAss5 Verify the server initiates the Associate

IEC 61850-10:2012/AMD1:2025 © IEC 2025
6.2.4.7.2 Negative test cases
The test cases listed in Table 5 shall apply.
Table 5 – Association negative test cases
Test Test case description
case
sAssN1 Check that with incorrect authentication parameters and authentication turned on at server the
association fails, and with authentication turned off the server associates (IEC 61850-7-2:2010, 8.3)
sAssN2 Check that with incorrect association parameters at server
...