ANSI ISA 88.00.02-2001 Batch Control Part 2 Data Structures and Guidelines for Languages《批量控制.第2部分 语言的数据结构和指南》.pdf

《ANSI ISA 88.00.02-2001 Batch Control Part 2 Data Structures and Guidelines for Languages《批量控制.第2部分 语言的数据结构和指南》.pdf》由会员分享，可在线阅读，更多相关《ANSI ISA 88.00.02-2001 Batch Control Part 2 Data Structures and Guidelines for Languages《批量控制.第2部分 语言的数据结构和指南》.pdf（124页珍藏版）》请在麦多课文档分享上搜索。

1、Batch Control Part 2:Data Structures andGuidelines for LanguagesApproved 7 February 2001ANSI/ISA88.00.022001AMERICAN NATIONAL STANDARDISA The Instrumentation,Systems, andAutomation Society TMNOTICEOFCOPYRIGHTThis is a copyrighted document and may not be copied or distributed in anyform or manner wit

2、hout the permission of ISA. This copy of the document wasmadeforthesoleuseofthepersontowhomISAprovideditandissubjecttothe restrictions stated in ISAs license to that person. It may not be provided toany other person in print, electronic, or any other form. Violations of ISAscopyright will be prosecu

3、ted to the fullest extent of the law and may result insubstantial civil and criminal penalties.ANSI/ISA88.00.022001Batch Control Part 2: Data Structures and Guidelines for LanguagesCopyright 2001 by ISAThe Instrumentation, Systems, and Automation Society. All rights reserved. Not for resale. Printed

4、 in the United States of America. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), without the prior written permission of the Publisher.ISBN: 1-55617-745-3ISA67 Al

5、exander DrivePO Box 12277Research Triangle Park, NC 27709USA 3 ANSI/ISA88.00.022001PrefaceThis preface, as well as all footnotes and annexes, is included for information purposes and is not part of ANSI/ISA-88.00.02-2001.The standards referenced within this document may contain provisions that, thro

6、ugh reference in this text, constitute requirements of this document. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this document are encouraged to investigate the possibility of applying the most recent editi

7、ons of the standards indicated within this document. Members of IEC and ISO maintain registers of currently valid International Standards. ANSI maintain registers of currently valid U.S. National Standards. This document has been prepared as part of the service of ISAThe Instrumentation, Systems, an

8、d Automation Society, 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 asks that they be addressed to the Secretary, St

9、andards 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 attention to the metric system of units in gener

10、al, 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 system) in their business and professional deali

11、ngs 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 International System of Units (SI): The Modern Metr

12、ic System, published by the American Society for Testing b) responsible for specifying controls and the associated application programs for batch manufacturing plants; orc) involved in the design and marketing of products in the area of batch control.The following people served as active members of

13、ISA CommitteeSP88:NAME COMPANYL. Craig, Chairman Rohm and Haas Co. T. Fisher, Editor The Lubrizol Corp.M. Albano Honeywell, Inc.J. Barrault Siemens AGD. Brandl Sequencia Corp.B. Braunstein Exxon Chemical Co.E. Bristol The Foxboro Co.L. Charpentier GSE Systems Inc.T. Crowl Siemens Moore Process Autom

14、ationC. Eaves Intellution, Inc.D. Emerson Yokogawa Corp. of AmericaL. Falkenau E.I. du Pont de Nemours and Co.M. Fersky ABB Automation Inc.D. Fleming Rockwell AutomationA. Ghosh ARC 5 ANSI/ISA88.00.022001R. Hall Sequencia Corp.W. Hawkins HLQ Ltd.N. Haxthausen Novo Nordisk EngineeringB. Jensen Yokoga

15、wa Corp. of AmericaB. Korkmaz Automation Vision Inc.D. Kraska Geon Co.T. McFarlane Neles Automation Inc.R. Mergen The Lubrizol Corp.D. Moffatt Wonderware Corp.P. Moylan Rockwell AutomationT. Mller-Heinzerling Siemens AGL. Natiello MerckP. Nelson Dow Corning Corp.L. Noble ABB Automation, Inc.L. Pilla

