_RP_1111-2015_2021.pdf

Design,Construction,Operation,and Maintenance of Offshore Hydrocarbon Pipelines(Limit State Design)API RECOMMENDED PRACTICE 1111FIFTH EDITION,SEPTEMBER 2015REAFFIRMED,JANUARY 2021Special 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 anywarranty 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 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 theaccuracy and reliability of the data contained in them;however,the Institute makes no representation,warranty,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 facilitate 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 utilized.The formulation and publication of API publicationsis 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 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 applicable API standard.Classified areas may vary depending on the location,conditions,equipment,and substances involved in any givensituation.Users of this Recommended 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.Sound business,scientific,engineering,and safety judgment should be used in employing the information containedherein.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 Publishing Services,200 Massachusetts Avenue,NW,Suite 1100,Washington,DC,20001.Copyright 2015 American Petroleum InstituteForewordThis recommended practice(RP)sets out criteria for the design,construction,testing,operation,and maintenance ofoffshore steel pipelines utilized in the production,production support,or transportation of hydrocarbons,that is,themovement by pipeline of hydrocarbon liquids,gases,and mixtures of these hydrocarbons with water.The criteria contained in this document are intended to permit the economical transportation of hydrocarbons whileproviding for the safety of life and property and the protection of the environment.The general adoption of thesecriteria should assure that offshore hydrocarbon pipelines possess the requisite structural integrity for their safe andefficient operation.This RP includes a“limit state design”methodology.Safety margins similar to existing levels are obtained for thelower D/t ratio by changing to a limit state design based on the actual burst strength of pipe.The burst pressureformula in the document is based on theoretical considerations and confirmed by more than 250 burst tests of full-sizepipe specimens that cover a wide range of pipe grade,diameter,and wall thickness.Portions of this publication have changed from the previous editions,which have been an RP,but the changes are toonumerous to use bar notations in this edition.In some cases,the changes are significant,while in other cases thechanges reflect minor editorial adjustments.Nothing 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 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 specification.Should:As used in a standard,“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 en