API RP 1177-2017 Recommended Practice for Steel Pipeline Construction Quality Management Systems (FIRST EDITION) .pdf

1、Recommended Practice for Steel Pipeline Construction Quality Management SystemsAPI RECOMMENDED PRACTICE 1177FIRST EDITION, NOVEMBER 2017Special NotesAPI publications necessarily address problems of a general nature. With respect to particular circumstances, local,state, and federal laws and regulati

2、ons should be reviewed.Neither API nor any of APIs employees, subcontractors, consultants, committees, or other assignees make anywarranty or representation, either express or implied, with respect to the accuracy, completeness, or usefulness of theinformation contained herein, or assume any liabili

3、ty or responsibility for any use, or the results of such use, of anyinformation or process disclosed in this publication. Neither API nor any of APIs employees, subcontractors,consultants, or other assignees, represent that use of this publication would not infringe upon privately owned rights.Class

4、ified areas may vary depending on the location, conditions, equipment, and substances involved in any givensituation. Users of this specification should consult with the appropriate authorities having jurisdiction.Users of this specification should not rely exclusively on the information contained i

5、n this specification. Soundbusiness, scientific, engineering, and safety judgment should be used in employing the information contained herein.API is not undertaking to meet the duties of employers, service providers, or suppliers to warn and properly train andequip their employees, and others expos

6、ed, concerning health and safety risks and precautions, nor undertaking theirobligations to comply with authorities having jurisdiction.Information concerning safety and health risks and proper precautions with respect to particular materials andconditions should be obtained from the employer, the s

7、ervice provider or supplier of that material, or the materialsafety datasheet.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, war

8、ranty, orguarantee in connection with this publication and 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 facilit

9、ate the broad availability of proven, sound engineering and operatingpractices. These publications are not intended to obviate the need for applying sound engineering judgmentregarding when and where these publications should be used. The formulation and publication of API publications isnot intende

10、d in any way to inhibit anyone from using any other practices.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 p

11、ublisher. Contact the Publisher, API Publishing Services, 1220 L Street, NW, Washington, DC 20005.Copyright 2017 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

12、 method, apparatus, or product covered 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 specificat

13、ion.Should: As used in a standard, “should” denotes a recommendation or that which is advised but not required in orderto conform to the specification.May: As used in a standard, “may” denotes a course of action permissible within the limits of a standard.Can: As used in a standard, “can” denotes a

14、statement of possibility or capability.This specification was produced under API standardization procedures that ensure appropriate notification andparticipation in the developmental process and is designated as an API standard. Questions concerning theinterpretation of the content of this publicati

15、on 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, NW, Washington, DC 20005. Requests for permission to reproduce or translate all or any partof the m

16、aterial published herein should 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 to this review cycle. Status of the publication can be ascertained from theAPI Stand

17、ards Department, telephone (202) 682-8000. A catalog of API publications and materials is publishedannually by API, 1220 L Street, NW, Washington, DC 20005.This standard shall become effective on the date printed on the cover but may be used voluntarily from the date ofdistribution.Suggested revisio

18、ns are invited and should be submitted to the Standards Department, API, 1220 L Street, NW,Washington, DC 20005, standardsapi.org.iiiContentsPage1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19、 . . . . . . . . 12 Normative References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Definitions and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20、. . . . . . . . . . . . . . . . . 13.1 Terms and Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Quality Management System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.2 Management Responsibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74.3 Organization Capability . . . . . . . . . . . . . .

23、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.4 Documentation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.5 Control of Records . . . . . . .

24、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.6 Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.7 Risk Ass

25、essment and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Pipeline Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

26、.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2 Legal and Organizational Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27、. . . . . . . . . 125.3 Verification of Engineering and Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.4 Contract Development and Review. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

28、. . . . . . . . . . 135.5 Procurement of Materials and Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145.6 Pipeline Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

29、 . . . . . . . . . . . . . . . 155.7 Inspection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.8 Control of Nonconformances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

