IEC 61400-25-5:2006

INTERNATIONAL IEC
STANDARD 61400-25-5
First edition
2006-12
Wind turbines –
Part 25-5:
Communications for monitoring
and control of wind power plants –
Conformance testing
Reference number
Publication numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series. For example, IEC 34-1 is now referred to as IEC 60034-1.
Consolidated editions
The IEC is now publishing consolidated versions of its publications. For example,
edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the
base publication incorporating amendment 1 and the base publication incorporating
amendments 1 and 2.
Further information on IEC publications
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology. Information relating to
this publication, including its validity, is available in the IEC Catalogue of
publications (see below) in addition to new editions, amendments and corrigenda.
Information on the subjects under consideration and work in progress undertaken
by the technical committee which has prepared this publication, as well as the list
of publications issued, is also available from the following:
• IEC Web Site (www.iec.ch)
• Catalogue of IEC publications
The on-line catalogue on the IEC web site (www.iec.ch/searchpub) enables you to
search by a variety of criteria including text searches, technical committees
and date of publication. On-line information is also available on recently issued
publications, withdrawn and replaced publications, as well as corrigenda.
• IEC Just Published
This summary of recently issued publications (www.iec.ch/online_news/ justpub)
is also available by email. Please contact the Customer Service Centre (see
below) for further information.
• Customer Service Centre
If you have any questions regarding this publication or need further assistance,
please contact the Customer Service Centre:

Email: custserv@iec.ch
Tel: +41 22 919 02 11
Fax: +41 22 919 03 00
INTERNATIONAL IEC
STANDARD 61400-25-5
First edition
2006-12
Wind turbines –
Part 25-5:
Communications for monitoring
and control of wind power plants –
Conformance testing
© IEC 2006 ⎯ Copyright - all rights reserved
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 the publisher.
International Electrotechnical Commission, 3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, Switzerland
Telephone: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale X
International Electrotechnical Commission
МеждународнаяЭлектротехническаяКомиссия
For price, see current catalogue

– 2 – 61400-25-5 © IEC:2006(E)
CONTENTS
FOREWORD.3
INTRODUCTION.5

1 Scope.6
2 Normative references .7
3 Terms and definitions .7
4 Abbreviated terms .10
5 Introduction to conformance testing.11
5.1 General .11
5.2 Conformance test procedures.11
5.3 Quality assurance and testing .12
5.4 Testing .13
5.5 Documentation of conformance test report .15
6 Device related conformance testing.15
6.1 General guidelines .15
6.2 Standard test procedures .17
6.3 Conformance test procedures.17
7 Performance tests .39
7.1 General .39
7.2 Communications latency.40
7.3 Time synchronisation and accuracy.41
7.4 Stability test .43

Annex A (informative) Examples of test procedure template.44

Bibliography.45

Figure 1 – Conceptual communication model of the IEC 61400-25 series .7
Figure 2 – Conceptual conformance assessment process .14
Figure 3 – Conceptual test system architecture.16
Figure 4 – Test procedure format.18
Figure 5 – Performance testing (black box principle).41
Figure 6 – Time synchronisation and accuracy test setup .42

61400-25-5 © IEC:2006(E) – 3 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
WIND TURBINES –
Part 25-5: Communications for monitoring
and control of wind power plants –
Conformance testing
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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
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.
International Standard IEC 61400-25-5 has been prepared by IEC technical committee 88:
Wind turbines.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
The text of this standard is based on the following documents:
FDIS Report on voting
88/277/FDIS 88/283/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
A list of all parts of the IEC 61400 series, under the general title Wind turbines can be found
on the IEC website.
– 4 – 61400-25-5 © IEC:2006(E)
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

