IEC TR 62795:2013

Interoperation guide of field device tool (FDT) / device type manager (DTM) and electronic device description language (EDDL)

IEC/TR 62795:2013(E) provides the general requirements for converting an EDD into a DTM. Using this TR, an FDT/DTM developer can develop an EDD-DTM conversion tool that can be used to import, parse, and manage EDD to generate the corresponding DTM. A conversion tool versus a DTM written independent of an EDD helps the DTM generation to maintain consistency in function, data and presentation styles.

General Information

• Status: Withdrawn
• Publication Date: 24-Sep-2013
• Withdrawal Date: 02-Apr-2017
• ICS: 25.040.40 - Industrial process measurement and control
• ICS: 35.240.50 - IT applications in industry
• Technical Committee: SC 65E - Devices and integration in enterprise systems
• Current Stage: WPUB - Publication withdrawn
• Start Date: 03-Nov-2017
• Completion Date: 03-Apr-2017

Standards Content (Sample)

IEC/TR 62795
®

Edition 1.0 2013-09
TECHNICAL
REPORT

colour
inside


Interoperation guide for field device tool (FDT) / device type manager (DTM) and
electronic device description language (EDDL)

IEC/TR 62795:2013(E)

---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2013 IEC, Geneva, Switzerland

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 Tel.: [phone]
3, rue de Varembé Fax: [phone]
CH-1211 Geneva 20 [e-mail]
Switzerland 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.

Useful links:

IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org
The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and
by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and
committee,…). definitions in English and French, with equivalent terms in
It also gives information on projects, replaced and additional languages. Also known as the International
withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.

IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc
Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication
details all new publications released. Available on-line and or need further assistance, please contact the
also once a month by email. Customer Service Centre: [e-mail].

---------------------- Page: 2 ----------------------
IEC/TR 62795

®


Edition 1.0 2013-09




TECHNICAL



REPORT








colour

inside










Interoperation guide for field device tool (FDT) / device type manager (DTM) and

electronic device description language (EDDL)



























INTERNATIONAL

ELECTROTECHNICAL

COMMISSION

PRICE CODE
U


ICS 25.040.40; 35.240.50 ISBN 978-2-8322-1116-8



  Warning! Make sure that you obtained this publication from an authorized distributor.


® Registered trademark of the International Electrotechnical Commission

---------------------- Page: 3 ----------------------
– 2 – TR 62795 © IEC:2013(E)
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions, and abbreviations . 7
3.1 Terms and definitions . 7
3.2 Abbreviations . 8
4 Typical methods to convert EDD to FDT/DTM . 8
4.1 Overview . 8
4.2 Using a universal DTM to integrate the EDD document . 9
4.2.1 General . 9
4.2.2 Basic contents of the transformation from EDD to DTM. 9
4.2.3 Procedure . 10
4.3 Using a converting tool to integrate EDD documents . 11
4.3.1 General . 11
4.3.2 Basic contents . 12
4.3.3 Procedure . 12
4.4 Generate an FDT/DTM based on EDD documents . 13
5 General requirements for the conversion from EDD to FDT . 13
5.1 Overview . 13
5.2 Requirements for the agent interpreter . 13
5.2.1 General . 13
5.2.2 Standardized requirements of the basic parameters description
. 16
5.2.3 Standardized requirements of the fieldbus communication
protocol mapping . 17
5.2.4 Standardized requirements of the device parameters visual
description . 17
5.2.5 Standardized requirements of error handling . 18
5.3 The requirements of EDD document format . 19
5.4 Requirements for EDD storage management. 19
5.5 The user interface style requirements of FDT/DTM converted from EDDL . 20
5.5.1 Overview . 20
5.5.2 Basic requirements of the FDT/DTM interface design . 20
5.5.3 FDT/DTM user interface . 20
5.5.4 FDT/DTM user interface areas . 21
5.5.5 Parameter handling . 24
Annex A (informative) Standard user interface of FDT/DTM . 26
Bibliography . 27

Figure 1 – EDD to DTM conversion flowchart . 11
Figure 2 – EDD to DTM general process of conversion flowchart . 12
Figure 3 – Basic parameter description mapping . 17
Figure 4 – Communication mapping . 17
Figure 5 – User interface mapping . 18
Figure A.1 – Specific example of FDT/DTM’s standard user interface . 26

---------------------- Page: 4 ----------------------
TR 62795 © IEC:2013(E) – 3 –

