2015 Pipeline Safety Trust Conference

1. 2015 Pipeline Safety Trust Conference API RP 1175 Pipeline Leak Detection Program Management – New RP Highlights November 20th, 2015 | New Orleans, LA

2. Agenda • API Process • Current Status • Intent of API RP 1175 • Proposed RP 1175 Table of Contents • Overview of Sections • Questions/Comments

4. Document Types • Bulletin/Technical Report – Documents that convey technical information on a specific subject or topic and are generally issued on a one-time basis. • Code – A document intended for adoption by regulatory agencies or authorities having jurisdiction. • Recommended Practice (RP) – A document that communicates proven industry practices. • Specification – A document that prescribes technical requirements to be fulfilled by a product, process, or service. • Standard – A document that provides for common and repeated use, rules, guidelines or characteristics for activities or their results aimed at the achievement of the optimum degree of order in a given context. Standards typically include elements of both specifications and recommended practices.

5. Current Status • Document has been balloted • All comments being resolved • Targeting 1Q2016 publication

6. Intent of API RP 1175 • Provide holistic, high-level overview of LIQUIDs Leak Detection Program (LDP) management • Guidance on development, implementation, and management of a program • Enhanced guidance and establishment of performance measures • Address identified gaps and develop a comprehensive LDP document • Focuses on using a risk-based approach • Suggest all forms of leak detection managed in a coordinated manner. • Promote advancement of robust LDPs • Represent industry best practices

7. Key Definitions • Leak Detection Program (LDP) • Top level term that encompasses all the various leak detection systems (LDSs) (which may include multiple techniques) employed by the pipeline operator and identifies all methods used to detect leaks and the policies, processes, and the human element. • Leak Detection System (LDS) • End-to-end application of one technique that may be internally-based or externally-based and continuous or non-continuous

8. RP 1175 Sections • Scope • Normative References • Definitions • Leak Detection Culture and Strategy • Selection of Leak Detection Methods • Performance Targets, Metric, and KPIs • Testing • Control Center Procedures for Recognition and Response • Alarm Management • Roles, Responsibilities, and Training • Reliability Centered Maintenance for Leak Detection Equipment • Overall Performance Evaluation of the LDP • Management of Change • Improvement Planning and Process

9. Leak Detection Culture and Strategy • Culture • Influences how personnel behave and act • Shared • Affects and is affected by the behavior and interactions of people • Includes an organization's beliefs • Evolving • Ongoing management direction and support • Doing every task, the right way, every time

10. Thinking to Knowing • Strong Leak Detection Culture Indicators: • Support from management • Exceeding minimum regulatory requirements • Ongoing improvement • Coordination of all leak detection methods • Coordination and teamwork between different entities involved • Clear policies, procedures, and processes • Comprehensive management of change • Ongoing training • A focus on the safe and reliable operations of the pipeline with no negative repercussions on the staff who take actions in response to leak indications

11. Leak Detection Culture and Strategy • Strategy • Outlines the technical aspects • Sets the goals • Details how will be met

12. Elements of strategy • Management commitment and leadership • Pipeline operator’s requirements and goals • How requirements and goals should be satisfied • Employing risk management • Selection of leak detection systems (LDSs) • Integration of all LDSs employed • Regulatory requirements and industry standards • Ongoing measurement of performance • Reporting • Training, testing, and operations / procedures • Review and approvals • Management of change • Ongoing improvement to the LDP

13. Selection of Leak Detection Methods • Choose appropriate principles, methods, and techniques • Selection of new applications, additional applications, or re- examine existing applications • Multi-step, multi-faceted, and iterative • Documentation is essential

14. The Process of Selection • Culture and strategy alignment • Performance Targets, Metrics, and KPIs • Regulatory Requirements, Best Practices, and Company Requirements • Overall Risk Assessments • Best Available Technology(ies) • “Fit-for-purpose” • Leak Detection Capability Evaluation (LDCE)

15. Performance Metrics, KPIs, and Targets Metrics Key Performance Indicators (KPIs) Performance targets

16. Proposed Metrics • Four leak detection metrics • Reliability – can you depend on the alarms? • Sensitivity – how small a leak can you detect? • Accuracy – how good are the size/location estimates? • Robustness – will it work in a less than perfect environment? • KPIs add specificity

17. Control Center Procedures for Recognition & Response • Documented leak response procedure • Complementary • Additional guidance • Pipeline Controllers • Front lines • Level of authority and responsibility • Think Teamwork!

18. A little more • Reinforce all potential leak alarms • Have a cause • Evaluate • Immediate attention • Leak response procedures • Processes, tools, and actions • Consequence-based mindset with directives for taking action • Simple to understand and implement • Be reinforced • SHUTDOWN is always an option

19. Reporting and Documentation • Log actions • Use a standard form • Utilize in incident investigation

20. Pipeline Restart • Restart procedure be included in Control Center procedures • Involve • Appropriate authorization • When to restart • High-level of awareness • Extra attention by both field personnel and the Control Center staff

21. Overall Performance Evaluation of the LDP • Capture noteworthy results of the performance of the LDP • Benchmark • Involve management • Use KPIs

22. Improvement Planning and Process 1. Identifying and Defining • Identify and capture issues • Look for sources of improvement • Review history 2. Initiating and Monitoring • Review all opportunities, set targets, recommend actions • Plan, budget, schedule, track • Consider the timeframe • Use checklists • Update and improve

23. Thank you! Stuart Saulters Policy Advisor, API 202-682-8493 saulterss@api.org