61400-25-5 © IEC:2006(E) – 5 –
INTRODUCTION
The IEC 61400-25 series defines communication for monitoring and control of wind power
plants. The modeling approach of the IEC 61400-25 series has been selected to provide
abstract definitions of classes and services such that the specifications are independent of
specific protocol stacks, implementations, and operating systems. The mapping of these
abstract classes and services to a specific communication profile may be found in IEC 61400-
25-4 .
This part of IEC 61400-25 defines the methods and abstract test cases for conformance
testing of devices used in wind power plants. The intended readers are test system
developers.
NOTE 1 It is recommended to obtain a common knowledge of the standards IEC 61400-25-1, IEC 61400-25-2,
IEC 61400-25-3, and IEC 61400-25-4 before reading this part.
NOTE 2 Abbreviations used in IEC 61400-25-5 may be listed in Clause 3 or may be found in other parts of
IEC 61400-25 that are relevant for conformance testing.

—————————
To be published.
– 6 – 61400-25-5 © IEC:2006(E)
WIND TURBINES –
Part 25-5: Communications for monitoring
and control of wind power plants –
Conformance testing
1 Scope
The focus of the IEC 61400-25 series is on the communications between wind power plant
components such as wind turbines and actors such as SCADA Systems. Internal
communication within wind power plant components is outside the scope of the IEC 61400-25
series.
The IEC 61400-25 series is designed for a communication environment supported by a client-
server model. Three areas are defined, that are modelled separately to ensure the scalability
of implementations:
1) wind power plant information models,
2) information exchange model, and
3) mapping of these two models to a standard communication profile.
The wind power plant information model and the information exchange model, viewed
together, constitute an interface between client and server. In this conjunction, the wind
power plant information model serves as an interpretation frame for accessible wind power
plant data. The wind power plant information model is used by the server to offer the client a
uniform, component-oriented view of the wind power plant data. The information exchange
model reflects the whole active functionality of the server. The IEC 61400-25 series enables
connectivity between a heterogeneous combination of client and servers from different
manufacturers and suppliers.
As depicted in Figure 1, the IEC 61400-25 series defines a server with the following aspects:
– Information provided by a wind power plant component, e. g., “wind turbine rotor speed” or
“total power production of a certain time interval” is modelled and made available for
access. The information modelled in the standard is defined in part IEC 61400-25-2,
– services to exchange values of the modelled information defined in part IEC 61400-25-3,
– mapping to a communication profile, providing a protocol stack to carry the exchanged
values from the modelled information (part IEC 61400-25-4).
The IEC 61400-25 series only defines how to model the information, information exchange
and mapping to specific communication protocols. The IEC 61400-25 series excludes a
definition of how and where to implement the communication interface, the application
program interface and implementation recommendations. However, the objective of the IEC
61400-25 series is that the information associated with a single wind power plant component
(such as the wind turbine) is accessible through a corresponding logical device.
This part of IEC 61400-25 specifies standard techniques for testing of conformance of
implementations, as well as specific measurement techniques to be applied when declaring
performance parameters. The use of these techniques will enhance the ability of users to
purchase systems that integrate easily, operate correctly, and support the applications as
intended.
NOTE The role of the test facilities for conformance testing and certifying the results are outside of the scope of
IEC 61400-25-5.
61400-25-5 © IEC:2006(E) – 7 –
Communication model of the IEC 61400-25 series
Client Server
Messaging
Messaging
Information exchange Information exchange
Information exchange through mapping Information exchange
through mapping
model (get, set, report, model (get, set, report,
model (get, set, report, to communication model (get, set, report,
to communication
log, control, publish / log, control, publish /
log, control, publish / profile (Read, log, control, publish /
profile (Read,
subscribe, etc.) subscribe, etc.)
subscribe, etc.) write, . message) subscribe, etc.)
write, . message)
defined in defined in
defined in defined in defined in
defined in
Wind power
Actor IEC 61400-25-3 IEC 61400-25-3
IEC 61400-25-3 IEC 61400-25-4 IEC 61400-25-3
plant
e.g. IEC 61400-25-4
component
SCADA
e.g. wind turbine
Wind power plant Wind power plant
Wind power plant Wind power plant
information model information model
information model information model
(rotor speed, break
defined in
(rotor speed, break
defined in
status, total power
status, total power
IEC 61400-25-2
Application Application
IEC 61400-25-2 production, etc.)
production, etc.)
defined in
defined in
IEC 61400-25-2
IEC 61400-25-2
Outside
Outside
scope
scope
IEC  2172/06
Figure 1 – Conceptual communication model of the IEC 61400-25 series
2 Normative references
The following referenced documents are indispensable for the application 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 61400-25 (all parts), Wind turbines - Part 25: Communications for monitoring and control
of wind power plants
IEC 61850-7-1:2003, Communication networks and systems in substations – Part 7-1: Basic
communication structure for substations and feeder equipment – Principles and models
IEC 61850-7-2:2003, Communication networks and systems in substations – Part 7-2: Basic
communication structure for substations and feeder equipment – Abstract communication
service interface (ACSI)
IEC 61850-7-4:2003, Communication networks and systems in substations – Part 7-4: Basic
communication structure for substations and feeder equipment – Compatible logical node and
data classes
ISO/IEC 9646 (all parts), Information technology – Open Systems Interconnection –
Conformance testing methodology and framework
3 Terms and definitions
For the purpose of this document, the terms and definitions defined in IEC 61400-25-1 and
the following apply.
3.1
Factory Acceptance Test
FAT
customer agreed functional tests of the specifically manufactured substation automation
system or its parts using the parameter set for the planned application.

