BS PD CLC TR 62453-61-2009 8125 Field device tool interface (FDT) nspecification — nPart 61 Device type manager (DTM) — Styleguide for common object model《现场设备工具接口(FDT)规格 第61部分 设.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationField device tool interface (FDT)specification Part 61: Device type manager (DTM) Styleguide for common object modelPD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE C

2、HINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSINational forewordThis Published Document is the UK implementation of CLC/TR 62453-61:2009.The UK participation in its preparation was entrusted to Technical CommitteeAMT/7, Industrial communications: process measurement and control, includi

3、ng fieldbus.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions of acontract. Users are responsible for its correct application. BSI 2010ISBN 978 0 580 62575 6ICS 25.040.40; 35.100.

4、05; 35.110Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under the authority of theStandards Policy and Strategy Committee on 31 January 2010Amendments issued since publicationAmd. No. Date Text affectedBRITISH STANDARDPD CLC/TR

5、62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSITECHNICAL REPORT CLC/TR 62453-61 RAPPORT TECHNIQUE TECHNISCHER BERICHT November 2009 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrot

6、echnique Europisches Komitee fr 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 ICS 25.040.40; 35.100.05; 35.110 English v

7、ersion Field device tool interface (FDT) specification - Part 61: Device type manager (DTM) - Styleguide for common object model (IEC/TR 62453-61:2009) Spcification des interfaces des outils des dispositifs de terrain (FDT) - Partie 61: Gestionnaire type de dispositifs (DMT) - Guide stylistique pour

8、 le modle objet commun (CEI/TR 62453-61:2009) Field Device Tool (FDT)-Schnittstellenspezifikation - Teil 61: Device Type Manager (DTM) - Leitfaden zur Gestaltung von Bedienoberflchen (IEC/TR 62453-61:2009) This Technical Report was approved by CENELEC on 2009-10-01. CENELEC members are the national

9、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, Sw

10、itzerland and the United Kingdom. PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSICLC/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 integr

11、ation 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 IE

12、C/TR 62453-61:2009 was approved by CENELEC as a Technical Report without any modification. _ PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSI- 3 - CLC/TR 62453-61:2009 Annex ZA (normative) Normative references to international

13、 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 amendment

14、s) 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 specification - Part 1: Overview and guidance EN 62453-1 2009 IEC 62453-2

15、 2009 Field device tool (FDT) interface specification - Part 2: Concepts and detailed description EN 62453-2 2009 IEC/TR 62453-41 2009 Field device tool (FDT) interface specification - Part 41: Object model integration profile - Common object model CLC/TR 62453-41 2009 ISO/IEC 19501 2005 Information

16、 technology - Open Distributed Processing - Unified Modeling Language (UML) - - _ PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSI 2 TR 62453-61 IEC:2009(E) CONTENTS INTRODUCTION.6 1 Scope.7 2 Normative references .7 3 Terms,

17、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 requirements8 3.3.3 Specific formatting.8 3.3.4 State machine diagrams 8 4 Principles

18、for designing DTM user interfaces8 5 Benefits from the FDT users point of view9 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 .1

19、2 7.2.2 GUI navigation.12 7.2.3 GUI resizeability 12 7.2.4 Display of information12 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 Ar

20、ea20 7.5.2 Change of parameter values20 7.5.3 Representation of parameters22 8 Representation of DTM functions24 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 para

21、meterization / 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 PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, U

22、ncontrolled Copy, (c) BSITR 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 Bibliography33 Figure 1 Part 61 of the IEC 62453 series .6 Figure 2 Standard User Interface (SUI) 10 Figure 3 Advanced User Interface (AUI).11 Fig

23、ure 4 Areas of an SUI14 Figure 5 Areas of an AUI15 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

24、 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 Representatio

25、n of functions.25 Table 11 Relation between user roles and parameter classes 30 Table 12 Installation and un-installation .31 PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSI 6 TR 62453-61 IEC:2009(E) INTRODUCTION This technic

26、al 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 develo

27、pment 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 specif

28、ication. 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 t

29、o 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 struct

30、ure of the IEC 62453 series. Part 41Object Model Integration ProfilePart 61DTM StyleguideFigure 1 Part 61 of the IEC 62453 series PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSITR 62453-61 IEC:2009(E) 7 FIELD DEVICE TOOL (FDT

31、) 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 gui

32、delines 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 o

33、f 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 Dev

34、ice 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

35、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 th

36、at 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 624

37、53-1, IEC 62453-2, IEC/TR 62453-41 and the following apply. GUI Graphical User Interface PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010 08:26, Uncontrolled Copy, (c) BSI 8 TR 62453-61 IEC:2009(E) SUI Standard User Interface (a GUI layout defined in this docu

38、ment) 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

39、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

40、 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 follo

41、wing 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 st

42、ate 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. F

43、or 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

44、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. PD CLC/TR 62453-61:2009Licensed Copy: Wang Bin, ISO/EXCHANGE CHINA STANDARDS, 15/04/2010

45、08:26, Uncontrolled Copy, (c) BSITR 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 standard

46、s 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 Mak

47、e 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 u

48、ser - 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

49、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 necess