IEC 62453-1:2009

IEC 62453-1 ®
Edition 1.0 2009-06
INTERNATIONAL
STANDARD
Field device tool (FDT) interface specification –
Part 1: Overview and guidance
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 Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
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 corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 62453-1 ®
Edition 1.0 2009-06
INTERNATIONAL
STANDARD
Field device tool (FDT) interface specification –
Part 1: Overview and guidance
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
W
ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-88910-715-5
– 2 – 62453-1 © IEC:2009(E)
CONTENTS
FOREWORD.4
INTRODUCTION.6
1 Scope.7
2 Normative references .7
3 Terms, definitions, symbols, abbreviations and conventions .7
3.1 Terms and definitions .7
3.2 Abbreviations .12
3.3 Conventions .12
4 FDT overview .12
4.1 State of the art .12
4.2 Objectives of FDT .13
4.2.1 General features.13
4.2.2 Device and module manufacturer benefits .14
4.2.3 System manufacturer and integrator benefits.14
4.2.4 Other applications .14
4.3 FDT model .15
4.3.1 General .15
4.3.2 Frame Applications.16
4.3.3 Device Type Manager.17
4.3.4 Communication Channel concept.18
4.3.5 Presentation object.20
5 Structure of the IEC 62453 series.20
5.1 Structure overview .20
5.2 Part 2 – Concepts and detailed description.21
5.3 Parts 3xy – Communication profile integration.22
5.3.1 General .22
5.3.2 Communication profile integration – IEC 61784 CPF 1.22
5.3.3 Communication profile integration – IEC 61784 CPF 2.22
5.3.4 Communication profile integration – IEC 61784 CP 3/1 and 3/2 .22
5.3.5 Communication profile integration – IEC 61784 CP 3/4, CP 3/5 and

3/6.22
5.3.6 Communication profile integration – IEC 61784 CPF 6.22
5.3.7 Communication profile integration – IEC 61784 CPF 9.23
5.3.8 Communication profile integration – IEC 61784 CPF 15.23
5.4 Parts 4x – Object model integration profiles .23
5.4.1 General .23
5.4.2 Object model integration profile – Common object model.23
5.5 Parts 5xy – Communication profile implementation.23
5.5.1 General .23
5.5.2 Communication profile integration – IEC 61784 CPF 1.23
5.5.3 Communication profile integration – IEC 61784 CPF 2.24
5.5.4 Communication profile integration – IEC 61784 CP 3/1 and 3/2 .24
5.5.5 Communication profile integration – IEC 61784 CP 3/4, CP 3/5 and
3/6.24
5.5.6 Communication profile integration – IEC 61784 CPF 6.24
5.5.7 Communication profile integration – IEC 61784 CPF 9.24
5.5.8 Communication profile integration – IEC 61784 CPF 15.24

62453-1 © IEC:2009(E) – 3 –
5.6 Parts 6x – DTM styleguides.25
5.6.1 General .25
5.6.2 Device Type Manager (DTM) styleguide for common object model .25
6 Relation of the IEC 62453 series to other standardization activities .25
7 Migration to DTM.29
8 How to read IEC 62453 .30
8.1 Architecture.30
8.2 Dynamic behavior.30
8.3 Structured data types .31
8.4 Fieldbus communication .31
Annex A (informative) UML notation.32
Annex B (informative) Implementation policy.37
Bibliography.38

Figure 1 − Different tools and fieldbusses result in limited integration .13
Figure 2 – Full integration of all devices and modules into a homogeneous system.14
Figure 3 – General architecture and components .15
Figure 4 – FDT software architecture .17
Figure 5 – General FDT client/server relationship .18
Figure 6 – Typical FDT channel architecture .19
Figure 7 – Channel/parameter relationship.20
Figure 8 – Structure of the IEC 62453 series .20
Figure 9 – Standards related to IEC 62453 – in an automation hierarchy .26
Figure 10 – Standards related to IEC 62453 – grouped by purpose.28
Figure 11 – DTM – implementations.30
Figure A.1 – Note .32
Figure A.2 – Class .32
Figure A.3 – Association .32
Figure A.4 – Composition.33
Figure A.5 – Aggregation .33
Figure A.6 – Dependency .33
Figure A.7 – Abstract class, generalization and interface .33
Figure A.8 – Multiplicity .34
Figure A.9 – Elements of UML statechart diagrams.34
Figure A.10 – Example of UML state chart diagram .35
Figure A.11 – UML use case syntax.35
Figure A.12 – UML sequence diagram .36

