Field device tool (FDT) interface specification - Part 62: Field device tool (FDT) styleguide for common language infrastructure (IEC TR 62453-62:2017)

IEC TR 62453-62, which is a Technical Report, explains the guidelines and rules for the CLI based implementation of a Device Type Manager (DTM) and parts of a Frame Application with regard to the user interface and its behaviour. These guidelines and rules are part of the FDT specification (IEC TR 62453 42) and are intended to ensure that all users are provided with clear and consistent user interface functions and features across DTMs in a system.
This specification neither contains the FDT specification nor modifies it.

Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 62: Field device tool (FDT) Leitfaden für common language infrastructure (IEC TR 62453-62:2017)

Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 62: Guide stylistique de l’outil de dispositif de terrain (FDT) pour l’infrastructure commune de langage (IEC TR 62453-62:2017)

Specifikacija vmesnika orodja procesne naprave - 62. del: Specifikacija vmesnika orodja procesne naprave za slogovno vodilo za skupno jezikovno infrastrukturo (IEC TR 62453-62:2017)

Standard IEC TR 62453-62, ki je tehnično poročilo, razlaga smernice in pravila za implementacijo naprave DTM (Device Type Manager) na osnovi CLI in delov Frame Application v zvezi z uporabniškim vmesnikom in njegovim vedenjem. Te smernice in pravila so del specifikacije orodja procesne naprave (IEC TR 62453 42) in vsem uporabnikom zagotavljajo jasne in dosledne funkcije in lastnosti uporabniškega vmesnika za orodja procesnih naprav v sistemu.
Ta specifikacija niti ne vsebuje specifikacije orodja procesne naprave niti je ne spreminja.

General Information

Status
Published
Publication Date
28-May-2019
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
16-Apr-2019
Due Date
21-Jun-2019
Completion Date
29-May-2019

Buy Standard

Technical report
TP CLC/TR IEC 62453-62:2019 - BARVE
English language
45 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-TP CLC/TR IEC 62453-62:2019
01-julij-2019
Specifikacija vmesnika orodja procesne naprave - 62. del: Specifikacija vmesnika
orodja procesne naprave za slogovno vodilo za skupno jezikovno infrastrukturo
(IEC TR 62453-62:2017)
Field device tool (FDT) interface specification - Part 62: Field device tool (FDT)
styleguide for common language infrastructure (IEC TR 62453-62:2017)
Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 62: Field device tool (FDT)
Leitfaden für common language infrastructure (IEC TR 62453-62:2017)
Spécification des interfaces des outils des dispositifs de terrain (FDT) - Partie 62: Guide
stylistique de l’outil de dispositif de terrain (FDT) pour l’infrastructure commune de
langage (IEC TR 62453-62:2017)
Ta slovenski standard je istoveten z: CLC/TR IEC 62453-62:2019
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 IEC 62453-62:2019 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019

---------------------- Page: 2 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019


TECHNICAL REPORT CLC/TR IEC 62453-62

RAPPORT TECHNIQUE

TECHNISCHER BERICHT
April 2019
ICS 25.040.40; 35.100.05; 35.110

English Version
Field device tool (FDT) interface specification - Part 62: Field
device tool (FDT) styleguide for common language infrastructure
(IEC TR 62453-62:2017)
Spécification des interfaces des outils des dispositifs de Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 62:
terrain (FDT) - Partie 62: Guide stylistique de l'outil de Field device tool (FDT) Leitfaden für common language
dispositif de terrain (FDT) pour l'infrastructure commune de infrastructure
langage (IEC TR 62453-62:2017)
(IEC TR 62453-62:2017)


This Technical Report was approved by CENELEC on 2019-03-18.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic,
Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden,
Switzerland, Turkey and the United Kingdom.



European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2019 CENELEC All rights of exploitation in any form and by any means reserved worldwide for CENELEC Members.
 Ref. No. CLC/TR IEC 62453-62:2019 E

---------------------- Page: 3 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
CLC/TR IEC 62453-62:2019 (E)


European foreword

This document (CLC/TR IEC 62453-62:2019) consists of the text of the
IEC TR 62453-62:2017 prepared by 65E: "Devices and integration in enterprise systems", of
IEC technical committee 65: "Industrial process measurement, control and automation".

Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights. CENELEC shall not be held responsible for identifying any or all
such patent rights.

2

