1、Recommended Practice for Subsea Production System Reliability and Technical Risk ManagementAPI RECOMMENDED PRACTICE 17NFIRST EDITION, MARCH 2009Recommended Practice for Subsea Production System Reliability and Technical Risk ManagementUpstream SegmentAPI RECOMMENDED PRACTICE 17NFIRST EDITION, MARCH
2、2009Special 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 anywa
3、rranty or representation, either express or implied, with respect to the accuracy, completeness, or usefulness of theinformation contained herein, or assume any liability or responsibility for any use, or the results of such use, of anyinformation or process disclosed in this publication. Neither AP
4、I nor any of APIs employees, subcontractors,consultants, or other assignees represent that use of this publication would not infringe upon privately owned rights.Classified areas may vary depending on the location, conditions, equipment, and substances involved in any givensituation. Users of this r
5、ecommended practice should consult with the appropriate authorities having jurisdiction.Users of this recommended practice should not rely exclusively on the information contained in this document. Soundbusiness, scientific, engineering, and safety judgment should be used in employing the informatio
6、n contained herein. API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to assure theaccuracy and reliability of the data contained in them; however, the Institute makes no representation, warranty, orguarantee in connection with this publication and
7、 hereby expressly disclaims any liability or responsibility for loss ordamage resulting from its use or for the violation of any authorities having jurisdiction with which this publication mayconflict.API publications are published to facilitate the broad availability of proven, sound engineering an
8、d operatingpractices. These publications are not intended to obviate the need for applying sound engineering judgmentregarding when and where these publications should be utilized. The formulation and publication of API publicationsis not intended in any way to inhibit anyone from using any other pr
9、actices.Any manufacturer marking equipment or materials in conformance with the marking requirements of an API standardis solely responsible for complying with all the applicable requirements of that standard. API does not represent,warrant, or guarantee that such products do in fact conform to the
10、applicable API standard.All rights reserved. No part of this work may be reproduced, translated, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from the publisher. Contact the Publisher, API P
11、ublishing Services, 1220 L Street, N.W., Washington, D.C. 20005.Copyright 2009 American Petroleum InstituteForewordNothing contained in any API publication is to be construed as granting any right, by implication or otherwise, for themanufacture, sale, or use of any method, apparatus, or product cov
12、ered by letters patent. Neither should anythingcontained in the publication be construed as insuring anyone against liability for infringement of letters patent.Shall: As used in a standard, “shall” denotes a minimum requirement in order to conform to the specification.Should: As used in a standard,
13、 “should” denotes a recommendation or that which is advised but not required in orderto conform to the specification. This document was produced under API standardization procedures that ensure appropriate notification andparticipation in the developmental process and is designated as an API standar
14、d. Questions concerning theinterpretation of the content of this publication or comments and questions concerning the procedures under whichthis publication was developed should be directed in writing to the Director of Standards, American PetroleumInstitute, 1220 L Street, N.W., Washington, D.C. 20
15、005. Requests for permission to reproduce or translate all or anypart of the material published herein should also be addressed to the director.Generally, API standards are reviewed and revised, reaffirmed, or withdrawn at least every five years. A one-timeextension of up to two years may be added t
16、o this review cycle. Status of the publication can be ascertained from theAPI Standards Department, telephone (202) 682-8000. A catalog of API publications and materials is publishedannually by API, 1220 L Street, N.W., Washington, D.C. 20005.Suggested revisions are invited and should be submitted t
17、o the Standards Department, API, 1220 L Street, NW,Washington, D.C. 20005, standardsapi.org.iiiContentsPage1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Project Types .
18、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Equipment Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19、. . . . . . . . 21.3 Project Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4 Qualification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Other Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1 API Specification Q1 (ISO/TS 29001). . . . . . . . . . . . . . . . . . . . . .
21、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2 DNV RP A203 and API Recommended Practice 17Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.3 ISO 20815 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Terms and Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Abbreviations. . . . . . . . . . . . . . . . . . . . . .
23、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Overview of Reliability and Technical Risk Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.1 Underlying Structure. . . . . . . . . . . . . . .
24、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.2 Define . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.3 Plan . .
25、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.4 Implementing the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26、. . . . . . . . . . . . 105.5 Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.6 Supporting Reliability Key Processes (KPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27、. . . . . . . . . . . . . . . . . . . . . 125.7 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Recommended Practice for Each Project Stage . . . . . . . . . . . . . . . . . . . .
28、. . . . . . . . . . . . . . . . . . . . . . . . . . 136.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136.2 Technical Risk and Reliability Effort . . . . . . . . . . . . . . .
29、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136.3 Feasibility Stage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156.4 Concept Selection . . . . . . . . . . . . .
30、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.5 Front End Engineering Design (FEED) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.6 Detail Design and Manufacture
31、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.7 System Integration Test (SIT), Install, Commission and Operate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Annex A (informative) Technical Risk Categor
32、ization Approach to Reliability and Technical Risk Management. 26Annex B (informative) Detailed Reliability Process and Activity Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Annex C (informative) Reliability Data Management . . . . . . . . . . . . . . . . . . . . . . . . . .
33、. . . . . . . . . . . . . . . . . . . . . . 89Annex D (informative) Application of Test Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Figures1 Define, Plan, Implement and Feedback Loop. . . . . . . . . . . . . . . . . . . . . . . . . . .
34、. . . . . . . . . . . . . . . . . . . . . . . 82 Project Life Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Key Process (KP) Interaction with Define, Plan, Implement, and Feedback Loop . . . .
35、. . . . . . . . . . . . . . 154 Guide to Process Effort by Project Phase and Risk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16B.1 Procedure for Defining Availability Goals and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36、 . 42B.2 Functional Test Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74B.3 Outline Qualification Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37、 . . . . . . . . . . . . 77B.4 Example Output from Reliability Capability Maturity Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82C.1 Data Collection and Usage Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38、 . . . . 91vPageTablesA.1 Technical Risk Categorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27B.1 Availability Performance Metrics Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39、. . . . . . . . . . . . . 42B.2 Value Metrics Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44B.3 Primary Drivers and Influences for Planning for Availability. . . . . . . . . . . . . . . . . . . . . . . .
40、 . . . . . . . . . . . . 47B.4 Guidance on the Level of Effort Required for Reliability Effort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48B.5 Types of Reliability Assurance Evidence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41、 . . . . . . 54B.6 Suggested Constituent Parts of a Reliability Assurance Document (RAD) . . . . . . . . . . . . . . . . . . . . . . . . 55B.7 Relationship of Analysis Type to Project Stage and Technical Risk Categorization. . . . . . . . . . . . . . . . . 57B.8 Failure Modes, Effects and Criticalit
42、y Analysis (FMECA) Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58B.9 Fault Tree Analysis (FTA) Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59B.10 Reliability Block Diagram (RBD) Summary . . . . . . .
43、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60B.11 Event Tree Analysis (ETA) Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61B.12 Physics of Failure Summary . . . . . . . . . . . . . . .
44、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62B.13 Importance Analysis Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63B.14 Qualitative Common Cause Failure Analysis S
45、ummary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64B.15 Quantitative Common Cause Failure Analysis Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65B.16 Reliability Availability Maintainability (RAM) Analysis Summary . . . . .
46、 . . . . . . . . . . . . . . . . . . . . . . . . . . . 66B.17 Root Cause Analysis (RCA) Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67B.18 Recommended Verification and Validation of the Key Processes (KPs) . . . . . . . . . . .
47、. . . . . . . . . . . . . . . 68B.19 Definition of Technology Readiness Levels (TRLs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75B.20 Standard Reference for Goodness of Fit Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48、 . . . . . . . . . 76B.21 Standard Reference for Reliability Parameter Estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78B.22 Standard Reference for Compliance Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49、 . . . 78B.23 Standard Reference for Comparison Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78B.24 Overview of Reliability Capability Maturity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81B.25 Some Instruments for Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86D.1 Example of Sorted Failure Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