Table 1 – Overview of related standards .27

– 4 – 62453-1 © IEC:2009(E)
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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
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) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard 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.
This part, in conjunction with the other parts of the first edition of the IEC 62453 series
cancels and replaces IEC/PAS 62453-1, IEC/PAS 62453-2, IEC/PAS 62453-3, IEC/PAS
62453-4 and IEC/PAS 62453-5 published in 2006, and constitutes a technical revision.
The text of this standard is based on the following documents:
FDIS Report on voting
65E/123/FDIS 65E/136/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

62453-1 © IEC:2009(E) – 5 –
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 publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

– 6 – 62453-1 © IEC:2009(E)
INTRODUCTION
Enterprise automation requires 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.
With the integration of fieldbusses into control systems, there are a few other tasks which
need to be performed. In addition to fieldbus- and device-specific tools, there is a need to
integrate these tools into higher-level system-wide planning- or engineering tools. 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 have to be 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
necessary to fully integrate fieldbusses, 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 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.
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
be included in future editions of FDT publications.

62453-1 © IEC:2009(E) – 7 –
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 1: Overview and guidance
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.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
IEC 61158 (all parts), Industrial communication networks – Fieldbus specifications
IEC 61784 (all parts), Industrial communication networks – Profiles
ISO/IEC 19501:2005, Information technology – Open Distributed Processing – Unified
Modeling Language (UML) Version 1.4.2
3 Terms, definitions, symbols, abbreviations and conventions
For the purposes of this document the following terms, definitions and abbreviations apply.
3.1 Terms and definitions
3.1.1
actor
coherent set of roles that users of use cases play when interacting with these use cases
[ISO/IEC 19501]
NOTE An actor has one role for each use case with which it communicates.
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 An application may be distributed among resources, and may communicate with other applications.

– 8 – 62453-1 © IEC:2009(E)
3.1.4
business object
object representing specific behavior (e.g. DTM, BTM and channel)
NOTE The term business object has been defined originally as part of the design pattern 3-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
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
(see also parameterize)
setting parameters at the instance data as well as the logical association of plant components
to build up the plant topology (off-line)
3.1.10
connection
established data path for communication with an selected device
3.1.11
data
set of parameter values
3.1.12
data type
set of values together with a set of permitted operations
[ISO 2382 series]
3.1.13
DCS manufacturer / system manufacturer
manufacturer of the engineering system
3.1.14
device
(see also field device)
a) networked independent physical entity of an industrial automation system capable of
performing specified functions in a particular context and delimited by its interfaces
[IEC 61499-1]
b) entity that performs control, actuating and/or sensing functions and interfaces to other
such entities within an automation system

62453-1 © IEC:2009(E) – 9 –
3.1.15
device manufacturer
manufacturer of fieldbus devices
3.1.16
device type
device characterization based on abstract properties such as manufacturer, fieldbus protocol,
device type identifier, device classification, version information or other information
NOTE 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.17
distributed system
FDT objects that jointly are executed on different PCs in a network
NOTE 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 multi-user system on different PCs)
3.1.18
documentation
human readable information about a device instance
NOTE This may be electronic information in a database.
3.1.19
Device Type Manager (DTM)
a) software component containing device specific application software
b) generic class and means "Type Manager"
NOTE The D is kept because the Acronym is well-known in the market.
3.1.20
DTM device type
software module for a particular device type within the DTM
NOTE A DTM may contain one or more DTM device types
3.1.21
entity
particular thing, such as a person, place, process, object, concept, association, or event
[IEC 61499-1]
3.1.22
field device
(see also device)
3.1.23
Frame Application
FDT runtime environment
3.1.24
FDT model
interface specification for objects and object behavior in a monitoring and control system
3.1.25
function
specific purpose of an entity or its characteristic action
[IEC 61499-1]
– 10 – 62453-1 © IEC:2009(E)
3.1.26
hardware
physical equipment, as opposed to programs, procedures, rules and associated
documentation
[ISO/AFNOR Dictionary of computer science]
3.1.27
implementation
development phase in which the hardware and software of a system become operational
[IEC 61499-1]
3.1.28
instantiation
creation of an instance of a specified type
[IEC 61499-1]
3.1.29
interface
shared boundary between two functional units, defined by functional characteristics, signal
characteristics, or other characteristics as appropriate
[IEC 60050-351]
3.1.30
mapping
set of values having defined correspondence with the quantities or values of another set
[ISO/AFNOR Dictionary of computer science]
3.1.31
multi-user environment
environment which allows operation by more than one user
3.1.32
network
all of the media, connectors, repeaters, routers, gateways and associated node
communication elements by which a given set of communicating devices are interconnected
[IEC 61158-5-X]
NOTE In this document network is used to express that one or more interconnected fieldbus systems with
different protocols can be applied.
3.1.33
nested communication
communication using a hierarchy of communication systems
3.1.34
operation
well-defined action that, when applied to any permissible combination of known entities,
produces a new entity
[ISO/AFNOR Dictionary of computer science]
3.1.35
parameter
variable that is given a constant value for a specified application and that may denote the
application
[ISO/AFNOR Dictionary of computer science]