Table 1 – EDD basic elements . 14
Table 2 – The related interfaces of DTM . 15
Table 3 – Standard user interface of FDT/DTM . 21
Table 4 – Contents of Identification Area . 21
Table 5 – Contents of Action Area . 22
Table 6 – Elements of the Status Bar . 23
Table 7 – Connection states of DTM . 23
Table 8 – Data source states . 24
Table 9 – States of the instance data set . 24
Table 10 – Device diagnostic states . 24

---------------------- Page: 5 ----------------------
– 4 – TR 62795 © IEC:2013(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________

INTEROPERATION GUIDE FOR FIELD DEVICE TOOL (FDT) /
DEVICE TYPE MANAGER (DTM) AND ELECTRONIC DEVICE
DESCRIPTION LANGUAGE (EDDL)


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) 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.
The main task of IEC technical committees is to prepare International Standards. However, a
technical committee may propose the publication of a technical report when it has collected data
of a different kind from that which is normally published as an International Standard, for
example "state of the art".
IEC 62795, which is a technical report, has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee 65: Industrial-process
measurement, control and automation.
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
65E/240/DTR 65E/330/RVC

Full information on the voting for the approval of this technical report 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.

---------------------- Page: 6 ----------------------
TR 62795 © IEC:2013(E) – 5 –
The committee has decided that the contents of this publication will remain unchanged until the
stability 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.

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.

---------------------- Page: 7 ----------------------
– 6 – TR 62795 © IEC:2013(E)
INTRODUCTION
At present, there are two International Standards for device integration that describe the
properties of automation system components to be used in host systems. They are IEC 61804
for electronic device description language (EDDL) and IEC 62453 for field device tools (FDT),
with both standards having their own characteristics. The number of manufacturers and users
using EDDL or FDT technologies is increasing, and investment in both of them is therefore
increasing too.
EDDL technology enables the integration of real product details using the tools of the
engineering life cycle and specifies EDDL as a generic language for describing the properties of
automation system components. EDDL technology allows to transfer the properties of a device
to a data set, called electronic device description (EDD), that can be interpreted by configuration
tools in a host system. EDD files, representing the behavior and attributes of a device, can be
stored in the field device or control system. The interaction between a field device and a control
system uses various communication protocols such as specified in IEC 61784-1, CP 1-1 (FF) or
®
1
IEC 61784-1, CP 9-1 (HART ).
FDT is an open and independent software interface specification. An FDT specification
describes software interface and relationships within the framework of the project (FDT
container, FDT frame applications) and device software components in a Device Type Manager
(DTM). An FDT framework is independent from the devices and fieldbus system, while the DTM
depends on specific device and fieldbuses.
Both technologies are supported by automation vendors and users, so that there is a need to
generate a DTM based on an EDD as long as the field device integration (FDI) technology is not
published as an International Standard.
FDI (IEC 62769) covers device integration and device management technology, combining base
concepts and technology aspects of the EDDL (IEC 61804), FDT (IEC 62543) and OPC UA
(IEC 62541-1). The combination of those different proven technologies ensures a secure life
cycle and the ability to address all challenges of device integration and device management in a
scalable manner.
EDDL and FDT are complimentary in a way that an EDDL can be converted into an FDT-DTM. As
long as FDI is not available, converting EDD into a DTM helps to combine the two standards and
use EDDs in an FDT frame environment in case there is no specific DTM available. The
conversion criterion is based on EDDL and FDT technologies.
______________
®
1
 HART is an example of a suitable product available commercially. This information is given for the convenience
of users of this document and does not constitute an endorsement by IEC of this product.

---------------------- Page: 8 ----------------------
TR 62795 © IEC:2013(E) – 7 –
INTEROPERATION GUIDE FOR FIELD DEVICE TOOL (FDT) /
DEVICE TYPE MANAGER (DTM) AND ELECTRONIC DEVICE
DESCRIPTION LANGUAGE (EDDL)



1 Scope
This Technical Report provides the general requirements for converting an EDD into a DTM.
Using this TR, an FDT/DTM developer can develop an EDD-DTM conversion tool that can be
used to import, parse, and manage EDD to generate the corresponding DTM. A conversion tool
versus a DTM written independent of an EDD helps the DTM generation to maintain consistency
in function, data and presentation styles.
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 61804 (all parts), Function blocks (FB) for process control
IEC 61804-3:2010, Function blocks (FB) for process control – Part 3 Electronic Device
Description Language (EDDL)
IEC 62453-1:2009, Field device tool (FDT) interface specification – Part 1: Overview and
guidance
3 Terms, definitions, and abbreviations
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62453-1, IEC 61804-3,
as well as the following apply.
3.1.1
agent interpreter
analytical software for parsing EDD
Note 1 to entry: An agent interpreter can parse out the elements in the EDD document and map to the DTM.
Note 2 to entry: An agent interpreter can realize the interaction between the DTM and the physical device.
3.1.2
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 across multiple resources, and may communicate with other
applications.
[SOURCE: IEC 61499-1:2005, 3.5]

