ISA TR88 00 02-2015 Machine and Unit States An Implementation Example of ANSI ISA-88 00 01.pdf

1、 ANSI/ISA-TR88.00.02-2015 A Technical Report prepared by ISA and registered with ANSI Machine and Unit States: An implementation example of ANSI/ISA-88.00.01 Approved 26 October 2015 ANSI/ISA-TR88.00.02-2015, Machine and Unit States: An implementation example of ANSI/ISA-88.00.01 ISBN: 978-1-941546-

2、65-9 Copyright 2015 by ISA. All rights reserved. Not for resale. Printed in the United States of America. ISA 67 Alexander Drive P. O. Box 12277 Research Triangle Park, NC 27709 USA- 3 - ANSI/ISA-TR88.00.02-2015 Copyright 2015 ISA. All rights reserved. Preface This preface, as well as all footnotes,

3、 is included for information purposes only and is not part of ANSI/ISA-TR88.00.02-2015. This technical report has been prepared as part of the service of ISA, the International Society of Automation, toward a goal of uniformity in the field of instrumentation. To be of real value, this document shou

4、ld 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 Practices Board; ISA, 67 Alexander Drive; P.O. Box 12277; Research Triangle Park, NC 277099; Telephone (919) 54

5、9-8411; Fax (919) 549-8288; E-mail: standardsisa.org.This ISA Standards and Practices Department is aware of the growing need for attention to the metric system of units in general, and the International System of Units (SI) in particular, in the preparation of instrumentation standards, recommended

6、 practices, and technical reports. The Department is further aware of the benefits of USA users of ISA standards of incorporating suitable references to the SI (and the metric system) in their business and professional dealings with other countries. Toward this end, the Department will endeavor to i

7、ntroduce SI and acceptable metric units in all new and revised standards to the greatest extent possible. The Metric Practice Guide, which has been published by the Institute of Electrical and Electronics Engineers (IEEE) as ANSI/IEEE Std. 268-1992, and future revisions, will be the reference guide

8、for definitions, symbols, abbreviations, and conversion factors. It is the policy of ISA to encourage and welcome the participation of all concerned individuals and interests in the development of ISA standards. Participation in the ISA standards-making process by an individual in no way constitutes

9、 endorsement by the employer of that individual, of ISA, or of any of the standards, recommended practices, and technical reports that ISA develops. This standard is structured to follow the IEC guidelines. Therefore, the first three sections discuss the Scope of the standard, Normative References a

10、nd Definitions, in that order. CAUTION ISA ADHERES TO THE POLICY OF THE AMERICAN NATIONAL STANDARDS INSTITUTE WITH REGARD TO PATENTS. IF ISA IS INFORMED OF AN EXISTING PATENT THAT IS REQUIRED FOR USE OF THE STANDARD, IT WILL REQUIRE THE OWNER OF THE PATENT TO EITHER GRANT A ROYALTY-FREE LICENSE FOR

11、USE OF THE PATENT BY USERS COMPLYING WITH THE STANDARD OR A LICENSE ON REASONABLE TERMS AND CONDITIONS THAT ARE FREE FROM UNFAIR DISCRIMINATION. EVEN IF ISA IS UNAWARE OF ANY PATENT COVERING THIS STANDARD, THE USER IS CAUTIONED THAT IMPLEMENTATION OF THE STANDARD MAY REQUIRE USE OF TECHNIQUES, PROCE

12、SSES, OR MATERIALS COVERED BY PATENT RIGHTS. ISA TAKES NO POSITION ON THE EXISTENCE OR VALIDITY OF ANY PATENT RIGHTS THAT MAY BE INVOLVED IN IMPLEMENTING THE STANDARD. ISA IS NOT RESPONSIBLE FOR IDENTIFYING ALL PATENTS THAT MAY REQUIRE A LICENSE BEFORE IMPLEMENTATION OF THE STANDARD OR FOR INVESTIGA

13、TING THE VALIDITY OR SCOPE OF ANY PATENTS BROUGHT TO ITS ATTENTION. THE USER SHOULD CAREFULLY INVESTIGATE RELEVANT PATENTS BEFORE USING THE STANDARD FOR THE USERS INTENDED APPLICATION. HOWEVER, ISA ASKS THAT ANYONE REVIEWING THIS STANDARD WHO IS AWARE OF ANY PATENTS THAT MAY IMPACT IMPLEMENTATION OF