62453-1 © IEC:2009(E) – 11 –
3.1.36
parameterize
(see also configure)
setting parameters in a device or a block or an object
3.1.37
persistent data
stored data that is preserved through shut down/restart and maintenance activities
3.1.38
Process Channel
representation of process value and its properties
3.1.39
service
functional capability of a resource, which can be modeled by a sequence of service primitives
[IEC 61499-1]
3.1.40
session
instance of user interactions within the FDT model
3.1.41
synchronization
synchronization of data depending on the context where used
NOTE For example, synchronization can occur between the DTM and device or between several DTM instances
having a reference to the same instance data.
3.1.42
system
set of interrelated elements considered in a defined context as a whole and separated from its
environment
[IEC 60050-351]
NOTE 1 Such elements may be both material objects and concepts as well as the results thereof (e.g. forms of
organization, mathematical methods, and programming languages).
NOTE 2 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.
3.1.43
transient data
temporary data which have not been stored (while configuring or parameterizing)
3.1.44
type
software element, which specifies the common attributes shared by all instances of the type
[IEC 61499-1]
3.1.45
variable
software entity that may take different values, one at a time
[IEC 61499-1]
NOTE 1 The values of a variable are usually restricted to a certain data type.

– 12 – 62453-1 © IEC:2009(E)
NOTE 2 Variables are described as input variables, output variables, and internal variables.
3.1.46
use case
specification of a sequence of actions, including variants, that a system (or other entity) can
perform, interacting with actors of the system
[ISO/IEC 19501]
3.2 Abbreviations
BTM Block Type Manager
COM Component Object Model
CP Communication profile
CPF Communication profile family
DCS Distributed control system
DD Device description
DTM Device Type Manager
ERP Enterprise resource planning
FA Frame Application
FB Function block
FDT Field device tool
GUI Graphical user interface
ID Identifier
IDL Interface definition language
I/O Input/output
IT Information technology
MES Manufacturing execution systems
OEM Original equipment manufacturer
OLE Object Linking and Embedding
OPC Open connectivity via open standards (originally: OLE for
Process Control)
PC Personal computer
PLC Programmable logic controller
SCADA Supervisory, control and data acquisition
UML Unified modeling language
UUID Universal unique identifier
XML Extensible markup language

3.3 Conventions
The conventions for UML notation used in the IEC 62453 series is defined in Annex A.
4 FDT overview
4.1 State of the art
In industrial automation, a control system often comprises many binary and analog
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.
62453-1 © IEC:2009(E) – 13 –
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.
Large control systems
> 10 manufacturers
> 100 device types
Function Chart
> 10000 I/Os
Tool 1
Fieldbus Type 1
Tool 2
Device description
Function blocks
Device addresses
Fieldbus Type 2
Device parameters
Device I/Os
Link
Type 3
Tool n
Tool 3
IEC  1047/09
Figure 1 − Different tools and fieldbusses 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
fieldbusses to the individual field devices.
FDT supports:
• central facilities for planning, diagnostics and service with direct access to all devices;
• integrated, consistent configuration and documentation of the automation system, its
fieldbusses and devices;
• organization of common data for the automation system and the field devices;

