IEC 62453-1:2025

IEC 62453-1 ®
Edition 3.0 2025-08
INTERNATIONAL
STANDARD
REDLINE VERSION
Field device tool (FDT) interface specification -
Part 1: Overview and guidance
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8327-0658-9
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or
by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either
IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC copyright
or have an enquiry about obtaining additional rights to this publication, please contact the address below or your local
IEC member National Committee for further information.

IEC Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - IEC Products & Services Portal - products.iec.ch
webstore.iec.ch/advsearchform Discover our powerful search engine and read freely all the
The advanced search enables to find IEC publications by a publications previews, graphical symbols and the glossary.
variety of criteria (reference number, text, technical With a subscription you will always have access to up to date
committee, …). It also gives information on projects, content tailored to your needs.
replaced and withdrawn publications.
Electropedia - www.electropedia.org
The world's leading online dictionary on electrotechnology,
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published containing more than 22 500 terminological entries in English
details all new publications released. Available online and and French, with equivalent terms in 25 additional languages.
once a month by email. Also known as the International Electrotechnical Vocabulary
(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc
If you wish to give us your feedback on this publication or
need further assistance, please contact the Customer
Service Centre: sales@iec.ch.
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 9
2 Normative references . 9
3 Terms, definitions, symbols, abbreviated terms and conventions . 9
3.1 Terms and definitions. 9
3.2 Abbreviated terms . 15
3.3 Conventions . 15
4 FDT overview . 15
4.1 State of the art . 15
4.2 Objectives of FDT . 16
4.2.1 General features . 16
4.2.2 Device and module manufacturer benefits . 17
4.2.3 System manufacturer and integrator benefits . 18
4.2.4 Other applications . 18
4.3 FDT model . 18
4.3.1 General . 18
4.3.2 Frame Applications . 20
4.3.3 Device Type Manager . 21
4.3.4 Communication Channel concept . 22
4.3.5 Presentation object . 24
5 Structure of the IEC 62453 series . 24
5.1 Structure overview . 24
5.2 Part 2 – Concepts and detailed description . 27
5.3 Parts 3xy – Communication profile integration . 27
5.3.1 General . 27
5.3.2 Communication profile integration – IEC 61784 CPF 1 . 27
5.3.3 Communication profile integration – IEC 61784 CPF 2 . 28
5.3.4 Communication profile integration – IEC 61784 CP 3/1 and 3/2 . 28
5.3.5 Communication profile integration – IEC 61784 CP 3/4, CP 3/5 and 3/6 . 28
5.3.6 Communication profile integration – IEC 61784 CPF 6 . 28
5.3.7 Communication profile integration – IEC 61784 CPF 9 . 28
5.3.8 Communication profile integration – IEC 61784 CPF 15 . 28
5.4 Parts 4z – Object model integration profiles . 28
5.4.1 General . 28
5.4.2 Object model integration profile – Common object model (COM) . 29
5.4.3 Object model integration profile – Common language infrastructure
(CLI) . 29
5.4.4 Object model integration profile – CLI and HTML . 29
5.5 Parts 51-xy/52-xy/53-xy – Communication profile implementation . 29
5.5.1 General . 29
5.5.2 Communication profile implementation – IEC 61784 CPF 1 . 29
5.5.3 Communication profile implementation – IEC 61784 CPF 2 . 29
5.5.4 Communication profile implementation – IEC 61784 CP 3/1 and 3/2 . 30
5.5.5 Communication profile implementation – IEC 61784 CP 3/4,
CP 3/5 and 3/6 . 30
5.5.6 Communication profile implementation – IEC 61784 CPF 6 . 30
5.5.7 Communication profile implementation – IEC 61784 CPF 9 . 30
5.5.8 Communication profile implementation – IEC 61784 CPF 15 . 30
5.6 Parts 6z – DTM styleguides . 30
5.6.1 General . 30
5.6.2 Device Type Manager (DTM) styleguide for common object model . 30
5.6.3 Field Device Tool (FDT) styleguide for common language infrastructure . 30
5.7 Part 71 – OPC UA Information Model for FDT . 30
6 Relation of the IEC 62453 series to other standardization activities . 31
7 Migration to DTM . 36
8 How to read IEC 62453. 37
8.1 Architecture . 37
8.2 Dynamic behaviour . 37
8.3 Structured data types . 38
8.4 Fieldbus communication . 38
Annex A (informativenormative) UML notation . 39
A.1 Common model elements . 39
A.1.1 General . 39
A.1.2 Note . 39
A.2 Class diagram . 39
A.2.1 General . 39
A.2.2 Class . 39
A.2.3 Abstract class . 40
A.2.4 Association . 40
A.2.5 Composition . 40
A.2.6 Aggregation . 40
A.2.7 Dependency . 41
A.2.8 Association class . 41
A.2.9 Generalization . 41
A.2.10 Interface . 42
A.2.11 Multiplicity . 42
A.2.12 Enumeration class . 42
A.3 Component diagram . 43
A.3.1 General . 43
A.3.2 Component . 43
A.4 Statechart diagram . 43
A.4.1 General . 43
A.4.2 State . 43
A.4.3 Initial state . 44
A.4.4 Final state . 44
A.4.5 Composite state. 44
A.5 Use case diagram . 44
A.5.1 General . 44
A.5.2 Actor . 45
A.5.3 Use case . 45
A.5.4 Inheritance relation . 45
A.6 Sequence diagram . 45
A.6.1 General . 45
A.6.2 Frame . 47
A.6.3 Object with life line . 47
A.6.4 Method calls . 47
A.6.5 State and constraint. 48
A.6.6 Alternative, optional and repetitive execution sequence . 49
A.6.7 Break notation . 50
A.6.8 Interaction references . 50
A.7 Object diagram . 50
Annex B (informative) Implementation policy . 51
Bibliography . 52

Figure 1 − Different tools and fieldbuses result in limited integration . 16
Figure 2 – Full integration of all devices and modules into a homogeneous system . 17
Figure 3 – General architecture and components . 19
Figure 4 – FDT software architecture . 21
Figure 5 – General FDT client/server relationship . 22
Figure 6 – Typical FDT channel architecture . 23
Figure 7 – Channel/parameter relationship. 24
Figure 8 – Structure of the IEC 62453 series . 25
Figure 9 – Standards related to IEC 62453 in an automation hierarchy . 31
Figure 10 – Standards related to IEC 62453 – Grouped by purpose . 35
Figure 11 – DTM implementations . 37
Figure A.1 – Note . 39
Figure A.2 – Class . 39
Figure A.3 – Icons for class members . 39
Figure A.4 – Association . 40
Figure A.5 – Navigable Association . 40
Figure A.6 – Composition . 40
Figure A.7 – Aggregation . 40
Figure A.8 – Dependency . 41
Figure A.9 – Association class . 41
Figure A.10 – Abstract class, generalization and interface . 41
Figure A.11 – Interface related notations . 42
Figure A.12 – Multiplicity . 42
Figure A.13 – Enumeration datatype . 43
Figure A.14 – Component . 43
Figure A.15 – Elements of UML statechart diagrams . 43
Figure A.16 – Example of UML state chart diagram . 44
Figure A.17 – UML use case syntax . 45
Figure A.18 – UML sequence diagram . 46
Figure A.19 – Empty UML sequence diagram frame . 47
Figure A.20 – Object with life line and activation . 47
Figure A.21 – Method calls . 48
Figure A.22 – Modelling guarded call and multiple calls . 48
Figure A.23 – Call to itself. 48
Figure A.24 – Continuation / StateInvariant . 49
Figure A.25 – Alternative fragment . 49
Figure A.26 – Option fragment . 49
Figure A.27 – Loop combination fragment . 49
Figure A.28 – Break notation . 50
Figure A.29 – Sequence reference . 50
Figure A.30 – Objects . 50
Figure A.31 – Object link . 50

Table 1 – Overview of IEC 62453 series . 27
Table 2 – Overview of related standards . 32

INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
Field device tool (FDT) interface specification -
Part 1: Overview and guidance
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch. IEC
shall not be held responsible for identifying any or all such patent rights.
This redline version of the official IEC Standard allows the user to identify the changes made
to the previous edition IEC 62453-1:2016. A vertical bar appears in the margin wherever a
change has been made. Additions are in green text, deletions are in strikethrough red text.

IEC 62453-1 has been prepared by subcommittee 65E: Devices and integration in enterprise
systems, of IEC technical committee 65: Industrial-process measurement, control and
automation. It is an International Standard.
This third edition cancels and replaces the first edition published in 2016. This edition
constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous
edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
The text of this International Standard is based on the following documents:
Draft Report on voting
65E/1173/FDIS 65E/1176/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
A list of all parts of the IEC 62453 series, under the general title Field Device Tool (FDT)
interface specification, can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
INTRODUCTION
Enterprise automation requires employs two main data flows: a “vertical” data flow from
enterprise level down to the field devices including signals and configuration data, and a
“horizontal” communication between field devices operating on the same or different
communication technologies.
ieldbuses into control systems, there are a few additional tasks to be
With the integration of f
performed. They may can result in a large number of fieldbus- and device-specific tools in
addition to system and engineering tools. Integration of these tools into higher-level system-
wide planning or engineering tools is an advantage. In particular, for use in extensive and
heterogeneous control systems, typically in the area of the process industry, the unambiguous
definition of engineering interfaces that are easy to use for all those involved is of great
importance.
Several different manufacturer specific tools are used. The data in these tools are often invisible
data islands from the viewpoint of system life-cycle management and plant-wide automation.
To ensure the consistent management of a plant-wide control and automation technology, it is
important to fully integrate fieldbuses, devices and sub-systems as a seamless part of a wide
range of automation tasks covering the whole automation life cycle.
IEC 62453 provides an interface specification for developers of FDT (Field Device Tool)
components to support function control and data access within a client/server architecture. The
availability of this standard interface facilitates development of servers and clients by multiple
manufacturers and supports open interoperation.
A device or module-specific software component, called a DTM (Device Type Manager) is
supplied by a manufacturer with the related device type or software entity type. Each DTM can
be integrated into engineering tools via defined FDT interfaces. This approach to integration is
in general open for all fieldbusses and thus supports integration of different devices and
software modules into heterogeneous control systems.
The IEC 62453 common application interface supports the interests of application developers,
system integrators, and manufacturers of field devices and network components. It also
simplifies procurement, reduces system costs and helps manage the lifecycle. Significant
savings are available in operating, engineering and maintaining the control systems.
The objectives of the IEC 62453 series are to support:
• universal plant-wide tools for life-cycle management of heterogeneous fieldbus
environments, multi-manufacturer devices, function blocks and modular sub-systems for all
automation domains (e.g. process automation, factory automation and similar monitoring
and control applications);
• integrated and consistent life-cycle data exchange within a control system including its
fieldbuses, devices, function blocks and modular sub-systems;
• simple and powerful manufacturer-independent integration of different automation devices,
function blocks and modular sub-systems into the life-cycle management tools of a control
system.
___________
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.
The FDT concept supports planning and integration of monitoring and control applications, it
does not provide a solution for other engineering tasks such as "electrical wiring planning”,
“mechanical planning”. Plant management subjects such as "maintenance planning”, “control
optimization”, “data archiving”, are not part of this FDT standard. Some of these aspects may
can be included in future editions of FDT publications.

1 Scope
This part of IEC 62453 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many
of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments)
applies.
IEC 61158 (all parts), Industrial communication networks – Fieldbus specifications
IEC 61784 (all parts), Industrial communication networks – Profiles
There are no normative references in this document.
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document and of the IEC 62453 series, the following terms and
definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http:www.iso.org/obp
3.1.1
actor
coherent set of roles that users of use cases play when interacting with these use cases
Note 1 to entry: An actor has one role for each use case with which it communicates.
[SOURCE: ISO/IEC 19501:2005, 4.11.2.1]
3.1.2
address
communication protocol specific access identifier
3.1.3
application
software functional unit that is specific to the solution of a problem in industrial-process
measurement and control
Note 1 to entry: An application may be distributed among resources, and may communicate with other applications.
3.1.4
business object
object representing specific behaviour (e.g. DTM, BTM and channel)
Note 1 to entry: The term business object has been defined originally as part of the design pattern three-tier
architecture, where the business object is part of the business layer.
3.1.5
Block Type Manager
BTM
specialized DTM to manage and handle a block
Note 1 to entry: This note applies to the French language only.
3.1.6
communication
fieldbus protocol specific data transfer
3.1.7
Communication Channel
access point for communication to field device
3.1.8
configuration
system created by configuring the plant components and the topology
3.1.9
configure
setting parameters at the instance data as well as the logical association of plant components
to build up the plant topology (off-line)
Note 1 to entry: See also parameterize (3.1.38).
3.1.10
connection
established data path for communication with a selected device
3.1.11
data
set of parameter values
3.1.12
data type
defined set of data objects of a specified data structure and a set of permissible operations,
such that these data objects act as operands in the execution of any one of these operations
[SOURCE: ISO/IEC 2382-15:1999, 15.04.01 (2382)]
3.1.13
DCS manufacturer
system manufacturer
manufacturer of the control system
Note 1 to entry: This note applies to the French language only.
3.1.14
device
independent physical entity of an automation system capable of performing specified functions
in a particular context and delimited by its interfaces
[SOURCE: IEC 61499-1:2012, 3.29, modified – The note has been deleted The words “of an
automation system” have been added, the expression “one or more specified functions” has
been replaced by “specified functions” and the note has been deleted.]
3.1.15
field device
networked independent physical entity of an automation system capable of performing specified
functions in a particular context and delimited by its interfaces
[SOURCE: IEC 61375-3-3:2012, 3.1.3]
3.1.16
device manufacturer
manufacturer of fieldbus devices
3.1.17
device type
device characterization based on abstract properties such as manufacturer, fieldbus protocol,
device type identifier, device classification, version information or other information
Note 1 to entry: The scope of such characterizations can vary depending on the properties that are used in the
definition of such a set and is manufacturer specific for each DTM.
3.1.18
distributed system
FDT objects that jointly are executed on different PCs in a network
Note 1 to entry: The implementation of such a distributed system is vendor specific (for example: DTM and
Presentation are executed on different PCs or DTMs are executed in a multi-user system on different PCs).
Note 2 to entry: This note applies to the French language only.
3.1.19
documentation
human readable information about a device instance
Note 1 to entry: This may can be electronic information in a database.
3.1.20
Device Type Manager
DTM
software component containing device-specific application software
Note 1 to entry: The DTM is a generic class and means "Type Manager". The D is kept because the acronym is
well-known in the market.
Note 2 to entry: This note applies to the French language only.
3.1.21
DTM device type
software module for a particular device type within the DTM
Note 1 to entry: A DTM may can contain one or more DTM device types.
3.1.22
entity
particular thing, such as a person, place, process, object, concept, association, or event
[SOURCE: IEC 61499-1:2012, 3.31]
3.1.23
Frame Application
FDT runtime environment
3.1.24
FDT model
interface specification for objects and object behaviour in a monitoring and control system
3.1.25
function
specific purpose of an entity or its characteristic action
[SOURCE: IEC 61499-1:2012, 3.44]
3.1.26
Generic DTM
DTM which interprets device type or domain specific device descriptions and provides the FDT
interfaces
Note 1 to entry: This note applies to the French language only.
3.1.27
hardware
physical equipment, as opposed to programs, procedures, rules and associated documentation
[SOURCE: IEC 61499-1:2012, 3.49]
3.1.28
implementation
development phase in which the hardware and software of a system become operational
[SOURCE: IEC 61499-1:2012, 3.51]
3.1.29
instantiation
creation of an instance of a specified type
[SOURCE: IEC 61499-1:2012, 3.57]
3.1.30
interface
shared boundary between two functional units, defined by functional characteristics, signal
characteristics, or other characteristics as appropriate
[SOURCE: IEC 60050-351:2013, 351-42-25, modified – The notes have been deleted.]
3.1.31
Interpreter DTM
generic DTM which interprets device descriptions
3.1.32
mapping
set of features or attributes having defined correspondence with the members of another set
[SOURCE: IEC 61499-1:2012, 3.66]
3.1.33
multi-user environment
environment which allows operation by more than one user
3.1.34
network
all of the media, connectors, repeaters, routers, gateways and associated node communication
elements by which a given set of communicating devices are interconnected
Note 1 to entry: In this document, network is used to express that one or more interconnected fieldbus systems
with different protocols can be applied.
[SOURCE: IEC 61158-1:2014, 3.1.5, modified – Note 1 has been added.]
3.1.35
nested communication
communication using a hierarchy of communication systems
3.1.36
operation
well-defined action that, when applied to any permissible combination of known entities,
produces a new entity
[SOURCE: IEC 61499-1:2012, 3.73]
3.1.37
parameter
variable that is given a constant value for a specified application and that may denote the
application
[SOURCE: IEC 61499-1:2012, 3.75]
3.1.38
parameterize
setting parameters in a device or a block or an object
Note 1 to entry: See also configure (3.1.9).
3.1.39
persistent data
stored data that is preserved through shutdown/restart and maintenance activities
3.1.40
Process Channel
representation of process value and its properties
3.1.41
service
functional capability of a resource which can be modeled by a sequence of service primitives
[SOURCE: IEC 61499-1:2012, 3.87]
3.1.42
session
instance of user interactions within the FDT model
3.1.43
synchronization
synchronization of data depending on the context where used
Note 1 to entry: For example, synchronization can occur between the DTM and the device or between several DTM
instances having a reference to the same instance data.
3.1.44
system
set of interrelated elements considered in a defined context as a whole and separated from
their environment
Note 1 to entry: Elements of a system may be natural or man-made material objects, as well as modes of thinking
and the results thereof (for example forms of organization, mathematical methods, and programming languages).
Note 2 to entry: The system is considered to be separated from the environment and other external systems by an
imaginary surface, which can cut the links between them and the considered system.
[SOURCE: IEC 60050-351:2013, 351-42-08, modified – some notes have Note 1 has been
deleted.]
3.1.45
transient data
temporary data which have not been stored (while configuring or parameterizing)
3.1.46
type
software element which specifies the common attributes shared by all instances of the type
[SOURCE: IEC 61499-1:2012, 3.99]
3.1.47
variable
ake different values, one at a time
software entity that may can t
Note 1 to entry: The values of a variable are usually restricted to a certain data type.
Note 2 to entry: Variables are described as input variables, output variables, internal variables and temporary
variables.
[SOURCE: IEC 61499-1:2012, 3.102]
3.1.48
use case
class specification of a sequence of actions, including variants, that a system (or other entity)
can perform, interacting with actors of the system
[SOURCE: IEC TR 62390:2005, 3.1.26]
3.2 Abbreviated terms
BTM Block Type Manager
CLI Common Language Infrastructure
COM Component Object Model [IEC 62541-1]
CP Communication profile [IEC 61784-1]
CPF Communication profile family [IEC 61784-1]
DCS Distributed control system [IEC 62351-2]
DD Device description
DTM Device Type Manager
ERP Enterprise resource planning
FA Frame Application
FB Function block [IEC 61784-3-3]
FDT Field device tool
GUI Graphical user interface
ID Identifier
IDL Interface definition language [ISO/IEC 24775]
I/O Input/output
IT Information technology [IEC 80001-2-1]
MES Manufacturing execution systems
OEM Original equipment manufacturer [IEC 62402]
OLE Object Linking and Embedding [IEC 61970-2]
OPC Open connectivity via open standards
(originally: OLE for Process Control) [IEC 61970-2]
PC Personal computer [IEC 62481-1]
PLC Programmable logic controller [IEC 61131-1]
SCADA Supervisory, control and data acquisition [IEC 62443-1-1]
UML Unified modeling language [ISO/IEC 19501]
UUID Universal unique identifier [IEC 62755]
XML Extensible markup language [IEC 61970-2]

