{"id":255349,"date":"2024-10-19T16:52:47","date_gmt":"2024-10-19T16:52:47","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61400-25-42017\/"},"modified":"2024-10-25T12:19:55","modified_gmt":"2024-10-25T12:19:55","slug":"bs-en-61400-25-42017","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61400-25-42017\/","title":{"rendered":"BS EN 61400-25-4:2017"},"content":{"rendered":"
IEC 61400-25-4:2016 is also available as \/2 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 61400-25-4:2016 specifies the specific mappings to protocol stacks encoding the messages required for the information exchange between a client and a remote server for: data access and retrieval, device control, event reporting and logging, publisher\/subscriber, self-description of devices (device data dictionary), data typing and discovery of data types. The mappings specified in this part of IEC 61400-25 comprise: – a mapping to SOAP-based web services, – a mapping to OPC\/XML-DA, – a mapping to IEC 61850-8-1 MMS, – a mapping to IEC 60870-5-104, – a mapping to DNP3. The main technical changes with regard to the previous edition are as follows: – general harmonization with information models in IEC 61400-25-2 and information exchange services in IEC 61400-25-3; – reduction of overlap between standards and simplification by increased referencing.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
5<\/td>\n | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | English CONTENTS <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 2 Normative references Figures Figure 1 \u2013 Conceptual communication model of IEC 61400-25 series <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 3 Terms and definitions 4 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5 General overview 5.1 General <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.2 Mapping to protocol stacks 5.3 Services of IEC 61400-25-3 mapped to protocol stacks Figure 2 \u2013 Communication profiles <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | Tables Table 1 \u2013 Mapping overview of IEC 61400-25-3 services <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | Annexes Annex A (normative) Specific communication service mapping \u2013 Definition and mapping to Web Services A.1 General 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 <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | Figure A.1 \u2013 Mapping architecture (conceptual) <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Table A.1 \u2013 Web Services mapping overview of IEC 61400-25 IM and IEM <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | A.2 Mapping of the IEC 61400-25 Information Model to Web Services A.2.1 General introduction to mapping to web services Table A.2 \u2013 Mapping the IEC 61400-25 IM to Web Services <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure A.2 \u2013 Naming structure applied in the IEC 61400-25 series (conceptual) <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | A.2.2 DATA OBJECT class A.2.3 DATA ATTRIBUTE definition Table A.3 \u2013 XML schema for wind power information model <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | A.3 Mapping of the Information Exchange Model to Web Services A.3.1 General A.3.2 SERVER class service mapping Table A.4 \u2013 Server class services mapped to Web Services <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Table A.5 \u2013 GetServerDirectoryRequest Table A.6 \u2013 GetServerDirectoryResponse <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Table A.7 \u2013 AssociateRequest <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Table A.8 \u2013 AssociateResponse <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Table A.9 \u2013 ReleaseRequest Table A.10 \u2013 ReleaseResponse <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | A.3.3 LOGICAL-DEVICE class service mapping Table A.11 \u2013 AbortRequest Table A.12 \u2013 AbortResponse <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Table A.13 \u2013 LOGICAL-DEVICE service mapping Table A.14 \u2013 GetLogicalDeviceDirectoryRequest <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | A.3.4 LOGICAL-NODE class services mapping Table A.15 \u2013 GetLogicalDeviceDirectoryResponse Table A.16 \u2013 LOGICAL-NODE mapping <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Table A.17 \u2013 GetLogicalNodeDirectoryRequest Table A.18 \u2013 GetLogicalNodeDirectoryResponse <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table A.19 \u2013 GetAllDataValuesRequest <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | A.3.5 DATA class services mapping Table A.20 \u2013 GetAllDataValuesResponse Table A.21 \u2013 Data mapping <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Table A.22 \u2013 GetDataValuesRequest Table A.23 \u2013 GetDataValuesResponse <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Table A.24 \u2013 SetDataValuesRequest <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Table A.25 \u2013 SetDataValuesResponse Table A.26 \u2013 GetDataDirectoryRequest <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Table A.27 \u2013 GetDataDirectoryResponse <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Table A.28 \u2013 GetDataDefinitionRequest <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Table A.29 \u2013 GetDataDefinitionResponse <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | A.3.6 DATA-SET class services mapping Table A.30 \u2013 DATA-SET mapping <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Table A.31 \u2013 GetDataSetValuesRequest Table A.32 \u2013 GetDataSetValuesResponse <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Table A.33 \u2013 SetDataSetValuesRequest Table A.34 \u2013 SetDataSetValuesResponse <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Table A.35 \u2013 CreateDataSetRequest <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Table A.36 \u2013 CreateDataSetResponse Table A.37 \u2013 DeleteDataSetRequest <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Table A.38 \u2013 DeleteDataSetResponse Table A.39 \u2013 GetDataSetDirectoryRequest <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | A.3.7 REPORT-CONTROL-BLOCK (RCB) class services mapping Table A.40 \u2013 GetDataSetDirectoryResponse Table A.41 \u2013 Report control block services mapping <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure A.3 \u2013 Client behavior in the reporting service (conceptual) <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Figure A.4 \u2013 Server behavior in the reporting service (conceptual) <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | Figure A.5 \u2013 Reporting Services mechanism (conceptual) <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table A.42 \u2013 ReportFormat <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Table A.43 \u2013 GetBRCBValuesRequest <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table A.44 \u2013 GetBRCBValuesResponse <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table A.45 \u2013 SetBRCBValuesRequest <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table A.46 \u2013 SetBRCBValuesResponse <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table A.47 \u2013 GetURCBValuesRequest Table A.48 \u2013 GetURCBValuesResponse <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table A.49 \u2013 SetURCBValuesRequest <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table A.50 \u2013 SetURCBValuesResponse <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Table A.51 \u2013 ReportRequest <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | A.3.8 LOG-CONTROL-BLOCK (LCB) class services mapping Table A.52 \u2013 ReportResponse Table A.53 \u2013 LOG-CONTROL-BLOCK services mapping <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table A.54 \u2013 GetLCBValuesRequest <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table A.55 \u2013 GetLCBValuesResponse <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table A.56 \u2013 SetLCBValuesRequest Table A.57 \u2013 SetLCBValuesResponse <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | A.3.9 LOG class services mapping Table A.58 \u2013 Log class services mapping Table A.59 \u2013 GetLogStatusValuesRequest <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Table A.60 \u2013 GetLogStatusValuesResponse <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Table A.61 \u2013 QueryLogByTimeRequest <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table A.62 \u2013 QueryLogByTimeResponse Table A.63 \u2013 QueryLogAfterRequest <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | A.3.10 CONTROL class services mapping Table A.64 \u2013 QueryLogAfterResponse <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Table A.65 \u2013 Control class services mapping Table A.66 \u2013 SelectRequest <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Table A.67 \u2013 SelectResponse <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Table A.68 \u2013 SelectWithValueRequest <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table A.69 \u2013 SelectWithValueResponse <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table A.70 \u2013 CancelRequest <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table A.71 \u2013 CancelResponse <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table A.72 \u2013 OperateRequest <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table A.73 \u2013 OperateResponse <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table A.74 \u2013 CommandTerminationRequest Table A.75 \u2013 CommandTerminationResponse <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table A.76 \u2013 TimeActivatedOperateRequest <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table A.77 \u2013 TimeActivatedOperateResponse <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Table A.78 \u2013 TimeActivatedOperateTerminationRequest Table A.79 \u2013 TimeActivatedOperateTerminationResponse <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | A.4 Protocol stack details Table A.80 \u2013 AddCause parameter response <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | A.5 The WSDL specification for the definition and mapping to Web Services Table A.81 \u2013 Protocol stack selections <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Annex B (normative) Specific communication service mapping \u2013 Mapping to OPC XML-DA B.1 General 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 <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Figure B.1 \u2013 Mapping architecture (conceptual) <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Table B.1 \u2013 Mapping of IEC 61400-25-3 IEM service into OPC XML-DA services <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | B.2 Mapping of the IEC 61400-25 Information Model to OPC XML-DA B.2.1 Mapping of IEC 61400-25-2 Information Model classes to OPC XML-DA B.2.2 Server Table B.2 \u2013 Mapping of IEC 61400-25-2 IM classes to OPC XML-DA Table B.3 \u2013 Server class attributes <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | B.2.3 Logical Device B.2.4 Logical Node B.2.5 Data Object Table B.4 \u2013 Logical Device Class attributes Table B.5 \u2013 Logical Node Class attributes <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | B.2.6 Data Attribute Table B.6 \u2013 Data Object Class attributes Table B.7 \u2013 Data Attribute Class attributes <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Table B.8 \u2013 Mapping of the Basic Types <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | Figure B.2 \u2013 Differences between OPC XML-DA and IEC Information Model timestamp Table B.9 \u2013 New OPC XML-DA Error codes <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Table B.10 \u2013 Timestamp mapping Table B.11 \u2013 Mapping of the Quality attribute <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | B.3 Mapping of the Information Exchange Model to OPC XML-DA services B.3.1 General B.3.2 Association model <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | Table B.12 \u2013 Cookie parameter explanation <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Figure B.3 \u2013 Sequence of services to establish an association <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | B.3.3 Server class services \u2013 GetServerDirectory Table B.13 \u2013 IEM GetServerDirectory mapping <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Table B.14 \u2013 IEM GetServerDirectory mapping detailed <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | B.3.4 Logical device class services \u2013 GetLogicalDeviceDirectory Table B.15 \u2013 IEM GetLogicalDeviceDirectory mapping Table B.16 \u2013 IEM GetLogicalDeviceDirectory mapping detailed <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Table B.17 \u2013 GetLogicalDeviceDirectory negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | B.3.5 Logical node class services Table B.18 \u2013 IEM GetLogicalNodeDirectory mapping Table B.19 \u2013 IEM GetLogicalNodeDirectory mapping detailed <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | Table B.20 \u2013 GetLogicalNodeDirectory negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | B.3.6 Data class services Table B.21 \u2013 IEM GetDataValues mapping <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | Table B.22 \u2013 IEM GetDataValues mapping detailed <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | Table B.23 \u2013 GetDataValues negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Table B.24 \u2013 IEM SetDataValues mapping Table B.25 \u2013 IEM SetDataValues mapping detailed <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Table B.26 \u2013 SetDataValues negative response mapping to IEM ServiceError Table B.27 \u2013 IEM GetDataDirectory mapping <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | Table B.28 \u2013 IEM GetDataDirectory mapping detailed <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | B.3.7 Data set model Table B.29 \u2013 GetDataDirectory negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Figure B.4 \u2013 CreateDataSet sequence of services Table B.30 \u2013 Mapping of CreateDataSet service parameters Table B.31 \u2013 CreateDataSet negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Table B.32 \u2013 GetDataSetValues negative response mapping to IEM ServiceError Table B.33 \u2013 SetDataSetValues negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | B.3.8 Report model Table B.34 \u2013 OPC Subscription attributes\u2019 constrained value <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | Table B.35 \u2013 Subscribe <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | Table B.36 \u2013 Subscription Cancel Table B.37 \u2013 Fault mapping to IEM ServiceError Table B.38 \u2013 Mapping of Report service parameters <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | B.3.9 Control model Table B.39 \u2013 Control models supported in this mapping Table B.40 \u2013 Control services supported <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Table B.41 \u2013 Control model writable custom item properties <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Table B.42 \u2013 AddCause mapping to OPC Error Code <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | Table B.43 \u2013 Select request service mapping <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | Table B.44 \u2013 SelectWithValue service parameter mapping <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | Table B.45 \u2013 Cancel service parameter mapping Table B.46 \u2013 Cancel negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | Table B.47 \u2013 Operate service parameter mapping Table B.48 \u2013 Operate negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | Table B.49 \u2013 TimeActivatedOperate service parameter mapping <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | Table B.50 \u2013 TimeActivatedOperate negative response mapping to IEM ServiceError <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | B.4 Protocol stack details <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Table B.51 \u2013 Protocol stack details <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | Annex C (normative) Specific communication service mapping \u2013 Mapping to ISO 9506 specified in IEC 61850-8-1 C.1 General 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 <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | Figure C.1 \u2013 Mapping architecture (conceptual) Table C.1 \u2013 Mapping of IEC 61400-25-3 IEM to ISO 9506 according to IEC 61850-8-1 <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | C.2 Mapping of the IEC 61400-25 Information Model to ISO 9506 as specified in IEC 61850-8-1 C.2.1 General <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | C.2.2 Extended Logging services C.3 Protocol stack details C.3.1 General C.3.2 A-Profile Table C.2 \u2013 QueryLogByTime mapping Table C.3 \u2013 QueryLogAfter mapping <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | C.3.3 TCP\/IP T-Profile Table C.4 \u2013 Service and protocols for client\/server communication A-Profile Table C.5 \u2013 Service and protocols for client\/server TCP\/IP T-Profile <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Annex D (normative) Specific communication service mapping \u2013 Mapping to IEC 60870-5-104 specified in IEC TS 61850-80-1 D.1 General 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 <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | Figure D.1 \u2013 Mapping architecture (conceptual) <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Table D.1 \u2013 Services Mapping overview of IEC 61400-25 IM and IEM <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | D.2 Mapping of the IEC 61400-25 Information Model to IEC 60870-5-104 as specified in IEC TS 61850-80-1 D.2.1 General <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | D.2.2 Logical Device IM class mapping Table D.2 \u2013 Example for mapping of LD and LN to CASDU and IOA <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | D.2.3 Logical Node IM class mapping D.3 Mapping of IEC 61400-25 Information Model data to IEC 60870-5-104 D.3.1 Mapping of the Common Data Classes (CDC) Table D.3 \u2013 Logical device mapping Table D.4 \u2013 Logical node mapping <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Table D.5 \u2013 CDCs defined in IEC 61400-25-2 Table D.6 \u2013 CDC: Status Value, STV class Table D.7 \u2013 CDC: Setpoint Value, SPV class <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Table D.8 \u2013 CDC: Alarm, ALM class Table D.9 \u2013 CDC: Command CMD class Table D.10 \u2013 CDC: Event Counting, CTE class <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | Table D.11 \u2013 CDC: State Timing, TMS class Table D.12 \u2013 Mapping structure basic CDC <\/td>\n<\/tr>\n | ||||||
199<\/td>\n | Table D.13 \u2013 CDC: Controllable Analog set point, APC class Table D.14 \u2013 CDC: Controllable analogue set point information (APC) mapping of data attributes of the Functional Constraint MX <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | Table D.15 \u2013 CDC: Controllable Analog set point, APC class mapping of data and attributes of the Functional Constraint CO Table D.16 \u2013 CDC: Enumerated status, ENS class <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | Table D.17 \u2013 CDC: Enumerated status, ENS class mapping of dataand attributes of the Functional Constraint ST <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Table D.18 \u2013 CDC: ENC Controllable enumerated status, class ENC Table D.19 \u2013 CDC: Controllable enumerated status, ENC class mappingof data and attributes of the Functional Constraint CO <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | Table D.20 \u2013 CDC: ENG Enumerated status setting, class ENG Table D.21 \u2013 Relationship between complex CDCs and IEC 60870-5-104 ASDUs <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | D.4 Mapping of the Information Exchange Model to IEC 60870-5-104 services D.4.1 List of service models and corresponding mappings Table D.22 \u2013 Mapping of IEC 61400-25 ACSI service into IEC 60870-5-104 services <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | D.4.2 Control class mapping <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Figure D.2 \u2013 Direct Control with Normal Security with status update \u2013 positive case <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | Figure D.3 \u2013 Direct Control with Normal Security in general \u2013 negative case a) Figure D.4 \u2013 Direct Control with Normal Security in general \u2013 negative case b) <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Figure D.5 \u2013 Direct Control with Normal Security with status update \u2013 negative case c) <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | Figure D.6 \u2013 Direct Control with Normal Security without status update \u2013 positive case <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | Figure D.7 \u2013 Direct Control with Enhanced Security \u2013 positive case <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | Figure D.8 \u2013 Direct Control with Enhanced Security \u2013 negative case c) <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Figure D.9 \u2013 Direct Control with Enhanced Security \u2013 negative case d) <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | Figure D.10 \u2013 SBOw control \u2013 positive case Figure D.11 \u2013 SBOw control \u2013 negative case a) <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | Figure D.12 \u2013 SBOw control \u2013 negative case b) <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | Figure D.13 \u2013 SBOw control \u2013 negative case c) Figure D.14 \u2013 SBO with Enhanced Security \u2013 positive case <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | Figure D.15 \u2013 SBO with Enhanced Security \u2013 negative case a) <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | D.5 Protocol stack selections for IEC 60870-5-104 (Protocol stack details) D.5.1 General D.5.2 Structure of application data D.5.3 IEC 60870-5-104 Interoperability Figure D.16 \u2013 SBO with Enhanced Security \u2013 negative case b) <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | D.6 Use of SCL (Substation Configuration Language) extension to include IEC 60870-5-101\/104 information (informative) 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 <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | Annex E (normative) Specific communication service mapping \u2013 Mapping to DNP3 E.1 General E.1.1 Introduction to mapping to DNP3 E.1.2 Scope for the mapping to DNP3 E.1.3 Mapping architecture <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | Figure E.1 \u2013 Mapping architecture (conceptual) <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | Table E.1 \u2013 Services requiring Client\/Server Communication Profile <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | E.2 Mapping of the IEC 61400-25 Information Model to DNP3 E.2.1 Mapping of IEC 61850-7-3 inherited common Data Classes E.2.2 CDC Setpoint Parameter Value (SPV) <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | E.2.3 CDC Status Value (STV) Table E.2 \u2013 CDC: Setpoint Parameter Value (SPV) mapping <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | E.2.4 CDC Alarm (ALM) Table E.3 \u2013 CDC: Status Value (STV) mapping <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Table E.4 \u2013 CDC: Alarm (ALM) mapping <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | E.2.5 CDC Command (CMD) E.2.6 CDC Event Counting (CTE) Table E.5 \u2013 CDC: Command (CMD) mapping <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | E.2.7 CDC State Timing (TMS) Table E.6 \u2013 CDC: Event Counting (CTE) mapping <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | E.2.8 CDC Device Name Plate (WDPL) Table E.7 \u2013 CDC: State Timing (TMS) mapping <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | E.2.9 CDC Alarm Set Status (AST) Table E.8 \u2013 CDC: Device Name Plate (WDPL) mapping <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | E.3 Mapping of the Information Exchange Model to DNP3 services Table E.9 \u2013 CDC: Alarm Set Status (AST) mapping <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | Annex F (normative) Time synchronization F.1 General F.2 A-Profile F.3 T-Profile <\/td>\n<\/tr>\n | ||||||
245<\/td>\n | Annex G (informative) Interfaces \u2013 Implementation considerations G.1 General G.2 Example interfaces of a real system <\/td>\n<\/tr>\n | ||||||
246<\/td>\n | Figure G.1 \u2013 Implementation issues (example) <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Wind energy generation systems – Communications for monitoring and control of wind power plants. Mapping to communication profile<\/b><\/p>\n |