1、 TECHNICAL REPORT ANSI/ISA-TR104.00.03-2010 EDDL: Meeting the requirements for integrating fieldbus devices in engineering tools for field devices Approved 29 September 2010 ANSI Technical Report prepared by ISA and registered 31 January 2011 ANSI/ISA-TR104.00.03-2010 EDDL: Meeting the requirements
2、for integrating fieldbus devices in engineering tools for field devices ISBN: 978-1-936007-76-9 Copyright 2010 by ISA. All rights reserved. Not for resale. Printed in the United States of America. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form
3、 or by any means (electronic mechanical, photocopying, recording, or otherwise), without the prior written permission of the Publisher. ISA 67Alexander Dr Research Triangle Park, North Carolina 27709 USA - 3 - ANSI/ISA-TR104.00.03-2010 Foreword Publication of this Registered Technical Report has bee
4、n approved by the Accredited Standards Developer. This document is registered as a Technical Report series of publications according to the procedures for the Registration of Technical Reports with ANSI. This document is not an American National Standard and the material contained herein is not norm
5、ative in nature. Comments on the content of this document should be sent to the Accredited Standards Developer. This preface, as well as all footnotes and annexes, is included for information purposes and is not part of ANSI/ISA-TR104.00.03-2010. This document has been prepared as part of the servic
6、e of ISA toward a goal of uniformity in the field of automation. 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 asks that they be addressed to the Secretary, Standards and Practic
7、es 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 endeavors to introduce SI-acceptable metric units in all new and revised standards, recommended pra
8、ctices, and technical reports to the greatest extent possible. Standard for Use of the International System of Units (SI): The Modern Metric System, published by the American Society for Testing officially known as an EDDL method 3.2 Abbreviated terms and acronyms EDD Electronic Device Description a
9、ccording to IEC 61804-3 EDDL Electronic Device Description Language according to IEC 61804-3 DCS Distributed Control System 4 Requirement analysis 4.1 Conventions This requirement analysis evaluates each clause in NAMUR NE 105 containing a requirement. The clause number in NAMUR NE 105 is indicated
10、within parenthesis for each sub-clause of this clause and starts with a summary of the requirement in NAMUR NE 105. This TR then proceeds to analyze how EDDL meets this requirement. NOTE The summary for each requirement does not take the place of the original NAMUR recommendation. This is an abridge
11、d version. In case of questions, users should follow the original NAMUR NE 105 text. ANSI/ISA-TR104.00.03-2010 - 14 - 4.2 Investment safety (3.1) 4.2.1 NAMUR requirement summary Plants and their automation systems remain operational for 15 years or more. Constant software upgrades would present an u
12、ndue burden. Therefore, shared components or application programming interfaces between software programs not updated together as one must be eliminated or minimized to avoid cascading upgrades. Investment must be protected by stable interoperability. Operating system dependencies must be minimized
13、because: Operating system version should not be made obsolete by EDD files for new device versions. EDD files should not be made obsolete by operating system patches, service packs, or upgrade. EDD files should not be made obsolete by new software versions. It must be possible to integrate all prese
14、nt and future devices in any tool. 4.2.2 How EDDL meets this requirement An EDD file contains only text in a common format; it is a document, not software, and therefore is independent of the operating system. Thus, the files are intrinsically unaffected by changes in off-the-shelf IT products such
15、as operating system and software during the operation of process plants, and therefore do not reduce the lifecycle of the system as a whole. This also makes long-term support easier for the DCS and device manufacturers. That is, EDD files are compatible with old and new versions of operating systems
16、 and old and new versions of the software using the EDD files. From the description written in EDDL, some device manufacturers use the “tokenizer“ utility to generate encrypted EDD files for the latest version and prior versions of the EDDL standard, enabling a new device to also be integrated to ol
17、d software. By loading the EDD files, it is possible to operate and parameterize field devices from a single tool instead of using device-specific solutions. 4.3 Version conflicts (3.2) 4.3.1 NAMUR requirement summary Change of version of software components in modular systems such as operating syst
18、ems or software programs is a source of substantial risk of interfering with DCS software as a whole. If the software using the EDD files is integrated with the DCS, the EDD files must not interfere with the DCS in any way. Devices must be supplied together with past and current version EDD files. I
19、t must be possible to write a new version EDD file for an existing device in the future. Software using the EDD files must support past and current version EDD files. 4.3.2 How EDDL meets this requirement An EDD file contains only text, a document. No software is installed to support a new device ty
20、pe or version. Therefore, there are no software components to interfere with the DCS software. - 15 - ANSI/ISA-TR104.00.03-2010 Each version of each device type from each manufacturer has a unique EDD file. Thus, existing EDD on the system are not removed or replaced when new devices types or versio
21、ns are added. Software using the EDD files includes interpreter services for both old and existing version EDD files. New version EDD files can be written for old devices to enhance the user experience. From the description of the device written in EDDL, some vendors use the “tokenizer“ to generate
22、encrypted EDD files for the latest version and prior versions of the EDDL standard, enabling a new device to also be integrated to old software. 4.4 Integration of devices (installation it is a document, not software. An EDD file cannot be coded with a locking mechanism. The content of an EDD file s
23、hould comply with the EDDL standard and with that the EDD file is freely available in principle. 4.10 Cross-platform compatibility (5.3) 4.10.1 NAMUR requirement summary EDD files should not be made obsolete by operating system patches, service packs, or upgrades. 4.10.2 How EDDL meets this requirem
24、ent An EDD file contains only text, a document, not software, and therefore is independent of the operating system. Thus, the files are intrinsically unaffected by changes in the operating system. 4.11 Full support of device functionality (5.4) 4.11.1 NAMUR requirement summary EDD files should give
25、access to all device parameters and features. Graphics should be used when required. 4.11.2 How EDDL meets this requirement EDDL enables both standard and manufacturer-specific parameters in a device to be described. Graphical elements such as images, waveform graphics, needle gauges, trend charts,
26、and tables, are provided in EDDL. 4.12 Standardized data filing (5.5) 4.12.1 NAMUR Requirement Summary Parameters displayed in multiple workstations must be synchronized. 4.12.2 How EDDL meets this requirement An EDD file contains only text, a document, not software. Because parameter changes and ot
27、her functions are executed by the software using the EDD files and not the individual EDD file itself, the device manufacturer need not program data synchronization functionality in the EDD file. Therefore, data synchronization functionality in the software using the EDD files supports all devices r
28、egardless of manufacturer or type. - 19 - ANSI/ISA-TR104.00.03-2010 4.13 Certification (6) 4.13.1 NAMUR requirement summary EDD files and software using the EDD files should be tested by an independent third-party to ensure interoperability. 4.13.2 How EDDL meets this requirement An EDD file contain
29、s only text, a document, not software. Therefore, the information about the device is not encapsulated, but externally accessible. The interoperability test software extracts information about the device from the EDD file and communicates with the device to compare the description of the device in t
30、he file against the data in the actual device. Each EDD file only supports a single version of a single device type. Therefore, each file need only be tested against a single version of a single device type. Software using the EDD files is tested to verify it can render the different graphical eleme
31、nts, handle conditionals, interpret methods, and so forth. Common and protocol specific test requirements are defined by the EDDL Cooperation Team (ECT) and protocol organisations to ensure common behaviour. ANSI/ISA-TR104.00.03-2010 - 20 - Bibliography NAMUR recommendation NE 105, Version: 24.08.20
32、04 - Specifications for Integrating Fieldbus Devices in Engineering Tools for Field Devices ANSI/ISA-61804-3 (104.00.01)-2007 - Function Blocks (FB) for Process Control - Part 3: Electronic Device Description Language (EDDL) ANSI/ISA-TR61804-4 (104.00.02)-2007 - Function Blocks (FB) for Process Cont
33、rol - Part 4: EDD Interoperability Guideline InTech June 2008 - German lab tests benefits of EDDL for integrating field devices, By Sven Seintsch, BIS Prozesstechnik GmbH Developing and promulgating sound consensus standards, recommended practices, and Technical Reports is one of ISAs primary goals.
34、 To achieve this goal the Standards and Practices Department relies on the technical expertise and efforts of volunteer committee members, chairmen and reviewers. ISA is an American National Standards Institute (ANSI) accredited organization. ISA administers United States Technical Advisory Groups (
35、USTAGs) and provides secretariat support for International Electrotechnical Commission (IEC) and International Organization for Standardization (ISO) committees that develop process measurement and control standards. To obtain additional information on the Societys standards program, please write: ISA Attn: Standards Department 67 Alexander Drive P.O. Box 12277 Research Triangle Park, NC 27709 USA ISBN: 978-1-936007-76-9
