1、Field device tool (FDT) interface specificationPart 62: Field device tool (FDT) styleguide for common language infrastructurePD IEC/TR 62453-62:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National forewordThis Published Document is the UK implementation of IE
2、C/TR62453-62:2017.The UK participation in its preparation was entrusted to TechnicalCommittee AMT/7, Industrial communications: process measurement andcontrol, including fieldbus.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does no
3、t purport to include all the necessary provisions ofa contract. Users are responsible for its correct application. The British Standards Institution 2017.Published by BSI Standards Limited 2017ISBN 978 0 580 88997 4ICS 25.040.40; 35.100.05; 35.110Compliance with a British Standard cannot confer immu
4、nity fromlegal obligations.This Published Document was published under the authority of theStandards Policy and Strategy Committee on 28 February 2017.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD IEC/TR 62453-62:2017IEC TR 62453-62 Edition 1.0 2017-01 TECHNICA
5、L REPORT 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 Registered trademark of the International Electrotechnical Commiss
6、ion Warning! Make sure that you obtained this publication from an authorized distributor. colourinsidePD IEC/TR 62453-62:2017 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
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 users point of view . 9
8、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 2
9、1 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 p
10、arameters . 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 Synchroni
11、zed 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 PD IEC/TR 62453-62:2017IEC TR 62453-62:2017 IEC 2017 3 8.5.2 Parameterize device offline 27 8.5.3 Parameterize device with online co
12、nnection (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 Paramete
13、r 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
14、(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 Figur
15、e 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
16、 (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 sour
17、ce 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 applicatio
18、n . 27 PD IEC/TR 62453-62:2017 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
19、 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
20、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 t
21、he 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 conditi
22、ons 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 Nation
23、al 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
24、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 P
25、ublication 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
26、 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
27、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
28、 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 s
29、ubject 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
30、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 mea
31、surement, 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 PD IEC/TR 62453-62:2017IEC TR 62453-62:2017 IEC 2017 5 Full information on the voting for the approval of this Technical Report can be found
32、 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 commit
33、tee 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 amen
34、ded. 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 doc
35、ument using a colour printer. PD IEC/TR 62453-62:2017 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
36、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.
37、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
38、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 spec
39、ific components. Figure 1 shows how IEC TR 62453-62 is aligned in the structure of IEC 62453 (all parts). Figure 1 IEC 62453-62 in IEC 62453 (all parts) IEC TR 62453-42 Object model integration profile IEC TR 62453-62 FDT styleguide IEC PD IEC/TR 62453-62:2017IEC TR 62453-62:2017 IEC 2017 7 FIELD DE
40、VICE 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 Applicat
41、ion 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 n
42、either 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, t
43、he 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 de
44、vice 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,
45、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
46、 Functions PD IEC/TR 62453-62:2017 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 Automatio
47、n 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 ex
48、pressions 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 behaviour. Usage of “can“ or “Optional“ A DTM may provide the
49、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 or InterfaceName:MethodName Name of property or method accordi