14、 THE STANDARD NOTIFY THE ISA STANDARDS AND PRACTICES DEPARTMENT OF THE PATENT AND ITS OWNER. ADDITIONALLY, THE USE OF THIS STANDARD MAY INVOLVE HAZARDOUS MATERIALS, OPERATIONS OR EQUIPMENT. THE STANDARD CANNOT ANTICIPATE ALL POSSIBLE APPLICATIONS OR ADDRESS ALL POSSIBLE SAFETY ISSUES ASSOCIATED WITH

15、 USE IN HAZARDOUS CONDITIONS. THE USER OF THIS STANDARD MUST EXERCISE SOUND PROFESSIONAL JUDGMENT CONCERNING ITS USE AND APPLICABILITY UNDER THE USERS PARTICULAR CIRCUMSTANCES. THE USER MUST ALSO CONSIDER THE ANSI/ISA-TR88.00.02-2015 - 4 - Copyright 2015 ISA. All rights reserved. APPLICABILITY OF AN

16、Y GOVERNMENTAL REGULATORY LIMITATIONS AND ESTABLISHED SAFETY AND HEALTH PRACTICES BEFORE IMPLEMENTING THIS STANDARD. THE USER OF THIS DOCUMENT SHOULD BE AWARE THAT THIS DOCUMENT MAY BE IMPACTED BY ELECTRONIC SECURITY ISSUES. THE COMMITTEE HAS NOT YET ADDRESSED THE POTENTIAL ISSUES IN THIS VERSION. T

17、he following people served as active members in the revision of this document: NAME COMPANY David Bell ATR Distributing Co (Wonderware) Jerry Golden B the document is not definitive in this respect. The models used, and applied, in this document are an extension of the models presented in ANSI/ISA-8

18、8.00.01 and are shown how they are applied to differing machine functionality. Discrete machine functionality is expressed graphically in several situations and described. The intent of this document is proposing specific implementation options and indicates a preference for a specific set of machin

19、e types. In 2013 this document was updated for three reasons: to simplify the document and enable easier adoption, to clarify existing materials and make them easier to apply and to make it more complete, including the best approaches being used to implement. Major changes include addition of a mini

20、mum set of PackTags, a minimum set of states and removal of examples and MES definitions not central to the documents purpose. Other changes addressed in this revision are: improved definition of suspending and holding, transition between modes, blocked and starved tags, stop reasons, and warnings.

21、Publication of this technical report that has been registered with ANSI has been approved by ISA, 67 Alexander Drive, Research Triangle Park, NC 27709. This document is registered as a technical report according to the Procedures for the Registration of Technical Reports with ANSI. This document is

22、not an American National Standard and the material contained herein is not normative in nature. Comments on the content of this document should be sent to ISA, 67 Alexander Drive, Research Triangle Park, NC 27709. Abstract The approaches used in programming discrete machines today are generally cons

23、idered to be solely dependent on the machine and the software engineer, or control systems programmer. This constant change offers little additional value and generally increases the total costs, from the designing and building of the process to operating and maintaining the system by the end user.

24、This technical report on the implementation of ANSI/ISA-88.00.01 in discrete machines breaks this paradigm and demonstrates how to apply the ANSI/ISA-88.00.01 standard concepts to automated machine states and modes. This technical report gives examples of general and specific machine state models an

25、d procedural methods. The report cites real control examples as implementations, and provides specific tag naming conventions; it also cites a number of common terms that are consistent with batch processing and ANSI/ISA-88.00.01. Key words state machine, state model, mode manager, machine state, un

26、it control mode, PackML, state commands, command tags, status tags, administration tags, base state model, functional programming, modular programming, machine control software, discrete machine software, PackTags, Weihenstephan, Production Data Acquisition, PDA, ISA88, TR88.ANSI/ISA-TR88.00.02-2015

27、 - 12 - Copyright 2015 ISA. All rights reserved. Introduction When the ANSI/ISA-88.00.01 standard is applied to applications across a plant, there is a need to align the terminologies, models and key definitions between different process types: continuous, batch, and discrete processes. Discrete pro

28、cesses involve machines found in the packaging, converting, and material handling applications. The operation of these machines is typically defined by the OEM, system integrator, end user, or is industry specific. A task group with members from technology providers, OEMs, system integrators, and en

29、d users was chartered by the OMAC (Organization for Machine Automation and Control) Packaging Workgroup. The task group generated the PackML guidelines as a method to show how the ANSI/ISA-88.00.01 concepts could be extended into packaging machinery. This technical report is intended to build upon a

30、nd formalize the concepts of the PackML guidelines and to show application examples. The purpose of the technical report is to: o Define a standard state-based model for automated machines. o Identify definitions for common terminology. o Explain to practitioners how to use state programming for aut

31、omated machines. o Provide references to actual implementation examples and templates from automation and control vendors. o Identify a common tag structure for automated machines in order to: Provide for “connect Terminology Associated with Filling Plants and their Constituent Machines ANSI/ISA-TR8

