Pipeline public awareness programs lessons learned november 4 2010
Download
1 / 11

Pipeline Public Awareness Programs: Lessons Learned November 4, 2010 - PowerPoint PPT Presentation


  • 256 Views
  • Uploaded on

Pipeline Public Awareness Programs: Lessons Learned November 4, 2010. Public Awareness Program Objectives. Raise awareness of affected public and key stakeholders of presence of pipelines Increase understanding of role of pipelines in transporting energy

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Pipeline Public Awareness Programs: Lessons Learned November 4, 2010' - baris


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Pipeline public awareness programs lessons learned november 4 2010

Pipeline Public Awareness Programs:Lessons LearnedNovember 4, 2010


Public awareness program objectives
Public Awareness Program Objectives

  • Raise awareness of affected public and key stakeholders of presence of pipelines

  • Increase understanding of role of pipelines in transporting energy

  • Help public understand accidents are possible, but pipelines still safe transportation

  • Help public understand measures pipeline operators take to prevent accidents

  • Help public understand the steps they can take to prevent and respond to pipeline emergencies


Objectives of the rp
Objectives of the RP

  • Assist pipeline operators develop framework for public awareness program

  • Assist operators with determining factors that may indicate enhancements necessary

  • Provide practices that are clear, reasonable and practical to enhance pipeline safety


Timeline
Timeline

  • 2003: API RP 1162 drafted

  • May 2005: API RP 1162 incorporated into regulation

  • June 20, 2006: Clock starts ticking on PAPs

  • June 20, 2010: End of 1st 4-year cycle; external measurement must be completed


2006 2010 challenges
2006 – 2010: Challenges

  • Supplemental (Enhanced) programs

    • Implementation

      • Internal

    • Triggers

    • Diverse industry = no cookie-cutter approach

    • Getting key stakeholders to pay attention

      • Motivation


2006 2010 challenges1
2006 – 2010: Challenges

  • Measuring change in behavior

    • Impossible to measure quantitatively

      • Clutter

    • Can be measured anecdotally and applied

    • Communication process: attention, awareness, agreement, opinions, behavior…

      • More informed and aware = more likely to act

    • Goal of API RP 1162 is increased awareness, not behavior change


2006 2010 challenges2
2006 – 2010: Challenges

  • Evaluating program effectiveness

    • Define effective

      • Reaching intended recipients?

      • Easy to understand messaging, content?

      • Behavior change?

      • Bottom-line results?

    • What can we effectively measure, and how?


Revision of api rp 1162
Revision of API RP 1162

  • Revised document completed

  • Currently in publication process

  • Editorial changes

    • Remove redundancies

    • Streamline writing

    • Improve document functionality


  • Substantive issues addressed

    • Number of messages

      • Baseline (core safety) vs. Enhanced (non-core safety)

    • Delivery methods

      • Increased flexibility for operators

    • Measurement

      • Awareness vs. change in behavior


Conclusions
Conclusions

  • Not a perfect program

    • Continued improvement

    • Adapt to changing environments

  • Shared goals

    • Safety

    • Increased awareness of pipelines in communities

  • Partnership: How can we work together?



ad