16、i Pharmacia b) are amenable to translation to other technologies; c) are adequate; and d) are consistent with other sections of the standard.Multiple methods of information transfer have not been defined, nor has there been an attempt to identify all information that might be exchanged. In the futur

17、e, additional methods may be defined to provide alternate ways to exchange data.Clause 6 defines the symbols and rules for a graphical language that can be used to depict recipes. Recipes are the central feature of batch control, and they can address a wide range of complexity, but there is no one d

18、epiction that is ideal for all circumstances. A simple table, for example, might be the most appropriate recipe form for simple cases. This standard specifies a method for depiction of master and control recipe procedures that can be applied over a broader range of complexity. Although this standard

19、 is intended primarily for batch processes, there may be considerable value for other types of processes.This page intentionally left blank. 13 ANSI/ISA88.00.0220011 ScopeThis Part 2 standard on Batch Control defines data models that describe batch control as applied in the process industries, data

20、structures for facilitating communications within and between batch control implementations, and language guidelines for representing recipes.2 Normative referencesThe following normative documents contain provisions that, through reference in this text, constitute provisions this standard. At the t

21、ime of publication, the editions indicated were valid. All normative documents are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. Members of IEC and I

22、SO maintain registers of currently valid normative documents.IEC 60848:1988, Preparation of function charts for control systemsIEC 60902:1987, Industrial-process measurement and control: Terms and definitionsNOTE IEC 60902:1987 has been replaced by IEC 60050-351:1998, International electrotechnical

23、vocabulary-Part 351: Automatic controlIEC 61131-3:1993, Programmable controllers Part 3: Programming languagesIEC 61512-1:1997, Batch control Part 1: Models and terminologyANSI/ISA-88.01-1995, Batch Control Part 1: Models and TerminologyISO/IEC 9075:1992, Information processing systems Database lang

24、uage SQL with integrity enhancement3 DefinitionsISA hereby grants a non-exclusive, royalty-free, limited license under ISAs copyright in the standard, to copy, display and distribute this section of this ISA standard (including software included in or defined by such section), as follows:1. Producer

25、s of products or services intended to comply with the standard may incorporate this designated section, but only to the extent reasonably necessary to make, use, and distribute any product or service (including product documentation) that is compliant with this standard.2. End users of a product or

26、service made by a producer acting under the preceding license may reproduce and use the designated section, but only to the extent reasonably necessary to enjoy the intended functions of the product or service and to maintain, configure, or reconfigure systems to be compliant.3. Persons providing ed

27、ucation on or promotion of the standard may copy, display and distribute the designated section, but only to the extent reasonably necessary to provide information related to the standard.Except as expressly permitted, all other reproduction and distribution without permission of ISA is prohibited.

28、All copies of this section of the standard made or distributed under this license must cite the standard and include the following notice of copyright:ANSI/ISA88.00.022001 14 Copyright 2001 by ISAThe Instrumentation, Systems, and Automation Society. All rights reserved. Used with permission of ISA.F

29、or the purposes of this standard, the following definitions apply. Definitions and concepts expressed in ANSI/ISA-88.01-1995 apply, except where differences are explicitly stated in this Part 2 standard. Definitions in IEC 60902:1987 were also used as a basis.3.1 allocation symbol: a graphical symbo

30、l that is used to represent the encapsulation of the resource allocation and de-allocation rules for a recipe procedural element.3.2 building block: a recipe entity that exists in a library.3.3 enumeration set: a list of predefined strings and their associated numerical values.3.4 exchange table: a

31、database table that is used to exchange batch-related information between systems.3.5 link: an object that specifies the connection between two other objects (e.g., the connection between recipe entities or between recipe entities and transitions).3.6 procedure function chart:a graphical representat

32、ion of a recipe procedure that specifies the processing order for recipe procedural elements.3.7 recipe element: a structural entity that is used to represent recipe entities and symbols, except transitions and directed links, that are used in procedure function charts.3.8 recipe entity: the combina