– 8 – 61400-25-5 © IEC:2006(E)
The FAT shall be carried out in the factory of the manufacturer or other agreed-upon location
by the use of process simulating test equipment
3.2
interoperability
ability of two or more devices from the same vendor (or different vendors) to exchange
information and use that information for correct co-operation. A set of values defined
corresponds with the quantities or values of another set
3.3
Model Implementation Conformance Statement
MICS
details the standard data object model elements supported by the system or device
3.4
negative test
test to verify the correct response of a device or a system when subjected to:
– IEC 61400-25 series conformant information and services which are not implemented in
the device or system under test,
– non IEC 61400-25 series conformant information and services sent to the device or system
under test.
3.5
Protocol Implementation Conformance Statement
PICS
summary of the capabilities of the system to be tested
3.6
Protocol Implementation Extra Information For Testing
PIXIT
the Protocol Implementation eXtra Information for Testing document contains system specific
information regarding the capabilities of the system to be tested and which are outside the
scope of the IEC 61400-25 series
NOTE The PIXIT is not subject to standardisation.
3.7
routine test
performed by the manufacturer in order to ensure device operation and safety
3.8
Site Acceptance Test
SAT
verification of each data and control point and the correct functionality within the WPP and its
operating environment at the whole installed plant by use of the final parameter set. The SAT
is the precondition for the WPP being put into operation.
3.9
system test
verification of correct behaviour of the WPP components and of the overall WPP under
various application conditions
NOTE The system test marks the final stage of the development of a WPP system component.

