383-0-1 2006-0045 Projektnr IEC 61400 25 4 Ed 1 0

DKE Deutsche Kommission
Elektrotechnik Elektronik Informationstechnik

im DIN und VDE
Deutsches Mitglied in IEC und CENELEC
VDE – DKE · Stresemannallee 15 · 60596 Frankfurt am Main
383.0.1_2006-0045
An die
im Verteiler genannten Rundschreiben Nr. 383_2006-0081
Damen und Herren
Frankfurt am Main 2006-12-05

Unser Zeichen 1/383 bg/vr
Durchwahl + 49 69 6308-226
E-Mail arno.bergmann@vde.com
Parallele Umfrage
IEC-Schriftstück Projektnr: IEC 61400-25-4 Ed.1.0
IEC 88/288/CDV
"IEC 61400-25-4 Ed.1: Wind turbines - Part 25-4: Communications for monitoring
and control of wind power plants - Mapping to communication profile"
Sehr geehrte Damen und Herren,
als Anlage übersenden wir Ihnen das im Betreff genannte, in der Parallelen Umfrage erschienene IEC-Schrift-
stück, zu dem das Central Office der IEC und das Central Secretariat von CENELEC um Stellungnahme bis
zum 2007-05-04 gebeten haben.
Bitte teilen Sie Ihre Kommentare und Änderungswünsche unter Verwendung des Formulars DKEF08C.Doc bis
spätestens 2007-04-06 dem Deutschen Sprecher
Herrn
Dipl.-Ing. Christian Nath
Germanischer Lloyd Industrial Services GmbH Wind Energie
Steinhöft 9
20459 Hamburg
Telefon: 040 31106-480
E-Mail: christian.nath@gl-group.com
in englischer Sprache mit.
Den Deutschen Sprecher bitten wir bis spätestens 2007-04-20 jeweils um Mitteilung, wie die Umfrageformulare
zum CDV und zur prEN zu beantworten sind. Für eine Ablehnung des CDV/ der prEN ist eine Begründung
erforderlich. Die Stellungnahme bitten wir unter Verwendung des Formulars DKEF08C.Doc möglichst über
E-Mail zur Verfügung zu stellen.
Hinweis: Das Formular DKEF08C.Doc kann von der DKE-Homepage www.dke.de unter der Adresse:
"http://www.dke.de/IEC-CLC-Stellungnahme" heruntergeladen werden.
Mit freundlichen Grüßen
DKE Deutsche Kommission
Elektrotechnik Elektronik Informationstechnik
im DIN und VDE
Referat K 383
für Herrn Arno Bergmann
gez. Verena Rupps, Sekretärin
Anlage Verteiler: umseitig
Stresemannallee 15; 60596 Frankfurt am Main; Telefon: +49 69 6308-0; Telefax: +49 69 6312925
E-Mail: dke@vde.com Internet: http://www.dke.de
-2- 383_2006-0081
383_2006-0081 -3-
Verteiler K 383 Windenergieanlagen (Stand: 2006-12-05)

Mitarbeiter:
Hofmann, Dr. E.ON Netz Bayreuth
Jepsen ENERCON Aurich.................................. .. P
Köhne WINDTEST KWK Kaiser-Wilhelm-Koog
Korzeniewski TÜV NORD Hamburg
Kröning (stv. Obmann) DEWI-OCC Cuxhaven
Meesenburg AN Windenergie Bremen
Nath (Obmann) Germ. Lloyd WindEnergie Hamburg
Pechoc BGFE Köln
Rees aerodyn Rendsburg
Seifert, Prof. Hochschule Bremerhaven
von Mutius REpower Systems Rendsburg
Referent:
Bergmann DKE Frankfurt am Main
Gäste:
Birkl Dehn + Söhne Neumarkt
Brokopf, Dr. Germ. Lloyd WindEnergie Hamburg
Gregorius Ingenieurbüro Kempen
Hahn ISET Kassel
Jaquemotte ENERCON Aurich
Klug, Dr. Gerrad Hassan Oldenburg
Kornprobst NALS im DIN Berlin
Neumann, Dr. DEWI Wilhelmshaven
Öhlbüttel BV WindEnergie Osnabrück
Runkel DeWind Lübeck
Schubert Nordex Energy Norderstedt
Söker DEWI Wilhelmshaven
Weis, Prof. Dr. Adolf Schuch Worms................................. .. P
Wensky ABB Mannheim
Wöste GE Wind Energy Salzberger
Wüstenberg WIND-consult Bargeshagen
Zur Kenntnis:
FGH Mannheim
Adam natcon7 Norderstedt
Erling ZVEI Frankfurt am Main
Häusler, Frau DIBt Berlin
Holtel GE Wind Energy Salzbergen
Reeder FGW Kiel
Rixius FNL Berlin
Schiel VDMA Berlin
Schwarz SCC Schwarz Karlsruhe
Vogl, Frau DKE Frankfurt am Main............. 2
Erläuterung der Kennziffern:

1: nur Einladungen, 2: nur Ergebnisberichte, 3: nur Einladungen und Ergebnisberichte
-4- 383_2006-0081
Verteiler AK 383.0.1 Kommunikation für Windenergieanlagen (Stand: 2006-12-05)

Mitarbeiter:
Adam natcon7 Norderstedt
Berger Ostwind technic Bockelwitz
Bohlen ENERCON Aurich
Bosch skytron Berlin
Czybik, Dr. AREVA Energietechnik Frankfurt am Main
Ehlers, Dr. REpower Systems Rendsburg
Fischer, Dr. ENERCON Aurich
Giebhardt ISET Kassel
Hantschel E.ON Gelsenkirchen
Harden REpower System Rendsburg
Hartung REpower Systems Rendsburg
Heckel Siemens Nürnberg
Hellack GHF Herzogenrath
Heseding NAM Frankfurt am Main
Huhn, Dr. Suzlon Energy Rostock
Kaib Kisters Thedinghausen
Klemm Phoenix Contact Blomberg
Luppa VA TECH SAT Dortmund
März MCC Dortmund
Maschka AMA Pforzheim
Meesenburg AN Windenergie Bremen
Müller DeWind Lübeck
Muuß Germ. Lloyd WindEnergie Hamburg
Nestle ISET Kassel
Oertel µ-sen Mikrosystemtechnik Rudolfstadt
Orth ABB Mannheim
Packard Ostwind technic Bockelwitz
Paetzke Nordex Norderstedt
Patz, Dr. Softing Haar
Reeder FGW Kiel
Reichenbächer SMA Niestetal
Runkel DeWind Lübeck
Saß ENERTRAG Dauerthal
Schloegl ISET Kassel
Schubert Nordex Energy Norderstedt
Schwarz (Obmann) SCC Schwarz Karlsruhe
Vaehsen DMT Essen
Wensky ABB Mannheim
Wöste GE Wind Energy Salzberger
Ziehmann Ing.-Büro Hamburg
Zöllner, Dr. IGUS Dresden
Referent:
Bergmann DKE Frankfurt am Main
88/288/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJET DE COMITÉ POUR VOTE (CDV)
Project number IEC 61400-25-4 Ed.1

Numéro de projet
IEC/TC or SC: TC 88 Secretariat / Secrétariat
CEI/CE ou SC: Netherlands
Submitted for parallel voting in Date of circulation Closing date for voting (Voting
CENELEC Date de diffusion mandatory for P-members)
2006-12-01 Date de clôture du vote (Vote
Soumis au vote parallèle au obligatoire pour les membres (P))
CENELEC 2007-05-04
Also of interest to the following committees Supersedes document
Intéresse également les comités suivants Remplace le document
88/287/NP (See note)
Functions concerned
Fonctions concernées
Safety EMC Environment Quality assurance
Sécurité CEM Environnement Assurance qualité
CE DOCUMENT EST TOUJOURS À L'ÉTUDE ET SUSCEPTIBLE DE THIS DOCUMENT IS STILL UNDER STUDY AND SUBJECT TO CHANGE. IT
MODIFICATION. IL NE PEUT SERVIR DE RÉFÉRENCE. SHOULD NOT BE USED FOR REFERENCE PURPOSES.
LES RÉCIPIENDAIRES DU PRÉSENT DOCUMENT SONT INVITÉS À RECIPIENTS OF THIS DOCUMENT ARE INVITED TO SUBMIT, W ITH THEIR
PRÉSENTER, AVEC LEURS OBSERVATIONS, LA NOTIFICATION DES COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF
DROITS DE PROPRIÉTÉ DONT ILS AURAIENT ÉVENTUELLEMENT WHICH THEY ARE AW ARE AND TO PROVIDE SUPPORTING
CONNAISSANCE ET À FOURNIR UNE DOCUMENTATION EXPLICATIVE. DOCUMENTATION.
Title : IEC 61400-25-4 Ed.1: Wind turbines - Part 25-4: Communications for monitoring and
control of wind power plants - Mapping to communication profile
Introductory note: This CDV is circulated in parallel with the NP, see 88/287/NP
ATTENTION ATTENTION
VOTE PARALLÈLE IEC – CENELEC
CEI – CENELEC PARALLEL VOTING
L’attention des Comités nationaux de la CEI, membres du The attention of IEC National Committees, members of
CENELEC, est attirée sur le fait que ce projet de comité CENELEC, is drawn to the fact that this Committee Draft for
pour vote (CDV) de Norme internationale est soumis au Vote (CDV) for an International Standard is submitted for
vote parallèle. parallel voting.
Un bulletin de vote séparé pour le vote CENELEC leur sera A separate form for CENELEC voting will be sent to them by
envoyé par le Secrétariat Central du CENELEC. the CENELEC Central Secretariat.
Copyright © 2006 International Electrotechnical Commission, IEC. All rights reserved. It is

permitted to download this electronic file, to make a copy and to print out the content for the sole
purpose of preparing National Committee positions. You may not copy or "mirror" the file or
printed version of the document, or any part of it, for any other purpose without permission in
writing from IEC.
FORM CDV (IEC) 2005-09-23

2CDV for 61400-25-4 © IEC:2007 -2- 88/288/CDV
1
2
3
4 WIND TURBINES
5 Part 25-4:
6 Communications for monitoring and control of wind power plants –
7 Mapping to communication profile
8
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26 Version: 61400-25-4_R1-0_2CDV_2006-11-16
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 -3- 88/288/CDV
2 CONTENTS
3 FOREWORD.................................................................................................................... - 11 -
4 INTRODUCTION.............................................................................................................. - 13 -
5 1 Scope ........................................................................................................................ - 14 -
6 2 Normative references ................................................................................................ - 16 -
7 3 Terms and definitions ................................................................................................ - 17 -
8 4 Abbreviated terms ..................................................................................................... - 22 -
9 5 General Introduction .................................................................................................. - 23 -
10 5.1 Mapping to protocol stacks. .............................................................................. - 24 -
11 5.2 Services of IEC 61400-25-3 mapped to protocol stacks .................................... - 24 -
12 Annex A (normative) Specific communication service mapping – Mapping to
13 WebService ............................................................................................................... - 26 -
14 A.1 General ..................................................................................................................... - 26 -
15 A.1.1 Introduction .......................................................................................... - 26 -
16 A.1.2 Scope - 26 -
17 A.1.3 The mapping architecture ..................................................................... - 26 -
18 A.2 Specific normative references for Web Services ........................................................ - 29 -
19 A.3 Abbreviated terms ..................................................................................................... - 30 -
20 A.4 Mapping of the IEC 61400-25 Information Model to Web Services ............................. - 30 -
21 A.4.1 Introduction .......................................................................................... - 30 -
22 A.4.2 SERVER class...................................................................................... - 33 -
23 A.4.3 LOGICAL-DEVICE class ....................................................................... - 33 -
24 A.4.4 LOGICAL-NODE class .......................................................................... - 34 -
25 A.4.5 DATA class .......................................................................................... - 34 -
26 A.4.6 DATA-SET class ................................................................................... - 34 -
27 A.4.7 DATA ATTRIBUTE definition ................................................................ - 34 -
28 A.4.8 DAType class ....................................................................................... - 35 -
29 A.4.9 REPORT-CONTROL-BLOCK class ....................................................... - 35 -
30 A.4.10 BUFFERED-REPORT-CONTROL-BLOCK Class (BRCB) ...................... - 35 -
31 A.4.11 UNBUFFERED-REPORT-CONTROL-BLOCK Class (URCB) ................. - 36 -
32 A.4.12 LOG-CONTROL-BLOCK class (LCB) .................................................... - 36 -
33 A.4.13 LOG class ........................................................................................... - 37 -
34 A.5 Mapping of the Information Exchange Model to Web Services ................................... - 37 -
35 A.5.1 SERVER class service mapping ........................................................... - 37 -
36 A.5.2 LOGICAL-DEVICE class service mapping............................................. - 43 -
37 A.5.3 LOGICAL-NODE class services mapping .............................................. - 45 -
38 A.5.4 DATA class services mapping .............................................................. - 46 -
39 A.5.5 DATA-SET class services mapping....................................................... - 51 -
40 A.5.6 REPORT-CONTROL-BLOCK (RCB) class services mapping ................ - 57 -
41 A.5.7 LOG-CONTROL-BLOCK (LCB)class services mapping ......................... - 69 -
42 A.5.8 LOG class services mapping ................................................................ - 71 -
43 A.5.9 CONTROL class services mapping ....................................................... - 74 -
44 A.6 Protocol stack details ................................................................................................ - 81 -
45 A.7 The WSDL specification for the mapping to Web Services ......................................... - 82 -
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 -4- 88/288/CDV
1 Annex B (normative) Specific communication service mapping – Mapping to OPC

2 XML-DA................................................................................................................... - 118 -
3 B.1 General ................................................................................................................... - 118 -
4 B.1.1 Introduction ........................................................................................ - 118 -
5 B.1.2 Scope - 118 -
6 B.1.3 The mapping architecture ................................................................... - 118 -
7 B.2 Specific normative references for OPC XML-DA mapping ........................................ - 120 -
8 B.3 Abbreviated terms ................................................................................................... - 121 -
9 B.4 Mapping of the IEC 61400-25 Information Model to OPC XML-DA ........................... - 121 -
10 B.4.1 Mapping of IEC 61400-25-2 Information Model classes to OPC XML-
11 DA - 121 -
12 B.4.2 Server - 122 -
13 B.4.3 Logical Device .................................................................................... - 122 -
14 B.4.4 Logical Node ...................................................................................... - 122 -
15 B.4.5 Data - 123 -
16 B.4.6 DataAttributeType............................................................................... - 123 -
17 B.5 Mapping of the Information Exchange Model to OPC XML-DA services ................... - 128 -
18 B.5.1 Association model (informative) .......................................................... - 128 -
19 B.5.2 Server class model ............................................................................. - 131 -
20 B.5.3 Logical device class model ................................................................. - 133 -
21 B.5.4 Logical node class model ................................................................... - 134 -
22 B.5.5 Data class model ................................................................................ - 136 -
23 B.5.6 Data set class model ( informative ) .................................................... - 144 -
24 B.5.7 Report class model ............................................................................. - 147 -
25 B.5.8 Control model ..................................................................................... - 152 -
26 B.6 Protocol stack details. ............................................................................................. - 161 -
27 Annex C (normative) Specific communication service mapping – Mapping to ISO 9506
28 specified in IEC 61850-8-1 ...................................................................................... - 163 -
29 C.1 General ................................................................................................................... - 163 -
30 C.1.1 Introduction ........................................................................................ - 163 -
31 C.1.2 Scope - 163 -
32 C.1.3 The mapping architecture ................................................................... - 163 -
33 C.2 Normative references for Annex C ........................................................................... - 165 -
34 C.3 Abbreviated terms for Annex C ................................................................................ - 166 -
35 C.4 Mapping of the IEC 61400-25 Information Model to ISO 9506 as specified in IEC
36 61850-8-1................................................................................................................ - 166 -
37 C.5 Mapping of the extended Information Exchange Model to ISO 9506 ........................ - 167 -
38 C.5.1 General - 167 -
39 C.5.2 AddSubscription ................................................................................. - 167 -
40 C.5.3 RemoveSubscription........................................................................... - 169 -
41 C.5.4 Extended Logging services ................................................................. - 170 -
42 C.6 Protocol stack details .............................................................................................. - 171 -
43 C.6.2 A-Profile - 171 -
44 C.6.3 TCP/IP T-Profile ................................................................................. - 172 -
45 Annex D (normative) Specific communication service mapping – Mapping to IEC
46 60870-5-104 ............................................................................................................ - 173 -
47 D.1 General ................................................................................................................... - 173 -
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 -5- 88/288/CDV
1 D.1.1 Introduction ........................................................................................ - 173 -

2 D.1.2 Scope - 173 -
3 D.1.3 The mapping architecture ................................................................... - 173 -
4 D.2 Normative references for IEC 60870-5-104 .............................................................. - 176 -
5 D.3 Abbreviated terms ................................................................................................... - 176 -
6 D.4 Mapping of IEC 61400-25 Information Model to IEC 60870-5-104 ............................ - 177 -
7 D.4.1 Introduction ........................................................................................ - 177 -
8 D.4.2 Logical Device IM class mapping ........................................................ - 178 -
9 D.4.3 Logical Node IM class mapping ......................................................... - 179 -
10 D.4.4 Mapping of the Common Data Classes (CDC) .................................... - 179 -
11 D.5 Mapping of the Information Exchange Model to IEC 60870-5-104 services .............. - 194 -
12 D.5.1 List of service models and corresponding mappings ........................... - 194 -
13 D.5.2 Server class mapping ......................................................................... - 196 -
14 D.5.3 Association class mapping.................................................................. - 196 -
15 D.5.4 Logical Node class mapping ............................................................... - 196 -
16 D.5.5 Data class mapping ............................................................................ - 197 -
17 D.5.6 Report Control Block class mapping ................................................... - 197 -
18 D.5.7 Control class mapping ........................................................................ - 197 -
19 D.6 Protocol stack selections for IEC 60870-5-104. (Protocol stack details) ................... - 199 -
20 D.6.1 General - 199 -
21 D.6.2 IEC 60870-5-104 Interoperability ........................................................ - 199 -
22 D.6.3 Redundancy / Redundant connections ................................................ - 208 -
23 D.7 Signal mapping List ................................................................................................. - 210 -
24 D.7.1 Signal mapping list schema definition ................................................. - 210 -
25 D.7.2 Signal Mapping List schema definition ................................................ - 211 -
26 D.7.3 SML file example ................................................................................ - 215 -
27 Annex E (normative) Specific communication service mapping – Mapping to DNP3 ..... - 220 -
28 E.1 General ................................................................................................................... - 220 -
29 E.1.1 Introduction ........................................................................................ - 220 -
30 E.1.2 Scope - 220 -
31 E.1.3 The mapping architecture ................................................................... - 220 -
32 E.2 Normative references for DNP3 services ................................................................. - 223 -
33 E.3 Abbreviated terms ................................................................................................... - 223 -
34 E.4 Mapping of the IEC 61400-25 Information Model to DNP3 ....................................... - 224 -
35 E.4.1 Relationship of Common Data Class and Data Set Prototypes ............ - 224 -
36 E.4.2 Relationship of Quality Mapping to SQ2.............................................. - 224 -
37 E.4.3 CDC Measured Value (MV)................................................................. - 224 -
38 E.4.4 CDC Setpoint Parameter Value (SPV) ................................................ - 225 -
39 E.4.5 CDC Status Value (STV) .................................................................... - 226 -
40 E.4.6 CDC Alarm (ALM) ............................................................................... - 226 -
41 E.4.7 CDC Command (CMD) ....................................................................... - 227 -
42 E.4.8 CDC Event Counting (CTE) ................................................................ - 228 -
43 E.4.9 CDC State Timing (TMS) .................................................................... - 229 -
44 E.4.10 CDC Single Point Status (SPS) .......................................................... - 230 -
45 E.4.11 CDC Integer Status (INS) ................................................................... - 231 -
46 E.4.12 CDC Controllable single point (SPC) .................................................. - 231 -
47 E.4.13 CDC Controllable integer status (INC) ................................................ - 231 -
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 -6- 88/288/CDV
1 E.4.14 CDC Binary Counter Reading (BCR)................................................... - 232 -

2 E.4.15 CDC Controllable analogue set point (APC)........................................ - 232 -
3 E.4.16 CDC Phase to ground related measured value of a three phase
4 system (WYE)..................................................................................... - 233 -
5 E.4.17 CDC Phase to phase related measured value of a three phase
6 system (DEL)...................................................................................... - 233 -
7 E.4.18 CDC Device Name Plate (WDPL) ....................................................... - 234 -
8 E.4.19 CDC Logical Node Name Plate (LPL) ................................................. - 234 -
9 E.4.20 CDC Alarm Set Status (ASS) .............................................................. - 235 -
10 E.4.21 Relationship of Data Class Attributes and Data Set Descriptors.......... - 235 -
11 E.4.22 Role of the DNP Users Group ............................................................. - 237 -
12 E.5 Mapping of the Information Exchange Model to DNP3 services ............................... - 237 -
13 E.6 Protocol stack details .............................................................................................. - 238 -
14 E.6.1 DNP3 DEVICE PROFILE DOCUMENT................................................ - 238 -
15 Annex F (normative) Time synchronization ................................................................... - 242 -
16 F.1 Introduction ............................................................................................................. - 242 -
17 F.2 A-Profile .................................................................................................................. - 242 -
18 F.3 T-Profile .................................................................................................................. - 242 -
19 Annex G (informative) Interfaces – Implementation considerations ............................... - 243 -
20 G.1 General ................................................................................................................... - 243 -
21 G.2 Example interfaces of a real system ........................................................................ - 243 -
22
23 Figure 1 – Conceptual communication model of IEC 61400-25......................................... - 15 -

24 Figure 2 – Communication profiles ................................................................................... - 24 -
25 Figure 3 – CreateDataSet sequence of services ............................................................ - 145 -
26
27 Figure A-1– Mapping architecture (conceptual) ................................................................ - 27 -

28 Figure A-2– Reporting Services mechanisme (conceptual)............................................... - 59 -
29 Figure C-1 – Mapping architecture (conceptual) ............................................................. - 164 -
30 Figure D-1 – Mapping architecture (conceptual) ............................................................. - 174 -
31 Figure E-1 – Mapping architecture (conceptual) ............................................................. - 221 -
32 Figure G-1 – Implementation issues (example) .............................................................. - 244 -
33
34 Table A-1 – Web Services Mapping overview of IEC 61400-25 IM and IEM...................... - 27 -
35 Table A-2 – Mapping the IEC 61400-25 IM to Web Services ............................................ - 31 -
36 Table A-3 – Mapping of IEC 61400-25 data attribute basic types ..................................... - 31 -
37 Table A-4 – XML schema for wind power information model ............................................ - 32 -
38 Table A-5 – Server class services mapped to Web Services ............................................ - 37 -
39 Table A-6 – GetServerDirectoryRequest .......................................................................... - 38 -
40 Table A-7 – GetServerDirectoryResponse........................................................................ - 38 -
41 Table A-8 – AssociateRequest ......................................................................................... - 40 -
42 Table A-9 – AssociateResponse ...................................................................................... - 41 -
43 Table A-10 – ReleaseRequest ......................................................................................... - 42 -
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 -7- 88/288/CDV
1 Table A-11 – ReleaseResponse ....................................................................................... - 42 -

2 Table A-12 – AbortRequest .............................................................................................. - 43 -
3 Table A-13 – AbortResponse ........................................................................................... - 43 -
4 Table A-14 – LOGICAL-DEVICE service mapping ............................................................ - 44 -
5 Table A-15 – GetLogicalDeviceDirectoryRequest ............................................................. - 44 -
6 Table A-16 – GetLogicalDeviceDirectoryResponse .......................................................... - 45 -
7 Table A-17 – LOGICAL-NODE mapping ........................................................................... - 45 -
8 Table A-18 – GetLogicalNodeDirectoryRequest ............................................................... - 46 -
9 Table A-19 – GetLogicalNodeDirectoryResponse............................................................. - 46 -
10 Table A-20 – Data mapping ............................................................................................. - 47 -
11 Table A-21 – GetDataValuesRequest............................................................................... - 47 -
12 Table A-22 – GetDataValuesResponse ............................................................................ - 48 -
13 Table A-23 – SetDataValuesRequest ............................................................................... - 48 -
14 Table A-24 – SetDataValuesResponse ............................................................................ - 49 -
15 Table A-25 – GetDataDirectoryRequest ........................................................................... - 49 -
16 Table A-26 – GetDataDirectoryResponse......................................................................... - 50 -
17 Table A-27 – GetDataDefinitionRequest........................................................................... - 51 -
18 Table A-28 – GetDataDefinitionResponse ........................................................................ - 51 -
19 Table A-29 – DATA-SET mapping .................................................................................... - 51 -
20 Table A-30 – GetDataSetValuesRequest ......................................................................... - 52 -
21 Table A-31 – GetDataSetValuesResponse ....................................................................... - 53 -
22 Table A-32 – SetDataSetValuesRequest .......................................................................... - 53 -
23 Table A-33 – SetDataSetValuesResponse ....................................................................... - 54 -
24 Table A-34 – CreateDataSetRequest ............................................................................... - 54 -
25 Table A-35 – CreateDataSetResponse............................................................................. - 55 -
26 Table A-36 – DeleteDataSetRequest................................................................................ - 55 -
27 Table A-37 – DeleteDataSetResponse ............................................................................. - 56 -
28 Table A-38 – GetDataSetDirectoryRequest ...................................................................... - 56 -
29 Table A-39 – GetDataSetDirectoryResponse ................................................................... - 57 -
30 Table A-40 – Report control block services mapping ........................................................ - 57 -
31 Table A-41 – AddSubscriptionRequest ............................................................................. - 60 -
32 Table A-42 – AddSubscriptionResponse .......................................................................... - 60 -
33 Table A-43 – RemoveSubscriptionRequest ...................................................................... - 61 -
34 Table A-44 – RemoveSubscriptionResponse.................................................................... - 61 -
35 Table A-45 – ReportFormat.............................................................................................. - 62 -
36 Table A-46 – GetBRCBValuesRequest ............................................................................ - 63 -
37 Table A-47 – DetBRCBValuesResponse .......................................................................... - 64 -
38 Table A-48 – SetBRCBValuesRequest ............................................................................. - 64 -
39 Table A-49 – SetBRCBValuesResponse .......................................................................... - 65 -
40 Table A-50 – GetURCBValuesRequest ............................................................................ - 65 -
41 Table A-51 – GetURCBValuesResponse .......................................................................... - 66 -
42 Table A-52 – SetURCBValuesRequest............................................................................. - 67 -
43 Table A-53 – SetURCBValuesResponse .......................................................................... - 67 -
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 -8- 88/288/CDV
1 Table A-54 – ReportRequest............................................................................................ - 68 -

2 Table A-55 – ReportResponse ......................................................................................... - 68 -
3 Table A-56 – LOG-CONTROL-BLOCK services mapping ................................................. - 69 -
4 Table A-57 – GetLCBValuesRequest ............................................................................... - 69 -
5 Table A-58 – GetLCBValuesResponse............................................................................. - 70 -
6 Table A-59 – SetLCBValuesRequest................................................................................ - 70 -
7 Table A-60 – SetLCBValuesResponse ............................................................................. - 71 -
8 Table A-61 – Log class services mapping ........................................................................ - 71 -
9 Table A-62 – GetLogStatusValuesRequest ...................................................................... - 72 -
10 Table A-63 – GetLogStatusValuesResponse .................................................................... - 72 -
11 Table A-64 – GetLogByTimeRequest ............................................................................... - 73 -
12 Table A-65 – QueryLogByTimeResponse ......................................................................... - 73 -
13 Table A-66 – QueryLogAfterRequest................................................................................ - 74 -
14 Table A-67 – QueryLogAfterResponse ............................................................................. - 74 -
15 Table A-68 – Control class services mapping................................................................... - 75 -
16 Table A-69 – SelectRequest ............................................................................................ - 75 -
17 Table A-70 – SelectResponse .......................................................................................... - 76 -
18 Table A-71 – SelectWithValueRequest............................................................................. - 76 -
19 Table A-72 – SelectWithValueResponse .......................................................................... - 77 -
20 Table A-73 – CancelRequest ........................................................................................... - 77 -
21 Table A-74 – CancelResponse......................................................................................... - 78 -
22 Table A-75 – OperateRequest.......................................................................................... - 78 -
23 Table A-76 – OperateResponse ....................................................................................... - 79 -
24 Table A-77 – CommandTermonationRequest ................................................................... - 79 -
25 Table A-78 – CommandTerminationResponse ................................................................. - 80 -
26 Table A-79 – TimeActivatedOperateRequest.................................................................... - 80 -
27 Table A-80 – TimeActivatedOperateResponse ................................................................. - 81 -
28 Table A-81 – Protocol stack selections ............................................................................ - 81 -
29 Table C-1 – Mapping of IEC 61400-25 IEM onto MMS according to IEC 81850-8-1 ....... - 164 -
30 Table C-2 - Mapping of AddSubscribtion service (Step 1) .............................................. - 167 -
31 Table C-3 - Mapping of AddSubscribtion service (Step 2) .............................................. - 167 -
32 Table C-4 - Mapping of AddSubscribtion service (Step 3) ............................................. - 168 -
33 Table C-5 - AddSubscription Negative response ........................................................... - 169 -
st
34 Table C-6 - Mapping of RemoveSubscribtion service. 1 MMS service .......................... - 169 -
nd
35 Table C-7 - Mapping of RemoveSubscribtion service. 2 MMS service .......................... - 170 -
36 Table C-8 - RemoveSubscription Negative response..................................................... - 170 -
37 Table C-9 - QueryLogByTime mapping ......................................................................... - 171 -
38 Table C-10 - QueryLogAfter mapping............................................................................ - 171 -
39 Table C-11 – Service and protocols for client/server communication A-Profile ............... - 171 -
40 Table C-12 – Service and protocols for client/server TCP/IP T-Profile ............................ - 172 -
41 Table D-1 Services Mapping overview of IEC 61400-25 IM and IEM .............................. - 174 -
42 Table D-2 – Overview of LD and LN mapping................................................................. - 178 -
43 Table D-3 – Logical device mapping .............................................................................. - 178 -
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 -9- 88/288/CDV
1 Table D-4– Logical node mapping .................................................................................. - 179 -

2 Table D-5 – CDC: Status Value, STV class ................................................................... - 179 -
3 Table D-6 – CDC: Setpoint Value, SPV class ................................................................. - 180 -
4 Table D-7 - CDC: Alarm, ALM class ............................................................................... - 180 -
5 Table D-8 – CDC: Command CMD class ....................................................................... - 180 -
6 Table D-9 – CDC: Event Counting, CTE class .............................................................. - 181 -
7 Table D-10 – CDC: State Timing, TMS class................................................................ - 181 -
8 Table D-11 – Mapping structure basic CDC ................................................................... - 182 -
9 Table D-12 - CDC: Single Point Status, SPS class ........................................................ - 182 -
10 Table D-13 - CDC: Single Point Status, SPS class mapping........................................... - 183 -
11 Table D-14 – CDC: Double point status, DPS class ...................................................... - 183 -
12 Table D-15 - CDC: Double Point Status, DPS class mapping ......................................... - 184 -
13 Table D-16 CDC: Integer Status, INS class ................................................................... - 184 -
14 Table D-17 CDC: Interger Status, INS class mapping to ASDU TI <35> ......................... - 185 -
15 Table D-18 CDC: Interger Status, INS class mapping to ASDU TI <37> ......................... - 185 -
16 Table D-19 – CDC: Binary Conter Reading, BCR class ............................................... - 186 -
17 Table D-20 – CDC: Binary Conter Reading, BCR class mapping ................................. - 186 -
18 Table D-21 – CDC: Controllable single point, SPC class ............................................... - 186 -
19 Table D-22 – CDC: Controllable single point, SPC mapping ........................................... - 187 -
20 Table D-23 – CDC: Controllable double point, DPC class ............................................. - 187 -
21 Table D-24– CDC: Controllable double point (DPC) mapping ......................................... - 188 -
22 Table D-25 CDC: Controllable Interger Status, INC class .............................................. - 188 -
23 Table D-26 – CDC: Controllable Interger Status , INC class mapping............................. - 189 -
24 Table D-27 – CDC: Controllable Analog set point, APC class....................................... - 189 -
25 Table D-28 – CDC: Controllable Analog set point, APC class mapping ......................... - 190 -
26 Table D-29 – CDC: Binary controlled step position, BSC class..................................... - 190 -
27 Table D-30 – CDC: Binary controlled step position, BSC class mapping to ASDU TI
28 <60> .............................................................................................................................. - 191 -
29 Table D-31 – CDC: Binary controlled step position, BSC class mapping to ASDU TI
30 <32> .............................................................................................................................. - 191 -
31 Table D-32 - CDC: Measured Value, MV class ............................................................... - 191 -
32 Table D-33 - CDC: Measured Value, MV class mapping................................................. - 192 -
33 Table D-34 – Relationship between complex CDCs and IEC 60870-5-104 ASDUs ......... - 192 -
34 Table D-35 - CDC: Complex Measured Value, CMV class .............................................. - 192 -
35 Table D-36 - CDC: Complex Measured Value, CMV class mapping................................ - 193 -
36 Table D-37 - CDC: Three Phase Value (DEL) class ....................................................... - 193 -
37 Table D-38 - CDC: Three Phase Value (DEL) class mapping ......................................... - 193 -
38 Table D-39 – WYE: Three Phase Value, WYE class...................................................... - 194 -
39 Table D-40 – CDC: Three Phase Value (WYE), mapping ............................................... - 194 -
40 Table D-41 – Mapping of IEC 61400-25 ACSI service into IEC 60870-5-104 services .... - 195 -
41 Table D-42 – Server services mapping .......................................................................... - 196 -
42 Table D-43 – Association services mapping ................................................................... - 196 -
43 Table D-44 – Logical Nodes services mapping ............................................................... - 196 -
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 10 - 88/288/CDV
1 Table D-45 – Data services mapping ............................................................................. - 197 -

2 Table D-46 – Report Control Block services mapping..................................................... - 197 -
3 Table D-47 – Control services mapping ......................................................................... - 197 -
4 Table E-1 – Services requiring Client/Server Communication Profile.............................. - 221 -
5 Table E-2 – Quality mapping .......................................................................................... - 224 -
6 Table E-3 – CDC: Measured Value (MV) mapping.......................................................... - 224 -
7 Table E-4 – CDC: Setpoint Parameter Value (SPV) mapping ......................................... - 225 -
8 Table E-5 – CDC: Status Value (STV) mapping ............................................................. - 226 -
9 Table E-6 – CDC: Alarm (ALM) mapping ........................................................................ - 226 -
10 Table E-7 – CDC: Command (CMD) mapping ................................................................ - 227 -
11 Table E-8 – CDC: Event Counting (CTE) mapping ......................................................... - 228 -
12 Table E-9 – CDC: State Timing (TMS) mapping ............................................................. - 229 -
13 Table E-10 – CDC: Single Point Status (SPS) mapping.................................................. - 230 -
14 Table E-11 – CDC: Integer Status (INS) mapping .......................................................... - 231 -
15 Table E-12 – CDC: Controllable single point (SPC) mapping ......................................... - 231 -
16 Table E-13 – CDC: Controllable integer status (INC) mapping ....................................... - 231 -
17 Table E-14 – CDC: Binary Counter Reading (BCR) mapping .......................................... - 232 -
18 Table E-15 – CDC: Controllable analogue set point (APC) mapping ............................... - 232 -
19 Table E-16 – CDC: Phase to ground (WYE) mapping ..................................................... - 233 -
20 Table E-17 – CDC: Phase to phase (DEL) mapping ....................................................... - 233 -
21 Table E-18 – CDC: Device Name Plate (WDPL) mapping............................................... - 234 -
22 Table E-19 – CDC: Logical Node Name Plate (LPL) mapping ........................................ - 234 -
23 Table E-20 – CDC: Alarm Set Status (ASS) mapping ..................................................... - 235 -
24 Table E-21 – Sample Data Class Attribute mapping ....................................................... - 236 -
25 Table E-22 – Sample Data Class mapping ..................................................................... - 236 -
26 Table E-23 – Sample partial Data Class mapping .......................................................... - 237 -
27
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 11 - 88/288/CDV
2 INTERNATIONAL ELECTROTECHNICAL COMMISSION

3 ____________
4
5 WIND TURBINES –
6
7 Part 25-4:
8 Communications for monitoring and control of wind power plants –
10
11 FOREWORD
12 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
13 all national electrotechnical committees (IEC National Committees). The object of IEC is to promote interna-
14 tional co-operation on all questions concerning standardization in the electrical and electronic fields. To this
15 end and in addition to other activities, IEC publishes International Standards, Technical Specifications, Techni-
16 cal Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”).
17 Their preparation is entrusted to technical committees; any IEC National Committee interested in the subject
18 dealt with may participate in this preparatory work. International, governmental and non-governmental organiza-
19 tions liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Or-
20 ganization for Standardization (ISO) in accordance with conditions determined by agreement between the two
21 organizations.
22 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
23 consensus of opinion on the relevant subjects since each technical committee has representation from all inter-
24 ested IEC National Committees.
25 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
26 Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
27 Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any misinter-
28 pretation by any end user.
29 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
30 transparently to the maximum extent possible in their national and regional publications. Any divergence be-
31 tween any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
32 the latter.
33 5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equip-
34 ment declared to be in conformity with an IEC Publication.
35 6) All users should ensure that they have the latest edition of this publication.
36 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
37 members of its technical committees and IEC National Committees for any personal injury, property damage or
38 other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and ex-
39 penses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publica-
40 tions.
41 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
42 indispensable for the correct application of this publication.
43 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of pat-
44 ent rights. IEC shall not be held responsible for identifying any or all such patent rights.
45 This committee draft for voting of the International Standard IEC 61400-25-4 has been pre-
46 pared by IEC technical committee 88: Wind turbines Project team 25.
47 This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
48 CDV NOTE IEC 61400-25 consists of the following parts, under the general title Communications for monitoring
49 and control of wind power plants:
50 Part 25-1: Overall description on principles and models
51 Part 25-2: Information models
52 Part 25-3: Information exchange models
53 Part 25-4: Mapping to communication profile
54 Part 25-5: Conformance testing
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 12 - 88/288/CDV
1 Part 25-6: Logical node classes and data classes for condition monitoring 1
2 A list of all parts of the IEC 61400 series, under the general title Wind turbines can be found
3 on the IEC website.
———————
1 To be published
The National Committees are requested to note that for this publication the maintenance result date is
2010
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 13 - 88/288/CDV
1 INTRODUCTION
2 The IEC 61400-25 series defines communication architecture for wind power plants. This ar-
3 chitecture has been selected to provide an abstract definition of classes and services such
4 that the specifications are independent of specific protocol stacks, implementations, and op-
5 erating systems. This part of the IEC 61400-25 series specifies the mapping of these abstract
6 classes and services to protocol stacks required to comply with the standard.
7 NOTE 1 Performance of the IEC 61400-25 series implementations are application specific. The IEC 61400-25 se-
8 ries does not guarantee a certain level of performance. This is beyond the scope of the IEC 61400-25 series. How-
9 ever there is no underlying limitation in the communications technology to prevent high-speed application (millisec-
10 ond level responses).
11
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 14 - 88/288/CDV
2 WIND TURBINES –
3
4 Part 25-4: Communications for monitoring
5 and control of wind power plants –
7
8
9
10 1 Scope
11 The focus of the IEC 61400-25 series is on the communications between wind power plant
12 components such as wind turbines and actors such as SCADA Systems. Internal communica-
13 tion within wind power plant components is outside the scope of the IEC 61400-25 series.
14 The IEC 61400-25 series is designed for a communication environment supported by a client-
15 server model. Three areas are defined, that are modelled separately to ensure the scalability
16 of implementations:
17 1) wind power plant information model,

18 2) information exchange model, and
19 3) mapping of these two models to a standard communication profile.
20 The wind power plant information model and the information exchange model, viewed to-
21 gether, constitute an interface between client and server. In this conjunction, the wind power
22 plant information model serves as an interpretation frame for available wind power plant in-
23 formation. The wind power plant information model is used by the server to offer the client a
24 uniform, component-oriented view of the wind power plant data. The information exchange
25 model reflects the whole active functionality of the server. The IEC 61400-25 series enables
26 connectivity between a heterogeneous combination of client and servers from different manu-
27 facturers and suppliers.
28 As depicted in Figure 1 the IEC 61400-25 series defines a server with the following aspects:
29 – information provided by a wind power plant component, for example, ‘wind turbine rotor
30 speed’ or ‘total power production of a certain time interval’ is modelled and made available
31 for access. The information modelled in the IEC 61400-25 series is defined in IEC 61400-
32 25-2.
33 – services to exchange values of the modelled information defined in IEC 61400-25-3.
34 – mapping to a communication profile, providing a protocol stack to carry the messages, i.e.
35 the service requests and responses and the values from the modelled information
36 (IEC 61400-25-4).
37 IEC 61400-25-5 defines test cases associated with information, services and protocol stacks
38 for conformance testing of both servers and clients.
39 The IEC 61400-25 series only defines how to model the information, information exchange
40 and mapping to specific communication protocols. The IEC 61400-25 series excludes a defini-
41 tion of how and where to implement the communication interface, the application program in-
42 terface and implementation recommendations. However, the objective of the IEC 61400-25
43 series is that the information associated with a single wind power plant component (such as a
44 wind turbine) is accessible through a corresponding logical device.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 15 - 88/288/CDV
1 This part of the IEC 61400-25 series specifies the specific mappings to protocol stacks encod-
2 ing the messages required for the information exchange between a client and a remote server
3 for
4 – data access and retrieval

5 – device control
6 – event reporting and logging
7 – publisher/subscriber
8 – self-description of devices (device data dictionary)
9 – data typing and discovery of data types
10
11 The mappings specified in this document comprises:
12 – a mapping to SOAP-based web services
13 – a mapping to OPC/XML-DA
14 – a mapping to IEC 61850-8-1 MMS
15 – a mapping to IEC 60870-5-1-104
16 – a mapping to DNP3
17 All mappings are optional, but at least one optional mapping must be selected in order to
18 be compliant with the standard.
Communication model of IEC 61400-25
Client Server
Messaging
Information exchange Messaging Information exchange
Information exchange through mapping Information exchange
model (get, set, report, through mapping model (get, set, report,
model (get, set, report, to communication model (get, set, report,
log, control, publish / to communication log, control, publish /
log, control, publish / profile log, control, publish /
subscribe, …) profile(Read,
(Read, subscribe, …)
subscribe, …) write, ... message) subscribe, …)
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
SCADA component
e. g. wind turbine
Wind power plant Wind power plant

Wind power plant Wind power plant
information model information model
information model information model
defined in (roto speed, break
defined in (roto speed, break
status, total power
Application IEC 6140-25-2 status, total power Application
IEC 6140-25-2 production, …)
production, …)
defined in
defined in
IEC 6140-25-2
IEC 6140-25-2
Outside
scope Outside
scope
Conformance test cases (information, exchange, communication profile)
Conformance test cases (information, exchange, communication profile)
defined in IEC 61400-25-5
defined in IEC 61400-25-5
19
20 Figure 1 – Conceptual communication model of IEC 61400-25

21
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 16 - 88/288/CDV
1 2 Normative references
2 The following referenced documents are indispensable for the application of this document.
3 For dated references, only the edition cited applies. For undated references, the latest edition
4 of the referenced document (including any amendments) applies.
5 IEC 61400-25 (all parts), Wind turbines – Part 25: Communications for monitoring and control
6 of wind power plants
7 IEC 61850-7-2:2003, Communication networks and systems in substations – Part 7-2: Basic
8 communication structure for substations and feeder equipment – Abstract communication ser-
9 vice interface (ACSI)
11 communication structure for substations and feeder equipment – Common data classes
13 communication structure for substations and feeder equipment – Compatible logical node
14 classes and data classes
15
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 17 - 88/288/CDV
1 3 Terms and definitions
2 For the purpose of this document, the following terms and definitions apply.
3 3.1
4 actor
5 role a system plays in the context of monitoring and control, while it is not directly involved in
6 wind power plant operation, such as Supervisory Control and Data Acquisition System
7 (SCADA)
8 NOTE There are many other designations, for example, Central Management System, Monitoring and Control
9 System, Remote Control System.
10 3.2
11 alarm
12 state information. Statement of safety intervention by the wind turbine control system (i.e
13 on/off)
14 3.3
15 command
16 controllable data for system behaviour (enable/disable, active/deactivate, etc.)
17 3.4
18 communication function
19 used by an actor to configure, perform and monitor the information exchange with wind power
20 plants, for example operational and management function
21 3.5
22 control
23 operational function used for changing and modifying, intervening, switching, controlling,
24 parameterisation and optimising of wind power plants
25 3.6
26 data retrieval
27 operational function used for collecting of wind power plant data
28 3.7
29 diagnostics
30 management function used to set up and provide for self-monitoring of the communication
31 system
32 3.8
33 electrical system
34 component of a wind power plant responsible for collecting and transmitting the energy pro-
35 duced in wind turbines
36 3.9
37 event
38 state transition (status, alarm, command)
39 3.10
40 function
41 a function is a task that is performed in the control centre or the wind power plant. Generally,
42 a function consists of sub functions that exchange data with each other. Depending on the
43 function definition, functions themselves exchange data with other functions.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 18 - 88/288/CDV
1 3.11
2 Intelligent Electronic Device
3 IED
4 any device incorporating one or more processors, with the capability to receive data from an
5 external sender or to send data to an external receiver
6 NOTE For example, wind turbine controller. An IED may have connections as a client, or as a server, or both, with
7 other IED.
8 3.12
9 information
10 content of communication. Information is defined as data (usually processed and derived
11 data, and information describing other data). The basic element is raw data from the wind
12 power plant component, which should be processed into specified information according to
13 the IEC 61400-25 series
14 NOTE Wind power plant information categories: source information (analogue and state information), control in-
15 formation, derived information (statistical and historical information).
16 3.13
17 information exchange
18 communication process between two systems, such as wind power component and actor, with
19 the goal to provide and to get relevant information. Requires specific communication func-
20 tions, consisting of one or more services
21 3.14
22 information model
23 represents the knowledge concerning functions and devices in which the functions are imple-
24 mented. This knowledge is made visible and accessible through the means of the IEC 61400-
25 25 series. The model describes in an abstract way a communication oriented representation
26 of a real function or device
27 3.15
28 log
29 historical information. Chronological list of source information for a period of time
30 3.16
31 logging
32 operational function The praxis of recording sequential data often chronologically. The result
33 of the logging is a log
34 3.17
35 logical device
36 entity that represent a set of typical wind power plant functions
37 3.18
38 management function
39 function required for the administration of the information exchange in a certain level
40 NOTE Management functions are user/access management, time synchronisation, diagnostics, and configuration.
41 3.19
42 mandatory
43 defined content shall be provided in compliance with the IEC 61400-25 series
44 3.20
45 measured data
46 sampled value of a process quantity with associated data attributes such as time stamp and
47 quality
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 19 - 88/288/CDV
1 3.21
2 meteorological system
3 component of a wind power plant responsible for the monitoring of the ambient conditions, for
4 example the wind speed, wind direction, pressure, temperature etc. It supplies data for vari-
5 ous purposes for example to correlate the meteorological data to the electrical energy output
6 by individual wind turbines to the potentially usable wind energy
7 3.22
8 monitoring
9 operational function used for local or remote observation of a system or a process for any
10 changes which may occur over time. The term can also be used for observation of the behav-
11 iour of a data value or a group of data values
12 3.23
13 operational function
14 function to obtain information and to send instructions for the normal daily operation of wind
15 power plants. Types: monitoring, logging and reporting, data retrieval, control
16 3.24
17 optional
18 defined content can be optionally provided in compliance to the IEC 61400-25 series
19 3.25
20 parameter
21 controllable information intended for obtaining or correcting system behaviour
22 3.26
23 processed data
24 measured value, with the associated data attributes such as time stamp and quality, which
25 has been processed according the calculation method attribute
26 3.27
27 profile(s)
28 Defines format(s) used by a particular protocol to transmit data objects or commands, etc.
29 3.28
30 protocol stack
31 a particular software implementation of a computer networking protocol suite. The terms are
32 often used interchangeably. Strictly speaking, the suite is the definition of the protocols and
33 the stack is the software implementation of them
34 3.29
35 report
36 actual information sent by the function reporting
37 3.30
38 reporting
39 operational function to transfer data from a server to a client, initiated by a server application
40 process
41 3.31
42 Supervisory Control and Data Acquisition
43 SCADA
44 system based on a processor unit which receives information from IEDs, determines the con-
45 trol requirements and sends commands to IEDs. A computer system that for example the dis-
46 patchers use to monitor the power distribution throughout a service or control area
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 20 - 88/288/CDV
1 3.32
2 status
3 state condition of a component or system (st1/st2/..stn)
4 3.33
5 statistical information
6 the result of applying a statistical algorithm to a set of data in order to get e.g. minimum,
7 maximum, mean, average, standard deviation, etc.
8
9 3.34
10 timing data
11 time duration of a specific state.
12 3.35
13 time synchronisation
14 the coordination of occurrences to operate in unison with respect to time. This process can be
15 a premeditated arrangement set forth on a parallel time scape, or it can be an observable co-
16 incidence in eventuality
17 3.36
18 three phase data
19 measured value in a three phase electrical circuit with associated data attributes such as time
20 stamp, quality and calculation method
21 3.37
22 user / access management
23 management function used for setting up, modifying, deleting users (administratively), assign-
24 ing access rights (administratively) and monitoring access
25 3.38
26 wind power plant
27 complete system consisting of any number of technical subsystems referred to in the IEC
28 61400-25 series as wind power plant components, for example one or more wind turbines.
29 NOTE The main objective of a wind power plant is to generate electrical energy from the wind
30 3.39
31 wind power plant analogue information
32 continuous information concerning the actual condition or behaviour of a component or sys-
33 tem
34 NOTE Types are, for example, measured value, processed value, three phase value, setpoint, parameter.
35 3.40
36 wind power plant component
37 technical system employed in the operation of wind power plants, such as wind turbine, mete-
38 orological, electrical and wind power plant management system
39 3.41
40 wind power plant management system
41 component of a wind power plant, which is responsible to ensure that the complete system
42 adapts itself to the static and dynamic conditions and requirements of the electrical power
43 connection (i.e., interoperation of the WTs with substation and other power network related
44 devices)
45 NOTE A wind power plant management system may include other functions (for example shadow control func-
46 tionality, noise or sound reduction, ice warning, lightning protection) not modelled in the IEC 61400-25 series.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 21 - 88/288/CDV
1 3.42
2 wind turbine
3 main component of a wind power plant. It is responsible for generating energy and meets the
4 task of using the wind potential of a certain location that converts kinetic wind energy into
5 electric energy.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 22 - 88/288/CDV
1 4 Abbreviated terms
ACSI Abstract Communication Service Interface (defined for example in 61850-7-2)

A-Profile Application profile
HTTP HyperText Transfer Protocol
ICMP Internet Control Message Protocol
IED Intelligent Electronic Device
IEM Information Exchange Model
IP Internet Protocol
LCB Log Control Block
LD Logical Device
LN Logical Node
LOG Log
LPHD Logical Node Physical Device
RCB Report Control Block
RFC Request For Comments
SCADA Supervisory Control and Data Acquisition
SCL substation (system) configuration language (defined in IEC 61850-6)
SCSM specific communication service mapping (defined e.g. in 61850-8-1)
SOAP simple object access protocol
TCP Transmission Control Protocol
T-Profile Transport profile
UDP User Datagram Protocol
UUID Universally Unique Identifier
WPP Wind Power Plant
WSDL Web Services Description Language
WT Wind Turbine
XML Extensible Mark-up Language
XPATH XML Path Language
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 23 - 88/288/CDV
1 5 General Introduction
2 The mapping of the information model defined in IEC61400-25-2 and information exchange
3 model, defined in IEC 61400-25-3, are specified in this document with specific mappings
4 given in five annexes
5 A. The wind power plant information exchange model mapped to a set of web services
6 that provide a mapping for all information exchange services defined and referenced in
7 part IEC 61400-25-3.
8 B. The wind power plant information exchange model mapped to an OPC/XML protocol
9 stack that provide a mapping for the information exchange services defined and refer-
10 enced in part IEC 61400-25-3.
11 C. The wind power plant information exchange model mapped to an IEC 61850-8-1 MMS
12 protocol stack that provide a mapping for the information exchange services defined
13 and referenced in part IEC 61400-25-3
14 D. The wind power plant information exchange model mapped to an IEC 60870-5-
15 101/104 protocol stack that provide a mapping for the information exchange services
16 defined and referenced in part IEC 61400-25-3
17 E. The wind power plant information exchange model mapped to an DNP3 protocol stack
18 that provide a mapping for the information exchange services defined and referenced
19 in part IEC 61400-25-3
20 Clause 5.1 provides an overview of the relation between the information model, the informa-
21 tion exchange services and the mapping to protocol stacks.
22 Clause 5.2 provides an overview of the information exchange services specified in IEC 61400-
23 25-3 and the capability of the mappings to protocol stacks.
24 Annex F provides a description of the time synchronization requirements to be implemented in

25 order to be compliant with this standard.
26 Annex G provides a readers guide to smooth the understanding of the standard. An example
27 with a real system is used for explanation.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 24 - 88/288/CDV
2 5.1 Mapping to protocol stacks.
3 Multiple mappings are supported by IEC 61400-25-4, i.e. that more than one specific mapping
4 are specified as normative. At least one mapping must be seleceted in order to comply with
5 the standard. The conceptual architecture of the multiple mapping is shown in Figure 2.
Information model
IEC 61400-25-2
Information exchange
IEC 61400-25-3
Mapping 1 Mapping 2 Mapping 3 ... Mapping N
Mapping to protocol
stacks
Application
n
n
io
io
io
io
Presentation
1 cat
2 cat
3 cat
N cat
ile uni
ile uni
ile uni
ile uni
pr mm
pr mm
pr mm
pr mm
Session
Co
Co
Co
Co
of
of
of
of
Transport TCP
Network IP
out of scope
Data Link Ethernet, ... other
out of scope
Physical Physical
8 Figure 2 – Communication profiles
10 5.2 Services of IEC 61400-25-3 mapped to protocol stacks
11 In Table 1 below is provided an overview of the information exchange services specified in

12 IEC 61400-25-3 and the degree of fulfillment provided by the specified mappings to protocol
13 stacks. For each mappings is provided a column with the compliance to the services required.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 25 - 88/288/CDV
2 Table 1 – Mapping overview of IEC 61400-25-3 services
Mapping capability overview

IEC 61400-25-3 Services M/O Web- OPC XML- IEC 61850- IEC 60870- DNP3
services DA 8-1 (MMS) 5-101/104
Associate M Y Y Y Y Y
Release O Y Y Y Y N
Abort O Y Y Y N N
GetServerDirectory O Y Y Y Y Y
GetLogicalDeviceDirectory O Y Y Y Y Y
GetLogicalNodeDirectory O Y Y Y Y N
GetDataValues M Y Y Y Y Y
SetDataValues M Y Y Y Y Y
GetDataDirectory O Y Y Y Y N
GetDataDefinition O Y Y Y Y N
GetDataSetValues M Y N Y N Y
SetDataSetValues O Y N Y N Y
CreateDataSet O Y N Y N N
DeleteDataSet O Y N Y N N
GetDataSetDirectory O Y N Y N N
Report O Y Y Y Y N
GetBRCBValues O Y N Y N N
SetBRCBValues O Y N Y N N
GetURCBValues O Y N Y Y N
SetURCBValues O Y N Y Y N
AddSubscription O Y Y Y N N
RemoveSubscription O Y Y Y N N
GetLCBValues O Y N Y N N
SetLCBValues O Y N Y N N
GetLogStatusValues O Y N Y N N
QueryLogByTime O Y N Y N N
a
QueryLogAfter O Y N Y N N
Select O Y Y Y Y Y
SelectWithValue O Y N Y Y Y
Cancel O Y Y Y Y N
Operate M Y Y Y Y Y
CommandTermination O Y N Y Y Y
TimeActivatedOperate O Y N Y N N
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 26 - 88/288/CDV
1 Annex A
2 (normative)
3
4 Specific communication service mapping –
5 Mapping to WebService
7 A.1 General
8 A.1.1 Introduction
9 This Annex describes as solution including the definition & mapping of the IEC 61400-25 In-
10 formation Model and Information Exchange Classes and Model services into objects and Web
11 Services. The annex describes a complete communication solution defined by a WSDL file
12 applicable for implementation of communication with a wind power plant.
13 This annex includes the clauses as follows:
14 Clause A.1 provides an general introduction of the mapping to WebServices.
15 Clause A.2 provides the list of normative references for mapping to WebServices.
16 Clause A.3 provides a list of abbreviated terms used in annex A.
17 Clause A.4 provides mapping of the information model to WebServices.
18 Clause A.5 provides mapping of the information exchange model to WebServices.
19 Clause A.6 provides the protocol stack details.
20 Clause A.7 provides the WSDL specification for the mapping to WebServices. The binding
21 style selected in the WSDL specification is the document/literal wrapped.
22 A.1.2 Scope
23 The scope of the mapping to Web Services is the exchange of process information required
24 for operational purposes based on a client – server association.
25 The information model and the information exchange model constitutes the interface specifi-
26 cation between a client and a server.The information model provides an interpretation frame
27 for the exposed wind power plant data and is used by the server to offer the associated client
28 a uniform and component-oriented view of the wind power plant data.
29 The amount of information provided by the server can vary dependent on the range of op-
30 tional data offered by the various manufacturer.
31 Clients can be local, regional or placed in nationwide control centres that exchange informa-
32 tion in order to monitor and control the wind power plant..
33 A.1.3 The mapping architecture
34 The mapping architecture consists of 3 parts:
35 1. Mapping of the information model

Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 27 - 88/288/CDV
1 2. Mapping of the data classes
2 3. Mapping of the information exchange services
3 The specified mapping for IEC 61400-25 Annex A is based on using SOAP/XML to exchange
4 the information modelled of the wind power plant components in a server – client based archi-
5 tecture.
6 The wind power plant information model defined in 61400-25-2 shall be mapped to a hierar-
7 chical structure.
8 The conceptual mapping is depicted in Figure A-1. The wind power plant information model of
9 IEC 61400-25-2 are intended to be preserved when mapped to Web Services. This especially
10 means that:
11 - the server implements the hierarchical wind power plant information model of IEC 61400-
12 25-2 (IM) that can be retrieved by the services according to Table A-1.
13 - the client implements the wind power plant information model by configuration.
14 - the client station accesses the hierarchical wind power plant information model of IEC
15 61400-25-3 through the services provided by WebSevices mapping to exchange informa-
16 tion and real-time data.
Information model of
IEC 61400-25 (server):
Turbine5
Client Information model (LD „Turbine5“ and its LNs
W GEN
and Data) through configuration
W TUR
TurSt
W
mag
Object references and real-time q
values of: t
Turbine5/WTUR.W.m ag units
Turbine5/WTUR.W.q db
Turbine5/WTUR.W.t d
map to xx of type „yyy“
according to IEM as
specified in IEC61400-25-3
local local
interface W ebService mapping interface
Request
Response
…
17
18 Figure A-1– Mapping architecture (conceptual)
19
20 Table A-1 – Web Services Mapping overview of IEC 61400-25 IM and IEM
IEC 61400-25-2 IM Class IEC 61400-25-3 IEM M/O Included in Maps to objects &
IEC 61400-25-3 IEM Class Services the mapping Web Services
SERVER Y tServer
GetServerDirectory O Y GetServerDirectory
ASSOCIATION
Associate M Y Associate
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 28 - 88/288/CDV
IEC 61400-25-2 IM Class IEC 61400-25-3 IEM M/O Included in Maps to objects &
IEC 61400-25-3 IEM Class Services the mapping Web Services
Release O Y Release
Abort O Y Abort
LOGICAL-DEVICE Y tLD
GetLogicalDeviceDirec- O Y GetLogicalDeviceDi-
tory rectory
LOGICAL-NODE Y tLN
GetLogicalNodeDirec- O Y GetLogicalNodeDi-
tory rectory
DATA Y tData
GetDataValues M Y GetDataValues
SetDataValues M Y SetDataValues
GetDataDirectory O Y GetDataDirectory
GetDataDefinition O Y GetDataDefinition
DATA-SET Y tDataSet
GetDataSetValues M Y GetDataSetValues
SetDataSetValues O Y SetDataSetValues
CreateDataSet O Y CreateDataSet
DeleteDataSet O Y DeleteDataSet
GetDataSetDirectory O Y GetDataSetDirectory
REPORTING
AddSubscription O Y AddSubscription
RemoveSubscription O Y RemoveSubscription
Report O Y ReportRe-
quest/Response
BRCB tBRCB
GetBRCBValues O Y GetBRCBValues
SetBRCBValues O Y SetBRCBValues
URCB
GetURCBValues O Y GetURCBValues
SetURCBValues O Y SetURCBValues
LOG Y tLOG
GetLogStatusValues O Y GetLogStatusValues
QueryLogByTime O Y QueryLogByTime
QueryLogAfter O Y QueryLogAfter
LCB tLCB
GetLCBValues O Y GetLCBValues
SetLCBValues O Y SetLCBValues
CONTROL CONTROL
Select O Y Select
SelectWithValue O Y SelectWithValue
Cancel O Y Cancel
Operate M Y Operate
CommandTermination O Y CommandTermination
TimeActivatedOperate O Y TimeActivatedOperate
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 29 - 88/288/CDV
2 A.2 Specific normative references for Web Services
3 The following referenced documents are indispensable for the application of this document.
4 For dated references, only the edition cited applies. For undated references, the latest edition
5 of the referenced document including any amendments applies.
6
7 IEC 61400-25 (all parts), Wind turbines - Part 25: Communications for monitoring and control
8 of wind power plants
9
10 IEC 61850-6: 2004, Communication networks and systems in substations – Part 7-2: Basic
11 communication structure for substations and feeder equipment – Configuration description
12 language for communication in electrical substationsrelated to IEDs
13 W3C, Extensible Markup Language (XML) 1.0, http://www.w3.org/TR/2000/REC-xml-

14 20001006
15
16 W3C, Name spaces in XML, http://www.w3.org/TR/REC-xml-names
17 W3C, XML Schema Part 0: Primer, http://www.w3.org/TR/xmlschema-0
18 W3C, XML Schema Part 1: Structures, http://www.w3.org/TR/xmlschema-1
19 W3C, XML Schema Part 2: Data Types, http://www.w3.org/TR/xmlschema-2
20 SOAP ver. 1.1, W3C Note "Simple Object Access Protocol (SOAP) 1.1, 8 May 2000.
21 http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321/#reqoptrespbinding
22 ISO 639-2 Codes for the representation of names of languages
23 RFC 791 Internet Protocol specification (IP)
24 RFC 792 Internet Control Message Protocol (ICMP)
25 RFC 793 Transmission Control Protocol (TCP)
26 RFC 826 Ethernet Address Resolution Protocol
27 RFC 919 Broadcasting internet datagrams
28 RFC 922 Broadcasting internet datagrams in presence of subnets
29 RFC 950 Internet Standard Subnetting Procedure
30 RFC 1112 Host Extensions for IP Multicasting
31 RFC 2616 Hypertext Transfer Protocol - HTTP/1.1
32 RFC 2617 Upgrading to TLS Within HTTP/1.1
33 RFC 2246 Transport Layer Security (TLS) protocol
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 30 - 88/288/CDV
1 RFC 4122 Universally Unique IDentifier (UUID) URN Namespace
3 A.3 Abbreviated terms
HTTP Hyper Text Transfer Protocol

ICMP Internet Control Message Protocol
IP Internet Protocol
LD Logical Device
LN Logical Node
LOG Log
SCSM Specific Communication Service Mapping (defined in 61850-8-1)
SOAP Simple Object Access Protocol
UDP User Datagram Protocol
UUID Universally Unique IDentifier
WSDL Web Services Description Language. Litteral/wrapped
WT Wind Turbine
5 A.4 Mapping of the IEC 61400-25 Information Model to Web Services
6 A.4.1 Introduction
7 The main characteristics of the classes defined in part IEC 61400-25-2 mapped to web ser-
8 vices are listed in Table A-2.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 31 - 88/288/CDV
1 Table A-2 – Mapping the IEC 61400-25 IM to Web Services
IEC 61400-25-2 IM Classes Mapping to objects & Web Services

SERVER tServer
LOGICAL-DEVICE tLD
LOGICAL-NODE tLN
DATA classes tDATA
COMMON-DATA classes tCDC
DATA-ATTRIBUTE type tDataAttribute
DA-COMPONENT type tDAType
2 The mapping of the basic data types attributes are depicted in Table A-3.
3 Table A-3 – Mapping of IEC 61400-25 data attribute basic types
IEC 61400-25 name Value Range / explanation Mapping to objects & Web Services
BOOLEAN True | False according to tBasicType

INT8 -128 to +127 according to tBasicType
INT16 -32.768 to +32.767 according to tBasicType
INT24 -8.388.608 to 8.388.607 according to tBasicType
INT32 -2**32 to (2**32)-1 according to tBasicType
INT128 -2**127 to (2**127)-1 according to tBasicType
INT8U 0 to 255 according to tBasicType

INT16U 0 to 65.535 according to tBasicType
INT24U 0 to 16.777.215 according to tBasicType
INT32U 0 to 4.294.967.295 according to tBasicType
FLOAT32 single precision floating point according to tBasicType
FLOAT64 double precision floating point according to tBasicType
ENUMERATED Ordered set of values dependent of information according to tBasicType

CODED ENUM Ordered set of values, defined once according to tBasicType
OCTET STRING Hexadecimal binary according to tBasicType
VISIBLE STRING String according to tBasicType
UNICODE STRING String according to tBasicType
5 The wind power plant information model specified in IEC 61400-25-2 is defined by LOGICAL-
6 NODES classes, DATA classes, COMMON-DATA classes, DATA-ATTRIBUTE types, and DA-
7 COMPONENT types. The XML schema for the recursive definition of classes listed in Table
8 A-2 is defined in Table A-4.
9 The naming convention and object references to be applied shall follow the guidelines and re-
10 strictions given in IEC61850-6, clause 8.3 and related sub clauses and referenced standards.
11 The schema shall be used for all services that carry structure and/or data values of a given
12 instance of the wind power information model derived from the classes specified in this stan-
13 dard. The WSDL structures shown are to facilitate understanding of the specification. The ex-
14 act WSDL specifications are given in A.7, which has to be implemented in order to comply
15 with this standard.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 32 - 88/288/CDV
1 Table A-4 – XML schema for wind power information model
2 <s:schema targetNamespace="http://iec.ch/61400/ews/1.0/"
3 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
4 xmlns:s="http://www.w3.org/2001/XMLSchema"
5 xmlns:ews="http://iec.ch/61400/ews/1.0/"
6 elementFormDefault="qualified">
7
8 <s:complexType name="tLD">
9 <s:sequence>
10 <s:element name="LDName" type="ews:tObjectName"/>
11 <s:element name="LN" type="ews:tLN" minOccurs="3" maxOccurs="unbounded"/>
12 </s:sequence>
13 </s:complexType>
14
15 <s:complexType name="tLN">
16 <s:sequence>
17 <s:element name="LNName" type="ews:tObjectName"/>
18 <s:element name="Data" type="ews:tDATA" maxOccurs="unbounded"/>
19 <s:element name="DataSet" type="ews:tDATASet" minOccurs="0" maxOccurs="unbounded"/>
20 <s:element name="BRCB" type="ews:tBRCB" minOccurs="0" maxOccurs="unbounded"/>
21 <s:element name="URCB" type="ews:tURCB" minOccurs="0" maxOccurs="unbounded"/>
22 <s:element name="LCB" type="ews:tLCB" minOccurs="0" maxOccurs="unbounded"/>
23 <s:element name="LOG" type="ews:tLOG" minOccurs="0"/>
24 </s:sequence>
25 </s:complexType>
26
27
28
29
30 <s:complexType name="tDATA">
31 <s:sequence>
32 <s:element name="DataName" type="ews:tObjectName"/>
33 <s:sequence maxOccurs="unbounded">
34 <s:element name="DataAttr" type="ews:tDataAttribute" minOccurs="0" maxOccurs="unbounded"/>
35 <s:element name="CompositeCDC" type="ews:tDATA" minOccurs="0" maxOccurs="unbounded"/>
36 <s:element name="SimpleCDC" type="ews:tSimpleData" minOccurs="0" maxOccurs="unbounded"/>
37 </s:sequence>
38 </s:sequence>
39 </s:complexType>
40
41
42
43
44 <s:complexType name="tSimpleData">
45 <s:sequence>
48 <s:element name="DataAttr" type="ews:tDataAttribute"/>
49 </s:sequence>
50 </s:sequence>
51 </s:complexType>
52
53
54
55
56 <s:complexType name="tDataAttribute">
57 <s:sequence>
58 <s:element name="DAType" type="ews:tDAType"/>
59 <s:element name="TrgOp" type="ews:tTrgCond" minOccurs="0" maxOccurs="unbounded"/>
60 </s:sequence>
61 <s:attribute name="FC" type="tFC” use=”required” />
62 </s:complexType>
63
64
65
66 <s:complexType name="tDAType">
67 <s:sequence>
68 <s:element name="DAName" type="ews:tObjectName"/>
69 <s:choice minOccurs="1" maxOccurs="unbounded">
70 <s:element name="DAComp" type="ews:tDAType" minOccurs="0" maxOccurs="unbounded"/>
71 <s:element name="PrimComp" type="ews:tBasicType" minOccurs="0"/>
72 </s:choice>
73 </s:sequence>
74 </s:complexType>
75
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 33 - 88/288/CDV
1 Example - The logical node “Wind turbine converter information” (WCNV) contains an example with hierarchical
2 (nested) DATA at the LN level (DATA class CurMs has two components: DATA class CnVGn and CnVGd of type
3 WWYE) and hierarchical DATA at the CDC level (CDC WWYE has one additional data level: phsA in WWYE). The
4 example also has two nested data attribute component (DAC): mag and the underlying i. The following xml struc-
5 ture represents an excerpt of the logical device WPP1. The logical device contains one logical node WCNV with the
6 instance name WCNV1.
7 The self-description of the first DATA instance CnvGnFreq ( Frequency value for generator ) is as follows:
8 <LD>
9 <LDName>WPP1</LDName>
10 <LN>
11 <LNName>WCNV1</LNName>
12 <Data>
13 <DataName>CnvGnFrq</DataName>
14 <DataAttr FC=”MX”>
15 <DAType>
16 <DAName>AV</DAName>
17 <DAComp>
18 <DAName>mag</DAName>
19 <PrimComp>
20 <BasName>i</BasName>
21 <int32>75</int32>
22 </PrimComp>
23 </DAComp>
24 </DAType>
25 <DataAttr>
26 </Data>
27 </LN>
28 ….
29 </LD>
30
31 A.4.2 SERVER class
32 The SERVER class shall be mapped as defined in the following text.
33 <s:complexType name="tServer">
34 <s:sequence>
35 <s:element name="ServerAccessPoint" type="s:string" maxOccurs="unbounded"/>
36 <s:element name="LD" type="ews:tLD" maxOccurs="unbounded"/>
37 </s:sequence>
38 </s:complexType>
39 All elements shall be as defined in IEC 61850-7-2.
40 A.4.3 LOGICAL-DEVICE class
41 The LOGICAL-DEVICE class shall be mapped as defined in the following text.
43 <s:annotation>
44 <s:documentation>Container for Logical Device object</s:documentation>
45 </s:annotation>
46 <s:sequence>
49 </s:sequence>
50 </s:complexType>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 34 - 88/288/CDV
1 A.4.4 LOGICAL-NODE class
2 The LOGICAL-NODE class shall be mapped as defined in the following text.
4 <s:sequence>
12 </s:sequence>
13 </s:complexType>
15 A.4.5 DATA class
16 The DATA class shall be mapped as defined in the following text.
18 <s:sequence>
21 <s:element name="DataAttr" type="ews:tDataAttribute" minOccurs="0" maxOccurs="unbounded"/>
22 <s:element name="CompositeCDC" type="ews:tDATA" minOccurs="0" maxOccurs="unbounded"/>
23 <s:element name="SimpleCDC" type="ews:tSimpleData" minOccurs="0" maxOccurs="unbounded"/>
24 </s:sequence>
25 </s:sequence>
26 </s:complexType>
27 The CompositeCDC and the SimpleCDC is a specialization of the DATA class for this stan-
28 dard, all other elements shall be as defined in IEC 61850-7-2.
29 A.4.6 DATA-SET class
30 The DATA-SET class shall be mapped as defined in the following text.
31 <s:complexType name="tDATASet">
32 <s:annotation>
33 <s:documentation>Container for DATA-SET object</s:documentation>
34 </s:annotation>
35 <s:sequence>
36 <s:element name="DSName" type="ews:tObjectName"/>
37 <s:element name="DSMemberRef" type="ews:tFcdFcdaType" maxOccurs="unbounded"/>
38 </s:sequence>
39 </s:complexType>
41 A.4.7 DATA ATTRIBUTE definition
42 The DATA ATTRIBUTE definition shall be mapped as defined in the following text.
44 <s:annotation>
45 <s:documentation>Container for DataAttributes</s:documentation>
46 </s:annotation>
47 <s:sequence>
48 <s:element name="DataAttributeType" type="ews:tDAType"/>
51 </s:sequence>
52 </s:complexType>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 35 - 88/288/CDV
1 A.4.8 DAType class
2 The DAType class shall be mapped as defined in the following text.
4 <s:annotation>
5 <s:documentation>Container for DAType</s:documentation>
6 </s:annotation>
7 <s:sequence>
11 <s:element name="PrimComp" type="ews:tBasicType" minOccurs="0"/>
12 </s:choice>
13 </s:sequence>
14 </s:complexType>
15 DAComp and PrimComp is a specialization of the DAType class for this standard, all elements
16 shall be as defined in IEC 61850-7-2.
17 A.4.9 REPORT-CONTROL-BLOCK class
18 Report control block provides the mechanism of spontaneously reporting of data values on
19 specific criteria (e.g., on change of value, on change of quality information, or simply periodi-
20 cally). The behaviour of a report control is determined by the values of the attributes of the
21 corresponding control block instances (e.g., en-able/disable reporting, use of sequence num-
22 ber). A report control block references an instance of a data set to specify the data values to
23 be monitored and reported spontaneously.
24 The BUFFERED-REPORT-CONTROL-BLOCK (BRCB) provides the functionality to ensure

25 that a server sends a sequence-of-events even if the communication is temporarily inter-
26 rupted. With the UNBUFFERED-REPORT-CONTROL-BLOCK (URCB) a server does not need
27 to buffer events in case of communication interruption.
28 All attributes and behavour of the report control block classes (BRCB and URCB) as defined
29 in IEC 61850-7-2 shall be mapped as follows.
30 A.4.10 BUFFERED-REPORT-CONTROL-BLOCK Class (BRCB)
31 The BRCB class shall be mapped as defined in the following text.
32 <s:complexType name="tBRCB">
33 <s:annotation>
34 <s:documentation>Container for BRCB object</s:documentation>
35 </s:annotation>
36 <s:sequence>
37 <s:element name="BRCBName" type="ews:tObjectName"/>
38 <s:element name="RptID" type="ews:tstring65"/>
39 <s:element name="RptEna" type="s:boolean"/>
40 <s:element name="DatSet" type="ews:tObjectReference"/>
41 <s:element name="ConfRev" type="s:unsignedInt"/>
42 <s:element name="OptFlds" type="s:tOptFldsBRCB"/>
43 <s:element name="BufTm" type="s:unsignedInt"/>
44 <s:element name="SqNum" type="s:unsignedShort"/>
45 <s:element name="TrgOp" type="ews:tTrgCond"/>
46 <s:element name="IntgPd" type="ews:unsignedInt"/>
47 <s:element name="GI" type="s:boolean"/>
48 <s:element name="PurgeBuf" type="s:boolean"/>
49 <s:element name="EntryID" type="ews:tEntryID"/>
50 <s:element name="TimeOfEntry" type="ews:tTimeStamp"/>
51 </s:sequence>
52 </s:complexType>
53 
55 <s:complexType name="tOptFldsBRCB">
56 <s:annotation>
57 <s:documentation>Optional fields for BRCB</s:documentation>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 36 - 88/288/CDV
1 </s:annotation>
2 <s:sequence>
3 <s:element name="seqNum" type="s:boolean"/>
4 <s:element name="timeStamp" type="s:boolean"/>
5 <s:element name="reasonCode" type="s:boolean"/>
6 <s:element name="dataSet" type="s:boolean"/>
7 <s:element name="dataRef" type="s:boolean"/>
8 <s:element name="bufOvfl" type="s:boolean"/>
9 <s:element name="entryID" type="s:boolean"/>
10 <s:element name="configRef" type="s:boolean"/>
11 </s:sequence>
12 </s:complexType>
13
15 A.4.11 UNBUFFERED-REPORT-CONTROL-BLOCK Class (URCB)
16 The URCB class shall be mapped as defined in the following text.
17 <s:complexType name="tURCB">
18 <s:annotation>
19 <s:documentation>Container for URCB object</s:documentation>
20 </s:annotation>
21 <s:sequence>
22 <s:element name="URCBName" type="ews:tObjectName"/>
25 <s:element name="Resv" type="s:boolean"/>
28 <s:element name="OptFlds" type="ews:tOptFldsURCB"/>
32 <s:element name="IntgPd" type="s:unsignedInt"/>
34 </s:sequence>
35 </s:complexType>
36 
38 <s:complexType name="tOptFldsURCB">
39 <s:annotation>
40 <s:documentation>Optional fields for URCB</s:documentation>
41 </s:annotation>
42 <s:sequence>
48 <s:element name="reserved" type="s:boolean"/>
50 <s:element name="configRev" type="s:boolean"/>
51 </s:sequence>
52 </s:complexType>
54 A.4.12 LOG-CONTROL-BLOCK class (LCB)
55 LOG-CONTROL-BLOCK class shall be mapped as defined in the following text.

56 <s:complexType name="tLCB">
57 <s:sequence>
58 <s:element name="LCBName" type="ews:tObjectName"/>
59 <s:element name="LogEna" type="s:boolean"/>
61 <s:element name="OptFlds" type="ews:tOptFldsLCB"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 37 - 88/288/CDV
1 <s:element name="LogRef" type="ews:tObjectReference"/>

2 </s:sequence>
3 </s:complexType>
5 A.4.13 LOG class
6 the LOG class shall mapped as defined in the following text.
7 <s:complexType name="tLOG">
8 <s:annotation>
9 <s:documentation>Container for LOG object</s:documentation>
10 </s:annotation>
11 <s:sequence>
12 <s:element name="LogName" type="ews:tObjectName"/>
13 <s:element name="OldEntrTm" type="ews:tTimeStamp"/>
14 <s:element name="NewEntrTm" type="ews:tTimeStamp"/>
15 <s:element name="OldEntr" type="s:unsignedInt"/>
16 <s:element name="NewEntr" type="s:unsignedInt"/>
18 <s:element name="LogEntry" type="ews:tLOGEntry"/>
19 </s:sequence>
20 </s:sequence>
21 </s:complexType>
23 A.5 Mapping of the Information Exchange Model to Web Services
24 The wind power plant information exchange services specified in the IEC 61400-25-3 IEM
25 shall be mapped to the services defined in this clause.
26 A.5.1 SERVER class service mapping
27 The SERVER class services shall be mapped to web services as depicted in Table A-5.
28 Table A-5 – Server class services mapped to Web Services
IEC 61400-25-2 IM Class IEC 61400-25-3 IEM Services Maps to objects & Web Services
IEC 61400-25-3 IEM Class
SERVER tServer
GetServerDirectory GetServerDirectory
ASSOCIATION
Associate Associate
Release Release
Abort Abort
29
30 A.5.1.1 GetServerDirectory
31 A client shall use the GetServerDirectory services to retrieve the namespace of LOGICAL-
32 DEVICEs exposed and thus accessible to a client addressing the SERVER.
33 A.5.1.1.1 GetServerDirectoryRequest
34 The GetServerDirectoryRequest service shall be defined as follows:
35 <s:element name="GetServerDirectoryRequest">
36 <s:complexType>
37 <s:sequence>
38 <s:element name="ObjClass" type="ews:tObjectClass"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 38 - 88/288/CDV
1 </s:sequence>
2 <s:attribute name="UUID" type="ews:tstring36" use="optional"/>
3 <s:attribute name="AssocID" type=”ews:tAssocID” use="required"/>
4 </s:complexType>
5 </s:element>
6
7 The Tag Names shall be defined according to Table A-6
8 Table A-6 – GetServerDirectoryRequest
Tag Name Description

ObjClass A reference to a LOGICAL-DEVICE or a FILE reference.
UUID Universal Unique ID is used as a unique service identification for a request/response
relationship. The UUID details shall be as specified in RFC 4122.
AssocID AssocID is used to identify the association originator - the specific client. The Asso-
cID shall be used to identify e.g. established subscriptions and loggings on the
server.
Other elements as defined in IEC 61850-7-2.
9
10 A.5.1.1.2 GetServerDirectoryResponse
11 The GetServerDirectoryResponse service shall be defined as follows:
12 <s:element name="GetServerDirectoryResponse">
13 <s:complexType>
14 <s:sequence>
15 <s:choice>
16 <s:element name="LDRef" type="ews:tObjectReference" minOccurs="0" maxOccurs="unbounced/>
17 <s:element name="FileRef" type="ews:tFileName" minOccurs="0" maxOccurs="unbounded"/>
18 </s:choice>
19 <s:element name="ServiceError" type="ews:tServiceError" minOccurs="0" maxOccurs="unbounced"/>
20 </s:sequence>
23 </s:complexType>
24 </s:element>
25 The Tag Names shall be defined according to Table A-7.
26 Table A-7 – GetServerDirectoryResponse

ServiceError An embedded error. The server shall use the element to indicate that the requested
service was not successfully. When this element is present in the response message,
the client shall assume that the request is rejected by the server.
relationship. The UUID details shall be as specified in RFC 4122.The Server shall
mirror the UUID value received in the request message and return the same value in
the response message.
server.
27
28 A.5.1.2 ASSOCIATION services mapping
29 The process of creating an association with a server shall be the step taking place before the
30 data exchange takes place. The client shall identify itself to the server. The server shall ap-
31 prove the parameter values provided in the association request before a session between cli-
32 ent and server shall continue.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 39 - 88/288/CDV
1 A client and a server might have multiple associations only limited by the implementation and
2 accordingly out of scope for this document.
3 The final step in a communication session shall be releasing the association. It enables the
4 client to notify the server about its intension to release the association, so the server is able
5 to de-allocate resources related to the association.
6 The server shall keep a time-out linked to each association established. If this timeout is ex-
7 ceeded without any service request from the client, it shall be considered that the com-
8 munication is over and release any resource allocated. Any service request received with an
9 invalid (not in use) association identifier shall return the "connection-lost" service error.
10 <s:enumeration value="connection-lost"/>
11 On the client side, the reception of the "connection-lost" service error shall be considered a
12 communication lost so a new association shall be requested in order to exchange services
13 with the server side.
14 In case the client detects an abnormal situation that discontinue interchanging of services or
15 in the case the server refuses the release of an association the client may abort the associa-
16 tion using the "AbortRequest" service.
17 The server cannot refuse this service. The only service error allowed in the AbortResponse is
18 the "connection-lost" that means that the association is considered over from the server point
19 of view.
20 A.5.1.3 Associate
21 A.5.1.3.1 AssociateRequest
22 The AssociateRequest service shall be defined as follows:
23 <s:element name="AssociateRequest">
24 <s:complexType>
25 <s:choice>
26 <s:element name="UserName" type="s:string"/>
27 <s:element name="Password" type="s:string"/>
28 <s:element name="LocalID" type="s:string" minOccurs="0"/>
29 <s:element name="MaxMessageSize" type="s:unsignedInt "/>
30 </s:choice>
32 </s:complexType>
33 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 40 - 88/288/CDV
2 Table A-8 – AssociateRequest

AssociateRequest AssociateRequest shall be the first message sent when establishing a connection to a
server. This allows the client to set up properties for the session and the server to
verify that these properties are set to a proper value. If a client tries to send any
messages prior to an AssociateRequest the response shall be a SOAP Fault with the
fault code: Client.MustAssociate, but without any restrictions on the specific wording
of the fault string. If the client already is logged on to the server and sends a Associ-
ateRequest, the AssociateResponse shall contain a ServiceError.
UserName The server shall use the UserName to identify the client as a registered user and if
this is not possible the server shall return an error in the AssociateResponse.
Password The Password attribute shall be used by the server to verify that the requesting client
is allowed to assosicate with the system. If the password verification is rejected the
server shall return an error in the AssociateResponse.
LocalID The LocalID attribute shall be optional and could be used by the server to respond to
a client request to select e.g. which language shall be used for display of the informa-
tion requested. If none LocalID is supplied the default selections defined in the
nameplate shall be used. If this attribute is set to an invalid value the server must re-
spond with an error. Valid range of LocalID shall be a three letter code according to
the ISO639-2 standard.
MaxMessageSize Max number of octets the client are able to receive in one SOAP reply message from
the server.
3
4 EXAMPLE Body of the corresponding SOAP message for an AssociateRequest:
5
6 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
7 xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/”>
8 <SOAP-ENV:Body>
9 <m:AssociateRequest xmlns:m="http://iec.ch/61400/ews/1.0/">
10 <m:UserName>MyName</m:UserName>
11 <m:Password>MyPassword</m:Password>
12 <m:LocalID>ger</m:LocalID>
13 <m:MaxMessageSize>MaxMessageSize</m:MaxMessageSize>
14 </m:AssociateRequest>
15 </SOAP-ENV:Body>
16 </SOAP-ENV:Envelope>
17 The LocalID specify that German language shall be applied in the association. The MaxMes-
18 sageSize specify by the client gives the maximum number of octets that the client are be able
19 to receive in one SOAP reply message.
20 A.5.1.3.2 AssociateResponse
21 The AssociateResponse shall be defined as follows:
22
23 <s:element name="AssociateResponse">
24 <s:complexType>
25 <s:choice>
26 <s:sequence>
27 <s:element name="MaxMessageSize" type="s:unsignedInt use="required"/>
28 </s:sequence>
29 <s:element name="ServiceError" type="ews:tServiceError" minOccurs="0" maxOccurs="unbounded"/>
30 </s:choice>
33 </s:complexType>
34 </s:element>
35
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 41 - 88/288/CDV
1 Table A-9 – AssociateResponse

AssociateResponse AssociateResponse shall be the response message by the server upon receiving a
AssociateRequest. This message shall contain only an optional error and an optional
ClientRequestHandle. The Client shall use the AssociateResponse to verify the Asso-
ciateRequest has been successfully executed.
MaxMessageSize Max number of octets that the server shall send in one SOAP reply massage to the
client. The number of octets send by the server shall be less or equal to the MaxMes-
sageSize specified in the client AssociateRequest..
relationship. The UUID details shall be as specified in RFC 4122. The Server shall
server.
2
3 EXAMPLE Body of the corresponding SOAP message for AssociateResponse:
4
5 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
6 xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/”>
7 <SOAP-ENV:Body>
8 <m:AssociateResponse xmlns:m="http://iec.ch/61400/ews/1.0/">
9 <m:MaxMessageSize>??</m:MaxMessageSize>
10 <m:UUID>??</m:UUID>
11 <m:AssocID>??< /m:AssocID>
12 </m:AssociateResponse>
13 </SOAP-ENV:Body>
14 </SOAP-ENV:Envelope>
15
16 A.5.1.4 Release
17 A.5.1.4.1 ReleaseRequest
18 The ReleaseRequest shall be defined as follows:
19 <s:element name="ReleaseRequest">
20 <s:complexType>
23 </s:complexType>
24 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 42 - 88/288/CDV
2 Table A-10 – ReleaseRequest

ReleaseRequest ReleaseRequest shall be the last message sent when terminating the session. This
allows the client to prepare the server for the closing of the session.If one or more
client subscriptions is running on the server at the time ReleaseRequest is accepted.
The identifier AssocID is used for identification of the subscribtion owner.
server.
4 A.5.1.4.2 ReleaseResponse
5 The ReleaseResponse shall be defined as follows:
6 <s:element name="ReleaseResponse">
7 <s:complexType>
8 <s:choice>
9 <s:element name="ServiceError" type="ews:tServiceError" minOccurs="0" maxOccurs="1"/>
10 </s:choice>
13 </s:complexType>
14 </s:element>
15 The Tag Names shall be defined according to Table A-11..
16 Table A-11 – ReleaseResponse

ReleaseResponse ReleaseResponse shall be the response message by the server upon receiving a Re-
leaseRequest.The Client shall use the ReleaseResponse to verify that the Re-
leaseRequest has been successfully executed.
server.
17
18 A.5.1.5 Abort
19 A.5.1.5.1 AbortRequest
20 The AbortRequest shall be defined as follows:
21 <s:element name="AbortRequest">
22 <s:complexType>
25 </s:complexType>
26 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 43 - 88/288/CDV
2 Table A-12 – AbortRequest

AbortRequest In case the client detects an anormal situation that discontinue interchanging of ser-
vices or in the case the server refuses the release of an association the client may
abort the association using the "AbortRequest" service.
The server cannot refuse this service. The only service error allowed in the AbortRe-
sponse is the "connection-lost" that means that the association is considered over
from the server point of view.
server.
4 A.5.1.5.2 AbortResponse
5 The AbortResponse shall be defined as follows:
6 <s:element name="AbortResponse">
7 <s:complexType>
8 <s:choice>
10 </s:choice>
13 </s:complexType>
14 </s:element>
16 Table A-13 – AbortResponse

AbortResponse Any service request received an invalid (not in use) association identifier shall return
the "connection-lost" service error: <s:enumeration value="connection-lost"/>
On the client side, the reception of the "connection-lost" service error shall be con-
sidered a communication lost so a new association shall be requested in order to ex-
change services with the server side.
server.
17
18 A.5.2 LOGICAL-DEVICE class service mapping
19 The LOGICAL-DEVICE class service shall be mapped to web services as given in Table A-14.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 44 - 88/288/CDV
2 Table A-14 – LOGICAL-DEVICE service mapping
LOGICAL-DEVICE tLD
GetLogicalDeviceDirectory GetLogicalDeviceDirectory
3
4
5 A.5.2.1 GetLogicalDeviceDirectory
6 A client shall use the GetLogicalDeviceDirectory service to retrieve the LD namespace with all
7 LOGICAL-NODEs exposed, and thus accessible to a client addressing the Logical Device.
8
9 A.5.2.1.1 GetLogicalDeviceDirectoryRequest
10 The GetLogicalDeviceDirectoryRequest service shall be defined as follows:
11 <s:element name="GetLogicalDeviceDirectoryRequest">
12 <s:complexType>
13 <s:sequence>
14 <s:element name="LDRef" type="ews:tObjectReference"/>
15 </s:sequence>
18 </s:complexType>
19 </s:element>
21
22 Table A-15 – GetLogicalDeviceDirectoryRequest

server.
23
24
25 A.5.2.1.2 GetLogicalDeviceDirectoryResponse
26 The GetLogicalDeviceDirectoryResponse service shall be defined as follows:
27 <s:element name="GetLogicalDeviceDirectoryResponse">
28 <s:complexType>
29 <s:choice>
30 <s:element name="LNRef" type="ews:tObjectReference" minOccurs="3" maxOccurs="unbounded"/>
32 </s:choice>
35 </s:complexType>
36 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 45 - 88/288/CDV
1 Table A-16 – GetLogicalDeviceDirectoryResponse

server.
3 A.5.3 LOGICAL-NODE class services mapping
4 The LOGICAL-NODE class services shall be mapped to web services as defined in Table
5 A-17.
6 Table A-17 – LOGICAL-NODE mapping
LOGICAL-NODE tLN
GetLogicalNodeDirectory GetLogicalNodeDirectory
8 A.5.3.1 GetLogicalNodeDirectory
9 A client shall use the GetLogicalNodeDirectory service to retrieve the LN namespace with all
10 DATA and Control Blocks (e.g. RCB or LCB) exposed, and thus accessible to a client ad-
11 dressing the Logical Node.
12
13 A.5.3.1.1 GetLogicalNodeDirectoryRequest
14 The GetLogicalNodeDirectoryRequest service shall be defined as follows:
15 <s:element name="GetLogicalNodeDirectoryRequest">
16 <s:complexType>
17 <s:sequence>
18 <s:element name="LNRef" type="ews:tObjectReference"/>
19 <s:element name="IEMcls" type="ews:tIEMcls"/>
20 </s:sequence>
23 </s:complexType>
24 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 46 - 88/288/CDV
2 Table A-18 – GetLogicalNodeDirectoryRequest

IEMcls Enumeration (“DATA”, “DATASET”, “BRCB”, “URCB”, “LCB”, “LOG”)
server.
4 A.5.3.1.2 GetLogicalNodeDirectoryResponse
5 The GetLogicalNodeDirectoryResponse service shall be defined as follows:
6 <s:element name="GetLogicalNodeDirectoryResponse">
7 <s:complexType>
8 <s:choice>
10 <s:element name="DATAname" type="ews:tObjectName"/>
11 <s:element name="DSname" type="ews:tObjectName"/>
12 <s:element name="BRCBname" type="ews:tObjectName"/>
13 <s:element name="URCBname" type="ews:tObjectName"/>
14 <s:element name="LCBname" type="ews:tObjectName"/>
15 <s:element name="LOGname" type="ews:tObjectName"/>
16 </s:choice>
18 </s:choice>
21 </s:complexType>
22 </s:element>
24 Table A-19 – GetLogicalNodeDirectoryResponse

server.
25
26 A.5.4 DATA class services mapping
27 The DATA class services shall be mapped to web services as defined in Table A-20.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 47 - 88/288/CDV
2 Table A-20 – Data mapping
DATA tDATA
GetDataValues GetDataValues
SetDataValues SetDataValues
GetDataDirectory GetDataDirectory
GetDataDefinition GetDataDefinition
4 A.5.4.1 GetDataValues
5 A.5.4.1.1 GetDataValuesRequest
6 The GetDataValuesRequest service shall be defined as follows:
7 <s:element name="GetDataValuesRequest">
8 <s:complexType>
9 <s:sequence>
10 <s:element name="Ref" type="ews:tFcdFcdaType" maxOccurs="unbounded"/>
11 </s:sequence>
14 </s:complexType>
15 </s:element>
17 Table A-21 – GetDataValuesRequest

Ref Reference of type FCD or FCDA as defined in IEC 61850-7-2.
server.
18
19 A.5.4.1.2 GetDataValuesResponse
20 The GetDataValuesResponse service shall be defined as follows:
21 <s:element name="GetDataValuesResponse">
22 <s:complexType>
23 <s:choice>
24 <s:sequence>
25 <s:element name="DataAttrVal" type="ews:tDataAttributeValue" minOccurs="0" maxOc-
26 curs="unbounded"/>
27 </s:sequence>
29 </s:choice>
32 </s:complexType>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 48 - 88/288/CDV
1 </s:element>
3 Table A-22 – GetDataValuesResponse

AccessResult Simple result string “Ok” stating the SetValue request was accepted.
server.
5 A.5.4.2 SetDataValues
6 A.5.4.2.1 SetDataValuesRequest
7 The SetDataValuesRequest service shall be defined as follows:
8 <s:element name="SetDataValuesRequest">
9 <s:complexType>
10 <s:sequence>
11 <s:element name="DataAttrVal" type="ews:tDataAttributeValue" maxOccurs="unbounded"/>
12 </s:sequence>
15 </s:complexType>
16 </s:element>
18 Table A-23 – SetDataValuesRequest

DataAttrVal Type referencing Value from DataRef contained in tDataAttributeValue type.
server.
19
20 A.5.4.2.2 SetDataValuesResponse
21 The GetDataValuesResponse service shall be defined as follows:

22 <s:element name="SetDataValuesResponse">
23 <s:complexType>
24 <s:sequence>
25 <s:choice>
26 <s:element name="AccessResult" type="ews:tResult" minOccurs="0"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 49 - 88/288/CDV
1 <s:element name="ServiceError" type="ews:tServiceError" minOccurs="0" maxOc-

3 </s:choice>
4 </s:sequence>
7 </s:complexType>
8 </s:element>
10 Table A-24 – SetDataValuesResponse

AccessResult Simple result string “Ok” stating the SetValue request was accepted.
server.
11
12 A.5.4.3 GetDataDirectory
13 A client shall use the GetDataDirectory service to retrieve the namespace of all DATA-
14 ATTRIBUTES exposed and thus accessible to a client addressing the DATA class.
15
16 A.5.4.3.1 GetDataDirectoryRequest
17
18 The GetDataDirectoryRequest service shall be defined as follows:
19 <s:element name="GetDataDirectoryRequest">
20 <s:complexType>
21 <s:sequence>
22 <s:element name="DataRef" type="ews:tObjectReference"/>
23 </s:sequence>
26 </s:complexType>
27 </s:element>
29 Table A-25 – GetDataDirectoryRequest

server.
30
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 50 - 88/288/CDV
1 A.5.4.3.2 GetDataDirectoryResponse
2 The GetDataDirectoryResponse service shall be defined as follows:
3 <s:element name="GetDataDirectoryResponse">
4 <s:complexType>
5 <s:choice>
6 <s:sequence>
7 <s:element name="DataName" type="ews:tObjectName" maxOccurs="unbounded"/>
8 <s:element name="DataAttrName" type="ews:tObjectName" maxOccurs="unbounded"/>
11 </s:sequence>
12 </s:choice>
15 </s:complexType>
16 </s:element>
18 Table A-26 – GetDataDirectoryResponse

server.
19
20
21 A.5.4.4 GetDataDefinition
22 A client shall use the GetDataDefinition service to retrieve the definitions of all DATA-
23 ATTRIBUTES exposed and thus accessible to a client addressing the DATA class.
24
25 A.5.4.4.1 GetDataDefinitionRequest
26 The GetDataDefinitionRequest service shall be defined as follows:

27 <s:element name="GetDataDefinitionRequest">
28 <s:complexType>
29 <s:sequence>
31 </s:sequence>
34 </s:complexType>
35 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 51 - 88/288/CDV
2 Table A-27 – GetDataDefinitionRequest

server.
3
4 A.5.4.4.2 GetDataDefinitionResponse
5 The GetDataDefinitionResponse shall be defined as follows:
6 <s:element name="GetDataDefinitionResponse">
7 <s:complexType>
8 <s:choice>
9 <s:sequence>
10 <s:element name="DataAttrDef" type="ews:tDataAttributeDefinition"/>
11 </s:sequence>
13 </s:choice>
16 </s:complexType>
17 </s:element>
19 Table A-28 – GetDataDefinitionResponse

DataAttributeDefinition String type is used in the WSDL specification
server.
20
21 A.5.5 DATA-SET class services mapping
22 A.5.5.1 General
23 The DataSet class shall be mapped to a list of items as defined in Table A-29.
24 Table A-29 – DATA-SET mapping
DATA-SET tDataSet
GetDataSetValues GetDataSetValues
SetDataSetValues SetDataSetValues
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 52 - 88/288/CDV
CreateDataSet CreateDataSet
DeleteDataSet DeleteDataSet
GetDataSetDirectory GetDataSetDirectory
2 A.5.5.2 GetDataSetValues
3 A.5.5.2.1 GetDataSetValuesRequest
4 The GetDataSetValuesRequest service shall be defined as follows:
5 <s:element name="GetDataSetValuesRequest">
6 <s:complexType>
7 <s:sequence>
8 <s:element name="DSRef" type="ews:tObjectReference"/>
9 </s:sequence>
12 </s:complexType>
13 </s:element>
15
16 Table A-30 – GetDataSetValuesRequest

server.
17
18 A.5.5.2.2 GetDataSetValuesResponse
19 The GetDataSetValuesResponse service shall be defined as follows:
20 <s:element name="GetDataSetValuesResponse">
21 <s:complexType>
22 <s:choice>
23 <s:sequence>
26 </s:sequence>
29 </s:choice>
32 </s:complexType>
33 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 53 - 88/288/CDV
2 Table A-31 – GetDataSetValuesResponse

DataAttrVal Type referencing Value from DataRef contained in tDataAttributeValue type..
server.
4 A.5.5.3 SetDataSetValues
5 A.5.5.3.1 SetDataSetValuesRequest
6 The SetDataSetValuesRequest service shall be defined as follows:
7 <s:element name="SetDataSetValuesRequest">
8 <s:complexType>
9 <s:sequence>
11 </s:sequence>
14 </s:complexType>
15 </s:element>
17
18 Table A-32 – SetDataSetValuesRequest

server.
19
20 A.5.5.3.2 SetDataSetValuesResponse
21 The SetDataSetValuesResponse service shall be defined as follows: <s:element
22 name="SetDataSetValuesResponse">
23 <s:complexType>
24 <s:sequence>
25 <s:choice>
26 <s:element name="Result" type="ews:tResult" minOccurs="0"/>
29 </s:choice>
30 </s:sequence>
33 </s:complexType>
34 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 54 - 88/288/CDV
2 Table A-33 – SetDataSetValuesResponse

DataAttrVal Type referencing Value from DataRef contained in tDataAttributeValue type..
Result Simple result string “Ok” stating the SetValue request was accepted.
server.
4 A.5.5.4 CreateDataSet
5 A.5.5.4.1 CreateDataSetRequest
6 The CreateDataSetRequest service shall be defined as follows:
7 <s:element name="CreateDataSetValuesRequest">
8 <s:complexType>
9 <s:sequence>
12 </s:sequence>
15 </s:complexType>
16 </s:element>
18 Table A-34 – CreateDataSetRequest

server.
19
20 A.5.5.4.2 CreateDataSetResponse
21 The CreateDataSetResponse service shall be defined as follows:
22 <s:element name="CreateDataSetValuesResponse">
23 <s:complexType>
24 <s:sequence>
25 <s:choice>
29 </s:choice>
30 </s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 55 - 88/288/CDV
1 </s:complexType>
2 </s:element>
4 Table A-35 – CreateDataSetResponse

server.
6 A.5.5.5 DeleteDataSet
7 A.5.5.5.1 DeleteDataSetRequest
8 The DeleteDataSetRequest service shall be defined as follows:
9 <s:element name="DeleteDataSetRequest">
10 <s:complexType>
11 <s:sequence>
13 </s:sequence>
16 </s:complexType>
17 </s:element>
19
20 Table A-36 – DeleteDataSetRequest

server.
21
22 A.5.5.5.2 DeleteDataSetResponse
23 The DeleteDataSetResponse service shall be defined as follows:

24 <s:element name="DeleteDataSetResponse">
25 <s:complexType>
26 <s:sequence>
27 <s:choice>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 56 - 88/288/CDV

3 </s:choice>
4 </s:sequence>
7 </s:complexType>
8 </s:element>
9
11 Table A-37 – DeleteDataSetResponse

server.
12
13 A.5.5.6 GetDataSetDirectory
14 A client shall use the GetDataSetDirectory service to retrieve a the namespace with all DATA
15 exposed and thus accessible to a client addressing the DATA-SET.
16
17 A.5.5.6.1 GetDataSetDirectoryRequest
18 The GetDataSetDirectoryRequest shall be defined as follows:
19 <s:element name="GetDataSetDirectoryRequest">
20 <s:complexType>
21 <s:sequence>
23 </s:sequence>
26 </s:complexType>
27 </s:element>
29 Table A-38 – GetDataSetDirectoryRequest

server.
30
31 A.5.5.6.2 GetDataSetDirectoryResponse
32 The GetDataSetDirectoryResponse shall be defined as follows:
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 57 - 88/288/CDV
1 <s:element name="GetDataSetDirectoryResponse">
2 <s:complexType>
3 <s:choice>
6 </s:choice>
9 </s:complexType>
10 </s:element>
12 Table A-39 – GetDataSetDirectoryResponse

server.
13
14 A.5.6 REPORT-CONTROL-BLOCK (RCB) class services mapping
15 The RCB class services shall be mapped to web services as defined in Table A-40.
16 Table A-40 – Report control block services mapping
REPORT-CONTROL-BLOCK
AddSubscription AddSubscription
RemoveSubscription RemoveSubscription
Report ReportRequest / ReportResponse
BRCB tBRCB
GetBRCBValues GetBRCBValues
SetBRCBValues SetBRCBValues
URCB tURCB
GetURCBValues GetURCBValues
SetURCBValues SetURCBValues
17
18 The web service approach imposes that the server responds to the requests sent by the cli-
19 ents. The reporting mechanism defined in the IEM services specified has the approach where
20 the server, after being requested, notifies the events collected to the client.
21 The client behaviour in the reporting procedure shall be as follows.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 58 - 88/288/CDV
1 When the client requests the AddSubscription service or activates the reporting forcing the
2 RptEna attribute to true using the SetURCBValues or SetBRCBValues services. The client
3 mapping shall send the corresponding web service. Apart from that the web service mapping
4 shall send periodically ReportRequest service to the server within the time window between
5 MinRequestTime and MaxRequestTime.
6 The client request shall be issued after the MinRequestTime has elapsed and before the
7 MaxRequestTime has been obtained. The client MinRequestTime is defined by the server and
8 informed to the client in the ReportResponse and is used by the server to balance load in a
9 controlled manner.The client MaxRequestTime is defined by the server in order to allow the
10 server to handle timeouts in a controlled manner.
11 When the client desires to terminate reception of reports it shall request an IEM RemoveSub-
12 scription or the SetURCBValues or SetBRCBValues services by forcing the RptEna attributes
13 to false. The mapping shall send the last ReportRequest web services followed by the web
14 service associated to the IEM service requested (RemoveSubscriptionRequest” ,
15 SetURCBValuesRequest, or SerBRCBValuesRequest).
16 The time windows defined by the Min-MaxRequestTime and the Min-MaxResponseTime shall
17 also be applied in the termination of a report request-response procedure.
18 The server behaviour in the reporting procedure shall be as follows.
19 When the server application receives a client ReportRequest service the server mapping shall
20 keep it stored together with the AssocID until the server desires to send the report. On the re-
21 ception of the client web service ReportRequest all the reports stored that match with the
22 specified AssocID requested shall be included in the response.
23 If there are no reports stored that match with the AssocID specified, the ReportResponse will
24 be sent empty (with no ReportFormats).
25 The server shall respond to the client ReportRequest after a MinResponseTime has elapsed
26 and before a MaxResponseTime has been obatined. The server MinResponseTime is defined
27 by the client and informed to the server in the ReportRequest in order to balance load on the
28 client in a controlled manner.The server MaxResponseTime is defiend by the client to allow
29 the client to handle timeouts in a controlled manner.
30 The time windows defined by the Min-MaxRequestTime and the Min-MaxResponseTime shall
31 also be applied in termination of a report request-respone procedure.
32 In order to keep track of the reporting sequence in case of association malfunction, lost con-
33 nections, buffer overflow etc. a server generated sequence number is given by the SqNum in
34 the ReportForemat. The client mapping is by receipt of the SqNum able to keep track of the
35 report sequence and detect if any report has been lost or a duplicate report has been re-
36 ceived. By using the EntryID the client is able to request a specific report lost during the as-
37 sociation. The more detailed processing of the SqNum and recovering of lost reports is im-
38 plementation specific and not concerned in this document. The SqNum shall be unique for
39 each association.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 59 - 88/288/CDV
2 Figure A-2– Reporting Services mechanisme (conceptual)
3 The reporting mechanisme specified has several benefits in complex communication environ-
4 ments with local and wide area networks involved including several layers of security obtaind
5 via firewalls and routers.
6 The services involved in reporting shall be as specified in the following clauses.
7 A.5.6.1 AddSubscription
8 A.5.6.1.1 AddSubscriptionRequest
9 The AddSubscriptionRequest service shall be defined as follows:
10 <s:element name="AddSubscriptionRequest">
11 <s:complexType>
12 <s:sequence>
13 <s:element name="RCBRef" type="ews:tObjectReference"/>
14 <s:element name="RCBType" type="ews:tRCBType"/>
15 <s:element name="RptID" type="ews:tstring65" minOccurs="0"/>
16 <s:element name="RptEna" type="s:boolean" minOccurs="0"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 60 - 88/288/CDV
1 <s:element name="DatSet" type="ews:tObjectReference" minOccurs="0"/>

2 <s:element name="OptFlds" type="ews:tOptFldsBRCB" minOccurs="0"/>
3 <s:element name="BufTm" type="s:unsignedInt" minOccurs="0"/>
4 <s:element name="TrgOp" type="ews:tTrgCond" minOccurs="0"/>
5 <s:element name="IntgPd" type="s:unsignedInt" minOccurs="0"/>
6 <s:element name="DSMbrRef" type="ews:tFcdFcdaType" minOccurs="0" maxOccurs="unbounded"/>
7 </s:sequence>
10 </s:complexType>
11 </s:element>
13
14 Table A-41 – AddSubscriptionRequest

server.
AddSubscriptionRequest shall be followed by a ReportRequest within the time window of MinRequest and
MaxRequestTime defined for the Report service.
Other element shall be as defined in IEC 61850-7-2.
15
16 A.5.6.1.2 AddSubscriptionResponse
17 The AddSubscriptionResponse service shall be defined as follows:

18 <s:element name="AddSubscriptionResponse">
19 <s:complexType>
20 <s:sequence>
21 <s:choice>
23 <s:element name="ServiceError" type="ews:tServiceError" minOccurs="0" maxOccurs="unbound"/>
24 </s:choice>
25 </s:sequence>
28 </s:complexType>
29 </s:element>
31 Table A-42 – AddSubscriptionResponse

server.
AddSubscriptionResponse shall be followed by a ReportResponse within the time window of MinResponse and
MaxResponseTime defined for the Report service.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 61 - 88/288/CDV
2 A.5.6.2 Remove Subscription
3 A.5.6.2.1 RemoveSubscriptionRequest
4 The RemoveSubscriptionRequest service shall be defined as follows:
5 <s:element name="RemoveSubscriptionRequest">
6 <s:complexType>
7 <s:sequence>
9 </s:sequence>
10 </s:complexType>
13 </s:element>
15
16 Table A-43 – RemoveSubscriptionRequest

server.
17
18 A.5.6.2.2 RemoveSubscriptionResponse
19 The RemoveSubscriptionResponse service shall be defined as follows:

20 <s:element name="RemoveSubscriptionResponse">
21 <s:complexType>
22 <s:sequence>
23 <s:choice>
27 </s:choice>
28 </s:sequence>
31 </s:complexType>
32 </s:element>
34 Table A-44 – RemoveSubscriptionResponse

Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 62 - 88/288/CDV

server.
2 A.5.6.2.3 ReportFormat
3 The ReportFormat service shall be as defined as follows.
4 <s:complexType name="tReportFormat">
5 <s:sequence>
6 <s:element name="RptID" type="ews:tstring65" minOccurs="1" maxOccurs="1"/>
7 <s:element name="OptFlds" type="ews:tOptFldsBRCB" minOccurs="1" maxOccurs="1"/>
8 
9 <s:element name="SqNum" type="s:unsignedShort" minOccurs="0" maxOccurs="1"/>
10 <s:element name="SubSqNum" type="s:unsignedShort" minOccurs="0" maxOccurs="1"/>
11 <s:element name="MoreSegFlw" type="s:boolean" minOccurs="1" maxOccurs="1"/>
12 
13 <s:element name="DatSet" type="ews:tObjectReference" minOccurs="0" maxOccurs="1"/>
14 
15 <s:element name="BufOvfl" type="s:boolean" minOccurs="0" maxOccurs="1"/>
16 
17 <s:element name="ConfRev" type="s:string" minOccurs="0" maxOccurs="1"/>
18 
19 
20 <s:element name="TimeOfEntry" type="s:string" minOccurs="0" maxOccurs="1"/>
21 
22 <s:element name="EntryID" type="s:string" minOccurs="0" maxOccurs="1"/>
23 <s:sequence>
24 <s:element name="EntryData" type="ews:tEntryData" minOccurs="0" maxOccurs="1"/>
25 </s:sequence>
26 </s:sequence>
29 </s:complexType>
31 Table A-45 – ReportFormat

server.
32
33 A.5.6.3 GetBRCBValues
34 A.5.6.3.1 GetBRCBValuesRequest
35 The GetBRCBvaluesRequest service shall be defined as follows:
36 <s:element name="GetBRCBValuesRequest">
37 <s:complexType>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 63 - 88/288/CDV
1 <s:element name="BRCBRef" type="ews:tObjectReference"/>

4 </s:complexType>
5 </s:element>
7 Table A-46 – GetBRCBValuesRequest

server.
9 A.5.6.3.2 GetBRCBValuesResponse
10 The GetBRCBvaluesResponse service shall be defined as follows:
11 <s:element name="GetBRCBValuesResponse">
12 <s:complexType>
13 <s:sequence>
14 <s:choice>
15 <s:sequence>
20 <s:element name="OptFlds" type="ews:tOptFldsBRCB"/>
26 <s:element name="EntryID" type="s:string"/>
28 </s:sequence>
29 <s:element name="ServiceError" type="ews:tServiceError" minOccurs="0"
30 maxOccurs="1"/>
31 </s:choice>
32 </s:sequence>
35 </s:complexType>
36 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 64 - 88/288/CDV
2 Table A-47 – DetBRCBValuesResponse

server.
4 A.5.6.4 SetBRCBValues
5 A.5.6.4.1 SetBRCBValuesRequest
6 The SetBRCBvaluesRequest service shall be defined as follows:
7 <s:element name="SetBRCBValuesRequest">
8 <s:complexType>
9 <s:sequence>
18 <s:element name="GI" type="s:boolean" minOccurs="0"/>
19 <s:element name="PurgeBuf" type="s:boolean" minOccurs="0"/>
20 <s:element name="EntryID" type="s:string" minOccurs="0"/>
21 </s:sequence>
24 </s:complexType>
25 </s:element>
27 Table A-48 – SetBRCBValuesRequest

server.
28
29 A.5.6.4.2 SetBRCBValuesResponse
30 The SetBRCBvaluesRequest service shall be defined as follows:
31 <s:element name="SetBRCBValuesResponse">
32 <s:complexType>
33 <s:sequence>
34 <s:choice>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 65 - 88/288/CDV

3 maxOccurs="unbounded"/>
4 </s:choice>
5 </s:sequence>
8 </s:complexType>
9 </s:element>
11 Table A-49 – SetBRCBValuesResponse

server.
12
13 A.5.6.5 GetURCBValues
14 A.5.6.5.1 GetURCBValuesRequest
15 The GetURCBvaluesRequest service shall be defined as follows:
16 <s:element name="GetURCBValuesRequest">
17 <s:complexType>
18 <s:sequence>
19 <s:element name="URCBRef" type="ews:tObjectReference"/>
20 </s:sequence>
23 </s:complexType>
24 </s:element>
26 Table A-50 – GetURCBValuesRequest

server.
27
28 A.5.6.5.2 GetURCBValuesResponse
29 The GetURCBvaluesRequest service shall be defined as follows:
30 <s:element name="GetURCBValuesResponse">
31 <s:complexType>
32 <s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 66 - 88/288/CDV
1 <s:choice>
2 <s:sequence>
5 <s:element name="Resv" type="s:boolean" minOccurs="0"/>
14 </s:sequence>
18 </s:choice>
19 </s:sequence>
22 </s:complexType>
23 </s:element>
25 Table A-51 – GetURCBValuesResponse

server.
26
27 A.5.6.6 SetURCBValues
28 A.5.6.6.1 SetURCBValuesRequest
29 The SetURCBvaluesRequest service shall be defined as follows:
30 <s:element name="SetURCBValuesRequest">
31 <s:complexType>
32 <s:sequence>
38 <s:element name="OptFlds" type="ews:tOptFldsURCB" minOccurs="0"/>
43 </s:sequence>
46 </s:complexType>
47 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 67 - 88/288/CDV
1 Table A-52 – SetURCBValuesRequest

server.
3 A.5.6.6.2 SetURCBValuesResponse
4 The SetURCBvaluesRequest service shall be defined as follows:
5 <s:element name="SetURCBValuesResponse">
6 <s:complexType>
7 <s:sequence>
8 <s:choice>
12 </s:choice>
13 </s:sequence>
16 </s:complexType>
17 </s:element>
19 Table A-53 – SetURCBValuesResponse

server.
20
21 A.5.6.6.3 ReportRequest
22 The ReportRequest service shall be defined as follows:
23 <s:element name="ReportRequest">
24 <s:complexType>
25 <s:sequence>
26 <s:element name="MaxResponseTime" type="ews:tTimeStamp" minOccurs="1"/>
27 <s:element name="MinRequestTime" type="ews:tTimeStamp" minOccurs="0"/>
28 </s:sequence>
31 </s:complexType>
32 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 68 - 88/288/CDV
1 Table A-54 – ReportRequest

MinRequestTime The MinRequestTime is defined by the client and informed to the server in the Repor-
tRequest and is an indication of the minimum time the client will wait between receiv-
ing a ReportResponse and sending the next ReportRequest on the same association
This waite time is used by the client to balance load in a controlled manner.
MaxResponseTime The MaxResponseTime is defiend by the client and informed to the server in order to
allow the client to handle timeouts in a controlled manner. When the MaxRespon-
seTime has expired the client shall assume the server to be inactive.
server.
3 A.5.6.6.4 ReportResponse
4 The ReportResponse service shall be defined as follows:
5 <s:element name="ReportResponse">
6 <s:complexType>
7 <s:choice>
8 <s:sequence>
9 <s:element name="ReportFormat" type="ews:tReportFormat" minOccurs="0" maxOc-
11 <s:element name="MaxRequestTime" type="ews:tTimeStamp" minOccurs="1"/>
12 <s:element name="MinResponseTime" type="ews:tTimeStamp" minOccurs="0"/>
13 </s:sequence>
15 </s:choice>
18 </s:complexType>
19 </s:element>
21 Table A-55 – ReportResponse

MinResponseTime The MinResponseTime is defined by the server and informed to the client in the Re-
portResponse and is an indication of the minimum time the server will wait between
responding a ReportRequest and sending the next ReportResponse on the same as-
sociation This waite time is used by the server to balance load in a controlled man-
ner.
MaxRequestTime The MaxRequestTime is defined by the server and informed to the client in the Re-
portResponse service in order to allow the server to handle timeouts in a controlled
manner. When the MaxRequestTime has expired the server shall assume the client to
be inactive.
server.
22
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 69 - 88/288/CDV
1 A.5.7 LOG-CONTROL-BLOCK (LCB)class services mapping
2 The LCB class services shall be mapped to web services as defined in Table A-56.
3 Table A-56 – LOG-CONTROL-BLOCK services mapping
LOG-CONTROL-BLOCK tLCB
GetLCBValues GetLCBValues
SetLCBValues SetLCBValues
5 A.5.7.1 GetLCBValues
6 A.5.7.1.1 GetLCBValuesRequest
7 The GetLCBValuesRequest service shall be defined as follows:
8 <s:element name="GetLCBValuesRequest">
9 <s:complexType>
10 <s:sequence>
11 <s:element name="LCBRef" type="ews:tObjectReference"/>
12 </s:sequence>
15 </s:complexType>
16 </s:element>
18 Table A-57 – GetLCBValuesRequest

server.
19
20 A.5.7.1.2 GetLCBValuesResponse
21 The GetLCBValuesResponse service shall be defined as follows:
22 <s:element name="GetLCBValuesResponse">
23 <s:complexType>
24 <s:sequence>
25 <s:choice>
26 <s:sequence>
32 </s:sequence>
34 </s:choice>
35 </s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 70 - 88/288/CDV
1 </s:complexType>
2 </s:element>
4 Table A-58 – GetLCBValuesResponse

server.
6 A.5.7.2 SetLCBValues
7 The attributes and behaviour of the LCB shall be as defined in IEC 61850-7-2.
8 A.5.7.2.1 SetLCBValuesRequest
9 The SetLCBValuesRequest service shall be defined as follows:
10 <s:element name="SetLCBValuesRequest">
11 <s:complexType>
12 <s:sequence>
14 <s:element name="LogEna" type="s:boolean" minOccurs="0"/>
16 <s:element name="OptFlds" type="ews:tOptFldsLCB" minOccurs="0"/>
18 <s:element name="LogRef" type="ews:tObjectReference" minOccurs="0"/>
19 </s:sequence>
22 </s:complexType>
23 </s:element>
25 Table A-59 – SetLCBValuesRequest

server.
26
27 A.5.7.2.2 SetLCBValuesResponse
28 The SetLCBValuesResponse service shall be defined as follows:
29 <s:element name="SetLCBValuesResponse">
30 <s:complexType>
31 <s:sequence>
32 <s:choice>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 71 - 88/288/CDV

3 </s:choice>
4 </s:sequence>
7 </s:complexType>
8 </s:element>
10 Table A-60 – SetLCBValuesResponse

server.
11
12 A.5.8 LOG class services mapping
13 The LOG class services shall be mapped to web services as defined in Table A-61.
14 Table A-61 – Log class services mapping
LOG tLOG
GetLogStatusValues GetLogStatusValues
QueryLogByTime QueryLogByTime
QueryLogAfter QueryLogAfter
15
16 A.5.8.1 GetLogStatusValues
17 A.5.8.1.1 GetLogStatusValuesRequest
18 The GetLogStatusValuesRequest service shall be defined as follows:
19 <s:element name="GetLogStatusValuesRequest">
20 <s:complexType>
21 <s:sequence>
23 </s:sequence>
26 </s:complexType>
27 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 72 - 88/288/CDV
2 Table A-62 – GetLogStatusValuesRequest

server.
4 A.5.8.1.2 GetLogStatusValuesResponse
5 The GetLogStatusValuesResponse service shall be defined as follows:
6 <s:element name="GetLogStatusValuesResponse">
7 <s:complexType>
8 <s:choice>
9 <s:sequence>
14 </s:sequence>
16 </s:choice>
19 </s:complexType>
20 </s:element>
22 Table A-63 – GetLogStatusValuesResponse

server.
23
24 A.5.8.2 QueryLogByTime
25 A.5.8.2.1 QueryLogByTimeRequest
26 The QueryLogByTimeRequest service shall be defined as follows:
27 <s:element name="QueryLogByTimeRequest">
28 <s:complexType>
29 <s:sequence>
31 <s:element name="StartTime" type="ews:tTimeStamp" minOccurs="0"/>
32 <s:element name="StopTime" type="ews:tTimeStamp" minOccurs="0"/>
33 <s:element name="DataFilter" type="ews:tFcdFcdaType" minOccurs="0" maxOccurs="unbounded"/>
34 </s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 73 - 88/288/CDV

3 </s:complexType>
4 </s:element>
6 Table A-64 – GetLogByTimeRequest

server.
8 A.5.8.2.2 QueryLogByTimeResponse
9 The QueryLogByTimeResponse service shall be defined as follows:
10 <s:element name="QueryLogByTimeResponse">
11 <s:complexType>
12 <s:sequence>
13 <s:choice>
14 <s:sequence>
16 </s:sequence>
18 </s:choice>
19 </s:sequence>
22 </s:complexType>
23 </s:element>
25 Table A-65 – QueryLogByTimeResponse

server.
26
27 A.5.8.3 QueryLogAfter
28 A.5.8.3.1 QueryLogAfterRequest
29 The QueryLogAfterRequest service shall be defined as follows:
30 <s:element name="QueryLogAfterRequest">
31 <s:complexType>
32 <s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 74 - 88/288/CDV
1 <s:element name="EntryID" type="s:unsignedInt" minOccurs="0"/>

2 <s:element name="DataFilter" type="ews:tFcdFcdaType" minOccurs="0" maxOccurs="unbounded"/>
3 </s:sequence>
6 </s:complexType>
7 </s:element>
9 Table A-66 – QueryLogAfterRequest

server.
10
11 A.5.8.3.2 QueryLogAfterResponse
12 The QueryLogAfterResponse service shall be defined as follows:
13 <s:element name="QueryLogAfterResponse">
14 <s:complexType>
15 <s:sequence>
16 <s:choice>
17 <s:sequence>
19 </s:sequence>
20 <s:element name="Log" type="ews:tLOG"/>
23 </s:choice>
24 </s:sequence>
27 </s:complexType>
28 </s:element>
30 Table A-67 – QueryLogAfterResponse

server.
31
32 A.5.9 CONTROL class services mapping
33 The CONTROL class services shall be mapped to web services as defined in Table A-68.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 75 - 88/288/CDV
1 Table A-68 – Control class services mapping
CONTROL CONTROL
Select Select
SelectWithValue SelectWithValue
Cancel Cancel
Operate Operate
CommandTermination CommandTermination
TimeActivatedOperate TimeActivatedOperate
3 A.5.9.1 Select
4 The Select services shall be defined as follows:
5 A.5.9.1.1 SelectRequest
6 <s:element name="SelectRequest">
7 <s:complexType>
8 <s:sequence>
9 <s:element name="ControlObjectRef" type=" ews:tObjectReference "/>
10 </s:sequence>
13 </s:complexType>
14 </s:element>
16
17 Table A-69 – SelectRequest

server.
18
19 A.5.9.1.2 SelectResponse
20 <s:element name="SelectResponse">
21 <s:complexType>
22 <s:sequence>
24 </s:sequence>
27 </s:complexType>
28 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 76 - 88/288/CDV
2 Table A-70 – SelectResponse

server.
4 A.5.9.2 SelectWithValue
5 The SelectWithValue services shall be defined as follows:
6 A.5.9.2.1 SelectWithValueRequest
7
8 <s:element name="SelectWithValueRequest">
9 <s:complexType>
10 <s:sequence>
12 <s:element name="Value" type=" ews:tControlValue "/>
13 <s:element name="T" type=" ews:tTimeStamp "/>
14 <s:element name="Test" type=" s:boolean "/>
15 <s:element name="Check" type=" ews:tCheck "/>
16 </s:sequence>
19 </s:complexType>
20 </s:element>
22
23 Table A-71 – SelectWithValueRequest

server.
24
25 A.5.9.2.2 SelectWithValueResponse
26 <s:element name="SelectWithValueResponse">
27 <s:complexType>
28 <s:sequence>
33 <s:element name="AddCause" type="ews:tAddCause" minOccurs="0" maxOccurs="1"/>
34 </s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 77 - 88/288/CDV

2 </s:complexType>
3 </s:element>
5 Table A-72 – SelectWithValueResponse
6
server.
8 A.5.9.3 Cancel
9 The Cancel services shall be defined as follows:
10 A.5.9.3.1 CancelRequest
11 <s:element name="CancelRequest">
12 <s:complexType>
13 <s:sequence>
18 </s:sequence>
21 </s:complexType>
22 </s:element>
24
25 Table A-73 – CancelRequest

server.
26
27 A.5.9.3.2 CancelResponse
28 <s:element name="CancelResponse">
29 <s:complexType>
30 <s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 78 - 88/288/CDV
1 </s:sequence>
4 </s:complexType>
5 </s:element>
7 Table A-74 – CancelResponse

server.
9 A.5.9.4 Operate
10 The Operate services shall be defined as follows:
11 A.5.9.4.1 OperateRequest
12 <s:element name="OperateRequest">
13 <s:complexType>
14 <s:sequence>
20 </s:sequence>
23 </s:complexType>
24 </s:element>
26
27 Table A-75 – OperateRequest

server.
28
29 A.5.9.4.2 OperateResponse
30 <s:element name="OperateResponse">
31 <s:complexType>
32 <s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 79 - 88/288/CDV

3 </s:sequence>
6 </s:complexType>
7 </s:element>
9 Table A-76 – OperateResponse

server.
10
11 A.5.9.5 CommandTermination
12 The CommandTermination services shall be defined as follows:
13 A.5.9.5.1 CommandTerminationRequest
14 <s:element name="CommandTerminationRequest">
15 <s:complexType>
16 <s:sequence>
17 <s:element name="ControlObjectRef" type="ews:tObjectReference"/>
18 <s:element name="T" type="ews:tTimeStamp"/>
19 <s:element name="Test" type="s:boolean"/>
20 </s:sequence>
22 <s:attribute name="AssocID" type="ews:tAssocID" use="required"/>
23 </s:complexType>
24 </s:element>
26
27 Table A-77 – CommandTermonationRequest

server.
28
29 A.5.9.5.2 CommandTerminationResponse
30 <s:element name="CommandTerminationResponse">
31 <s:complexType>
32 <s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 80 - 88/288/CDV

2 </s:sequence>
5 </s:complexType>
6 </s:element>
8 Table A-78 – CommandTerminationResponse

server.
10 A.5.9.6 TimeActivatedOperate
11 The TimeActivatedOperate service shall be defined as follows:
12 A.5.9.6.1 TimeActivatedOperateRequest
13 <s:element name="TimeActivateOperateRequest">
14 <s:complexType>
15 <s:sequence>
21 </s:sequence>
24 </s:complexType>
25 </s:element>
27
28 Table A-79 – TimeActivatedOperateRequest

server.
29
30 A.5.9.6.2 TimeActivatedOperateResponse
31 <s:element name="TimeActivateOperateResponse">
32 <s:complexType>
33 <s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 81 - 88/288/CDV

3 <s:choice>
4 <s:element name="AddCause" type="ews:tAddCause"/>
5 <s:element name="TimOperRsp" type="ews:tTimOperRsp"/>
6 </s:choice>
7 </s:sequence>
10 </s:complexType>
11 </s:element>
13 Table A-80 – TimeActivatedOperateResponse

server.
14
15 A.6 Protocol stack details
16 To be compliant with this mapping, the following stack of protocols shall be used.
17 The protocols TCP shall be the basic transport layer protocol and IP shall be the basic network layer
18 protocols provided for the Web Services mapping. Specifications for the data link layer and the physi-
19 cal layer are implementation specific and beyond the scope of the IEC 61400-25 series.
20
21 Table A-81 – Protocol stack selections
OSI model Specification M/O

layer
Service specifi- Protocol
Name
cation specification
Application Web Services M
SOAP SOAP ver 1.1 M
HTTP ver 1.1 RFC 2616, RFC 2617 M
SSL/TLS ver. 1.0 RFC 2246 O
Presentation - -
Session - -
Transport Transmission Contol Protocol (TCP) RFC 793 M
Network Internet Protocol IPver. 4 (ICMPv4) or IP RFC 792, RFC 791 M
ver.6(ICMPv6)
An Ethernet Address Resolution Protocol RFC 826 M
(ARP)
Broadcasting Internet Datagrams RFC 922 M
RFC 950
RFC 919
Host Extensions for IP Multicasting RFC 1112 M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 82 - 88/288/CDV
OSI model Specification M/O

layer
Service specifi- Protocol
Name
cation specification
Data Link Implementation specific and beyond the scope -
Layer of the IEC 61400-25 series.
Physical Implementation specific and beyond the scope -
layer of the IEC 61400-25 series.
2 A.7 The WSDL specification for the mapping to Web Services
3 The WSDL specification for the mapping to web servces shall be as defined as given in the
4 text following. The style used for the WSDL description is the litteral/wrapped style.
5 <?xml version="1.0" encoding="UTF-8"?>

6 <definitions xmlns:ews="http://iec.ch/61400/ews/1.0/"
7 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
9 xmlns:s="http://www.w3.org/2001/XMLSchema"
10 xmlns="http://schemas.xmlsoap.org/wsdl/"
11 targetNamespace="http://iec.ch/61400/ews/1.0/">
12 <types>
13 <s:schema targetNamespace="http://iec.ch/61400/ews/1.0/"
15 xmlns:sc="http://www.w3.org/2001/XMLSchema"
16 xmlns:ews="http://iec.ch/61400/ews/1.0/"
17 elementFormDefault="qualified">
18 
21 
31 
34 <s:simpleType name="tObjectName">
35 <s:annotation>
36 <s:documentation>Name of an instance of a class of a single hierarchy level</s:documentation>
37 </s:annotation>
38 <s:restriction base="s:string">
39 <s:maxLength value="32"/>
40 </s:restriction>
41 </s:simpleType>
42 
44 <s:simpleType name="tObjectReference">
45 <s:annotation>
46 <s:documentation>ObjectReference comprises the whole path-name of an instance of a class that
47 identifies the instance uniquely</s:documentation>
48 </s:annotation>
51 </s:restriction>
52 </s:simpleType>
53 
55 <s:simpleType name="tInt24">
56 <s:restriction base="s:integer">
57 <s:minInclusive value="-8388608"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 83 - 88/288/CDV
1 <s:maxInclusive value="8388607"/>
2 </s:restriction>
3 </s:simpleType>
4 
6 <s:simpleType name="tInt24u">
8 <s:minInclusive value="0"/>
10 </s:restriction>
11 </s:simpleType>
12 
14 <s:simpleType name="tInt32">
16 <s:minInclusive value="-4294967296"/>
18 </s:restriction>
19 </s:simpleType>
20 
22 <s:simpleType name="tInt32u">
24 <s:minInclusive value="0"/>
26 </s:restriction>
27 </s:simpleType>
28 
30 <s:simpleType name="tstring36">
33 </s:restriction>
34 </s:simpleType>
35 
37 <s:simpleType name="tstring65">
40 </s:restriction>
41 </s:simpleType>
42 
44 <s:simpleType name="tHexString">
46 <s:pattern value="([0-9]|[a-f]|[A-F])"/>
47 </s:restriction>
48 </s:simpleType>
49 
51 <s:simpleType name="tOctetString64">
52 <s:restriction base="ews:tHexString">
54 </s:restriction>
55 </s:simpleType>
56 
58 <s:simpleType name="tEntryID">
59 <s:restriction base="ews:tHexString">
61 </s:restriction>
62 </s:simpleType>
63 
64 
65 
66 <s:simpleType name="tTimeAccuracy">
67 <s:restriction base="s:byte">
68 <s:enumeration value="7"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 84 - 88/288/CDV
3 </s:restriction>
4 </s:simpleType>
5 
7 <s:complexType name="tTimeQuality">
8 <s:annotation>
9 <s:documentation>LSK = LeapSecondsKnown, CF = Clock Failure, CNS = ClockNotSunchronised,
10 TA = Time Accuracy</s:documentation>
11 </s:annotation>
12 <s:sequence>
13 <s:element name="LSK" type="s:boolean"/>
14 <s:element name="CF" type="s:boolean"/>
15 <s:element name="CNS" type="s:boolean"/>
16 <s:element name="TA" type="ews:tTimeAccuracy"/>
17 </s:sequence>
18 </s:complexType>
19 
21 <s:complexType name="tTimeStamp">
22 <s:annotation>
23 <s:documentation>SecSE = SecondsSinceEpoch, FracOfSec = FractionsOfSecond, Tq = TimeQual-
24 ity</s:documentation>
25 </s:annotation>
26 <s:sequence>
27 <s:element name="SecSE" type="s:unsignedInt"/>
28 <s:element name="FracOfSec" type="ews:tInt24u"/>
29 <s:element name="Tq" type="ews:tTimeQuality"/>
30 </s:sequence>
31 </s:complexType>
32 
34 
35 
37 <s:simpleType name="tValidity">
39 <s:enumeration value="good"/>
40 <s:enumeration value="invalid"/>
41 <s:enumeration value="reserved"/>
42 <s:enumeration value="questionable"/>
43 </s:restriction>
44 </s:simpleType>
45 
47 <s:complexType name="tDetailQual">
48 <s:attribute name="overflow" type="s:boolean" default="false"/>
49 <s:attribute name="outOfRange" type="s:boolean" default="false"/>
50 <s:attribute name="badReference" type="s:boolean" default="false"/>
51 <s:attribute name="oscillatory" type="s:boolean" default="false"/>
52 <s:attribute name="failure" type="s:boolean" default="false"/>
53 <s:attribute name="oldData" type="s:boolean" default="false"/>
54 <s:attribute name="inconsistent" type="s:boolean" default="false"/>
55 <s:attribute name="inaccurate" type="s:boolean" default="false"/>
56 </s:complexType>
57 
59 <s:simpleType name="tSource">
61 <s:enumeration value="process"/>
62 <s:enumeration value="substituted"/>
63 </s:restriction>
64 </s:simpleType>
65 
67 <s:complexType name="tQuality">
68 <s:annotation>
69 <s:documentation>As defined in IEC 61400-25-2 clause 7.2.3 </s:documentation>
70 </s:annotation>
71 <s:sequence>
72 <s:element name="Validity" type="ews:tValidity"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 85 - 88/288/CDV
1 <s:element name="DetailQual" type="ews:tDetailQual"/>

2 <s:element name="Source" type="ews:tSource"/>
3 </s:sequence>
4 <s:attribute name="test" type="s:boolean" default="false" />
5 <s:attribute name="operatorBlock" type="s:boolean" default="false" />
6 </s:complexType>
7 
9 
10 
12 <s:complexType name="tArray">
13 <s:sequence>
14 <s:element name="arrayElem" type="ews:tBasicType" maxOccurs="unbounded"/>
15 </s:sequence>
16 </s:complexType>
17 
19 <s:complexType name="tBasicType">
20 <s:choice>
21 <s:element name="Boolean" type="s:boolean"/>
22 <s:element name="int8" type="s:byte"/>
23 <s:element name="int16" type="s:short"/>
24 <s:element name="int24" type="ews:tInt24"/>
25 <s:element name="int32" type="ews:tInt32"/>
26 <s:element name="int128" type="s:integer"/>
27 <s:element name="int8u" type="s:unsignedByte"/>
28 <s:element name="int16u" type="s:unsignedShort"/>
29 <s:element name="int24u" type="ews:tInt24u"/>
30 <s:element name="int32u" type="ews:tInt32u"/>
31 <s:element name="float32" type="s:float"/>
32 <s:element name="float64" type="s:double"/>
33 <s:element name="enum" type="s:string"/>
34 <s:element name="codedEnum" type="s:string"/>
35 <s:element name="octetString" type="ews:tHexString"/>
36 <s:element name="visibleString" type="s:string"/>
37 <s:element name="unicodeString" type="s:string"/>
38 <s:element name="quality" type="ews:tQuality"/>
39 <s:element name="timeStamp" type="ews:tTimeStamp"/>
40 <s:element name="array" type="ews:tArray"/>
41 </s:choice>
42 <s:attribute name="pos" type="s:integer" use="optional"/>
43 </s:complexType>
44 
46 <s:simpleType name="tTrgCond">
47 <s:annotation>
48 <s:documentation>Trigger conditions definitions</s:documentation>
49 </s:annotation>
51 <s:enumeration value="dchg"/>
52 <s:enumeration value="qchg"/>
53 <s:enumeration value="dupd"/>
54 <s:enumeration value="integrity"/>
55 <s:enumeration value="genrInterg"/>
56 </s:restriction>
57 </s:simpleType>
58 
60 <s:simpleType name="tFC">
61 <s:annotation>
62 <s:documentation>Functional Constaint definitions</s:documentation>
63 </s:annotation>
65 <s:enumeration value="ST"/>
66 <s:enumeration value="MX"/>
67 <s:enumeration value="CO"/>
68 <s:enumeration value="SP"/>
69 <s:enumeration value="CF"/>
70 <s:enumeration value="DC"/>
71 <s:enumeration value="EX"/>
72 <s:enumeration value="BR"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 86 - 88/288/CDV
1 <s:enumeration value="RP"/>
2 <s:enumeration value="LG"/>
3 </s:restriction>
4 </s:simpleType>
5 
8 <s:annotation>
9 <s:documentation>Container for DAType</s:documentation>
10 </s:annotation>
11 <s:sequence>
15 <s:element name="PrimComp" type="ews:tBasicType" maxOccurs="1"/>
16 </s:choice>
17 
18 </s:sequence>
19 </s:complexType>
20 
24 <s:annotation>
25 <s:documentation>Container for DataAttributes</s:documentation>
26 </s:annotation>
27 <s:sequence>
28 <s:element name="DAType" type="ews:tDAType"/>
29 <s:element name="FC" type="ews:tFC"/>
31 </s:sequence>
32 </s:complexType>
33 
35 <s:complexType name="tSimpleData">
36 <s:annotation>
37 <s:documentation>Container for Common-Data Class</s:documentation>
38 </s:annotation>
39 <s:sequence>
42 <s:element name="DataAttr" type="ews:tDataAttribute"/>
43 </s:sequence>
44 </s:sequence>
45 </s:complexType>
46 
50 <s:annotation>
51 <s:documentation>Container for DATA object</s:documentation>
52 </s:annotation>
53 <s:sequence>
56 <s:element name="DataAttr" type="ews:tDataAttribute" minOccurs="0" maxOc-
58 
60 
61 
63 <s:element name="CompositeCDC" type="ews:tDATA" minOccurs="0" maxOc-
65 <s:element name="SimpleCDC" type="ews:tSimpleData" minOccurs="0" maxOc-
67 </s:sequence>
68 </s:sequence>
69 </s:complexType>
70 
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 87 - 88/288/CDV
2 <s:annotation>
3 <s:documentation>Container for Logical Node object</s:documentation>
4 </s:annotation>
5 <s:sequence>
13 </s:sequence>
14 </s:complexType>
15 
19 <s:annotation>
20 <s:documentation>Container for Logical Device object</s:documentation>
21 </s:annotation>
22 <s:sequence>
25 </s:sequence>
26 </s:complexType>
27 
30 <s:complexType name="tServer">
31 <s:annotation>
32 <s:documentation>Container for Server object</s:documentation>
33 </s:annotation>
34 <s:sequence>
35 <s:element name="ServerAccessPoint" type="s:string" maxOccurs="unbounded"/>
36 <s:element name="LD" type="ews:tLD" maxOccurs="unbounded"/>
37 </s:sequence>
38 </s:complexType>
39 
41 
43 
45 <s:complexType name="tFCD">
46 <s:annotation>
47 <s:documentation>Functionally Constrained Data</s:documentation>
48 </s:annotation>
49 <s:sequence>
50 <s:element name="DataRef" type="ews:tObjectReference" minOccurs="0"/>
52 </s:sequence>
53 </s:complexType>
54 
56 <s:complexType name="tFCDA">
57 <s:annotation>
58 <s:documentation>Functionally Constrained DataAttribute</s:documentation>
59 </s:annotation>
60 <s:sequence>
61 <s:element name="DataAttrRef" type="ews:tObjectReference" minOccurs="0"/>
63 </s:sequence>
64 </s:complexType>
65 
67 <s:complexType name="tFcdFcdaType">
68 <s:annotation>
69 <s:documentation>DATA-SET Member reference type</s:documentation>
70 </s:annotation>
71 <s:sequence>
72 <s:choice>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 88 - 88/288/CDV
1 <s:element name="FcdRef" type="ews:tFCD"/>

2 <s:element name="FcdaRef" type="ews:tFCDA"/>
3 </s:choice>
4 </s:sequence>
5 </s:complexType>
6 
8 <s:complexType name="tDATASet">
9 <s:annotation>
10 <s:documentation>Container for DATA-SET object</s:documentation>
11 </s:annotation>
12 <s:sequence>
13 <s:element name="DSName" type="ews:tObjectName"/>
15 </s:sequence>
16 </s:complexType>
17 
19 <s:complexType name="tOptFldsBRCB">
20 <s:annotation>
21 <s:documentation>Optional fields for BRCB</s:documentation>
22 </s:annotation>
23 <s:sequence>
29 <s:element name="bufOvfl" type="s:boolean"/>
30 <s:element name="entryID" type="s:boolean"/>
31 <s:element name="configRef" type="s:boolean"/>
32 </s:sequence>
33 </s:complexType>
34 
36 <s:complexType name="tBRCB">
37 <s:annotation>
38 <s:documentation>Container for BUFFERED-REPORT-CONTROL-BLOCK ob-
39 ject</s:documentation>
40 </s:annotation>
41 <s:sequence>
42 <s:element name="BRCBName" type="ews:tObjectName"/>
56 </s:sequence>
57 </s:complexType>
58 
60 <s:complexType name="tOptFldsURCB">
61 <s:annotation>
62 <s:documentation>Optional fields for URCB</s:documentation>
63 </s:annotation>
64 <s:sequence>
72 <s:element name="configRev" type="s:boolean"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 89 - 88/288/CDV
1 </s:sequence>
2 </s:complexType>
3 
5 <s:complexType name="tURCB">
6 <s:annotation>
7 <s:documentation>Container for UNBUFFERED-REPORT-CONTROL-BLOCK ob-
8 ject</s:documentation>
9 </s:annotation>
10 <s:sequence>
11 <s:element name="URCBName" type="ews:tObjectName"/>
23 </s:sequence>
24 </s:complexType>
25 
27 <s:complexType name="tOptFldsLCB">
28 <s:annotation>
29 <s:documentation>Optional fields for LCB</s:documentation>
30 </s:annotation>
31 <s:sequence>
32 <s:element name="ReasFI" type="s:boolean"/>
33 </s:sequence>
34 </s:complexType>
35 
37 <s:complexType name="tLCB">
38 <s:annotation>
39 <s:documentation>Container for LOG-CONTROL-BLOCK object</s:documentation>
40 </s:annotation>
41 <s:sequence>
42 <s:element name="LCBName" type="ews:tObjectName"/>
45 <s:element name="OptFlds" type="ews:tOptFldsLCB"/>
49 </s:sequence>
50 </s:complexType>
51 
54 <s:complexType name="tEntryData">
55 <s:sequence>
56 
57 <s:element name="DSMemberRef" type="ews:tFcdFcdaType" minOccurs="0" maxOccurs="1"/>
58 <s:element name="Value" type="ews:tDataAttributeValue" minOccurs="1" maxOccurs="unbounded" />
59 
60 <s:element name="ReasonCode" type="ews:tTrgCond" minOccurs="0" maxOccurs="1"/>
61 </s:sequence>
62 </s:complexType>
63 
65 <s:complexType name="tLOGEntry">
66 <s:sequence>
70 <s:element name="EntryData" type="ews:tEntryData"/>
71 </s:sequence>
72 </s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 90 - 88/288/CDV
1 </s:complexType>
2 
4 <s:complexType name="tLOG">
5 <s:annotation>
6 <s:documentation>Container for LOG object</s:documentation>
7 </s:annotation>
8 <s:sequence>
9 <s:element name="LogName" type="ews:tObjectName"/>
16 </s:sequence>
17 </s:sequence>
18 </s:complexType>
19 
22 
25 <s:simpleType name=”ews:tAssocID”>
26 <s:annotation>
27 <s:documentation>Association Identifier returned in the positive confimation of the Associate service
28 and used in the Reporting Services as well as the Control Model to identify who is performing the control or-
29 der</s:documentation>
30 </s:annotation>
33 </s:restriction>
34 </s:simpleType>
35 
37 <s:simpleType name="tServiceError">
38 <s:annotation>
39 <s:documentation>The service error code for negative service responses</s:documentation>
40 </s:annotation>
42 <s:enumeration value="instance-not-available"/>
43 <s:enumeration value="instance-in-use"/>
44 <s:enumeration value="access-violation"/>
45 <s:enumeration value="access-not-allowed-in-current-state"/>
46 <s:enumeration value="parameter-value-inappropriate"/>
47 <s:enumeration value="parameter-value-inconsistent"/>
48 <s:enumeration value="class-not-supported"/>
49 <s:enumeration value="instance-locked-by-other-client"/>
50 <s:enumeration value="control-must-be-selected"/>
51 <s:enumeration value="type-conflict"/>
52 <s:enumeration value="failed-due-to-communications-constraint"/>
53 <s:enumeration value="failed-due-to-server-constraint"/>
54 <s:enumeration value="application-unreachable"/>
56 <s:enumeration value="memory-unavailable"/>
57 <s:enumeration value="processor-resource-unavailable"/>
59 </s:restriction>
60 </s:simpleType>
61 
65 
67 <s:simpleType name="tObjectClass">
68 <s:annotation>
69 <s:documentation>ObjectClass to distinguise LDObject or FileName</s:documentation>
70 </s:annotation>
72 <s:enumeration value="LD"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 91 - 88/288/CDV
1 </s:restriction>
2 </s:simpleType>
3 
6 <s:simpleType name="tIEMcls">
8 <s:enumeration value="DATA"/>
9 <s:enumeration value="DATASET"/>
10 <s:enumeration value="BRCB"/>
11 <s:enumeration value="URCB"/>
12 <s:enumeration value="LCB"/>
13 <s:enumeration value="LOG"/>
14 </s:restriction>
15 </s:simpleType>
16 
19 
22 <s:simpleType name="tAddCause">
23 <s:annotation>
24 <s:documentation>Additional Cause Diagnosis used in the negative control responses. It can include
25 all the ServiceError</s:documentation>
26 </s:annotation>
28 <s:enumeration value="instance-not-available"/>
29 <s:enumeration value="instance-in-use"/>
30 <s:enumeration value="access-violation"/>
31 <s:enumeration value="access-not-allowed-in-current-state"/>
32 <s:enumeration value="parameter-value-inappropriate"/>
33 <s:enumeration value="parameter-value-inconsistent"/>
34 <s:enumeration value="class-not-supported"/>
35 <s:enumeration value="instance-locked-by-other-client"/>
36 <s:enumeration value="control-must-be-selected"/>
37 <s:enumeration value="type-conflict"/>
38 <s:enumeration value="failed-due-to-communications-constraint"/>
39 <s:enumeration value="failed-due-to-server-constraint"/>
40 <s:enumeration value="application-unreachable"/>
42 <s:enumeration value="memory-unavailable"/>
43 <s:enumeration value="processor-resource-unavailable"/>
44 <s:enumeration value="blocked-by-switching-hierarchy"/>
45 <s:enumeration value="select-failed"/>
46 <s:enumeration value="invalid-position"/>
47 <s:enumeration value="position-reached"/>
48 <s:enumeration value="parameter-change-in-execution"/>
49 <s:enumeration value="command-already-in-execution"/>
50 <s:enumeration value="step-limit"/>
51 <s:enumeration value="blocked-by-mode"/>
52 <s:enumeration value="blocked-by-process"/>
53 <s:enumeration value="blocked-by-interlocking"/>
54 <s:enumeration value="blocked-by-synchrocheck"/>
55 <s:enumeration value="command-already-in-execution"/>
56 <s:enumeration value="blocked-by-health"/>
57 <s:enumeration value="1-of-n-control"/>
58 <s:enumeration value="abortion-by-cancel"/>
59 <s:enumeration value="time-limit-over"/>
60 <s:enumeration value="abortion-by-trip"/>
61 <s:enumeration value="unknown"/>
62 <s:enumeration value="not-supported"/>
63 </s:restriction>
64 </s:simpleType>
65 
68 <s:complexType name="tCheck">
69 <s:annotation>
70 <s:documentation>Container for Check Conditions</s:documentation>
71 </s:annotation>
72 <s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 92 - 88/288/CDV
1 <s:element name="Syncrocheck" type="s:boolean"/>

2 <s:element name="InterlockCheck" type="s:boolean"/>
3 </s:sequence>
4 </s:complexType>
5 
7 <s:simpleType name="tTimOperRsp">
8 <s:annotation>
9 <s:documentation>Time Activated Operate response type</s:documentation>
10 </s:annotation>
12 <s:enumeration value="timerActivated"/>
13 <s:enumeration value="commandExecuted"/>
14 </s:restriction>
15 </s:simpleType>
16 
18 <s:simpleType name="tOrcat">
19 <s:annotation>
20 <s:documentation>Originator Category</s:documentation>
21 </s:annotation>
23 <s:enumeration value="not-supported"/>
24 <s:enumeration value="reserved1"/>
25 <s:enumeration value="station-control"/>
26 <s:enumeration value="remote-control"/>
27 <s:enumeration value="reserverd"/>
28 <s:enumeration value= "automatic-station"/>
29 <s:enumeration value="automatic-remote"/>
30 <s:enumeration value="maintenance"/>
31 <s:enumeration value="process"/>
32 </s:restriction>
33 </s:simpleType>
34 
36 <s:complexType name="tOrigin">
37 <s:annotation>
38 <s:documentation>Control originator</s:documentation>
39 </s:annotation>
40 <s:sequence>
41 <s:element name="orIdent" type="ews:tOctetString64"/>
42 <s:element name="orCat" type="ews:tOrcat"/>
43 </s:sequence>
44 </s:complexType>
45 
47 <s:complexType name="tControlValue">
48 <s:annotation>
49 <s:documentation>Control value</s:documentation>
50 </s:annotation>
51 <s:sequence>
52 <s:element name="ctlVal" type="ews:tDAType"/>
53 <s:element name="origin" type="ews:tOrigin"/>
54 <s:element name="ctlNum" type="s:int"/>
55 </s:sequence>
56 </s:complexType>
57 
60 <s:complexType name="tDataAttributeValue">
61 <s:annotation>
62 <s:documentation>Container for a DataAttribute </s:documentation>
63 </s:annotation>
64 <s:sequence>
65 <s:element name="DataAttrRef" type="ews:tObjectReference"/>
66 <s:element name="Value" type="ews:tDataAttribute"/>
67 </s:sequence>
68 </s:complexType>
69 
71 <s:simpleType name="tResult">
72 <s:annotation>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 93 - 88/288/CDV
1 <s:documentation>The SetDataValueResult for successfull responses</s:documentation>

2 </s:annotation>
4 <s:enumeration value="Ok"/>
5 </s:restriction>
6 </s:simpleType>
7 
10 <s:simpleType name="tDataAttrBasicType">
11 <s:annotation>
12 <s:documentation>DataAttributeType definition</s:documentation>
13 </s:annotation>
15 <s:enumeration value="Boolean"/>
16 <s:enumeration value="Int8"/>
21 <s:enumeration value="Int8U"/>
25 <s:enumeration value="Float32"/>
26 <s:enumeration value="Float64"/>
27 <s:enumeration value="Enumerated"/>
28 <s:enumeration value="CodedEnum"/>
29 <s:enumeration value="OctetString"/>
30 <s:enumeration value="VisibleString"/>
31 <s:enumeration value="UnicodeString"/>
32 <s:enumeration value="Quality"/>
33 <s:enumeration value="TimeStamp"/>
34 <s:enumeration value="ArrayOfBoolean"/>
35 <s:enumeration value="ArrayOfInt8"/>
40 <s:enumeration value="ArrayOfInt8U"/>
44 <s:enumeration value="ArrayOfFloat32"/>
45 <s:enumeration value="ArrayOfFloat64"/>
46 <s:enumeration value="ArrayOfEnum"/>
47 <s:enumeration value="ArrayOfCodedEnum"/>
48 <s:enumeration value="ArrayOfOctetString"/>
49 <s:enumeration value="ArrayOfVisibleString"/>
50 <s:enumeration value="ArrayOfUnicodeString"/>
51 </s:restriction>
52 </s:simpleType>
53 
55 <s:complexType name="tDataAttrType">
56 <s:annotation>
57 <s:documentation>DataAttrType</s:documentation>
58 </s:annotation>
59 <s:sequence>
60 <s:element name="BasicType " type="ews:tDataAttrBasicType"/>
61 <s:element name="Len" type="s:int" minOccurs="0"/> 
62 </s:sequence>
63 </s:complexType>
64 
66 <s:complexType name="tDataAttributeDefinition">
67 <s:annotation>
68 <s:documentation>DataAttributesDefinition</s:documentation>
69 </s:annotation>
70 <s:sequence>
71 <s:element name="DARef" type="ews:tObjectReference"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 94 - 88/288/CDV
1 <s:element name="DAType" type="ews:tDataAttrType"/>

2 </s:sequence>
3 </s:complexType>
4 
7 <s:complexType name="tReportFormat">
8 <s:sequence>
9 <s:element name="RptID" type="ews:tstring65" minOccurs="1" maxOccurs="1"/>
10 <s:element name="OptFlds" type="ews:tOptFldsBRCB" minOccurs="1" maxOccurs="1"/>
11 
12 <s:element name="SqNum" type="s:unsignedShort" minOccurs="0" maxOccurs="1"/>
13 <s:element name="SubSqNum" type="s:unsignedShort" minOccurs="0" maxOccurs="1"/>
14 <s:element name="MoreSegFlw" type="s:boolean" minOccurs="1" maxOccurs="1"/>
15 
16 <s:element name="DatSet" type="ews:tObjectReference" minOccurs="0" maxOccurs="1"/>
17 
18 <s:element name="BufOvfl" type="s:boolean" minOccurs="0" maxOccurs="1"/>
19 
20 <s:element name="ConfRev" type="s:string" minOccurs="0" maxOccurs="1"/>
21 
22 
23 <s:element name="TimeOfEntry" type="s:string" minOccurs="0" maxOccurs="1"/>
24 
25 <s:element name="EntryID" type="s:string" minOccurs="0" maxOccurs="1"/>
26 <s:sequence>
27 <s:element name="EntryData" type="ews:tEntryData" minOccurs="0" maxOccurs="unbounded"/>
28 </s:sequence>
29 </s:sequence>
32 </s:complexType>
33 
35 <s:simpleType name="tRCBType">
37 <s:enumeration value="BRCB"/>
38 <s:enumeration value="URCB"/>
39 </s:restriction>
40 </s:simpleType>
41 
44 
47 <s:element name="GetServerDirectoryRequest">
48 <s:complexType>
49 <s:sequence>
50 <s:element name="ObjClass" type="ews:tObjectClass"/>
51 </s:sequence>
54 </s:complexType>
55 </s:element>
56 
59 <s:element name="GetServerDirectoryResponse">
60 <s:complexType>
61 <s:choice>
62 <s:element name="LDRef" type="ews:tObjectReference" minOccurs="0" maxOc-
65
66 </s:choice>
69 </s:complexType>
70 </s:element>
71 
2 <s:element name="AssociateRequest">
3 <s:complexType>
4 <s:annotation>
5 <s:documentation> AssociateRequest is the message used when a client try to establish an as-
6 sociation to a server</s:documentation>
7 </s:annotation>
8 <s:sequence>
9 <s:element name="UserName" type="s:string"/>
10 <s:element name="Password" type="s:string"/>
11 <s:element name="ClientRequestHandle" type="s:string"/>
12 <s:element name="LocalID" type="s:string" minOccurs="0"/>
13 <s:element name="MaxMessageSize" type="s:unsignedInt "/>
14 </s:sequence>
16 </s:complexType>
17 </s:element>
18 
21 <s:element name="AssociateResponse">
22 <s:complexType>
23 <s:choice>
24 <s:sequence>
25 <s:element name="MaxMessageSize" type="s:unsignedInt" minOccurs="0"/>
26 <s:element name="AssocID" type="ews:tAssocID"/>
27 </s:sequence>
29 </s:choice>
31 </s:complexType>
32 </s:element>
33 
36 <s:element name="ReleaseRequest">
37 <s:complexType>
38 <s:annotation>
39 <s:documentation> ReleaseRequest is the message used when releaseing an associa-
40 tion</s:documentation>
41 </s:annotation>
44 </s:complexType>
45 </s:element>
46 
49 <s:element name="ReleaseResponse">
50 <s:complexType>
51 <s:annotation>
52 <s:documentation> ReleaseResponse is the message returned from a server when receiving a
53 ReleaseRequest</s:documentation>
54 </s:annotation>
55 <s:sequence>
57 </s:sequence>
60 </s:complexType>
61 </s:element>
62 
65 <s:element name="AbortRequest">
66 <s:complexType>
69 </s:complexType>
70 </s:element>
71 
2 <s:element name="AbortResponse">
3 <s:complexType>
4 <s:choice>
7 </s:choice>
10 </s:complexType>
11 </s:element>
12 
15 <s:element name="GetLogicalDeviceDirectoryRequest">
16 <s:complexType>
17 <s:sequence>
18 <s:element name="LDRef" type="ews:tObjectReference"/>
19 </s:sequence>
22 </s:complexType>
23 </s:element>
24 
27 <s:element name="GetLogicalDeviceDirectoryResponse">
28 <s:complexType>
29 <s:choice>
30 <s:element name="LNRef" type="ews:tObjectReference" minOccurs="3" maxOc-
34 </s:choice>
37 </s:complexType>
38 </s:element>
39 
42 <s:element name="GetLogicalNodeDirectoryRequest">
43 <s:complexType>
44 <s:sequence>
45 <s:element name="LNRef" type="ews:tObjectReference"/>
46 <s:element name="IEMcls" type="ews:tIEMcls"/>
47 </s:sequence>
50 </s:complexType>
51 </s:element>
52 
55 <s:element name="GetLogicalNodeDirectoryResponse">
56 <s:complexType>
57 <s:choice>
59 <s:element name="DATAname" type="ews:tObjectName"/>
60 <s:element name="DSname" type="ews:tObjectName"/>
61 <s:element name="BRCBname" type="ews:tObjectName"/>
62 <s:element name="URCBname" type="ews:tObjectName"/>
63 <s:element name="LCBname" type="ews:tObjectName"/>
64 <s:element name="LOGname" type="ews:tObjectName"/>
65 </s:choice>
67 </s:choice>
70 </s:complexType>
71 </s:element>
72 
3 <s:element name="GetDataValuesRequest">
4 <s:complexType>
5 <s:sequence>
6 <s:element name="Ref" type="ews:tFcdFcdaType" maxOccurs="unbounded"/>
7 </s:sequence>
10 </s:complexType>
11 </s:element>
12 
15 <s:element name="GetDataValuesResponse">
16 <s:complexType>
17 <s:choice>
18 <s:sequence>
21 </s:sequence>
24 </s:choice>
27 </s:complexType>
28 </s:element>
29 
32 <s:element name="SetDataValuesRequest">
33 <s:complexType>
34 <s:sequence>
35 <s:element name="Ref" type="ews:tFcdFcdaType"/>
37 </s:sequence>
40 </s:complexType>
41 </s:element>
42 
45 <s:element name="SetDataValuesResponse">
46 <s:complexType>
47 <s:sequence>
48 <s:choice>
52 </s:choice>
53 </s:sequence>
56 </s:complexType>
57 </s:element>
58 
61 <s:element name="GetDataDirectoryRequest">
62 <s:complexType>
63 <s:sequence>
65 </s:sequence>
68 </s:complexType>
69 </s:element>
70 
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 98 - 88/288/CDV
1 <s:element name="GetDataDirectoryResponse">
2 <s:complexType>
3 <s:choice>
4 <s:sequence>
5 <s:element name="DataName" type="ews:tObjectName" maxOccurs="unbounded"/>
6 <s:element name="DataAttrName" type="ews:tObjectName" maxOccurs="unbounded"/>
7 </s:sequence>
10 </s:choice>
13 </s:complexType>
14 </s:element>
15 
18 <s:element name="GetDataDefinitionRequest">
19 <s:complexType>
20 <s:sequence>
22 </s:sequence>
25 </s:complexType>
26 </s:element>
27 
30 <s:element name="GetDataDefinitionResponse">
31 <s:complexType>
32 <s:choice>
33 <s:element name="DataAttrDef" type="ews:tDataAttributeDefinition" minOccurs="1" maxOc-
36 </s:choice>
39 </s:complexType>
40 </s:element>
41 
44 <s:element name="GetDataSetValuesRequest">
45 <s:complexType>
46 <s:sequence>
48 </s:sequence>
51 </s:complexType>
52 </s:element>
53 
56 <s:element name="GetDataSetValuesResponse">
57 <s:complexType>
58 <s:choice>
63 </s:choice>
66 </s:complexType>
67 </s:element>
68 
71 <s:element name="SetDataSetValuesRequest">
72 <s:complexType>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 99 - 88/288/CDV
1 <s:sequence>
4 </s:sequence>
7 </s:complexType>
8 </s:element>
9 
12 <s:element name="SetDataSetValuesResponse">
13 <s:complexType>
14 <s:sequence>
15 <s:choice>
19 </s:choice>
20 </s:sequence>
23 </s:complexType>
24 </s:element>
25 
28 <s:element name="CreateDataSetRequest">
29 <s:complexType>
30 <s:sequence>
33 </s:sequence>
36 </s:complexType>
37 </s:element>
38 
41 <s:element name="CreateDataSetResponse">
42 <s:complexType>
43 <s:sequence>
44 <s:choice>
47 </s:choice>
48 </s:sequence>
51 </s:complexType>
52 </s:element>
53 
56 <s:element name="DeleteDataSetRequest">
57 <s:complexType>
58 <s:sequence>
60 </s:sequence>
63 </s:complexType>
64 </s:element>
65 
68 <s:element name="DeleteDataSetResponse">
69 <s:complexType>
70 <s:sequence>
71 <s:choice>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 100 - 88/288/CDV

2 </s:choice>
3 </s:sequence>
6 </s:complexType>
7 </s:element>
8 
11 <s:element name="GetDataSetDirectoryRequest">
12 <s:complexType>
13 <s:sequence>
15 </s:sequence>
18 </s:complexType>
19 </s:element>
20 
23 <s:element name="GetDataSetDirectoryResponse">
24 <s:complexType>
25 <s:choice>
29 </s:choice >
32 </s:complexType>
33 </s:element>
34 
37 <s:element name="AddSubscriptionRequest">
38 <s:complexType>
39 <s:sequence>
41 <s:element name="RCBType" type="ews:tRCBType"/>
49 <s:element name="DSMbrRef" type="ews:tFcdFcdaType" minOccurs="0" maxOc-
51 </s:sequence>
54 </s:complexType>
55 </s:element>
56 
59 <s:element name="AddSubscriptionResponse">
60 <s:complexType>
61 <s:sequence>
62 <s:choice>
66 </s:choice>
67 </s:sequence>
70 </s:complexType>
71 </s:element>
72 
3 <s:element name="RemoveSubscriptionRequest">
4 <s:complexType>
5 <s:sequence>
7 </s:sequence>
10 </s:complexType>
11 </s:element>
12 
15 <s:element name="RemoveSubscriptionResponse">
16 <s:complexType>
17 <s:sequence>
18 <s:choice>
21 </s:choice>
22 </s:sequence>
25 </s:complexType>
26 </s:element>
27 
30 <s:element name="GetBRCBValuesRequest">
31 <s:complexType>
32 <s:sequence>
34 </s:sequence>
37 </s:complexType>
38 </s:element>
39 
42 <s:element name="GetBRCBValuesResponse">
43 <s:complexType>
44 <s:sequence>
45 <s:choice>
46 <s:sequence>
60 </s:sequence>
62 </s:choice>
63 </s:sequence>
66 </s:complexType>
67 </s:element>
68 
71 <s:element name="SetBRCBValuesRequest">
72 <s:complexType>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 102 - 88/288/CDV
1 <s:sequence>
11 <s:element name="PurgeBuf" type="s:boolean" minOccurs="0"/>
12 <s:element name="EntryID" type="s:string" minOccurs="0"/>
13 </s:sequence>
16 </s:complexType>
17 </s:element>
18 
21 <s:element name="SetBRCBValuesResponse">
22 <s:complexType>
23 <s:sequence>
24 <s:choice>
28 </s:choice>
29 </s:sequence>
32 </s:complexType>
33 </s:element>
34 
37 <s:element name="GetURCBValuesRequest">
38 <s:complexType>
39 <s:sequence>
41 </s:sequence>
44 </s:complexType>
45 </s:element>
46 
49 <s:element name="GetURCBValuesResponse">
50 <s:complexType>
51 <s:sequence>
52 <s:choice>
53 <s:sequence>
65 </s:sequence>
67 </s:choice>
68 </s:sequence>
71 </s:complexType>
72 </s:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 103 - 88/288/CDV
1 
4 <s:element name="SetURCBValuesRequest">
5 <s:complexType>
6 <s:sequence>
12 <s:element name="OptFlds" type="ews:tOptFldsURCB" minOccurs="0"/>
17 </s:sequence>
20 </s:complexType>
21 </s:element>
22 
25 <s:element name="SetURCBValuesResponse">
26 <s:complexType>
27 <s:sequence>
28 <s:choice>
32 </s:choice>
33 </s:sequence>
36 </s:complexType>
37 </s:element>
38 
41 <s:element name="ReportRequest">
42 <s:complexType>
43 <s:sequence>
44 <s:element name="MaxResponseTime" type="ews:tTimeStamp" minOccurs="1"/>
45 <s:element name="MinRequestTime" type="ews:tTimeStamp" minOccurs="0"/>
46 </s:sequence>
49 </s:complexType>
50 </s:element>
51 
54 <s:element name="ReportResponse">
55 <s:complexType>
56 <s:choice>
57 <s:sequence>
58 <s:element name="ReportFormat" type="ews:tReportFormat" minOccurs="0" maxOc-
60 <s:element name="MaxRequestTime" type="ews:tTimeStamp" minOccurs="1"/>
61 <s:element name="MinResponseTime" type="ews:tTimeStamp" minOccurs="0"/>
62 </s:sequence>
64 </s:choice>
67 </s:complexType>
68 </s:element>
69 
72 <s:element name="GetLCBValuesRequest">
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 104 - 88/288/CDV
1 <s:complexType>
2 <s:sequence>
4 </s:sequence>
7 </s:complexType>
8 </s:element>
9 
12 <s:element name="GetLCBValuesResponse">
13 <s:complexType>
14 <s:sequence>
15 <s:choice>
16 <s:sequence>
22 </s:sequence>
24 </s:choice>
25 </s:sequence>
28 </s:complexType>
29 </s:element>
30 
33 <s:element name="SetLCBValuesRequest">
34 <s:complexType>
35 <s:sequence>
37 <s:element name="LogEna" type="s:boolean" minOccurs="0"/>
39 <s:element name="OptFlds" type="ews:tOptFldsLCB" minOccurs="0"/>
41 <s:element name="LogRef" type="ews:tObjectReference" minOccurs="0"/>
42 </s:sequence>
45 </s:complexType>
46 </s:element>
47 
50 <s:element name="SetLCBValuesResponse">
51 <s:complexType>
52 <s:sequence>
53 <s:choice>
56 </s:choice>
57 </s:sequence>
60 </s:complexType>
61 </s:element>
62 
65 <s:element name="GetLogStatusValuesRequest">
66 <s:complexType>
67 <s:sequence>
69 </s:sequence>
72 </s:complexType>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 105 - 88/288/CDV
1 </s:element>
2 
5 <s:element name="GetLogStatusValuesResponse">
6 <s:complexType>
7 <s:choice>
8 <s:sequence>
13 </s:sequence>
15 </s:choice>
18 </s:complexType>
19 </s:element>
20 
23 <s:element name="QueryLogByTimeRequest">
24 <s:complexType>
25 <s:sequence>
28 <s:element name="StopTime" type="ews:tTimeStamp" minOccurs="0"/>
29 <s:element name="DataFilter" type="ews:tFcdFcdaType" minOccurs="0" maxOc-
31 </s:sequence>
34 </s:complexType>
35 </s:element>
36 
39 <s:element name="QueryLogByTimeResponse">
40 <s:complexType>
41 <s:sequence>
42 <s:choice>
43 <s:sequence>
45 </s:sequence>
47 </s:choice>
48 </s:sequence>
51 </s:complexType>
52 </s:element>
53 
56 <s:element name="QueryLogAfterRequest">
57 <s:complexType>
58 <s:sequence>
61 <s:element name="EntryID" type="s:unsignedInt" minOccurs="0"/>
62 <s:element name="DataFilter" type="ews:tFcdFcdaType" minOccurs="0" maxOc-
64 </s:sequence>
67 </s:complexType>
68 </s:element>
69 
72 <s:element name="QueryLogAfterResponse">
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 106 - 88/288/CDV
1 <s:complexType>
2 <s:sequence>
3 <s:choice>
4 <s:sequence>
6 </s:sequence>
7 <s:element name="Log" type="ews:tLOG"/>
10 </s:choice>
11 </s:sequence>
14 </s:complexType>
15 </s:element>
16 
19 <s:element name="SelectRequest">
20 <s:complexType>
21 <s:sequence>
23 </s:sequence>
26 </s:complexType>
27 </s:element>
28 
31 <s:element name="SelectResponse">
32 <s:complexType>
33 <s:sequence>
35 </s:sequence>
38 </s:complexType>
39 </s:element>
40 
43 <s:element name="SelectWithValueRequest">
44 <s:complexType>
45 <s:sequence>
47 <s:element name="Value" type="ews:tControlValue"/>
50 <s:element name="Check" type="ews:tCheck"/>
51 </s:sequence>
54 </s:complexType>
55 </s:element>
56 
59 <s:element name="SelectWithValueResponse">
60 <s:complexType>
61 <s:sequence>
67 </s:sequence>
70 </s:complexType>
71 </s:element>
72 
3 <s:element name="CancelRequest">
4 <s:complexType>
5 <s:sequence>
10 </s:sequence>
13 </s:complexType>
14 </s:element>
15 
18 <s:element name="CancelResponse">
19 <s:complexType>
20 <s:sequence>
26 </s:sequence>
29 </s:complexType>
30 </s:element>
31 
34 <s:element name="OperateRequest">
35 <s:complexType>
36 <s:sequence>
42 </s:sequence>
45 </s:complexType>
46 </s:element>
47 
50 <s:element name="OperateResponse">
51 <s:complexType>
52 <s:sequence>
58 </s:sequence>
61 </s:complexType>
62 </s:element>
63 
66 <s:element name="CommandTerminationRequest">
67 <s:complexType>
68 <s:sequence>
72 </s:sequence>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 108 - 88/288/CDV

3 </s:complexType>
4 </s:element>
5 
8 <s:element name="CommandTerminationResponse">
9 <s:complexType>
10 <s:sequence>
15 </s:sequence>
18 </s:complexType>
19 </s:element>
20 
23 <s:element name="TimeActivatedOperateRequest">
24 <s:complexType>
25 <s:sequence>
31 </s:sequence>
34 </s:complexType>
35 </s:element>
36 
39 <s:element name="TimeActivatedOperateResponse">
40 <s:complexType>
41 <s:sequence>
46 <s:choice>
47 <s:element name="TimOperRsp" type="ews:tTimOperRsp"/>
48 <s:element name="AddCause" type="ews:tAddCause"/>
49 </s:choice>
50 </s:sequence>
53 </s:complexType>
54 </s:element>
55 </s:schema>
56 </types>
57 
59 <message name="AssociateSoapIn">
60 <part name="parameters" element="ews:AssociateRequest"/>
61 </message>
62 <message name="AssociateSoapOut">
63 <part name="parameters" element="ews:AssociateResponse"/>
64 </message>
65 <message name="ReleaseSoapIn">
66 <part name="parameters" element="ews:ReleaseRequest"/>
67 </message>
68 <message name="AbortSoapOut">
69 <part name="parameters" element="ews:ReleaseResponse"/>
70 </message>
71 <message name="AbortSoapIn">
72 <part name="parameters" element="ews:AbortRequest"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 109 - 88/288/CDV
1 </message>
2 <message name="ReleaseSoapOut">
3 <part name="parameters" element="ews:AbortResponse"/>
4 </message>
5 <message name="GetServerDirectorySoapIn">
6 <part name="parameters" element="ews:GetServerDirectoryRequest"/>
7 </message>
8 <message name="GetServerDirectorySoapOut">
9 <part name="parameters" element="ews:GetServerDirectoryResponse"/>
10 </message>
11 <message name="GetLogicalDeviceDirectorySoapIn">
12 <part name="parameters" element="ews:GetLogicalDeviceDirectoryRequest"/>
13 </message>
14 <message name="GetLogicalDeviceDirectorySoapOut">
15 <part name="parameters" element="ews:GetLogicalDeviceDirectoryResponse"/>
16 </message>
17 <message name="GetLogicalNodeDirectorySoapIn">
18 <part name="parameters" element="ews:GetLogicalNodeDirectoryRequest"/>
19 </message>
20 <message name="GetLogicalNodeDirectorySoapOut">
21 <part name="parameters" element="ews:GetLogicalNodeDirectoryResponse"/>
22 </message>
23 <message name="GetDataValuesSoapIn">
24 <part name="parameters" element="ews:GetDataValuesRequest"/>
25 </message>
26 <message name="GetDataValuesSoapOut">
27 <part name="parameters" element="ews:GetDataValuesResponse"/>
28 </message>
29 <message name="SetDataValuesSoapIn">
30 <part name="parameters" element="ews:SetDataValuesRequest"/>
31 </message>
32 <message name="SetDataValuesSoapOut">
33 <part name="parameters" element="ews:SetDataValuesResponse"/>
34 </message>
35 <message name="GetDataDirectorySoapIn">
36 <part name="parameters" element="ews:GetDataDirectoryRequest"/>
37 </message>
38 <message name="GetDataDirectorySoapOut">
39 <part name="parameters" element="ews:GetDataDirectoryResponse"/>
40 </message>
41 <message name="GetDataDefinitionSoapIn">
42 <part name="parameters" element="ews:GetDataDefinitionRequest"/>
43 </message>
44 <message name="GetDataDefinitionSoapOut">
45 <part name="parameters" element="ews:GetDataDefinitionResponse"/>
46 </message>
47 <message name="GetDataSetValuesSoapIn">
48 <part name="parameters" element="ews:GetDataSetValuesRequest"/>
49 </message>
50 <message name="GetDataSetValuesSoapOut">
51 <part name="parameters" element="ews:GetDataSetValuesResponse"/>
52 </message>
53 <message name="SetDataSetValuesSoapIn">
54 <part name="parameters" element="ews:SetDataSetValuesRequest"/>
55 </message>
56 <message name="SetDataSetValuesSoapOut">
57 <part name="parameters" element="ews:SetDataSetValuesResponse"/>
58 </message>
59 <message name="CreateDataSetSoapIn">
60 <part name="parameters" element="ews:CreateDataSetRequest"/>
61 </message>
62 <message name="CreateDataSetSoapOut">
63 <part name="parameters" element="ews:CreateDataSetResponse"/>
64 </message>
65 <message name="DeleteDataSetSoapIn">
66 <part name="parameters" element="ews:DeleteDataSetRequest"/>
67 </message>
68 <message name="DeleteDataSetSoapOut">
69 <part name="parameters" element="ews:DeleteDataSetResponse"/>
70 </message>
71 <message name="GetDataSetDirectorySoapIn">
72 <part name="parameters" element="ews:GetDataSetDirectoryRequest"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 110 - 88/288/CDV
1 </message>
2 <message name="GetDataSetDirectorySoapOut">
3 <part name="parameters" element="ews:GetDataSetDirectoryResponse"/>
4 </message>
5 <message name="ReportSoapIn">
6 <part name="parameters" element="ews:ReportRequest"/>
7 </message>
8 <message name="ReportSoapOut">
9 <part name="parameters" element="ews:ReportResponse"/>
10 </message>
11 <message name="AddSubscriptionSoapIn">
12 <part name="parameters" element="ews:AddSubscriptionRequest"/>
13 </message>
14 <message name="AddSubscriptionSoapOut">
15 <part name="parameters" element="ews:AddSubscriptionResponse"/>
16 </message>
17 <message name="RemoveSubscriptionSoapIn">
18 <part name="parameters" element="ews:RemoveSubscriptionRequest"/>
19 </message>
20 <message name="RemoveSubscriptionSoapOut">
21 <part name="parameters" element="ews:RemoveSubscriptionResponse"/>
22 </message>
23 <message name="GetBRCBValuesSoapIn">
24 <part name="parameters" element="ews:GetBRCBValuesRequest"/>
25 </message>
26 <message name="GetBRCBValuesSoapOut">
27 <part name="parameters" element="ews:GetBRCBValuesResponse"/>
28 </message>
29 <message name="SetBRCBValuesSoapIn">
30 <part name="parameters" element="ews:SetBRCBValuesRequest"/>
31 </message>
32 <message name="SetBRCBValuesSoapOut">
33 <part name="parameters" element="ews:SetBRCBValuesResponse"/>
34 </message>
35 <message name="GetURCBValuesSoapIn">
36 <part name="parameters" element="ews:GetURCBValuesRequest"/>
37 </message>
38 <message name="GetURCBValuesSoapOut">
39 <part name="parameters" element="ews:GetURCBValuesResponse"/>
40 </message>
41 <message name="SetURCBValuesSoapIn">
42 <part name="parameters" element="ews:SetURCBValuesRequest"/>
43 </message>
44 <message name="SetURCBValuesSoapOut">
45 <part name="parameters" element="ews:SetURCBValuesResponse"/>
46 </message>
47 <message name="GetLCBValuesSoapIn">
48 <part name="parameters" element="ews:GetLCBValuesRequest"/>
49 </message>
50 <message name="GetLCBValuesSoapOut">
51 <part name="parameters" element="ews:GetLCBValuesResponse"/>
52 </message>
53 <message name="SetLCBValuesSoapIn">
54 <part name="parameters" element="ews:SetLCBValuesRequest"/>
55 </message>
56 <message name="SetLCBValuesSoapOut">
57 <part name="parameters" element="ews:SetLCBValuesResponse"/>
58 </message>
59 <message name="QueryLogByTimeSoapIn">
60 <part name="parameters" element="ews:QueryLogByTimeRequest"/>
61 </message>
62 <message name="QueryLogByTimeSoapOut">
63 <part name="parameters" element="ews:QueryLogByTimeResponse"/>
64 </message>
65 <message name="QueryLogAfterSoapIn">
66 <part name="parameters" element="ews:QueryLogAfterRequest"/>
67 </message>
68 <message name="QueryLogAfterSoapOut">
69 <part name="parameters" element="ews:QueryLogAfterResponse"/>
70 </message>
71 <message name="GetLogStatusValuesSoapIn">
72 <part name="parameters" element="ews:GetLogStatusValuesRequest"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 111 - 88/288/CDV
1 </message>
2 <message name="GetLogStatusValuesSoapOut">
3 <part name="parameters" element="ews:GetLogStatusValuesResponse"/>
4 </message>
5 <message name="SelectSoapIn">
6 <part name="parameters" element="ews:SelectRequest"/>
7 </message>
8 <message name="SelectSoapOut">
9 <part name="parameters" element="ews:SelectResponse"/>
10 </message>
11 <message name="SelectWithValueSoapIn">
12 <part name="parameters" element="ews:SelectWithValueRequest"/>
13 </message>
14 <message name="SelectWithValueSoapOut">
15 <part name="parameters" element="ews:SelectWithValueResponse"/>
16 </message>
17 <message name="CancelSoapIn">
18 <part name="parameters" element="ews:CancelRequest"/>
19 </message>
20 <message name="CancelSoapOut">
21 <part name="parameters" element="ews:CancelResponse"/>
22 </message>
23 <message name="OperateSoapIn">
24 <part name="parameters" element="ews:OperateRequest"/>
25 </message>
26 <message name="OperateSoapOut">
27 <part name="parameters" element="ews:OperateResponse"/>
28 </message>
29 <message name="CommandTerminationSoapIn">
30 <part name="parameters" element="ews:CommandTerminationRequest"/>
31 </message>
32 <message name="CommandTerminationSoapOut">
33 <part name="parameters" element="ews:CommandTerminationResponse"/>
34 </message>
35 <message name="TimeActivatedOperateSoapIn">
36 <part name="parameters" element="ews:TimeActivatedOperateRequest"/>
37 </message>
38 <message name="TimeActivatedOperateSoapOut">
39 <part name="parameters" element="ews:TimeActivatedOperateResponse"/>
40 </message>
41 <portType name="ServicePortType">
42 <operation name="Associate">
43 <input message="ews:AssociateSoapIn"/>
44 <output message="ews:AssociateSoapOut"/>
45 </operation>
46 <operation name="Release">
47 <input message="ews:ReleaseSoapIn"/>
48 <output message="ews:ReleaseSoapOut"/>
49 </operation>
50 <operation name="GetServerDirectory">
51 <input message="ews:GetServerDirectorySoapIn"/>
52 <output message="ews:GetServerDirectorySoapOut"/>
53 </operation>
54 <operation name="GetLogicalDeviceDirectory">
55 <input message="ews:GetLogicalDeviceDirectorySoapIn"/>
56 <output message="ews:GetLogicalDeviceDirectorySoapOut"/>
57 </operation>
58 <operation name="GetLogicalNodeDirectory">
59 <input message="ews:GetLogicalNodeDirectorySoapIn"/>
60 <output message="ews:GetLogicalNodeDirectorySoapOut"/>
61 </operation>
62 <operation name="GetDataValues">
63 <input message="ews:GetDataValuesSoapIn"/>
64 <output message="ews:GetDataValuesSoapOut"/>
65 </operation>
66 <operation name="SetDataValues">
67 <input message="ews:SetDataValuesSoapIn"/>
68 <output message="ews:SetDataValuesSoapOut"/>
69 </operation>
70 <operation name="GetDataDirectory">
71 <input message="ews:GetDataDirectorySoapIn"/>
72 <output message="ews:GetDataDirectorySoapOut"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 112 - 88/288/CDV
1 </operation>
2 <operation name="GetDataDefinition">
3 <input message="ews:GetDataDefinitionSoapIn"/>
4 <output message="ews:GetDataDefinitionSoapOut"/>
5 </operation>
6 <operation name="GetDataSetValues">
7 <input message="ews:GetDataSetValuesSoapIn"/>
8 <output message="ews:GetDataSetValuesSoapOut"/>
9 </operation>
10 <operation name="SetDataSetValues">
11 <input message="ews:SetDataSetValuesSoapIn"/>
12 <output message="ews:SetDataSetValuesSoapOut"/>
13 </operation>
14 <operation name="CreateDataSet">
15 <input message="ews:CreateDataSetSoapIn"/>
16 <output message="ews:CreateDataSetSoapOut"/>
17 </operation>
18 <operation name="DeleteDataSet">
19 <input message="ews:DeleteDataSetSoapIn"/>
20 <output message="ews:DeleteDataSetSoapOut"/>
21 </operation>
22 <operation name="GetDataSetDirectory">
23 <input message="ews:GetDataSetDirectorySoapIn"/>
24 <output message="ews:GetDataSetDirectorySoapOut"/>
25 </operation>
26 <operation name="Report">
27 <input message="ews:ReportSoapIn"/>
28 <output message="ews:ReportSoapOut"/>
29 </operation>
30 <operation name="AddSubscription">
31 <input message="ews:AddSubscriptionSoapIn"/>
32 <output message="ews:AddSubscriptionSoapOut"/>
33 </operation>
34 <operation name="RemoveSubscription">
35 <input message="ews:RemoveSubscriptionSoapIn"/>
36 <output message="ews:RemoveSubscriptionSoapOut"/>
37 </operation>
38 <operation name="GetBRCBValues">
39 <input message="ews:GetBRCBValuesSoapIn"/>
40 <output message="ews:GetBRCBValuesSoapOut"/>
41 </operation>
42 <operation name="SetBRCBValues">
43 <input message="ews:SetBRCBValuesSoapIn"/>
44 <output message="ews:SetBRCBValuesSoapOut"/>
45 </operation>
46 <operation name="GetURCBValues">
47 <input message="ews:GetURCBValuesSoapIn"/>
48 <output message="ews:GetURCBValuesSoapOut"/>
49 </operation>
50 <operation name="SetURCBValues">
51 <input message="ews:SetURCBValuesSoapIn"/>
52 <output message="ews:SetURCBValuesSoapOut"/>
53 </operation>
54 <operation name="GetLCBValues">
55 <input message="ews:GetLCBValuesSoapIn"/>
56 <output message="ews:GetLCBValuesSoapOut"/>
57 </operation>
58 <operation name="SetLCBValues">
59 <input message="ews:SetLCBValuesSoapIn"/>
60 <output message="ews:SetLCBValuesSoapOut"/>
61 </operation>
62 <operation name="QueryLogByTime">
63 <input message="ews:QueryLogByTimeSoapIn"/>
64 <output message="ews:QueryLogByTimeSoapOut"/>
65 </operation>
66 <operation name="QueryLogAfter">
67 <input message="ews:QueryLogAfterSoapIn"/>
68 <output message="ews:QueryLogAfterSoapOut"/>
69 </operation>
70 <operation name="GetLogStatusValues">
71 <input message="ews:GetLogStatusValuesSoapIn"/>
72 <output message="ews:GetLogStatusValuesSoapOut"/>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 113 - 88/288/CDV
1 </operation>
2 <operation name="Select">
3 <input message="ews:SelectSoapIn"/>
4 <output message="ews:SelectSoapOut"/>
5 </operation>
6 <operation name="SelectWithValue">
7 <input message="ews:SelectWithValueSoapIn"/>
8 <output message="ews:SelectWithValueSoapOut"/>
9 </operation>
10 <operation name="Cancel">
11 <input message="ews:CancelSoapIn"/>
12 <output message="ews:CancelSoapOut"/>
13 </operation>
14 <operation name="Operate">
15 <input message="ews:OperateSoapIn"/>
16 <output message="ews:OperateSoapOut"/>
17 </operation>
18 <operation name="CommandTermination">
19 <input message="ews:CommandTerminationSoapIn"/>
20 <output message="ews:CommandTerminationSoapOut"/>
21 </operation>
22 <operation name="TimeActivatedOperate">
23 <input message="ews:TimeActivatedOperateSoapIn"/>
24 <output message="ews:TimeActivatedOperateSoapOut"/>
25 </operation>
26 </portType>
27 <binding name="IECXMLServiceSoapBinding" type="ews:ServicePortType">
28 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
29 <operation name="Associate">
30 <soap:operation soapAction="http://iec.ch/ews/1.0/Associate" style="document"/>
31 <input>
32 <soap:body use="literal"/>
33 </input>
34 <output>
36 </output>
37 </operation>
38 <operation name="Release">
39 <soap:operation soapAction="http://iec.ch/ews/1.0/Release" style="document"/>
40 <input>
42 </input>
43 <output>
45 </output>
46 </operation>
47 <operation name="GetServerDirectory">
48 <soap:operation soapAction="http://iec.ch/ews/1.0/GetServerDirectory" style="document"/>
49 <input>
51 </input>
52 <output>
54 </output>
55 </operation>
56 <operation name="GetLogicalDeviceDirectory">
57 <soap:operation soapAction="http://iec.ch/ews/1.0/GetLogicalDeviceDirectory" style="document"/>
58 <input>
60 </input>
61 <output>
63 </output>
64 </operation>
65 <operation name="GetLogicalNodeDirectory">
66 <soap:operation soapAction="http://iec.ch/ews/1.0/GetLogicalNodeDirectory" style="document"/>
67 <input>
69 </input>
70 <output>
72 </output>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 114 - 88/288/CDV
1 </operation>
2 <operation name="GetDataValues">
3 <soap:operation soapAction="http://iec.ch/ews/1.0/GetDataValues" style="document"/>
4 <input>
6 </input>
7 <output>
9 </output>
10 </operation>
11 <operation name="SetDataValues">
12 <soap:operation soapAction="http://iec.ch/ews/1.0/SetDataValues" style="document"/>
13 <input>
15 </input>
16 <output>
18 </output>
19 </operation>
20 <operation name="GetDataDirectory">
21 <soap:operation soapAction="http://iec.ch/ews/1.0/GetDataDirectory" style="document"/>
22 <input>
24 </input>
25 <output>
27 </output>
28 </operation>
29 <operation name="GetDataDefinition">
30 <soap:operation soapAction="http://iec.ch/ews/1.0/GetDataDefinition" style="document"/>
31 <input>
33 </input>
34 <output>
36 </output>
37 </operation>
38 <operation name="GetDataSetValues">
39 <soap:operation soapAction="http://iec.ch/ews/1.0/GetDataSetValues" style="document"/>
40 <input>
42 </input>
43 <output>
45 </output>
46 </operation>
47 <operation name="SetDataSetValues">
48 <soap:operation soapAction="http://iec.ch/ews/1.0/SetDataSetValues" style="document"/>
49 <input>
51 </input>
52 <output>
54 </output>
55 </operation>
56 <operation name="CreateDataSet">
57 <soap:operation soapAction="http://iec.ch/ews/1.0/CreateDataSet" style="document"/>
58 <input>
60 </input>
61 <output>
63 </output>
64 </operation>
65 <operation name="DeleteDataSet">
66 <soap:operation soapAction="http://iec.ch/ews/1.0/DeleteDataSet" style="document"/>
67 <input>
69 </input>
70 <output>
72 </output>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 115 - 88/288/CDV
1 </operation>
2 <operation name="GetDataSetDirectory">
3 <soap:operation soapAction="http://iec.ch/ews/1.0/GetDataSetDirectory" style="document"/>
4 <input>
6 </input>
7 <output>
9 </output>
10 </operation>
11 <operation name="Report">
12 <soap:operation soapAction="http://iec.ch/ews/1.0/Report" style="document"/>
13 <input>
15 </input>
16 <output>
18 </output>
19 </operation>
20 <operation name="AddSubscription">
21 <soap:operation soapAction="http://iec.ch/ews/1.0/AddSubscription" style="document"/>
22 <input>
24 </input>
25 <output>
27 </output>
28 </operation>
29 <operation name="RemoveSubscription">
30 <soap:operation soapAction="http://iec.ch/ews/1.0/RemoveSubscription" style="document"/>
31 <input>
33 </input>
34 <output>
36 </output>
37 </operation>
38 <operation name="GetBRCBValues">
39 <soap:operation soapAction="http://iec.ch/ews/1.0/GetBRCBValues" style="document"/>
40 <input>
42 </input>
43 <output>
45 </output>
46 </operation>
47 <operation name="SetBRCBValues">
48 <soap:operation soapAction="http://iec.ch/ews/1.0/SetBRCBValues" style="document"/>
49 <input>
51 </input>
52 <output>
54 </output>
55 </operation>
56 <operation name="GetURCBValues">
57 <soap:operation soapAction="http://iec.ch/ews/1.0/GetURCBValues" style="document"/>
58 <input>
60 </input>
61 <output>
63 </output>
64 </operation>
65 <operation name="SetURCBValues">
66 <soap:operation soapAction="http://iec.ch/ews/1.0/SetURCBValues" style="document"/>
67 <input>
69 </input>
70 <output>
72 </output>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 116 - 88/288/CDV
1 </operation>
2 <operation name="GetLCBValues">
3 <soap:operation soapAction="http://iec.ch/ews/1.0/GetLCBValues" style="document"/>
4 <input>
6 </input>
7 <output>
9 </output>
10 </operation>
11 <operation name="SetLCBValues">
12 <soap:operation soapAction="http://iec.ch/ews/1.0/SetLCBValues" style="document"/>
13 <input>
15 </input>
16 <output>
18 </output>
19 </operation>
20 <operation name="QueryLogByTime">
21 <soap:operation soapAction="http://iec.ch/ews/1.0/QueryLogByTime" style="document"/>
22 <input>
24 </input>
25 <output>
27 </output>
28 </operation>
29 <operation name="QueryLogAfter">
30 <soap:operation soapAction="http://iec.ch/ews/1.0/QueryLogAfter" style="document"/>
31 <input>
33 </input>
34 <output>
36 </output>
37 </operation>
38 <operation name="GetLogStatusValues">
39 <soap:operation soapAction="http://iec.ch/ews/1.0/GetLogStatusValues" style="document"/>
40 <input>
42 </input>
43 <output>
45 </output>
46 </operation>
47 <operation name="Select">
48 <soap:operation soapAction="http://iec.ch/ews/1.0/Select" style="document"/>
49 <input>
51 </input>
52 <output>
54 </output>
55 </operation>
56 <operation name="SelectWithValue">
57 <soap:operation soapAction="http://iec.ch/ews/1.0/SelectWithValue" style="document"/>
58 <input>
60 </input>
61 <output>
63 </output>
64 </operation>
65 <operation name="Cancel">
66 <soap:operation soapAction="http://iec.ch/ews/1.0/Cancel" style="document"/>
67 <input>
69 </input>
70 <output>
72 </output>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 117 - 88/288/CDV
1 </operation>
2 <operation name="Operate">
3 <soap:operation soapAction="http://iec.ch/ews/1.0/Operate" style="document"/>
4 <input>
6 </input>
7 <output>
9 </output>
10 </operation>
11 <operation name="CommandTermination">
12 <soap:operation soapAction="http://iec.ch/ews/1.0/CommandTermination" style="document"/>
13 <input>
15 </input>
16 <output>
18 </output>
19 </operation>
20 <operation name="TimeActivatedOperate">
21 <soap:operation soapAction="http://iec.ch/ews/1.0/TimeActivatedOperate" style="document"/>
22 <input>
24 </input>
25 <output>
27 </output>
28 </operation>
29 </binding>
30 <service name="IECXMLService">
31 <port name="IECXMLServicePort" binding="ews:IECXMLServiceSoapBinding">
32 <soap:address location="http://someserver.com/ews"/>
33 </port>
34 </service>
35 </definitions>
36
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 118 - 88/288/CDV
1 Annex B
2 (normative)
3
5 Mapping to OPC XML-DA
7 B.1 General
8 B.1.1 Introduction
9 This Annex describes the mapping of the IEC 61400-25 services to OPC XML-DA services.
10 This mapping is based on two principles:
11 - The Information Model defined in the IEC 61400-25-2 document must be accessible
12 using the OPC XML-DA services.
13 - The OPC XML-DA server must follow the rules specified in the OPC XML-DA 1.01
14 Specification.
16 Clause B.1 provides a general introduction of the mapping to OPC XML-DA.
17 Clause B.2 provides the list of normative references for mapping to OPC XML-DA.
18 Clause B.3 provides a list of abbreviated terms used in annex B.
19 Clause B.4 provides mapping of the IEC 61400-25-2 information model to OPC XML-DA.
20 Clause B.5 provides mapping of the IEC 61400-25-3 information exchange model to OPC
21 XML-DA.
22 Clause B.6 provides the protocol stack details.
23 B.1.2 Scope
24 The scope of the mapping to OPC XML-DA services is the exchange of process information
25 required for operational purposes. The amount of information provided by the server can vary
26 dependent on the operational needs. Actors could be local, regional or nationwide control
27 centres that receive information in order to monitor and control the process.
28 B.1.3 The mapping architecture
32 The wind power plant information model defined in IEC 61400-25-2 shall be mapped to a hi-
33 erarchical structure.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 119 - 88/288/CDV
1 The conceptual mapping is depicted in Figure B-1. The wind power plant information model of
2 IEC 61400-25 is intended to be preserved when mapped to OPC XML-DA services. This
3 means that:
5 25 that can be retrieved by the services according to Table B-1.
6 - the client implements the wind power plant information model by configuration or can re-
7 trieve it using the autodescription services.
8 - the master/client station accesses the hierarchical wind power plant information model of
9 IEC 61400-25 through the services provided by OPC XML-DA mapping to exchange in-
10 formation model data.
Information Model
IEC 61400-25-2
IEC
Client Turbine5
Application WGEN
Information model WTUR
through configuration TurSt
or autodescription W
services mag IEC
q Server
t Application
IEC 61400-25-3
units
db
local local
interface d
interface
Information exchange Information exchange

according to SCSM as according to SCSM as
described in this Annex described in this Annex
local local
interface OPC XML-DA protocol Interface
Browse
Read response
Write …
11
12 Figure B-1 – Mapping architecture (conceptual)
14 shall be mapped to the services listed in Table B-1 below.
15 Table B-1 – Mapping of IEC 61400-25 IEM service into OPC XML-DA services
IEC 61400-25-2 IM Classes IEC 61400-25-3 IEM Ser- M/O Included OPC XML-DA services
IEC 61400-25-3 IEM Classes vices in the
mapping
ASSOCIATION
Associate M Y -
Release O Y -
Abort O N -
SERVER
GetServerDirectory O Y Browse
LOGICAL-DEVICE
GetLogicalDeviceDirectory O Y Browse
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 120 - 88/288/CDV
LOGICAL-NODE
GetLogicalNodeDirectory O Y Browse
DATA
GetDataValues M Y Read
SetDataValues M Y Write
GetDataDirectory O Y Browse
GetDataDefinition O Y Browse
DATA-SET
GetDataSetValues M N
SetDataSetValues O N
CreateDataSet O N
DeleteDataSet O N
GetDataSetDirectory O N
REPORTING
Report O Y SubscriptionPolledRefresh
AddSubscription O Y Subscribe
RemoveSubscription O Y SubscriptionCancel
URCB
GetURCBValues O N
SetURCBValues O N
BRCB
GetBRCBValues O N
SetBRCBValues O N
LCB
GetLCBValues O N
SetLCBValues O N
LOG
GetLogStatusValues O N
QueryLogByTime O N
QueryLogAfter O N
CONTROL
Select O Y Write
SelectWithValue O Y Write
Cancel O Y Write
Operate M Y Write
CommandTermination O Y Read / Subscribe, Subscrip-
tionPolledRefresh, Subscrip-
tionCancel
TimeActivatedOperate O Y Write, Read /Subscribe, Sub-
scriptionPolledRefresh, Sub-
scriptionCancel
2 B.2 Specific normative references for OPC XML-DA mapping
3 OPC XML-DA Specification. Version1.01. Released, 18 December 2004.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 121 - 88/288/CDV
1 Hypertext Transfer Protocol -- HTTP/1.1. RFC2616. June 1999.
3 B.3 Abbreviated terms
ACSI Abstract Communication Cervice Interface (defined in 61850-7-2)

Note: In this Annex C the term IEM (see below) will be used instead of ACSI.
HTTP HyperText Transfer Protocol
IM Information Model
LD Logical Device
LN Logical Node
LOG Log
SSL Socket Secure Layer
URL Uniform Resource Locator
TTL Time To Live
WT Wind Turbine
5 B.4 Mapping of the IEC 61400-25 Information Model to OPC XML-DA
6 B.4.1 Mapping of IEC 61400-25-2 Information Model classes to OPC XML-DA
7 Table B-2 – Mapping of IEC-61400-25-2 IM classes to OPC XML-DA
IEC 61400-25-2 IM Class OPC XML-DA concept OPC XML-DA related services
Server Web Service Browse
Logical Device Branch Browse
Logical Node
Data
DataAttribute (Composite)
DataAttribute (Primitive) Item Browse
Read
Write
Subscribe
SubscriptionPolledRefresh
SubscriptionCancel
8
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 122 - 88/288/CDV
1 Note: The concepts Branch and Item are not accessible objects. They are used by the different OPC XML-DA web
2 methods.
3
4 B.4.2 Server
5 The IEC 61400-25 Server is represented by an OPC XML-DA web server.
6 An OPC XML-DA web service is each of the web services running inside a web server accord-
7 ing to rules defined in the OPC XML-DA specification. Each web service is assigned a com-
8 munication address, its Service Access Point through which the OPC XML-DA services can
9 be exchanged. The format of the address is an URL, such as
10 http://machineName/virtualDirectory/serviceName.asmx or
11 https://machineName/virtualDirectory/serviceName.asmx
12 The IEM server is covered by the web server that holds the OPC XML-DA services.
13 The server class attributes are mapped as follows.
14 Table B-3 – Server class attributes
IEC 61400-25-2 OPC XML-DA Comment

(referencing IEC 61850-7-2)
ServiceAccessPoint [1..n] URL of the OPC XML-DA
web service
LogicalDevice [1..n] child / branch

TPAppAssociation [0..n] -- HTTP-Session
15 NOTE: The referenced IEC 61850-7-2 defines Files and MCAppAssociations as Server class attributes. Files and
16 MCAppAssociations are not part of the IEC 61400-25-2 Information Model.
17 B.4.3 Logical Device
18 Logical Devices are mapped to branches in the OPC hierarchy. For each logical device there
19 shall be a branch in the OPC hierarchy. The branch name shall be the LDName of the logical
20 device.
21 The logical device class attributes are mapped as follows.
22 Table B-4 – Logical Device Class attributes

LDName Name
LDRef ItemName
LogicalNode [3..n] branch At least LLN0, LPHD and one more LN shall be
present.
23
24 B.4.4 Logical Node
25 Logical Nodes shall be mapped to branches in the OPC hierarchy. For each logical node there
26 shall be a branch in the OPC hierarchy. The branch name shall be the LNName of the logical
27 node. The ItemName of the branch shall have the format: LDName/LNName.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 123 - 88/288/CDV
1 The logical node class attributes are mapped as follows.
2 Table B-5 – Logical Node Class attributes

LNName Name
LNRef ItemName
Data [1..n] Branch
DataSet [0..n] Not-mapped
BufferedReportControlBlock [0..n] Not-mapped
UnbufferedReportControlBlock [0..n] Not-mapped
LogControlBlock [0..n] Not-mapped
Log [0..n] Not-mapped
4 B.4.5 Data
5 Each data shall be mapped to a branch in the OPC hierarchy.
6 The data class attributes are mapped as follows.
7 Table B-6 – Data Class attributes

DataName Name
DataRef ItemName
Presence Not mapped
DataAttribute [0..n]
DataAttributeType Item or branch
FunctionalContraint ItemPath / custom item prop-

erty
TrgOp Not mapped
Specialisations of DATA
CompositeCDC Branch
SimpleCDC Branch
9 B.4.6 DataAttributeType
10 DataAttributeType shall be mapped either to branches (Composite DataAttributes) or items

11 (Primite DataAttributes) in the OPC hierarchy. There has to be one branch for each Compo-
12 siteComponent and one item for each PrimitiveComponent. The PrimitiveComponent items
13 form the leafs in the OPC XML-DA hierarchy. The DAType attributes are mapped as follows.
14 Table B-7 – DataAttributeType (DAType) Class attributes

Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 124 - 88/288/CDV

DatName Name
DatRef ItemName
Presence --
Specialisations of DAType
CompositeComponent branch
[ 0..n ] of DAType
PrimitiveComponent Item It shall map to a BasicType.
[ 0..1 ] of BasicType
2 B.4.6.1 Mapping of the attribute BasicTypes
3 Table B-8 – Mapping of the attribute BasicType
IEC 61400-25-2 BasicType OPC XML-DA type Value Range Comment

BOOLEAN boolean Binary logic value.
true | false
INT8 byte 8-bit signed integer value
/-128 to 127
INT16 short 16-bit signed integer
value /-32.768 to 32.767
INT24 int Extends the value range
from: -8.388.608 to
8.388.607to: -2**31 to
(2**31)-1
INT32 int 32-bit signed integer
value / -2**31 to (2**31)-1
INT128 long Reduces the value range The maximum value is lim-
from: -2**127 to (2**127)- ited within this mapping
1 to: -2**63 to (2**63)-1
INT8U unsignedByte 8-bit unsigned integer /0
to 255
INT16U unsignedShort 16-bit unsigned integer /0
to 65.535
INT24U unsignedInt Extends the value range
from: 0 to 16.777.215to: 0
to 4.294.967.295
INT32U unsignedInt 32-bit unsigned integer /0
to 4.294.967.295
FLOAT32 float IEEE single-precision 32-
bit floating point value
FLOAT64 double IEEE single-precision 64-
bit floating point value
ENUMERATED unsignedInt Ordered set of values, de-
fined where type is used;
custom extensions are al-
lowed.
CODED ENUM unsignedInt Ordered set of values, de-
fined where type is used;
custom extensions shall
not be allowed.
VISIBLE STRING string From: ASCII stringto: Uni- Length is specified in the
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 125 - 88/288/CDV
code character string CDC definition.

UNICODE STRING string Unicode character string Length is specified in the
CDC definition.
2 B.4.6.2 Additional definition of common data types
3 General
4 B.4.6.2.1 Coded enum
5 The CODED ENUM shall map to an unsignedInt. The bit 0 of the CODED ENUM shall be the
6 most significant bit in the unsignedInt.
7 Value = bit[0] * 2 N-1
+ bit[1] * 2 N-2
+…+ bit[N] *2 0
,where N is the number of bits in the coded enum.
8 B.4.6.2.2 Octet string
9 The IEC OctetString shall map to an OPC/ XML DA hexadecimal string. Only the characters 0-
10 9, a-f and A-F should be used.
11 B.4.6.3 Array
12 The IEC 61400-25-2 “ARRAY OF xxx” shall map to an OPC XML-DA “ArrayOfXXX” where
13 XXX is defined where type is used.
14 B.4.6.4 Common Data Types
15 B.4.6.4.1 ObjectName
16 The IEM ObjectName (VisibleString32) attribute shall map to the attribute “Name” (string) in-
17 side the OPC XML-DA services.
18 B.4.6.4.2 ObjectReference
19 The IEM ObjectReference (VisibleString255) attribute shall map to the attribute “ItemName”
20 (string) inside the OPC XML-DA services.
21 B.4.6.4.3 ServiceError
22 The IEM ServiceError (ENUMERATED) shall map to the OPC XML-DA Text (string) element of
23 the OPCError element . The list of the standard OPC XML-DA error codeshas been extended
24 with the following ones:
25 Table B-9 – New OPC XML-DA Error codes
New OPC XML-DA Error codes

E_61400_25_INSTANCE_NOT_AVAILABLE
E_61400_25_INSTANCE_IN_USE
E_61400_25_ACCESS_VIOLATION
E_61400_25_ACCESS_NOT_ALLOWED_IN_CURRENT_STATE
E_61400_25_PARAMETER_VALUE_INAPPROPRIATE
E_61400_25_PARAMETER_VALUE_INCONSISTENT
E_61400_25_CLASS_NOT_SUPPORTED
E_61400_25_INSTANCE_LOCKED_BY_OTHER_CLIENT
E_61400_25_CONTROL_MUST_BE_SELECTED
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 126 - 88/288/CDV
E_61400_25_TYPE_CONFLICT
E_FAILED_DUE_TO_COMMUNICATIONS_CONSTRAINT
E_FAILED_DUE_TO_SERVER_CONSTRAINT
2 B.4.6.4.4 TimeStamp
3 Maps to a OPC XML-DA dateTime type.
4 In this mapping, the OPC XML-DA Timestamp property is not used. The reason is that the
5 TimeStamp of the Information Model reflects the last instant when the value changed while the OPC
6 Timestamp reflects the time at which the server knew the corresponding value was accurate.
7 ”Note that if a device or server is checking a value every 10 seconds then the expected behavior
8 would be that the timestamp of that value would be updated every 10 seconds (even if the value is not
9 actually changing).”
10
11
12 Figure B-2 – Differences between OPC XML-DA and IEC Information Model timestamp
13 Figure B-2 shows the difference in the values of the OPC Timestamp property and the Item that re-
14 flects the Information Model TimeStamp.
15 The Timestamp mapping is described in details in the Table B-10.
16 Table B-10 – Timestamp mapping
IM TimeStamp attributes OPC mapping Constraints

SecondSinceEpoch OPC XML-DA dateTime
FractionOfSecond
TimeQuality LeapSecondsKnown Not mapped
ClockFailure Quality property of the TimeStamp “bad”
item
ClockNotSynchronized Quality property of the TimeStamp “uncertain”
item
TimeAccuracy Not mapped Fixed to n=10.
17
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 127 - 88/288/CDV
1 B.4.6.4.5 Quality
2 The information model defined in the document IEC 61400-25-2 specifies the existence of a
3 quality attribute that is referred to the value of some status or measurement attributes.
4 The values that can be hold inside the IEM Quality attribute, are quite different from the ones
5 inside the OPC XML-DA Quality property. In this mapping, the OPC XML-DA Quality property
6 is not used. The IEM Quality will be an item in the OPC hierarchy.
7 The Quality attributes inside the information model shall be considered as a CODED ENUM
8 formed by 13 bits and mapped to an OPC unsignedInt in the following way:
9 Table B-11 – Mapping of the Quality attribute
Bit(s) AttributeName Attribute Value Comment

0-1 validity good Value = 0 0
invalid Value = 0 1
reserved Value = 1 0
questionable Value = 1 1
2 overflow
3 outOfRange
4 badReference
5 oscillatory
6 failure
7 oldData
8 inconsistent
9 inaccurate
10 source
11 test
12 operatorBlocked
10
11 Quality value = bit[0] * 2^12 + bit[1] * 2^11 +…+ bit[12] * 2^0
12 B.4.6.5 Mapping of the functional constraint
13 Within this mapping the Functional Constraints are assigned to the ItemPath of the lowest
14 level DataAttributes (PrimitiveComponents).
15 Additionally an optional custom item property “FC” is introduced to reduce the number of
16 Browse services to get the full list of elements that compose an FCD or FCDA. This custom
17 item property, assigned to the Data and DataAttributes, identifies which FCs are used inside
18 the correspondent element.
ItemName DataRef.FC / DATRef.FC

ItemPath “” (empty string)
Type CODEDENUM (ST(0) | MX(1) | CO(2) | SP(3) | CF(4) | DC(5) | EX(6) | BR(7) | RP(8)
|LG(9) )
19
20 Note: the client shall not expect the presence of this property in the model.
21 Note 2: In the case a DataAttribute exists within two or more different functional constraints, that will cause the ex-
22 istance of more than one item with the same name (but different FC) in the OPC XML DA hierarchy. It is responsi-
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 128 - 88/288/CDV
1 bility of the client detecting this repetition and dropping the ones that are not needed on the reception of the OPC
2 XML-DA service responses.
4 B.5 Mapping of the Information Exchange Model to OPC XML-DA services
5 In the definition of the IEM services mapping the following definitions apply:
6 • M : Mandatory. This attribute/element is required either by OPC XML-DA or this map-

7 ping specification.
8 • C: Conditional. This attribute/element is conditional to another attribute or the recep-

9 tion of a parameter in the request.
10 • O: Optional. Can be included, but it is not mandatory, so it can not be expected in any
11 implementation.
12 • N: Not used. This attribute/element must not be included in the mapping.
14 shall be mapped to the services defined in this clause.
15 B.5.1 Association model (informative)
16 Web services are built as connectionless services in order to improve scalability over connec-
17 tion-oriented services. A connectionless service can behave like a connected service by build-
18 ing it as a stateful service.
19 This clause describes a method to use the HTTP header in order to tranfer information to
20 share a connection identifier during intechange of different OPC XML-DA services . This
21 mapping do not oblige this behaviour to be adopted, but it recommends that if this information
22 is provided by a server the method described should be used.
23 The two-party-application-association class and its services the IEC 61400-25-2 and 61400-
24 25-3 ) specify the concept of a stateful connection. By contrast OPC XML-DA is based upon
25 SOAP and the stateless protocol HTTP, i.e. the server treats each request as an independent
26 transaction, unrelated to any previous request. This mapping prescribes that the requests
27 shall be bundled by establishing a virtual session within the application layer.
28 The virtual session shall be established by using a unique session ID that is created by the
29 server and transmitted with at least every request. It is required that the session ID is unique
30 within the server, i.e. there is a one-to-one-connection between a client and a session ID, and
31 within the client, i.e. there is a one-to-one-connection between a server (represented by its
32 URL) and a session ID. The mapping does not prescribe how the exchange of the session ID
33 shall be implemented (e.g. via HTML cookie or as part of the URL).
34 It is prescribed that the server has to keep a timer for each session ID. The timer has to be
35 set anew with every request of the associated client. If the timer expires, i.e. there was no fur-
36 ther client request within a certain time, the server shall consider the session closed and de-
37 lete the session ID.
38 It is not prescribed by this mapping how the authentication of the client has to be implemented
39 but it is required that the client does not have to authenticate itself again with every request.
40 This can be obtained e.g. by using the session ID to identify the requesting client.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 129 - 88/288/CDV
1 It is strongly recomended to encrypt the transferred data (e.g. by using https) especially the
2 data that are transferred for authentification purposes (username/password).
3 B.5.1.1 Association attributes
4 B.5.1.1.1 AssocitationID
5 The AssociationID format and content shall be a local issue. In the server side, there shall be
6 a one-to-one correspondence between an AssociationID and the connection between the cli-
7 ent and the web server. In the client side, the union of the AssociationID and the URL of the
8 server should be unique.
9 B.5.1.2 Association services
10 B.5.1.2.1 Associate
11 The HTTP Header Authentication could be use if is desired to authenticate the client. This ap-
12 proach could only be used if both the server and the client support authentication. All the se-
13 curity aspect are out of the scope of this document.
14 The associate service shall not map to any specific OPC XML-DA service. Each time a client
15 sends an OPC XML-DA service request without the associationID in the HTTP header, the
16 server shall consider it a new association and in the reply to the service it shall include the
17 identifier of that association.
18 The HTTP header used shall follow the sintax:
19 Set-Cookie: AssociationID = AssocValue; expires=date; path=/SERVICE1; domain=url.
20 Table B-12 – Cookie parameter explanation
Parameter Explanation
AssociationID Identifier of the association. The server shall send different identifiers for all the con-
nections it holds.
Expires This parameter shall be consider as the maximum Time To Live of the connection.
The format is:
Wdy, dd-mmm-yyyy hh:mm:ss GMT
path The service that need the association
Domain Server’s URL.
21
22 If the associationID is needed in more than one OPC XML-DA services, the server shall in-
23 clude different cookies each one related to one OPC XML-DA service.
24 Once the client receives this information, the association identifier shall be sent in all the re-
25 quests sent to the server: Cookie: AssociationID = AssocValue.
26 On the reception of this header the server might send the same associationID with a new ex-
27 piration date to keep the connection open longer that the previous TTL.
28 The server shall keep a timer so if no message is received with one of the AssociationIDs
29 consider as active, the association shall be considered lost. On the reception of a message
30 with an AssociationID that is no valid in the server-side, a new AssociationID shall be pro-
31 vided so a new connection shall be created.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 130 - 88/288/CDV
IEC 61400-25 Client OPC XML-DA Client Mapping OPC XML-DA Server Mapping
ServiceReq
OPC XML-DA Request
AssociateInd
ServiceInd
AssociateResp
ServiceResp
OPC XML-DA Response HTTP Response

Set-Cookie AssociationID
= AssocID expires = Tue,
27 Jul 2006 21:00:00 UTC
ServiceConf path = myPath
domain = MyDomain
ServiceReq
OPC XML-DA Request

HTTP Request
Cookie AssociationID = AssocID
ServiceInd
ServiceResp
OPC XML-DA Response HTTP Response

Set-Cookie AssociationID
= AssocID expires =
ServiceConf Tue, 27 Jul 2006 21:00:30
UTC
path = myPath
domain = MyDomain
3
4 Figure B-3 – Sequence of services to establish an association
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 131 - 88/288/CDV
1 B.5.1.2.2 Release
2 The Release service shall not map to any specific OPC XML-DA service. The client who de-
3 sires to close an association shall stop using the AssociationID cookie in its messages. Once
4 the timer set in the server expires, the connection shall be considered released.
5 B.5.1.2.3 Abort (informative)
6 This clause describes how an abort mechanism can be implemented within the OPC XML-DA
7 sequence of messages interchanged.
8 B.5.1.2.3.1 Client side
9 An abort request shall erase the Cookie with the AssociationID so that association shall be
10 considered finished.
11 An Abort indication shall be sent to the application each time the server replies with a differ-
12 ent AssociationID to the provided in the request. In that case, the Abort indication shall be fol-
13 lowed by the Association indication and the confirmation of the OPC service requested.
14 B.5.1.2.3.2 Server side
15 An abort request shall erase the AssociationID requested so that association shall be consid-
16 ered over.
17 An Abort indication should be sent to the application each time an association is consider lost.
18 An association shall be considered lost if there has not been activity during the preconfigured
19 time in the server.
20 B.5.2 Server class model
21 B.5.2.1 Server class services
22 B.5.2.1.1 GetServerDirectory
23 This service allows a client to retrieve the list of Logical Devices that the server holds. This
24 service shall map to the OPC XML-DA Browse. The parameters of the Browse service shall
25 be as defined below.
26 Table B-13 – IEM GetServerDirectory mapping

(referencing
IEC 61850-7-2)
Request Browse
-ObjectClass -- “LogicalDevice”. Files are not con-
sidered within this mapping.
Response + BrowseResponse (+)
- Reference 0..n] - Elements: ItemName LDRef
Response – BrowseResponse (-)
- ServiceError - Errors (OPCErrors)
27
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 132 - 88/288/CDV
2 Table B-14 – IEM GetServerDirectory mapping detailed
GetServerDirectory OPC XML-DA parameters M/C/O/I/N Constraint

parameters
Request Browse
E PropertyNames N
@ LocaleID O
@ ClientRequestHandle O
@ ItemPath N or “” both missing or both empty
@ ItemName N or “” both missing or both empty
@ ContinuationPoint O See Note 1.
@ MaxElementsReturned O See Note 1.
@ BrowseFilter N
@ ElementNameFilter N
@ VendorFilter N
@ ReturnAllProperties N
@ ReturnPropertyValues N
@ ReturnErrorText O
Response+ BrowseResponse
E BrowseResult M
E Elements M Shall exist as many “Elements”
as Logical Devices in the
Server.
E Properties C Should not come in the re-
quest.
Reference @ Name M
@ ItemPath M
Reference @ ItemName M
@ IsItem M
@ HasChildren M Shall be “true”
E Errors N Must not appear in a positive
response.
Response- BrowseResponse
E BrowseResult M
E Elements N In the negative response there
should not be any element.
E Properties N
@ Name N
@ ItemPath N
@ ItemName N
@ IsItem N
@ HasChildren N
ServiceError E Errors M See Note 2
E Text C
@ ID M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 133 - 88/288/CDV
E: OPC XML-DA service element

@: OPC XML-DA attribute
1
2 NOTE 1 Its use is optional in the client side.
3 NOTE 2 Any error code returned in this service should map to the IEM ServiceError “failed-due-to-
4 server-constraint”.
5
6 B.5.3 Logical device class model
7 B.5.3.1 Logical device class services
8 B.5.3.1.1 GetLogicalDeviceDirectory
9 The mapping of this service shall be as defined below.
10 Table B-15 – IEM GetLogicalDeviceDirectory
IEC 61400-25-2 OPC XML-DA comment

Request Browse
- LDRef - ItemName
- LNRef [3..n] - Elements: ItemName
11
12 Table B-16 – IEM GetLogicalDeviceDirectory mapping detailed
GetLogicalDevice Di- OPC XML-DA parameters M/C/O/I/N Constraint

rectory parameters
Request Browse
E PropertyNames N
@ LocaleID O
@ ItemPath N
@ ItemName M The string shall be the Logical-
Device reference
@ ContinuationPoint O
@ MaxElementsReturned O
@ BrowseFilter N
@ VendorFilter N
@ ReturnErrorText O
E BrowseResult M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 134 - 88/288/CDV
E Elements M Shall exist as many “Elements”

as Logical Nodes in the Logical
Device.
E Properties C Should not come in the request.
@ Name M
@ ItemPath M
Reference @ ItemName M
@ IsItem M
response.
@ ContinuationPoint C
@ MoreElements C
E BrowseResult M
E Properties N
@ Name N
@ ItemPath N
@ ItemName N
@ IsItem N
@ HasChildren N
ServiceError E Errors M See Table B-17
E Text C
@ ID M
@ ContinuationPoint N
@ MoreElements N

1
2 Table B-17 – GetLogicalDeviceDirectory negative response mapping to IEM ServiceEr-
3 ror
IEM ServiceError OPC Error Code

Parameter-value-inappropriate E_INVALIDITEMNAME, E_UNKNOWNITEMNAME
Failed-due-to-server-constraint Any other code
5 B.5.4 Logical node class model
6 An instance of an IEM LogicalNode shall be a branch in the OPC hierarchy.
7 B.5.4.1 Logical node class attributes
8 This mapping only supports the existence of Data inside the Logical Node class. The Data
9 shall be mapped as branch-items just below the logical node in the hierarchy of the OPC
10 XML-DA server.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 135 - 88/288/CDV
1 B.5.4.2 Logical node class services
2 B.5.4.2.1 GetLogicalNodeDirectory
3 The OPC XML-DA mapping only allows the use of the “DATA” IEMClass. The specification of
4 anyother IEMClass can not be mapped using this mapping.
5 If the IEMClass specified is DATA the mapping shall be as defined in Table B-19.
6 Table B-18 – IEM GetLogicalNodeDirectory mapping

Request Browse
- LNRef - ItemName
- ACSI class
- InstanceName [0..n] - Elements: Name
7
8 Table B-19 – IEM GetLogicalNodeDirectory mapping detailed
GetLogicalNode Di- OPC XML-DA parameters M/C/O/I/N Constraint

rectory parameters
Request Browse
E PropertyNames N
@ LocaleID O
@ ItemPath M Must be empty
@ ItemName M The string shall be the
LogicalNode reference
@ BrowseFilter N
@ VendorFilter N
@ ReturnErrorText O
E BrowseResult M
E Elements M Shall exist as many “Ele-
ments” as Datas in the
Logical Node.
E Properties N
Reference @ Name M
@ ItemPath M
@ ItemName M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 136 - 88/288/CDV
@ IsItem M Shall be “true”

E Errors N Must not appear in a posi-
tive response.
@ MoreElements C
E BrowseResult M
E Elements N In the negative response
there should not be any
element.
E Properties C
@ Name N
@ ItemPath N
@ ItemName N
@ IsItem N
@ HasChildren N
ServiceError E Errors M See Table B-20.
E Text O
@ ID M
@ MoreElements N

1
2 Table B-20 – GetLogicalNodeDirectory negative response mapping to IEM ServiceError

Parameter-value-inappropriate E_INVALIDITEMNAME, E_UNKNOWNITEMNAME
Failed-due-to-server-constraint Any other code.
4 B.5.5 Data class model
5 An IEM Data class shall be mapped to a branch in the hierarchy OPC. Its primitive data attrib-
6 ute shall be the Items in the leafs of the OPC XML-DA tree.
7 Functional Constrained Data
8 The Functional Constrained Data shall map to a OPC XML-DA ItemName and ItemPath. The
9 format shall be as defined in the IEM.
10
ItemName LDName/LNName.DataName[.DataName[. …]]
ItemPath FC
11
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 137 - 88/288/CDV
1 Functional Constrained DataAttribute
2 The Functional Constrained DataAttribute shall map to a OPC XML-DA ItemName and Item-
3 Path. The format shall be as defined in the IEM.
4
ItemName LDName/LNName.DataName[.DataName[. …[DataAttribute[. …]]]
ItemPath FC
5
6 Note: the [] characters should not be used in the reference. They express that there can exist more levels in thre
7 hierarchy.
8 ItemPath
9 The ItemPath in the OPC XML-DA is defined as a server specific mechanism to help the
10 server in order to find the information requested by the client.
11 Inside this mapping, the ItemPath specifies the functional constraint that is requested by the
12 client. It shall be used as a filter mechanism. If there is an attribute that includes more than
13 one functional contraint, the ItemPath will specify the one that is requested.
14 In the Browse service, if there is no ItemPath specified, all the items in the specified hierarchy
15 level are returned. If the client specifies the use of an specific ItemPath, only the elements
16 that include the requested functional constraint shall be returned.
17 B.5.5.1 Data class services
18 B.5.5.1.1 GetDataValues
19 The IEM GetDataValues shall be mapped to the OPC XML-DA Read service. The mapping of
20 the IEM parameters shall be as defined below.
21 Table B-21 – IEM GetDataValues mapping

Request Read
- Reference - ItemList / Items [1..n]: ItemName ,
ItemPath
(FCD or FCDA)
Response + ReadResponse
- DataAttributeValue[1..n] - RItemList / Items [1..n]: Value
- ServiceError - RItemList / Items [1..n]: ResultID
- Errors (OPCErrors)
22
23 Table B-22 – IEM GetDataValues mapping detailed
GetDataValues pa- OPC XML-DA parameters M/C/O/I/N Constraint

rameters
Request Read
E Options M
@ ReturnErrorText O
@ ReturnDiagnosticInfo O
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 138 - 88/288/CDV
@ ReturnItemTime N
@ ReturnItemPath C See Note 1.
@ ReturnItemName C See Note 1.
@ RequestDeadline N
@ ClientRequestHandle C See Note 1.
@ LocaleID O
Reference E ItemList M
@ ItemPath N
@ ReqType N
@ MaxAge N
E Items M
@ ItemPath M FC of the FCD or FCDA
@ ReqType N
@ ItemName M ObjectReference of Data
@ ClientItemHandle C
@ MaxAge N
Response+ ReadResponse
E ReadResult M
E RItemList M
DataAttributeValue E Items M
E Diagnostic Info C
E Value M
E Quality C See explanation in B.4.6.4.5
@ ValueType Quali- N
fier
@ ItemPath C If specified in the request.
@ ItemName C If specified in the request.
@ ClientItem Handle C If specified in the request.
@ TimeStamp M See explanation in B.4.6.4.4.
@ ResultID O
response.
Response- ReadResponse
E ReadResult M .
E RItemList M
E Items M The Items that could be
Read should appear.
E Diagnostic Info C
E Value M
E Quality C
@ ValueType Quali- C
fier
@ ItemPath C If specified in the request.
@ ItemName C If specified in the request.
@ ClientItem Handle C If specified in the request.
@ TimeStamp N See explanation in B.4.6.4.4.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 139 - 88/288/CDV
@ ResultID C The items whose read proc-

ess failed shall include this
field.
ServiceError E Errors M Shall be as defined in Table
B-23
E Text O
@ ID M
1
2 Note 1: Either ItemName and ItemPath or the ItemHandle shall be returned in the response .
3
4 If the “Reference” specified by the application specifies an FCDA that holds a basicType in-
5 side, the Read service shall include only one Item in the request. If the “Reference” is an FCD
6 or a composite FCDA, the client mapping to OPC XML-DA has to split the FCD or FCDA in its
7 primitive attributes and it shall include all of them in the OPC XML-DA Read service. The way
8 this decomposition is performed is a local issue in the client side.
9 The mapping layer in the server side shall map the OPC Read service to the IEM GetData-
10 Values Indication.
11 The reception of any negative result for any of the items requested shall be considered as a
12 negative response of the GetDataValues service. The mapping of the ServiceError is defined
13 in the Table B-23.
14 Table B-23 – GetDataValues negative response mapping to IEM ServiceError

Access-violation E_ACCESS_DENIED
Parameter-value-inappropriate E_INVALIDITEMNAME
Parameter-value-inconsistent E_INVALIDITEMPATH
Parameter-value-inappropriate E_UNKNOWNITEMNAME
Parameter-value-inconsistent E_UNKNOWNITEMPATH
Failed-due-to-server-constraint Any other error code
15
16 B.5.5.1.2 SetDataValues
17 The IEM SetDataValues shall be mapped to the OPC XML-DA Write service. The mapping of
18 the IEM parameters shall be as defined in Table B-25
19 Table B-24 – IEM SetDataValues mapping

Request Write
- Reference - ItemList / Items [1..n]: ItemName ,
ItemPath
(FCD or FCDA)
- ItemList / Items [1..n]:Value
- DataAttributeValue[1..n]
Response +
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 140 - 88/288/CDV

2 Table B-25 – IEM SetDataValues mapping detailed
SetDataValues pa- OPC XML-DA parameters M/C/O/I/N Constraint

rameters
Request Write
E Options M
@ ReturnErrorText O
@ ReturnDiagnosticInfo N
@ ReturnItemTime N
@ ReturnItemPath M Value shall be “true”
@ ReturnItemName M Value shall be “true”
@ RequestDeadline N
E ItemList
E Items M
E Diagnostic Info N
DataAttributeValue E Value M
E Quality N
@ ValueType Quali- N
fier
Reference @ ItemPath M FC of the FCD or FCDA
Reference @ ItemName M ObjectReference of Data
@ ClientItem Handle O
@ TimeStamp O
@ ResultID O
@ ReturnValuesOnReply M
Response+ WriteResponse
E WriteResult M .
E RItemList M
E Items M The Items that could be written
should appear.
E Diagnostic C
Info
E Value C
E Quality C
@ ValueType N
Qualifier
@ ItemPath C
@ ItemName C
@ ClientItem C
Handle
@ TimeStamp M
@ ResultID O
E Errors N Must not appear in a positive re-
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 141 - 88/288/CDV
sponse.
Response- WriteResponse
E WriteResult M
E RItemList O
E Items O
E Diagnostic Info C
E Value C
E Quality C
@ ValueType Quali- C
fier
@ ItemPath C
@ ItemName C
@ ClientItem Handle C
@ TimeStamp C
@ ResultID M
ServiceError E Errors M Shall be as defined in Table B-26
E Text C
@ ID M
2 If the “Reference” specified by the application specifies an FCDA that holds a basicType in-
3 side, the Write service shall include only one Item in the request. If the “Reference” is an FCD
4 or a composite FCDA, the client mapping to OPC XML-DA has to split the FCD or FCDA in its
5 primitive attributes and it shall include all of them in the OPC XML-DA Write service. The way
6 this decomposition is performed is a local issue in the client side.
7 The mapping layer in the server side shall map the OPC Write service to the IEM SetDataVal-
8 ues Indication. The Write service shall be executed as an atomic service, i.e. either the value
9 for every item or for none of them is written. In the WriteResponse there shall be either a Re-
10 sultID for each item or for none of them.
11 In the negative response the IEM ServiceError shall map to an OPC Error Code of all the
12 items requested. The mapping of the ServiceError is defined in the Table B-26
13 Table B-26 – SetDataValues negative response mapping to IEM ServiceError

Access-violation E_READONLY
Parameter-value-inconsistent E_INVALIDITEMPATH
Parameter-value-inconsistent E_UNKNOWNITEMPATH
Type-conflict E_BADTYPE
14
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 142 - 88/288/CDV
1 B.5.5.1.3 GetDataDirectory
2 The IEM GetDataDirectory shall map to an OPC XML-DA Browse service. If the number of
3 elements exceeds the maximum number of references specified by the client in the request,
4 a sequence of Browse services of the reference shall be issued.
5 The former or the latter approach depends on the number of references returned and the lim-
6 its imposed by the client in the MaxElementsReturned attribute of the Browse server, or the
7 limits of the server: “MaxItemsReturned”.
8 Table B-27 – IEM GetDataDirectory mapping

Request Browse
- DataRef - ItemName
- DataAttributeName[1..n] - Name
10 Table B-28 – IEM GetDataDirectory mapping detailed
GetDataDirectory pa- OPC XML-DA parameters M/C/O/I/N Constraint

rameters
Request Browse
E PropertyNames N
@ LocaleID O
@ ItemPath N
@ ItemName M The string shall be the Data
reference
@ BrowseFilter N
@ VendorFilter N
@ ReturnErrorText O
E BrowseResult M
E Elements M Shall appear as many “Ele-
ments” as the number of items
in the first level of dependency
of the Data.
E Properties N
Reference @ Name M
@ ItemPath M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 143 - 88/288/CDV
@ ItemName M
@ IsItem M Shall be “true”
response.
@ MoreElements C
E BrowseResult M
E Properties N
@ Name N
@ ItemPath N
@ ItemName N
@ IsItem N
@ HasChildren N
ServiceError E Errors M See Table B-29
E Text C
@ ID M
@ MoreElements N
2 The negative response shall map as defined in Table B-29
3 Table B-29 – GetDataDirectory negative response mapping to IEM ServiceError

5 B.5.5.1.4 GetDataDefinition
6 The IEM GetDataDefinition service shall map in a sequence of OPC XML-DA Browse services
7 in order to know the “type” of all the items that are below in the hierarchy of the requested
8 reference of a Data.
9 On the recepción of the GetDataDefinition service the client shall request a Browse service as
10 in the GetDataDirectory. For each element returned that has the “HasChildren” attribute set to
11 “true”, a new Browse service shall be requested. Once the full list of attributes that build the
12 data are in the client side, the confirmation shall be delivered to the client application.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 144 - 88/288/CDV
1 In the server side, the difference between the GetDataDefinition and the GetDataDirectory
2 service consist of the use of the attributes:
ReturnPropertyValues Y
PropertyNames “BasicType”,”FC”
3
4 The BasicType property is a new property used to define the type of the primitive dataattrib-
5 utes that hold the information in the model.
6 The negative response shall map as in the GetDataDirectory service. See Table B-29.
7 B.5.6 Data set class model ( informative )

8 Note: The concept of Data set does not exist in the server side. This section describes how the client could use the
9 IEM DataSet services to handle Data sets using OPC XML-DA services. It is described as an example and it is not
10 requested for any kind of implementation claiming conformance with this mapping.
11 B.5.6.1 Data set class
12 The OPC XML-DA specification does not include any element able to group in a static way a
13 list of items (FCDs or FCDAs).
14 In this mapping the server side shall not allow configured DATA-SET.
15 The functionality of the client shall only allow the creation of non-persistent DATA-SETs. The
16 DATA-SETs shall be dynamically created by the clients and stored internally in the client side.
17 The IEM DATA-SET class shall only be available in the client side. The client shall store in-
18 ternally the information about the contents of the DATA-SET so the application shall manipu-
19 late them as if the DATA-SET were physically implemented in the server side.
20 Retrieving information using the DataSets services allows the client application to recover the
21 current value of a selected group of items withouth having to specify the complet list of items.
22 B.5.6.2 Data set attributes
23 They are not mapped.
24 B.5.6.3 Data set services

25
26 The creation of the DATA-SET shall check that the elements the client has requested to build
27 the DATA-SET exist in the server. Once this has happened the client internally stores the list
28 of items that compose the DATA-SET requested.
29 The retrieve of the DATA-SET values shall cause the sending of a Read service of all the
30 items that build the DATA-SET. With this service the client application will be able to manipu-
31 late groups of data of different branches of the model without needing to specify the complete
32 list of references.
33 B.5.6.3.1 CreateDataSet
34 The IEM CreateDataSet service shall map to a sequence of Browse services in order to get
35 the full list of primitive items that are defined by the list of elements that shall compose the
36 DATA-SET.
37 If any of the OPC Browse services return a failure the CreateDataSet service shall return a
38 ServiceError to the client application.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 145 - 88/288/CDV
1 Only non-persistent DATA-SET are allowed.
2 If the service returns a positive confirmation, the client should store the list of basic data at-
3 tributes associated to the DataSetReference requested by the application. How this informa-
4 tion is stored is a local issue.
ACSI Client OPC-XML-DA Client OPC-XML-DA Server
CreateDataSetRequest
BrowseItem()
Browse Item1
Browse Item2
Mensaje1
Mensaje2
BrowseItem()
CreateDataSetConfirmation
7 Figure B-3 – CreateDataSet sequence of services
9 Table B-30 – Mapping of CreateDataSet service parameters
CreateDataSet service parame- OPC XML-DA service or parameter Constraint

ters
Request Browse request services
DataSetRefence -
DSMemberRef[1..n] ItemName
Confirmation+ Browse response services If all browse services succeded.
Result
Confirmation - Browse response services If any browse service failed.
ServiceError OPC Errorcode
The ServiceError shall be as
defined in
Table B-31
10
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 146 - 88/288/CDV
1 Table B-31 – CreateDataSet negative response mapping to IEM ServiceError
IEM ServiceError OPC XML-DA ErrorCode

failed-due-to-server-constraint Internal client error. Client request a persistent DATA-
SET
instance-in-use Internal client error. Client detects the DATA-SET al-
ready exists.
parameter-value-inconsistent E_INVALIDITEMNAME
E_INVALIDITEMPATH
failed-due-to-communication-constraint Any unmapped error code
2
3 B.5.6.3.2 DeleteDataSet
4 This service shall delete the internal structure that stores the list of basic data attributes that
5 compose the server.
6 No communication services are needed.
7 B.5.6.3.3 GetDataSetDirectory
8 This service is not included in this mapping. Using this mapping, all the DATA-SETs are con-
9 figured by the client online so, the information about the elements that compose the DATA-
10 SETs are already known.
11
12 B.5.6.3.4 GetDataSetValues
13 The IEM GetDataSetValues service shall map to the OPC XML-DA Read service. The list of
14 OPC Items that build the DATA-SET have been stored by the SCSM in the client side during
15 the CreateDataSet service. The mapping of the IEM service parameters shall be the same as
16 the ones defined in the GetDataValues service.
17 If the DataSetReference specified has not a list of items stored, the service shall return a Ser-
18 viceError as specified in Table B-32.
19 Table B-32 – GetDataSetValues negative response mapping to IEM ServiceError

instance-not-available The DATA-SET requested is not in the list of the
DATA-SETs of the client.
access-violation E_ACCESS_DENIED
failed-due-to-server-constraint Any unmapped error code
20
21 B.5.6.3.5 SetDataSetValues
22 The IEM SetDataSetValues service shall map to the OPC XML-DA Write service of the full list
23 of basic data attributes that compose the DATA-SET. The list of OPC Items that build the
24 DATA-SET have been stored by the SCSM in the client side during the CreateDataSet ser-
25 vice.
26 The mapping of the IEM service parameters shall be as the ones defined in the SetDataVal-
27 ues service.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 147 - 88/288/CDV
1 If the DataSetReference specified has not a list of items the service shall return a ServiceEr-
2 ror as specified in Table B-33.
3 Table B-33 – SetDataSetValues negative response mapping to IEM ServiceError

instance-not-available The DATA-SET requested is not in the list of the
DATA-SETs of the client.
access-violation E_ACCESS_DENIED
Type-conflict E_BAD_TYPE
failed-due-to-server-constraint Any unmapped error code
5 B.5.7 Report class model
6 IEC 61400-25-3 describes a server guided reporting mechanish where the server detects the
7 changes in its information model (events), sending these information inside the structure of
8 the report message following the rules specified by the client in the configuration of the re-
9 porting mechanishm.
10 Inside the OPC XML-DA, the reporting mechanishm uses a different approach. The client has
11 to interrogate periodically the server to receive the last group of changes (events).
12 B.5.7.1 OPC XML-DA reporting attributes
13 The way the OPC XML-DA responses are sent depends on some attributes included in the
14 service request sent by the client. The most important attributes in OPC XML-DA are:
15 Holdtime - instructs the server to hold off returning from the SubscriptionPolledRefresh call
16 until the specified absolute server time is reached.
17 Waittime - instructs the server to wait the specified duration (number of milliseconds) after
18 the Holdtime is reached before returning if there are no changes to report. A change in one of
19 the subscribed items, during this wait period, will result in the server returning immediately
20 rather than completing the wait time.
21 EnableBuffering - By specifying EnableBuffering = True, the server will save all value
22 changes detected at the specified rate in a buffer for return to the client at the next Subscrip-
23 tionPolledRefresh request.
24
25 Table B-34 – OPC Subscription attributes’ constrained value
OPC attributes IEC 61400-25 constraint

HoldTime Near zero
WaitTime Greater than 0
EnableBuffering TRUE
26
27 Note: Using a HoldTime and WaitTime of zero, the server shall reply inmediately with the last set of changes de-
28 tected. These changes shall be buffered (EnableBuffering set to true) in order not to lose any event.
29
30 B.5.7.2 OPC XML-DA reporting services
31 OPC XML-DA supports the following subscription based services: Subscribe, Subscription-
32 PolledRefresh, and SubscriptionCancel. Subscribe is used to initiate a subscription contract
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 148 - 88/288/CDV
1 with a server. SubscriptionPolledRefresh is called periodically to acquire the latest item value
2 changes. SubscriptionCancel is used to terminate the subscription contract with the server.
3 B.5.7.3 IEC 61400-25-3 reporting services
4 B.5.7.3.1 AddSubscription
5 The AddSubscription service defines a set of variables that the server has to monitor in order
6 to detect their changes and notify them to the clients that requested this behaviour.
7 Table B-35 – AddSubscription service parameter constraints
Request
RcbRef Not mapped to communication service.
RCBType
ReportIdentifier [0..1] Not mapped to communication service.
ReportEnable [0..1] Not mapped. ReportEnable always consid-
ered TRUE.
DataSetReference [0..1] Not mapped to communication service.
OptionalFields [0..1] Sequence-number = N
Report-time-stamp = Y
Reason-for-inclusion = N
Data-set-name = Y
Data-reference = Y
Buffer-overflow = Y
EntryID = N
Conf-Revision = N
BufferTime [0..1] The client shall request a SubscriptionPolle-
dRefresh each time this timer expires.
TriggerOptions [0..1] dchg = Y
qchg= Y
dupd = N
integrity-period = Y
general-interrogation = N
IntegrityPeriod [0..1] The client shall request a SubscriptionPolle-
dRefresh with the attribute RequestAllItems
set to true each time this timer expires.
DSMemberRef [1..n] Only FCDA that references basicTypes are
allowed.
Response+
Response–
ServiceError
9 Table B-36 – Mapping of AddSubscription service parameters
AddSubscription pa- OPC XML-DA parameters M/C/O/I/N Constraint

rameters
Request Subscribe
@ ReturnValuesInReply N
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 149 - 88/288/CDV
@ SubscriptionPingRate M
E Options N
E ItemList M
@ ItemPath N
@ ReqType N
@ Deadband N
@ RequestedSampleTime C locale issue; M if not set on
List-level
@ EnableBuffering M Always “True”
E Items
DSMemberRef @ ItemPath M The FC of the FCDA
@ ReqType O
DSMemberRef @ ItemName M The ObjectReference of the
FCDA
@ ClientItemHandle O
@ Deadband M Value “0”
@ RequestedSampleTime C local issue; M if not set for
every item on the Item-level
@ EnableBuffering M Always “True”
Response+ SubscribeResponse
@ ServerSubHandle M
E SubscribeResult M
E RItemList M
@ RevisedSamplingRate
Reference E Items M
@ RevisedSamplingRate O
E ItemValue M
response.
Response- SubscribeResponse
@ ServerSubHandle M
E SubscribeResult M
E RItemList M
@ RevisedSamplingRate C
Reference E Items M
@ RevisedSamplingRate C
E ItemValue M
E Errors M See Table B-37

1
2 Note 1: If there is any Error element in the SubscribeResponse service, the IEM Addsubscription service shall be
3 considered as failed.
4
5 On the reception of the OPC XML-DA SubscribeResponse service with no errors, the client
6 mapping shall:
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 150 - 88/288/CDV
1 1) store internally the ServerSubHandle linked to the RCBRef, ReportID, DataSetRefer-

2 ence and OptFields, received in the AddSubscription request,
3 2) start a periodical timer that shall request each integrity period a SubscriptionPolle-
4 dRefresh with the attributes:
HoldTime 0
WaitTime 0
ReturnAllItems True
5 If the integrity period is zero, this timer shall not be created.
6 3) start a periodical timer that shall request each BufferTime a SubscriptionPolledRe-

7 fresh with the attributes:
HoldTime 0
WaitTime 0
ReturnAllItems False
8 If the buffertime period is zero, the client shall send the requests as fast as it consider
9 appropriate in order to avoid colapsing the network bandwith.
10 Note: using this mapping it is recommended to use a BufferTime higher than 500ms to improve the performance on
11 the network.
12
13 An OPC XML-DA subscription will be created if at least one of the specified items is valid. If
14 the Subscribe request fails for at least one of the specified items the response has to be
15 mapped to a negative AddSubscription response and the subscription has to be canceled us-
16 ing the OPC-MXL-DA SubscriptionCancel service.
17
18 Table B-37 – AddSubscription negative response mapping to IEM ServiceError

Instance-not-available E_INVALIDITEMNAME
Parameter-value-inappropriate E_INVALIDITEMPATH
Instance-not-available E_UNKNOWNITEMNAME
Parameter-value-inappropriate E_UNKNOWNITEMPATH
Failed-due-to-server-constraint Any other error code.
19
20 B.5.7.3.2 RemoveSubscription
21 The IEM RemoveSubscription service shall be mapped to the OPC XML-DA Subscription
22 Cancel. The serverSubhandle shall be the one returned on the Subscription service.
23 Table B-38 – Mapping of RemoveSubscription service parameters
RemoveSubscription OPC XML-DA parameters M/C/O/I/N Constraint

parameters
Request SubscriptionCancel
@ ServerSubHandle M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 151 - 88/288/CDV
RCBRef @ ClientRequestHandle M
Response+ SubscriptionCancel Response

@ ClientRequestHandle M
Response- SubscriptionCancel Response

@ ClientRequestHandle M

2 Table B-39 – Fault mapping to IEM ServiceError

Instance-not-available E_NOSUBSCRIPTION
Failed-due-to-server-constraint E_SERVERSTATE, Any other fault code.
4 B.5.7.3.3 Report
5 The Report service shall be mapped to the OPC XML-DA SubscriptionPolledRefreshResponse

6 service.
7 Table B-40 – Report service parameters
Report Constraint
RptID Included in the client side by
the mapping.
OptFlds Included in the client side by
the mapping.
SeqNum Not Available.
SubSeqNum Not Available.
MoreSegmentsFollow Not used.
DatSet If requested in the OptFlds, it
shall be included in the client
side by the mapping.
BufOvfl Available.
ConfRev Not Available.
TimeOfEntry Available.
DataRef Available.
Value Available.
ReasonCode Not Available.
9 Table B-41 – Mapping of Report service parameters
Report parameters OPC XML-DA parameters M/C/O/I/N Constraint
SubscriptionPolledRefresh
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 152 - 88/288/CDV
@ HoldTime M Set to 0
@ WaitTime M Set to 0
@ ReturnAllItems M Depends on the case
E Options
E ServerSubHandle M
Report SubscriptionPolledRefresh Response

BufferOverflow @ DataBufferOverflow
E SubscriptionPolledRefreshResul M
t
E InvalidServerSubHandles M
E RitemList M
@ SubscriptionHandle M
DataRef and DataValue E Items M
E Errors M
2 On the reception of the SubscriptionPolledRefreshResponse the client shall have to build the
3 Report messages. Due to the “EnableBuffering” attribute, the SubscriptionPolledRefreshRe-
4 sponse can include several samples of the same item. If this situation happens, the client side
5 shall:
6 • split the message in two different report messages, so no change is lost, if the item
7 represents an status value (ST).
8 • either split the message or remove the previous value if the item represents a meas-
9 ured value (MX).
10 Depending on the OptFlds stored by the client on the Subscribe service, different elements of
11 the Report as the ReportId, DatSetRef,… (also kept by the client) shall be included in the Re-
12 port Indication.
13 B.5.8 Control model
14 The IEC 61400-25 control model is accessed via the following OPC XML-DA services:
15 - Read,
16 - Write
17 - Subscribe, SubscribePolledRefresh, RemoveSubscription
18 B.5.8.1 IEM control models supported
19 The Table B-42 specifies the control models supported bythis mapping.
20 Table B-42 – Control models supported in this mapping
IEC 61400-25-3 (IEC 61850-7-2)CtlModels Supported

1 direct-with-normal-security Y
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 153 - 88/288/CDV
2 sbo-with-normal-security Y
3 direct-with-enhanced-security Y
4 sbo-with-enhanced-security Y
2 B.5.8.2 IEM Control services supported
3 The Table B-43 specifies the control services provided by this mapping.
4 Table B-43 – Control services supported
IEC 61400-25-3 (IEC 61850-7-2) Supported

Select Y
SelectWithValue Y
Operate Y
TimeActivatedOperate Y
Cancel Y
CommandTermination Y
6 B.5.8.3 Control Service Parameters
7 Some of the parameters of the control services are neither part of the Information Model nor
8 do they semantically match any of the OPC XML-DA service parameters. The control model
9 services cannot be mapped directly to any OPC XML-DA web service using the information
10 model.
11 Table B-44 – AddCause mapping to OPC Error Code
AddCause OPC Error Code Extended Enumerated Value

Select-failed E_ADDCAUSE_SELECT_FAILED 3
Invalid-position E_ADDCAUSE_INVALID_POSITION 4
Position-reached E_ADDCAUSE_POSITION_REACHED 5
Parameter-change-in- E_ADDCAUSE_PARAMETER_CHANGE_IN_EXEC 6
execution
Step-limit E_ADDCAUSE_STEP_LIMIT 7
Command-already-in- E_ADDCAUSE_COMMAND_ALREADY_IN_EXEC 8
execution
Abortion-by-cancel E_ADDCAUSE_BY_CANCEL 9
Time-limit-over E_ADDCAUSE_TIME_LIMIT_OVER 10
12
13 To solve this issue, these parameters of the control services are mapped to writeable cus-
14 tom item properties that are assigned to the dataAttributes of each control object. The list of
15 writeable custom item properties is described in Table B-45.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 154 - 88/288/CDV
2 Table B-45 – Control model writable custom item properties
Control service Writeable custom item property

parameter
ItemName ItemPath IEC 61400-25-2 BasicType
T DataRef .ctlVal.t CO TimeStamp
Test DataRef .ctlVal.test CO Boolean
Check DataRef .ctlVal.check CO CodedEnum
DataRef .ctlVal.service CO ENUMERATED
(operate | taOperate |sbo |sbow |cancel )
1= operate
2 = taOperate
3 = sbo
4= sbow
5 = cancel
AddCause DataRef .ctlVal.cmdState CO ENUMERATED
(not-in-use | executing-command | status-changed |
AddCause )
0 = not-in-use
1 = executing-command
2 = status-changed (to the requested value and
output is deactivated)
AddCause = if the timer expired but the status did
not change to the requested value; output is deac-
tivated
TimOperRsp DataRef .operTm.taoState CO ENUMERATED
(not-in-use | waiting / timer-activated | command-
executed | AddCause )
0= not-in-use
1= timer-activated
2= command-executed
AddCause : if the timer expired but the requested
action could not be caused
3
4 Note 1: DataRef is used as a placeholder for the ObjectReference of any control data.
5 Note 2: “cmdState” shall only be present in those controllable object where an enhanced security model is used.
6 Note 3: If the CommandTermination service is not supported by the server, the item property “cmdState” does not
7 have to be provided for any control object.
8 Note 4: If the mandatory Operate service is the only control service that is supported by the server, the item prop-
9 erty “service” does not have to be provided.
10 Note 5: If the server does not support the TimeActivatedOperate service, the item property “taoState” does not
11 have to be provided
12 Note 6: The values of the item properties “cmdState” and “taoState” must not be set with a control negative re-
13 sponse.
14 Most of the control services are mapped to the Write service. The writeable custom item
15 property “service” is added to specify the control service that is being requested.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 155 - 88/288/CDV
1 B.5.8.4 Mapping of the control services
2 B.5.8.4.1 Select
3 B.5.8.4.1.1 SelectRequest
4 The Select service shall be mapped to the OPC XML-DA Write service of the “service” write-
5 able custom item property with the value “sbo”.
IEC 61400-25-3 parameter OPC XML-DA Item / Item property Constraint

ControlObjectReference ItemName of the controllable
object.
ItemPath = “CO”
DataRef.ctlVal.service “sbo”
8 B.5.8.4.1.2 Select Response +
9 The Select positive response service shall be mapped to the OPC XML-DA WriteResponse
10 service with a positive result.
11 After the response, the values of the item properties taoState and cmdState (if present) have
12 to be set as follows:
13
Writeable custom item property Value Meaning
DataRef.operTm.taoState “0“ Not-in-use
DataRef.ctlVal.cmdState “0” Not-in-use
14
15 B.5.8.4.1.3 Select Response -
16 The Select negative response service shall be mapped to the OPC XML-DA WriteResponse
17 service with an ErrorCode indicating failure.
18 The custom item properties “taoState” and “cmdState” shall not be modified.
19 B.5.8.4.2 SelectWithValue
20 B.5.8.4.2.1 SelectWithValue Request
21 The SelectWithValue service shall be performed through the use of an OPC XML-DA Write of
22 the values of the following items and item-properties of the controllable object.
23 Table B-46 – SelectWithValue service parameter mapping

object.
ItemPath = “CO”
Value DataRef.ctlVal
DataRef.origin
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 156 - 88/288/CDV
DataRef.ctlNum
DataRef.operTm
T DataRef.ctlVal.T
Test DataRef.ctlVal.Test
Check DataRef.ctlVal.Check
DataRef.ctlVal.service “sbow”
2 B.5.8.4.2.2 SelectWithValue Response+
3 The SelectWithValue positive response shall be performed through the use of an OPC XML-
4 DA Write positive response. Only if all the items returned a positive result the SelectWith-
5 Value service can be considered accepted.
7 to be set as follows.
8
10 B.5.8.4.2.3 SelectWithValue Response-
11 The SelectWithValue negative response shall be performed through the use of an OPC XML-
12 DA Write negative response. The OPC Error code/s should include the AdditionalCause of
13 failure providing the reason of the negative response.
15 B.5.8.4.3 Cancel
16 B.5.8.4.3.1 Cancel Request
17 The Cancel service shall be performed through the use of an OPC XML-DA Write of the val-
18 ues of the items and item-properties of the controllable object. The mapping of parameters is
19 as specified in Table B-47.
20 Table B-47 – Cancel service parameter mapping

object.
ItemPath = “CO”
T DataRef.ctlVal.T
DataRef.ctlVal.service “cancel”
21
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 157 - 88/288/CDV
1 B.5.8.4.3.2 Cancel Response+
2 The cancel response+ shall be performed through the use of an OPC XML-DA WriteResponse
3 that contains no Errors.
5 to be set as follows.
6
8 B.5.8.4.3.3 Cancel Response-
9 The cancel response- shall be performed through the use of an OPC XML-DA WriteResponse
10 that contains “Errors” indicating the failure of the service. The error codes shall be mapped as
11 specified in Table B-48. The AddCause error codes defined in Table B-44 can also be used.
12 Table B-48 – Cancel negative response mapping to IEM ServiceError
IEC 61850-7-2 ServiceError OPC Error Code

Not-supported E_NOTSUPPORTED
Object-not-selected E_SERVERSTATE
Accesss-violation E_ACCESS_DENIED
Instante-not-available E_UNKNOWNITEMNAME
13
15 B.5.8.4.4 Operate
16 B.5.8.4.4.1 Operate Request
17 The operate request service shall be performed through the use of an OPC XML-DA Write of
18 the values of the items and item-properties of the controllable object.
19 Table B-49 - Operate service parameter mapping

object.
ItemPath = “CO”
DataRef.origin
DataRef.ctlNum
T DataRef.ctlVal.T
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 158 - 88/288/CDV
DataRef.ctlVal.service “operate”
2 B.5.8.4.4.2 Operate Response+
3 The operate response+ shall be performed through the use of an OPC XML-DA WriteRe-
4 sponse that contains a WriteResult indicating success.
6 to be set as follows:
7
Writeable custom item property Value Meaning Constraint
DataRef.ctlVal.cmdState “0” Not-in-use if Operate is used within a control model
with normal security
“1” executing command if Operate is used within a control model
with enhanced security.
9 B.5.8.4.4.3 Operate Response-
10 The operate response- shall be performed through the use of an OPC XML-DA WriteRe-
11 sponse that contains an Error indicating the failure of the service. The error codes shall be
12 mapped as specified in Table B-50 and Table B-44.
13 Table B-50 – Operate negative response mapping to IEM ServiceError

Failed-due-to-server-constraint Any other OPC Error code
14

DataRef.ctlVal.cmdState “0” Not-in-use if Operate is used within an simple security
control model
15
16 B.5.8.4.5 TimeActivatedOperate
17 The TimeActivatedOperate request with the first response shall be mapped to the OPC XML-
18 DA Write service.
19 The second response shall be mapped either to a OPC XML-DA Subscribe of the “operTm
20 .taoState” item-property of the controllable object or can be get using the Read service to
21 check when the “operTm.taoState” property changed.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 159 - 88/288/CDV
1 On receipt of a positive WriteResponse the OPC XML-DA client shall request the value of the
2 taoState and of the other item properties whose values are needed for a TimeActivatedOper-
3 ate response. As long as taoState = “timer-activated” the OPC XML-DA client shall continue
4 requesting the values.
5 If “taoState” changes its value to “command-executed”, the client shall create a TimeActivat-
6 edOperate positive confirmation with TimOperRsp = “command-executed”.
7 If “taoState” changes its value to any AddCause code, the client shall create a TimeActivate-
8 dOperate negative confirmation.
9 NOTE: It is left to the client implementation wether the values for the second response are requested via the Read
10 service or the Subscribe mechanism (= Subscribe + SubscriptionPolledRefresh + SubscriptionCancel).
11 B.5.8.4.5.1 TimeActivatedOperateRequest
12 The TimeActivatedOperate request service shall be performed through the use of an OPC
13 XML-DA Write of the values of the items and item-properties of the controllable object.
14 Table B-51 - TimeActivatedOperate service parameter mapping

ControlObjectReference ItemName of the controllable ob-
ject.
ItemPath = “CO”
DataRef.origin
DataRef.ctlNum
DataRef.operTm
T DataRef.ctlVal.T
DataRef.ctlVal.service “taOperate”
15
16 B.5.8.4.5.2 TimeActivatedOperateResponse + (timer-activated)
17 The TimeActivatedOperate positive response shall be performed through the use of an OPC
18 XML-DA WriteResponse that contains no ErrorCodes. With this response, the values of the
19 item properties taoState and cmdState have to be set as follows:

DataRef.operTm.taoState “1“ waiting / timer activated
20
21 B.5.8.4.5.3 TimeActivatedOperateResponse -
22 The TimeActivatedOperate negative response shall be performed through the use of an OPC
23 XML-DA WriteResponse indicating the failure in the ErrorCodes as defined in the Table B-52
24 or using any of the AddCause codes defined in Table B-44.
25 Table B-52– TimeActivatedOperate negative response mapping to IEM ServiceError

Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 160 - 88/288/CDV

Failed-due-to-server-constraint Any other OPC Error code
2 B.5.8.4.5.4 TimeActivatedOperateResponse + (command-executed)
3 The second positive TimeActivatedOperate response has no service associated. The client
4 shall either susbcribe the taoState item property or request an OPC XML-DA Read service to
5 detect the situation.
6 On expiration of the timer the wanted action shall be activated. If the activation was success-
7 ful the state properties have to be set as follows.

DataRef.operTm.taoState “2“ command-executed
DataRef.ctlVal.cmdState “0” Not-in-use if TimeActivatedOperate is used
within an simple security control
model
“1” executing-command if TimeActivatedOperate is used
within a normal security control
model
9 B.5.8.4.5.5 TimeActivatedOperateResponse - (second response)
10 If the activation was not successful only the value of the item property taoState has to be set:

DataRef.operTm.taoState AddCause
11
12 B.5.8.4.6 CommandTermination
13 On the reception of a positive Operate response or a second positive TimeActivatedOperate

14 response the “cmdState” item-property is set to “command-executed”.
15 If the status changed to the requested value, “cmdState” shall be set to “status-changed”.
16 Otherwise the cmdState is set to AddCause.
17 The OPC XML-DA client requests the “cmdState” via the Read service or the Subscribe
18 mechanism.
19 Table B-53 - CommandTermination + service parameter mapping

object.
ItemPath = “CO”
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 161 - 88/288/CDV
T DataRef.ctlVal.T
DataRef.ctlVal.cmdState “status-changed”
2 Table B-54 - CommandTermination - service parameter mapping

object.
ItemPath = “CO”
T DataRef.ctlVal.T
AddCause DataRef.ctlVal.cmdState AddCause error codes
4 B.6 Protocol stack details.
5 To be compliant with this mapping, the following stack of protocols shall be used.
6 Specifications for the data link layer and the physical layer are implementation specifc and beyond the
7 scope of the IEC 61400-25 series.
8 Table B-55 – Protocol stack details
OSI model layer Specification M/O

Name Service specifica- Protocol specifi-
tion cation
Application OPC XML-DA OPC XMLDA 1.01 M
SOAP SOAP version 1.1 M
http://www.w3.org/TR/soap/
Hypertext Transfer RFC 2616 M
Protocol HTTP/1.1
Presentation - - - -
Session - - - -
Transport Transport Layer RFC 2246 O
Secure (TLS)
Internet Control RFC 792 M
Message Protocol
(ICMP)
Transmision Con- RFC 793 M
trol Protocol (TCP)
Network Internet Protocol RFC 791 M
(IP)
Address Resolution RFC 826 M
Protocol (ARP)
Data Link Implementation specific and beyond the scope of the IEC 61400- -
25 series.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 162 - 88/288/CDV
Physical Implementation specific and beyond the scope of the IEC 61400- -
25 series.
1
2 Note 1: The use of HTTPS (SSL) is a local issue, out of scope of this mapping.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 163 - 88/288/CDV
1 Annex C
2 (normative)
3
5 Mapping to ISO 9506 specified in IEC 61850-8-1
7 C.1 General
8 C.1.1 Introduction
9 This Annex describes the use of IEC 61850-8-1 for the mapping of the information model and
10 information exchange model defined in IEC 61400-25-2 and IEC 61400-25-3 to ISO 9506.
11 Almost all service models defined in IEC 61400-25-3 are mapped to ISO 9506 as defined in
12 IEC 61850-8-1. The mapping specified in IEC 61850-8-1 is referenced in this Annex C. The
13 two services (AddSubscriptions and RemoveSubcription) defined in IEC 61400-25-4 are
14 mapped to IEC 61850-8-1. This additional mapping is defined in this Annex C.
15 The QueryLog service defined in IEC 61850-8-1 is extended by a filter parameter (supported
16 by ISO 9506 but not used in IEC 61850-8-1).
17 C.1.2 Scope
18 The scope of the mapping defined in this Annex C is the use of ISO 9506 for the representa-
19 tion to the information model and the information exchange model defined in IEC 61400-25-2
20 and IEC 61400-25-3.
21 The mapping defined in IEC 61850-8-1 is mainly intended for real-time exchange of informa-
22 tion. Clients communicating with servers could be systems that needs to receive real-time in-
23 formation in order to monitor and control the generation process and the related equipment.
24 C.1.3 The mapping architecture
25 The mapping architecture comprises the:
26 1. Mapping of the information model to MMS models (see C.4)
27 2. Mapping of the information exchange services to MMS services (see C.5)
28 3. Communication stacks (see C.6)
29 The mapping for IEC 61400-25-3 is defined IEC 61850-8-1 with the exception of two addi-
30 tional services and an extension of the QueryLog service.
31 The wind power plant information model defined in IEC 61400-25-2 is mapped to a hierarchi-
32 cal structure as defined in clauses 7 to 17 and 20 of IEC 61850-8-1. The corresponding ser-
33 vices are mapped as defined in these clauses.
34 The conceptual mapping is depicted in Figure C-1. The wind power plant information model of
35 IEC 61400-25 is intended to be preserved when mapped to IEC 61850-8-1 MMS services.
36 This especially means that:
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 164 - 88/288/CDV
2 25 that can be retrieved by the services according to table 30.
3 - the client need to interpret the wind power plant information model.
4 - the client accesses the hierarchical wind power plant information model of IEC 61400-25
5 through the services provided by IEC 61850-8-1 and ISO 9506 as defined in this Annex C.
WPP information model of

Master/ Turbine5
Information model (LD „Turbine5“ and its LNs
Client WGEN
WTUR
TurSt
W
mag
Object references and real-time q
values of: t
Turbine5/WTUR.W.mag units
Turbine5/WTUR.W.q db
Turbine5/WTUR.W.t d
map to xx of type „yyy“
according to SCSM as
described in this Annex
local local
interface IEC 61850-8-1 MMS protocol interface
Response
command …
6
7 Figure C-1 – Mapping architecture (conceptual)
8 Table C-1 lists the mappings of the information models and information exchange services to
9 ISO 9506 as defined in IEC 61850-8-1.
10 Table C-1 – Mapping of IEC 61400-25 IEM onto MMS according to IEC 81850-8-1
IEC 6140-25-2 IM Class IEC 61400-25-3 IEM M/O Included in the ISO 9506 model / services
IEC61400-25-3 IEM Class Services mapping
SERVER Y Server
GetServerDirectory O Y GetNameList
ASSOCIATION Application association
Associate M Y Initiate
Release M Y Conclude
Abort O Y Abort
Reject
Cancel
Identify
LOGICAL-DEVICE Y Domain
GetLogicalDeviceDirec- O Y GetNameList
tory
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 165 - 88/288/CDV
IEC 6140-25-2 IM Class IEC 61400-25-3 IEM M/O Included in the ISO 9506 model / services
IEC61400-25-3 IEM Class Services mapping
LOGICAL-NODE Y NamedVariable
GetLogicalNodeDirec- O Y GetNameList
tory
DATA Y NamedVariable
GetDataValues M Y Read
SetDataValues M Y Write
GetDataDirectory O Y GetVariableAccessAttribute
GetDataDefinition O Y GetVariableAccessAttribute
DATA-SET Y NamedVariableList
GetDataSetValues M Y Read
SetDataSetValues O Y Write
CreateDataSet O Y DefineNamedVariableList
DeleteDataSet O Y DeleteNamedVariableList
GetDataSetDirectory O Y GetVariableListAttributes
REPORTING NamedVariable
Report InformationReport
GetBRCBValues O Y Read
SetBRCBValues O Y Write
GetURCBValues O Y Read
SetURCBValues O Y Write
AddSubscription O Y (DefineNamedVariableList)
Write (to RCB)
RemoveSubscription O Y Write (to RCB)
(DeletNamedVariableList)
LOG-CONTROL-BLOCK Y NamedVariable
GetLCBValues O Y Read
SetLCBValues O Y Write
LOG Y Journal
GetLogStatusValues O Y InitializeJournal
QueryLogByTime O Y ReadJournal
QueryLogAfter O Y ReadJournal
CONTROL Control
Select O Y Write
SelectWithValue O Y Write
Cancel O Y Write
Operate M Y Write
CommandTermination O Y InformationReport
TimeActivatedOperate O Y Write
2 C.2 Normative references for Annex C
3 IEC 61850-8-1:2003, Communication networks and systems in substations – Part 8-1 Specific
4 communication service mapping (SCSM) – Mappings to MMS (ISO/IEC 9506 Part 1 and Part
5 2) and to ISO/IEC 8802-3
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 166 - 88/288/CDV
1 ISO 9506-1:2003, Industrial automation systems – Manufacturing Message Specification –

2 Part 1: Service definition
3 ISO 9506-2:2003, Industrial automation systems – Manufacturing Message Specification –

4 Part 2: Protocol specification
5 ISO/IEC ISP 11188-1:1995, Information technology – International Standardized Profile –

6 Common upper layer requirements – Part 1: Basic connection oriented requirements
7 ISO/IEC ISP 11188-3:1996, Information technology – International Standardized Profile –

8 Common upper layer requirements – Part 3: Minimal OSI upper layer facilities
9 ISO/ISP 14226-1:1996, Industrial automation systems – International Standardized Profile

10 AMM11: MMS General Applications Base Profile – Part 1: Specification of ACSE, Presenta-
11 tion and Session protocols for use by MMS

13 AMM11: MMS General Applications Base Profile – Part 2: Common MMS requirements

15 AMM11: MMS General Applications Base Profile – Part 3: Specific MMS requirements
16 RFC 793, Transmission Control Procedure – DARPA Internet Program Protocol Specification,
17 IETF, available at <http://www.ietf.org>
18
19 C.3 Abbreviated terms for Annex C
ACSI Abstract Communication Cervice Interface (defined in 61850-7-2)

Note: In this Annex C the term IEM (see below) will be used instead of ACSI.
LD Logical Device
LN Logical Node
LOG Log
MMS Manufacturing Message Specification (ISO 9506)
SCSM specific communication service mapping (defined in 61850-8-1)
WT Wind Turbine
20
21 C.4 Mapping of the IEC 61400-25 Information Model to ISO 9506 as specified in
22 IEC 61850-8-1
23 The wind power plant information model defined in 61400-25-2 shall be mapped to a hierar-
24 chical structure of ISO 9506 as defined in clauses 7 to 17 and 20 of IEC 61850-8-1. The cor-
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 167 - 88/288/CDV
1 responding services shall be mapped to ISO 9506 as defined in IEC 61850-8-1 (and shown in
2 Table C-1).
4 C.5 Mapping of the extended Information Exchange Model to ISO 9506
5 C.5.1 General
6 This clause describes how the additional abstract IEM services defined in IEC 61400-25-3
7 (AddSubscriptions and RemoveSubcription) and the extended filter parameter for the Query-
8 Log service shall map onto the MMS services as specified in the following clauses.
9 C.5.2 AddSubscription
10 This service shall map to the following sequence of three MMS services:
11 - Step1: Creation of the requested dataset (DefineNamedVariableList) according to Table

12 C-2.
13 - Step2: Configuration of the Report Control Block (Write) according to Table C-3.
14 - Step3: Activation of the Report Control Block (Write) according to Table C-4.
15 These services shall be issued once the previous one has returned a positive response. If any
16 of these three MMS services fails the service Addsubscription shall be treated as failed.
17 Step 1 may not be needed in case the NamedVariableList already exists. It may be used by
18 several Report Control Blocks or Log Control Blocks.
19 Table C-2 - Mapping of AddSubscribtion service (Step 1)
AddSubscription parameters MMS service or parameter Constraint

Request DefineNamedVariableList request ser-
vice
DataSetReference variableListName
DSMemberRef[1..n] listOfVariable
Response+ DefineNamedVariableList response
service
Response-
ServiceError MMS Service Error See Table C-5
20

Request Write request service
ClientHandle VariableAccessSpecification.
(ListOfVariable)
RCBType variableAccessSpecification.
(ListOfVariable)
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 168 - 88/288/CDV

MMS Data Only appears if
RCBType specifies
Resv of the referenced /URCB as defined RCB of type URCB.
in 14.2 of IEC 61850-7-2.
ReportIdentifier [0..1] MMS Data
RptID of the referenced BRCB/URCB as
defined in 14.2 of IEC 61850-7-2.
DataSetReference [0..1] MMS Data
DatSet of the referenced BRCB/URCB as
OptionalFields [0..1] MMS Data
OptFlds of the referenced BRCB/URCB as
BufferTime [0..1] MMS Data
BufTm of the referenced BRCB/URCB as
TriggerOptions [0..1] MMS Data
TrgOp of the referenced BRCB/URCB as
IntegrityPeriod [0..1] MMS Data
IntgPd of the referenced BRCB/URCB as
Response+ Write response services
Success on all the elements
Response- Write response services
ServiceError Failure on any of the elements See Table C-5
1
2 NOTE 1 The Resv element will be included due to some servers need a previous reservation of the Unbuffered
3 ReportControlBlock before giving access to their attributes.

(ListOfVariable)
(ListOfVariable)
ReportEnable [0..1] MMS Data
RptEna of the referenced BRCB/URCB as
Success
ServiceError Failure See Table C-5
6 Table C-5 describes the possible negative circumstances and the error code that shall be
7 provided to the application layer.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 169 - 88/288/CDV
1 Table C-5 - AddSubscription Negative response
IEM service error MMS service error Explanation

Error class Error code
instance-in-use definition object-exists The dataset already exists.
parameter-value- definition Invalid-address The DSMemberRefs are not correct.
inconsistent
parameter-value- resource memory- The number of DSMemberRefs is
inappropriate unavailable higher than the maximun allowed by
the device
MMS DataAccessError
access-violation object-access-denied The client has not rights to use the
RCB.
parameter-value- object-non-existing The RCB specified by the client
inappropriate does not exist.
instance-in-use temporarily-unavailable The RCB is already under control of
other client.
parameter-value- object-value-invalid Any of the select attributes is not
inconsistent supported by the RCB.
3 C.5.3 RemoveSubscription
4 This service shall map in the following sequence of MMS services:
5 - Step 1: Deactivation of the Report Control Block (Write) Table C-6.
6 - Step 2: Deleting of the associated DataSet (DeleteNamedVariableList) Table C-7.
7 The DeleteNamedVariableList service shall only be issued if the first one succeeded. The
8 NamedVariableList need not be deleted in any case. It may be used by another Report Con-
9 trol Block or by a Log Control Block.
st
10 Table C-6 - Mapping of RemoveSubscribtion service. 1 MMS service

(ListOfVariable)
(ListOfVariable)
ReportEnable [0..1] MMS Data
RptEna of the referenced BRCB/URCB as
MMS Data Only appears if
RCBType specifies
Resv of the referenced /URCB as defined RCB of type URCB.
in 14.2 of IEC 61850-7-2.
Success
ServiceError Failure See
11
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 170 - 88/288/CDV
nd
1 Table C-7 - Mapping of RemoveSubscribtion service. 2 MMS service

Request DeleteNamedVariableList request service
ClientHandle ListOfVariableListName
Response+ DeleteNamedVariableList response service
numberDeleted
Response-
ServiceError MMS ServiceError See Table C-8
3 Table C-8 describes the possible negative circumstances and the error code that shall be
4 provided to the application layer.
5 Table C-8 - RemoveSubscription Negative response
IEM service error MMS service error Explanation

Error class Error code
instance-in-use definition object-undefined The dataset does no exists.
access-violation access object-access- The dataset cannot be deleted due
denied to access rights or being preconfig-
ured.
parameter-value- service object-state- The dataset is being used by any
inappropriate conflict control block so it cannot be deleted
MMS DataAccessError
access-violation object-access-denied The client has not rights to use the
RCB or perform the operation re-
quested
parameter-value- object-non-existing The RCB specified by the client
inappropriate does not exist.
instance-in-use temporarily-unavailable The RCB is already under control of
other client.
7 C.5.4 Extended Logging services
8 C.5.4.1 General
9 The logging services specified in clause 9.9 of the part IEC 61400-25-3 describe the use of a
10 parameter to filter the references of the log entries that shall be retrieved when a client que-
11 ries the server for log entries. This parameter is not specified in the mapping to MMS de-
12 scribed in the clause 17.3.4 of IEC 61850-8-1.
13 Only the requests are extended, the responses include the same fields. In case the filter is
14 used the only difference (according to the format of the response) is the number of log entries
15 returned.
16 C.5.4.1.1 QueryLogByTime mapping
17 The QueryLogByTime service mapping shall be as defined in Table C-9.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 171 - 88/288/CDV
1 Table C-9 - QueryLogByTime mapping
IEM QueryLogByTime request MMS ReadJournal-Request

Parameter Type Parameter MMS definition
LogReference ObjectReference journalName ObjectName
RangeStartTime EntryTime startingTime TimeOfDay
RangeStopTime EntryTime endidngTime TimeOfDay
DataFilter [1..n] ObjectReferences listOfVariables Sequence of VisibleStrings
3 C.5.4.1.2 QueryLogAfter mapping
4 The QueryLogAfter service mapping shall be as defined in Table C-10.
5 Table C-10 - QueryLogAfter mapping
IEM QueryLogAfter request MMS ReadJournal-Request

Parameter Type Parameter MMS definition
LogReference ObjectReference journalName ObjectName
EntryToStartAfter EntryTime timeSpecfication TimeOfDay
Entry EntryID entrySpecification OCTET STRING
DataFilter [1..n] ObjectReferences listOfVariables Sequence of VisibleStrings
7 C.6 Protocol stack details
8 C.6.1.1 General
9 The wind power plant information exchange model for client and server communication de-
10 fined in 61400-25-2 shall use the protocol stack as defined in C.6.2 and C.6.3.
11 C.6.2 A-Profile
12 Services and protocols of the A-Profile client/server shall be as shown in Table C-11.
13 Table C-11 – Service and protocols for client/server communication A-Profile
OSI model layer Specification m/o

Name Service specification Protocol specification
Application Manufacturing Mes- ISO 9506-1:2003 ISO 9506-2:2003 m
sage Specification
Association Control ISO/IEC 8649:1996 ISO/IEC 8650:1996 m
Service Element
Presentation Connection Oriented ISO/IEC 8822:1994 ISO/IEC 8823-1:1994 m
Presentation
Abstract Syntax ISO/IEC 8824-1:1999 ISO/IEC 8825-1 m
Session Connection Oriented ISO/IEC 8326:1996 ISO/IEC 8327-1:1997 m
Session
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 172 - 88/288/CDV
1
2 Implementation agreements
3 This A-Profile shall conform to the agreements specified in ISO/ISP 14226-1, ISO/ISP 14226-2,
4 ISO/ISP 14226-3, ISO/IEC ISP 11188-1 and ISO/IEC ISP 11188-3.
5 C.6.3 TCP/IP T-Profile
6 Services and protocols of the TCP/IP T-Profile shall be as shown in Table C-12.
7 Specifications for the data link layer and the physical layer are implementation specific and beyond the
8 scope of the IEC 61400-25 series.
9 Table C-12 – Service and protocols for client/server TCP/IP T-Profile
OSI Model Specification m/o

Layer
Name Service specifica- Protocol specifica-
tion tion
Transport ISO Transport on top of TCP RFC 1006 m
Internet Control Message Protocol RFC 792 m
(ICMP)
Transmission Control Protocol (TCP) RFC 793 m
Network Internet Protocol RFC 791 m
An Ethernet Address Resolution RFC 826 m
Protocol (ARP)
DataLink Implementation specific and beyond the scope of the IEC 61400-25 series. -
Physical Implementation specific and beyond the scope of the IEC 61400-25 series. -
10
11 Implementation agreements
12 TCP_KEEPALIVE
13 The TCP_KEEPALIVE function according to RFC 793 shall be implemented. The value of the
14 TCP KEEPALIVE shall be configurable. The range of allowed values shall be specified in the
15 PIXIT declaration of the implementation. The value of the TCP shall be specified in seconds.
16 NOTE It is recommended that the minimum-maximum value of the allowable range should be no greater than
17 20 s. It is also recommended that the TCP_KEEPALIVE be configurable to a minimum of 1 s. This results in a rec-
18 ommended range of 1 to 20.
19 Transport selector
20 The Transport Selector size shall be limited to a maximum of 4 octets.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 173 - 88/288/CDV
1 Annex D
2 (normative)
3
5 Mapping to IEC 60870-5-104
6 D.1 General
7 D.1.1 Introduction
8 This Annex describes the definition and mapping of the IEC 61400-25 Information Model (IM)
9 classes & Information Exchange Model (IEM) services to IEC 60870-5-104.
11 Clause D.1 provides a General introduction of the mapping to IEC 60870-5-104.
12 Clause D.2 provides the list of Normative references for mapping to IEC 60870-5-104.
13 Clause D.3 provides a list of Abbreviated terms used in Annex D.
14 Clause D.4 provides mapping of the Information Model to IEC 60870-5-104.
15 Clause D.5 provides mapping of the Information Exchange Model to IEC 60870-5-104.
16 Clause D.6 provides the Protocol stack details for IEC 60870-5-104.
17 D.1.2 Scope
18 The scope of the mapping to IEC 60870-5-104 is the real-time exchange of process informa-
19 tion required for operational purposes.
20 The IEC 60870-5-104 is based on a client – server association. The amount of real-time in-
21 formation provided by the server can vary dependent on the operational needs.
22 Actors to use this mapping could be regional and nationwide control centres that receive real-
23 time information in order to monitor and issue control to the process. The IEC 60870-5-104
24 protocol can be configured to have a deterministic behavior. Other operational needs could
25 also therefore be meet.
26 D.1.3 The mapping architecture
29 2. Mapping of the data (part of the information model)
31 The specified mapping is based on using the Common Address of ASDU (CASDU) and the In-
32 formation Object Address (IOA) to accommodate the model using LD and LN and transfer of
33 real-time information (data) using standardized ASDUs. The same is applicable for the ser-
34 vices and the Basic Application functions in IEC 60870-5-104.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 174 - 88/288/CDV
1 The wind power plant IM defined in 61400-25-2 shall be mapped to a hierarchical structure.
2 The conceptual mapping is depicted in Figure D-1. The wind power plant information model of
3 the IEC 61400-25 series is intended to be preserved when mapped to IEC 60870-5-104 ser-
4 vices. This especially means that:
5 - the parts of the hierarchical wind power plant information model of IEC 61400-25-2 which
6 are needed by the client must be defined in a Signal Mapping List (SML) according to
7 Clause D.7
8 - the server and the client implement the specific hierarchical wind power plant information
9 model of IEC 61400-25 defined in the SML by configuration
10 - the client accesses the hierarchical wind power plant information model of IEC 61400-25-2
11 through the services provided by IEC 60870-5-104 to exchange real-time data.
WPP information model of

Master/ Turbine5
Information model (LD „Turbine5“ and its LNs
Client WGEN
WTUR
TurSt
W
mag
Object references and real-time values of: q
Turbine5/WTUR.W.mag t
Turbine5/WTUR.W.q units
Turbine5/WTUR.W.t db
LD/LN maps CASDU/IOA d
CDC (mag, t, q) maps to „ASDU <36>“
according to SCSM as
described in Annex D
104 interface 104 interface

Client IEC 60870-5-104 protocol Server
Commands Status Update

Spontaneous transfer
Response Acknowledge
12
13 Figure D-1 – Mapping architecture (conceptual)
15 shall be mapped to the services listed in table below.
16 Table D-1 Services Mapping overview of IEC 61400-25 IM and IEM
IEC 61400-25-2 IM Class IEC 61400-25-3 Included in Maps to

M/O
IEC 61400-25-3 IEM Class IEM Services the mapping IEC 60870-5 Services
SERVER Y Server
(Controlled station)
GetServerDirectory O The SML describes the
data to be exchanged
ASSOCIATION Connection
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 175 - 88/288/CDV

M/O
Associate M Y Establish
Abort O N
Release O Y Close
LOGICAL-DEVICE Y CASDU
GetLogicalDeviceDirec- O Y The SML describes the

tory data to be exchanged
LOGICAL-NODE Y IOA
GetLogicalNodeDirec- O Y The SML describes the

tory data to be exchanged
DATA Y ASDU
GetDataValues M Y a
<100> (C_IC_NA_)
SetDataValues M Y <111> (P_ME_NB_1)
<112> (P_ME_NC_1)
<113> (P_AC_NA_1)
GetDataDirectory O Y The SML describes the
GetDataDefinition O Y The SML describes the
DATA-SET N
CreateDataSet O N
DeleteDataSet O N
REPORTING
AddSubscription O N
RemoveSubscription O N
Report O Y ASDU’s with COT <3>
= spontaneous
BRCB
GetBRCBValues O N
SetBRCBValues O N
URCB
GetURCBValues O N
SetURCBValues O N
LOG N
GetLogStatusValues O
QueryLogByTime O
QueryLogAfter O
LCB N
GetLCBValues O
SetLCBValues O
CONTROL Y Control
Select O Y ASDU TI <58, 59, 63>
Select (S/E=0)
SelectWithValue O Y ASDU <62, 63>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 176 - 88/288/CDV

M/O
Cancel O Y ASDU TI <58, 59, 62,
63> COT <8> deactiva-
tion
Operate M Y Execute (S/E=1)
CommandTermination O Y ASDU TI <58, 59, 62,
63> COT <10> ActTerm
TimeActivatedOperate O N
a General Interrogation <100> with broadcast CAA= FFFF (all Data) or CAA=LD gives the LD data.
2 D.2 Normative references for IEC 60870-5-104
3 IEC 60870-5-101 Ed. 2:2003 (IS), Telecontrol equipment and systems - Part 5-101: Transmis-
4 sion protocols – Companion standard for basic telecontrol tasks
5 IEC 60870-5-104 Ed2:2006 (57/812/FDIS), Telecontrol equipment and systems – Part 5-104:
6 Transmission protocols – Network access for IEC 60870-5-101 using standard transport pro-
7 files
9 D.3 Abbreviated terms
ACSI Abstract Communication Service Interface (defined e.g. in 61850-7-2)

ASDU Application Service Data Unit
CASDU Common Address of ASDU
DAComp Data attribute component
GI General Interrogation
IOA Information Object Address
LD Logical Device
LN Logical Node
LOG Log
LSByte Least significant byte
MSByte Most significant byte
PI Process Image
QOI Qualifier of interrogation
SCSM Specific Communication Service Mapping (defined e.g. in 61850-8-1)
SML Signal MappingList
TI Type Identification
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 177 - 88/288/CDV

WSDL Web Services Description Language
WT Wind Turbine
2 D.4 Mapping of IEC 61400-25 Information Model to IEC 60870-5-104
3 D.4.1 Introduction
4 Mapping of the the hierarchical WPP information model of IEC 61400-25-2 to the IEC 60870-
5 5-104 protocol is based on configuration as viewed in Fig D-1. The data, also defined as the
6 Process Image (PI), must be defined in an Signal Mapping List as described in Clause D.7.
7 Table D-1 defines vitale information defined in the IM and how this is mapped into the IEC
8 60870-5-104 protocol.
9 The IM data of IEC 61400-25-2 are unique and defined by its orgin in the hierarchical model
10 of IEC 61400-25-2. Mapping to IEC 60870-5-104 will maintain a unique numbering schema for
11 the single data. The definition is achieved by assigning the LD to a unique number defining
12 the CASDU. The LNs are assigned to a serie of numbers of the IOA address.
13 A decimal approach is used to define the LDs and LNs. The two bytes used by the CASDU
14 makes it possible to address 65345 different LDs, each hosting 16.777.215 data in the LNs
15 by using the 3 bytes defining the IOA. The maximum number of data possible to adress is
16 1.099.478.007.810 . Table D-2 gives an overview of two possible addressing schemas when
17 mapping the IM of 61400-25 LDs and LNs to IEC 60870-5-104. It is recomented to use an
18 Data Engineering tool in order to manage the use of CASDU and IOA numbers in order to ob-
19 tain a unic numbering schema.
20 The CDCs are mapped to the ASDUs of IEC 60870-5-104. For each single data there will be a
21 unique combination of the address (CASDU and IOA) and an ASDU. D.4.4.1 describes the
22 standard mapping of the CDCs of 61400-25-2 to IEC 60870-5-104.
23 Annex D is specialized for the mapping to IEC 60870-5-104. The protocol stack described in
24 D.6 is therefore optimized (crossed out) for the mapping of the IEC 61400-25 series to IEC
25 60870-5-104. Spontaneous transfer of changes (deadband and change of status) will after au-
26 thorization of client peformed by the server maintain correct status of the Process Image (PI).
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 178 - 88/288/CDV
2 Table D-2 – Overview of LD and LN mapping
61400-25 IEC 60870-5-101/104
IOA IOA
LD LN CASDU Comment
from to
WPP X LN according to the operational need
WTG1 X+1 LN according to the operational need
WTGn X+n LN according to the operational need
WALM 10.000 19.999 Alternative A,

WMET 20.000 29.999
WAPC 30.000 39.999 This alternative is using a predefined
WRPC 40.000 49.999 numering schema forassigning the
LD and LN numbers.
WTUR 100.000 109.999
WROT 110.000 119.999 The LD is assigned with a unic-
WTRM 120.000 129.999 CASDU number within a system.
WGEN 130.000 139.999 The LN class uses a range of IOA
WCNV 140.000 149.999 addresses. The range can be ad-
WTRF 150.000 159.999 justet to the number of data hosted by
X+1
WNAC 160.000 169.999 the LN. If the number of data is low a
WYAW 170.000 179.999 number of 1000 adresses for the LN
WTOW 180.000 189.999 can be used.
WALM 190.000 199.999
WSLG 200.000 209.999 Unic addresses for the data is ob-
WALG 210.000 219.999 tained by a specific CASDU number
WREP 220.000 229.999 for the LD and the IOA adress
It is recommended to to have a Data
Engineering tool that manages the
use of CASDU and IOA numbers.
WALM Alternativ B:
WMET
WAPC For this alternative all LD within a
WRPC specific area like a wind park have
the same CASDU number (X).
WTUR
WROT The definition of the LN class the
WTRM IOA numbers freely defined by the
WGEN vendor or adapt to the numbering
WCNV schema used by the ulitily.
X
WTRF Unic addresses for the data is ob-
WNAC tained by a one specific CASDU and
WYAW unic IOA for the LN data.
WTOW
WALM It is recommended to to have a Data
WSLG Engineering tool that manages the
WALG use of CASDU and IOA numbers.
WREP
4 D.4.2 Logical Device IM class mapping
5 The logical device class shall be mapped to one CASDU address(es) according to Table D-3
6 Table D-3 – Logical device mapping
IEC 61400-25-2 IM class Maps to

Logical Device, e.g. WPP or
CASDU
WTs
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 179 - 88/288/CDV

Logical Device – LD One number is assigned for each LD.
1
2 Note; The CASDU number must be defined by the operator (owner) according to the numbering schema used for
3 IEC 60870-5-104 related links.
4 D.4.3 Logical Node IM class mapping
5 Each logical node class shall be mapped to a defined range of numbers as defined in
6 Table D-2
7 Table D-4– Logical node mapping

Logical Node IOA address
A serie of IOA numbers shall be assigned to
Logical Node – LN
each LN class.
8
9 Note; The IOA can must be defined by the operator (owner) according to the numbering schema used for IEC
10 60870-5-104 related links.
11 D.4.4 Mapping of the Common Data Classes (CDC)
12 The mapping of the Common Data Classes has been divided into the following sections.
13 • Mapping of the Common Data Classes defined in the Information Model IEC 61400-
14 25-2.
15 • Mapping of the basic Common Data Classes inherited from IEC 61850-7-3.
16 • Mapping of the complex Common Data Classes inherited from IEC 61850-7-3.
17 D.4.4.1 Mapping of the Common Data Classes defined in the Information Model IEC
18 61400-25-2.
19 The mapping of the common data classes defined in the information model is based on the
20 simple CDCs used.
21 D.4.4.1.1 CDC Status Value, STV class mapping
22 The mandatory Data of the common data class STV is depicted in Table D-5
23 Table D-5 – CDC: Status Value, STV class
STV class
Attribute Name Attribute Type FC TrgOp Explanation and Value / M/O
Range
DataName Inherited from Data Class (see IEC 61850-7-2)
Data
Status Information
actSt INS Actual status M
24 The data [actSt] is an INS. It shall be mapped as defined in D.4.4.2.3.
25 D.4.4.1.2 CDC Setpoint Value, SPV class mapping
26 The mandatory Data of the common data class SPV is depicted in Table D-6.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 180 - 88/288/CDV
2 Table D-6 – CDC: Setpoint Value, SPV class
SPV class
Range
Data
Set point information
actVal APC Demand value of set point or pa- M
rameter.
3 The data [actVal] is an APC. It shall be mapped as defined in D.4.4.2.8.
4 D.4.4.1.3 CDC Alarm, ALM class mapping
5 The mandatory Data of the common data class ALM is depicted in Table D-7.
6 Table D-7 - CDC: Alarm, ALM class
ALM class
Attribute Name Attribute Type FC TrgOp Explanation and Value / Range M/O
Data
Status information
actSt INS Alarm status value M
7 The data [actSt] is an INS. It shall be mapped as defined in D.4.4.2.3.
8 D.4.4.1.4 CDC Command, CMD class mapping
9 The mandatory Data of the common data class CMD is depicted in Table D-8.
10 Table D-8 – CDC: Command CMD class
CMD class
Attribute Attribute Type FC TrgOp Value/Value Range M/O/C
Name
Data
Control and status
actSt INC Actual controllable status M
11 The data [actSt] is an INC. It shall be mapped as defined in D.4.4.2.7.
12 D.4.4.1.5 CDC Event Counting, CTE class mapping
13 The mandatory Data of the common data class CTE is depicted in Table D-9.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 181 - 88/288/CDV
2 Table D-9 – CDC: Event Counting, CTE class
CTE class
DataAttribute
Status Information
ActCtVal INS Actual event counts M
Status Information
ManRs SPC Manual forced reset. M
3 The data [actCtVal] is an INS. It shall be mapped as defined in D.4.4.2.3. The data [manRs]
4 is a SPC. It shall be mapped as defined in D.4.4.2.5.
5 The mapping of the CTE shall use two consecutive IOAs.
6 D.4.4.1.6 CDC State Timing, TMS class mapping
7 The mandatory Data of the common data class TMS is depicted in Table D-10.
8 Table D-10 – CDC: State Timing, TMS class
TMS class
Data
Status Information
ManRs SPC Manual forced reset M
ActTmVal INS Actual time duration of state M
OldTmVal INS Previous time duration of state M
9
10 The Data [manRs ] shall be mapped as the CDC SPC as specified in D.4.4.2.5
11 The Data [actTmVal] represent the Actual time duration of state. TimeStamp [t] shall repre-
12 sent the time when the [actTmVal] reached the accumulated value [stVal]. The DataAttributes
13 [stVal + t + q] shall be mapped as the CDC INS specified in D.4.4.2.3
14 The Data [oldTmVal] represent the Previous time duration of state . TimeStamp [t] shall rep-
15 resent the time when the current [actTmVal] last was reset. The DataAttributes [stVal + t + q]
16 shall be mapped as the INS specified in D.4.4.2.3.
17 D.4.4.1.7 CDC Alarm Set Status, ASS class mapping
18 This mapping does not use this common data class. The status of the alarms shall be re-
19 trieved accessing to the different alarms that build the information model.
20 D.4.4.2 Mapping of the basic Common Data Classes inherited from IEC 61850-7-3
21 Each Common Data Class consists data and related attributes. Table D-11 defines relation
22 between the CDC and the related ASDUs to be used for mapping to IEC 60870-5-104. Map-
23 ping of data and the related attributes are defined in detail in clause D.4.4.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 182 - 88/288/CDV
2 Table D-11 – Mapping structure basic CDC
CDC Inhered from 61850 7-3 IEC 60870-5-104 AS-

(Attribute data types) DU Type Identifier (TI)
SPS - Single Point Status 30 monitor as event

1 monitor as part of GI
DPS – Double Point Status 31 monitor as event

35 / 37 monitor as event
INS – Integer Status
BCR - Binary Counter Reading 37 monitor as event
SPC - Controlable Single Point 58 control

30 monitor as event
DPC - Controlable Double Point 59 control
31 monitor as event
62 control
INC - Controllable Integer Status
35 monitor as SVA
APC - Controllable Analog process 63 control

value 36 monitor as MV
60 as command
BSC - Binary controlled step infro-
32 monitor as event
mation
36 monitor as event
MV - Measured Value
Note: DPS, DPC, BSC are not used inside IEC-61400-25-2, but are de-
fined so they can be used in extensions of the model.
4 Other common data classes as LPL or WDPL shall be defined inside the Signal Mapping List
5 as static information. The attributes of these classes are not interchanged by communication
6 services.
7 D.4.4.2.1 CDC Single Point Status, SPS class mapping
8 The mandatory DataAttributes of the common data class SPS depicted in Table D-12 shall be
9 mapped as shown in Table D-13.
10 Table D-12 - CDC: Single Point Status, SPS class
SPS class
Name
DataAttribute
Status
stVal BOOLEAN ST dchg TRUE | FALSE M
q Quality ST qchg M
t TimeStamp ST M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 183 - 88/288/CDV
2 The data attributes [stVal + q + t] shall map to ASDU TI<30> as specified in Table D-13.
3 Table D-13 - CDC: Single Point Status, SPS class mapping
IEC 61400-25-2 CDC class IEC 60870-5-104 mapping

SPS TI <30>
Attribute Attribute Type IEC 60870-5-104 Information Object Mapping
Name
stVal BOOLEAN SIQ SPI:<0> OFF = FALSE
<1> ON = TRUE
q Quality valididy -> IV/NT
good | invalid -> valid | invalid
questionable -> not topical
source -> SB
substituted -> substituted
operatorBlocked -> BL
blocked -> blocked
t TimeStamp CP56Time2a Seven octet binary time, CP56Time2a – Time of occur-
rence for Trigging of dchg or qchg
5 D.4.4.2.2 CDC Double Point Status, DPS class mapping
6 The mandatory DataAttributes of the common data class DPS depicted in Table-14 shall be
8 Table D-14 – CDC: Double point status, DPS class
DPS class
Name
DataAttribute
Status
stVal CODED ENUM ST dchg intermediate-state | off | on | bad-state M
q Quality ST qchg M
t TimeStamp ST M
9 The data attributes [stVal + t + q] shall map to ASDU TI<31> as specified in .
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 184 - 88/288/CDV
1 Table D-15 - CDC: Double Point Status, DPS class mapping

DPS TI <31>
Name
stVal CODED ENUM DIQ DPI
<0> intermediate state = intermediate-state
<1> determined state OFF = off
<2> determined state ON = on
<3> indeterminate = bad-state
q Quality valididy -> IV/NT
source -> SB
blocked -> blocked
t TimeStamp Seven octet binary time, CP56Time2a – Time of occur-
rence for object
3 D.4.4.2.3 CDC Integer Status, INS class mapping
4 The common data class INS shall map to the ASDU TI <35>.
5 Only in the cases that an INS is a component of a CTE or TMS common data classes, it shall
6 map to the ASDU TI <37>. The Table D-16 define the mapping of the INS.

STV TI <35>
ALM TI <35>
CTE TI <37>
TMS TI <37>
8 The mandatory DataAttributes of the common data class INS depicted in Table D-16 shall be
9 mapped either to ASDU TI <35> or ASDU TI<37> as shown in Table D-17 and Table D-18.
10 Table D-16 CDC: Integer Status, INS class
INS class
DataAttribute
Status
stVal INT32 ST dchg M
q Quality ST qchg M
t TimeStamp ST M
11
12 The signal [stVal+ t + q] shall map to the ASDU TI <35> as specified in Table D-17.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 185 - 88/288/CDV
1 Note: The CDC describes Attribute type INT32. The Scaled Value (SVA) ASDU 35 uses 16 bits which then defines
2 the resolution for the CDC objects mapped to ASDU <35>.
3 Table D-17 CDC: Interger Status, INS class mapping to ASDU TI <35>

INS TI <35>
Name
stVal INT32 SVA = Scaled SVA: = I16[1..16]<–2^15..+2^15–1>
value
q Quality QDS= Quality valididy -> IV/NT
descriptor good | invalid -> valid | invalid
source -> SB
blocked -> blocked
OV: <0> = no overflow
<1>= overflow
t TimeStamp Seven octet binary time, CP56Time2a
5 The data attributes [stVal + q + t] shall map to ASDU TI<37> as specified in Table D-18.
6 Table D-18 CDC: Interger Status, INS class mapping to ASDU TI <37>

INS TI <37>
Name
stVal BCR – Binary Counter reading := I32[1..32]<–2’31..+2’31–1>
Counter Read-
ing SQ = sequence number
q Quality
CY = carry
<0> := no counter overflow occurred in the corre
sponding integration period
<1> := counter overflow occurred in the corresponding
integration period
CA = counter was adjusted
<0> := Counter was not adjusted since last reading
<1> := Counter was adjusted since last reading
IV := invalid
<0> = Counter reading is valid
<1> = Counter reading is invalid

rence of counter reading or quality change (qchg)
7
8 Note: CA, CY and IV are only modified when the value is determined. This may be in response to a counter interro-
9 gation command or in response to an automatic internal function that performs the counter freeze or freeze and re-
10 set command.
11
12 D.4.4.2.4 CDC Binary Conter Reading, BCR class mapping
13 The DataAttributes of the common data class BCR depicted in Table D-19 shall be mapped as
14 shown in Table D-20.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 186 - 88/288/CDV
2 Table D-19 – CDC: Binary Conter Reading, BCR class
BCR class
DataAttribute
Status Information
actVal INT128 ST dchg M
Q Quality ST qchg M
T TimeStamp ST M
Configuration, describtion and extentions.
pulsQty FLOAT32 CF dchg M
3 Note: DataAttribute [pulsQty] will be part of the local functionally providet by the IED. The [pulsQty] factor will be
4 taken into account for [actVal] and is therefore not part of the mapping.
5 The data attributes [actVal + t + q] shall map to ASDU TI <37> as specified in Table D-20.
6 Table D-20 – CDC: Binary Conter Reading, BCR class mapping

BCR TI <37>
Name
actVal BCR – Binary Counter Reading
q Quality BCR
Counter reading := I32[1..32]<–2’31..+2’31–1>
SQ = sequence number
CY = carry
<0> := no counter overflow occurred in the corre
sponding integration period
<1> := counter overflow occurred in the corresponding
integration period
CA = counter was adjusted
<0> := Counter was not adjusted since last reading
<1> := Counter was adjusted since last reading
IV := invalid
<0> = Counter reading is valid
<1> = Counter reading is invalid

8 D.4.4.2.5 CDC Controllable single point , SPC class mapping
9 The DataAttributes of the common data class SPC depicted in Table D-21 shall be mapped as
10 shown in Table D-22.
11 Table D-21 – CDC: Controllable single point, SPC class
SPC class
Name
DataAttribute
Control and status
ctlVal BOOLEAN CO off (FALSE) | on (TRUE) AC_CO_M
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 187 - 88/288/CDV
operTm TimeStamp CO AC_CO_O

stVal BOOLEAN ST dchg FALSE or TRUE AC_ST
q Quality ST qchg AC_ST
t TimeStamp ST AC_ST
Configuration, describtion and extention
ctlModel ctlModels CF M
1 The data attributes [ctlVal] shall map to CDC SPC, ASDU TI<58> as specified in D.4.4.2.5.
2 The data attributes [stVal + q + t] hold the actual status value of the object and is mapped as
3 the SPS described in D.4.4.2.1.
4 Note: The attribute [ctlModel] with FC [CF] shall be configured according to the definition done in the Signal Map-
5 ping List (SML).
6 Note 2: Other optional configuration attributes as [sboTimeout] or [sboClass] may also be described in the Signal
7 Mapping List (SML).
8 Table D-22 – CDC: Controllable single point, SPC mapping

SPC TI <58 >
Name
ctlVal BOOLEAN SCO = Single SCS (Single command state) OFF / ON -> off/on
command
QU <0> no additional definition other QU values are not
used; pulse duration etc. are defined in the control model
defined in IEC 61850-7-x.
S/E <0> execute -> Operate service

<1> select -> SelectWithValue service
Seven octet binary time, CP56Time2a – Time of occur-
rence for sending of command by the client.
It holds the information of the “T” parameter of the con-
trol services.
10 D.4.4.2.6 CDC Controllable double point, DPC class mapping
11 The mandatory DataAttributes of the common data class DPC is depicted in Table D-23 shall
12 be mapped as shown in Table D-24.
13 Table D-23 – CDC: Controllable double point, DPC class
DPC class
Name
DataAttribute
Control and status
ctlVal BOOLEAN CO off (FALSE) | on (TRUE) M
operTm TimeStamp CO M
stVal CODED ENUM ST dchg intermediate-state | off | on | bad-state M
q Quality ST qchg M
t TimeStamp ST M
ctlModel CtlModels CF M
14 The data attributes [ctlVal] shall map to IEC 60870-5-104 ASDU TI<59> double point com-
15 mand with time tag CP56Time2a as specified in Table D-24.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 188 - 88/288/CDV
1 The data attributes [stVal + q + t] hold the actual status value of the object and they are
2 mapped as it is described in the mapping of the DPS in D.4.4.2.2.
4 ping List (SML).
8 Table D-24– CDC: Controllable double point (DPC) mapping

DPC TI <59>
Name
ctlVal BOOLEAN DCO =Double DCS (Double command state) OFF / ON -> off/on
command <0> := not permitted
<1> := OFF
<2> := ON
<3> := not permitted
QU <0> no additional definition other QU values are not

used; pulse duration etc. are defined in the control model
defined in IEC 61850-7-x.

rence for each object
trol services.
9
10 D.4.4.2.7 CDC Controllable Integer Status, INC class mapping
11 The mandatory DataAttributes of the common data class INC depicted in Table D-25 shall be
12 mapped as shown in Table D–26.
13 Table D-25 CDC: Controllable Interger Status, INC class
INC class
Range
DataAttribute
Control and status
ctlVal INT32 CO M
OperTm TimeStamp CO O
stVal INT32 ST dchg M
q Quality ST qchg M
t TimeStamp ST M
Configuration, description and extensions.
ctlModel CtlModel CF M
sboTimeout INT32 CF O
sboClass sboClasses CF O
14
15 The Attribute [ctlVal] shall map to ASDU Type <62> as specified in Table D-26.
16 The signal [stVal+ t + q] shall map to the ASDU TI <35> as defined in Table D-26.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 189 - 88/288/CDV
2 ping List (SML).
5 Table D-26 – CDC: Controllable Interger Status , INC class mapping

INC TI <62>
Name
ctlVal INT32 SVA = Scaled SVA: = I16[1..16]<–2^15..+2^15–1>
Value
QOS QL <0>

trol services.
7 D.4.4.2.8 CDC Controllable Analog process value, APC class mapping
8 The mandatory DataAttributes of the common data class APC are depicted in Table D-27
9 Table D-27 – CDC: Controllable Analog set point, APC class
APC class
Name
DataAttribute
Set points and measured attributes
ctlVal AnalogueValue CO M
mxVal AnalogueValue MX dchg M
q Quality MX qchg M
t TimeStamp MX M
ctlModel ctlModels CF M
10
11 The data attributes [ctlVal] shall map to ASDU TI <63> as specified in Table D-28.
12 The data attributes [mxVal + q + t] is the actual analogue value of the object and is mapped to
13 ASDU TI <36> as described in Table.
15 ping List (SML).
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 190 - 88/288/CDV
1
2 Table D-28 – CDC: Controllable Analog set point, APC class mapping

APC TI <63>
Name
ctlVal IEEE STD 754 IEEE STD 754 = short floating point number
QOS QL <0>


trol services.
4 D.4.4.2.9 CDC Binary controlled step position information, BSC class mapping
5 The mandatory DataAttributes of the common data class BSC are depicted in Table D-29.
6 Table D-29 – CDC: Binary controlled step position, BSC class
BSC class
Name
DataAttribute
Set points and measured attributes
ctlVal CODED ENUM CO M
valWTr ValWithTrans MX dchg M
q Quality MX qchg M
t TimeStamp MX M
persistent BOOLEAN CF M
ctlModel CtlModels CF M
7 The data attributes [ctlVal] shall map to ASDU TI <60> as specified in Table D-30.
8 The data attributes [valWTr + t + q] is the actual position of the object and is mapped to ASDU
9 TI <32> as described in Table D-31.
11 ping List (SML).
12 Note 2: This mapping restricts the value of persistent to FALSE. It shall be defined with this value in the Signal
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 191 - 88/288/CDV
2 Table D-30 – CDC: Binary controlled step position, BSC class mapping to ASDU TI <60>

BSC TI <60>
Name
ctlVal RCO = Regulat- RCS= Regulating step command state
ing step com-
mand <0> : not permitted
<1> : next step LOWER
<2> : next step HIGHER
<3> : not permitted
QU <0>


trol services.
4 Table D-31 – CDC: Binary controlled step position, BSC class mapping to ASDU TI <32>

BSC TI <32>
Name
valWTr VTI = Value Value <-64..63>
with transient
state indication Trasient:
<0> = equipment is not in trasient state
<1> = equipment is in trasient state
q Quality QDS = Quality valididy -> IV/NT
descriptor good | invalid -> valid | invalid
source -> SB
blocked -> blocked
OV: <0> = no overflow
<1>= overflow
t TimeStamp CP56Time2a Seven octet binary time, CP56Time2a – Time of occur-
6 D.4.4.2.10 CDC Measured Value, MV class mapping
7 The mandatory DataAttributes of the common data class MV depicted in Table D-32 shall be
8 mapped as shown in Table D-33
9 Table D-32 - CDC: Measured Value, MV class
MV class
DataAttribute
analogue information
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 192 - 88/288/CDV
mag AnalogueValue MX dchg Deadbanded value M

q Quality MX qchg Quality M
t TimeStamp MX Time value M
1 The signal [mag + t + q] shall map to the ASDU TI <36> as specified in Table D-33.
2 Table D-33 - CDC: Measured Value, MV class mapping

MV TI <36>
Attribute Attribute Type DAComponent IEC 60870-5-104 Information Object Mapping
Name
mag AnalogueValue f FLOAT32 IEEE STD 754 = short floating point number
Q Quality QDS
valididy -> IV/NT
source -> SB
blocked -> blocked
OV: <0> = no overflow <1>= overflow
t TimeStamp Seven octet binary time, CP56Time2a
4 D.4.4.3 Mapping of the complex Common Data Classes inherited from IEC 61850-7-3
5 Table D-34 defines the relationship between the complex CDCs inherited from IEC 61850-7-3
6 and the related ASDUs to be used for mapping to IEC 60870-5-104.
7 Table D-34 – Relationship between complex CDCs and IEC 60870-5-104 ASDUs
CDC Inhered from 61850 7-3

IEC 60870-5-104 Mapping
(Attribute data types)
CMV - Complex Measured Value Mapped as a set of MV common

Value data classes. Each MV has its
one IOA.
Mapped as a set of CMV com-

WYE - Three Phase Value mon data classes. Each MV in-
side the CMV has its one IOA.
Mapped as a set of CMV com-

DEL - Three Phase Value mon data classes. Each MV in-
side the CMV has its one IOA.
9 D.4.4.3.1 CDC Complex Measured Value, CMV class mapping
10 The mandatory DataAttributes of the common data class CMV depicted in XX shall be
12 Table D-35 - CDC: Complex Measured Value, CMV class
CMV class
DataAttribute
analogue information
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 193 - 88/288/CDV
cVal Vector MX dchg Deadbanded value M

q Quality MX qchg Quality M
t TimeStamp MX Time value M
2 The signal [cVal + t + q] shall map to the ASDU TI <36>. If the definition of [cVal] only in-
3 cludes the magnitude [mag], one ASDU TI <36> is needed. In case the angle [ang] is also in-
4 cluded in the CMV, a second IOA address is needed to map the data.
5 Table D-36 - CDC: Complex Measured Value, CMV class mapping

CMV TI <36>
Attribute Attribute Type DAComponent IEC 60870-5-104 Information Object Mapping
Name
cVal AnalogueValue mag.f FLOAT32 Mapped as a measured value MV: TI <36>.
q Quality
t TimeStamp
cVal AnalogueValue ang.f FLOAT32 Mapped as a measured value MV: TI <36> with a differ-
ent IOA.
q Quality
t TimeStamp
7 D.4.4.3.2 CDC Three Phase Value (DEL)
8 The mandatory Data of the common data class DEL depicted in Table D-37 shall be mapped
9 as shown in Table D-38
10 Table D-37 - CDC: Three Phase Value (DEL) class
DEL class
Name
Data
phsAB CMV GC_1
phsBC CMV GC_1
phsCA CMV GC_1
11 Note: GC_1 means that at least one shall be present.
12 The data [phsAB, phsBC and phsCA] are CMV and they shall map as described in D.4.4.3.1.
13 Each data that build the DEL shall use consecutive IOAs.
14 Table D-38 - CDC: Three Phase Value (DEL) class mapping

DEL TI <36>
Data Name Attribute Type IEC 60870-5-104 Information Object Mapping
phsAB CMV Three to six objects of ASDU TI<36> with consecutive indices of the IOA
phsBC [n]:
phsCA IOA n : phsAB
IOA n+2 : phsBC
IOA n+4 : phsCA
15 Note: The number of IOAs depends of the use or not of tha “ang” attribute of the CMV.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 194 - 88/288/CDV
1 D.4.4.3.3 CDC Three Phase Value (WYE), class
2 The mandatory Data of the common data class WYE depicted Table D-39 shall be mapped as
3 in Table D-40.
4 Table D-39 – WYE: Three Phase Value, WYE class
WYE class
Name
Data
phsA CMV GC_1
phsB CMV GC_1
phsC CMV GC_1
neut CMV GC_1
net CMV GC_1
res CMV GC_1
5 The data [phsA, phsB, phsC, neut, net, res] are CMV and they shall map as described in XXX.
6 Each data that build the WYE shall use consecutive IOAs.
7 Table D-40 – CDC: Three Phase Value (WYE), mapping

WYE TI <36>
Data Name Attribute Type IEC 60870-5-104 Information Object Mapping
phsA AnalogueValue Six to twuelve objects of ASDU TI<36> with consecutive indices of the IOA
phsB [n]:
phsC IOA n: phsA
IOA n+2: phsB
neut
net IOA n+4: phsC
IOA n+6: neut
res
IOA n+8: net
IOA n+10: res
8 Note: The number of IOAs depends of the use or not of tha “ang” attribute of the CMV.
10 D.5 Mapping of the Information Exchange Model to IEC 60870-5-104 services
11 D.5.1 List of service models and corresponding mappings
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 195 - 88/288/CDV
2 Table D-41 – Mapping of IEC 61400-25 ACSI service into IEC 60870-5-104 services
IEC 61400-25-3 IEM Services M/O Included in IEC 60870-5-104 -

the mapping services
Associate M Y
Release M Y
Abort O Y
GetServerDirectory O Y The SML describes the
GetLogicalDeviceDirectory O Y The SML describes the
GetLogicalNodeDirectory O Y The SML describes the
GetDataValues M Y a
<100> (C_IC_NA_)
SetDataValues M Y <112> (P_ME_NC_1)
<113> (P_AC_NA_1)
GetDataDirectory O Y The SML describes the
GetDataDefinition O Y The SML describes the
CreateDataSet O N
DeleteDataSet O N
Report O N
GetBRCBValues O N
SetBRCBValues O N
GetURCBValues O N
SetURCBValues O N
AddSubscription O N
RemoveSubscription O N
GetLCBValues O N
SetLCBValues O N
GetLogStatusValues O N
QueryLogByTime O N
a
QueryLogAfter O N
Select O Y ASDU TI <58, 59, 63> Se-
lect (S/E=0)
SelectWithValue O Y ASDU <63>
Cancel O Y ASDU TI <58, 59, 63>
COT <8> deactivation
Operate M Y Execute (S/E=1)
CommandTermination O Y ASDU TI <58, 59, 63>
COT <10> ActTerm
TimeActivatedOperate O N
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 196 - 88/288/CDV
1 D.5.2 Server class mapping
2 The server class shall be mapped to a controlled station as shown in Table D-42.
3 NOTE Details of the initialisation etc. of the server are defined in IEC 60870-5-104.
4 Table D-42 – Server services mapping
IEC 61850-7-2 Service Maps to

Server outstation (controlled station)
GetServerDirectory The SML describes the data to be ex-
changed
6 D.5.3 Association class mapping
7 The association service shall be mapped to a controlled station as shown in Table D-43.
8 NOTE Details of the initialisation etc. of the server are defined in IEC 60870-5-104.
9 Table D-43 – Association services mapping

Association Connection
Associate Establish; IEC 60870-5-104
Station initialization
a
Abort n.a.
Release Close; IEC 60870-5-104
Station initialization
a not applicable for the mapping to IEC 60870-5-104
10
11 D.5.4 Logical Node class mapping
12 The GetAllDataValues service shall be mapped as shown in Table D-44.
13 Table D-44 – Logical Nodes services mapping
IEC 61850-7-2 Service Maps to IEC 60870-5-104

Logical Node
GetAllDataValues TI <100> General Interrogation with:
- CASDU address FFFF (broadcast)
- Qualifier of interrogation (QOI)=20
14
15 The corresponding process data response shall be one or more than one of the following
16 ASDU’s depending on the type of data with cause of transmission (COT) = 20 <interrogated
17 by station interrogation>:
Type Id ASDU Abbreviation

Process information in monitoring direction
<1> Single-point information without time tag M_SP_NA_1
<3> Double-point information without time tag M_DP_NA_1
<5> Set position information without time tag M_ST_NA_1
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 197 - 88/288/CDV

<11> Measured value, scaled value without time tag M_ME_NB_1
<13> Measured value, short floating point number without time tag M_ME_NC_1
<15> Integrated totals without time tag M_IT_NA_1
1
2 D.5.5 Data class mapping
3 The GetDataValues service shall be mapped as shown in Table D-45.
4 Table D-45 – Data services mapping

Data One or a set of IOA(‘es).
GetDataValues TI <102> Read command with:
- applicable CASDU address
- applicable IOA address
COT <5> := Request The respons will
be all data for the LD which is defined in
the SML.
5
6 The corresponding process data response shall be only one of the following ASDU’s depend-
7 ing on the type of the object address with cause of transmission (COT) = 5 <requested>

<30> Single-point information with time tag CP56Time2a M_SP_TB_1
<31> Double-point information with time tag CP56Time2a M_DP_TB_1
<32> Step position with time taf CP56Time2a M_ST_TB_1
<35> Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
<36> Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1
<37> Integrated totals with time tag CP56Time2a M_IT_TB_1
8
9 D.5.6 Report Control Block class mapping
10 The Report Control Block services shall be mapped as shown in Table D-46.
11 Table D-46 – Report Control Block services mapping

Report Control Block
Report ASDU’s with COT <3> = spontaneous
12
13 D.5.7 Control class mapping
14 The Control services shall be mapped as shown in Table D-47.
15 Table D-47 – Control services mapping

Control Controllable IOA
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 198 - 88/288/CDV

SelectWithValue TI <58, 59, 60, 62 or 63> in control di-
rection:
- Qualifier of command (QOC)=0 <no
additional definition>
- COT <6> := Activation
- S/E <1> := Select
Cancel TI <58, 59, 60, 62 or 63> in control di-
rection:
- COT <8> := Deactivation
- S/E value is irrelevant
Operate TI <58, 59, 60, 62 or 63> in control di-
rection:
- COT <6> := Activation
- S/E <0> := Execute
Command Termination TI <58, 59, 60, 62 or 63> in monitor di-
rection:
- COT <10> := Activation Termina-
tion
- S/E <0> := Execute
1
2 Only when using operate there shall be a corresponding process data response of one of the
3 following ASDU’s, depending on the type of the requested signal, with cause of transmission
4 (COT) = <3> spontaneous, <11> return information caused by a remote command or <12> re-
5 turn information caused by a local command:

<30> Single-point information with time tag CP56Time2a M_SP_TB_1
<31> Double-point information with time tag CP56Time2a M_DP_TB_1
<32> Step position with time taf CP56Time2a M_ST_TB_1
<35> Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
<36> Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1
<37> Integrated totals with time tag CP56Time2a M_IT_TB_1
7
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 199 - 88/288/CDV
1 D.6 Protocol stack selections for IEC 60870-5-104. (Protocol stack details)
2 D.6.1 General
3 The mapping of IEC 61400-25 to IEC 60870-5-101/104 focus on the maping to IEC 60870-5-
4 104. The Inter operability list, D.6.2 is optimized for IEC 60870-5-104 and items that are not
5 valid fortIEC 60870-5-104 is left out. The complete Interoperbility List is found in the IEC
6 60870-5-101/104 standards.
7 The mapping in to IEC 60870-5-104 is done for the applicable data (ASDUs) and services
8 (Basic Application Functions) according to the marked check boxes in the Interoperability
9 sheet in D.6.2. The boxes defined is a subset of the IEC 60870-5-104 standard.
10 D.6.2 IEC 60870-5-104 Interoperability
11 D.6.2.1 Introduction
12 This companion standard presents sets of parameters and alternatives from which subsets
13 must be selected to implement particular telecontrol systems. Certain parameter values, such
14 as the choice of “structured“ or “unstructured“ fields (addresses) of the INFORMATION OBJECT
15 ADDRESS of ASDUs represent mutually exclusive alternatives. This means that only one value
16 of the defined parameters is admitted per system. For the mapping of IEC 61400-25 to IEC
17 60870-5-104 unstruckted addressing is used.
18 Other parameters, such as the listed set of different process information in command and in
19 monitor direction allow the specification of the complete set or subsets, as appropriate for
20 given applications. This clause summarizes the parameters to facilitate a suitable selection
21 for a specific application. If a system is composed of equipment stemming from different
22 manufacturers it is necessary that all partners agree on the selected parameters.
23 The interoperability list is a sub set of the complete list defined as in IEC 60870-5-101 and ex-
24 tended with parameters used in this standard.
25 Note In addition, the full specification of a system may require individual selection of certain parameters for
26 certain parts of the system, such as the individual selection of scaling factors for individually addressable meas-
27 ured values.
28 The selected parameters should be marked in the white boxes as follows:
Function or ASDU is not used

X Function or ASDU is used as standardized (default)
R Function or ASDU is used in reverse mode
B Function or ASDU is used in standard and reverse mode
29
30 The possible selection (blank, X, R, or B) is specified for each specific clause or parameter.
31 For the mapping of IEC 61400-25 to IEC 60870-5-104 the selection(s) are made in this docu-
32 ment.
33 A black check box indicates that the option cannot be selected in this companion standard.
34 D.6.2.2 System or device
35 (system-specific parameter, indicate definition of a system or a device by marking one of the

36 following with ‘ X ’)
X System definition
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 200 - 88/288/CDV
Controlling station definition

Controlled station definition
2 D.6.2.3 Network configuration
3 (network-specific parameter, all configurations that are used are to be marked ‘ X ’)
Point-to-point Multipoint-
Multiple point-to-point Multipoint-star
4
5 D.6.2.4 Physical layer
6 The RFC 2200 is used for the IEC 60870-5-104.
7 D.6.2.5 Link layer
8 (network-specific parameter, all options that are used are to be marked ‘X ’.)
9 Acording to the RFC 2200.
10 D.6.2.6 Application layer

11 Transmission mode for application data
12 Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 60870-5-4, is used ex-
13 clusively in this companion standard.
14 Common address of ASDU

15 (system-specific parameter, all configurations that are used are to be marked ‘ X ’)
One octets
X Two octets
16
17 Information object address
Two octets structured

X Three octets X unstructured
19
20 Cause of transmission
X Two octets (with originator address) Originator address is set to zero if not used
22
23 Length of APDU
24 (system-specific parameter, specify the maximum length of the APDU per system)
25 The maximum length of APDU for both directions is 253. It is a fixed system parameter.
26
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 201 - 88/288/CDV
Maximum length of APDU per system
2 Selection of standard ASDUs

3 Process information in monitor direction
4 (station-specific parameter, mark each Type ID ‘ X ’ if it is only used in the standard direction,
5 ‘ R ’ if only used in the reverse direction, and ‘ B ’ if used in both directions)
ASDU <TI>:= function

X <1>:= Single-point information M_SP_NA_1
X <3>:= Double-point information M_DP_NA_1
<5>:= Step position information M_ST_NA_1
<11>:= Measured value, scaled value M_ME_NB_1
X <13>:= Measured value, short floating point value M_ME_NC_1
X <30>:= Single-point information with time tag CP56Time2a M_SP_TB_1
X <31>:= Double-point information with time tag CP56Time2a M_DP_TB_1
<32>:= Step position with time taf CP56Time2a M_ST_TB_1
X <35>:= Measured value, scaled value with time tag CP56Time2a M_ME_TE_1
X <36>:= Measured value, short floating point value with time tag CP56Time2a M_ME_TF_1
X <37>:= Integrated totals with time tag CP56Time2a M_IT_TB_1
6 In this companion standard only the use of the set <30> – <40> for ASDUs with time tag is-
7 permitted.
8 Process information in control direction

ASDU <TI>:= function

X <58>:= Single command with time tag CP56Time C_SC_TA_1
<59>:= Double command with time tag CP56Time C_DC_TA_1
<60>:= Regulating step command with time tag CP56Time 2a C_RC_TA_
X <62>:= Set point command, scaled value with time tag CP56Time 2a C_SC_TB_1
X <63>:= Set point command, short floating point value with time tag CP56Time 2a C_SE_TC_1
11
12 System information in monitor direction

13 (station-specific parameter, mark ‘ X ’ if used)
TI ASDU <TI>:= function

X 70 <70>:= End of initialization M_EI_NA_1
14
15 System information in control direction

Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 202 - 88/288/CDV
ASDU <TI> := function

X <100>:= Interrogation command C_IC_NA_1
<101>:= Counter interrogation command C_CI_NA_1
X <102>:= Read command C_RD_NA_1
<103>:= Clock synchronization command C_CS_NA_1
<105>:= Reset process command C_RP_NA_1
<107>:= Test command with time tag CP56time2a C_TS_TA_1
2 Parameter in control direction


X <112>:= Parameter of measured value, short floating point value P_ME_NC_1
X <113>:= Parameter activation P_AC_NA_1
6 File Transfer

<120>:= File ready F_FR_NA_1
<121>:= Section ready F_SR_NA_1
<122>:= Call directory, select file, call file, call section F_SC_NA_1
<123>:= Last section, last segment F_LS_NA_1
<124>:= Ack file, ack section F_AF_NA_1
<125>:= Segment F_SG_NA_1
<126>:= Directory {blank or X, only available in monitor (standard) direction} F_DR_TA_1
<127>:= QueryLog – Request archive file F_SC_NB_1
10 Type Identifier and Cause of Transmission Assignments

11 (station-specific parameters)
12 Shaded boxes are not required.

13 Black boxes are not permitted in this companion standard
14 Blank = Function or ASDU is not used.
15 Mark Type Identification/Cause of transmission combinations:
16 ‘X’ if only used in the standard direction
17 ‘R’ if only used in the reverse direction
18 ‘B’ if used in both directions
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 203 - 88/288/CDV
1
Type Identification Cause of transmission
1 2 3 4 5 6 7 8 9 1 1 1 1 2 3 4 4 4 47
0 1 2 3 0 7 4 5 6
to to
3 4
6 1
<1> M_SP_NA_1 X
<3> M_DP_NA_1 X
<13> M_ME_NC_1
<15> M_IT_NA_1
<30> M_SP_TB_1 X X X
<31> M_DP_TB_1 X X X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1
<58> C_SC_TA_1 X X X X X X X X X
<59> C_DC_TA_1 X X X X X X X X X
<60> C_RC_TA_1
<62> C_SE_TB_1 X X X X X X X X X
<63> C_SE_TC_1 X X X X X X X X X
<70> M_EI_NA_1 *)
<100> C_IC_NA_1 X X X X X X X
<102> C_RD_NA_1 X X X X X
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1
<121> F_SR_NA_1
<122> F_SC_NA_1
<123> F_LS_NA_1
<124> F_AF_NA_1
<125> F_SG_NA_1
<126> F_DR_TA_1 *)
<127> F_SC_NB_1 *)
2 *) blank or X only
3
4
Cause of transmission description
<0> := not used
<1> := periodic, cyclic - per/cyc
<2> := background scan3 - back
<3> := spontaneous - spont
<4> := initialized - init
<5> := request or requested - req
<6> := activation - act
<7> := activation confirmation - actcon
<8> := deactivation - deact
<9> := deactivation confirmation - deactcon
<10> := activation termination - actterm
<11> := return information caused by a remote command - retrem
<12> := return information caused by a local command - retloc
<13> := file transfer file
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 204 - 88/288/CDV
<14..19> := reserved for further compatible definitions
<20> := interrogated by station interrogation - inrogen

<21> := interrogated by group 1 interrogation- inro1
<22> := interrogated by group 2 interrogation - inro2
<37> := requested by general counter request - reqcogen
<38> := requested by group 1 counter request - reqco1
<42..43> := reserved for further compatible definitions
<44> := unknown TI - type identification
<45> := unknown COT - cause of transmission
<46> := unknown CAA - common address of ASDU
<47> := unknown IOA - information object address
<48..63> := for special use (private range)
2 D.6.2.7 Basic application functions

3 Station initialization
4 (station-specific parameter, mark ‘ X ’ if function is used)
Remote initialization
6 Cyclic data transmission

7 (station-specific parameter, mark ‘ X ’ if function is only used in the standard direction, ‘ R ’ if
8 only used in the reverse direction, and ‘ B ’ if used in both directions)
Cyclic data transmission
10 Read procedure
Read procedure
13
14 Spontaneous transmission
X Spontaneous transmission
17
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 205 - 88/288/CDV
1 Double transmission of information objects with cause of transmission spontane-

2 ous
3 (station-specific parameter, mark each information type ‘X’ where both a Type ID without time
4 and corresponding Type ID with time are issued in response to a single spontaneous change
5 of a monitored object)
6 This function is not used
7
8 Station interrogation
X global
group 1 group 7 group 13
group 5 group 11
group 6 group 12
11
12 D.6.2.8 Information Object Addresses assigned to each group must be shown in a

13 separate table
14 Clock synchronization
Clock synchronization
17 The clock synchronization procedure defined in IEC 60870-5-5 cannot be used in this stan-
18 dard because the link layer according to IEC 60870-5-2, which provides the exact time of
19 sending the clock command, is no longer available.
20 Command transmission
21 (object-specific parameter, mark ‘X ’ if function is only used in the standard direction, ‘ R ’ if
23 This function must be xrossed out according to the requirement in the CDC control model (ctrModel)
x Direct command transmission (de)
x Direct set point command transmission (de)
Select and execute command (sbo)
x Select and execute set point command (sbo)
x Select and execute command (sbo with enhanced security)
x Select and execute set point command (sbo with enhanced security)
C_SE ACTTERM used
No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)
Persistent output
Supervision of maximum delay in command direction of commands and set point commands
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 206 - 88/288/CDV
1
20 sec Maximum allowable delay of commands and set point commands
3 Transmission of integrated totals

4 (station- or object-specific parameter, mark ‘ X ’ if function is only used in the standard direc-
5 tion, ‘R ’ if only used in the reverse direction, and ‘ B ’ if used in both directions)
Mode A: Local freeze with spontaneous transmission

Mode B: Local freeze with counter interrogation
Mode C: Freeze and transmit by counter interrogation commands
Mode D: Freeze by counter interrogation command, frozen values reported spontaneously
Counter read
Counter freeze without reset
Counter freeze with reset
Counter reset,
General request counter
Request counter group 1
7 Parameter loading
X Threshold value
Smoothing factor
10
Low limit for transmission of measured value
11
High limit for transmission of measured value
12
13 Parameter activation
Act/deact of persistent cyclic or periodic transmission of the addressed object
16
17
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 207 - 88/288/CDV
1 Test procedure
Test procedure
5 File transfer
6 (station-specific parameter, mark ‘ X ’ if function is used)
7 File transfer in monitor direction
Transparent file
Transmission of disturbance data of protection equipment
Transmission of sequences of events
Transmission of sequences of recorded analogue values
9 File transfer in control direction
Transparent file
10
11 Background scan
Background scan
14
15 Acquisition of transmission delay

18 Definition of time outs

Parameter Default value Remarks Selected value
t0 30s Time out of connection establishment
t1 15s Time out of send or test APDUs
t2 10s Time out for acknowledges in case of no data

messages t2 < t1
t3 20s Time out for sending test frames in case of a

long idle state
19 Maximum range of values for all time outs: 1 to 255 s, accuracy 1 s

20 Note: The timer must be adjusted for the concrete link or system in order to achieve an deterministich and desired
21 functionality of the system.
22 Maximum number of outstanding I format APDUs k and latest acknowledge
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 208 - 88/288/CDV
Parameter Default value Remarks Selected value
k 12 APDUs Maximum difference receive sequence num-

ber to send state variable
w 8 APDUs Latest acknowledge after receiving w I-format

APDUs
15
1 Maximum range of values k: 1 to 32767 (2 -1) APDUs, accuracy 1 APDU
2 Maximum range of values w: 1 to 32767 APDUs, accuracy 1 APDU (Recommendation: w should not
3 exceed 2/3 of k).
4 Note: The parameters k and w must be adjusted for the concrete link in order to utilize the provided bandwidth .
5 Portnumber
Parameter Value Remarks
Portnumber 2404 In all cases

6
7 RFC 2200 suite

8 RFC 2200 is an official Internet Standard which describes the state of standardization of protocols
9 used in the Internet as determined by the Internet Architecture Board (IAB). It offers a broad spectrum
10 of actual standards used in the Internet. The suitable selection of documents from RFC 2200 defined
11 in this standard for given projects has to be chosen by the user of this standard.
X Ethernet 802.3
Serial X.21 interface
Other selection from RFC 2200:
12
13 List of valid documents from RFC 2200
1: ……………………………………………………
2: ……………………………………………………
3: ……………………………………………………
4: ……………………………………………………
Etc
14 Editors note: Specifications for the data link layer and the physical layer are implementation specific and beyond
15 the scope of the IEC 61400-25 series.
16
17 D.6.3 Redundancy / Redundant connections
18 The companion standard IEC 60870-5-104 defines network access for IEC 60870-5-101 us-
19 ing the TCP/IP transport profile, and mainly focuses on the use of a single TCP connection.
20 In many cases, however, redundancy is required to increase the availability of the system. In
21 these cases, multiple redundant connections should be established between the two stations.
22 This clause describes in short the interoperability issues that arise when standby connections
23 are used as redundant connections. The companion standard IEC 60870-5-104 Ed.2 de-
24 scribes the details regarding redundant connections.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 209 - 88/288/CDV
1 Redundant communication in a system using IEC 60870-5-104 can be achieved by providing

2 the possibility to establish more than one logical connection between two stations. A logical
3 connection is defined by a unique combination of two IP-addresses and two port-numbers,
4 namely controlling station IP-address/port-number pair and controlled station IP-
5 address/portnumber pair.
6 Connection establishment is performed by the controlling station in the case of a controlled

7 station as a partner, or by a fixed selection (parameter) in case of two equivalent controlling-
8 stations or partners. The station that performs the connection establishment is in either case
9 referred to as the controlling station (station A) in the subsequent description, while the part-
10 ner station is referred to as the controlled station (station B).
11 The following general rules apply to this clause concerning redundant connections:
12 1) The controlling and controlled station shall be able to handle multiple ( N ) logical connec-
13 tions.
14 2) The N logical connections represent one redundancy group.
15 3) Only one logical connection is in the started state and sending/receiving user data at a
16 time for one redundancy group.
17 4) The controlling station decides which one of the N connections is to be in started state.
18 5) All logical connections of a redundancy group shall be supervised by test frames
19 6) A redundancy group shall rely upon only one process image (database/event buffer).
20 7) If more than one controlling station need to access the same controlled station simulta-
21 neously, each controlling station must be assigned to a different redundancy group (proc-
22 ess image).
23 The logical connection which is enabled for user data transfer (started) at any time is defined
24 to be the started connection, while the others are stopped connections. Selection of started
25 connection is performed by means of the unnumbered control functions (U-frames)
26 STARTDT/STOPDT
27 As stated in rule 4 above, the selection and switchover of the started connection is always ini-
28 tiated by the controlling station, and is managed by the transport interface or higher lay-
29 ers.Selection of the started connection after station initialisation is performed by transmitting
30 a STARTDT_ACT on the desired connection. Similarly, connection switchover in the case of a
31 failure (connection failover) is performed by transmitting a STARTDT_ACT on the stopped
32 connection that is selected to take over. The controlled station (station B) always understands
33 the connection on which it last received a STARTDT_ACT as the started connection. It con-
34 firms the activation request by issuing a STARTDT_CON. The whole activation procedure is
35 completed when the STARTDT_CON is received in the controlling station.
36 Manual connection switchover can be performed by first issuing a STOPDT_ACT on the cur-
37 rently started connection and then a STARTDT_ACT on the selected new started connection.
38 This will gracefully terminate data transfer on the first connection before it is resumed on the
39 new connection. The controlling and/or controlled station shall regularly check the status of all
40 established connections to detect any communication problems as soon as possible. This is
41 done by sending TESTFR frames.
42 Send and receive counters on each connection within a redundancy group continue their func-
43 tionality independently of the use of STARTDT/STOPDT and this will prevent loss of data be-
44 tween the two stations.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 210 - 88/288/CDV
1 D.7 Signal mapping List
2 This section describes how the IEC 60870-5-104 addressing information can be linked with
3 the IEC 61400-25-2 Information Model. Apart from that, the configuration and descriptive in-
4 formation, that is not interchanged by communication means, shall be described in the Signal
5 Mapping List so both sides in the communication link can share the information.
6 The SML file is a configuration file that shall be shared by both client and server. It reflects a
7 contract that links the IEC 60870-5-104 addressing information to the IEC-61400-25-2 infor-
8 mation model so both sides are able to know the reference and "meaning" of any data inter-
9 changed. The SML file shall typically be stored at the server and be accessible to clients. The
10 content shall reflect the latest configured information.
11 The Signal Mapping List is described in a XML format so it can be easily interpreted and
12 transformed. In this section a schema definition of the SML is described; this schema restricts
13 the information allowed and assure that the information of the SML file can be processed by
14 different tools.
15 D.7.1 Signal mapping list schema definition
16 The SML file is divided in two different sections:
17 - LD: This section focus on the definition of the address that allows the master-station (cli-
18 ent) to access the different data of the IM inside the remote station (server)
19 - DOITypes: It describes the data attributes and the ASDUs that can be accessed by any of
20 the IOAs defined in the LD section.
21 D.7.1.1 Signal Mapping List LD definition
22 Each logical device shall be represented by an LD inside the SML file. The LD is defined by
23 its name and its address CASDU. This address shall aply to all the data inside the logical de-
24 vice.
25 A Logical Device shall be composed of Logical Nodes represented by the LN tag.
26 D.7.1.1.1 Signal Mapping List LN definition
27 The Logical Node LN only allows the inclusion of the attribute “name”.
28 A Logical Node shall be composed of a DOI (Data Object Instance) represented by the DOI
29 tag.
30 D.7.1.1.2 Signal Mapping List DOI definition
31 The DOI is defined by the attributes name, type, cdc and ioa.
32 <DOI name="DataMV" type="defaultMV" cdc="MV" ioa="6001" />
33 The “type” attribue links a specific instance of a Data with one of the types defined in the
34 DOITypes section.
35 The “cdc” is used to check that the structured defined in the “DOITypes” is in accordance with
36 the specification of the mapping.
37 The “ioa” defines how this data can be accessed by communication means.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 211 - 88/288/CDV
1 A DOI is composed of DOIs (if it is a complex CDC) and it can include the definition of con-
2 figuration and description attributes using the DAI element.
3 D.7.1.1.3 Signal Mapping List DAI definition
4 The DAI (Data Attribute Instance) allows the definition of configuration and descriptive attrib-
5 utes that are not interchanged by communication services.
6 <DAI name="ctlModel" fc="CF" bType="Enum">

7 <Val>status-only</Val>
8 </DAI>
9
10 D.7.1.2 Signal Mapping List DOITypes definition
11 The DOITypes section is composed of the set of “DOIType” element that allows the definition
12 of all the information hold in the IM that is interchanged by communication services.
13 D.7.1.2.1 Signal Mapping List DOIType definition
14 Each simple CDC defined by a DOI in the LD section will be linked to a type defined as a
15 DOIType. The attribute “id” of the DOIType shall be equal to the value defined by the attribute
16 “type” inside the “DOI” tag.
17 A DOIType is composed of the ASDUs used to obtain the information of that data.
18 D.7.1.2.2 Signal Mapping List ASDU definition
19 The ASDU is defined by the attributes:
20 • “ti” (type ident) that details the structure that is interchanged in the communication service.
21 • “cot” (cause of transmision) of this ASDU (event, part of gi,…). Each cause of transmision is
22 assigned a defined number.
23 <ASDU ti="3" cot="20">

24 <DA name="stVal" fc="ST" bType="Dbpos" typ104="DIQ" />
25 <DA name="q" fc="ST" bType="Quality" typ104="DIQ" />
26 </ASDU>
27 An ASDU is composed of the DAs (DataAttributes) of the IM that are obtained when this
28 ASDU is received.
29
30 D.7.1.2.3 Signal Mapping List DA definition
31 The DA represents each attribute that is obtained with the ASDU it is included in. It details
32 where this information is stored inside the ASDU (“typ104” attribute”).

34 The DA shall be always a BasicType. The complex DataAttributes shall be descomposed in
35 simple ones using different instances of DA elements.
36 <DA name="mag.f" fc="MX" bType="FLOAT32" typ104="IEEE_STD_754" />

37
38 D.7.2 Signal Mapping List schema definition

39 <?xml version="1.0" encoding="UTF-8" ?>
40 <xs:schema targetNamespace="http://www.iec.ch/61400-25-4-D/2007/SML"
41 xmlns:xs="http://www.w3.org/2001/XMLSchema"
42 xmlns="http://www.iec.ch/61400-25-4-D/2007/SML"
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 212 - 88/288/CDV
1 xmlns:sml="http://www.iec.ch/61400-25-4-D/2007/SML" elementFormDe-
2 fault="qualified" attributeFormDefault="unqualified" finalDefault="extension" ver-
3 sion="1.0">
4 - <xs:annotation>
5 <xs:documentation xml:lang="en">COPYRIGHT IEC, 2007. Version 1.0. Re-
6 lease 2006/10/24. (Uncommented)</xs:documentation>
7 </xs:annotation>
8 <xs:simpleType name="tBasicTypeEnum">
9 <xs:restriction base="xs:string">
10 <xs:enumeration value="BOOLEAN" />
11 <xs:enumeration value="INT8" />
16 <xs:enumeration value="INT8U" />
20 <xs:enumeration value="FLOAT32" />
21 <xs:enumeration value="FLOAT64" />
22 <xs:enumeration value="Enum" />
23 <xs:enumeration value="Dbpos" />
24 <xs:enumeration value="Tcmd" />
25 <xs:enumeration value="Quality" />
26 <xs:enumeration value="Timestamp" />
27 <xs:enumeration value="VisString32" />
30 <xs:enumeration value="Octet64" />
31 <xs:enumeration value="EntryTime" />
32 <xs:enumeration value="Unicode255" />
33 </xs:restriction>
34 </xs:simpleType>
35 <xs:simpleType name="tType104">
37 <xs:enumeration value="SIQ" />
38 <xs:enumeration value="DIQ" />
39 <xs:enumeration value="SVA" />
40 <xs:enumeration value="SCO" />
41 <xs:enumeration value="DCO" />
42 <xs:enumeration value="RCO" />
43 <xs:enumeration value="QDS" />
44 <xs:enumeration value="VTI" />
45 <xs:enumeration value="IEEE_STD_754" />
46 <xs:enumeration value="BCR_VAL" />
47 <xs:enumeration value="CP56Time2a" />
49 </xs:simpleType>
50 <xs:simpleType name="tCDC">
52 <xs:enumeration value="SPS" />
53 <xs:enumeration value="DPS" />
54 <xs:enumeration value="INS" />
55 <xs:enumeration value="BCR" />
56 <xs:enumeration value="SPC" />
57 <xs:enumeration value="DPC" />
58 <xs:enumeration value="INC" />
59 <xs:enumeration value="APC" />
60 <xs:enumeration value="BSC" />
61 <xs:enumeration value="MV" />
62 <xs:enumeration value="CMV" />
63 <xs:enumeration value="WYE" />
64 <xs:enumeration value="DEL" />
65 <xs:enumeration value="STV" />
66 <xs:enumeration value="SPV" />
67 <xs:enumeration value="ALM" />
68 <xs:enumeration value="CMD" />
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 213 - 88/288/CDV
1 <xs:enumeration value="CTE" />

2 <xs:enumeration value="TMS" />
3 </xs:restriction>
4 </xs:simpleType>
5 <xs:simpleType name="tFC">
7 <xs:enumeration value="ST" />
8 <xs:enumeration value="MX" />
9 <xs:enumeration value="CF" />
10 <xs:enumeration value="DC" />
11 <xs:enumeration value="CO" />
12 <xs:enumeration value="EX" />
14 </xs:simpleType>
15 <xs:simpleType name="tTypeInformation">
17 <xs:enumeration value="1" />
35 </xs:simpleType>
36 <xs:simpleType name="tCauseOfTransmision">
41 </xs:simpleType>
42 
45 <xs:complexType name="tDAI">
46 <xs:sequence>
47 <xs:element name="Val" type="xs:string" />
48 </xs:sequence>
49 <xs:attribute name="name" type="xs:string" use="required" />
50 <xs:attribute name="fc" type="tFC" use="optional" />
51 <xs:attribute name="bType" type="tBasicTypeEnum" use="optional" />
52 </xs:complexType>
53 <xs:complexType name="tDOI">
54 <xs:sequence>
55 <xs:element name="DOI" type="tDOI" minOccurs="0" maxOc-
56 curs="unbounded">
57 <xs:unique name="UniqueDOIinDOI">
58 <xs:selector xpath="./DOI" />
59 <xs:field xpath="@name" />
60 <xs:field xpath="@type" />
61 <xs:field xpath="@ioa" />
62 </xs:unique>
63 <xs:unique name="UniqueDAIinDOI">
64 <xs:selector xpath="./DAI" />
66 <xs:field xpath="@fc" />
67 </xs:unique>
68 </xs:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 214 - 88/288/CDV
1 <xs:element name="DAI" type="tDAI" minOccurs="0" maxOc-

2 curs="unbounded" />
3 </xs:sequence>
5 <xs:attribute name="cdc" type="tCDC" use="required" />
6 <xs:attribute name="ioa" type="xs:integer" use="optional" />
7 <xs:attribute name="type" type="xs:string" use="optional" />
8 </xs:complexType>
9 <xs:complexType name="tLN">
10 <xs:sequence>
11 <xs:element name="DOI" type="tDOI" minOccurs="0" maxOc-
13 <xs:unique name="UniqueDOIinDOILN">
14 <xs:selector xpath="./DOI" />
18 </xs:unique>
19 <xs:unique name="UniqueDAIinDOILN">
20 <xs:selector xpath="./DAI" />
23 </xs:unique>
24 </xs:element>
25 </xs:sequence>
28 <xs:complexType name="tLD">
29 <xs:sequence>
30 <xs:element name="LN" type="tLN" minOccurs="0" maxOc-
32 <xs:unique name="UniqueDOIInLN">
33 <xs:selector xpath="sml:DOI" />
37 </xs:unique>
38 </xs:element>
39 </xs:sequence>
41 <xs:attribute name="casdu" type="xs:string" use="required" />
43 
46 <xs:complexType name="tDA">
48 <xs:attribute name="fc" type="tFC" use="required" />
49 <xs:attribute name="bType" type="tBasicTypeEnum" use="required" />
50 <xs:attribute name="typ104" type="tType104" use="required" />
52 <xs:complexType name="tASDU">
53 <xs:sequence>
54 <xs:element name="DA" type="tDA" minOccurs="1" maxOc-
55 curs="unbounded" />
56 </xs:sequence>
57 <xs:attribute name="ti" type="tTypeInformation" use="required" />
58 <xs:attribute name="cot" type="tCauseOfTransmision" use="optional" />
60 <xs:complexType name="tDOIType">
61 <xs:sequence>
62 <xs:element name="ASDU" type="tASDU" minOccurs="1" maxOc-
64 <xs:unique name="UniqueDAinASDU">
65 <xs:selector xpath="sml:DA" />
68 </xs:unique>
69 </xs:element>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 215 - 88/288/CDV
1 </xs:sequence>
2 <xs:attribute name="id" type="xs:string" use="required" />
3 </xs:complexType>
4 <xs:complexType name="tDOITypes">
5 <xs:sequence>
6 <xs:element name="DOIType" type="tDOIType" minOccurs="1" maxOc-
7 curs="unbounded">
8 <xs:unique name="UniqueDOITypeIdinDOITypes">
9 <xs:selector xpath="sml:DOIType" />
10 <xs:field xpath="@id" />
11 </xs:unique>
12 </xs:element>
13 </xs:sequence>
15 <xs:element name="SML">
16 <xs:complexType>
17 <xs:sequence>
18 <xs:element name="LD" type="tLD" minOccurs="0" maxOc-
20 <xs:unique name="UniqueLDInSCL">
21 <xs:selector xpath="sml:LD" />
23 </xs:unique>
24 </xs:element>
25 <xs:element name="DOITypes" type="tDOITypes" minOccurs="1"
26 maxOccurs="1" />
27 </xs:sequence>
28 <xs:attribute name="version" type="xs:string" use="optional" />
29 <xs:attribute name="revision" type="xs:string" use="optional" />
31 <xs:key name="DOITypeKey">
32 <xs:selector xpath="./sml:DOITypes/sml:DOIType" />
33 <xs:field xpath="@id" />
34 </xs:key>
35 <xs:keyref name="ref2DOIType" refer="DOITypeKey">
36 <xs:selector xpath="./sml:LD/sml:LN/sml:DOI" />
38 </xs:keyref>
39 <xs:keyref name="ref2DOITypeComplex" refer="DOITypeKey">
40 <xs:selector xpath="./sml:LD/sml:LN/sml:DOI/sml:DOI" />
42 </xs:keyref>
43 </xs:element>
44 </xs:schema>
45
46 D.7.3 SML file example
47 This section shows an example including all the datatypes defined.
48 <?xml version="1.0" encoding="ISO-8859-1" ?>

49 <SML xmlns="http://www.iec.ch/61400-25-4-D/2007/SML"
50 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
51 xsi:schemaLocation="http://www.iec.ch/61400-25-4-D/2007/SML SML.xsd">
52 <LD name="LDName" casdu="100">
53 <LN name="LNName">
54 <DOI name="DataSPS" type="defaultSPS" cdc="SPS" ioa="1001" />
55 <DOI name="DataINS" type="defaultINS35" cdc="INS" ioa="2001" />
56 <DOI name="DataSPC" type="defaultSPCwithoutControl" cdc="SPC"
57 ioa="3001">
59 <Val>status-only</Val>
60 </DAI>
61 </DOI>
62 <DOI name="DataSPC2" type="defaultSPC" cdc="SPC" ioa="3002">
64 <Val>direct-with-normal-security</Val>
65 </DAI>
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 216 - 88/288/CDV
1 </DOI>
2 <DOI name="DataINC" type="defaultINC" cdc="INC" ioa="4001">
4 <Val>sbo-with-normal-security</Val>
5 </DAI>
6 </DOI>
7 <DOI name="DataAPC" type="defaultAPC" cdc="APC" ioa="5001">
9 <Val> sbo-with-normal-security </Val>
10 </DAI>
11 </DOI>
12 <DOI name="DataMV" type="defaultMV" cdc="MV" ioa="6001" />
13 <DOI name="DataMV2" type="defaultMV" cdc="MV" ioa="6002">
14 <DAI name="units.SIunit" fc="CF" bType="Enum">
15 <Val>0</Val>
16 </DAI>
17 <DAI name="units.multiplier" fc="CF" bType="Enum">
18 <Val>1</Val>
19 </DAI>
20 <DAI name="d" fc="DC" bType="VisString255">
21 <Val>Descriptive information of this data</Val>
22 </DAI>
23 </DOI>
24 <DOI name="DataCMV" type="default_CMV_mag" cdc="CMV"
25 ioa="7001" />
26 <DOI name="DataCMV2" type="default_CMV_ang" cdc="CMV"
27 ioa="7002" />
28 <DOI name="DataDEL" cdc="DEL" ioa="8001">
29 <DOI name="phsAB" type="default_CMV_mag" cdc="CMV"
30 ioa="8002" />
31 <DOI name="phsAB" type="default_CMV_ang" cdc="CMV"
32 ioa="8003" />
33 <DOI name="phsBC" type="default_CMV_mag" cdc="CMV"
34 ioa="8004" />
35 <DOI name="phsBC" type="default_CMV_ang" cdc="CMV"
36 ioa="8005" />
37 <DOI name="phsCA" type="default_CMV_mag" cdc="CMV"
38 ioa="8006" />
39 <DOI name="phsCA" type="default_CMV_ang" cdc="CMV"
40 ioa="8007" />
41 </DOI>
42 <DOI name="DataWYE" cdc="WYE" ioa="9001">
43 <DOI name="phsA" type="defaultMV" cdc="MV" ioa="9002" />
44 <DOI name="phsB" type="defaultMV" cdc="MV" ioa="9003" />
45 <DOI name="phsC" type="defaultMV" cdc="MV" ioa="9004" />
46 <DOI name="neut" type="defaultMV" cdc="MV" ioa="9005" />
47 <DOI name="net" type="defaultMV" cdc="MV" ioa="9006" />
48 <DOI name="res" type="defaultMV" cdc="MV" ioa="9007" />
49 </DOI>
50 <DOI name="DataSTV" cdc="STV" ioa="10001">
51 <DOI name="actSt" type="defaultINS35" cdc="INS" ioa="10001"
52 />
53 </DOI>
54 <DOI name="DataSPV" cdc="SPV" ioa="11001">
55 <DOI name="actVal" type="defaultAPC" cdc="APC" ioa="11001" />
56 </DOI>
57 <DOI name="DataALM" cdc="ALM" ioa="12001">
58 <DOI name="almAck" type="defaultSPC" cdc="SPC" ioa="12001"
59 />
60 <DOI name="actVal" type="defaultINS35" cdc="INS" ioa="12002"
61 />
62 </DOI>
63 <DOI name="DataCMD" cdc="CMD" ioa="13001">
64 <DOI name="actVal" type="defaultINC" cdc="INC" ioa="13001" />
65 </DOI>
66 <DOI name="DataCTE" cdc="CTE" ioa="14001">
67 <DOI name="manRs" type="defaultSPC" cdc="SPC" ioa="14002" />
68 <DOI name="actCtVal" type="defaultINS37" cdc="INS"
69 ioa="14003" />
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 217 - 88/288/CDV
1 </DOI>
2 <DOI name="DataCTE" cdc="CTE" ioa="14001">
4 <DOI name="actCtVal" type="defaultINS37" cdc="INS"
5 ioa="14003" />
6 </DOI>
7 <DOI name="DataTMS" cdc="TMS" ioa="15001">
9 <DOI name="actTmVal" type="defaultINS37" cdc="INS"
10 ioa="15003" />
11 <DOI name="oldTmVal" type="defaultINS37" cdc="INS"
12 ioa="15004" />
13 </DOI>
14 <DOI name="DataBCR" type="defaultBCR" cdc="BCR" ioa="16001" />
15 <!
16 IEC61850 CDCs defined
17 >
18 <DOI name="DataDPS" type="defaultDPS" cdc="DPS" ioa="17001" />
19 <DOI name="DataDPC" type="defaultDPC" cdc="DPC" ioa="18001" />
20 <DOI name="DataBSC" type="defaultBSC" cdc="BSC" ioa="19001" />
21 </LN>
22 </LD>
23 <DOITypes>
24 <DOIType id="defaultSPS">
25 <ASDU ti="1" cot="20">
26 <DA name="stVal" fc="ST" bType="BOOLEAN" typ104="SIQ" />
27 <DA name="q" fc="ST" bType="Quality" typ104="SIQ" />
28 </ASDU>
29 <ASDU ti="30" cot="3">
32 <DA name="t" fc="ST" bType="Timestamp" typ104="CP56Time2a"
33 />
34 </ASDU>
35 </DOIType>
36 <DOIType id="defaultDPS">
37 <ASDU ti="3" cot="20">
40 </ASDU>
41 <ASDU ti="31" cot="3">
45 />
46 </ASDU>
47 </DOIType>
48 <DOIType id="defaultINS35">
49 <ASDU ti="11" cot="20">
50 <DA name="stVal" fc="ST" bType="INT32" typ104="SVA" />
51 <DA name="q" fc="ST" bType="Quality" typ104="QDS" />
52 </ASDU>
53 <ASDU ti="35" cot="3">
57 />
58 </ASDU>
59 </DOIType>
60 <DOIType id="defaultINS37">
61 <ASDU ti="37" cot="3">
62 <DA name="stVal" fc="ST" bType="INT32" typ104="BCR_VAL" />
63 <DA name="q" fc="ST" bType="Quality" typ104="BCR_VAL" />
65 />
66 </ASDU>
67 </DOIType>
68 <DOIType id="defaultSPC">
69 <ASDU ti="30" cot="3">
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 218 - 88/288/CDV

4 />
5 </ASDU>
6 <ASDU ti="58">
7 <DA name="ctlVal" fc="CO" bType="BOOLEAN" typ104="SCO" />
8 </ASDU>
9 </DOIType>
10 <DOIType id="defaultSPCwithoutControl">
11 <ASDU ti="30" cot="3">
15 />
16 </ASDU>
17 </DOIType>
18 <DOIType id="defaultDPC">
19 <ASDU ti="31" cot="3">
23 />
24 </ASDU>
25 <ASDU ti="59">
26 <DA name="ctlVal" fc="CO" bType="BOOLEAN" typ104="DCO" />
27 </ASDU>
28 </DOIType>
29 <DOIType id="defaultINC">
30 <ASDU ti="35" cot="3">
34 />
35 </ASDU>
36 <ASDU ti="62">
37 <DA name="ctlVal" fc="CO" bType="INT32" typ104="SVA" />
38 </ASDU>
39 </DOIType>
40 <DOIType id="defaultAPC">
41 <ASDU ti="36" cot="3">
42 <DA name="mxVal.f" fc="MX" bType="FLOAT32" typ104="SIQ" />
43 <DA name="q" fc="MX" bType="Quality" typ104="SIQ" />
44 <DA name="t" fc="MX" bType="Timestamp" typ104="CP56Time2a"
45 />
46 </ASDU>
47 <ASDU ti="63">
48 <DA name="ctVal.f" fc="CO" bType="FLOAT32"
49 typ104="IEEE_STD_754" />
50 </ASDU>
51 </DOIType>
52 <DOIType id="defaultBSC">
53 <ASDU ti="5" cot="20">
54 <DA name="valWTr.posVal" fc="ST" bType="INT8" typ104="VTI" />
55 <DA name="q" fc="MX" bType="Quality" typ104="QDS" />
56 </ASDU>
57 <ASDU ti="32" cot="3">
58 <DA name="valWTr.posVal" fc="ST" bType="INT8" typ104="VTI" />
61 />
62 </ASDU>
63 <ASDU ti="60">
64 <DA name="ctVal" fc="CO" bType="Tcmd" typ104="RCO" />
65 </ASDU>
66 </DOIType>
67 <DOIType id="defaultMV">
68 <ASDU ti="13" cot="20">
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 219 - 88/288/CDV
1 <DA name="mag.f" fc="MX" bType="FLOAT32"

2 typ104="IEEE_STD_754" />
4 </ASDU>
5 <ASDU ti="36" cot="3">
6 <DA name="mag.f" fc="MX" bType="FLOAT32"
7 typ104="IEEE_STD_754" />
10 />
11 </ASDU>
12 </DOIType>
13 <DOIType id="default_CMV_mag">
14 <ASDU ti="13" cot="20">
15 <DA name="cVal.mag.f" fc="MX" bType="FLOAT32"
16 typ104="IEEE_STD_754" />
18 </ASDU>
19 <ASDU ti="36" cot="3">
20 <DA name="cVal.mag.f" fc="MX" bType="FLOAT32"
21 typ104="IEEE_STD_754" />
24 />
25 </ASDU>
26 </DOIType>
27 <DOIType id="default_CMV_ang">
28 <ASDU ti="13" cot="20">
29 <DA name="cVal.ang.f" fc="MX" bType="FLOAT32"
30 typ104="IEEE_STD_754" />
32 </ASDU>
33 <ASDU ti="36" cot="3">
34 <DA name="cVal.ang.f" fc="MX" bType="FLOAT32"
35 typ104="IEEE_STD_754" />
38 />
39 </ASDU>
40 </DOIType>
41 <DOIType id="defaultBCR">
42 <ASDU ti="15" cot="20">
43 <DA name="actVal" fc="ST" bType="INT128" typ104="BCR_VAL" />
45 </ASDU>
46 <ASDU ti="37" cot="3">
47 <DA name="actVal" fc="ST" bType="INT128" typ104="BCR_VAL" />
50 />
51 </ASDU>
52 </DOIType>
53 </DOITypes>
54 </SML>
55
56
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 220 - 88/288/CDV
1 Annex E
2 (normative)
3
5 Mapping to DNP3
7 E.1 General
8 E.1.1 Introduction
9 This Annex describes the mapping of information model and information exchange model de-
10 fined in IEC 61400-25-2 and IEC 61400-25-3 to DNP3.
11 Clause E.1 provides an general introduction of the mapping to DNP3.
12 Clause E.2 provides the list of normative references for mapping to DNP3.
13 Clause E.3 provides a list of abbreviated terms used in annex E.
14 Clause E.4 provides mapping of the information model to DNP3 services.
15 Clause E.5 provides mapping of the information exchange model to DNP3.
16 Clause E.6 specifies the interoperability detail (device profile document) for the mapped
17 DNP3 interface.
18 E.1.2 Scope
19 The scope of the mapping to DNP3 services is the real-time exchange of process information
20 required for operational purposes. The amount of real-time information provided by the server
21 can vary dependent on the operational needs. Actors could be local, regional or nationwide
22 control centres that receive real-time information on the current state (status and measurand
23 information) and send control and setpoint commands. The regional and nationwide control
24 centre may communicate with a SCADA concentrator that includes wind power plant controller
25 functions to ensure that the complete system adapts itself to conditions and requirements for
26 the electrical power connection.
27 NOTE The exchange of this real-time information maps a small number of DataAttributes of the common data
28 classes defined in IEC 61400-25-2.
29 E.1.3 The mapping architecture
32 2. Mapping of the data classes
34 The specified mapping for IEC 61400-25 is based on using DNP3 Data Sets to transport the
35 information modelled of the wind power plant components in a outstation – master based ar-
36 chitecture.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 221 - 88/288/CDV
1 The wind power plant information model defined in 61400-25-2 shall be mapped to DNP3 data
2 set descriptors with DNP3 objects as defined in the DNP V3.00 Data Object Library.
3 NOTE This results in the encapsulation of path names.
4 The conceptual mapping is depicted in Figure E-1. The Information Model of IEC 61400-25 is
5 intended to be hidden when mapped to DNP3. This means especially that
6 – the server encapsulates the Information Model of IEC 61400-25-2 that can be read by the
7 services (according to DNP3 Technical Bulletin TB2003/001),
8 – the master/client station accesses the DataAttributes from the Information Model of IEC
9 61400-25-2 through the services provided by DNP3.
10
Server/Outstation -
Read Information
Master/ M/C sees the encapsulated IM Object Model of
Client Group 0 IEC 61400-25
(e.g., WGEN)
Information
Exchange Methods
for process data
DNP3 interface DNP3 interface

M/C uses a subset of the IEM
Signals
existing Data Objects
existing Data Objects

11
12 Figure E-1 – Mapping architecture (conceptual)
13 The service models defined in IEC 61400-25-3 IEM and the mapping to DNP3 is summarised
14 in Table E-1.
15 Table E-1 – Services requiring Client/Server Communication Profile
IEC 61400-25-2 IM Class IEC 61400-25-3 IEM Services M/O Maps to DNP3
SERVER outstation (controlled station)
a
GetServerDirectory O Read Object Group 0
ASSOCIATION
Associate M RESET of remote link; DNP3
Data Link Layer
b
Abort O n.a.
Release O b
n.a.
LOGICAL-DEVICE
a
GetLogicalDeviceDirectory O Read Object Group 0
LOGICAL-NODE
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 222 - 88/288/CDV
IEC 61400-25-2 IM Class IEC 61400-25-3 IEM Services M/O Maps to DNP3
GetLogicalNodeDirectory O b
n.a.
DATA
GetDataValues M Read (Function Code 1)
SetDataValues M Write (Function Code 2)
b
GetDataDirectory O n.a.
b
GetDataDefinition O n.a.
DATA-SET
GetDataSetValues M c
Read (Function Code 1)
SetDataSetValues O c
Write (Function Code 2)
CreateDataSet O b
n.a.
b
DeleteDataSet O n.a.
b
GetDataSetDirectory O n.a.
REPORT
Report O b
n.a.
GetBRCBValues O b
n.a.
SetBRCBValues O b
n.a.
GetURCBValues O b
n.a.
SetURCBValues O b
n.a.
AddSubscription O b
n.a.
RemoveSubscription O b
n.a.
LOG-CONTROL-BLOCK
GetLCBValues O b
n.a.
SetLCBValues O b
n.a.
LOG
GetLogStatusValues O b
n.a.
QueryLogByTime O b
n.a.
QueryLogAfter O b
n.a.
CONTROL
Select O Select (Function Code 3)
SelectWithValue O Select (Function Code 3)
Cancel O b
n.a.
Operate M Operate (Function Code 4)
CommandTermination O Operate (Function Code 4)
b
TimeActivatedOperate O n.a.
a Read Object Group 0 see Technical Bulletin TB2003/001 and TB2005/001a
b not applicable for the mapping to DNP3
c partially applicable for the mapping to DNP3 see Technical Bulletin TB2004-004e
1
2
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 223 - 88/288/CDV
1 E.2 Normative references for DNP3 services
2 DNP V3.00 Subset Definitions , Edition 2.00, November 1995, DNP Users Group; Document
3 Nr. P009-0IG.SUB
4 DNP V3.00 Data Object Library , Edition 0.02, July 1997, DNP Users Group; Document Nr.
5 P009-0BL
6 DNP3 Specification Volume 2 Application Layer, Version 2.00, October 2005, DNP Users
7 Group
8 DNP3 Specification Volume 3 Transport Function, Version 2.00, November 2002, DNP Users
9 Group
10 DNP3 Specification Volume 4 Data Link Layer, Version 2.00, December 2002, DNP Users
11 Group
12 DNP3 Specification Volume 6 DNP3 Object Library, Version 2.00, December 2005, DNP Us-
13 ers Group
14 DNP3 Specification Volume 7 IP Networking, Version 2.00, December 2004, DNP Users
15 Group
16 Technical Bulletin TB2004-004e Data Sets , 30 March 2006. DNP Users Group
17 Technical Bulletin TB2003-001 Device Attributes , 8 April 2003. DNP Users Group
18 Technical Bulletin TB2005-001a Output Event Objects , 12 June 2005. DNP Users Group
19 E.3 Abbreviated terms
ACSI Abstract Communication Service Interface

DNP3 Distributed Network Protocol version 3.00
LD Logical Device
LN Logical Node
LOG Log
SCL substation (system) configuration language (defined in IEC 61850-6)
WT Wind Turbine
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 224 - 88/288/CDV
2 E.4 Mapping of the IEC 61400-25 Information Model to DNP3
3 E.4.1 Relationship of Common Data Class and Data Set Prototypes
4 IEC 61400-25-2 specifies common data classes related to wind power plant applications.
5 Specific common data classes in IEC 61400-25-2 shall be mapped to specific data set proto-
6 types in DNP3. Because IEC 61400-25-2 inherits common data classes from IEC 61850 and
7 possibly specialises, a DNP3 Universally Unique Identifier is reserved for each common data
8 class in IEC 61400-25-2. A single DNP3 Namespace is reserved for all common data classes
9 in IEC 61400-25-2. Mapping shall be applied in the outstation (server-side).
10 E.4.2 Relationship of Quality Mapping to SQ2
11 Table E-2 defines the mapping for quality attribute in the IEC 61850-7-3 & IEC 61400-25-2
12 common data classes. The IEC 61850-7-3 & IEC 61400-25-2 data attribute [q] shall map to a
13 DNP3 bitstring in a DNP3 data set prototype.
14 Table E-2 – Quality mapping
Attribute Name Attribute Type DNP3 Data DNP3 Data Element Mapping
Specification
q Quality DAEL:BSTR SQ2 - Object coding
validity -> IV/NT
good | invalid -> on-line | off-line
detailQual -> OV
overflow -> over-range
source -> SB
substituted -> local forced
blocked -> force off-line
15 The ancillary value associated with each DNP3 data element shall be the IEC 61400-25-2 At-
16 tribute Name e.g. “q”.
17 E.4.3 CDC Measured Value (MV)
18 Table E-3 defines the mapping for data attributes in the IEC 61850-7-3 common data class
19 MV. The data attributes [mag + t + q] shall map to a DNP3 data set prototype.
20 Table E-3 – CDC: Measured Value (MV) mapping
Specification
- - UUID:OSTR {29787E10-484F-4B22-A7BF-1C669D3748E8}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “MV”
mag AnalogueValue DAEL:FLT32 32-bit floating point value
q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)

t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
22 tribute Name e.g. “mag”.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 225 - 88/288/CDV
1 E.4.4 CDC Setpoint Parameter Value (SPV)
3 SPV. The mandatory data attributes of [chaManRs + actVal + oldVal] shall map to a DNP3
4 data set prototype.
5 Table E-4 – CDC: Setpoint Parameter Value (SPV) mapping
Specification
- - UUID:OSTR {5DFC4FE5-BBA8-4CB4-934F-0637B19832F6}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “SPV”
- - CTLS:UINT One octet control status element
chaManRs.ctlVal BOOLEAN CTLV:BSTR FLAG ={ BS8 [0..7]
Status = BS1 [0] <0, False; 1, True> }
chaManRs.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
chaManRs.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
chaManRs.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
chaManRs.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
chaManRs.stVal BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]

chaManRs.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)

chaManRs.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
chaManRs.ctlModel CtlModels DAEL:INT32 32-bit integer value

actVal.ctlVal AnalogueValue CTLV:FLT32 32-bit floating point value
actVal.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
actVal.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
actVal.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
actVal.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
actVal.mxVal AnalogueValue DAEL:FLT32 32-bit floating point value
actVal.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)

actVal.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 226 - 88/288/CDV
actVal.ctlModel CtlModels DAEL:INT32 32-bit integer value
oldVal.ctlVal AnalogueValue DAEL:FLT32 32-bit floating point value
oldVal.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)

oldVal.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
oldVal.ctlModel CtlModels DAEL:INT32 32-bit integer value
2 tribute Name e.g. “actVal.mxVal”.
3 E.4.5 CDC Status Value (STV)
5 STV. The mandatory data attributes of [actSt + oldSt] shall map to a DNP3 data set prototype.
6 Table E-5 – CDC: Status Value (STV) mapping
Specification
- - UUID:OSTR {36798E8E-2138-477D-868E-A5B6ADFA0410}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “STV”
actSt.stVal CtxInt DAEL:INT32 32-bit integer value
actSt.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
actSt.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
oldSt.stVal CtxInt DAEL:INT32 32-bit integer value
oldSt.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
oldSt.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
8 tribute Name e.g. “actSt.stVal”.
9 E.4.6 CDC Alarm (ALM)
11 ALM. The mandatory data attributes of [almAck + actSt + oldSt] shall map to a DNP3 data set
12 prototype.
13 Table E-6 – CDC: Alarm (ALM) mapping
Specification
- - UUID:OSTR {E53A1962-0DFC-4506-A509-E1A430A491FA}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “ALM”
almAck.ctlVal BOOLEAN CTLV:BSTR FLAG ={ BS8 [0..7]
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 227 - 88/288/CDV
almAck.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
almAck.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
almAck.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
almAck.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
almAck.stVal BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]

almAck.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)

almAck.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
almAck.ctlModel CtlModels DAEL:INT32 32-bit integer value

3 E.4.7 CDC Command (CMD)
5 CMD. The mandatory data attributes of [actSt + oldSt] shall map to a DNP3 data set proto-
6 type.
7 Table E-7 – CDC: Command (CMD) mapping
Specification
- - UUID:OSTR {3A7C7799-3379-4CC5-B1F0-AE5F865E1AC1}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “CMD”
actSt.ctlVal CtxInt CTLV:INT32 32-bit integer value
actSt.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
actSt.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
actSt.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
actSt.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 228 - 88/288/CDV

actSt.ctlModel CtlModels DAEL:INT32 32-bit integer value

3 E.4.8 CDC Event Counting (CTE)
5 CTE. The mandatory data attributes of [manRs + hisRs + actCtVal + oldCtVal] shall map to a
6 DNP3 data set prototype.
7 Table E-8 – CDC: Event Counting (CTE) mapping
Specification
- - UUID:OSTR {DC8804E1-A36F-4105-8335-27D5344F1BDD}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “CTE”
manRs.ctlVal BOOLEAN CTLV:BSTR FLAG ={ BS8 [0..7]
manRs.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
manRs.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
manRs.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
manRs.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
manRs.stVal BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]

manRs.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)

manRs.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
manRs.ctlModel CtlModels DAEL:INT32 32-bit integer value

hisRs.ctlVal CtxInt CTLV:INT32 32-bit integer value
hisRs.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
hisRs.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 229 - 88/288/CDV
hisRs.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
hisRs.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
hisRs.stVal INT32 DAEL:UINT32 32-bit integer value

hisRs.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
hisRs.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
hisRs.ctlModel CtlModels DAEL:INT32 32-bit integer value
actCtVal.stVal CtxInt DAEL:INT32 32-bit integer value

actCtVal.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
actCtVal.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
oldCtVal.stVal CtxInt DAEL:INT32 32-bit integer value
oldCtVal.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
oldCtVal.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
2 tribute Name e.g. “actCtVal.stVal”.
3 E.4.9 CDC State Timing (TMS)
5 TMS. The mandatory data attributes of [manRs + hisRs + actTmVal + oldTmVal] shall map to
6 a DNP3 data set prototype.
7 Table E-9 – CDC: State Timing (TMS) mapping
Specification
- - UUID:OSTR {FE568612-8574-4B85-999F-21E14C7977B4}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “TMS”
manRs.ctlVal BOOLEAN CTLV:BSTR FLAG ={ BS8 [0..7]
Status = BS1 [0] <0, False; 1, True>}
manRs.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
manRs.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
manRs.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
manRs.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
manRs.stVal BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]

manRs.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)

manRs.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 230 - 88/288/CDV
manRs.ctlModel CtlModels DAEL:INT32 32-bit integer value

hisRs.ctlVal CtxInt CTLV:INT32 32-bit integer value
hisRs.origin.orCat ENUMERATED CTLV:INT32 32-bit integer value
hisRs.origin.orIdent OCTET STRING64 CTLV:OSTR 64 octets
hisRs.origin.orCat ENUMERATED DAEL:INT32 32-bit integer value
hisRs.origin.orIdent OCTET STRING64 DAEL:OSTR 64 octets
hisRs.stVal INT32 DAEL:UINT32 32-bit integer value

hisRs.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
hisRs.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
hisRs.ctlModel CtlModels DAEL:INT32 32-bit integer value
actTmVal.stVal CtxInt DAEL:INT32 32-bit integer value

actTmVal.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
actTmVal.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
oldTmVal.stVal CtxInt DAEL:INT32 32-bit integer value
oldTmVal.q Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
oldTmVal.t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
2 tribute Name egg “actTmVal.stVal”.
3 E.4.10 CDC Single Point Status (SPS)
5 SPS. The data attributes [stVal + t + q] shall map to a DNP3 data set prototype.
6 Table E-10 – CDC: Single Point Status (SPS) mapping
Specification
- - UUID:OSTR {D446D178-8B19-40ED-9F63-BA4E4DB3E3BA}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “SPS”
stVal BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]

8 tribute Name e.g. “stVal”.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 231 - 88/288/CDV
1 E.4.11 CDC Integer Status (INS)
3 INS. The data attributes [stVal + t + q] shall map to a DNP3 data set prototype.
4 Table E-11 – CDC: Integer Status (INS) mapping
Specification
- - UUID:OSTR {9A056CCD-BC92-42EE-ADEA-4B532764AB26}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “INS”
stVal INT32 DAEL:INT32 32-bit integer value
6 tribute Name egg “stVal”.
7 E.4.12 CDC Controllable single point (SPC)
9 SPC. The data attributes [stVal + t + q + ctlVal] shall map to a DNP3 data set prototype.
10 Table E-12 – CDC: Controllable single point (SPC) mapping
Specification
- - UUID:OSTR {FB1BDB9F-9D41-4DDA-AFDC-BC1E6911B3E1}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “SPC”
ctlVal BOOLEAN CTLV:BSTR FLAG ={ BS8 [0..7]
stVal BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]


12 tribute Name eg “stVal”.
13 E.4.13 CDC Controllable integer status (INC)
15 INC. The data attributes [stVal + t + q + ctlVal] shall map to a DNP3 data set prototype.
16 Table E-13 – CDC: Controllable integer status (INC) mapping
Specification
- - UUID:OSTR {FC47BCBE-D3CF-48FA-8311-6CF399C29DE4}
- - NSPC:VSTR “IEC 61400-25-2”
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 232 - 88/288/CDV
- - NAME:VSTR “INC”
ctlVal INT32 CTLV:INT32 32-bit integer value
stVal INT32 DAEL:INT32 32-bit integer value
2 tribute Name eg “stVal”.
3 E.4.14 CDC Binary Counter Reading (BCR)
5 BCR. The data attributes [actVal + t + q] shall map to a DNP3 data set prototype.
6 Table E-14 – CDC: Binary Counter Reading (BCR) mapping
Specification
- - UUID:OSTR {59C03F2E-9DC7-4D5F-8650-92C29FA8BFFA}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “BCR”
actVal INT128 DAEL:OSTR16 128-bit integer value
8 tribute Name eg “actVal”.
10 E.4.15 CDC Controllable analogue set point (APC)
12 APC. The data attributes [setMag + t + q] shall map to a DNP3 data set prototype.
13 Table E-15 – CDC: Controllable analogue set point (APC) mapping
Specification
- - UUID:OSTR {86AF9D1F-B5BF-4F7F-9FB1-8090090EBD87}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “APC”
setMag AnalogueValue CTLV:FLT32 32-bit floating point value
setMag AnalogueValue DAEL:FLT32 32-bit floating point value
15 tribute Name eg “setMag”.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 233 - 88/288/CDV
1 E.4.16 CDC Phase to ground related measured value of a three phase system (WYE)
3 WYE. The data attributes [(phsA | phsB | phsC | neut | net | res) + t + q] shall map to a DNP3
4 data set prototype.
5 Table E-16 – CDC: Phase to ground (WYE) mapping
Specification
- - UUID:OSTR {FCB770FF-0CA7-437C-B6E8-8F0A0C56ABF5}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “WYE”
phsA.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
phsA.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
phsB.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
phsB.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
phsC.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
phsC.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
neut.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
neut.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
net.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
net.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
res.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
res.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
q (note 2) Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
t (note 1) TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
7 tribute Name e.g. “phsA.cVal.mag”.
8 Note 1 - Per 61850-7-3, the individual “t” attribute values shall be identical. The DNP3 mapping shall
9 map one “t” attribute value onto a single DNP3 timestamp.
10 Note 2 – Per 61850-7-3, the individual “q” attribute values may be different. The DNP3 mapping shall
11 map all individual “q” attribute values by ORing onto a single DNP3 bitstring except for the validity flag
12 which will be set off line if any individual “q” attribute is off line.
13 E.4.17 CDC Phase to phase related measured value of a three phase system (DEL)
15 DEL. The data attributes [(phsAB | phsBC | phsCA) + t + q] shall map to a DNP3 data set pro-
16 totype.
17 Table E-17 – CDC: Phase to phase (DEL) mapping
Specification
- - UUID:OSTR {A51B25C2-B0DB-48B2-9038-522DE9D5FB9B}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “DEL”
phsAB.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 234 - 88/288/CDV
phsAB.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value

phsBC.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
phsBC.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
phsCA.cVal.mag AnalogueValue DAEL:FLT32 32-bit floating point value
phsCA.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value
q (note 2) Quality DAEL:BSTR SQ2 - Object coding (refer table E-2)
t (note 1) TimeStamp DAEL:TIME Six octet binary time – Time of occurrence
2 tribute Name e.g. “phsAB.cVal.mag”.
3 Note 1 - Per 61850-7-3, the individual “t” attribute values shall be identical. The DNP3 mapping shall
4 map one “t” attribute value onto a single DNP3 timestamp.
5 Note 2 – Per 61850-7-3, the individual “q” attribute values may be different. The DNP3 mapping shall
6 map all individual “q” attribute values by ORing onto a single DNP3 bitstring except for the validity flag
7 which will be set off line if any individual “q” attribute is off line.
8 E.4.18 CDC Device Name Plate (WDPL)
10 WDPL. The data attributes [vendor + tmOffset + tmUseDT + tmDT] shall map to a DNP3 data
11 set prototype.
12 Table E-18 – CDC: Device Name Plate (WDPL) mapping
Specification
- - UUID:OSTR {4DE9717C-E402-4961-99D9-2ABE3D121847}
- - NSPC:VSTR “IEC 61400-25-2”
- - NAME:VSTR “WDPL”
vendor VISIBLE STRING255 DAEL:VSTR 255 characters
tmOffset INT16 DAEL:INT32 Offset from UTC in minutes
tmUseDT BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]
tmDT BOOLEAN DAEL:BSTR FLAG ={ BS8 [0..7]

14 tribute Name e.g. “vendor”.
15 E.4.19 CDC Logical Node Name Plate (LPL)
17 LPL. The data attributes [vendor + swRev + d] shall map to a DNP3 data set prototype
18 Table E-19 – CDC: Logical Node Name Plate (LPL) mapping
Specification
- - UUID:OSTR {8FA4508F-1547-476F-829D-B3FCB35CA427}
- - NSPC:VSTR “IEC 61400-25-2”
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 235 - 88/288/CDV
- - NAME:VSTR “LPL”
vendor VISIBLE STRING255 DAEL:VSTR 255 characters
swRev VISIBLE STRING255 DAEL:VSTR 255 characters
d VISIBLE STRING255 DAEL:VSTR 255 characters
2 tribute Name eg “vendor”.
3 E.4.20 CDC Alarm Set Status (ASS)
5 ASS. The data attributes [(ARRAY of stVal) + t + q] shall map to a DNP3 data set prototype.
6 Table E-20 – CDC: Alarm Set Status (ASS) mapping
Specification
- - UUID:OSTR (see clause E.4.22)
- - NSPC:VSTR (see clause E.4.22)
- - NAME:VSTR “ASS”
stVal[0] CODED ENUM DAEL:BSTR FLAG ={ BS8 [0..7]
Status = BS1 [1..0] <0, Off;
1, Acknowledge ; 2, Warning; 3; Active>}
Status = BS1 [1..0] <0, Off;
Status = BS1 [1..0] <0, Off;
.................................... ............................. ........................ ..........................................................................
stVal[n] CODED ENUM DAEL:BSTR FLAG ={ BS8 [0..7]
Status = BS1 [1..0] <0, Off;
8 tribute Name eg “stVal[0]”.
9 E.4.21 Relationship of Data Class Attributes and Data Set Descriptors
10 IEC 61400-25-2 specifies data class attributes related to wind power plant applications. Either
11 data class or data class attributes in IEC 61400-25-2 shall be mapped to specific data set de-
12 scriptors in DNP3. Mapping shall be applied in the outstation (server-side).
13 Table E-21 defines the mapping for data attributes in the IEC 61400-25-2 data class attribute
14 WGEN.Spd. The data class attribute [e.g. WGEN.Spd] shall map to a DNP3 data set descrip-
15 tor.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 236 - 88/288/CDV
2 Table E-21 – Sample Data Class Attribute mapping
Specification
- - NAME “WGEN_Spd”
WGEN.Spd MV PTYP UUID of prototype for MV {29787E10-484F-4B22-
A7BF-1C669D3748E8}
3 Table E-21 defines the mapping for data attributes in the IEC 61400-25-2 data class WGEN.
4 The data class [e.g. WGEN] shall map to a DNP3 data set descriptor.
5 Table E-22 – Sample Data Class mapping
Specification
- - NAME “WGEN”
WGEN.OpTmRs TMS PTYP UUID of prototype for TMS {FE568612-8574-
4B85-999F-21E14C7977B4}
WGEN.GnOpMod STV PTYP UUID of prototype for STV {36798E8E-2138-
477D-868E-A5B6ADFA0410}
WGEN.ClSt STV PTYP UUID of prototype for STV {36798E8E-2138-
477D-868E-A5B6ADFA0410}
A7BF-1C669D3748E8}
WGEN.W WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.VAr WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.GnTmpSta MV PTYP UUID of prototype for MV {29787E10-484F-4B22-
A7BF-1C669D3748E8}
WGEN.GnTmpRtr MV PTYP UUID of prototype for MV {29787E10-484F-4B22-
A7BF-1C669D3748E8}
WGEN.GnTmpInlet MV PTYP UUID of prototype for MV {29787E10-484F-4B22-
A7BF-1C669D3748E8}
WGEN.StaPPV DEL PTYP UUID of prototype for DEL {A51B25C2-B0DB-
48B2-9038-522DE9D5FB9B}
WGEN.StaPhV WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.StaA WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.RtrPPV DEL PTYP UUID of prototype for DEL {A51B25C2-B0DB-
48B2-9038-522DE9D5FB9B}
WGEN.RtrPhV WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.RtrA WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.RtrExtDC MV PTYP UUID of prototype for MV {29787E10-484F-4b22-
A7BF-1C669D3748E8}
WGEN.RtrExtAC MV PTYP UUID of prototype for MV {29787E10-484F-4b22-
A7BF-1C669D3748E8}
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 237 - 88/288/CDV
2 Table E-23 defines the mapping for a selection of data attributes in the IEC 61400-25-2 data
3 class WGEN. The selection of data attributes from data class [e.g. WGEN] shall map to a
4 DNP3 data set descriptor.
5 Table E-23 – Sample partial Data Class mapping
Specification
- - NAME “WGEN_Spd-PwrAt-PwrRt-StaA”
A7BF-1C669D3748E8}
WGEN.PwrAt WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.PwrRt WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
WGEN.StaA WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7-
437C-B6E8-8F0A0C56ABF5}
7 E.4.22 Role of the DNP Users Group
8 DNP3 is administered by an independent body called the DNP Users Group, a consortium of device
9 vendors and users of the protocol. A function of this users group is to voluntarily register DNP3 imple-
10 mentations and to serve as an unbiased mediator to develop DNP3 for various classes of devices (i.e.,
11 meter, regulator, relay, et al.). Vendors, prior to beginning any DNP3 implementation, may become a
12 member of the users group to identify what DNP3 developments already exist and which features
13 should be supported for their device. The users group embodies a number of users and vendors who
14 represent an experience base and market expertise that assures DNP3 developments are relevant to
15 the largest body of potential users.
16 DNP3 uses data set prototypes to specify the structure and ordering of data within an entire data set
17 or a portion of a data set. This document specifies data set prototypes for use in DNP3 data sets.
18 DNP3 uses namespaces to assign unique meaning to common names that could otherwise be con-
19 fused with the same name used elsewhere. The DNP3 Users Group accepts voluntary registration of
20 Namespaces submitted by any vendor or user. Once a namespace is registered, the vendor or user is
21 free to define, redefine or delete any data set prototype(s) within that namespace. Each data set proto-
22 type is assigned a UUID when it is defined or modified to uniquely identify it. Any user or vendor is free
23 to make use of data sets defined by data set prototypes in any namespace where they have knowl-
24 edge of those data set prototypes. This permits the creation of private data sets where required and
25 also permits definition of shared data sets for common usage, such as the data sets prototypes de-
26 scribed in this document.
27 E.5 Mapping of the Information Exchange Model to DNP3 services
28 The following services defined in 61400-25-3 shall be mapped to services defined in DNP3:
29 – Data model (GetDataValue, SetDataValue)

30 – Control model (Select, SelectWithValue, Operate, CommandTermination)
31 1) The mapping to DNP3 provides services for the process data (signal) exchange only.
32 2) It is the intent of this mapping to use the services of DNP3 as they are. No extensions of
33 the definitions provided by DNP3 are intended.
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 238 - 88/288/CDV
1 E.6 Protocol stack details
2 E.6.1 DNP3 DEVICE PROFILE DOCUMENT
3 Minimum implementation for compatibility with IEC 61400-25 shall have a profile as shown in
4 this section.
5
6 Vendor Name: INTERNATIONAL ELECTROTECHNICAL COMMISSION
7
8
9 Device Name: WIND TURBINE
10
11
12 Highest DNP Level Supported: Device Function:
13 For Requests Level 2  M aster √ Slave
14 For Responses Level 2

15
16
17 Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels
18 Supported (the complete list is described in the attached table):
19
20 Read and Write of Obj 85, Var 0 & 1 (Data Set Prototype)
21
22 Read and Write of Obj 86, Var 0, 1, 2 & 3 (Data Set Descriptor)
23
24 Read, Write, Select, Operate and Direct Operate of Obj 87, Var 1 (Static Data Set)
25
26 Read of Obj 88, Var 0 & 1 (Event Data Set)
27
28 Read of Obj 0, Var 254 & 255 (Device Attributes); Obj 50 Var 3 (Record Current Time)
29
30 Supports static data read requests containing qualifiers 00 & 01 (8 & 16-bit start/stop point in-
31 dexes)
32
33
Maximum Data Link Frame Size (octets): Maximum Application Fragment Size (octets):
Transmitted 292 Transmitted 2048
Received 292 Received 2048
Maximum-Data-Link Re-tries: Maximum Application Layer Re-tries:
√ None √ None
Fixed at Configurable
Configurable
34
35
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 239 - 88/288/CDV
1 Requires Data Link Layer Confirmation:

2 √ Never (recommended)
3 Always
4 Sometimes
5 Configurable ( acceptable if device chooses to use data link confirm for flow control )
6
7 Requires Application Layer Confirmation:
8 Never
9 Always
10 √ When reporting Event Data
11 √ When sending multi-fragment responses
12 Sometimes
13 Configurable
14 Timeouts while waiting for:

15 Data Link Confirm √ None Fixed at Variable Configurable
16 Complete Appl. Fragment None Fixed at Variable √ Configurable
17 Application Confirm None Fixed at Variable √ Configurable
18 Complete Appl. Response None Fixed at Variable √ Configurable
19
20 Others
21 Transmission Delay: No intentional delay
22 Need Time Delay: Configurable (default = 24hrs)
23 Select/Operate Arm Timeout: Configurable (default = 10 s)
24 Unsolicited response notification delay: Configurable
25 Unsolicited response retry delay: Configurable (may be dynamically determined)
26
27 Sends/Executes Control Operations:
28 WRITE Binary Outputs √ Never Always Sometimes Configurable
29 SELECT/OPERATE Never √ Always Sometimes Configurable
30 DIRECT OPERATE Never √ Always Sometimes Configurable
31 DIRECT OPERATE - NO ACK Never √ Always Sometimes Configurable
32
33 Count > 1 √ Never Always Sometimes Configurable
34 Pulse On Never Always Sometimes √ Configurable
35 Pulse Off √ Never Always Sometimes Configurable
36 Latch On Never Always Sometimes √ Configurable
37 Latch Off Never Always Sometimes √ Configurable
38
39 Queue √ Never Always Sometimes Configurable
40 Clear Queue √ Never Always Sometimes Configurable
41
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 240 - 88/288/CDV
1 ITEM FOR MASTER DEVICES ONLY:
2 Expects Binary Input Change Events:

3
4 Either time-tagged or non-time-tagged for a single event
5 Both time-tagged and non-time-tagged for a single event
6 Configurable (attach explanation)
7
8
9 ITEMS FOR SLAVE DEVICES ONLY:
10
11
12 Reports Binary Input Change Events when no Reports time-tagged Binary Input Change
13 specific variation requested: Events when no specific variation requested:
14 (Event Class Poll or Obj 2 Var 0 read) (Class Poll or Obj 2 Var 0 read)
15
16 Never Never
17 √ Only time-tagged √ Binary Input Change With Time
18 Only non-time-tagged √ Binary Input Change With Relative Time
19 Configurable to send both, one or the Configurable (attach explanation)
20 other (attach explanation)
21
22
23 Sends Unsolicited Responses: Sends Static Data in Unsolicited Responses:
24
25 Never √ Never
26 √ Configurable (attach explanation) When Device Restarts
27 Only certain objects When Status Flags Change
28 Sometimes (attach explanation)
29 No other options are permitted.
30 √ ENABLE/DISABLE UNSOLICITED
31 Function codes supported
32
33 Default Counter Object/Variation: Counters Roll Over at:
34
35 No Counters Reported No Counters Reported
36 Configurable (attach explanation) Configurable (attach explanation)
37 √ Default Object 16 Bits
38 Default Variation √ 32 Bits
39 √ Point-by-point list attached Other Value
40 Point-by-point list attached
41
42 Sends Multi-Fragment Responses: Yes No (device vendor specified option)
43
44
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 241 - 88/288/CDV
1
2 DNP3 Device Profile Document
3
4 INTEROPERABILITY TABLE - 1 of 1
5
6 (slave parses) (slave sends)
Object Object Object Name / Description Request Request Response Response
Group Varia- Func Qual (hex) Func Qual
tion Code Code (hex)
0 254 Request return of all attributes 1 00,01,06 129 5B

0 255 Request list of attributes 1 00,01,06 129 5B
50 1 Time and Date 1 07 (qty=1) 129 07 (qty=1)
2 07 (qty=1)
52 1 Time Delay Coarse 129 07 (qty=1)
52 2 Time Delay Fine 129 07 (qty=1)
60 1 Class 0 Data 1 06
60 2 Class 1 Data 1 06,07,08
20, 21 06
60 3 Class 2 Data 1 06,07,08
20, 21 06
60 4 Class 3 Data 1 06,07,08
20, 21 06
80 1 Internal Indications 2 00 in-
dex=7
85 0 Data Set Prototype - All Var 1 06 - -
85 1 Data Set Prototype – with UUID 1 00,01,06, 129 5B
17,28
85 1 Data Set Prototype – with UUID 2 5B 129 -
86 0 Data Set Descriptor – All Var 1 06 - -
86 0 Data Set Descriptor – Assign 22 00,01,06, - -
Class 17,28
86 1 Data Set Descriptor – Data Set 1 00,01,06, 129 5B
Contents 17,28
86 1 Data Set Descriptor – Data Set 2 5B 129 -
Contents
86 2 Data Set Descriptor – Character- 1 00,01,06, 129 00, 01, 17,
istics 17,28 28
86 3 Data Set Descriptor – Point In- 1 00,01,06, 129 5B
dex Attributes 17,28
86 3 Data Set Descriptor – Point In- 2 5B 129 -
dex Attributes
87 0 Static Data Set – All Var 1 06 - -
87 1 Static Data Set 1 00,01,06, 129 5B
17,28
87 1 Static Data Set 2 5B 129 -
87 1 Static Data Set 3 5B 129 5B
87 1 Static Data Set 6 5B 129 -
88 0 Event Data Set – All Var 1 06,07,08 - -
88 1 Event Data Set – Snapshot 1 06,07,08 129 5B
88 1 Event Data Set – Snapshot - - 130 5B
No Object Cold Restart 13

No Object Delay Measurement 23
7
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 242 - 88/288/CDV
1 Annex F
2 (normative)
3
4 Time synchronization
5 F.1 Introduction
6 Any implementation claiming conformance to this standard and declaring support for objects
7 containing an attribute of type TIMESTAMP shall use the SNTP protocol as a minimum in or-
8 der to guarantee the synchronism inside the wind power plant. The use of other more precise
9 synchronisation protocols is not within the scope of this standard.
10 In order to get the same interpretation of the TimeQuality attribute of the TIMESTAMP the fol-
11 lowing rules should apply:
12 - On the device start-up its ClockNotSynchronized flag shall be set to TRUE until the device
13 synchronises with an external SNTP server or another more precise synchronisation
14 source (for example GPS, PTP or IRIG-B).
15 - If there is no other more accurate external synchronism source and the SNTP server does
16 not reply to the synchronisation requests or the SNTP responses arrive with the LI indica-
17 tor indicating the TimeServer is not reliable, the ClockNotSynchronized flag shall be set
18 after an specific timeout defined by the vendor (PIXIT). This timeout depends on the pre-
19 cision of the internal clock and shall guarantee a specified maximum deviation (PIXIT).
20 - If the TimeStamp information cannot be considered valid due to, for example, a failure in
21 the internal clock, the ClockFailure flag shall be raised.
22 - A value TRUE for the TimeQuality attributes ClockNotSynchronized or ClockFailure, indi-

23 cating that the timestamp is invalid, shall remain set for all data objects containing the
24 TIMESTAMP attribute until the clock has been succesfully synchronized.
25 F.2 A-Profile
26 The A-Profile for Time Sync Services shall be as defined in 6.5.1 of IEC 61850-8-1.
27 F.3 T-Profile
28 The T-Profile for Time Sync Services shall be as defined in 6.5.2 of IEC 61850-8-1.
29
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 243 - 88/288/CDV
1 Annex G
2 (informative)
3
4 Interfaces – Implementation considerations
5 G.1 General
6 To give some guidance in the understanding of the standard, the following discussion of an
7 example is intended to show what the standard covers compared with a real system.
8 This standard does not constrain any implementation of the information, service models,
9 communication stacks, actions, and application program interfaces (APIs).
10 NOTE The example is not representative. Many other possible interfaces on both sides are possible.
11 G.2 Example interfaces of a real system
12 The information exchange between a wind power plant (WPP) device and supervisory and
13 control systems mainly comprises – according to Figure G-1 – a client, a server, several inter-
14 faces, and actions.
15 The server (WPP server) represents the information and information exchange models. The
16 client (WPP client) represents the complementary to the server. E.g., a service provided by
17 the server can be requested by the client. The client itself is not specified (it mainly provides
18 the complementary roles of the server).
19 The complete chain from a source of information up to a SCADA visualisation is described

20 (from right to left in the figure):
21 — The data value source is the real WPP. The exchange of data (raw) values between the
22 real WPP process and the WPP server is realised by the interface 1 (IF1) and (IF2) –
23 these interfaces are implementation specific. How many interfaces are implemented at the
24 server side is implementation specific.
25 — The WPP server adds useful information to the (raw) process data (e.g., hierarchical
26 name, time stamp, quality, ...). This is defined in the model and the addition of the name
27 etc. is defined as the action 1 (Act1) – this action is implementation specific.
28 — The model of the information (as it is seen from the network point of view) is defined by
29 the standard – the model realisation is implementation specific.
30 — Monitoring of value changes of process data values delivered from the real-time data
31 source is represented by (Act1) – implementation specific, but behaviour and services de-
32 fined in the standard.
33 — Exchange of data values between WPP server and supervisory and control systems via
34 (IF3) – behaviour and services defined in the standard.
35 — Exchange of the model description located in the server with another system (IF3) – be-
36 haviour and services defined in the standard.
37 — Exchange of data values between (communication) client and client application (visualisa-
38 tion, HMI) via (IF4) and (Act2) – implementation specific
39
Version 61400-25-4_R1-0_2CDV_2006-11-16
2CDV for 61400-25-4 © IEC:2007 - 244 - 88/288/CDV
DLL RS 232
e.g., visualize at HMI
Model/
Act2 behavior Act1
SCADA IF3 WPP Server, Wind Real

Visualization WPP Client WPP device model, Power Plant WPP
HMI Services data values
TCP/IP
Network
Scope
IF4 IF2 IF1
1
2
3 Figure G-1 – Implementation issues (example)
4 Interface (IF3) is the only interface that is defined by this standard. This interface (IF3) is de-
5 fined by the information that is accessible through this interface and by the messages that
6 carry the service parameters and the values.
7 All (application program) interfaces (APIs) are outside the scope of this standard.
Version 61400-25-4_R1-0_2CDV_2006-11-16

383-0-1 2006-0045 Projektnr IEC 61400 25 4 Ed 1 0

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

383-0-1 2006-0045 Projektnr IEC 61400 25 4 Ed 1 0

Hochgeladen von

Copyright:

Verfügbare Formate

DKE Deutsche Kommission

Elektrotechnik Elektronik Informationstechnik

VDE – DKE · Stresemannallee 15 · 60596 Frankfurt am Main

Frankfurt am Main 2006-12-05

Sehr geehrte Damen und Herren,

Verteiler K 383 Windenergieanlagen (Stand: 2006-12-05)

Erläuterung der Kennziffern:

Verteiler AK 383.0.1 Kommunikation für Windenergieanlagen (Stand: 2006-12-05)

Project number IEC 61400-25-4 Ed.1

Copyright © 2006 International Electrotechnical Commission, IEC. All rights reserved. It is

FORM CDV (IEC) 2005-09-23

1 Annex B (normative) Specific communication service mapping – Mapping to OPC

1 D.1.1 Introduction ........................................................................................ - 173 -

1 E.4.14 CDC Binary Counter Reading (BCR)................................................... - 232 -

23 Figure 1 – Conceptual communication model of IEC 61400-25......................................... - 15 -

27 Figure A-1– Mapping architecture (conceptual) ................................................................ - 27 -

1 Table A-11 – ReleaseResponse ....................................................................................... - 42 -

1 Table A-54 – ReportRequest............................................................................................ - 68 -

1 Table D-4– Logical node mapping .................................................................................. - 179 -

1 Table D-45 – Data services mapping ............................................................................. - 197 -

2 INTERNATIONAL ELECTROTECHNICAL COMMISSION

17 1) wind power plant information model,

4 – data access and retrieval

Communication model of IEC 61400-25

Wind power plant Wind power plant

20 Figure 1 – Conceptual communication model of IEC 61400-25

1 3 Terms and definitions

ACSI Abstract Communication Service Interface (defined for example in 61850-7-2)

24 Annex F provides a description of the time synchronization requirements to be implemented in

2 5.1 Mapping to protocol stacks.

8 Figure 2 – Communication profiles

10 5.2 Services of IEC 61400-25-3 mapped to protocol stacks

11 In Table 1 below is provided an overview of the information exchange services specified in

2 Table 1 – Mapping overview of IEC 61400-25-3 services

Mapping capability overview

13 This annex includes the clauses as follows:

14 Clause A.1 provides an general introduction of the mapping to WebServices.

16 Clause A.3 provides a list of abbreviated terms used in annex A.

17 Clause A.4 provides mapping of the information model to WebServices.

18 Clause A.5 provides mapping of the information exchange model to WebServices.

19 Clause A.6 provides the protocol stack details.

33 A.1.3 The mapping architecture

34 The mapping architecture consists of 3 parts:

35 1. Mapping of the information model

1 2. Mapping of the data classes

2 3. Mapping of the information exchange services

18 Figure A-1– Mapping architecture (conceptual)

2 A.2 Specific normative references for Web Services

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

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

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

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

22 ISO 639-2 Codes for the representation of names of languages

23 RFC 791 Internet Protocol specification (IP)

24 RFC 792 Internet Control Message Protocol (ICMP)

25 RFC 793 Transmission Control Protocol (TCP)

26 RFC 826 Ethernet Address Resolution Protocol

27 RFC 919 Broadcasting internet datagrams

28 RFC 922 Broadcasting internet datagrams in presence of subnets

29 RFC 950 Internet Standard Subnetting Procedure

30 RFC 1112 Host Extensions for IP Multicasting

31 RFC 2616 Hypertext Transfer Protocol - HTTP/1.1

32 RFC 2617 Upgrading to TLS Within HTTP/1.1