32、8.00.02-2015 - 14 - Copyright 2015 ISA. All rights reserved. www.omac.org Organization for Machine Automation and Control Website ISA-TR88.00.02-2008 The original edition of this technical report. ISO 22400 Automation Systems and Integration Key performance indicators (KPIs) for manufacturing operat

33、ions management. 3 Overview 3.1 Introduction Automated machine programming is typically done by software engineers, machine designers, and system integrators. The form and style of the machine software ranges from modular, to monolithic in nature. The objective of this report is to specify the appli

34、cation of a common software methodology that is consistent with the modular programming of automated machinery as described in the draft ISA-88.00.05 standard. The naming of specific software components, or operational aspects, is dependent on the needs of the automated machine. This report shall be

35、 interpreted in a general sense to encompass all automated machinery. It is focused on the overall operation and functionality of automated machines. This document enables a consistent method of machine interconnection and operability. The diagrams and examples shown in the report are specific in te

36、rms of the functionality they provide but can be implemented in various ways to fit most automated machinery and machine controllers; therefore the figures do not follow ISO/IEC 19501:2005 for depiction of software flow. If automated machinery is modelled in an ANSI/ISA-88.00.01 physical hierarchy,

37、the example mapping shown in Figure 1 is possible. The example in this document will assume that a machine can represent the unit level in the ISA88 hierarchy. Figure 1: Automated machines applied to ANSI/ISA-88.00.01 physical model - 15 - ANSI/ISA-TR88.00.02-2015 Copyright 2015 ISA. All rights rese

38、rved. Furthermore, the objective of this document is to provide a definition of machine (unit) modes and states, as well as state models corresponding to the different machine (unit) modes. In this example application of ANIS/ISA-88.00.01, the use of the state model and unit modes are extensible, bu

39、t the methods governing the way in which the modes and states are used is not. This technical report demonstrates the flexibility and ease in which this method can be implemented in terms of ISA88, as well as how it provides the “common look and feel” desired in automated machines. This model only c

40、onstrains the standard names and semantics for commonly used high level machine states as per a Base State Model. The ANSI/ISA-88.00.01 standard describes example modes and states as applied to equipment entities and procedural elements. This report identifies unit/machine modes and states which sho

41、uld be considered an extension of the examples in the ANSI/ISA-88.00.01 standard in order to meet the needs of automated machine processing. 3.2 Personnel and environmental protection The personnel and environmental protection control activity provides safety for people and the environment. No contr

42、ol activity should intervene between personnel and environmental protection and the field hardware it is designed to operate with. Personnel and environmental protection is, by definition, separate from the higher level control activities in this document. It may map to more than one software level

43、of the equipment as desired. A complete discussion of personnel and environmental protection, the classification of these types of systems, and the segregation of levels of interlocks within these systems is a topic of its own and beyond the scope of this document. 3.3 Control system compatibility T

44、he minimum PackTag requirements that are identified in this document can be executed on a majority of PLC systems used by packaging machine manufacturers. It can also be implemented on systems such as check weighers, date coders, robotics, and other ancillary devices that may utilize proprietary con

45、trol platforms. Even though the PackTags naming convention is using logical names, it can be implemented using register memory systems. 4 Unit/Machine states 4.1 Definition A unit/machine state completely defines the current condition of a machine. A machine state is determined by an ordered procedu

46、re, or programming routine, that can consist of one or more commands to other procedural elements1 or equipment entities, or be affected by the status of a procedural element1 or equipment entity, or both. In performing the function specified by the state, the machine software will issue a set of co

47、mmands to the machine procedural elements1 or equipment entities which in turn can report status. Only one major processing activity may be active in one machine at any time2. The linear sequence of major activities will drive a strictly sequentially ordered flow of control from one state to the nex

48、t state no more than one state of the base model is allowed to be active in one machine at the same time. 1 Term “procedural element” defined (ANSI/ISA-88.00.01) 2 A “major processing activity” corresponds to the term “equipment operation” as defined in ANSI/ISA-88.00.01. ANSI/ISA-TR88.00.02-2015 -

49、16 - Copyright 2015 ISA. All rights reserved. The 2010 revision to this technical report added a minimum set of states in Figure 2. It also clarified the difference between holding and suspending in Table 1. Note: At a lower level, the minor sub-activities (or control procedures) that are combined to form a major activity at the machine operation level, may indeed be taking place in parallel as well as in sequence as defined in ANSI/ISA-88.00.01 for equipment phases. 4.2 Types of states For the purposes of understanding, two machine state types are defined: