Already a subscriber?
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
BS EN 61400-25-4:2017 Wind energy generation systems - Communications for monitoring and control of wind power plants. Mapping to communication profile, 2017
- undefined
- Annex ZA(normative)Normative references to international publicationswith their corresponding European publications
- English [Go to Page]
- CONTENTS
- FOREWORD
- INTRODUCTION
- 1 Scope
- 2 Normative references
- Figures [Go to Page]
- Figure 1 – Conceptual communication model of IEC 61400-25 series
- 3 Terms and definitions
- 4 Abbreviated terms
- 5 General overview [Go to Page]
- 5.1 General
- 5.2 Mapping to protocol stacks
- 5.3 Services of IEC 61400-25-3 mapped to protocol stacks
- Figure 2 – Communication profiles
- Tables [Go to Page]
- Table 1 – Mapping overview of IEC 61400-25-3 services
- Annexes [Go to Page]
- Annex A (normative) Specific communication service mapping – Definition and mapping to Web Services [Go to Page]
- A.1 General [Go to Page]
- A.1.1 Introduction to definition and mapping to Web Services
- A.1.2 Scope of the definition and mapping to Web Services
- A.1.3 The mapping architecture
- Figure A.1 – Mapping architecture (conceptual)
- Table A.1 – Web Services mapping overview of IEC 61400-25 IM and IEM [Go to Page]
- A.2 Mapping of the IEC 61400-25 Information Model to Web Services [Go to Page]
- A.2.1 General introduction to mapping to web services
- Table A.2 – Mapping the IEC 61400-25 IM to Web Services
- Figure A.2 – Naming structure applied in the IEC 61400-25 series (conceptual) [Go to Page]
- [Go to Page]
- A.2.2 DATA OBJECT class
- A.2.3 DATA ATTRIBUTE definition
- Table A.3 – XML schema for wind power information model [Go to Page]
- A.3 Mapping of the Information Exchange Model to Web Services [Go to Page]
- A.3.1 General
- A.3.2 SERVER class service mapping
- Table A.4 – Server class services mapped to Web Services
- Table A.5 – GetServerDirectoryRequest
- Table A.6 – GetServerDirectoryResponse
- Table A.7 – AssociateRequest
- Table A.8 – AssociateResponse
- Table A.9 – ReleaseRequest
- Table A.10 – ReleaseResponse [Go to Page]
- [Go to Page]
- A.3.3 LOGICAL-DEVICE class service mapping
- Table A.11 – AbortRequest
- Table A.12 – AbortResponse
- Table A.13 – LOGICAL-DEVICE service mapping
- Table A.14 – GetLogicalDeviceDirectoryRequest [Go to Page]
- [Go to Page]
- A.3.4 LOGICAL-NODE class services mapping
- Table A.15 – GetLogicalDeviceDirectoryResponse
- Table A.16 – LOGICAL-NODE mapping
- Table A.17 – GetLogicalNodeDirectoryRequest
- Table A.18 – GetLogicalNodeDirectoryResponse
- Table A.19 – GetAllDataValuesRequest [Go to Page]
- [Go to Page]
- A.3.5 DATA class services mapping
- Table A.20 – GetAllDataValuesResponse
- Table A.21 – Data mapping
- Table A.22 – GetDataValuesRequest
- Table A.23 – GetDataValuesResponse
- Table A.24 – SetDataValuesRequest
- Table A.25 – SetDataValuesResponse
- Table A.26 – GetDataDirectoryRequest
- Table A.27 – GetDataDirectoryResponse
- Table A.28 – GetDataDefinitionRequest
- Table A.29 – GetDataDefinitionResponse [Go to Page]
- [Go to Page]
- A.3.6 DATA-SET class services mapping
- Table A.30 – DATA-SET mapping
- Table A.31 – GetDataSetValuesRequest
- Table A.32 – GetDataSetValuesResponse
- Table A.33 – SetDataSetValuesRequest
- Table A.34 – SetDataSetValuesResponse
- Table A.35 – CreateDataSetRequest
- Table A.36 – CreateDataSetResponse
- Table A.37 – DeleteDataSetRequest
- Table A.38 – DeleteDataSetResponse
- Table A.39 – GetDataSetDirectoryRequest [Go to Page]
- [Go to Page]
- A.3.7 REPORT-CONTROL-BLOCK (RCB) class services mapping
- Table A.40 – GetDataSetDirectoryResponse
- Table A.41 – Report control block services mapping
- Figure A.3 – Client behavior in the reporting service (conceptual)
- Figure A.4 – Server behavior in the reporting service (conceptual)
- Figure A.5 – Reporting Services mechanism (conceptual)
- Table A.42 – ReportFormat
- Table A.43 – GetBRCBValuesRequest
- Table A.44 – GetBRCBValuesResponse
- Table A.45 – SetBRCBValuesRequest
- Table A.46 – SetBRCBValuesResponse
- Table A.47 – GetURCBValuesRequest
- Table A.48 – GetURCBValuesResponse
- Table A.49 – SetURCBValuesRequest
- Table A.50 – SetURCBValuesResponse
- Table A.51 – ReportRequest [Go to Page]
- [Go to Page]
- A.3.8 LOG-CONTROL-BLOCK (LCB) class services mapping
- Table A.52 – ReportResponse
- Table A.53 – LOG-CONTROL-BLOCK services mapping
- Table A.54 – GetLCBValuesRequest
- Table A.55 – GetLCBValuesResponse
- Table A.56 – SetLCBValuesRequest
- Table A.57 – SetLCBValuesResponse [Go to Page]
- [Go to Page]
- A.3.9 LOG class services mapping
- Table A.58 – Log class services mapping
- Table A.59 – GetLogStatusValuesRequest
- Table A.60 – GetLogStatusValuesResponse
- Table A.61 – QueryLogByTimeRequest
- Table A.62 – QueryLogByTimeResponse
- Table A.63 – QueryLogAfterRequest [Go to Page]
- [Go to Page]
- A.3.10 CONTROL class services mapping
- Table A.64 – QueryLogAfterResponse
- Table A.65 – Control class services mapping
- Table A.66 – SelectRequest
- Table A.67 – SelectResponse
- Table A.68 – SelectWithValueRequest
- Table A.69 – SelectWithValueResponse
- Table A.70 – CancelRequest
- Table A.71 – CancelResponse
- Table A.72 – OperateRequest
- Table A.73 – OperateResponse
- Table A.74 – CommandTerminationRequest
- Table A.75 – CommandTerminationResponse
- Table A.76 – TimeActivatedOperateRequest
- Table A.77 – TimeActivatedOperateResponse
- Table A.78 – TimeActivatedOperateTerminationRequest
- Table A.79 – TimeActivatedOperateTerminationResponse [Go to Page]
- A.4 Protocol stack details
- Table A.80 – AddCause parameter response [Go to Page]
- A.5 The WSDL specification for the definition and mapping to Web Services
- Table A.81 – Protocol stack selections
- Annex B (normative) Specific communication service mapping – Mapping to OPC XML-DA [Go to Page]
- B.1 General [Go to Page]
- B.1.1 Introduction to mapping to OPC XML-DA
- B.1.2 Scope for the mapping to OPC XML-DA
- B.1.3 The mapping architecture
- Figure B.1 – Mapping architecture (conceptual)
- Table B.1 – Mapping of IEC 61400-25-3 IEM service into OPC XML-DA services [Go to Page]
- B.2 Mapping of the IEC 61400-25 Information Model to OPC XML-DA [Go to Page]
- B.2.1 Mapping of IEC 61400-25-2 Information Model classes to OPC XML-DA
- B.2.2 Server
- Table B.2 – Mapping of IEC 61400-25-2 IM classes to OPC XML-DA
- Table B.3 – Server class attributes [Go to Page]
- [Go to Page]
- B.2.3 Logical Device
- B.2.4 Logical Node
- B.2.5 Data Object
- Table B.4 – Logical Device Class attributes
- Table B.5 – Logical Node Class attributes [Go to Page]
- [Go to Page]
- B.2.6 Data Attribute
- Table B.6 – Data Object Class attributes
- Table B.7 – Data Attribute Class attributes
- Table B.8 – Mapping of the Basic Types
- Figure B.2 – Differences between OPC XML-DA and IEC Information Model timestamp
- Table B.9 – New OPC XML-DA Error codes
- Table B.10 – Timestamp mapping
- Table B.11 – Mapping of the Quality attribute [Go to Page]
- B.3 Mapping of the Information Exchange Model to OPC XML-DA services [Go to Page]
- B.3.1 General
- B.3.2 Association model
- Table B.12 – Cookie parameter explanation
- Figure B.3 – Sequence of services to establish an association [Go to Page]
- [Go to Page]
- B.3.3 Server class services – GetServerDirectory
- Table B.13 – IEM GetServerDirectory mapping
- Table B.14 – IEM GetServerDirectory mapping detailed [Go to Page]
- [Go to Page]
- B.3.4 Logical device class services – GetLogicalDeviceDirectory
- Table B.15 – IEM GetLogicalDeviceDirectory mapping
- Table B.16 – IEM GetLogicalDeviceDirectory mapping detailed
- Table B.17 – GetLogicalDeviceDirectory negative response mapping to IEM ServiceError [Go to Page]
- [Go to Page]
- B.3.5 Logical node class services
- Table B.18 – IEM GetLogicalNodeDirectory mapping
- Table B.19 – IEM GetLogicalNodeDirectory mapping detailed
- Table B.20 – GetLogicalNodeDirectory negative response mapping to IEM ServiceError [Go to Page]
- [Go to Page]
- B.3.6 Data class services
- Table B.21 – IEM GetDataValues mapping
- Table B.22 – IEM GetDataValues mapping detailed
- Table B.23 – GetDataValues negative response mapping to IEM ServiceError
- Table B.24 – IEM SetDataValues mapping
- Table B.25 – IEM SetDataValues mapping detailed
- Table B.26 – SetDataValues negative response mapping to IEM ServiceError
- Table B.27 – IEM GetDataDirectory mapping
- Table B.28 – IEM GetDataDirectory mapping detailed [Go to Page]
- [Go to Page]
- B.3.7 Data set model
- Table B.29 – GetDataDirectory negative response mapping to IEM ServiceError
- Figure B.4 – CreateDataSet sequence of services
- Table B.30 – Mapping of CreateDataSet service parameters
- Table B.31 – CreateDataSet negative response mapping to IEM ServiceError
- Table B.32 – GetDataSetValues negative response mapping to IEM ServiceError
- Table B.33 – SetDataSetValues negative response mapping to IEM ServiceError [Go to Page]
- [Go to Page]
- B.3.8 Report model
- Table B.34 – OPC Subscription attributes’ constrained value
- Table B.35 – Subscribe
- Table B.36 – Subscription Cancel
- Table B.37 – Fault mapping to IEM ServiceError
- Table B.38 – Mapping of Report service parameters [Go to Page]
- [Go to Page]
- B.3.9 Control model
- Table B.39 – Control models supported in this mapping
- Table B.40 – Control services supported
- Table B.41 – Control model writable custom item properties
- Table B.42 – AddCause mapping to OPC Error Code
- Table B.43 – Select request service mapping
- Table B.44 – SelectWithValue service parameter mapping
- Table B.45 – Cancel service parameter mapping
- Table B.46 – Cancel negative response mapping to IEM ServiceError
- Table B.47 – Operate service parameter mapping
- Table B.48 – Operate negative response mapping to IEM ServiceError
- Table B.49 – TimeActivatedOperate service parameter mapping
- Table B.50 – TimeActivatedOperate negative response mapping to IEM ServiceError [Go to Page]
- B.4 Protocol stack details
- Table B.51 – Protocol stack details
- Annex C (normative) Specific communication service mapping – Mapping to ISO 9506 specified in IEC 61850-8-1 [Go to Page]
- C.1 General [Go to Page]
- C.1.1 Introduction to mapping to ISO 9506 specified in IEC 61850-8-1
- C.1.2 Scope of the mapping to ISO 9506 specified in IEC 61850-8-1
- C.1.3 The mapping architecture
- Figure C.1 – Mapping architecture (conceptual)
- Table C.1 – Mapping of IEC 61400-25-3 IEM to ISO 9506 according to IEC 61850-8-1 [Go to Page]
- C.2 Mapping of the IEC 61400-25 Information Model to ISO 9506 as specified in IEC 61850-8-1 [Go to Page]
- C.2.1 General
- C.2.2 Extended Logging services
- C.3 Protocol stack details [Go to Page]
- C.3.1 General
- C.3.2 A-Profile
- Table C.2 – QueryLogByTime mapping
- Table C.3 – QueryLogAfter mapping [Go to Page]
- [Go to Page]
- C.3.3 TCP/IP T-Profile
- Table C.4 – Service and protocols for client/server communication A-Profile
- Table C.5 – Service and protocols for client/server TCP/IP T-Profile
- Annex D (normative) Specific communication service mapping – Mapping to IEC 60870-5-104 specified in IEC TS 61850-80-1 [Go to Page]
- D.1 General [Go to Page]
- D.1.1 Introduction to mapping to IEC 60870-5-104 specified in IEC TS 61850-80-1
- D.1.2 Scope of the mapping to IEC 60870-5-104 specified in IEC TS 61850-80-1
- D.1.3 The mapping architecture
- Figure D.1 – Mapping architecture (conceptual)
- Table D.1 – Services Mapping overview of IEC 61400-25 IM and IEM [Go to Page]
- D.2 Mapping of the IEC 61400-25 Information Model to IEC 60870-5-104 as specified in IEC TS 61850-80-1 [Go to Page]
- D.2.1 General
- D.2.2 Logical Device IM class mapping
- Table D.2 – Example for mapping of LD and LN to CASDU and IOA [Go to Page]
- [Go to Page]
- D.2.3 Logical Node IM class mapping
- D.3 Mapping of IEC 61400-25 Information Model data to IEC 60870-5-104 [Go to Page]
- D.3.1 Mapping of the Common Data Classes (CDC)
- Table D.3 – Logical device mapping
- Table D.4 – Logical node mapping
- Table D.5 – CDCs defined in IEC 61400-25-2
- Table D.6 – CDC: Status Value, STV class
- Table D.7 – CDC: Setpoint Value, SPV class
- Table D.8 – CDC: Alarm, ALM class
- Table D.9 – CDC: Command CMD class
- Table D.10 – CDC: Event Counting, CTE class
- Table D.11 – CDC: State Timing, TMS class
- Table D.12 – Mapping structure basic CDC
- Table D.13 – CDC: Controllable Analog set point, APC class
- Table D.14 – CDC: Controllable analogue set point information (APC) mapping of data attributes of the Functional Constraint MX
- Table D.15 – CDC: Controllable Analog set point, APC class mapping of data and attributes of the Functional Constraint CO
- Table D.16 – CDC: Enumerated status, ENS class
- Table D.17 – CDC: Enumerated status, ENS class mapping of dataand attributes of the Functional Constraint ST
- Table D.18 – CDC: ENC Controllable enumerated status, class ENC
- Table D.19 – CDC: Controllable enumerated status, ENC class mappingof data and attributes of the Functional Constraint CO
- Table D.20 – CDC: ENG Enumerated status setting, class ENG
- Table D.21 – Relationship between complex CDCs and IEC 60870-5-104 ASDUs [Go to Page]
- D.4 Mapping of the Information Exchange Model to IEC 60870-5-104 services [Go to Page]
- D.4.1 List of service models and corresponding mappings
- Table D.22 – Mapping of IEC 61400-25 ACSI service into IEC 60870-5-104 services [Go to Page]
- [Go to Page]
- D.4.2 Control class mapping
- Figure D.2 – Direct Control with Normal Security with status update – positive case
- Figure D.3 – Direct Control with Normal Security in general – negative case a)
- Figure D.4 – Direct Control with Normal Security in general – negative case b)
- Figure D.5 – Direct Control with Normal Security with status update – negative case c)
- Figure D.6 – Direct Control with Normal Security without status update – positive case
- Figure D.7 – Direct Control with Enhanced Security – positive case
- Figure D.8 – Direct Control with Enhanced Security – negative case c)
- Figure D.9 – Direct Control with Enhanced Security – negative case d)
- Figure D.10 – SBOw control – positive case
- Figure D.11 – SBOw control – negative case a)
- Figure D.12 – SBOw control – negative case b)
- Figure D.13 – SBOw control – negative case c)
- Figure D.14 – SBO with Enhanced Security – positive case
- Figure D.15 – SBO with Enhanced Security – negative case a) [Go to Page]
- D.5 Protocol stack selections for IEC 60870-5-104 (Protocol stack details) [Go to Page]
- D.5.1 General
- D.5.2 Structure of application data
- D.5.3 IEC 60870-5-104 Interoperability
- Figure D.16 – SBO with Enhanced Security – negative case b) [Go to Page]
- D.6 Use of SCL (Substation Configuration Language) extension to include IEC 60870-5-101/104 information (informative) [Go to Page]
- D.6.1 General
- D.6.2 SCL information model hierarchy
- D.6.3 IEC 60870-5-101/104 Private section syntax
- D.6.4 IEC 60870-5-104 communication parameters configuration using SCL
- Annex E (normative) Specific communication service mapping – Mapping to DNP3 [Go to Page]
- E.1 General [Go to Page]
- E.1.1 Introduction to mapping to DNP3
- E.1.2 Scope for the mapping to DNP3
- E.1.3 Mapping architecture
- Figure E.1 – Mapping architecture (conceptual)
- Table E.1 – Services requiring Client/Server Communication Profile [Go to Page]
- E.2 Mapping of the IEC 61400-25 Information Model to DNP3 [Go to Page]
- E.2.1 Mapping of IEC 61850-7-3 inherited common Data Classes
- E.2.2 CDC Setpoint Parameter Value (SPV)
- E.2.3 CDC Status Value (STV)
- Table E.2 – CDC: Setpoint Parameter Value (SPV) mapping [Go to Page]
- [Go to Page]
- E.2.4 CDC Alarm (ALM)
- Table E.3 – CDC: Status Value (STV) mapping
- Table E.4 – CDC: Alarm (ALM) mapping [Go to Page]
- [Go to Page]
- E.2.5 CDC Command (CMD)
- E.2.6 CDC Event Counting (CTE)
- Table E.5 – CDC: Command (CMD) mapping [Go to Page]
- [Go to Page]
- E.2.7 CDC State Timing (TMS)
- Table E.6 – CDC: Event Counting (CTE) mapping [Go to Page]
- [Go to Page]
- E.2.8 CDC Device Name Plate (WDPL)
- Table E.7 – CDC: State Timing (TMS) mapping [Go to Page]
- [Go to Page]
- E.2.9 CDC Alarm Set Status (AST)
- Table E.8 – CDC: Device Name Plate (WDPL) mapping [Go to Page]
- E.3 Mapping of the Information Exchange Model to DNP3 services
- Table E.9 – CDC: Alarm Set Status (AST) mapping
- Annex F (normative) Time synchronization [Go to Page]
- F.1 General
- F.2 A-Profile
- F.3 T-Profile
- Annex G (informative) Interfaces – Implementation considerations [Go to Page]
- G.1 General
- G.2 Example interfaces of a real system
- Figure G.1 – Implementation issues (example)
- Bibliography [Go to Page]