---------------------- Page: 9 ----------------------
– 8 – TR 62795 © IEC:2013(E)
3.1.3
device type manager
DTM
device-specific application software components
3.1.4
field device tool
FDT
interfaces for data exchange among the field devices and control systems, engineering tools,
and resource management system tools
3.2 Abbreviations
BTM Block type manager
COM Component object model
CP Communication profile
DCS Distributed control system
DD Device description
DLL Dynamic link library
DTM Device type manager
EDD Electronic device description
EDDL Electronic device description language
ERP Enterprise resource planning
FA Frame application
FB Function block
FDI Field device integration
FDT Field device tool
FF Fieldbus Foundation
GUI Graphical user interface
I/O Input/output
ID Identifier
IT Information technology
MES Manufacturing execution systems
OLE Object linking and embedding
OPC Open connectivity via open standards
PLC Programmable logic controller
SCADA Supervisory, control and data acquisition
UML Unified modeling language
UUID Universal unique identifier
XML Extensible markup language

4 Typical methods to convert EDD to FDT/DTM
4.1 Overview
There are three typical methods to integrate EDD documents into FDT:
• Using a universal DTM to integrate EDD documents.

---------------------- Page: 10 ----------------------
TR 62795 © IEC:2013(E) – 9 –
• Using a converting tool importing an EDD document to generate a DTM.
• Developing a DTM based on an EDD.
4.2 Using a universal DTM to integrate the EDD document
4.2.1 General
FDT/DTM developers provide a universal DTM, which contains an EDD interpreter. The
implementation of the DTM is very flexible, so an EDD interpreter can be embedded into the
COM component of the DTM. The interpreter can be implemented in the DTM interface to not
change the external form of the DTM. When the host sends a request to this universal DTM
server, the DTM server acquires the information on the requested data by looking for a data
sheet generated by the interpreter, which then bases itself on this information to communicate
directly with the DTM through a communication device. When the DTM is running, the EDD can
be imported, the interpreter analyses the documents, and then generates the functions and data
according to the EDD. The corresponding functions and data are released after the FA releases
the DTM. Before the next time it is used, the file needs to be imported and treated accordingly.
Since the universal DTM needs to parse different EDD files, and generate a corresponding DTM,
the EDD file format is very essential The EDD file format needs to be defined in order to parse
correctly. If the EDD file format is not unified, the interpreter cannot parse or not exactly as the
analytical results are given, and as a result, it will not generate a DTM or generated DTMs will be
different, affecting consistency.
The procedure for using a universal FDT/DTM to integrate the EDD document is as follows:
1) Users start updating the list of FDT application devices, more precisely, the list of DTM
device types.
2) The FDT application instantiates the general device FDT, calling the DTM interface functions
IDtmInformation::GetInformation or calling the DTM interface functions
IDtmInformation2::GetDeviceIdentificiationInformation.
3) The universal DTM reads all the EDD files of a predefined path, parsing EDD file type
information such as the protocol which the devices support, manufacturer identification,
manufacturer name, device type ID, device name, EDD file path names.
4) The universal DTM writes the information into XML documents according to XML schema
defined by the FDT, and returns the XML documents back to the FDT application. The XML
documents can contain more than one device type information.
5) The FDT frame application generates a list of device types according to XML documents. At
this point the devices’ name defined in the EDD files will appear in the list.
6) Users create a new project in the FDT application, and select a communication DTM type (i.e.
an instance of a communication DTM) for the project.
7) Users select a type of universal DTM from the list of DTM device types (universal DTM) and
add it into communication DTM as a sub-project.
8) During the instancing of a universal DTM, the FDT frame application calls a DTM interface
function IDtm:InitNew. An input parameter of the function is an XML document, which
contains the device type information of a specific DTM. Since the information contains the
EDD file path information, the universal DTM reads one EDD file according to this
information and parses this file then generates the corresponding internal data model or
internal database according to the parameters of this EDD.
9) The communication DTM calls the interface function of the universal DTM
IDtmParamenter::GetParamenters to obtain information associated with the parameters of
the device.
4.2.2 Basic contents of the transformation from EDD to DTM
The transformation steps could be as follows:
1) Defining the transformation model