3.3 Conventions
The conventions for UML notation that shall be used in the IEC 62453 series are defined in
Annex A.
4 FDT overview
4.1 State of the art
In industrial automation, a control system often comprises many binary and analogue
input/output signals transmitted via a communication network. Numerous field devices provided
by different manufacturers have to be included in the network by direct connection or I/O
multiplex units. Many applications use more than 100 different field device types from various
device manufacturers.
Each device has specific configuration and parameterization functions to support its designed
task. These device-specific properties and settings have to be taken into consideration when
configuring a fieldbus coupler and bus communication for the device. The device presence and
its capability have to be made known to the control system. Device input and output signals and
function block services need to be effectively integrated into the planning of the control system.
In the absence of a common interface standard, the large number of different device types and
suppliers within a control system project makes the configuration task difficult and time-
consuming. Various different tools have to be used (see Figure 1). The user requirement for
consistency of data, documentation and application configurations can only be guaranteed by
intensive and costly system testing.
A common location for service and diagnostic tasks in the control system does not fully cover
the functional capabilities of available fieldbus devices nor does it guarantee that different
device or module-specific tools can be integrated into other system software tools. Typically,
device-specific tools can only be connected directly to a specific fieldbus or directly to a specific
field device type.
Figure 1 − Different tools and fieldbuses result in limited integration
4.2 Objectives of FDT
4.2.1 General features
Full integration of fieldbus devices or modules into automation systems requires a
communication path from central engineering or operator terminals via the system and
fieldbuses to the individual field devices.
IE
...