30、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 QMS Measurement, Analysis, and Improvement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466.2 Monitoring, Measuring, and Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466.3 Analysis of Data. . . . . . . . . . . . . . . . . . . . . . . . . . . .

32、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.4 Improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.5 Audits . . . . . . . . . . . . . .

33、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486.6 Management Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48An

34、nex A (informative) Construction Quality Management Systems50Annex B (informative) Personnel Training, Qualification, and Competence54Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35、 . . . 56FiguresA.1 QMS Framework Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52A.2 Quality Management Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

36、 . . . . . . . . . . . 53A.3 QMS and Project Reviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53BackgroundThis document is a framework for a quality management system (QMS) for onshore pipeline construction. While

37、 thisdocument may be used for facility and station construction, that is not the focus of the document. The QMSdeveloped for onshore pipeline projects shall include and document the following, which are discussed in more detailthroughout this recommended practice: defined project quality objectives

38、and personnel accountability; processes to establish and maintain the appropriate project organizational structure; processes to establish and maintain the appropriate training and qualification of internal and contractedpersonnel; processes to facilitate and verify quality throughout project design

39、, contracting, procurement, manufacturing,fabrication, and construction; processes to prevent, detect, mitigate, and eliminate potential and actual nonconformance with projectprocedures, specifications, and referenced standards ,or noncompliance with regulations, as well as verificationand documenta

40、tion of actions taken and the outcome; assessment of the achievement of quality objectives throughout the construction project; and methods to measure each processs effectiveness and enact continuous improvement of the QMS.This framework can be used to develop a stand-alone QMS or to integrate quali

41、ty management into an organizationsexisting corporate management system. In this document, “organization” is defined as the entity using this documentto develop its own QMS for pipeline construction.The organization may be the owner company, operating company, engineering and/or construction contrac

42、tor,supplier, or other stakeholder in pipeline construction that has its own QMS. Typically, the owner/operating companywill utilize contractors and suppliers on a pipeline construction project, which have their own QMS in alignment withthis document. When the QMS is developed, the term “organizatio

43、n” should be replaced with the responsible entities,such as operating company, owner-company, contractor, or supplier. Elements of this RP can be met in aggregate bythe organizations constructing the pipeline.Additionally, some processes covered in this framework may already be implemented by an org

44、anization; forexample, change management. Existing processes may be modified to address the quality concerns identified in thisframework.To be applicable to the wide range of organizations within the pipeline industry, the RP was developed to be flexibleand scalable. The RP was developed for use by

45、organizations of varying size and scope. While the QMS elementswill apply to each organization, the application of these elements are to be appropriate for the size of the organization,the scope of the project, and the risk to the public and environment.Each pipeline construction project is unique.

46、While typical pipeline construction activities are included in thisdocument, they may not be all-inclusive. Other construction activities may be relevant and should be addressed on aproject-by-project basis, utilizing the principles of this RP. Likewise, it is recognized that the identified construc

47、tionactivities may not be applicable to every pipeline construction project. It is the organizations responsibility to considerunique quality issues applicable to their projects and address them accordingly through their organization-specificQMS.Much of the input to this document is based on informa

48、tion provided in the PHMSA/DNV GL OAPUS314MJRU(PP087506), Rev. 3, report, Improving Quality Management Systems (QMS) for Pipeline Construction Activities,dated September 2, 2015.The management system principles are applied in a recurring manner to achieve continuous improvement. The PlanDoCheckAct (

49、PDCA) cycle is a four-step model for carrying out these efforts (Figure 1).This cycle can be applied to the management system as a whole, to individual construction projects, and to individualelements and processes within the system. Continuous improvement is at the core of many management systems,and its principal aim is to encourage creating strategies and plans, executing those strategies and plans in line withguidelines, evaluating those actions for conformity, and using those results to adjust the next generation of plans. Thiscycle is iterative.The components of the PDC