– 14 – 62453-1 © IEC:2009(E)
• central data management and data security;
• simple, fast integration of different device and module types into the automation system.
Integration of field devices into the engineering systems of automation technology can cover a
small set of configuration, service and diagnostic functions as well as large set of functions.
4.2.2 Device and module manufacturer benefits
FDT technology allows integration of individual device and module properties, including
specific characteristics and special features for different device and module types. Planning
and service tools provided by the manufacturer can be integrated as device or module-
specific software components into the engineering system. The manufacturer is able to define
the configuration, service and diagnostic functions and also to design the appearance of
devices and modules in the engineering environment of the automation system.
This reduces the costs for the manufacturer, as one standardized software component is able
to support configuration, service and diagnostic functions for the device in any automation
system. It also eliminates frequent project-specific or control system-specific adaptations,
which have to be developed and maintained for multiple device and module types in the
absence of a standard.
4.2.3 System manufacturer and integrator benefits
The control system manufacturer or integrator has to implement the defined interfaces for the
integration of all fieldbus devices and modules only once. Manufacturer-specific and/or
device-specific implementations and their maintenance are eliminated.
Master configuration
Function chart HMI configuration
SITRANS P
Device configuration
EC001 JC001
Reactor
Device diagnosis
> 10 manufacturers
> 100 device types
Common engineering data
> 10000 I/Os
PLD data
Fieldbus
I/O type
Range
Limit s
I/O channel assignment
Device parameters
IEC  1048/09
Figure 2 – Full integration of all devices and modules into a homogeneous system
4.2.4 Other applications
Although FDT is primarily designed to control device functionality and for accessing data to
configure parts of the control system, FDT interfaces can be used in many places within an
application. At the lowest level, they can get raw data from the devices and modules in a
SCADA, DCS or PLC to configure the bus master. At a higher level the Frame Application can

62453-1 © IEC:2009(E) – 15 –
start device specific diagnosis applications via the DTM. The architecture and design makes it
possible to build and to integrate scalable DTMs, where the functionality depends on the
capabilities of the device.
4.3 FDT model
4.3.1 General
FDT facilitates the interaction between device-specific software components, fieldbus
interface-specific software components and host systems (see Figure 3).
• The device-specific software components are called Device Type Managers (DTMs).
• The fieldbus interface-specific software components are called Communication Channels
• The host systems are called Frame Applications.

IEC  1049/09
Figure 3 – General architecture and components
A Frame Application provides the runtime environment for the DTMs. Typically, the Frame
Application comprises client applications that use DTMs, a database for persistent storage of
device data, and a Communication Channel to the field devices. Client applications are single
applications focusing on specific aspects such as configuration, observation, channel
assignment, and using the service provided by the DTMs.
A DTM encapsulates device-specific software applications and protocol specific definitions.
Thus a Frame Application is able to handle any type of device by integrating corresponding
DTMs without the need for device or fieldbus specific knowledge.

– 16 – 62453-1 © IEC:2009(E)
Device and module-specific software components are of several types to cover integration of
products commonly used in automation systems. DTM objects can, for example, represent
normal measurement and control devices. There are specializations of DTMs which represent:
• software entities or function blocks that are movable and may be hosted by different
modules in a network, also known as Block DTM (BTM) objects;
• modular equipment combinations, such as I/O stations with plug in boards to provide
combinations of I/O and control functions also known as Module DTM objects.
A Communication Channel represents the entry point to a fieldbus or point-to-point
communication. It provides fieldbus interface independent services. In general, the protocol
specific services are mapped to the services provided by the channel. The services may be
used by the Frame Application or a DTM to exchange data with a connected device or to
initiate a function (e.g. identification request, device reset, broad-cast, etc.).
FDT defines the services each of the components has to provide and the data which is
exchanged by those. The services are defined in a fieldbus independent way, but some
exchange fieldbus specific data. The content and data format for manufacturer independent
fieldbuses is defined in the IEC 62453-3xy specifications defining the protocol profile
integration in FDT. FDT also enables manufacturers to define their own content and data
formats, for example for a manufacturer specific fieldbus or point-to-point communication.
The main features of the FDT concept are:
• Frame Application is the representation of the host tool where the DTMs are interacting
with the control system, maintenance or engineering application;
• DTM is the main concept and can be applied for simple devices but also for modular
devices, software components (function block);
• nested communication is provided to meet the requirement of heterogeneous and
hierarchical networks where the intelligent field devices are connected. This is the
background for various communication parts in the standard;
• graphical interfaces are provided to provide interactive access to the functionality of the
intelligent field devices and its DTM to the human beings. These aspects are represented
by so called presentation objects.
4.3.2 Frame Applications
Frame Applications provide the runtime environment for the FDT system. Depending on the
intended use Frame Applications may have different appearances (e.g. standalone
configuration and engineering system). The following general requirements apply to all Frame
Applications:
• device and module-specific knowledge is not necessary;
• ability to manage all DTM instances and store instance data;
• ability to manage and create DTM communications and connections (including any
necessary message routing);
• guarantee of system-wide consistent configuration;
• enables multi-user and server/client operation (optional);
• takes care of data versions and consistency.
FDT is a specification to facilitate the interaction between device-specific objects (i.e.
presentation and DTM) and the Frame Application. This is shown in Figure 4.

