Bsi bs en 61400 25 4 2008

BS EN 61400-25-4: 2008 BSI British Standards Wind turbines — Part 25-4: Communications for monitoring and control of wind power plants — Mapping to communication profile NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW raising standards worldwide™ BRITISH STANDARD BS EN 61400-25-4:2008 National foreword This British Standard is the UK implementation of EN 61400-25-4:2008 It is identical to IEC 61400-25-4:2008 The UK participation in its preparation was entrusted to Technical Committee PEL/88, Wind turbines A list of organizations represented on this committee can be obtained on request to its secretary This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application © BSI 2009 ISBN 978 580 55687 ICS 27.180 Compliance with a British Standard cannot confer immunity from legal obligations This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2009 Amendments issued since publication Amd No Date Text affected EUROPEAN STANDARD EN 61400-25-4 NORME EUROPÉENNE October 2008 EUROPÄISCHE NORM ICS 27.180 English version Wind turbines Part 25-4: Communications for monitoring and control of wind power plants Mapping to communication profile (IEC 61400-25-4:2008) Eoliennes Partie 25-4: Communications pour la surveillance et la commande des centrales éoliennes Mapping des profils de communication (CEI 61400-25-4:2008) Windenergieanlagen Teil 25-4: Kommunikation für die Überwachung und Steuerung von Windenergieanlagen Abbildung auf ein Kommunikationsprofil (IEC 61400-25-4:2008) This European Standard was approved by CENELEC on 2008-10-01 CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member This European Standard exists in three official versions (English, French, German) A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels © 2008 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members Ref No EN 61400-25-4:2008 E EN 61400-25-4:2008 -2- Foreword The text of document 88/318/FDIS, future edition of IEC 61400-25-4, prepared by IEC TC 88, Wind turbines, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61400-25-4 on 2008-10-01 For the user’s convenience, a file containing the text of Clause A.7 is included with this document The following dates were fixed: – latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2009-07-01 – latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2011-10-01 Annex ZA has been added by CENELEC Endorsement notice The text of the International Standard IEC 61400-25-4:2008 was approved by CENELEC as a European Standard without any modification -3- EN 61400-25-4:2008 Annex ZA (normative) Normative references to international publications with their corresponding European publications The following referenced documents are indispensable for the application of this document For dated references, only the edition cited applies For undated references, the latest edition of the referenced document (including any amendments) applies NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies Publication Year Title EN/HD Year IEC 60870-5-104 2006 Telecontrol equipment and systems Part 5-104: Transmission protocols Network access for IEC 60870-5-101 using standard transport profiles EN 60870-5-104 2006 IEC 61400-25 Series Wind turbines Part 25: Communications for monitoring and control of wind power plants EN 61400-25 Series IEC 61850-7-2 2003 Communication networks and systems in substations Part 7-2: Basic communication structure for substation and feeder equipment Abstract communication service interface (ACSI) EN 61850-7-2 2003 IEC 61850-7-3 2003 Communication networks and systems in substations Part 7-3: Basic communication structure for substation and feeder equipment Common data classes EN 61850-7-3 2003 IEC 61850-8-1 2004 Communication networks and systems in substations Part 8-1: Specific Communication Service Mapping (SCSM) - Mappings to MMS (ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3 EN 61850-8-1 2004 DNP3 Specification 2007 Volume - Volume - - ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ –2– BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) CONTENTS INTRODUCTION 10 Scope 11 Normative references 12 Terms and definitions 13 Abbreviated terms 17 General overview 18 Annex A (normative) Specific communication service mapping – Definition and mapping to Web Services 21 Annex B (normative) Specific communication service mapping – Mapping to OPC XML-DA 127 Annex C (normative) Specific communication service mapping – Mapping to ISO 9506 specified in IEC 61850-8-1 175 Annex D (normative) Specific communication service mapping – Mapping to IEC 60870-5-104 specified in IEC/TS 61850-80-1 185 Annex E (normative) Specific communication service mapping – Mapping to DNP3 213 Annex F (normative) Time synchronization 236 Annex G (informative) Interfaces – Implementation considerations 237 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Figure – Conceptual communication model of IEC 61400-25 series 12 Figure – Communication profiles 19 Figure A.1 – Mapping architecture (conceptual) 22 Figure A.2 – Naming structure applied in the IEC 61400-25 series (conceptual) 27 Figure A.3 – Client behavior in the reporting service (conceptual) 56 Figure A.4 – Server behavior in the reporting service (conceptual) 57 Figure A.5 – Reporting Services mechanism (conceptual) 58 Figure B.1 – Mapping architecture (conceptual) 128 Figure B.2 – Differences between OPC XML-DA and IEC Information Model timestamp 136 Figure B.3 – Sequence of services to establish an association 141 Figure B.4 – CreateDataSet sequence of services 157 Figure C.1 – Mapping architecture (conceptual) 176 Figure D.1 – Mapping architecture (conceptual) 187 Figure D.2 – Direct Control with Normal Security with status update – positive case 202 Figure D.3 – Direct Control with Normal Security in general – negative case a) 202 Figure D.4 – Direct Control with Normal Security in general – negative case b) 203 Figure D.5 – Direct Control with Normal Security with status update – negative case c) 204 Figure D.6 – Direct Control with Normal Security without status update – positive case 204 Figure D.7 – Direct Control with Enhanced Security – positive case 205 Figure D.8 – Direct Control with Enhanced Security – negative case c) 206 Figure D.9 – Direct Control with Enhanced Security – negative case d) 206 Figure D.10 – SBOw control – positive case 207 Figure D.11 – SBOw control – negative case a) 208 BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) –3– Figure D.12 – SBOw control – negative case b) 208 Figure D.13 – SBOw control – negative case c) 209 Figure D.14 – SBO with Enhanced Security – positive case 210 Figure D.15 – SBO with Enhanced Security – negative case a) 210 Figure D.16 – SBO with Enhanced Security – negative case b) 211 Figure E.1 – Mapping architecture (conceptual) 214 Figure G.1 – Implementation issues (example) 238 Table – Mapping overview of IEC 61400-25-3 services 20 Table A.1 – Web Services mapping overview of IEC 61400-25 IM and IEM 22 Table A.2 – Mapping the IEC 61400-25 IM to Web Services 25 Table A.3 – Mapping of IEC 61400-25 data attribute basic types 26 Table A.4 – XML schema for wind power information model 29 Table A.5 – Server class services mapped to Web Services 34 Table A.6 – GetServerDirectoryRequest 35 Table A.7 – GetServerDirectoryResponse 35 Table A.8 – AssociateRequest 37 Table A.9 – AssociateResponse 38 Table A.10 – ReleaseRequest 39 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Table A.11 – ReleaseResponse 39 Table A.12 – AbortRequest 40 Table A.13 – AbortResponse 40 Table A.14 – LOGICAL-DEVICE service mapping 41 Table A.15 – GetLogicalDeviceDirectoryRequest 41 Table A.16 – GetLogicalDeviceDirectoryResponse 42 Table A.17 – LOGICAL-NODE mapping 42 Table A.18 – GetLogicalNodeDirectoryRequest 43 Table A.19 – GetLogicalNodeDirectoryResponse 43 Table A.20 – Data mapping 44 Table A.21 – GetDataValuesRequest 44 Table A.22 – GetDataValuesResponse 45 Table A.23 – SetDataValuesRequest 45 Table A.24 – SetDataValuesResponse 46 Table A.25 – GetDataDirectoryRequest 47 Table A.26 – GetDataDirectoryResponse 47 Table A.27 – GetDataDefinitionRequest 48 Table A.28 – GetDataDefinitionResponse 49 Table A.29 – DATA-SET mapping 49 Table A.30 – GetDataSetValuesRequest 50 Table A.31 – GetDataSetValuesResponse 50 Table A.32 – SetDataSetValuesRequest 51 Table A.33 – SetDataSetValuesResponse 51 Table A.34 – CreateDataSetRequest 52 –4– BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) Table A.35 – CreateDataSetResponse 52 Table A.36 – DeleteDataSetRequest 53 Table A.37 – DeleteDataSetResponse 54 Table A.38 – GetDataSetDirectoryRequest 54 Table A.39 – GetDataSetDirectoryResponse 55 Table A.40 – Report control block services mapping 55 Table A.41 – AddSubscriptionRequest 59 Table A.42 – AddSubscriptionResponse 60 Table A.43 – RemoveSubscriptionRequest 61 Table A.44 – RemoveSubscriptionResponse 61 Table A.45 – ReportFormat 62 Table A.46 – GetBRCBValuesRequest 63 Table A.47 – GetBRCBValuesResponse 64 Table A.48 – SetBRCBValuesRequest 66 Table A.49 – SetBRCBValuesResponse 67 Table A.50 – GetURCBValuesRequest 68 Table A.51 – GetURCBValuesResponse 68 Table A.52 – SetURCBValuesRequest 70 Table A.53 – SetURCBValuesResponse 71 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Table A.54 – ReportRequest 71 Table A.55 – ReportResponse 72 Table A.56 – LOG-CONTROL-BLOCK services mapping 73 Table A.57 – GetLCBValuesRequest 73 Table A.58 – GetLCBValuesResponse 74 Table A.59 – SetLCBValuesRequest 75 Table A.60 – SetLCBValuesResponse 75 Table A.61 – Log class services mapping 76 Table A.62 – GetLogStatusValuesRequest 76 Table A.63 – GetLogStatusValuesResponse 77 Table A.64 – QueryLogByTimeRequest 78 Table A.65 – QueryLogByTimeResponse 79 Table A.66 – QueryLogAfterRequest 79 Table A.67 – QueryLogAfterResponse 80 Table A.68 – Control class services mapping 81 Table A.69 – SelectRequest 81 Table A.70 – SelectResponse 82 Table A.71 – SelectWithValueRequest 83 Table A.72 – SelectWithValueResponse 83 Table A.73 – CancelRequest 85 Table A.74 – CancelResponse 85 Table A.75 – OperateRequest 87 Table A.76 – OperateResponse 87 Table A.77 – CommandTerminationRequest 89 BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) –5– Table A.78 – CommandTerminationResponse 89 Table A.79 – TimeActivatedOperateRequest 91 Table A.80 – TimeActivatedOperateResponse 91 Table A.81 – Protocol stack selections 93 Table B.1 – Mapping of IEC 61400-25-3 IEM service into OPC XML-DA services 128 Table B.2 – Mapping of IEC 61400-25-2 IM classes to OPC XML-DA 130 Table B.3 – Server class attributes 131 Table B.4 – Logical Device Class attributes 132 Table B.5 – Logical Node Class attributes 132 Table B.6 – Data Class attributes 133 Table B.7 – DataAttributeType (DAType) Class attributes 133 Table B.8 – Mapping of the attribute BasicType 134 Table B.9 – New OPC XML-DA Error codes 135 Table B.10 – Timestamp mapping 136 Table B.11 – Mapping of the Quality attribute 136 Table B.12 – Cookie parameter explanation 140 Table B.13 – IEM GetServerDirectory mapping 142 Table B.14 – IEM GetServerDirectory mapping detailed 143 Table B.15 – IEM GetLogicalDeviceDirectory mapping 144 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Table B.16 – IEM GetLogicalDeviceDirectory mapping detailed 144 Table B.17 – GetLogicalDeviceDirectory negative response mapping to IEM ServiceError 145 Table B.18 – IEM GetLogicalNodeDirectory mapping 146 Table B.19 – IEM GetLogicalNodeDirectory mapping detailed 146 Table B.20 – GetLogicalNodeDirectory negative response mapping to IEM ServiceError 147 Table B.21 – IEM GetDataValues mapping 148 Table B.22 – IEM GetDataValues mapping detailed 149 Table B.23 – GetDataValues negative response mapping to IEM ServiceError 150 Table B.25 – IEM SetDataValues mapping detailed 151 Table B.26 – SetDataValues negative response mapping to IEM ServiceError 153 Table B.27 – IEM GetDataDirectory mapping 153 Table B.28 – IEM GetDataDirectory mapping detailed 154 Table B.29 – GetDataDirectory negative response mapping to IEM ServiceError 155 Table B.30 – Mapping of CreateDataSet service parameters 157 Table B.31 – CreateDataSet negative response mapping to IEM ServiceError 157 Table B.32 – GetDataSetValues negative response mapping to IEM ServiceError 158 Table B.33 – SetDataSetValues negative response mapping to IEM ServiceError 158 Table B.34 – OPC Subscription attributes’ constrained value 159 Table B.35 – AddSubscription service parameter constraints 160 Table B.36 – Mapping of AddSubscription service parameters 160 Table B.37 – AddSubscription negative response mapping to IEM ServiceError 162 Table B.38 – Mapping of RemoveSubscription service parameters 162 Table B.39 – Fault mapping to IEM ServiceError 163 –6– BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) Table B.40 – Report service parameters 163 Table B.41 – Mapping of Report service parameters 163 Table B.42 – Control models supported in this mapping 164 Table B.43 – Control services supported 164 Table B.44 – Control model writable custom item properties 165 Table B.45 – AddCause mapping to OPC Error Code 166 Table B.46 – Select request service mapping 167 Table B.47 – SelectWithValue service parameter mapping 167 Table B.48 – Cancel service parameter mapping 168 Table B.49 – Cancel negative response mapping to IEM ServiceError 169 Table B.50 – Operate service parameter mapping 169 Table B.51 – Operate negative response mapping to IEM ServiceError 170 Table B.52 – TimeActivatedOperate service parameter mapping 171 Table B.53 – TimeActivatedOperate negative response mapping to IEM ServiceError 172 Table B.54 – CommandTermination + service parameter mapping 173 Table B.55 – CommandTermination – service parameter mapping 173 Table B.56 – Protocol stack details 174 Table C.1 – Mapping of IEC 61400-25-3 IEM onto ISO 9506 according to IEC 61850-8-1 176 Table C.2 – Mapping of AddSubscribtion service (Step 1) 179 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Table C.3 – Mapping of AddSubscribtion service (Step 2) 180 Table C.4 – Mapping of AddSubscribtion service (Step 3) 180 Table C.5 – AddSubscription Negative response 181 Table C.6 – Mapping of RemoveSubscribtion service – First MMS service 181 Table C.7 – Mapping of RemoveSubscribtion service – second MMS service 182 Table C.8 – RemoveSubscription Negative response 182 Table C.9 – QueryLogByTime mapping 183 Table C.10 – QueryLogAfter mapping 183 Table C.11 – Service and protocols for client/server communication A-Profile 183 Table C.12 – Service and protocols for client/server TCP/IP T-Profile 184 Table D.1 – Services Mapping overview of IEC 61400-25 IM and IEM 187 Table D.2 – Example for mapping of LD and LN to CASDU and IOA 191 Table D.3 – Logical device mapping 192 Table D.4 – Logical node mapping 192 Table D.5 – CDCs defined in IEC 61400-25-2 193 Table D.6 – CDC: Status Value, STV class 194 Table D.7 – CDC: Setpoint Value, SPV class 194 Table D.8 – CDC: Alarm, ALM class 194 Table D.9 – CDC: Command CMD class 195 Table D.10 – CDC: Event Counting, CTE class 195 Table D.11 – CDC: State Timing, TMS class 195 Table D.12 – Mapping structure basic CDC 196 Table D.13 – CDC: Controllable Analog set point, APC class 197 BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 226 – Attribute Name Attribute Type DNP3 Data Specification DNP3 Data Element Mapping res.cVal.ang AnalogueValue DAEL:FLT32 32-bit floating point value q (note 2) Quality DAEL:BSTR SQ2 – Object coding (refer to Table E.2) t (note 1) TimeStamp DAEL:TIME Six octet binary time – Time of occurrence The ancillary value associated with each DNP3 data element shall be the IEC 61850-7-3 Attribute Name e.g “phsA.cVal.mag” The DNP3 mapping shall map one “t” attribute value onto a single DNP3 timestamp The DNP3 mapping shall map all individual “q” attribute values by ORing onto a single DNP3 bitstring except for the validity flag which will be set off line if any individual “q” attribute is off line E.4.17 CDC Phase to phase related measured value of a three phase system (DEL) Table E.17 defines the mapping for data attributes in the IEC 61850-7-3 common data class DEL The data attributes [(phsAB | phsBC | phsCA) + t + q] shall map to a DNP3 data set prototype Table E.17 – CDC: Phase to phase (DEL) mapping Attribute Name Attribute Type DNP3 Data Specification DNP3 Data Element Mapping - - 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 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 to Table E.2) t (note 1) TimeStamp DAEL:TIME Six octet binary time – Time of occurrence The ancillary value associated with each DNP3 data element shall be the IEC 61850-7-3 Attribute Name e.g “phsAB.cVal.mag” The DNP3 mapping shall map one “t” attribute value onto a single DNP3 timestamp The DNP3 mapping shall map all individual “q” attribute values by ORing onto a single DNP3 bitstring except for the validity flag which will be set off line if any individual “q” attribute is off line E.4.18 CDC Device Name Plate (WDPL) Table E.18 defines the mapping for data attributes in the IEC 61400-25-2 common data class WDPL The data attributes [vendor + tmOffset + tmUseDT + tmDT] shall map to a DNP3 data set prototype BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 227 – Table E.18 – CDC: Device Name Plate (WDPL) mapping Attribute Name Attribute Type DNP3 Data Specification DNP3 Data Element Mapping - - 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] Status = BS1 [0] } tmDT BOOLEAN DAEL:BSTR FLAG ={ BS8 [0 7] Status = BS1 [0] } The ancillary value associated with each DNP3 data element shall be the IEC 61400-25-2 Attribute Name e.g “vendor” E.4.19 CDC Logical Node Name Plate (LPL) Table E.19 defines the mapping for data attributes in the IEC 61850-7-3 common data class LPL The data attributes [vendor + swRev + d] shall map to a DNP3 data set prototype Table E.19 – CDC: Logical Node Name Plate (LPL) mapping Attribute Name Attribute Type DNP3 Data Specification DNP3 Data Element Mapping - - UUID:OSTR {8FA4508F-1547-476F-829D.B3FCB35CA427} - - NSPC:VSTR “IEC 61400-25-2” - - NAME:VSTR “LPL” vendor VISIBLE STRING255 DAEL:VSTR 255 characters swRev VISIBLE STRING255 DAEL:VSTR 255 characters d VISIBLE STRING255 DAEL:VSTR 255 characters The ancillary value associated with each DNP3 data element shall be the IEC 61850-7-3 Attribute Name eg “vendor” E.4.20 CDC Alarm Set Status (ASS) Table E.20 defines the mapping for data attributes in the IEC 61400-25-2 common data class ASS The data attributes [(ARRAY of stVal) + t + q] shall map to a DNP3 data set prototype Table E.20 – CDC: Alarm Set Status (ASS) mapping Attribute Name Attribute Type DNP3 Data Specification DNP3 Data Element Mapping - - UUID:OSTR - - NSPC:VSTR (see E.4.22) - - NAME:VSTR “ASS” CODED ENUM DAEL:BSTR FLAG ={ BS8 [0 7] Status = BS1 [1 0] } BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 228 – Attribute Name stVal[1] Attribute Type CODED ENUM DNP3 Data Specification DAEL:BSTR DNP3 Data Element Mapping FLAG ={ BS8 [0 7] Status = BS1 [1 0] } stVal[2] CODED ENUM DAEL:BSTR FLAG ={ BS8 [0 7] Status = BS1 [1 0] } stVal[n] DAEL:BSTR CODED ENUM FLAG ={ BS8 [0 7] Status = BS1 [1 0] } q Quality DAEL:BSTR SQ2 – Object coding (refer Table E.2) t TimeStamp DAEL:TIME Six octet binary time – Time of occurrence The ancillary value associated with each DNP3 data element shall be the IEC 61400-25-2 Attribute Name eg “stVal[0]” NOTE As the number of elements in the alarm status array is implementation-dependent, vendors mapping this common data class to a DNP3 data set prototype should register a namespace with the DNP Users Group The implemented data set prototype may then be defined within that namespace and a UUID obtained for the implemented data set as described in E.4.22 The namespace and value of UUID so obtained is used for the NSPC and UUID shown in Table E.20 E.4.21 Relationship of Data Class Attributes and Data Set Descriptors IEC 61400-25-2 specifies data class attributes related to wind power plant applications Either data class or data class attributes in IEC 61400-25-2 shall be mapped to specific data set descriptors in DNP3 Mapping shall be applied in the outstation (server-side) Table E.21 defines the mapping for data attributes in the IEC 61400-25-2 data class attribute WGEN.Spd The data class attribute [e.g WGEN.Spd] shall map to a DNP3 data set descriptor Table E.21 – Sample Data Class Attribute mapping Attribute Name WGEN.Spd Attribute Type DNP3 Data Specification DNP3 Data Element Mapping - NAME “WGEN_Spd” MV PTYP UUID of prototype for MV {29787E10-484F-4B22A7BF-1C669D3748E8} Table E.22 defines the mapping for data attributes in the IEC 61400-25-2 data class WGEN The data class [e.g WGEN] shall map to a DNP3 data set descriptor Table E.22 – Sample Data Class mapping Attribute Name - Attribute Type DNP3 Data Specification DNP3 Data Element Mapping - NAME “WGEN” WGEN.OpTmRs TMS PTYP UUID of prototype for TMS {FE568612-85744B85-999F-21E14C7977B4} WGEN.GnOpMod STV PTYP UUID of prototype for STV {36798E8E-2138477D.868E-A5B6ADFA0410} WGEN.ClSt STV PTYP UUID of prototype for STV {36798E8E-2138477D.868E-A5B6ADFA0410} BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) Attribute Name – 229 – Attribute Type DNP3 Data Specification DNP3 Data Element Mapping WGEN.Spd MV PTYP UUID of prototype for MV {29787E10-484F-4B22A7BF-1C669D3748E8} WGEN.W WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.VAr WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.GnTmpSta MV PTYP UUID of prototype for MV {29787E10-484F-4B22A7BF-1C669D3748E8} WGEN.GnTmpRtr MV PTYP UUID of prototype for MV {29787E10-484F-4B22A7BF-1C669D3748E8} WGEN.GnTmpInlet MV PTYP UUID of prototype for MV {29787E10-484F-4B22A7BF-1C669D3748E8} WGEN.StaPPV DEL PTYP UUID of prototype for DEL {A51B25C2B0DB.48B2-9038-522DE9D5FB9B} WGEN.StaPhV WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.StaA WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.RtrPPV DEL PTYP UUID of prototype for DEL {A51B25C2B0DB.48B2-9038-522DE9D5FB9B} WGEN.RtrPhV WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.RtrA WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.RtrExtDC MV PTYP UUID of prototype for MV {29787E10-484F-4b22A7BF-1C669D3748E8} WGEN.RtrExtAC MV PTYP UUID of prototype for MV {29787E10-484F-4b22A7BF-1C669D3748E8} Table E.23 defines the mapping for a selection of data attributes in the IEC 61400-25-2 data class WGEN The selection of data attributes from data class [e.g WGEN] shall map to a DNP3 data set descriptor Table E.23 – Sample partial Data Class mapping Attribute Name - Attribute Type DNP3 Data Specification DNP3 Data Element Mapping - NAME “WGEN_SpD.PwrAt-PwrRt-StaA” WGEN.Spd MV PTYP UUID of prototype for MV {29787E10-484F-4B22A7BF-1C669D3748E8} WGEN.PwrAt WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.PwrRt WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} WGEN.StaA WYE PTYP UUID of prototype for WYE {FCB770FF-0CA7437C-B6E8-8F0A0C56ABF5} E.4.22 Role of the DNP Users Group DNP3 is administered by an independent body called the DNP Users Group, a consortium of device vendors and users of the protocol A function of this users group is to voluntarily register DNP3 implementations and to serve as an unbiased mediator to develop DNP3 for various classes of devices (i.e., meter, regulator, relay, etc.) Vendors, prior to beginning any DNP3 implementation, may become a member of the users group to identify what DNP3 developments already exist and which features should be supported for their device The – 230 – BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) users group embodies a number of users and vendors who represent an experience base and market expertise that assures DNP3 developments are relevant to the largest body of potential users DNP3 uses data set prototypes to specify the structure and ordering of data within an entire data set or a portion of a data set This part of IEC 61400-25 specifies data set prototypes for use in DNP3 data sets DNP3 uses namespaces to assign unique meaning to common names that could otherwise be confused with the same name used elsewhere The DNP3 Users Group accepts voluntary registration of Namespaces submitted by any vendor or user Once a namespace is registered, the vendor or user is free to define, redefine or delete any data set prototype(s) within that namespace Each data set prototype is assigned a UUID when it is defined or modified to uniquely identify it Any user or vendor is free to make use of data sets defined by data set prototypes in any namespace where they have knowledge of those data set prototypes This permits the creation of private data sets where required and also permits definition of shared data sets for common usage, such as the data sets prototypes described in this part of IEC 61400-25 E.5 Mapping of the Information Exchange Model to DNP3 services The following services defined in 61400-25-3 shall be mapped to services defined in DNP3: – Data model (GetDataValue, SetDataValue) – Control model (Select, SelectWithValue, Operate, CommandTermination) The mapping to DNP3 provides services for the process data (signal) exchange only It is the intent of this mapping to use the services of DNP3 as they are No extensions of the definitions provided by DNP3 are intended E.6 Protocol stack details E.6.1 DNP3 DEVICE PROFILE DOCUMENT Minimum implementation for compatibility with IEC 61400-25 shall have a device profile that permits the selections shown in this clause and Table E.6.1 Compatible devices may support any other options in addition to the selections listed here BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 231 – 1.1 DEVICE IDENTIFICATION Capabilities 1.1.7 DNP Levels Supported for: Masters Only shall include at least: Requests Responses ; ; Level Indicate each DNP3 Level to which the device conforms fully For Masters, requests and responses can be indicated independently 1.1.8 Supported Function Blocks: Shall include: ; Object – attribute objects ; Data Sets Notable Additions: Supports static data read requests containing qualifiers 00 & 01 (8 & 16-bit start/stop point indexes) 1.1.9 A brief description intended to quickly identify for the reader the most obvious features the device supports in addition to the Highest DNP Level Supported The complete list of features is described in the Implementation Table 1.4 LINK LAYER 1.4.5 Sends Confirmed User Data Frames: A list of conditions under which the device transmits confirmed link layer services (TEST_LINK_STATES, RESET_LINK_STATES, CONFIRMED_USER_DATA) 1.4.6 Outstations Only Requests and Responses shall include at least: ; Level Data Link Layer Confirmation Timeout: Capabilities Fixed at or configurable to never send confirmed user data frames Fixed at or configurable to be None This timeout applies to any secondary data link message that requires a confirm or response (link reset, link status, user data, etc) 1.4.7 Maximum Data Link Retries: Fixed at or configurable to include Never Retries The number of times the device will retransmit a frame that requests Link Layer confirmation 1.4.8 Maximum number of octets Transmitted in a Data Link Frame: Fixed at or configurable to include 292 This number includes the CRCs With a length field of 255, the maximum size would be 292 1.4.9 Maximum number of octets that can be Received in a Data Link Frame: Fixed at or configurable to include 292 This number includes the CRCs With a length field of 255, the maximum size would be 292 The device must be able to receive 292 octets to be compliant 1.5 APPLICATION LAYER Capabilities _ For item 1.1.8, Object and Data Sets are only required if the optional data set mapping is supported – 232 – 1.5 APPLICATION LAYER 1.5.1 Maximum number of octets Transmitted in an Application Layer Fragment other than File Transfer: BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) Capabilities For Masters: Fixed at or configurable to be 249 For Outstations: Fixed at or configurable to be 2048 This size does not include any transport or frame octets • Masters must provide a setting less than or equal to 249 • Outstations must provide a setting less than or equal to 2048 1.5.3 Maximum number of octets that can be Received in an Application Layer Fragment: For Masters: Fixed at or configurable to be 2048 For Outstations: Fixed at or configurable to be 249 This size does not include any transport or frame octets • Masters must provide a setting greater than or equal to 2048 • Outstations must provide a setting greater than or equal to 249 1.5.4 Timeout waiting for Complete Application Layer Fragment: Configurable Timeout if all frames of a message fragment are not received in the specified time Measured from time first frame of a fragment is received until the last frame is received 1.6 FILL OUT THE FOLLOWING ITEMS FOR MASTERS ONLY 1.6.1 Timeout waiting for Complete Application Layer Response(ms): Capabilities Configurable Timeout on Master if all fragments of a response message are not received in the specified time 1.6.2 Maximum Application Layer Retries for Request Messages: Fixed at or configurable to be None The number of times a Master will retransmit an application layer request message if a response is not received This parameter must never cause a Master to retransmit control or time sync messages Outstations should never transmit retries 1.7 FILL OUT THE FOLLOWING ITEMS FOR OUTSTATIONS ONLY 1.7.1 Timeout waiting for Application Confirm of solicited response message: Capabilities Configurable BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) 1.7 FILL OUT THE FOLLOWING ITEMS FOR OUTSTATIONS ONLY 1.7.2 How often is time synchronization required from the master? 1.8 OUTSTATION UNSOLICITED RESPONSE SUPPORT 1.8.1 Supports Unsolicited Reporting: – 233 – Capabilities Configurable (default = 24 hours) Capabilities ; Configurable, selectable from On and Off When the unsolicited response mode is configured “off”, the device shall behave exactly like an equivalent device that has no support for unsolicited responses If set to On, the Outstation will send a null Unsolicited Response after it restarts, then wait for an Enable Unsolicited Response command from the master before sending additional Unsolicited Responses containing event data 1.8.3 Unsolicited Response Confirmation Timeout: Configurable This is the amount of time that the outstation will wait for an Application Layer confirmation back from the master indicating that the master received the unsolicited response message As a minimum, the range of configurable values must include times from one second to one minute This parameter may be the same one that is used for normal, solicited, application confirmation timeouts, or it may be a separate parameter 1.9 OUTSTATION UNSOLICITED RESPONSE TRIGGER CONDITIONS 1.9.8 Hold time after event assigned to any class: Capabilities Configurable A configured value of indicates that responses are not delayed due to this parameter 3.1 3.1.2 3.3 3.3.9 SINGLE BIT BINARY INPUT Event Variation reported when variation requested: BINARY OUTPUT STATUS AND CONTROL RELAY OUTPUT BLOCK Maximum Time between Select and Operate: Capabilities ; Variation – with absolute time ; Variation – with relative time Capabilities Configurable (default = 10 seconds) BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 234 – Default Class Assigned to Events (1, 2, or none) 3.4 3.4.9 Close Configurable Cancel Currently Running Operation Trip Configurable Never Latch Off Configurable Counters Roll Over at: Count > Latch On Configurable COUNTERS/FROZEN COUNTERS Never Pulse Off Never Direct Operate – No Ack Always Pulse On Direct Operate Always Point Index Name Configurable Select/Operate Always Supported Control Operations Name for State when value is Name for State when value is Description Change Command Capabilities ; 32 Bits (4 294 967 295) BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 235 – DNP3 Device Profile Document Table E.6.1 – Interoperability DNP Object Group & Description Group Num Var Num Description Device Attributes — Non-specific all attributes request Device Attributes — List of attribute variations Time and Date — Absolute time a 254 a 255 50 50 52 52 60 60 2 Time and Date — Absolute time at last recorded time Time Delay — Coarse Time Delay — Fine Class Objects — Class Data Class Objects — Class Data 60 Class Objects — Class Data 60 Class Objects — Class Data 80 1 Internal Indications — Packed Format Data Set Prototype — All Var Data Set Prototype — with UUID 85 85 a 86 a Data Set Descriptor — All Var 86 a Data Set Descriptor — Data Set Contents 86 a 86 a Data Set Descriptor — Characteristics Data Set Descriptor — Point Index Attributes 87 87 a a a a Static Data Set — All Var Static Data Set — Present Value 88 Event Data Set — All Var a 88 Event Data Set — Snapshot No Object (function code only) Cold Restart No Object (function code only) Delay Measurement a Request Outstation must parse Function Qualifier Codes Codes (dec) (hex) Response Outstation may issue Function Qualifier Codes Codes (dec) (hex) 00,01,06 129 5B 00,01,06 129 5B 2 07 (qty=1) 07 (qty=1) 07 (qty=1) 129 - 07 (qty=1) - 129 129 - 07 (qty=1) 07 (qty=1) - 129 5B - - 129 5B 129 129 00, 01, 17, 28 5B 129 5B 129 129, 130 5B 5B 1 20, 21 20, 21 20, 21 1 22 1 1 3, 4, 5, 1 13 23 06 06,07,08 06 06,07,08 06 06,07,08 06 00 (index=7) 06 00,01,06, 17,28 5B 06 00,01,06, 17,28 00,01,06, 17,28 5B 00,01,06, 17,28 00,01,06, 17,28 5B 06 00,01,06, 17,28 5B 5B 06,07,08 06,07,08 Object groups and 85 to 88 are only required if the optional data set mapping is supported – 236 – BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) Annex F (normative) Time synchronization F.1 General Any implementation claiming conformance to this part of IEC 61400-25 and declaring support for objects containing an attribute of type TIMESTAMP shall use the SNTP protocol as a minimum in order to guarantee the synchronism inside the wind power plant The use of other more precise synchronisation protocols is not within the scope of this part of IEC 61400-25 In order to get the same interpretation of the TimeQuality attribute of the TIMESTAMP, the following rules should apply: – On the device start-up, its ClockNotSynchronized flag shall be set to TRUE until the device synchronises with an external SNTP server or another more precise synchronisation source (for example GPS, PTP or IRIG-B) – If no other more accurate external synchronism source exists and the SNTP server does not reply to the synchronisation requests or the SNTP responses arrive with the LI indicator indicating that the TimeServer is not reliable, the ClockNotSynchronized flag shall be set after an specific timeout defined by the vendor, in the Protocol Implementation eXtra Information for Testing (PIXIT) document This timeout depends on the precision of the internal clock and shall guarantee a specified maximum deviation (PIXIT) – If the TimeStamp information cannot be considered valid due to, for example, a failure in the internal clock, the ClockFailure flag shall be raised – A value TRUE for the TimeQuality attributes ClockNotSynchronized or ClockFailure, indicating that the timestamp is invalid, shall remain set for all data objects containing the TIMESTAMP attribute until the clock has been succesfully synchronized F.2 A-Profile The A-Profile for Time Sync Services shall be as defined in 6.5.1 of IEC 61850-8-1:2004 F.3 T-Profile The T-Profile for Time Sync Services shall be as defined in 6.5.2 of IEC 61850-8-1:2004 BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 237 – Annex G (informative) Interfaces – Implementation considerations G.1 General To give some guidance in the understanding of the IEC 61400-25 series of standards, the following discussion of an example is intended to show what the IEC 61400-25 series of standards covers compared with a real system The IEC 61400-25 series of standards does not constrain any implementation of the information, service models, communication stacks, actions, and application program interfaces (APIs) NOTE The example is not representative Many other possible interfaces on both sides are possible G.2 Example interfaces of a real system The information exchange between a wind power plant (WPP) device and supervisory and control systems mainly comprises – according to Figure G.1 – a client, a server, several interfaces, and actions The server (WPP server) represents the information and information exchange models The client (WPP client) represents the complementary to the server For example, a service provided by the server can be requested by the client The client itself is not specified (it mainly provides the complementary roles of the server) The complete chain from a source of information up to a SCADA visualisation is described (from right to left in the figure): – The data value source is the real WPP The exchange of data (raw) values between the real WPP process and the WPP server is realised by the interface (IF1) and (IF2) – these interfaces are implementation specific How many interfaces are implemented at the server side is implementation specific – The WPP server adds useful information to the (raw) process data (e.g., hierarchical name, time stamp, quality, etc.) This is defined in the model and the addition of the name etc is defined as the action (Act1) – this action is implementation specific – The model of the information (as it is seen from the network point of view) is defined by IEC 61400-25-2 – the model realisation is implementation specific – Monitoring of value changes of process data values delivered from the real-time data source is represented by (Act1) – this action is implementation specific, but behaviour and services are defined in IEC 61400-25-3 – Exchange of data values between WPP server and supervisory and control systems via (IF3) – the behaviour and services are defined in this part of IEC 61400-25 – Exchange of the model description located in the server with another system (IF3) – the behaviour and services are defined in this part of IEC 61400-25 – Exchange of data values between (communication) client and client application (visualisation, HMI) via (IF4) and (Act2) – this action is implementation specific BS EN 61400-25-4:2008 61400-25-4 © IEC:2008(E) – 238 – DLL e.g., visualize at HMI Model/ behavior Act2 IF3 SCADA Visualization HMI TCP/IP Network IF4 Act1 WPP Server, WPP device model, Services WPP Client RS 232 Scope Wind Power Plant data values IF2 Real WPP IF1 5.3.1 IEC 1398/08 Figure G.1 – Implementation issues (example) Interface (IF3) is the only interface that is defined by the IEC 61400-25 series of standards This interface (IF3) is defined by the information that is accessible through this interface and by the messages that carry the service parameters and the values All (application program) interfaces (APIs) are beyond the scope of the IEC 61400-25 series of standards _ This page deliberately left blank WB9423_BSI_StandardColCov_noK_AW:BSI FRONT COVERS 5/9/08 12:55 Page British Standards Institution (BSI) BSI is the independent national body responsible for preparing British Standards It presents the UK view on standards in Europe and at the international level It is incorporated by Royal Charter Revisions Information on standards British Standards are updated by amendment or revision Users of British Standards should make sure that they possess the latest amendments or editions It is the constant aim of BSI to improve the quality of our products and services We would be grateful if anyone finding an inaccuracy or ambiguity while using this British Standard would inform the Secretary of the technical committee responsible, the identity of which can be found on the inside front cover Tel: +44 (0)20 8996 9000 Fax: +44 (0)20 8996 7400 BSI offers members an individual updating service called PLUS which ensures that subscribers automatically receive the latest editions of standards BSI provides a wide range of information on national, European and international standards through its Library Various BSI electronic information services are also available which give details on all its products and services Contact the Information Centre Tel: +44 (0)20 8996 7111 Fax: +44 (0)20 8996 7048 Email: info@bsigroup.com Subscribing members of BSI are kept up to date with standards developments and receive substantial discounts on the purchase price of standards For details of these and other benefits contact Membership Administration Tel: +44 (0)20 8996 7002 Fax: +44 (0)20 8996 7001 Email: membership@bsigroup.com Information regarding online access to British Standards via British Standards Online can be found at www.bsigroup.com/BSOL Further information about BSI is available on the BSI website at www.bsigroup.com Buying standards Orders for all BSI, international and foreign standards publications should be addressed to BSI Customer Services Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 Email: orders@bsigroup.com You may also buy directly using a debit/credit card from the BSI Shop on the website www.bsigroup.com/shop In response to orders for international standards, it is BSI policy to supply the BSI implementation of those that have been published as British Standards, unless otherwise requested Copyright Copyright subsists in all BSI publications BSI also holds the copyright, in the UK, of the publications of the international standardization bodies Except as permitted under the Copyright, Designs and Patents Act 1988 no extract may be reproduced, stored in a retrieval system or transmitted in any form or by any means – electronic, photocopying, recording or otherwise – without prior written permission from BSI This does not preclude the free use, in the course of implementing the standard of necessary details such as symbols, and size, type or grade designations If these details are to be used for any other purpose than implementation then the prior written permission of BSI must be obtained Details and advice can be obtained from the Copyright & Licensing Manager Tel: +44 (0)20 8996 7070 Email: copyright@bsigroup.com BSI Group Headquarters 389 Chiswick High Road London W4 4AL UK Tel +44 (0)20 8996 9001 Fax +44 (0)20 8996 7001 www.bsigroup.com/standards raising standards worldwide™