ANSI ISA 5.06.01-2007 Functional Requirements Documentation for Control Software Applications《控制软件应用的功能要求文件》.pdf

《ANSI ISA 5.06.01-2007 Functional Requirements Documentation for Control Software Applications《控制软件应用的功能要求文件》.pdf》由会员分享，可在线阅读，更多相关《ANSI ISA 5.06.01-2007 Functional Requirements Documentation for Control Software Applications《控制软件应用的功能要求文件》.pdf（58页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD ANSI/ISA-5.06.01-2007 Functional Requirements Documentation for Control Software Applications Approved 29 October 2007 ANSI/ISA-5.06.01-2007 Functional Requirements Documentation for Control Software Applications ISBN: 978-1-934394-33-5 Copyright 2007 by ISA. All rights r

2、eserved. 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 or by any means (electronic mechanical, photocopying, recording, or otherwise), without the prior written permission of the Publis

3、her. ISA 67 Alexander Drive P.O. Box 12277 Research Triangle Park, North Carolina 27709 3 ANSI/ISA-5.06.01-2007 Copyright 2007 ISA. All rights reserved. Preface This preface, as well as all footnotes and annexes, is included for information purposes and is not part of ANSI/ISA-5.06.01-2007. This doc

4、ument 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 asks that they be

5、 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 attention to the

6、 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 system) in their

7、 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 International Syste

8、m of Units (SI): The Modern Metric System, published by the American Society for Testing as such, they may be designated in the FRS after selection of the control system. ANSI/ISA5.06.012007 18 Copyright 2007 ISA. All rights reserved. Figure 5 Database documentation The five sections of the database

9、 shown in Figure 5 can be consecutive column headings across a spreadsheet. They are shown here as separate sections of the table due to space limitations. In actual use on a spreadsheet they will all follow left to right on one table. The separate sections shown here may be useful for breaking out

10、the table for a printed copy. Leaving this as a continuous spreadsheet will make using it easier. Each row would then show the relevant information for a single instrument or control module; associated alarms may be designated using multiple entries per cell, additional columns or separate tags. Thi

11、s document is the cornerstone of the FRS because it forms the basis or foundation for the other documents that follow. It is applicable for both continuous and batch control but typically contains many more internal variables when applied to a batch process. 19 ANSI/ISA5.06.012007 Copyright 2007 ISA

12、. All rights reserved. The column names for the database (Figure 5) are suggestions only. Depending on the system, software to be used and other parameters, columns may need to be added, deleted or renamed. The planned uses for each column are: Basic Point Data CM Tag: the control module name usuall

13、y corresponding to the instrument tag number shown on the P may identify special or atypical feature requirements (not used in the examples that follow). I/O Interface Data Point Type: indicates the functionality of the item i.e., discrete vs. analog vs. digital, control vs. alarm, and input vs. out

14、put; optionally may refer to a separately specified class of control modules, equipment modules or units. Device Type: provides additional description of the item such as valve, motor starter, software / function block and may note signal conditioning such as characterization (chr) or square root ex

15、traction () to be performed within the field device. Signal Type: shows type of signal for the I/O loop. Signal Conditioning: shows any adjustments that must be made to the input signal for the desired control action-i.e., pressure or temperature linearization, square-root extraction. I/O Tags: show

16、s all P cabinet location and software identification for troubleshooting, etc. Human/Machine Interface Data Scale: the zero and full-scale values or enumerated state descriptors for each signal. Eng Units: unit descriptor to accompany the value display. Descriptor: the full description of the instru

17、ment or loop for use on alarm and event lists, point details and other displays having sufficient space. Keywords: the abbreviated description of the instrument or loop for use on group displays and others having limited space. Data Logging operators, interlocks or phase logic initiate all state tra

18、nsitions; class definitions should be reusable from project to project). Sequence definition and parameter identification for phases or classes of like phases whose instances are identified relative to a particular EM, unit or class of like EM or units referenced in the ANSI/ISA5.06.012007 24 Copyri

