SIST-TP CLC/TR 62453-61:2010
(Main)Field device tool interface specification -- Part 61: Device type manager (DTM) - Styleguide for common object model
Field device tool interface specification -- Part 61: Device type manager (DTM) - Styleguide for common object model
IEC/TR 62453-61, which is a technical report, explains the guidelines and rules for the implementation of a Device Type Manager (DTM) with regard to the user interface and its functions. These guidelines and rules are part of the FDT specification and are intended to ensure that all users are provided with clear and consistent user interface functions and features across DTM devices in a system.
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 61: Device Type Manager (DTM) - Leitfaden zur Gestaltung von Bedienoberflächen
Spécification des interfaces des outils des dispositifs de terrain (FDT) -Partie 61: Gestionnaire type de dispositifs (DMT) - Guide stylistique pour le modèle objet commun
Specifikacija vmesnika orodja procesne naprave - 61. del: Upravitelj tipa naprave (DTM) - Slogovno vodilo za skupni model objekta (IEC/TR 62453-61:2009)
IEC/TR 62453-61, ki je tehnično poročilo, pojasnjuje smernice in pravila za implementacijo upravitelja tipa naprave (DTM) za uporabniški vmesnik in njegove funkcije. Te smernice in pravila so del specifikacije FDT in so namenjene temu, da vsem uporabnikom zagotovijo popolne in združljive funkcije in lastnosti uporabniškega vmesnika skozi naprave DTM v sistemu.
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST-TP CLC/TR 62453-61:2010
01-februar-2010
Specifikacija vmesnika orodja procesne naprave - 61. del: Upravitelj tipa naprave
(DTM) - Slogovno vodilo za skupni model objekta (IEC/TR 62453-61:2009)
Field device tool interface specification -- Part 61: Device type manager (DTM) -
Styleguide for common object model
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 61: Device Type Manager
(DTM) - Leitfaden zur Gestaltung von Bedienoberflächen
Ta slovenski standard je istoveten z: CLC/TR 62453-61:2009
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.240.50 Uporabniške rešitve IT v IT applications in industry
industriji
SIST-TP CLC/TR 62453-61:2010 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST-TP CLC/TR 62453-61:2010
---------------------- Page: 2 ----------------------
SIST-TP CLC/TR 62453-61:2010
TECHNICAL REPORT
CLC/TR 62453-61
RAPPORT TECHNIQUE
November 2009
TECHNISCHER BERICHT
ICS 25.040.40; 35.100.05; 35.110
English version
Field device tool interface (FDT) specification -
Part 61: Device type manager (DTM) -
Styleguide for common object model
(IEC/TR 62453-61:2009)
Spécification des interfaces des outils Field Device Tool (FDT)-
des dispositifs de terrain (FDT) - Schnittstellenspezifikation -
Partie 61: Gestionnaire type Teil 61: Device Type Manager (DTM) -
de dispositifs (DMT) - Leitfaden zur Gestaltung
Guide stylistique von Bedienoberflächen
pour le modèle objet commun (IEC/TR 62453-61:2009)
(CEI/TR 62453-61:2009)
This Technical Report was approved by CENELEC on 2009-10-01.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.
CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
Central Secretariat: Avenue Marnix 17, B - 1000 Brussels
© 2009 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. CLC/TR 62453-61:2009 E
---------------------- Page: 3 ----------------------
SIST-TP CLC/TR 62453-61:2010
CLC/TR 62453-61:2009 - 2 -
Foreword
The text of document 65E/72/CDV, future edition 1 of IEC/TR 62453-61, prepared by SC 65E, Devices
and integration in enterprise systems, of IEC TC 65, Industrial-process measurement, control and
automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as
CLC/TR 62453-61 on 2009-10-01.
Annex ZA has been added by CENELEC.
__________
Endorsement notice
The text of the Technical Report IEC/TR 62453-61:2009 was approved by CENELEC as a Technical
Report without any modification.
__________
---------------------- Page: 4 ----------------------
SIST-TP CLC/TR 62453-61:2010
- 3 - CLC/TR 62453-61:2009
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
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.
NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year
IEC 62453-1 2009 Field device tool (FDT) interface EN 62453-1 2009
specification -
Part 1: Overview and guidance
IEC 62453-2 2009 Field device tool (FDT) interface EN 62453-2 2009
specification -
Part 2: Concepts and detailed description
IEC/TR 62453-41 2009 Field device tool (FDT) interface CLC/TR 62453-41 2009
specification -
Part 41: Object model integration profile -
Common object model
ISO/IEC 19501 2005 Information technology - - -
Open Distributed Processing -
Unified Modeling Language (UML)
__________
---------------------- Page: 5 ----------------------
SIST-TP CLC/TR 62453-61:2010
---------------------- Page: 6 ----------------------
SIST-TP CLC/TR 62453-61:2010
IEC/TR 62453-61
®
Edition 1.0 2009-08
TECHNICAL
REPORT
colour
inside
Field device tool (FDT) interface specification –
Part 61: Device Type Manager (DTM) Styleguide for common object model
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
V
ICS 25.040.40; 35.100.05; 35.110 ISBN 2-8318-1058-2
® Registered trademark of the International Electrotechnical Commission
---------------------- Page: 7 ----------------------
SIST-TP CLC/TR 62453-61:2010
– 2 – TR 62453-61 © IEC:2009(E)
CONTENTS
FOREWORD.4
INTRODUCTION.6
1 Scope.7
2 Normative references .7
3 Terms, definitions, symbols, abbreviated terms and conventions .7
3.1 Terms and definitions .7
3.2 Symbols and abbreviated terms.7
3.3 Conventions .8
3.3.1 Data type names and references to data types .8
3.3.2 Vocabulary for requirements.8
3.3.3 Specific formatting.8
3.3.4 State machine diagrams .8
4 Principles for designing DTM user interfaces .8
5 Benefits from the FDT user’s point of view.9
6 Functions of a DTM .11
6.1 General .11
6.2 Function “Main operation”.11
6.3 Functions “Online Parameterize” and “Offline Parameterize” .12
7 DTM user interface.12
7.1 Objective.12
7.2 General behavior.12
7.2.1 General .12
7.2.2 GUI navigation.12
7.2.3 GUI resizeability .12
7.2.4 Display of information.12
7.3 Microsoft Active Accessibility.13
7.4 Appearance.13
7.4.1 General .13
7.4.2 DTM user interface categories.14
7.4.3 DTM user interface areas .15
7.5 Parameter handling .20
7.5.1 Representation within Application Area.20
7.5.2 Change of parameter values.20
7.5.3 Representation of parameters.22
8 Representation of DTM functions.24
9 DTM behavior.27
9.1 Close of user interface with modified parameter values .27
9.2 Data set .27
9.2.1 Parameter in multiple user interfaces.27
9.2.2 Locking mechanism .27
9.3 Online parameterization / data source: device .28
9.4 Offline parameterization / data source: data set.28
9.5 Error handling .29
9.6 Communication .29
9.7 Access rights.30
9.7.1 FDT actors and parameter classes .30
---------------------- Page: 8 ----------------------
SIST-TP CLC/TR 62453-61:2010
TR 62453-61 © IEC:2009(E) – 3 –
9.7.2 OEM login .30
9.8 Localization.30
9.9 Documentation .30
9.10 Installation and un-installation .31
Bibliography.33
Figure 1 – Part 61 of the IEC 62453 series .6
Figure 2 – Standard User Interface (SUI) .10
Figure 3 – Advanced User Interface (AUI).11
Figure 4 – Areas of an SUI.14
Figure 5 – Areas of an AUI.15
Figure 6 – State diagram: Continuous Check .21
Figure 7 – State diagram: One Time Check.22
Figure 8 – Parameter value and associated information .22
Table 1 – Contents of Identification Area .16
Table 2 – Contents of Action Area .17
Table 3 – Contents of Status Bar .18
Table 4 – Possible connection states .18
Table 5 – Possible data source states.19
Table 6 – Possible states of the instance data set.19
Table 7 – Possible device diagnostic states (see [1]) .19
Table 8 – Possible states of parameters .23
Table 9 – Display of inadmissible or wrong data .24
Table 10 – Representation of functions .25
Table 11 – Relation between user roles and parameter classes .30
Table 12 – Installation and un-installation .31
---------------------- Page: 9 ----------------------
SIST-TP CLC/TR 62453-61:2010
– 4 – TR 62453-61 © IEC:2009(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
Part 61: Device Type Manager (DTM) Styleguide
for common object model
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.
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/TR 62453-61, 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:
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.
---------------------- Page: 10 ----------------------
SIST-TP CLC/TR 62453-61:2010
TR 62453-61 © IEC:2009(E) – 5 –
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
65E/72/DTR 65E/121/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.
The 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.
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 publication using a colour printer.
---------------------- Page: 11 ----------------------
SIST-TP CLC/TR 62453-61:2010
– 6 – TR 62453-61 © IEC:2009(E)
INTRODUCTION
This technical report is a user interface design specification for developers of FDT (Field
Device Tool) components for Function Control and Data Access within a Client/Server
architecture. The technical report is a result of an analysis and design process to develop
standard interfaces to facilitate the development of components by multiple vendors that shall
interoperate seamlessly.
A device-specific software component, called DTM (Device Type Manager), is supplied by the
field device manufacturer with its device. The DTM is integrated into engineering tools via the
FDT interfaces defined in this specification. The approach to integration is in general open for
all kinds of fieldbusses and thus meets the requirements for integrating different kinds of
devices into heterogeneous control systems.
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. This integration also
requires a consistent look and feel of device specific components.
Figure 1 shows how IEC/TR 62453-61 is aligned in the structure of the IEC 62453 series.
Part 61
DTM Styleguide
Part 41
Object Model
Integration Profile
Figure 1 – Part 61 of the IEC 62453 series
---------------------- Page: 12 ----------------------
SIST-TP CLC/TR 62453-61:2010
TR 62453-61 © IEC:2009(E) – 7 –
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –
Part 61: Device Type Manager (DTM) Styleguide
for common object model
1 Scope
IEC/TR 62453-61, which is a technical report, explains the guidelines and rules for the
implementation of a Device Type Manager (DTM) with regard to the user interface and its
functions. These guidelines and rules are part of the FDT specification and are intended to
ensure that all users are provided with clear and consistent user interface functions and
features across DTM devices in a system.
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 62453-1:2009, Field Device Tool (FDT) interface specification – Part 1: Overview and
guidance
IEC 62453-2:2009, Field Device Tool (FDT) interface specification – Part 2: Concepts and
detailed description
IEC/TR 62453-41:2009, Field Device Tool (FDT) interface specification – Part 41: Object
model integration profile – Common object model
ISO/IEC 19501:2005, Information technology – Open Distributed Processing – Unified
Modeling Language (UML) Version 1.4.2
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62453-1,
IEC 62453-2, IEC/TR 62453-41 and the following apply.
3.1.1
screen reader
software application that provides additional output to users (e.g. text-to-sound, braille)
3.1.2
navigation tree
GUI element, which displays the navigation information by means of a tree (e.g. tree control)
3.2 Symbols and abbreviated terms
For the purposes of this document, the symbols and abbreviations given in IEC 62453-1,
IEC 62453-2, IEC/TR 62453-41 and the following apply.
GUI Graphical User Interface
---------------------- Page: 13 ----------------------
SIST-TP CLC/TR 62453-61:2010
– 8 – TR 62453-61 © IEC:2009(E)
SUI Standard User Interface (a GUI layout defined in this document)
AUI Advanced User Interface (a GUI layout defined in this document)
CUI Composition User Interface (a GUI layout defined in this document)
MSAA Microsoft Active Accessibility
OEM Original Equipment Manufacturer
3.3 Conventions
3.3.1 Data type names and references to data types
The conventions for naming and referencing of data types are explained in IEC 62453-2,
Clause A.1
3.3.2 Vocabulary for requirements
The following expressions are used when specifying requirements.
Usage of “shall” or “mandatory” No exceptions allowed.
Usage of “should” or “recommended” Strong recommendation. It may make sense in special exceptional
cases to differ from the described behavior.
Usage of “can’ or “optional’ A DTM may provide the function or behavior depending on the task
and type of the DTM. If a function or behavior is provided, it shall
follow the style guide.
3.3.3 Specific formatting
The following formatting is used to describe specific context.
CAPITAL LETTERS Names of keys on the keyboard —for example, SHIFT, CTRL, or ALT.
[Button text] Button with the specified text.
Name of an XML element according to data type definition in IEC/TR 62453-41.
3.3.4 State machine diagrams
Syntax of the state machine diagrams in this document is defined in IEC 62453-1 and in
ISO/IEC 19501:2005.
4 Principles for designing DTM user interfaces
The design of GUIs for DTMs is based on the following general principles for user interface
design [4],[5]. These are recommendations for good engineering practice. For additional
fundamentals of user interface design, please see the available literature.
Visibility of system status
The system should always keep users informed about what is going on, through appropriate
feedback within an acceptable time limit.
Match between system and the real world
The system should speak the users' language with words, phrases and concepts familiar to
the user, rather than system-oriented terms. Follow real-world conventions, making
information appear in a natural and logical order.
---------------------- Page: 14 ----------------------
SIST-TP CLC/TR 62453-61:2010
TR 62453-61 © IEC:2009(E) – 9 –
User control and freedom
Users often choose system functions by mistake and need a clearly marked "emergency exit"
to leave the unwanted state without having to go through an extended dialogue. Support undo
and redo.
Consistency and standards
Users should not have to wonder whether different words, situations, or actions mean the
same thing. Follow platform conventions.
Error prevention
A careful design which prevents a problem from occurring in the first place is even better than
good error messages.
Recognition rather than recall
Make objects, actions, and options visible. The user should not have to remember information
from one part of the dialogue to another. Instructions for use of the system should be visible
or easily retrievable whenever appropriate.
Flexibility and efficiency of use
Accelerators - unseen by the novice user - may often speed up the interaction for the expert
user so that the system can cater to both inexperienced and experienced users. Allow users
tailoring of frequent actions.
Aesthetic and minimalist design
Dialogue should not contain information which is irrelevant or rarely needed. Every extra unit
of information in a dialogue competes with the relevant units of information and diminishes
their relative visibility.
Help users recognize, diagnose, and recover from errors
Error messages should be expressed in plain language (no codes), precisely indicate the
problem, and constructively suggest a solution.
Help and documentation
Even though it is better if the system can be used without documentation, it may be necessary
to provide help and documentation. Any such information should be easy to search, focus on
the user's task, list concrete steps to be carried out, and not be too large.
5 Benefits from the FDT user’s point of view
Using DTMs compliant with this style guide enables the user to operate more efficiently and
more safely. The user is able to parameterize and manage the data of devices from various
manufacturers in a uniform way. Therefore, the user is presented with a clearly structured
concept regardless of the manufacturer or the type of the device. Details or requirements for
developers of a DTM are given within the following clauses.
Guideline and rules are defined for
• uniform user guidance: DTM user interfaces are used and displayed in engineering
systems and stand alone tools in the same manner regardless of the device or DTM
manufacturer or communication protocol employed;
• uniform behavior of a DTM. This includes:
• persistent storage,
• behavior in multi-user environments,
• error handling;
• clear identification of the DTM and the assigned device;
• ensuring users will be updated on the status and the parameterization of the configuration
constantly. All changes of the configuration are marked;
• informing users, whether GUI input affects the device directly or the offline configuration;
---------------------- Page: 15 ----------------------
SIST-TP CLC/TR 62453-61:2010
– 10 – TR 62453-61 © IEC:2009(E)
• executing plausibility checks of the configuration on a lexical (e.g. only certain characters
are accepted), syntactical (e.g. a limited number of characters) and semantically (e.g.
given value is below upper limit) correct basis;
• uniform installation/un-installation procedure.
The following screen shots show a Standard User Interface (SUI) (see Figure 2) and an
Advanced User Interface (AUI) (Figure 3), two of three possible user interface types (see
7.4.2).
Figure 2 – Standard User Interface (SUI)
---------------------- Page: 16 ----------------------
SIST-TP CLC/TR 62453-61:2010
TR 62453-61 © IEC:2009(E) – 11 –
Figure 3 – Advanced User Interface (AUI)
6 Functions of a DTM
6.1 General
According to IEC/TR 62453-41, a DTM exposes the complete set of available functions with
respect to the current state within the XML document returned by IDtm:GetFunctions(). The
Frame Application (FA) is responsible for presenting these functions within its overall user
interface in a homogeneous way. There should be no break between the DTM based functions
and the FDT Frame Application functions.
In general, the Frame Application is responsible for identifying the DTM instance and starting
the current function performed by the DTM instance. Such a function can be handled by a
specific user interface provided by the DTM. In this case, the Frame Application starts this
DTM user interface as integrated application. The Frame Application then shows identification
information in a window title bar of this application.
See IEC 62453-2 for a list of predefined applicationIds (Table A.2). Clause 5 in IEC 62453
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.