---------------------- Page: 11 ----------------------
– 10 – TR 62795 © IEC:2013(E)
This requirement will be based on the EDDL specification to design a conversion model. The
model needs to achieve the following contents: parameter type, communication mode,
method, menu and other functions.
The characteristics of the DTM need to conform to the specification according to the actual
requirements, and the requirements of being able to provide consistent data and
functionality.
The features of the DTM need to demonstrate the data and functions which are involved in
EDDL. It can support only some of the features in EDDL. The usual functions are: the
displaying and setting of parameters, reading and writing parameters, user interface and so
on.
2) The specifications of the DTM interface, i.e. it is required to be able to display the EDD
interface correctly.
The EDD’s interface is defined by the menu, so it is better to correspond with the EDDL menu
when designing the DTM interface, and that will maintain the consistency of the interface.
3) After the specifications of how describing to resolve the EDD document, the interaction
between the instance and field devices as well as between the instance and the framework
should be handled.
The interaction between the instance and field devices needs to communicate with the
hardware, which requires a communication DTM to provide communication services. During
the interaction, an FDT FA provides a standardized method to handle the interaction
between Framework applications and each instance.
4) The specification of object mapping between EDDL and FDT
Object mapping is divided into two steps. First, it is required to map the elements of the table,
such as TYPE, ADDRESSBLOCK parsed from the EDD document, to the member variables
of the device object, and map the METHOD COMMAND to the member functions of device
object. Second, it is required to map member variables and methods of the device object into
FDT.
5) Guarantee that DTM can well manage the EDD document loaded in it well.
4.2.3 Procedure
The procedure for the transformation from EDD to DTM is shown in Figure 1.

---------------------- Page: 12 ----------------------
TR 62795 © IEC:2013(E) – 11 –

Begin
Start universal DTM

Import EDD document

Interpret
Generate functions
Acquire data
Release
End
IEC  2365/13

Figure 1 – EDD to DTM conversion flowchart
The general process of converting EDD to DTM is as follows:
1) Start universal DTM
There should be a universal DTM in the application framework, which contains the internal
implementation of EDD resolution. Before importing the EDD, you need to load the DTM in
the framework of the application.
2) Import the EDD
Import the EDD into a universal DTM which has implemented the function of EDD interpreter.
3) Interpret EDD
EDD files written using EDDL according to IEC 61804 should parse out all the information in
the EDD document.
4) Generate functions
According to EDDL standards, it is required to achieve all the functions that an EDD contains
during the course of parsing an EDD into the DTM. These functions include how to display
and set parameters, how to read and write parameters, the user interface and so on.
5) Acquire data
According to IEC 61804 it is required to give the corresponding data of parameters described
by EDD during the parsing of the EDD to generate a DTM.
6) Release
This universal DTM using an EDD interpreter on the fly can be generally useful for host
system vendors as a part of their host system because all devices that have EDD provided by
manufacturers are supported in the FDT host system.
4.3 Using a converting tool to integrate EDD documents
4.3.1 General
There will be a direct generation of the corresponding DTM after the FDT/DTM developers or
users parse through the EDD file. This DTM is independent of the EDD files and can be used
alone. However, this approach often requires the use of a specialized conversion tool. With the
support of this conversion tool, we can import the EDD file and do the associated analytical

---------------------- Page: 13 ----------------------
– 12 – TR 62795 © IEC:2013(E)
processing, to get a separate DTM which can run thanks to the conversion tool. This method
also requires to do format standardized work for the EDD file, in order to parse the file for the
conversion tool and generate the corresponding DTM. In this method, a device DTM can be
generated from one or more than one file, and this DTM can represent more than one device
type. The device type information and corresponding devices’ parameter information can exist in
the binary DLL files of the DTM in an entirely hard-coded format.
4.3.2 Basic contents
The basic contents of EDD to DTM transformation are the following:
1) Defining the transformation model
This requirement will be based on EDDL specification to design a conversion model. This
model needs to achieve the following contents: the parameter type, communication mode,
method, menu and other functions.
2) Defining the intermediate object model
The intermediate conversion process of the basic object model may be defined using XML or
UML. EDDL documents are loaded into the object model to generate the intermediate
objects.
3) Mapping intermediate objects to FDT objects
Var
...