API TR 1166-2015 Excavation Monitoring and Observation for Damage Prevention (SECOND EDITION).pdf

《API TR 1166-2015 Excavation Monitoring and Observation for Damage Prevention (SECOND EDITION).pdf》由会员分享，可在线阅读，更多相关《API TR 1166-2015 Excavation Monitoring and Observation for Damage Prevention (SECOND EDITION).pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、Excavation Monitoring and Observation for Damage PreventionTECHNICAL REPORT 1166 SECOND EDITION, OCTOBER 2015Special NotesAPI publications necessarily address problems of a general nature. With respect to particular circumstances, local, state, and federal laws and regulations should be reviewed.Nei

2、ther API nor any of APIs employees, subcontractors, consultants, committees, 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

3、 any use, or the results of such use, of any information 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.Classified areas may vary de

4、pending on the location, conditions, equipment, and substances involved in any given situation. Users of this Technical Report should consult with the appropriate authorities having jurisdiction.API publications may be used by anyone desiring to do so. Every effort has been made by the Institute to

5、assure the accuracy and reliability 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

6、of any authorities having jurisdiction 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 re

7、garding when and where these publications 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 standar

8、d is 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.All rights reserved. No part of this work may be reproduced, translated, stored in a retriev

9、al 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, 1220 L Street, NW, Washington, DC 20005.Copyright 2015 American Petroleum InstituteForewordNothi

10、ng contained in any API publication is 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 li

11、ability 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 order to conform to the specification.

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

13、 . . . . . . . . . . . . . . . . . 12 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Decision Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1 Decision Node 1Is Additional Information Required?. . .

15、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.2 Decision Node 2Office Analysis and Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34.3 Decision Node 3Site Visit Resolution . . . . . . . . . . . . . . . . . . . .

16、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34.4 Decision Nodes 4 and 5Excavation Proximity to Pipeline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34.5 Decision Node 6Ticket Closure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17、 . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.1 Task AClose Ticket . . . . . . . . . . . . . . . . . . . . . . .

18、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.2 Task BSecure Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.3 Task CConduct Site Visit . . . . . . . . . . . . . . .

19、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.4 Task DPerform Locate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.5 Task EExcavation Monitoring. . . . .

20、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.6 Task FExcavation Observation Not Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.7 Task GExcavation Observation . . . . . . .

21、 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Figure 1 FlowchartExcavation Monitoring and Observation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Bibliography . . . . . . . . . . . . . . . . . . . . . . .

22、. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8v1Excavation Monitoring and Observation for Damage Prevention1 ScopeThe scope of this technical report is to provide a consistently applied decision making process for monitoring and

23、observing of excavation and other activities on or near pipeline rights-of-way for “hazardous liquid” and “natural and other gas” transmission pipelines. The goal is to protect the public, excavation employees, and the environment by preventing damage to pipeline assets from excavation activities.NO

24、TE Pipeline operators are encouraged to refer to the latest edition of Common Ground Alliances “CGA Best Practices” for additional guidance.2 DefinitionsFor the purposes of this document, the following definitions apply.2.1activity Identified excavation activity.2.2excavation Disturbance or removal

25、of dirt or subsurface debris from a specified area.NOTE 1 Excavation can include the use of non-mechanized or mechanized equipment, or explosives.NOTE 2 Specific definitions and requirements for excavation may be established by regulation and the user is encouraged to check with the applicable autho

26、rities (e.g. municipal, county, state, etc) as to any relevant details.2.3excavation monitoring Oversight at regular intervals of the process to plan, request, design, approve, and excavate on or around pipelines to ensure the safe, effective completion with the desired results.NOTE Excavation monit

27、oring is commonly referred to or associated with Excavation Planning.2.4excavation observationActive participation in the onsite excavation before, during and after activities cease to ensure proper completion of the agreed work in a safe, effective manner.2.5locateTo indicate the existence of a bur

28、ied or otherwise obscured line or facility by establishing a mark through the use of stakes, paint, or some other customary manner that approximately determines the location of the line or facility.2.6one-call centerEntity in each state or territory that administers a system for their area of respon

29、sibility that can notify owners/operators of lines or facilities of proposed excavations. NOTE 1 One-call provisions and laws vary by state and it is the operators responsibility to be familiar with and comply with all applicable one-call laws. 2 API TECHNICAL REPORT 1166NOTE 2 There may be multiple

30、 entities providing service to a given area of responsibility.2.7operatorpipeline operatorPerson who owns or operates pipeline facilities.NOTE 1 For the purpose of this document, the terms “pipeline operator” and “operator” are synonymous.NOTE 2 “Person” means any individual, firm, joint venture, en