---------------------- Page: 4 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
CLC/TR IEC 62453-62:2019 (E)
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements 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 1 When an International Publication has been modified by common modifications, indicated by (mod), the relevant

EN/HD applies.

NOTE 2 Up-to-date information on the latest versions of the European Standards listed in this annex is available here:
www.cenelec.eu.

Publication Year Title EN/HD Year
Field device tool (FDT) interface
IEC TR 62453-42 -  - -
specification – Part 42: Object model
integration profile – Common Language
Infrastructure
IEC 62453-1 -  Field device tool (FDT) interface EN 62453-1 -
specification - Part 1: Overview and
guidance
IEC 62453-2 -  Field device tool (FDT) interface EN 62453-2 -
specification - Part 2: Concepts and
detailed description

3

---------------------- Page: 5 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019

---------------------- Page: 6 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019




IEC TR 62453-62

®


Edition 1.0 2017-01




TECHNICAL



REPORT








colour

inside










Field device tool (FDT) interface specification –

Part 62: Field device tool (FDT) styleguide for common language infrastructure



























INTERNATIONAL

ELECTROTECHNICAL


COMMISSION





ICS 25.040.40; 35.100.05; 35.110 ISBN 978-2-8322-3793-9



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


® Registered trademark of the International Electrotechnical Commission

---------------------- Page: 7 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
– 2 – IEC TR 62453-62:2017 © IEC 2017
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 . 8
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
4 Fundamentals of designing DTM user interfaces . 8
5 Benefits from the FDT user’s point of view . 9
6 DTM user interface . 10
6.1 Objective . 10
6.2 Appearance . 10
6.2.1 General . 10
6.2.2 DTM user interface categories . 10
6.2.3 DTM user interface areas . 13
6.3 General behaviour . 20
6.3.1 General . 20
6.3.2 WPF user interfaces . 20
6.3.3 UI navigation . 21
6.3.4 UI resize . 21
6.3.5 Display of information . 21
6.3.6 Use of modal user interfaces . 22
7 Parameter handling . 22
7.1 Representation within Application Area . 22
7.2 Change of parameter values . 22
7.2.1 Relation between parameters . 22
7.2.2 Block mode . 22
7.2.3 Direct Mode . 22
7.2.4 Continuous Check and One Time Check . 23
7.3 Representation of parameters . 24
7.3.1 Parameter value and associated information . 24
7.3.2 Parameter value modifications . 25
8 Applications of a DTM. 25
8.1 General . 25
8.2 Application categories . 26
8.2.1 Online application/data source: device . 26
8.2.2 Offline application/data source: data set . 26
8.2.3 Synchronized application/data source: data set and device . 26
8.3 User role related default application . 27
8.4 Main Operation . 27
8.5 Typical workflow . 27
8.5.1 General . 27

---------------------- Page: 8 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
IEC TR 62453-62:2017 © IEC 2017 – 3 –
8.5.2 Parameterize device offline. 27
8.5.3 Parameterize device with online connection (synchronized) . 29
8.5.4 Parameterize device with online connection (non synchronized) . 30
9 DTM behaviour . 31
9.1 Close of user interface . 31
9.1.1 Close of user interface with modified parameter values . 31
9.1.2 Synchronization on close of user interface . 32
9.2 Data set . 32
9.2.1 Parameter in multiple user interfaces . 32
9.2.2 Locking mechanism . 32
9.3 Error handling . 33
9.4 Localization . 33
9.5 Global report information . 33
Annex A (normative) Dictionary of standard terms . 34
Annex B (normative) Dictionary of standard phrases . 37
Bibliography . 42

Figure 1 – IEC 62453-62 in IEC 62453 (all parts) . 6
Figure 2 – Areas of a Standard user interface . 11
Figure 3 – Areas of an Advanced user interface . 12
Figure 4 – Areas of a Wizard user interface . 13
Figure 5 – Structure of the Identification Area . 13
Figure 6 – State diagram: Continuous Check . 23
Figure 7 – State diagram: One Time Check . 24
Figure 8 – Parameter value and associated information . 24
Figure 9 – Parameterize device offline . 28
Figure 10 – Parameterize device with offline parameterize and subsequent download . 29
Figure 11 – Parameterize device with online connection (synchronized) . 30
Figure 12 – Parameterize device with online connection (non synchronized) . 31