61400-25-5 © IEC:2006(E) – 9 –
3.10
test equipment
all tools and instruments which simulate and verify the input/outputs of the operating
environment of the WPP such as wind turbine, switchgear, transformers, network control
centres or connected telecommunication units on the one side, and the communication links
between the system components of the WPP on the other
3.11
test facility
organisation able to provide appropriate test equipment and trained staff for conformance
testing
NOTE The management of conformance tests and the resulting information should follow a quality system.
3.12
type test
verification of correct behaviour of the systems components of the WPP by use of the system
tested software under the test conditions corresponding with the technical data
NOTE The type test marks the final stage of the hardware development and is the precondition for the start of the
production. This test shall be carried out with system components which have been manufactured through the
normal production cycle.
3.13
witness point
point, defined in the appropriate document at which an inspection will take place on an
activity. The activity may proceed without the approval of the initiator of the conformance test.
The test facility provides a written notice to the initiator at an agreed time prior to the witness
point. The initiator or his representative has the right, but is NOT obligated, to verify the
witness point
– 10 – 61400-25-5 © IEC:2006(E)
4 Abbreviated terms
ACSI Abstract Communication Service Interface
BRCB Buffered Report Control Block
DUT Device Under Test
FAT Factory Acceptance Test
GI General Interrogation
HMI Human Machine Interface
IED Intelligent Electronic Device
IP Inter-networking protocol internet Protocol
LCB Log Control Block
LD Logical Device
LN Logical Node
MICS Model Implementation Conformance Statement
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
RCB Report Control Block
RTU Remote Terminal Unit
SAT Site Acceptance Test
SCADA Supervisory Control And Data Acquisition
SCSM Specific Communication Service Mapping
SoE Sequence-of-Events
SUT System Under Test
TPAA Two Party Application Association
URCB Unbuffered Report Control Block
UTC Coordinated Universal Time
WPP Wind Power Plant
61400-25-5 © IEC:2006(E) – 11 –
5 Introduction to conformance testing
5.1 General
There are many steps involved from the development and production of a device to the proper
running of a complete system designed according the specific needs of a customer. Suitable
test steps are incorporated in this process.
Many internal tests during the development of a device (or a system kit) result in a type test
(unit level test) performed at least by the provider and – if required by applicable standards –
by an independent test authority. In the context of this part of the IEC 61400-25 series, the
term type test is restricted to the functional behaviour of the device excluding communication.
Continuing routine tests in the production chain are necessary to ensure a constant quality of
delivered devices in accordance with the quality procedures of the producer.
A conformance test is the type test for communication and – since communication establishes
a system – the basic integrated systems test of the incorporated system components. As a
global communications standard, the IEC 61400-25 series includes standardised conformance
tests to insure that all suppliers comply with applicable requirements.
Type tests and conformance tests do not completely guarantee that all functional and
performance requirements are met. However, when properly performed, such tests
significantly reduce the risk of costly problems occurring during system integration in the
factory and on-site.
Conformance testing does not replace project specific system tests such as the FAT and SAT.
The FAT and SAT are based on customer requirements for a dedicated WPP system and are
done by the system integrator and normally witnessed by the customer. These tests increase
the confidence level that all potential problems in the system have been identified and solved.
These tests establish that the delivered WPP system is performing as specified.
5.2 Conformance test procedures
In general, conformance testing of the communication behaviour of a system component
should address the functional requirements and performance requirements of typical
applications supported by these devices in a WPP.
Conformance testing demonstrates the capability of the Device Under Test (DUT) to operate
with other system components in a specified way according to the IEC 61400-25 series.
Conformance testing requires consideration of the following issues:
– The problem of all testing is the completeness of the tests. The number of all possible
situations can be very large. It may be possible to cover all normal operating cases, but
this may not be true for all failure cases.
– It is impossible to test all system configurations using system components from different
world-wide suppliers. Therefore, standardised test architecture with device simulators
should be used. The use of such test architecture implies agreement about its
configuration and the test procedures applied in order to achieve compatible results.
– A communication standard does not standardise the functions of the communicating
equipment. Therefore, the failure modes of the functions are outside the scope of this part
of the IEC 61400-25 series. But both the existence of distributed functions and the impact
of function response in devices on the data flow, create some interdependence.
– Depending on the definition range of the IEC 61400-25 series, some properties of the
device may be proven by information and documents provided with the DUT for the
conformance testing instead of the conformance test itself.