19、ght 2007 ISA. All rights reserved. database (usually oriented toward minor processing functions requiring little product-specific knowledge; typically interfaces to field devices indirectly by manipulating CM and/or EM states; operators or recipe sequences initiate phase execution; class definitions

20、 for common requirements should be reusable from project to project). Definition of phase sequencing, equipment requirements/arbitration and process parameters necessary to manufacture each product or class of products (coordinates all product-specific control requirements; operator or higher-level

21、scheduling systems initiate recipe execution) Accommodation of both normal and abnormal process conditions for each of the above including hierarchical propagation of consequential actions as needed. Preparing the product-specific requirements necessitates a detailed knowledge of the operations to b

22、e conducted in the subject equipment. Typically, a process write-up or batch sheet and standard operating procedure will provide the necessary knowledge. Using common or generic terms for the phase names will make this document more understandable for others who use it. Sample operation names includ

23、e: prepare, react, distill, extract, solvent strip, clean and shutdown. Typical phase names include: initial, fill, mix, heat, cure, settle, drain/dump and transfer. The user can employ these or other names as appropriate. These names need to be clearly understood by the plant personnel. One or more

24、 phases may require that multiple actions be completed in order to satisfy the phase requirements. These multiple actions are called steps. All of these steps are typically shown in one column of the spreadsheet. The order in which these must be satisfied is indicated with numbers in parenthesis aft

25、er the listed action. Where additional distinction between the steps is necessary the column under the phase can be split to show the different steps. If an equipment module is part of the unit, this will need to be shown in the sequence matrix. If the equipment module is shared by multiple units it

26、 will require its own matrix. Otherwise, its phases can be incorporated into the matrix for that unit. Two examples are a heating/cooling system for a reactor jacket and charging manifold with valves and a pump. Using an equipment module may simplify the software programming during integration. The

27、Normal Sequence matrix (Figure 7a) provides information for all expected usual or routine operations. As indicated, it shows the expected operation of each discrete and analog device associated with the unit. Where there are particular conditions that must be met at the start or end of a phase these

28、 should be listed. These conditions include the setpoints of analog controls that must be satisfied as given in the Recipe Sequence below. Operator messages will appear on the HMI (human-machine interface) to cue an activity by the operator. Batch report variables will be configured into reports to

29、be prepared as hardcopy or electronic media. If manual operations are required to complete the phase, an operator message will cue the personnel and wait for the appropriate response before continuing the phase processing. Two formats for the Sequence matrix are shown in the examples. The first cont

30、ains less-detailed information and will often satisfy the needs of the URS. All of the operations, phases and steps can be shown; however, little detail of their functionality is possible here. Each phase occupies a single column in the spreadsheet. This provides a good overview of the control schem

31、e. This does not contain sufficient detail for an instrumentation engineer or system integrator. The second format provides the level of detail required by these last functions. The information for each phase is detailed over several columns. It can show the details of each control function needed f

32、or the system to function. This level of detail is necessary for the FRS and is illustrated for just one of the phases in each example. It also provides the information needed to validate the operation of a control system during start-up. 25 ANSI/ISA5.06.012007 Copyright 2007 ISA. All rights reserve

33、d. The Hold Sequence (Figure 7b) indicates which conditions are considered to be abnormal by the system and the resulting actions in response to these conditions. If any of the abnormal conditions are met, the system will proceed to the condition shown under Hold Actions and the operator message wil

34、l be displayed. When the abnormal condition no longer exists the “Recovery” status will be initiated if the system is in full automatic operation. The Recipe Sequence matrix (Figure 7c) may show general recipe information or have specific information for several recipes to be programmed for that uni

35、t. Each parameter needed for a recipe is shown with the permission level required by a person to enter or modify that parameter. Where there are limits on a parameter for a specific phase, this is shown in the appropriate column. This helps prevent entry of wrong values for the parameters. The allow