33、tion of a procedural element with associated recipe information (e.g., header, formula, equipment requirements, other information). General, site, master, and control recipes are also recipe entities.4 Data modelISA hereby grants a non-exclusive, royalty-free, limited license under ISAs copyright in

34、 the standard, to copy, display and distribute this section of this ISA standard (including software included in or defined by such section), as follows:1. Producers of products or services intended to comply with the standard may incorporate this designated section, but only to the extent reasonabl

35、y necessary to make, use, and distribute any product or service (including product documentation) that is compliant with this standard.2. End users of a product or service made by a producer acting under the preceding license may reproduce and use the designated section, but only to the extent reaso

36、nably necessary to enjoy the intended functions of the product or service and to maintain, configure, or reconfigure systems to be compliant. 15 ANSI/ISA88.00.0220013. Persons providing education on or promotion of the standard may copy, display and distribute the designated section, but only to the

37、 extent reasonably necessary to provide information related to the standard.Except as expressly permitted, all other reproduction and distribution without permission of ISA is prohibited. All copies of this section of the standard made or distributed under this license must cite the standard and inc

38、lude the following notice of copyright:Copyright 2001 by ISAThe Instrumentation, Systems, and Automation Society. All rights reserved. Used with permission of ISA.4.1 IntroductionThis clause defines data models that specify a set of objects, attributes, and their basic relationships that cover the c

39、oncepts of Part 1 at a high level of abstraction. The models apply to interfaces to batch control systems in a technology-independent manner. The models are not intended to address the internal system architecture of batch control systems.The intended use of these models is to provide a starting poi

40、nt for developing interface specifications for software components that address any subset of Part 1.The models address all of Part 1 as an integrated object model, but they do not presume or preclude any specific system architecture or information exchange. The models do not assume any specific div

41、ision of functionality between systems.In the cases where the objects and relationships defined in this clause are presented through an interface, then that interface shall use the object names, the attribute names, and the relationships of this clause commensurate with the interface technology chos

42、en and the capabilities offered. An example of such an interface is the SQL relational table interface that is defined in clause 5.An exchange format or interface specification may implement only some objects or parts of objects (e.g., not all properties are defined). An exchange format or interface

43、 specification may also provide additional objects or properties (e.g., phase duration information), including the expansion of any data model attribute into multiple attributes. Any such implementation shall be consistent with the data model that is presented here and the concepts of Part 1.4.1.1 M

44、odeling techniquesThe models that are described in this clause are based on the Unified Modeling Language (UML) (see clause A.1).The tables describe only the class attributes of the objects. The relationships between objects are described in the figures.4.2 Overview modelThis model (see figure 1) gi

45、ves a high level overview of the main classes that are defined and the relations between these classes for the batch domain that is described by the Control Activity Model of Part 1. The individual object classes are more thoroughly described in the subsequent models in this subclause. ANSI/ISA88.00

46、.022001 16 Figure 1 Overview modelA general or site recipe is made up of a hierarchy of general recipe entities that correspond to the procedural entities (process stages, process operations, and process actions). A master recipe may be derived from a general or site recipe. The master recipe itself

47、 may be seen as a top-level master recipe entity. A master recipe is made up of a hierarchy of master recipe entities that correspond to the procedural entities (i.e., procedures, unit procedures, operations, phases). A batch schedule entry specifies production of a specific batch through the execut

48、ion of a recipe. A batch schedule is, in principle, a list that specifies the production of batches, and it includes information about timing. The product-specific information necessary for this purpose is derived from a related master recipe entity. Based on a Batch Schedule Entry, a control recipe

49、 starts as a copy of a specific version of a master recipe, and it is then modified to create the recipe that will produce the batch. A control recipe includes the information necessary for equipment control.Control recipe entities are created based on master recipe entities. A control recipe may be enhanced with additional information (e.g., scaling, equipment assignment), and it may be modified (including creating or removing control recipe entities).Equipment entities are selected and allocated to the control recipe entities.