1、Process Control Systems Project Execution and Process Control System OwnershipAPI RECOMMENDED PRACTICE 554, PART 3 FIRST EDITION, OCTOBER 2008Process Control Systems Project Execution and Process Control System OwnershipDownstream SegmentAPI RECOMMENDED PRACTICE 554, PART 3 FIRST EDITION, OCTOBER 20
2、08Special 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, or other assignees make any wa
3、rranty 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 in this publication. Neither
4、API nor any of APIs employees, subcontractors, consultants, or other assignees represent that use of this publication would not infringe upon privately owned rights.API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure the accuracy and reliab
5、ility of the data contained in them; 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 juri
6、sdiction with which this publication may conflict.API publications are published to facilitate the broad availability of proven, sound engineering and operating practices. These publications are not intended to obviate the need for applying sound engineering judgment regarding when and where these p
7、ublications should be utilized. 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 co
8、mplying with all the applicable requirements of that standard. API does not represent, warrant, or guarantee that such products 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, el
9、ectronic, mechanical, photocopying, 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 2008 American Petroleum InstituteForewordNothing contained in any API publication is
10、 to be construed as granting any right, by implication 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 pa
11、tent.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
12、standardization procedures that ensure appropriate notification and participation in the developmental process and is designated as an API standard. Questions concerning the interpretation of the content of this publication or comments and questions concerning the procedures under which this publica
13、tion 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.Genera
14、lly, 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 publi
15、cations and materials is published annually by API, 1220 L Street, N.W., Washington, D.C. 20005.Suggested revisions are invited and should be submitted to the Standards Department, API, 1220 L Street, NW, Washington, D.C. 20005, standardsapi.org.iiiContentsPage1 Scope . . . . . . . . . . . . . . . .
16、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Ref
17、erenced Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18、. . . . . . . . . . . . 54 Scope and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Project Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19、 . . . . . . . . . . . . . . . . . . . . . . . . 115.1 Define/Execute Project Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Project Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166.2 Resources and Staffing . . . . . . . . . . . . . . .
21、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166.3 Standards and Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.4 Design Data Management. . . .
22、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186.5 Procurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.6 Phy
23、sical Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.7 Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24、. . . . . . . . . . . . . . 206.8 Training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.9 Testing, Validation and Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . .
25、. . . . . . . . . . . . . . . . . . . . . . . . . . 216.10 Project Close Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Testing, Validation and Commissioning . . . . . . . . . . . . . . . . . . . .
26、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227.2 Main Process Control System . . . . . . . . . . . . . .
27、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237.3 Field Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277.4 Tie-ins and Hot Cut Overs . . .
28、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297.5 Other Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297.6 Com
29、missioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307.7 Acceptance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30、 . . . . . . . . . . . . . 318 Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318.1 Management of Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31、. . . . . . . . . . . . . . . . . . . . . 318.2 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328.3 Maintenance Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348.4 Engineering and Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378.5 Testing Schedules . . . . . . . . . . . . . . . . . . . . . . . . .
33、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388.6 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388.7 Inspection, Calibration, Test and
34、Repair Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.8 Maintenance, Operation and Repair Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.9 Spare Parts . . . . . . . . . . . . . . . . .
35、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figures1 Refinery Control and Automation Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Tables1 Process Control S
36、ystems Life Cycle Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3vIntroductionAdvances in computing and digital communications technologies since the preparation of the first edition of API 554 have had major impacts on the way instrumentati
37、on and control systems function 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 as follows. The virtu
38、al disappearance of conventional central 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 pr
39、ocess control systems. This has greatly 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 maintenance systems. Advances in field instrumentation de
40、sign leading to the general use of “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
41、 process measurement, but also communicate 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 computer components
42、and peripherals operating on standard 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 pr
43、oducts running widely available operating 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 cur
44、rent and secure. Security and virus-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
45、and software systems offered by a single vendor. While these implementations are still available and form the preponderance 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 sof
46、tware which have both proprietary 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 cont
47、rol systems and the business functions 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 554 has been reorganized and split into th
48、ree documents in order to better define the processes required to properly scope, specify, select, install, commission, operate, and maintain process control systems. This recommended practice is not intended to be used as a purchase specification, but recommendations are made for minimum requiremen
49、ts that can be used as a specification basis. vi1Process Control SystemsProject Execution and Process Control System Ownership1 ScopeThis recommended practice (RP) addresses the processes required to successfully implement process control systems for refinery and petrochemical services. The major topics addressed are as follows. The basic functions that a process control system may need to perform, and recommended methodologies for determining the functional and integration requirements for a particular application. Practices to select and design the installation for hardware