62453-1 © IEC:2009(E) – 17 –
IEC  1050/09
Figure 4 – FDT software architecture
A Frame Application provides the runtime environment for device specific objects. Typically,
the Frame Application comprises client applications that use DTMs, a database for persistent
storage of device data, and a communication link to the field devices.
Client applications are single applications focusing on specific aspects such as configuration,
observation, channel assignment, and using the functionality provided by the DTM as a
server.
NOTE The IEC 62453 series distinguishes between the specification of the interactions between objects (e.g.
Frame Applications and DTMs) and the implementation technology for the implementation of those objects. It
specifies only the behavior that the objects are expected to provide to client applications that use them.
4.3.3 Device Type Manager
DTM objects are supplied by the device manufacturer together with the device. The following
properties are characteristic for the DTM:
• generally not a standalone tool;
• graphical user interfaces as defined by this specification;
• all rules of the device are known;
• all user dialogs are contained;
• user interface (multilingual including help system);
• parameter validity check (also depending on other device-specific parameters);
• automatic generation of dependent parameters;
• processing sequences are defined for complex calibration, and setup procedures where
needed;
• reading and writing of parameters from/to the field device;

– 18 – 62453-1 © IEC:2009(E)
• diagnostic functions customized for the device;
• provision of the type-specific data for establishment of communication;
• provision of device/instance-specific data, for example to be used in function planning;
• device or instance specific documentation;
• no direct connection to any other device;
• no information on the engineering environment;
• support for one or more device types.
Each device manufacturer chooses the number and range of functions for a DTM, as required
by the functional capabilities of the device(s) it supports. A DTM covers at least one field
device. DTMs can, however, also cover device families (for example, pressure transmitters) or
the entire product range of a manufacturer. Communication (via the various bus systems of a
control system) and data management are handled via the interfaces of the engineering tool.
Within the framework of overall system planning or plant management, a DTM must always be
integrated into the appropriate engineering tool. To avoid data consistency problems, parallel
access by standalone tools and the system’s engineering tool to access the same devices are
not recommended. Parallel standalone operation may be implemented in special cases for
example when migrating from a standalone tool to a DTM.
A DTM is installed as a component of an engineering tool or any other application that
manages the device instances, and provides the communication mechanisms and supports
the component with device-specific tasks. In the following, those applications are referred to
as ‘Frame Applications’.
4.3.4 Communication Channel concept
The IEC 62453 series specifies the FDT objects and their interfaces which support interaction
between a Frame Application and a device or module-specific application called a DTM.
Frame applications can be engineering tools, operator stations or standalone tools. The
Frame Applications act as clients and the DTMs act as servers.
DTMs can be connected to monolithic Frame Applications or to distributed Frame Applications
based on different components provided by one or more manufacturers. Frame Applications
can manage and integrate multiple DTMs provided by one or more manufacturers (see
Figure 5).
DTM
Server
Vendor A
Frame Frame
DTM
Application Application
Server
Engineering Operater Station
Vendor B
vendor #1 vendor #1
DTM
Server
Vendor C
Frame
Application
Standalone Tool
vendor #2
IEC  1051/09
Figure 5 – General FDT client/server relationship

62453-1 © IEC:2009(E) – 19 –
DTMs are composed of a server objec
...