– 12 – 61400-25-5 © IEC:2006(E)
The conformance test establishes that the communication of the DUT works according the
IEC 61400-25 series.
Since the IEC 61400-25 series defines no new communication stacks, the conformance to all
seven ISO/OSI layers may be proven by documentation that communication stack software
compliant with the corresponding specifications is implemented and may have been pre-
tested and optionally certified. In the standard conformance test, only the application
according to ACSI can be tested.
5.3 Quality assurance and testing
5.3.1 General
In order to assure the quality during conformance testing, a quality assurance system has to
be in place.
In general, quality surveillance is used to monitor and verify the status of components during
all phases of the conformance tests. For this purpose, inspections are carried out, based on
hold and witness points that are indicated by the initiator or its representative in the test and
the inspection plan that is supplied by the test facility. These inspections are process related
and will provide information and confidence on the quality of the tests. Quality surveillance
will reduce the risks of failure during the FAT and SAT.
5.3.2 Quality plan
5.3.2.1 Conformance test quality plan
The test facility will supply, for evaluation, a quality plan for the conformance test.
The plan shall describe all measures for the scope of work and/or deliveries in the areas of
organisation, time, information and quality. There is only one plan for the test facility and its
sub-suppliers.
The conformance test quality plan is proposed to contain the following:
– A complete and detailed description of the work methods. This will help insure that all
verifiable activities will fulfil all applicable requirements and conditions as stated in the
scope of work during the time allowed.
– A detailed description of all tasks to be performed, including references to the schedule,
an overview of the involved staff, materials and work methods as well as relevant methods
and procedures.
– A detailed description of the organisation, including the assignments, tasks and
responsibilities of mentioned staff during the different stages of the test programs. The
description shall include all tests, inspections, research and audits during the various
stages of the tests and the dates on which they will take place. These descriptions will be
part of the test and inspection plan.
– A method for handling deviations, changes and modifications during all stages of the test.
– A sign off procedure and a description of the documentation to be supplied.
5.3.2.2 Test and inspection plan
The conformance test quality plan shall contain a test and inspection plan. In this plan, the
test facility specifies, for all phases of the tests:
– what will be inspected, tested and registered;
– the purpose of the inspections and tests;
– the procedures and standards to which inspections, tests and registrations will be
performed;
61400-25-5 © IEC:2006(E) – 13 –
– the expected results of the inspections and tests;
– identification of persons to perform the inspections, tests and registrations.
The test facility is responsible for the correct and timely performance of all activities
mentioned in the test and inspection plan.
The test facility will include a proposal for so called hold, witness and review points in the test
and inspection plan.
There are several methods to perform a hold or witness point. The initiator of the
conformance test or a representative can be present during the execution of a test or
inspection. It is also possible to review the associated quality documents, e.g. checklists,
verification and validation documents. This review can take place at the test facilities site
during the execution of a test or inspection can be made at the initiator’s site.
All hold and witness points will be announced by the test facility at least a predefined time
before they take place. A period of at least one week is recommended, depending on the time
needed for making travel arrangements and the availability of the needed resources.
The initiator of a conformance test has the right to conduct audits on the quality system of the
test facility and its sub-suppliers. The test facility shall co-operate and provide access to all
locations applicable for the conformance test. The initiator’s right to check the quality of the
conformance test does not dismiss the test facility from its responsibilities.
Inspections and tests by the initiator of a conformance test shall be possible at mutually
agreeable times at the locations, offices and factories of the test facility and all applicable
third parties and sub-suppliers.
5.4 Testing
5.4.1 General
Conformance testing shall be customised for each device under test based on the capabilities
identified in the PICS, PIXIT and MICS provided by the vendor. When submitting devices for
testing, the following shall be provided:
– device for testing;
– Protocol Implementation Conformance Statement (PICS);
– Protocol Implementation eXtra Information for Testing (PIXIT) statement;
– Model Implementation Conformance Statement (MICS);
– instruction manuals detailing the installation and operation of the device.
The requirements for conformance testing fall into two categories:
a) static conformance requirements (define the requirements the implementation shall fulfil);
b) dynamic conformance requirements (define the requirements that arise from the protocol
used for a certain implementation).
The static and dynamic conformance requirements shall be defined in a Protocol
Implementation Conformance Statement or PICS. The PICS serves three purposes:
1) selection of the appropriate set of tests;
2) ensure that the tests appropriate to a claim of conformance are performed;
3) provide the basis for the review of the static conformance.
Concrete PICS shall be as defined for the SCSMs.

– 14 – 61400-25-5 © IEC:2006(E)
A Model Implementation Conformance Statement or MICS shall be provided detailing the
standard data object model elements supported by the system or device.
In addition to the PICS, a PIXIT document shall be provided.
The process of assessing the conformance is shown in Figure 2.

