200 likes | 483 Views
A Framework for Your Pipeline Integrity Program. A Few Thoughts Before Beginning. This rule is new to the pipeline industry although many of the concepts are not Many have struggled though the rule’s development A consistent approach can help. Why an Industry Standard?.
E N D
A Few Thoughts Before Beginning • This rule is new to the pipeline industry although many of the concepts are not • Many have struggled though the rule’s development • A consistent approach can help
Why an Industry Standard? • A systematic approach -- • focuses on risk reduction as a goal • is more effective • is called for by the rule • Provides a framework • for operators in developing their programs • for inspectors in auditing integrity programs • Provides additional “meat”
API 1160, “Managing System Integrity for Hazardous Liquid Pipelines” • Developed under ANSI consensus procedures • Work group included -- • Pipeline operators • OPS regulatory and enforcement • Inspection service providers • Metallurgists, engineers, corrosion specialists, and more
API 1160 -- The Process • Drafted by Work Group • Reviewed by peers • Pipeline operators • ASME B31.4 members • Pipeline safety advocates • Environmental interest groups • Comments resolved • Aligned with Final Rule on integrity management
API 1160 -- Scope • Hazardous liquid pipelines • Not limited to pipelines regulated in Part 195 • Not limited to pipelines in high consequence areas • Not limited to line pipe • PROVEN INDUSTRY PRACTICES
API 1160 -- Contents • Intro, Scope, References, Definitions • Integrity Management Programs -- Overview • High Consequence Areas • Identification • Using HCA info • Affecting HCAs • Documenting HCA info
API 1160 -- Contents • Data Gathering, Review and Integration • Risk Assessment Implementation • Initial Baseline Plan Development and Implementation • Mitigation Options • Revision of the Plan • Pump Stations and Terminals • Program Evaluation • Managing Change
API 1160 -- Appendixes • Anomaly Types, Causes and Concerns • Repair Strategies • Standard Data Fields • For tracking release information • For tracking system information
What the standard is NOT -- • A cookbook for compliance with the rules • A simplified approach to risk or integrity management
What the standard IS -- • An aid in developing the framework for your integrity management program • Guidance on the aspects of integrity management you need to be thinking about • A means to make your program comparable to other company programs • A set of standardized measures allowing you to compare your performance with your peers, if you choose to • AND MORE
Highlights -- Identifying HCAs • It’s the first thing you have to do • You are partially dependent on OPS but there are some caveats • Population -- Straightforward • Navigable waters -- Straightforward • USAs -- Not so simple • Timing may become an issue • Some guidance in the standard
Highlights -- Data • Identifying data sources (lots of examples) • Identifying data needs (different from what you have maybe) • Establishing a common reference system -- THE key to integration
Highlights --Risk Assessment • A primer that is specific to the pipeline industry • Defines the characteristics of a sound approach • Structure • Adequacy of resources • Experience-based • Predictive • Uses appropriate data • Importance of feeback mechanisms
Highlights -- Baseline Assessment • A tutorial on ILI -- • Anomalies and defects • Internal inspection and testing technologies • Tools • Intervals • A tutorial on hydrostatic testing • Value and limitations • Intervals
Highlights -- Baseline Assessment • What should you do with what you find? • What will be your strategy for responding to anomalies identified • Repair overview • Mitigation options -- lots of them
Highlights -- Program Evaluation • Recommends specific performance measures • Defines a way to look at the value and utility of performance measures, i.e. methodology • Comparisons • Internal • External • Audits
Final Thoughts • The Standard • The standard is not typical • The standard significantly raises the expectation bar, probably more then the rule itself does • The Rule • Requires leak detection capability in the rules for the first time • Is tough
To Get Your Copy of the Current Draft -- http://www.api.org/pipelineintegrity/