Table 1 – Contents of Identification Area . 14
Table 2 – Toolbar. 15
Table 3 – Methods for UI using Block Mode . 16
Table 4 – Methods for UI using Direct Mode . 17
Table 5 – Wizard actions . 17
Table 6 – Contents of Status Bar . 18
Table 7 – Possible connection states . 18
Table 8 – Possible data source and target states . 19
Table 9 – Possible states of the instance data set . 19
Table 10 – Possible modification states . 20
Table 11 – Possible device diagnostic states (see [1]) . 20
Table 12 – Display of inadmissible data . 24
Table 13 – Priority of parameter value states . 25
Table 14 – Recommended default application . 27

---------------------- Page: 9 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
– 4 – IEC TR 62453-62:2017 © IEC 2017
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________

FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 62: Field device tool (FDT) styleguide
for common language infrastructure

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 TR 62453-62, 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/442/DTR 65E/515/RVC

---------------------- Page: 10 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
IEC TR 62453-62:2017 © IEC 2017 – 5 –

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 document 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 document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document 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: 11 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
– 6 – IEC TR 62453-62:2017 © IEC 2017
INTRODUCTION
This document 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. This
document is a result of an analysis and design process to develop standard interfaces to
facilitate the development of components by multiple vendors that 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,
fieldbusses, devices and sub-systems are fully integrated 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-62 is aligned in the structure of IEC 62453 (all parts).
IEC TR 62453-62
FDT styleguide
IEC TR 62453-42
Object model
integration profile
IEC

Figure 1 – IEC 62453-62 in IEC 62453 (all parts)

---------------------- Page: 12 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
IEC TR 62453-62:2017 © IEC 2017 – 7 –
FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION –

Part 62: Field device tool (FDT) styleguide
for common language infrastructure



1 Scope
IEC TR 62453-62, which is a Technical Report, explains the guidelines and rules for the
CLI-based implementation of a Device Type Manager (DTM) and parts of a Frame Application
with regard to the user interface and its behaviour. These guidelines and rules are part of the
FDT specification (IEC TR 62453-42) and are intended to ensure that all users are provided
with clear and consistent user interface functions and features across DTMs in a system.
This specification neither contains the FDT specification nor modifies it.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their
content constitutes requirements 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, Field device tool (FDT) interface specification – Part 1: Overview and guidance
IEC 62453-2, Field device tool (FDT) interface specification – Part 2: Concepts and detailed
description
IEC TR 62453-42, Field device tool (FDT) interface specification – Part 42: Object model
integration profile – Common Language Infrastructure
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, [7] and the following apply.
ISO and IEC maintain terminological 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
Application
DTM UI Applications and DTM UI Functions

---------------------- Page: 13 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
– 8 – IEC TR 62453-62:2017 © IEC 2017
3.2 Symbols and abbreviated terms
For the purposes of this specification the symbols and abbreviated terms given in
IEC 62453-1, IEC 62453-2, IEC 62453-42 and the following apply.
UI user interface
NAMUR User Association of Automation Technology in Process Industries
WPF Windows Presentation Foundation (Microsoft user interface library)

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 [7].
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 Strong recommendation. It may make sense in special
"Recommended" exceptional cases to differ from the described
behaviour.
Usage of "can" or "Optional" A DTM may provide the function or behaviour depending
on the task and type of the DTM. If a function or
behaviour 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
ClassName::PropertyName Name of property or method according to definition in
or FDT 2.0 Technical Specification
InterfaceName::MethodName

4 Fundamentals of designing DTM user interfaces
The design of UIs for DTMs is based on the ten general principles for user interface design
accepted in general public [3], [4]. They are called "heuristics" because they are more in the
nature of rules of thumb than specific usability guidelines. The heuristics should give the DTM
developer some general hints on how to implement a DTM. For additional fundamentals of
user interface design, please see the available literature (e.g. [5], [6]). The ten general
principles are the following.

---------------------- Page: 14 ----------------------

SIST-TP CLC/TR IEC 62453-62:2019
IEC TR 62453-62:2017 © IEC 2017 – 9 –
Visibility of system status
The system should always keep users informed about what is going on, through appropriate
feedback within an acceptable time limit (dependant on the task, e.g. 1 sec.).
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.
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 such 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, be context sensitive and not be too large.
5 Benefits from the FDT user’s point of view
Using DTMs compliant with this style guide enables a 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. Therefor
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.