Start
Static
conformance
requirements
PICS
Static
conformance
Dynamic
review
MICS
conformance
requirements
Conformance
Selection
PIXIT test suite
and
parameterisation
Dynamic tests
_________________________
Basic Interconnection testing
Capability testing
Behaviour testing
Analysis of results
Final conformance review
Synthesis and conclusion
Test report production
Control flow
End
Data flow
IEC  2194/06
Figure 2 – Conceptual conformance assessment process
5.4.2 Device testing
A single device shall be conformance tested against a single test device.
The device specific conformance tests contain the positive and negative testing of the
following as appropriate:
– inspection of the documentation and version control of the device,
– test of device configuration file against the device related object model (IEC 61400-25-2),
– test of communication stack implementation against applicable SCSM (IEC 61400-25-4),
– test of implemented ACSI services against ACSI definition (IEC 61400-25-3),

61400-25-5 © IEC:2006(E) – 15 –
– test of device specific extensions according to rules given by the IEC 61400-25 series in
general.
5.5 Documentation of conformance test report
A conformance test report shall include the following information:
– A reference list of all documents that describe or specify any qualifying tests that have
been performed. These documents may include the vendor's standard operating and
testing procedures, and local, national and international standards. International standards
shall be cited by document number, date, Clause and Sub clauses. References to other
documents shall include a complete source address and document identification. A
complete and contextually accurate summary or extract of the document may be included
for convenience.
– A list of any specialised test equipment or computer programs used for performing the
conformance tests.
– Name and address of the vendor.
– Name and address of the initiator of the conformance test (if different from vendor name).
– Name of the tested device.
– All of the variants (hardware, firmware, etc.) of tested device.
– Name and address of the test facility.
– Date of issue of test report.
– Name and signature of the tester.
– Unique reference number.
– A list of test items performed to verify conformance.
– Comments and problems found.
– For each test item, the following subjects shall be documented:
• description of the test item with the objective of the test, the test procedure and the
expected result;
• reference to the IEC 61400-25 series part, chapter and paragraph;
• unique identifier per test item;
• test result: passed, failed, inconclusive, not applicable;
• comparison of the test result to the expected result.
Changes or alterations to the device made at any point in the test, particularly those made to
correct a test deficiency, shall be completely described.
Conformance test documentation shall be supplied to the initiator.
6 Device related conformance testing
6.1 General guidelines
6.1.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.

– 16 – 61400-25-5 © IEC:2006(E)
Special attention shall be given to communication equipment such as star-couplers, switches,
etc., which shall support all requested features of the IEC 61400-25 series but not introduce
additional contingencies and limitations.
The impact of the communication method (client-server, FTP/IP etc.) used by the device
under test shall be considered properly in the test procedures. Verification of functional
applications is not part of a conformance test even if advanced tools may offer such analysis.
6.1.2 Test system architectures
In order to be able to perform a device test, a minimum test set-up is necessary (see Figure
3). Beside the DUT, a device (for example, a simulator) which acts as a client and server is
required to initiate and generate messages and record and process resulting information.
Background load on the network may be provided by an additional load simulator, which may
also contain a master for time synchronisation (the time sync master). An optional HMI on the
network may be used for independent monitoring of the test system. The optional HMI may
include a network monitoring facility and the engineering software on a system and device
level. Network analyzers shall be used to monitor the system for errors during testing.

IEC  2195/06
Figure 3 – Conceptual test system architecture
In the case of testing devices with client-server roles, the test system shall provide connection
points for server devices, for client devices and for devices acting as both.
The test system shall include documentation regarding the following points:
– test configuration of the test system hardware;
– test configuration of the test system software;
– test simulator or background load simulator or time sync master.

