1、 AMERICAN NATIONAL STANDARD ANSI/ISA62453-1 (103.00.01)2011 Field device tool (FDT) interface specification Part 1: Overview and guidance Approved 31 May 2011 ANSI/ISA62453-1 (103.00.01)-2011, Field device tool (FDT) interface specification Part 1: Overview and guidance ISBN: 978-0-876640-55-5 Copyr
2、ight 2011 IEC and ISA. These materials are subject to copyright claims of IEC and ISA. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission of ISA. All requests pertaining to the ANSI/ISA62453-1 (103.00.01)-2011 Sta
3、ndard should be submitted to ISA. ISA 67 Alexander Drive P. O. Box 12277 Research Triangle Park, North Carolina 27709 USAANSI/ISA62453-1(103.00.01)2011 - 3 - Preface This preface, as well as all footnotes and annexes, is included for information purposes and is not part of ANSI/ISA62453-1 (103.00.01
4、)2011. This document has been prepared as part of the service of ISA toward a goal of uniformity in the field of instrumentation. To be of real value, this document should not be static but should be subject to periodic review. Toward this end, the Society welcomes all comments and criticisms and as
5、ks that they be addressed to the Secretary, Standards and Practices Board; ISA; 67 Alexander Drive; P. O. Box 12277; Research Triangle Park, NC 27709; Telephone (919) 549 -8411; Fax (919) 549-8288; E-mail: standardsisa.org. The ISA Standards and Practices Department is aware of the growing need for
6、attention to the metric system of units in general, and the International System of Units (SI) in particular, in the preparation of instrumentation standards. The Department is further aware of the benefits to USA users of ISA standards of incorporating suitable references to the SI (and the metric
7、system) in their business and professional dealings with other countries. Toward this end, this Department will endeavor to introduce SI-acceptable metric units in all new and revised standards, recommended practices, and technical reports to the greatest extent possible. Standard for Use of the Int
8、ernational System of Units (SI): The Modern Metric System , published by the American Society for Testing integrated and consistent life-cycle data exchange within a control system including its fieldbuses, devices, function blocks and modular sub-systems; simple and powerful manufacturer-independen
9、t integration of different automation devices, function blocks and modular sub-systems into the life-cycle management tools of a control system. ANSI/ISA62453-1(103.00.01)2011 - 10 - The FDT concept supports planning and integration of monitoring and control applications, it does not provide a solut
10、ion for other engineering tasks such as “electrical wiring planning”, “mechanical planning”. Plant management subjects such as “maintenance planning”, “control optimization”, “data archiving”, are not part of this FDT standard. Some of these aspects may be included in future editions of FDT publicat
11、ions. ANSI/ISA62453-1(103.00.01)2011 - 11 - Field Device tool (FDT) interface specification - Part 1: Overview and guidance 1 Scope This part of IEC ISA-62453 presents an overview and guidance for the IEC ISA-62453 series. It explains the structure and content of the IEC ISA-62453 series (see Clause
12、 5); provides explanations of some aspects of the IEC ISA-62453 series that are common to many of the parts of the series; describes the relationship to some other standards. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated r
13、eferences, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 61158 (all parts), Industrial communication networks Fieldbus specifications IEC 61784 (all parts), Industrial communication networks Profiles ISO/
14、IEC 19501:2005, Information technology Open Distributed Processing Unified Modeling Language (UML) Version 1.4.2 3 Terms, definitions, symbols, abbreviations and conventions For the purposes of this document the following terms, definitions and abbreviations apply. 3.1 Terms and definitions 3.1.1 ac
15、tor coherent set of roles that users of use cases play when interacting with these use cases based on ISO/IEC 19501 NOTE An actor has one role for each use case with which it communicates. 3.1.2 address communication protocol specific access identifier 3.1.3 application software functional unit that
16、 is specific to the solution of a problem in industrial-process measurement and control ANSI/ISA62453-1(103.00.01)2011 - 12 - NOTE An application may be distributed among resources, and may communicate with other applications. 3.1.4 business object object representing specific behavior (e.g. DTM, BT
17、M and channel) NOTE The term business object has been defined originally as part of the design pattern 3-tier architecture, where the business object is part of the business layer. 3.1.5 Block Type Manager (BTM) specialized DTM to manage and handle a block 3.1.6 communication fieldbus protocol speci
18、fic data transfer 3.1.7 Communication Channel access point for communication to field device 3.1.8 configuration system created by configuring the plant components and the topology 3.1.9 configure (see also parameterize) setting parameters at the instance data as well as the logical association of p
19、lant components to build up the plant topology (off-line) 3.1.10 connection established data path for communication with an selected device 3.1.11 data set of parameter values 3.1.12 data type set of values together with a set of permitted operations ISO 2382 series 3.1.13 DCS manufacturer / system
20、manufacturer manufacturer of the engineering system 3.1.14 device (see also field device) ANSI/ISA62453-1(103.00.01)2011 - 13 - a) networked independent physical entity of an industrial automation system capable of performing specified functions in a particular context and delimited by its inter fac
21、es IEC 61499-1 b) entity that performs control, actuating and/or sensing functions and interfaces to other such entities within an automation system 3.1.15 device manufacturer manufacturer of fieldbus devices 3.1.16 device type device characterization based on abstract properties such as manufacture
22、r, fieldbus protocol, device type identifier, device classification, version information or other information NOTE The scope of such characterizations can vary depending on the properties that are used in the definition of such a set and is manufacturer specific for each DTM. 3.1.17 distributed syst
23、em FDT objects that jointly are executed on different PCs in a network NOTE The implementation of such a distributed system is vendor specific (for example: DTM and Presentation are executed on different PCs or DTMs are executed in multi-user system on different PCs) 3.1.18 documentation human reada
24、ble information about a device instance NOTE This may be electronic information in a database. 3.1.19 Device Type Manager (DTM) a) software component containing device specific application software b) generic class and means “Type Manager“ NOTE The D is kept because the Acronym is well-known in the
25、market. 3.1.20 DTM device type software module for a particular device type within the DTM NOTE A DTM may contain one or more DTM device types 3.1.21 entity particular thing, such as a person, place, process, object, concept, association, or event IEC 61499-1 3.1.22 field device (see also device) AN
26、SI/ISA62453-1(103.00.01)2011 - 14 - 3.1.23 Frame Application FDT runtime environment 3.1.24 FDT model interface specification for objects and object behavior in a monitoring and control system 3.1.25 function specific purpose of an entity or its characteristic action IEC 61499-1 3.1.26 hardware phys
27、ical equipment, as opposed to programs, procedures, rules and associated documentation ISO/AFNOR Dictionary of computer science 3.1.27 implementation development phase in which the hardware and software of a system become operational IEC 61499-1 3.1.28 instantiation creation of an instance of a spec
28、ified type IEC 61499-1 3.1.29 interface shared boundary between two functional units, defined by functional characteristics, signal characteristics, or other characteristics as appropriate IEC 60050-351 3.1.30 mapping set of values having defined correspondence with the quantities or values of anoth
29、er set ISO/AFNOR Dictionary of computer science 3.1.31 multi-user environment environment which allows operation by more than one user 3.1.32 network all of the media, connectors, repeaters, routers, gateways and associated node communication elements by which a given set of communicating devices ar
30、e interconnected IEC 61158-5-X ANSI/ISA62453-1(103.00.01)2011 - 15 - NOTE In this document network is used to express that one or more interconnected fieldbus systems with different protocols can be applied. 3.1.33 nested communication communication using a hierarchy of communication systems 3.1.34
31、operation well-defined action that, when applied to any permissible combination of known entities, produces a new entity ISO/AFNOR Dictionary of computer science 3.1.35 parameter variable that is given a constant value for a specified application and that may denote the application ISO/AFNOR Diction
32、ary of computer science 3.1.36 parameterize (see also configure) setting parameters in a device or a block or an object 3.1.37 persistent data stored data that is preserved through shut down/restart and maintenance activities 3.1.38 Process Channel representation of process value and its properties
33、3.1.39 service functional capability of a resource, which can be modeled by a sequence of service primitives IEC 61499-1 3.1.40 session instance of user interactions within the FDT model 3.1.41 synchronization synchronization of data depending on the context where used NOTE For example, synchronizat
34、ion can occur between the DTM and device or between several DTM instances having a reference to the same instance data. 3.1.42 system set of interrelated elements considered in a defined context as a whole and separated from its environment IEC 60050-351 ANSI/ISA62453-1(103.00.01)2011 - 16 - NOTE 1
35、Such elements may be both material objects and concepts as well as the results thereof (e.g. forms of organization, mathematical methods, and programming languages). NOTE 2 The system is considered to be separated from the environment and other external systems by an imaginary surface, which can cut
36、 the links between them and the considered system. 3.1.43 transient data temporary data which have not been stored (while configuring or parameterizing) 3.1.44 type software element, which specifies the common attributes shared by all instances of the type IEC 61499-1 3.1.45 variable software entity
37、 that may take different values, one at a time IEC 61499-1 NOTE 1 The values of a variable are usually restricted to a certain data type. NOTE 2 Variables are described as input variables, output variables, and internal variables. 3.1.46 use case specification of a sequence of actions, including var
38、iants, that a system (or other entity) can perform, interacting with actors of the system ISO/IEC 19501 3.2 Abbreviations BTM Block Type Manager COM Component Object Model CP Communication profile CPF Communication profile family DCS Distributed control system DD Device description DTM Device Type M
39、anager ERP Enterprise resource planning FA Frame Application FB Function block FDT Field device tool GUI Graphical user interface ID Identifier IDL Interface definition language I/O Input/output IT Information technology MES Manufacturing execution systems OEM Original equipment manufacturer OLE Obj
40、ect Linking and Embedding OPC Open connectivity via open standards (originally: OLE for Process Control) ANSI/ISA62453-1(103.00.01)2011 - 17 - PC Personal computer PLC Programmable logic controller SCADA Supervisory, control and data acquisition UML Unified modeling language UUID Universal unique id
41、entifier XML Extensible markup language 3.3 Conventions The conventions for UML notation used in the IEC ISA-62453 series are defined in Annex A. 4 FDT overview 4.1 State of the art In industrial automation, a control system often comprises many binary and analog input/output signals transmitted via
42、 a communication network. Numerous field devices provided by different manufacturers have to be included in the network by direct connection or I/O multiplex units. Many applications use more than 100 different field device types from various device manufacturers. Each device has specific configurat
43、ion and parameterization functions to support its designed task. These device-specific properties and settings have to be taken into consideration when configuring a fieldbus coupler and bus communication for the device. The device presence and its capability have to be made known to the control sys
44、tem. Device input and output signals an d function block services need to be effectively integrated into the planning of the control system. In the absence of a common interface standard, the large number of different device types and suppliers within a control system project makes the configuration
45、 task difficult and time-consuming. Various different tools have to be used (see Figure 1). The user requirement for consistency of data, documentation and application configurations can only be guaranteed by intensive and costly system testing. A common location for service and diagnostic tasks in
46、the control system does not fully cover the functional capabilities of available fieldbus devices nor does it guarantee that different device or module-specific tools can be integrated into other system software tools. Typically, device-specific tools can only be connected directly to a specific fie
47、ldbus or directly to a specific field device type. ANSI/ISA62453-1(103.00.01)2011 - 18 - L ar g e co n t r o l sy st em s 10 m an u f act u r er s 100 d evic e t yp es 100 00 I/O sD evic e d esc r ip t io nF u n ct io n b lo cksD evic e ad d r ess esD evic e p ar am et er sD evic e I/O sF u n ct io
48、n C h ar tF ield b u s T yp e 1F ield b u s T yp e 2L in k T yp e 3T o o l nT o o l 2T o o l 1T o o l 3Figure 1 Different tools and fieldbusses result in limited integration 4.2 Objectives of FDT 4.2.1 General features Full integration of fieldbus devices or modules into automation systems requires
49、a communication path from central engineering or operator terminals via the system and fieldbusses to the individual field devices. FDT supports: central facilities for planning, diagnostics and service with direct access to all devices ; integrated, consistent configuration and documentation of the automation system, its fieldbusses and devices; organization of common data for the automation system and the field devices; central data management and data security; simple, fast integration of
