Little is known (or at least has been released) about the actual failure of the Blowout Preventer on the Deepwater Horizon. However, a technical paper (2003) has surfaced that may be a “smoking gun” if it is found that maintenance was deferred on the BOP to reduce costs of drilling.
Here’s a link to the paper (Earl Shanks, Transocean, presented at the Offshore Technology Conference, 2003):
“Because of the pressure on getting the equipment back to work, root cause analysis of the failure is generally not performed.”
Ah … a failure to perform root cause analysis to save time (and big bucks) during drilling.
Another quote:
“In general, operating reliability (of the BOP) is maintained on rigs mostly through regular maintenance intervals rather than specifying a reliability of a system or a component to minimize maintenance.”
The article also said:
“… this is a very expensive approach, and it is also an opportunity to introduce human error into the system.”
Most of the paper is about ways to improve the design and reliability of Blowout Preventers. But the vultures are circling. And the smoking gun quotes above will mean trouble if it is found that any maintenance was skipped or if the BOP had a poor reliability record.
If maintenance was skipped and/or if the BOP had a poor reliability record, you will hear the cry that BP is once again trading lives (as at the BP Texas City explosion) and the environment (as at the corrosion related oil leaks in their pipeline at Prudhoe Bay). Actually, many don’t need evidence. They will start saying it already!
[Comment From Greg Hellman, BNAGreg Hellman, BNA: ]
OSHA has placed an injury and illness prevention program rule on its agenda for the first time. Could such a rule address musculoskeletal disorders in some way?
Monday April 26, 2010 1:27 Greg Hellman, BNA
1:27
David (OSHA):
The i2p2 standard is not a substitute for other OSHA standards. It provides a mechanism to achieve the culture change needed in this country to effectively address workplace safety and health issues. It will be the employer’s responsibility to identify all hazards in their workplace, which may include ergonomics, falls, amputations, electrocutions, work-related respiratory disease (such as occupational asthma), etc. The i2p2 standard simply provides a mechanism for employers to identify hazards; however, the control of those hazards will be required by existing OSHA standards and the general duty clause, as is currently the case.
“How to Become Best in Class in Equipment Reliability by Maximizing Uptime” was a best practice session presented by Heinz Bloch at the 2009 TapRooT® Summit.
“Troubleshooting Plant Process Upsets: The Application of Customizable Equifactor® Troubleshooting Tables to Capture the Knowledge of Your Sages and Wiz Kids” was a best practice session presented by Jason Laws at the 2009 TapRooT® Summit.
2009 TapRooT® Summit best practice session “Practical Tools to Stop Worker Error” presented by Ralph Brickey, Jeff Hubbart and Chris Vallee. (Click the “Full Screen” button at the top right of the document to view the document in its entirety.)
I’m in a session on Success Stories from TapRooT® Users that have applied advanced root cause analysis techniques. Theresa Guay from Irving Oil gave an excellent talk about their use a TapRooT® to make pretty dramatic improvements in safety.
Right now, Ron Pryor is providing a very interesting talk on a kaizen project to improve environmental performance. He’s showing the Iowa’s largest SnapCharT®.
Wish you could be hear to hear the really useful lessons learned.
(Picture of Ron presenting and Iowa’s largest SnapCharT®. Boy … Ron sure is moving fast!)
Best practice presentation “Analyzing the Attack on the USS Stark” presented by Shane Deichman at the 2009 TapRooT® Summit. (Click the “full screen” button at the top right of the documents for best view).
“Analyzing 230 Environmental Incidents in 5 Months” is a 2009 TapRooT® Summit best practice session presented by Buck Griffith and Kevin McManus. (Click “full screen” on the top right of the document for best view.)
Bill Sirois, Senior Vice President & COO, Circadian Technologies, provided this informative white paper about the myths and realities of fatigue. Bill will be presenting “How Fatigue Impacts Human Error” at the 2009 TapRooT® Summit. (Click the “Full Screen” button at the top right of the document to see the document in its entirety.)
Here’s a link the Summit Opening Presentation (PDF format). It will help you get a better idea what the Summit is all about. (It’s big so it will take a few minutes.)
A TapRooT® User sent me this PowerPoint this morning. I’m always interested in preliminary failure analysis and this one is quite interesting. Here is the link to download the PowerPoint (.pps):
Time for a math lesson….. 60 students divided into two classes equals 14 final group exercises and presentations which equals 14 separate incidents analyzed using TapRooT®. Now that was a good day!
Here’s the tough crowd that critiques each presentation.
Here’s the course participants with new confidence presenting what happened, why it happened, and what they are going to do to keep the incident from happening in the future.
After just two days of training these students go back to work much more confident in their ability to find and fix the root causes of accidents, incidents, near-misses, quality problems, and process upsets.
If you would like your staff to be able to confidently lead a root cause analysis, consider sending them to a public TapRooT® Course. Or call us at 865-539-2139 about scheduling on-site training for 10 to 32 employees in a class.
Thursday night, Mark gave a talk on human error and root cause analysis at the National Irish Safety Organization pre-Conference Dinner in Trim. It was an excellent dinner and a receptive, interested audience.
Friday, Mark Paradies and Linda Unger will be at the NISO Conference and have a stand in the exhibit area.
I was so busy at the 2008 Summit that I really didn’t have a chance to take a break from Sunrise to Sunset.
That’s why I didn’t provide minute to minute reporting on what I was learning at the Summit – I just didn’t have a chance to write.
I did take some notes and I thought that readers might be interested in what I learned. Therefore, I will share my “A-Ha’s” here for everyone to read.
1. I learned from Darby Allen that 5-10% of all profits are consumed by the costs of accidents and incidents. The costs include hidden costs. For example:
Fines
Legal
Investigation
Productivity Loss
Retraining
Lost Production/Missed Orders
Sullied Reputation
Hidden Equipment Damage
2. I learned from Dave Prewitt that senior management needs a single source (a single database) that has all failure data and costs in it. This includes audit findings. That senior management can then use the data to build an organization that is resistant to disaster because they proactively ensure that systems are safe.
3. I learned from Lt. Col. Hayles that big organization naturally tend to cover up senior management failings and look for scape goats when big things go wrong. That this is a natural part of “protecting the mission of the organization”.
4. I received lots of good ideas about TapRooT® and the TapRooT® Software from the TapRooT® Advisory Board Meeting.
5. I really enjoyed the great people at the Summit and had a wonderful time at the Reception/Birthday Party where I got a chance to catch up with two old friends – David Busch and Kevin O’Connor.
6. I learned from Carolyn Griffith that the UK Rail Accident Investigation Board spends 7 months training one of their new investigators. Also, that a “no blame” policy is a major part of their investigations.
7. I heard many user best practices at several best practice sharing sessions including the TapRooT® User Best Practices Session run by Linda Unger and Michele Lindsay. I’ll try to do a separate write up of these later.
8. I learned from Chris Vallee (Six Sigma Black Belt and TapRooT® Instructor) that SnapCharT®s and Swim Lanes can be combined into a powerful Lean/Six Sigma tool.
9. That even though I had studied the accident at Three Mile Island extensively, I could learn much more by listening to an operator who was at the panel (Ed Frederick).
10. I learned from Marcia Wieder that dreams and visions are similar and that fear is the biggest roadblock to achieving your dreams (vision).
11. That I need to practice if I am going to play golf!
I also learned so things in general about the Summit that others should know about…
1. That there were many outstanding sessions that people told me about (and that I wanted to attend) but that I couldn’t go to. Therefore, bring several people from your facility to cover all the applicable sessions that you want to learn from.
2. That you should come early and stay late. This helps you learn more.
Start by attending one of the many pre-Summit courses.
Next, come down early in the morning and have a leisurely breakfast while networking with other participants.
Don’t plan to leave early. Plan to stay over Friday night and leave Saturday morning.
3. That people love to share best practices. We had 10 Best Practice sharing sessions at the 2008 Summit that were focussed on allowing participants to share their knowledge with others. These were some of the highest rated sessions of the Summit because the calibre of the attendees at the Summit is so exceptional.
4. That people love to be inspired. Speakers that inspire are always highly rated. Heinz Bloch, Marcia Wieder, Nikki Stone, and Beverly Chiodo inspired their audience and helped people leave the Summit energized to make a difference when they returned to work.
5. That even with a crowd that is as enlightened at people at the TapRooT® Summit, it is hard not to blame people for mistakes. This became apparent after Lt Col Hayles talk. Some of the people I spoke to just could get by his mistake when he pulled the trigger in a friendly fire incident. They could see how he was set up for the accident by factors beyond his control. And that to prevent future friendly fire accidents, you must go beyond “being more careful next time.”
6. That a hot room for one is a cold room for another. Temperature is an individual preference.
Here are some things I already knew, but were reinforced by the Summit:
1. We have great clients that are industry leaders. I’m always impressed by the discussions we have and how willing participants are to share their best practices.
2. I have a great staff that knows what they are doing, plans well, and handles unexpected changes with panache (style, grace, and a flair for excellence).
3. That even the best in any industry can learn from others. Even the best companies can improve.
4. That even companies with the most to learn, have best practices that others can learn from.
5. That some of the most eye opening lessons come from outside your industry (if you can translate from their terminology to yours).
6. That having a good time and learning are not mutually exclusive activities.
7. That TapRooT® really is an exceptional root cause analysis tool that is changing the way the world solves problems.
8. That EVERY facility and company that uses TapRooT® should have someone at the Summit. We guarantee that what you learn will produce a return on investment at least 10 X the cost of your attendance or you get your money back. So start planning to attend in 2009!
In February I had the opportunity to teach a portion of the science behind The TapRooT® System to the ASQ Automotive chapter in Detroit. The presentation went well and the research that supported my presentation was recently published in the ASQ Automotive Excellence Magazine. For more information about the article and ASQ, click on this link: ASQ Automotive Excellence Spring Magazine. There are also over 40 references listed in the article that helped me give a robust representation of root cause analysis research that you can look up.