oSIST prEN IEC 62453-1:2022
(Main)Field device tool (FDT) interface specification - Part 1: Overview and guidance
Field device tool (FDT) interface specification - Part 1: Overview and guidance
Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 1: Vue d'ensemble et guide
Specifikacija vmesnika orodja procesne naprave (FDT) - 1. del: Pregled in vodilo
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
oSIST prEN IEC 62453-1:2022
01-maj-2022
Specifikacija vmesnika orodja procesne naprave (FDT) - 1. del: Pregled in vodilo
Field device tool (FDT) interface specification - Part 1: Overview and guidance
Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 1: Vue
d'ensemble et guide
Ta slovenski standard je istoveten z: prEN IEC 62453-1:2022
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
oSIST prEN IEC 62453-1:2022 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN IEC 62453-1:2022
---------------------- Page: 2 ----------------------
oSIST prEN IEC 62453-1:2022
65E/872/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 62453-1 ED3
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2022-03-11 2022-06-03
SUPERSEDES DOCUMENTS:
65E/803/CD, 65E/850/CC
IEC SC 65E : DEVICES AND INTEGRATION IN ENTERPRISE SYSTEMS
SECRETARIAT: SECRETARY:
United States of America Mr Donald (Bob) Lattimer
OF INTEREST TO THE FOLLOWING COMMITTEES: PROPOSED HORIZONTAL STANDARD:
SC 65C
Other TC/SCs are requested to indicate their interest, if
any, in this CDV to the secretary.
FUNCTIONS CONCERNED:
EMC ENVIRONMENT QUALITY ASSURANCE SAFETY
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft
for Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of
which they are aware and to provide supporting documentation.
TITLE:
Field device tool (FDT) interface specification - Part 1: Overview and guidance
PROPOSED STABILITY DATE: 2025
2
Copyright © 2022 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.
---------------------- Page: 3 ----------------------
oSIST prEN IEC 62453-1:2022
IEC CDV 62453-1 ED3©IEC 2022 – 3 –
NOTE FROM TC/SC OFFICERS:
---------------------- Page: 4 ----------------------
oSIST prEN IEC 62453-1:2022
2 IEC CDV 62453-1 ED3©IEC 2022
1
2 CONTENTS
3 CONTENTS . 2
4 FOREWORD . 5
5 INTRODUCTION . 7
6 1 Scope . 9
7 2 Normative references . 9
8 3 Terms, definitions, symbols, abbreviations and conventions . 9
9 3.1 Terms and definitions . 9
10 3.2 Abbreviations . 14
11 3.3 Conventions . 15
12 4 FDT overview . 15
13 4.1 State of the art . 15
14 4.2 Objectives of FDT . 16
15 4.2.1 General features . 16
16 4.2.2 Device and module manufacturer benefits . 16
17 4.2.3 System manufacturer and integrator benefits . 17
18 4.2.4 Other applications . 17
19 4.3 FDT model . 17
20 4.3.1 General . 17
21 4.3.2 Frame Applications . 19
22 4.3.3 Device Type Manager . 20
23 4.3.4 Communication Channel concept . 21
24 4.3.5 Presentation object . 23
25 5 Structure of the IEC 62453 series . 23
26 5.1 Structure overview . 23
27 5.2 Part 2 – Concepts and detailed description . 25
28 5.3 Parts 3xy – Communication profile integration . 26
29 5.3.1 General . 26
30 5.3.2 Communication profile integration – IEC 61784 CPF 1 . 26
31 5.3.3 Communication profile integration – IEC 61784 CPF 2 . 26
32 5.3.4 Communication profile integration – IEC 61784 CP 3/1 and 3/2 . 26
33 5.3.5 Communication profile integration – IEC 61784 CP 3/4, CP 3/5 and 3/6 . 26
34 5.3.6 Communication profile integration – IEC 61784 CPF 6 . 26
35 5.3.7 Communication profile integration – IEC 61784 CPF 9 . 27
36 5.3.8 Communication profile integration – IEC 61784 CPF 15 . 27
37 5.4 Parts 4z – Object model integration profiles . 27
38 5.4.1 General . 27
39 5.4.2 Object model integration profile – Common object model (COM) . 27
40 5.4.3 Object model integration profile – Common language infrastructure
41 (CLI) . 27
42 5.4.4 Object model integration profile – CLI and HTML . 27
43 5.5 Parts 51-xy/52-xy/53-xy – Communication profile implementation . 27
2
---------------------- Page: 5 ----------------------
oSIST prEN IEC 62453-1:2022
IEC CDV 62453-1 ED3©IEC 2022 – 3 –
44 5.5.1 General . 27
45 5.5.2 Communication profile implementation – IEC 61784 CPF 1. 28
46 5.5.3 Communication profile implementation – IEC 61784 CPF 2. 28
47 5.5.4 Communication profile implementation – IEC 61784 CP 3/1 and 3/2 . 28
48 5.5.5 Communication profile implementation – IEC 61784 CP 3/4, CP 3/5 and
49 3/6 . 28
50 5.5.6 Communication profile implementation – IEC 61784 CPF 6. 28
51 5.5.7 Communication profile implementation – IEC 61784 CPF 9. 28
52 5.5.8 Communication profile implementation – IEC 61784 CPF 15 . 29
53 5.6 Parts 6z – DTM styleguides . 29
54 5.6.1 General . 29
55 5.6.2 Device Type Manager (DTM) styleguide for common object model . 29
56 5.6.3 Field Device Tool (FDT) styleguide for common language infrastructure . 29
57 5.7 Part 71 – OPC UA Information Model for FDT . 29
58 6 Relation of the IEC 62453 series to other standardization activities . 29
59 7 Migration to DTM . 33
60 8 How to read IEC 62453 . 34
61 8.1 Architecture . 34
62 8.2 Dynamic behavior . 34
63 8.3 Structured data types . 35
64 8.4 Fieldbus communication. 35
65 Annex A (normative) UML notation . 36
66 A.1 General . 36
67 A.2 Class diagram . 36
68 A.3 Component diagram . 39
69 A.4 Statechart diagram. 40
70 A.5 Use case diagram . 41
71 A.6 Sequence diagram . 42
72 A.7 Object diagram . 45
73 Annex B (informative) Implementation policy . 47
74 Bibliography . 48
75
76 Figure 1 − Different tools and fieldbuses result in limited integration . 16
77 Figure 2 – Full integration of all devices and modules into a homogeneous system . 17
78 Figure 3 – General architecture and components . 18
79 Figure 4 – FDT software architecture . 20
80 Figure 5 – General FDT client/server relationship . 21
81 Figure 6 – Typical FDT channel architecture . 22
82 Figure 7 – Channel/parameter relationship . 23
83 Figure 8 – Structure of the IEC 62453 series . 24
84 Figure 9 – Standards related to IEC 62453 in an automation hierarchy . 30
85 Figure 10 – Standards related to IEC 62453 – Grouped by purpose . 33
86 Figure 11 – DTM implementations . 34
87 Figure A.1 – Note. 36
88 Figure A.2 – Class . 36
89 Figure I.3 — Icons for class members . 36
90 Figure A.3 – Association . 37
---------------------- Page: 6 ----------------------
oSIST prEN IEC 62453-1:2022
– 4 – IEC CDV 62453-1 ED3©IEC 2022
91 Figure A.4 – Navigable Association . 37
92 Figure A.5 – Composition . 37
93 Figure A.6 – Aggregation . 37
94 Figure A.7 – Dependency. 37
95 Figure A.8 – Association class . 38
96 Figure A.9 – Abstract class, generalization and interface . 38
97 Figure A.10 – Interface related notations . 39
98 Figure A.11 – Multiplicity . 39
99 Figure A.12 – Enumeration datatype . 39
100 Figure I.14 — Component . 40
101 Figure A.13 – Elements of UML statechart diagrams . 40
102 Figure A.14 – Example of UML state chart diagram. 41
103 Figure A.15 – UML use case syntax . 41
104 Figure A.16 – UML sequence diagram . 42
105 Figure A.17 – Empty UML sequence diagram frame . 42
106 Figure A.20 – Modelling guarded call and multiple calls . 43
107 Figure A.21 – Call to itself . 44
108 Figure A.22 – Continuation / StateInvariant . 44
109 Figure A.23 – Alternative fragment . 44
110 Figure A.24 – Option fragment . 45
111 Figure A.25 – Loop combination fragment . 45
112 Figure A.26 – Break notation . 45
113 Figure A.27 – Sequence reference . 45
114 Figure A.28 – Objects . 46
115 Figure A.29 – Object link. 46
116
117 Table 1 – Overview of related standards . 31
118
119
---------------------- Page: 7 ----------------------
oSIST prEN IEC 62453-1:2022
IEC CDV 62453-1 ED3©IEC 2022 – 5 –
120 INTERNATIONAL ELECTROTECHNICAL COMMISSION
121 ____________
122
123 FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
124
125 Part 1: Overview and guidance
126
127 FOREWORD
128 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
129 all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
130 international co-operation on all questions concerning standardization in the electrical and electronic fields. To
131 this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
132 Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
133 Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
134 in the subject dealt with may participate in this preparatory work. International, governmental and non-
135 governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
136 with the International Organization for Standardization (ISO) in accordance with conditions determined by
137 agreement between the two organizations.
138 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
139 consensus of opinion on the relevant subjects since each technical committee has representation from all
140 interested IEC National Committees.
141 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
142 Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
143 Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
144 misinterpretation by any end user.
145 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
146 transparently to the maximum extent possible in their national and regional publications. Any divergence
147 between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
148 the latter.
149 5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
150 assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
151 services carried out by independent certification bodies.
152 6) All users should ensure that they have the latest edition of this publication.
153 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
154 members of its technical committees and IEC National Committees for any personal injury, property damage or
155 other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
156 expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
157 Publications.
158 8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
159 indispensable for the correct application of this publication.
160 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
161 patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
162 International Standard IEC 62453-1 has been prepared by subcommittee 65E: Devices and
163 integration in enterprise systems, of IEC technical committee 65: Industrial-process
164 measurement, control and automation.
165 This third edition cancels and replaces the first edition published in 2016. This edition
166 constitutes a technical revision.
167 This edition includes the following significant technical changes with respect to the previous
168 edition: introduction of a new implementation technology (defined in IEC TR 62453-43) as well
169 as an OPC UA information model for FDT (defined in IEC 62453-71).
170
---------------------- Page: 8 ----------------------
oSIST prEN IEC 62453-1:2022
– 6 – IEC CDV 62453-1 ED3©IEC 2022
171 The text of this standard is based on the following documents:
CDV Report on voting
65E/-/CDV 65E/-/RVC
172
173 Full information on the voting for the approval of this standard can be found in the report on
174 voting indicated in the above table.
175 This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
176 A list of all parts of the IEC 62453 series, under the general title Field Device Tool (FDT)
177 interface specification, can be found on the IEC website.
178 The committee has decided that the contents of this publication will remain unchanged until
179 the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
180 related to the specific publication. At this date, the publication will be
181 • reconfirmed,
182 • withdrawn,
183 • replaced by a revised edition, or
184 • amended.
185
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates that it
contains colours which are considered to be useful for the correct understanding of its
contents. Users should therefore print this document using a colour printer.
186
187
---------------------- Page: 9 ----------------------
oSIST prEN IEC 62453-1:2022
IEC CDV 62453-1 ED3©IEC 2022 – 7 –
188 INTRODUCTION
189 Enterprise automation requires two main data flows: a “vertical” data flow from enterprise
190 level down to the field devices including signals and configuration data, and a “horizontal”
191 communication between field devices operating on the same or different communication
192 technologies.
193 With the integration of fieldbuses into control systems, there are a few additional tasks to be
194 performed. They may result in a large number of fieldbus- and device-specific tools in addition
195 to system and engineering tools. Integration of these tools into higher-level system-wide
196 planning or engineering tools is an advantage. In particular, for use in extensive and
197 heterogeneous control systems, typically in the area of the process industry, the unambiguous
198 definition of engineering interfaces that are easy to use for all those involved is of great
199 importance.
200 Several different manufacturer specific tools are used. The data in these tools are often
201 invisible data islands from the viewpoint of system life-cycle management and plant-wide
202 automation.
203 To ensure the consistent management of a plant-wide control and automation technology, it is
204 important to fully integrate fieldbuses, devices and sub-systems as a seamless part of a wide
205 range of automation tasks covering the whole automation life-cycle.
1
206 IEC 62453 provides an interface specification for developers of FDT (Field Device Tool)
207 components to support function control and data access within a client/server architecture.
208 The availability of this standard interface facilitates development of servers and clients by
209 multiple manufacturers and supports open interoperation.
210 A device or module-specific software component, called a DTM (Device Type Manager) is
211 supplied by a manufacturer with the related device type or software entity type. Each DTM
212 can be integrated into engineering tools via defined FDT interfaces. This approach to
213 integration is in general open for all fieldbusses and thus supports integration of different
214 devices and software modules into heterogeneous control systems.
215 The IEC 62453 common application interface supports the interests of application developers,
216 system integrators, and manufacturers of field devices and network components. It also
217 simplifies procurement, reduces system costs and helps manage the lifecycle. Significant
218 savings are available in operating, engineering and maintaining the control systems.
219 The objectives of the IEC 62453 series are to support:
220 • universal plant-wide tools for life-cycle management of heterogeneous fieldbus
221 environments, multi-manufacturer devices, function blocks and modular sub-systems for
222 all automation domains (e.g. process automation, factory automation and similar
223 monitoring and control applications);
224 • integrated and consistent life-cycle data exchange within a control system including its
225 fieldbuses, devices, function blocks and modular sub-systems;
226 • simple and powerful manufacturer-independent integration of different automation devices,
227 function blocks and modular sub-systems into the life-cycle management tools of a control
228 system.
______________
1
FDT® is a registered trade name of FDT Group AISBL. This information is given for the convenience of users of this
document and does not constitute an endorsement by IEC of the trademark holder or any of its products. Compliance to this
document does not require use of the trade name. Use of the trade name requires permission of the trade name holder.
---------------------- Page: 10 ----------------------
oSIST prEN IEC 62453-1:2022
– 8 – IEC CDV 62453-1 ED3©IEC 2022
229 The FDT concept supports planning and integration of monitoring and control applications, it
230 does not provide a solution for other engineering tasks such as "electrical wiring planning”,
231 “mechanical planning”. Plant management subjects such as "maintenance planning”, “control
232 optimization”, “data archiving”, are not part of this FDT standard. Some of these aspects may
233 be included in future editions of FDT publications.
234
---------------------- Page: 11 ----------------------
oSIST prEN IEC 62453-1:2022
IEC CDV 62453-1 ED3©IEC 2022 – 9 –
235 FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
236
237 Part 1: Overview and guidance
238
239
240
241 1 Scope
242 This part of IEC 62453 presents an overview and guidance for the IEC 62453 series. It
243 • explains the structure and content of the IEC 62453 series (see Clause 5);
244 • provides explanations of some aspects of the IEC 62453 series that are common to many
245 of the parts of the series;
246 • describes the relationship to some other standards.
247 2 Normative references
248 The following documents, in whole or in part, are normatively referenced in this document and
249 are indispensable for its application. For dated references, only the edition cited applies. For
250 undated references, the latest edition of the referenced document (including any
251 amendments) applies.
252 IEC 61158 (all parts), Industrial communication networks – Fieldbus specifications
253 IEC 61784 (all parts), Industrial communication networks – Profiles
254 3 Terms, definitions, symbols, abbreviations and conventions
255 For the purposes of this document the following terms, definitions, abbreviations and
256 conventions apply.
257 3.1 Terms and definitions
258 3.1.1
259 actor
260 coherent set of roles that users of use cases play when interacting with these use cases
261 Note 1 to entry: An actor has one role for each use case with which it communicates.
262 [SOURCE: ISO/IEC 19501:2005, 4.11.2.1]
263 3.1.2
264 address
265 communication protocol specific access identifier
266 3.1.3
267 application
268 software functional unit that is specific to the solution of a problem in industrial-process
269 measurement and control
270 Note 1 to entry: An application may be distributed among resources, and may communicate with other
271 applications.
---------------------- Page: 12 ----------------------
oSIST prEN IEC 62453-1:2022
– 10 – IEC CDV 62453-1 ED3©IEC 2022
272 3.1.4
273 business object
274 object representing specific behavior (e.g. DTM, BTM and channel)
275 Note 1 to entry: The term business object has been defined originally as part of the design pattern three-tier
276 architecture, where the business object is part of the business layer.
277 3.1.5
278 Block Type Manager
279 BTM
280 specialized DTM to manage and handle a block
281 Note 1 to entry: This note applies to the French language only.
282 3.1.6
283 communication
284 fieldbus protocol specific data transfer
285 3.1.7
286 Communication Channel
287 access point for communication to field device
288 3.1.8
289 configuration
290 system created by configuring the plant components and the topology
291 3.1.9
292 configure
293 setting parameters at the instance data as well as the logical association of plant components
294 to build up the plant topology (off-line)
295 Note 1 to entry: See also parameterize (3.1.38).
296 3.1.10
297 connection
298 established data path for communication with a selected device
299 3.1.11
300 data
301 set of parameter values
302 3.1.12
303 data
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.