36、able modes of operation for each phase include manual and automatic. Under automatic operation, a recipe will proceed without operator interaction unless a hold condition occurs or interaction is required for a particular part of a phase. 4.1.4 Human - Machine Interface (HMI) ISA-5.5-1985, Graphic S

37、ymbols for Process Displays, provides a good starting point in defining the shapes of process equipment for the dynamic graphic displays on operator console screens. It also provides guidelines for use of color for graphic displays. Many hardware vendors have a built-in library of ISA symbols in the

38、ir graphic display packages. In addition to displays that usually are supplied as standard with most systems such as controller faceplates, alarm summary displays and trend displays, custom displays may be required to facilitate the operation of a control system. Examples include the interlock and s

39、equence status displays shown in Figures 12b and 12c. An important part of the HMI definition is setting the data security and access levels. A typical definition is shown in Figure 8. Access needs to be set for different functions in the system such as changing loop set points and changing recipes

40、by various personnel such as operators, supervisors and engineers. For some systems, many more access levels are available. A typical example of this is multiple operator classes with permissions limited by process area(s). PERSONNEL TYPE FUNCTION Operator Technician Supervisor Engineer Controller T

41、uning NO YES NO YES Controller SP Change YES YES YES YES Interlock Setting Change NO YES NO YES Alarm SP Change NO YES YES YES Recipe Selection NO NO YES YES Figure 8 Data security definition This page intentionally left blank. 27 ANSI/ISA5.06.012007 Copyright 2007 ISA. All rights reserved. Annex A

42、(informative) Application Example 1: Batch Reactor The following chemical reactor example illustrates the application of the methodology to a simple batch process. As the P (2) the logical connections to other control software; and (3) the software address as appropriate to the control system used f

43、or the particular process system. The HMI information for scale and engineering units (Figure 10b) will come from process information and possibly equipment design limits. The “keyword” is necessary only if the HMI display has an insufficient number of characters for the full length “descriptor.” Th

44、e alarm function and control loop data (Fig. 10c) will impact the Sequence Matrix inputs. Note that these three sections of Figure 10 will typically appear left to right in a spreadsheet and not as three separate items as shown in this document. This will more clearly show the relationship between t

45、he various sets of information. Obviously in this format the first three columns need not be repeated. Figure 11a illustrates the software interlock matrix for Unit R-101, which provides the following process functionality based on the P&ID: (a) If the liquid level is too low interlocks UC-102 and U

46、C-104 will shut off the mixer and pump. (b) Interlock UC-104 will prevent the drain pump from operating if the drain valve is closed. (c) Interlock UC-003 shuts down the charging control module when the desired charge quantity has been satisfied. The Manual Reset capability for each interlock in thi

47、s example is provided by de-energizing the associated “Hand Switch” that is normally used to manually change valve position or motor condition. In this way the Hand Switch outputs will not immediately reactivate the interlocked device when the initiating condition clears. Any additional interlocks w

48、ould be set up the same way. Definitions for the hazard and safety levels are based on the example shown in Figure 6. Figure 11b illustrates the software interlock matrix for the exclusive use common Equipment Module EM-1 which provides the following functionality based on standard operating practic

49、es: (a) Reinforce the hardwired charge valve interlocks shown on the P&ID by de-energizing the associated Hand Switch when a reactor level exceeds its safe limit, thereby requiring operator intervention (Manual Reset) for charging to resume after the condition clears. (b) Additional interlocks help to assure integrity of the charge path and measurement of the charged quantity. CM TAG LOCATION P&ID POINT TYPE * DEVICE TYPE SIGNAL TYPE I/O TAGS I/O ADDRESSES * XV-001 R-101 P-101 VLV-FC BALL VALVE 24 VDC ZSC, ZSO, XS DI (2), DO (1) XV-002 R-10