61400-25-5 © IEC:2006(E) – 17 –
6.2 Standard test procedures
6.2.1 Inspection of documentation and version control of the device
The following issues shall be addressed during the test:
– PICS,
– version control, and
– vendor documentation.
6.2.2 Test of basic system related communication functions
The following issues shall be addressed during the test:
– clock synchronisation;
– time stamping;
– loss of communication.
6.3 Conformance test procedures
6.3.1 General
This Subclause describes the test procedure requirements, test structure, the test cases
(what is to be tested) and the format and a few examples of test procedures (how it is to be
tested).
6.3.2 Test procedure requirements
The test procedure requirements are:
– The test cases describe what shall be tested; the 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.
– 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).

– 18 – 61400-25-5 © IEC:2006(E)
– 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 4. With this format, the test
procedures document can also be used as test report. A few test procedure examples are
depicted in Annex A.
Test purpose, e.g. 'Test if
Test reference:
correctly'
model>

e.g. RptP3
Test result
References to the
IEC 61400-25 … Passed
documents and
Failed
paragraph … Inconclusive
Expected result
Definition of the expected
behavior after a step
Test description
Step by step description of
how to perform the test
Comment
Area for comments during testing,

e.g. problems found and remarks

IEC  2196/06
Figure 4 – Test procedure format
6.3.3 Test structure
The server test cases are structured as follows:
a) Documentation and version control (IEC 61400-25-5).
b) Data model (IEC 61400-25-2).
c) Mapping of ACSI models and services (IEC 61400-25-3); the corresponding sub clauses
that define the abstract test cases are given in brackets:
– application association ( 6.3.4.5)
– server, logical device, logical node, and data model ( 6.3.4.6)
– data set ( 6.3.4.3)
– reporting ( 6.3.4.7)
– logging ( 6.3.4.9)
– control ( 6.3.4.10)
– time and time synchronization ( 6.3.4.11)
6.3.4 Test cases to test a server
6.3.4.1 General
This part of the IEC 61400-25-5 series specifies abstract test cases (see 6.3.4.5 to 6.3.4.12).
The abstract test cases shall be used for the definition of concrete test cases to run in tests.

61400-25-5 © IEC:2006(E) – 19 –
NOTE 1 The concrete syntax of test cases depends on the test system environment, i.e., mainly on the test script
language. The concrete test cases are to be provided by test facilities agreed upon by the market participants.
NOTE 2 The server tests may require a base load generator. The definition of base load is beyond the scope of
this part of the IEC 61400-25 series.
6.3.4.2 Documentation and version control test procedure overview
Check if the manufacturer’s PICS, MICS and PIXIT documentation and hardware and software
versions of the DUT match (IEC 61400-25-4).
6.3.4.3 Data model test cases
The data model test cases shall:
– verify presence of mandatory objects for each LN (presence = M, optional = O),
– verify non-presence of conditional presence false objects,
– verify data type of all objects for each LN,
– verify data attribute values from the device are in specified range (this is a continuous
effort during the whole conformance test).
The test result is a list of object references with data type, common data class, data attribute
type, M/O presence indication (from IEC 61400-25-2).
The data model extensions shall be checked according to the standardised extension rules
including the use of namespaces. The manufacturer-specific data model extensions shall be
documented. To enable this, the MICS shall include definitions of the specific logical nodes,
common data classes and data attribute types in the same format as IEC 61400-25-2.
The data model mapping shall be verified:
– verify name length and object expansion;
– verify the organisation of functional components;
– verify the naming of control blocks and logs.
6.3.4.4 Mapping of ACSI models and services test cases
Test items shall be grouped together in tables. The tables shall reflect the services specified
in IEC 61400-25-3:
– Application association (Ass);
– Server, Logical device, Logical node, Data, and Data Attribute model (Srv);
– Report control model (Rpt);
– Log control model (Log);
– Control model (Ctl);
– Time and time synchronisation model (Tm).
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, Annex A.

– 20 – 61400-25-5 © IEC:2006(E)
6.3.4.5 Application association
6.3.4.5.1 Positive
Test case Test case description
S_Ass1 Associate and release a TPAA association (IEC 61850-7-2, 7.4).
S_Ass2 Associate and client-abort TPAA association (IEC 61
...