31、tity, partnership, cooperation, association, state, municipality, cooperative association, or joint stock association, and includes any trustee, receiver, assignee, or person representative thereof.2.8originatorIndividual or company who has identified and made notification of an excavation activity

32、and/or initiated a one-call ticket.2.9positive responseProcedural system that ensures communication of locating and marking status of the excavation between the originator and the operator, regardless of whether or not the locate activities have been completed.2.10requestone-call requestOne-call tic

33、ket issued from a one-call center.2.11ticketDocumentation of the one-call request or the identified excavation activity, including assigned number identification for tracking the ticket and all associated documentation.3 Flow DiagramThe following sections make reference to Decision Nodes and Tasks i

34、dentified in Figure 1.4 Decision Nodes4.1 Decision Node 1Is Additional Information Required?The first step is to determine if additional information from the Originator is necessary, beginning with a review of the One-Call ticket. Contact with the originator is not required if the exact work locatio

35、n is known with certainty and the proposed work or activity falls outside designated company determined buffer zones. However, if any uncertainty exists, designated personnel must contact the originator, clearly confirm the activity location, and document the results of the conversation that all wor

36、k is outside of company buffer zones before closing the ticket.Contact the originator for more information when the above is not met.The operator performs due diligence to confirm several critical pieces of information before analyzing an excavation request: Is the locate request spatially correct (

37、i.e. will the excavator dig at the required location? Is the full or probable extent of the originators intended or possible excavation area included in the request?EXCAVATION MONITORING AND OBSERVATION FOR DAMAGE PREVENTION 3 Are the Operators buried assets properly identified and spatially accurat

38、e? Is the information submitted to the One-Call agencies correct and current?Originators should contact the operator under certain circumstances that include, but are not limited to: questions, incomplete locates where less than the requested area was addressed, no locating activity evidence is pres

39、ent such as flags, or any other uncertainty exists.Examples of situations requiring the operator to contact the originator include, but are not limited to: work location falls inside company defined buffer zone, ticket is classified as an emergency, address cannot be located on map or appears to be

40、incorrect (e.g. street number and name do not correspond), ticket indicates location map or additional information is available upon request, ticket contains conflicting or unclear information on work location or work scope, positive response required by regulations.Examples of specific verifiable w

41、ork locations include, but are not limited to: SW corner of intersection of Main and Beacon Streets, front property line of 704 Byrne, going East for 500 ft, accurate reporting of the proposed excavation location through provision of GPS coordinates.Examples of general work locations requiring origi

42、nator contact includes, but is not limited to: approximately five miles east of city on Highway 77, then 1 mile south on lease road, 704 Byrne (rural location and property size unknown).4.2 Decision Node 2Office Analysis and ResolutionSite visit is not required if contact with originator has determi

43、ned that, without question, work or activity falls outside company designated buffer zones. If any question exists, designated field personnel must conduct a site visit.4.3 Decision Node 3Site Visit ResolutionLocate is not required if site visit has determined that, without question, work or activit

44、y falls outside company designated buffer zones. If any question exists, designated field personnel must perform the locate.4.4 Decision Nodes 4 and 5Excavation Proximity to PipelineConsideration should be given, but not limited to, the following when evaluating the proximity of work (or work impact

45、) to the pipeline:4 API TECHNICAL REPORT 1166 Does the excavator have a proven record of following pipeline company procedures and requirements? Has the excavation area been marked (well defined excavation area, i.e. “white lined”)? Has the pipeline operator or appointed representative confirmed the

46、 type of mechanized equipment to be used, including the following considerations: weight limit issues (See API 1102, Steel Pipelines Crossing Railroads and Highways); reach/extension capabilities. Are there equipment components (excavator treads or tracks) that have the potential to impact a minimum

47、 safety radius (i.e. 5 ft, or 25 ft), even though the excavation itself does not? Are effective isolation measures in place to protect pipeline from mechanized equipment (example would be a residential security fence)? Have pipeline bends been accounted for in marking the area?Does the work plan ind

48、icate need for special considerations such as (includes, but is not limited to): blasting*, seismic testing*, mining*, quarry operations*, dredging*, heavy surface loading*, multiple pipeline corridors*, abandoned pipe segments*, boring/directional drilling*, pile drilling*. extremely wet soil, or o

49、ther applicable environmental factors*.NOTE The above items marked with an “*” may require special individual operator designated procedures.4.5 Decision Node 6Ticket ClosurePipeline representative should only close ticket when a review has been completed with excavator and confirmed all work activities in the area of excavation have been completed.5 Tasks5.1 Task AClose TicketRender the ticket completed using company protocols.EXCAVATION MONITORING AND OBSERVATION FOR DAMAGE PREVENTION 55.2 Task BSecure Additional I