2015 Annual Virginia SCC/LDC Conference Dan Cote, VP Pipeline Safety and Compliance October 7-8, 2015

Transcription

1 CGV SMS Non-Punitive Reporting 2015 Annual Virginia SCC/LDC Conference Dan Cote, VP Pipeline Safety and Compliance October 7-8, 2015

2 Agenda What is SMS? Why do we need SMS and Non-Punitive Reporting in Virginia? What is the purpose of Non-Punitive Reporting? Review of the PG&E program currently in place, and the status of CGV Non-Punitive Reporting development. 2

3 A Brief History of SMS SMS Systems & Non-Punitive Reporting: Born in the 90 s in the Nuclear, Chemical and Airline Industries. The common denominator to what are very different industries was major incidents and public outrage. Chernobyl, Three Mile Island - Nuclear Reactor Melt-Downs Bhopal India Major Chemical Release Airline Industry Multiple Airline Crashes SMS: A formal, structured, internally-driven process that is designed to identify safety risks of all kinds, then prioritize those risks against frequency and consequence to reduce the likelihood of significant incidents. The more significant components (in my opinion) of SMS include: A highly structured series of procedures and steps needed to execute an effective SMS. Top of the house support for the SMS Program from Corporate Sr. Leadership including the CEO. An effective Non-Punitive reporting system that engages, tracks and reports back to front line workers on near misses and other risk events during the routine execution of work. An integrated culture from the top to the bottom of the organization that supports SMS and demands safe operations and execution. 3

4 Why do we need SMS to do this in Virginia? After fatalities caused by major incidents in San Bruno, Allentown, Harlem, New Jersey, Kansas City, and others, the public is demanding that as an industry we must do a better job keeping them safe. (Some of these incidents clearly could have been mitigated/prevented by more effective processes/responses.) Data shows that we are finding a number of failures to follow operating procedures or manufacturers instructions when carrying out of our work, both in performing routine and emergency response activities. Further (in my opinion), this is occurring frequently enough so that additional action is clearly required to adequately address both the code compliance and the pipeline safety risks. We are seeing unprecedented rates of turnover among our employee and contractor workforce as highly experienced baby-boomers retire. This is happening at the same time that we are ramping up to dramatically increase the replacement rates of our first generation piping systems (Bare Steel, Cast Iron, pre-71 unprotected steel, Aldyl-A). As a result, we are seeing more inexperienced people doing more work than at any point in the last 50 years. This program and the associated Non-Punitive Reporting are logical extensions and continuations of our enhanced OQ qualification program. Insanity: doing the same thing over and over again and expecting different results. Albert Einstein 4

5 The Role SMS Plays in Executing Current Operator Responsibilities Current Operator Obligations and Responsibilities Under Part 192 Create clear and complete written operating procedures for front line workers to follow when performing system operating and construction tasks Monitor the performance of employees carrying out the activities to ensure compliance with the procedures Continually investigate failures, identify the root causes, take corrective actions It is operations management s responsibility to ensure that written O&M procedures are being followed. Writing the procedures is the easy part; ensuring execution in the field requires both process rigor and constant vigilance. Employee Responsibilities Follow the written procedures Identify problems or inadequacies with the procedures, and if there are questions on the procedures, ask! Report errors and do NOT bury mistakes! SMS simply creates a structured and verifiable process around these historic management and employee responsibilities. And in doing so, helps create and drive a culture of pipeline safety accountability across all levels of the organization. 5

6 The Purpose of Non-Punitive Reporting Simply stated, the Purpose of Non-Punitive Reporting is to get employees at all levels of our organization to report near misses lapses in process, or other pipeline safety performance or execution issues that they (the employees and contractors) believe to be significant. Survey data shows that approximately one third of the CGV front line workers and contractors in our workforce today would not report such issues if they saw them. (Actual experience shows that the true frequency of reporting such occurrences is much lower than that.) Would you report an issue (not following procedures, rules, regulations) or a near miss to your supervisor? If we don t know what is broken, it is very hard to fix. 6

7 A Simple SMS Non-Punitive Reporting Process A fast and easy process for all Front Line Employees and Contractor Employees to report Pipeline Safety concerns electronically, that will not result in any of the employees involved being punished for process or procedural infractions. A process to receive and quickly process the concerns expressed and communicate back to the employee (if so desired) that the issue is under investigation. An independent, but collaborative process to quickly (no more than 30 days) investigate each concern, determine root cause, and make recommendations on remedial measures. A report back to the employee (if so desired) on the resolution of the issue. This should include periodic statistical reports to the entire organization on the general findings and results. Periodic structural reports that sum up the high level issues and take-aways (e.g. training issues, excessively complex operator or manufacturers procedures. 7

8 A Nod to PG&E for Pioneering Non-Punitive Reporting! Note: PG&E currently has a Non-Punitive Reporting Process in place and deployed in the gas segment of its business. Further, they have been very helpful in sharing their development processes, and very open with identifying what worked (and what didn t) as they built their systems and processes. As a result of their openness and sharing, CGV has not only learned a great deal about the challenges of creating Non-Punitive Reporting, but will also be able to deploy our system much more quickly than would have otherwise been possible. CGV is very grateful to Nick and his team for all of their help 8

9 Existing CAP App Screenshots 9

10 App Icon on Phone Screen Authenticate with LAN ID 10

11 Filling Out the Required Fields 11

12 Selecting Additional Options 12

13 Selecting Additional Options 13

14 Take Pictures Using Your Phone 14

15 Review Pictures Taken Call CAP Help Desk for Help 15

16 Submit Your Issue Submission Successful 16

17 The Report Tracking Process NOTE: This is a work in progress. Application is currently in the design/build phase. Features will be made available in phased releases. Not all features may be incorporated in the final solution. 17

18 Investigation and Reporting Tracking Process 18

19 New Issue Form Expanded Description Screen 19

20 Preview Selected Images Add Additional Details 20

21 Preview Options Selected Save Draft For Later Editing 21

22 Navigation Screen Review Drafts for Edit 22

23 Navigation Screen View Status of Existing Issues 23

24 24