1、Process Control SystemsPart 1Process Control Systems Functions and Functional Specification DevelopmentAPI RECOMMENDED PRACTICE 554 SECOND EDITION, JULY 2007Process Control SystemsPart 1Process Control Systems Functions and Functional Specification DevelopmentDownstream SegmentAPI RECOMMENDED PRACTI
2、CE 554 SECOND EDITION, JULY 2007SPECIAL NOTESAPI publications necessarily address problems of a general nature. With respect to particular circumstances, local, state, and federal laws and regulations should be reviewed.Neither API nor any of APIs employees, subcontractors, consultants, committees,
3、or other assignees make any warranty or representation, either express or implied, with respect to the accuracy, completeness, or usefulness of the information contained herein, or assume any liability or responsibility for any use, or the results of such use, of any information or process disclosed
4、 in this publication. Neither API nor any of APIs employees, subcontractors, con-sultants, or other assignees represent that use of this publication would not infringe upon pri-vately owned rights.Users of this Recommended Practice should not rely exclusively on the information con-tained in this do
5、cument. Sound business, scientific, engineering, and safety judgement should be used in employing the information contained herein.API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure the accuracy and reliability of the data contained in the
6、m; however, the Institute makes no representation, warranty, or guarantee in connection with this publication and hereby expressly disclaims any liability or responsibility for loss or damage resulting from its use or for the violation of any authorities having jurisdiction with which this publi-cat
7、ion may conflict.API publications are published to facilitate the broad availability of proven, sound engineer-ing and operating practices. These publications are not intended to obviate the need for applying sound engineering judgment regarding when and where these publications should be utilized.
8、The formulation and publication of API publications is not intended in any way to inhibit anyone from using any other practices.Any manufacturer marking equipment or materials in conformance with the marking requirements of an API standard is solely responsible for complying with all the applicable
9、requirements of that standard. API does not represent, warrant, or guarantee that such prod-ucts do in fact conform to the applicable API standard.All rights reserved. No part of this work may be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopy
10、ing, recording, or otherwise, without prior written permission from the publisher. Contact the Publisher, API Publishing Services, 1220 L Street, N.W., Washington, D.C. 20005.Copyright 2007 American Petroleum InstituteFOREWORDNothing contained in any API publication is to be construed as granting an
11、y right, by impli-cation or otherwise, for the manufacture, sale, or use of any method, apparatus, or product covered by letters patent. Neither should anything contained in the publication be construed as insuring anyone against liability for infringement of letters patent.The following definitions
12、 apply:Shall: As used in a standard, “shall” denotes a minimum requirement in order to conform to the specification.Should: As used in a standard, “should” denotes a recommendation or that which is advised but not required in order to conform to the specification.This document was produced under API
13、 standardization procedures that ensure appropriate notification and participation in the developmental process and is designated as an API stan-dard. Questions concerning the interpretation of the content of this publication or comments and questions concerning the procedures under which this publi
14、cation was developed should be directed in writing to the Director of Standards, American Petroleum Institute, 1220 L Street, N.W., Washington, D.C. 20005. Requests for permission to reproduce or translate all or any part of the material published herein should also be addressed to the director.Gene
15、rally, API standards are reviewed and revised, reaffirmed, or withdrawn at least every five years. A one-time extension of up to two years may be added to this review cycle. Status of the publication can be ascertained from the API Standards Department, telephone (202) 682-8000. A catalog of API pub
16、lications and materials is published annually and updated quarterly by API, 1220 L Street, N.W., Washington, D.C. 20005.Suggested revisions are invited and should be submitted to the Standards and Publications Department, API, 1220 L Street, NW, Washington, D.C. 20005, standardsapi.org.iiiCONTENTSPa
17、ge1 OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11.2 Scope . . . . . . . . . . . . . . . .
18、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11.3 Document Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21.4 Referenced Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19、 . . . . . . . . . . .41.5 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 PROCESS CONTROL SYSTEM PLANNING AND CONCEPTUAL DESIGN BASIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20、 . . . . . . . . . . . . . . . . . . . .72.1 Business Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72.2 Process Control System Conceptual Design Basis . . . . . . . . . . . . . . . . . . . . . . . . .82.3 Input Requirements . . . . . .
21、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82.4 Conceptual Design Assessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 PROCESS CONTROL FUNCTIONAL SPECIFICATION . . . . . . . . . . . . . . . . . . . . .143.1 Scope Definit
22、ion Input. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143.2 Process Control System Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . .153.3 Process Control System Physical Requirements. . . . . . . . . . . . . . . . . . . . . . . . .
23、.153.4 Technology Selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153.5 Execution Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163.6 Ownership and Operation Plan . . . . . . . . . . .
24、 . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 GENERAL FUNCTIONS OF PROCESS CONTROL SYSTEMS . . . . . . . . . . . . . . .174.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174.2 Sensing and Actuation . . . . . .
25、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174.3 Signal Transmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174.4 Basic Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26、 . . . . . . . .184.5 Advanced Control Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204.6 Safety, Protective and Process Interlock Systems. . . . . . . . . . . . . . . . . . . . . . . . .214.7 Control Systems Digital Communication Functions . . . . . . .
27、. . . . . . . . . . . . . . .224.8 Human Machine Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224.9 Alarming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234.10 History . . . . . . . .
28、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254.11 Reporting and Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264.12 System Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . .
29、 . . . . . . . . . . . . . . . .274.13 Data Base Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274.14 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Figures1 Refinery Con
30、trol and Automation Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Process Control Systems Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Process Control System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31、. . . . . . . 28Tables1 Process Control Systems Lifecycle Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Continuous Control Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Auxilary Control Functions . . . . . . . . . . . . . . . .
32、 . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Logic Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Human Machine Interface (HMI) Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24v1Process Control S
33、ystemsPart 1Process Control Systems Functions and Functional Specification Development1 Overview1.1 INTRODUCTIONAdvances in computing and digital communications technologies since the preparation of the 1st edition of API RP 554 have had major impacts on the way instrumentation and control systems f
34、unction as compared to historical designs. The advances have also radically changed the way that the design and specification of such systems must be approached and have created major issues relative to system design and system security. These issues are: The virtual disappearance of conventional ce
35、ntral control room control panels. Advances in computing power, software standards and communications standards have resulted in many of the functions historically implemented in stand alone process control and historization computers being integrated within the Process Control Systems. This has gre
36、atly expanded the scope of Process Control System design and blurred the division between real time control and historization functions and higher-level information systems that provide input to business and main-tenance systems. Advances in field instrumentation design leading to the general use of
37、 “smart” digital field instrumentation. Further advances in fieldbus and related technologies allow these “smart” instruments to communicate directly with the Process Control Systems or with each other. These instruments not only transfer information about the basic process measurement, but also com
38、municate diagnostic information about the health of the device or other secondary information derived from the primary measurements. Further developments in standardization of operating systems and software practices have enabled use of standard com-puter components and peripherals operating on stan
39、dard operating systems. This has resulted in a developing trend away from control systems applications being implemented on proprietary hardware and software systems, but rather being implemented on standard personal computer, workstation and network communication products running widely available o
40、perating systems. This standardization has reduced the cost and increased the flexibility of the systems. It has also resulted in greater exposure of the Process Control System to external interference and requires additional support to keep the operating systems current and secure. Security and vir
41、us-protection are major concerns of newer Process Control Systems and must be addressed at both the design and operational phases. The result of all these technical advances is that Process Control Systems are no longer entirely based upon proprietary closed hardware and software systems offered by
42、a single vendor. While these implementations are still available and form the prepon-derance of the existing installed base, there is a very strong trend away from closed systems provided by one vendor, to more open systems based upon industry standard hardware and software which have both proprieta
43、ry and open system components.These trends result in a far greater flexibility in selection of the control functions and the control hardware. These trends place greater responsibility upon the design engineer and user to understand the interaction between Process Control Systems and the business fu
44、nctions of an organization; select and specify the functions that are necessary for a given application; and implement those functions in a safe, reliable, cost effective and maintainable manner. Therefore, this edition of API RP 554 has been reorganized and split into three documents in order to be
45、tter define the processes required to properly scope, specify, select, install, commission, operate, and maintain Process Control Systems. This Recom-mended Practice is not intended to be used as a purchase specification, but recommendations are made for minimum requirements that can be used as a sp
46、ecification basis. 1.2 SCOPEThis Recommended Practice addresses the processes required to successfully implement Process Control Systems for refinery and petrochemical services. The major topics addressed are:2 API RECOMMENDED PRACTICE 554 The basic functions that a Process Control System may need t
47、o perform, and recommended methodologies for determining the functional and integration requirements for a particular application. Practices to select and design the installation for hardware and software required to meet the functional and integration requirements. Project organization, skills and
48、management required to execute a process control project and then to own and operate a Process Control System.Figure 1 shows the general overall scope of refinery control and automation functions and the portions of which this recom-mended practice addresses. The second edition of API RP 554 has bee
49、n prepared by a collaborative effort of the API Subcommittee on Instrumentation and Control Systems and the PIP (Process Industries Practices) Process Control Function Team. As such, the general scope of the material contained has been expanded to cover general industrial process control topics that are applicable to both refineries and petrochemical facilities. (PIP is a consortium of owner and engineering/construction contractor companies whose purpose is to produce a set of harmonized engineering standards in a variety of discipline areas, including process control.) Alt
