site map Root Cause Methodology and Tools for Improved Operations
Home
About TapRooT®
Course Info
Summit Info
Software
Equipment Troubleshooting
Weblog
Store
Support
Contact Us

Archive for January, 2008

San Diego 5-Day TapRooT® Advanced Root Cause Analysis Team Leader Course Is Full!

Thursday, January 31st, 2008

Today is Day 4 of the 5-Day TapRooT® Advanced Root Cause Analysis Team Leader Course in San Diego. We had to split the course between two hotels (both courses filled up!).

Here’s some pictures from the course that Mark Paradies and Chris Vallee are teaching…

Dscn2508

Chris teaching…

Dscn2510

Class listening intently…
Dscn2509

Dscn2511

Group exercise - spirited debate and learning!
Dscn2512

If you haven’t attended a TapRooT® 5-Day Course, you are missing an opportunity to learn advanced root cause analysis that can help your company improve!

Rail Accident Report - Derailment of freight train at the King Edward Bridge in Newcastle, England, on May 10, 2007

Thursday, January 31st, 2008

Picture 9

Download the report from the UK Rail Accident Investigation Branch:

http://www.raib.gov.uk/cms_resources/080131_R022008_KEB.pdf

The report has four recommendation to reduce risk and improve performance.

UK Rail Accident Investigation Brach Publishes Accident Report on Derailment in London Underground

Thursday, January 31st, 2008

Picture 8

For a report on the July 2007 derailment near Mile End Station in the London Underground, see:

http://www.raib.gov.uk/cms_resources/2008-01-31-R032008-MileEnd.pdf

to download a PDF.

There are five recommendations for improvement in the report.

Job Opening: Exelon, LaSalle Nuclear Power Station - Instrumentation & Controls Planner - Needs Root Cause Analysis Skills

Thursday, January 31st, 2008

Exelon, a licensed TapRooT® User, is looking for an Instrumentation & Controls Planner with Root Cause Analysis Skills. For more info, see:

http://www.nukeworker.com/job/view.php?job_id=5887

System Improvements / TapRooT® 20th Anniversary / Birthday Party at the Summit!

Thursday, January 31st, 2008

Markbigmust

In 1988, Mark Paradies, with the help of David Busch and Kevin O’Connor, started System Improvements and developed the tools that started the development of TapRooT®. Linda Unger came aboard in 1989 to get things moving.

As you can tell from the old picture above, a lot has changed since 1988! TapRooT® has been developed, revised, and improved! And people have used TapRooT® to save lives, prevent injuries, improve the quality of products and services, improve equipment reliability and maintenance practices, improve productivity, and achieve operating excellence.

Because this a special year - the year that System Improvements turns 20 years old - we wanted to hold a special celebration. So at the TapRooT® Summit in Las Vegas on June 25th we will hold the System Improvements 20th Birthday Party!

Who will be there? All the Summit attendees. And we hope that includes you!

In addition, Mark Paradies, David Busch, Kevin O’Connor and Linda Unger - the people who got SI going - will be there.

Who else?

Elvis

Elvis (Greg Miller) will provide entertainment. And Olympian Nikki Stone will sign autographs.

Nikkistone

There will be food and drinks.

Lindaclient2-2

And there will be performance improvement exhibits.

Exhibit01-1

We are planning more surprises for the party, but we won’t tell about them until the first day of the Summit.

For complete Summit information, see:

http://www.taproot.com/summit.php

Then get signed up for a great learning event that includes a Birthday Party!

Bennaphilparty

Kevin McManus - Performance Improvement Coach and TapRooT® Instructor - To Speak at February ASQ St. Louis Meeting

Thursday, January 31st, 2008

Topics:

Pursuing Process Excellence – What’s Holding You Back?

Process Excellence from the Inside Out – Who Needs Top-Down Support?

For more info see:

http://www.asqstlouis.org/membership_meeting/

For more about Kevin’s work see:

http://www.greatsystems.com/

Monday Hearing on BP Texas City Blast Plea May Include Survivor Testimony

Thursday, January 31st, 2008

The Judge deciding on the BP Texas City explosion criminal settlement could hear from survivors asking for a bigger penalty. For more in the Houston Chronicle, see:

http://www.chron.com/disp/story.mpl/business/5500858.html

Construction Worker Killed at NYC Site

Thursday, January 31st, 2008

The building boom has a human cost. Another fatal construction accident in New York. For details see:

http://www.newsday.com/news/local/wire/newyork/ny-bc-ny–constructionaccid0130jan30,0,7640304.story

Job Opening: UK - Hardware Engineer - Root cause analysis of failures in manufacturing and in the field

Thursday, January 31st, 2008

For more info, see:

http://www.ukjobs.net/job-1475522-joEkS.html

Job Opening - Securities/Finance - Must Use Root Cause Analysis to Resolve Problems

Wednesday, January 30th, 2008

Here’s a differet job that requires root cause analysis skills:

http://www.hotgigs.com/logged_in/search/index.cfm?profileid=Ji5RUi5YXkYlCg%3D%3D&userid=JS8hUihYLlAgCg%3D%3D&id=Ji5RUi5YXkYlCg%3D%3D&page=viewsearchresults&Mode=G&override=true&jobview=yes

One Year After Deadly Explosion at WV Convenience Store CSB Completes Testing of Key Valve — Agency Continues Its Examination of Safety Practices and Emergency Response

Wednesday, January 30th, 2008

The following press release is from the U.S. Chemical Safety Board.

Washington, DC, January 30, 2008 - On the first anniversary of a fatal propane explosion at a West Virginia convenience store, the U.S. Chemical Safety Board (CSB) today announced that testing has been completed on a key propane valve and outlined other issues that will be examined in the final investigation report.

The accident on January 30, 2007, at the Little General Store in Ghent killed four people and injured six others when propane gas was suddenly released through a liquid withdrawal valve during a changeover between two propane tanks.  A volunteer firefighter and an EMT who responded to reports of the leak were among those killed when the propane cloud ignited, destroying the store.

The CSB has examined and tested the valve and found that on the day of the accident the valve was stuck in an open position.

Investigators are continuing their examination of regulatory and code compliance as well as West Virginia’s gas safety practices.

‘This investigation is about more than figuring out what went wrong with the valve, it is about getting to the root cause of this accident and preventing a similar incident from occurring,’ said CSB Lead Investigator Jeffrey Wanko, P.E., C.S.P.

On the day of the accident, a technician working for Appalachian Heating (a company that had a business arrangement with Thompson Gas) was preparing to switch propane service to Thompson Gas from a previous propane vendor, Ferrellgas. As part of the process, the technician was to transfer propane from the Ferrellgas tank to the newly installed one.

The Ferrellgas tank was located against the store’s outside rear wall. The Thompson Gas tank was located about ten feet away.  While preparing for the transfer, propane began flowing out of the liquid withdrawal valve on the Ferrellgas tank located next to the store.

Lead Investigator Jeffrey Wanko said, ‘The placement of the tank facilitated gas entering the building and the ignition of the flammable gas and contributed to the high number of injuries and fatalities.’ The tank did not comply with National Fire Protection Association or Occupation Safety and Health Administration siting specifications which require that a propane tank be placed 10 feet from the building.

Investigators believe personnel involved in the installation of a new propane tank at the store removed a metal screw cap on the liquid withdrawal valve, in preparation for removing propane from the old tank.  The malfunctioning withdrawal valve leaked, resulting in an uncontrollable release.  The technician was unable to stop the flow and placed a 9-1-1 emergency call at 10:40 a.m.

CSB investigators found that in common with many states, West Virginia does not require technicians who install propane tanks to receive any formal training.  The CSB is also examining the practices of 9-1-1 emergency call centers to provide basic emergency instructions for flammable gas incidents such as proper evacuation procedures. In this instance, Little General employees stayed in the building during the gas release.

The CSB’s final report and safety recommendations are expected to be complete in mid-2008.
 
The CSB is an independent federal agency charged with investigating industrial chemical accidents. The agency’s board members are appointed by the president and confirmed by the Senate. CSB investigations look into all aspects of chemical accidents, including physical causes such as equipment failure as well as inadequacies in regulations, industry standards, and safety management systems.

The Board does not issue citations or fines but does make safety recommendations to plants, industry organizations, labor groups, and regulatory agencies such as OSHA and EPA. Visit our website, www.csb.gov.

For more information, contact Director of Public Affairs Dr. Daniel Horowitz, (202) 261-7613, or Public Affairs Specialists Hillary Cohen at (202) 261-3601, or Jennifer Jones at (202) 261-3603.

Driving in Snow in the Middle-East

Wednesday, January 30th, 2008

Snow in Gaza -

Picture 7

Accidents sure to follow!

Root Cause Network Newsletters Archive

Wednesday, January 30th, 2008

Want to see past issues of the Root Cause Network Newsletter?

Read about:

  • New TapRooT® Book (Issue 87 - January)
  • Trending: Doing it Wrong? (Issue 87 - January)
  • Rule Breakers (Issue 87 - January)
  • A Perfect Corporate Safety Conference  (Issue 86 - November)
  • Bullet-Proof Root Cause Analysis (Issue 86 - November)
  • BP Not Alone? (Issue 86 - November)
  • Lean Root Cause Analysis (Issue 84 & 85 - May/September)
  • Repeat Failure (Issue 85 - September)
  • Instant Root Cause Analysis (Issue 85 - September)
  • Spotlight on Refinery Safety (Issue 85 - September)

OR see past issues of the TapRooT® Friends/Experts e-Newsletter and read about:

  • What to do when the facts don’t agree. (January 08)
  • Making plans for the new year. (December 07)
  • Press Access to In-Progress MSHA Investigation (November 07)
  • “Safety First” history. (October 07)
  • What’s a CAPER? (September 07)
  • Tips from Summit Attendees (June-September 07)
  • Applying Lean to Root Cause Analysis & Corrective Action Programs

To see a complete archive, go to:

http://www.rootcause.net/

Reminds me of old times… Bus rides to the “site” in the snow.

Wednesday, January 30th, 2008

I saw an article about a bus accident near ARCO, Idaho. It reminded me of my time (six months as a student) at S1W (west of Idaho Falls) at the INL site.

 Images 7791475 Bg1

It still looks cold in the winter. (I bet the bus drivers are looking forward to global warming!)

 Images 7791475 Bg2

I remember getting a foot a snow several days in a row and never having a snow cancellation. The average temperature was BELOW zero in January.

 Images 7791475 Bg4

I also remember great skiing. (And difficult driving getting there on black ice.)

 Main Content Wp En Thumb 5 53 300Px-Big Southern Butte At Craters Of The Moon Nm-750Px

I climbed the Great Southern Butte in the early spring. It was still snow capped and we used show shoes to climb up and then slid down.

I really enjoyed my time in Idaho … But I’m glad I don’t face that weather every day.

Article About Dropping a Patient During Surgery - Family Sues - Root Cause Analysis Points to Communication

Tuesday, January 29th, 2008

An 86-year-old woman (under anesthesia and not conscious) was dropped from a surgery table when a safety belt was released in preparation for transferring her to a mobile hospital bed. She died as a result of the head injury.

The family is suing. The article about the death said:

“The investigative report said the hospital did its own root cause analysis and determined that the doctors and nurses in the operating room were preoccupied with their own tasks and that the ‘removal of the . . . safety belt from the patient was not verbally communicated.’”

“The hospital has adopted a protocol requiring all nurses and doctors put their hands on the patient before removing the safety belt and making sure that there are people on both sides of the table.”

I know this isn’t a complete Sentinel Event Report, but what do you think of “communication” and a policy of “putting their hands on the patient and having people on both sides of the bed before removing the safety belt” as the Safeguards to prevent future accidents? Are these Safeguards strong enough? Will they be effective?

Leave a comment and let me know what you think…

ADDITION:

Here’s what the table looks like (I think):

 Med Orthovisiona

Here’s another example:

 Images Ortho

Or another:

 Images Ortho2Forweb

Demolition Accident Kills One at Pacific Gas & Electric Decommissioned Power Plant

Tuesday, January 29th, 2008

Picture 6-1

Read the Associated Press story at:

http://ap.google.com/article/ALeqM5jCUZUyqz41WcLXfHXqfWu3cIWLFgD8UF75KO0

TapRooT® Summit Movies

Tuesday, January 29th, 2008

Generalsession06

Want to learn more about the TapRooT® Summit? Then listen to past attendees tell their experience.

Markparadiesteaching-2

Introduction to the Summit:

http://www.taproot.com/download/summit08_discussion.mov

Networking03-1

Networking at the Summit:

http://www.taproot.com/download/summit08_networking.mov

Learning08-2

Breakout Sessions at the Summit:

http://www.taproot.com/download/summit08_breakouts.mov

Wnetworking-1

Best Practices Learned at the Summit:

http://www.taproot.com/download/summit08_bestpractices.mov

Dscn1567-1

Pre-Summit Courses:

http://www.taproot.com/download/summit08_presummit.mov

Happy03-2

Summit Fun and Refreshing/Reenergizing:

http://www.taproot.com/download/summit08_fun.mov

Bennaphilbusiness-2

Where can you learn more about the Summit? See:

http://www.taproot.com/summit.php

Tommyclient-1

Monday Accident & Lessons Learned: Cost of a Marine Accident (Oil Spill)

Monday, January 28th, 2008

It was December 7th.

Samsung, an industrial giant, was responsible for a crane on a barge that was being towed by two tug boats.

The weather was bad.

The seas were rough.

The barge broke loose from the tugs.

Now for the bad news … there was an oil supertanker anchored nearby.

With the whole ocean available for the barge to float in, what happens? It hits the supertanker that is at anchor, makes three holes, and spills 10,900 tons of oil.

But what can we all learn from this accident? Read about the protests and even suicides in the wake of the oil spill:

http://afp.google.com/article/ALeqM5gTFYqvDI0TxGOYZK66K9pBC7FAkQ

Picture 5-1

Also: http://www.energycurrent.com/?id=4&storyid=8266

Click Read More to see video and another story link.

(more…)

The Safety “Outsiders” and the “Hidden Factory”

Monday, January 28th, 2008

 F Rqqp Image 1813-465-349-Size
What reaction does the Environmental Health & Safety Engineer (EH&S) get from your employees? If it’s “oh no”, we better put on our safety glasses when we see her/him enter the work area, you have a “Hidden Factory”. Do you include EH&S in new facility or site designs? If not, you have a “Hidden Factory”. What is a “Hidden Factory” and what does it have to do with safety?

Six Sigma Black Belts and Quality Performance Experts have known about the “Hidden Factory” for years. Basically, you have company standards, policies, and procedures that are required to be used and then you have the cost of poor quality caused by short-cuts and business as usual non-standard practices. The pursuit of performance quality is to identify company requirements, identify how work is “really” being performed, and close the gap between the two to improve customer needs. The goal of any EH&S Engineer should be to recognize this “Hidden Factory”, the why’s behind the short-cuts, and their impact on SAFETY AND WORK COMPLETION. This also starts to close the gap between company risk and hazard assessments.

The EH&S will not be invited to see this internal company view if not she/he is not considered part of the work force. Prior to shutting down a site or work area for a non-risk of life-limb-enviroment violation, the EH&S Engineer should see how to help develop a safer process. Don’t be the outside enforcer, be the listener and helper. From past experience in the military and civilian life, this easy first step has been rare. It is easier to say people should be safe because it is the right thing to do. Recently however, I am seeing a positive change in closing this gap. Just this week while teaching a 5-day TapRooT® root cause analysis course in Edmonton, I had an operations lead in class with two of his EH&S engineers. Planting this first TapRooT® seed will encourage further discussions in the “Hidden Factory” for this company.

Oil Tank Truck Explosion in Philippeens: “…accident caused by a gas leak…”

Sunday, January 27th, 2008

A story about how an accident happens:

http://newsinfo.inquirer.net/inquirerheadlines/metro/view/20080125-114613/Oil-tanker-explosion-an-accident

BP Texas City Explosion: Texas Supreme Court Rules Against Extensive Deposition of ex-BP CEO John Browne

Saturday, January 26th, 2008

See this article in the Houston Chronicle:

http://www.chron.com/disp/story.mpl/business/5487314.html

Problems Driving on Snow Video

Saturday, January 26th, 2008

Finding a Castle in a Haystack is what Good Root Cause is All About

Friday, January 25th, 2008

Farmer hides castle from building inspectors behind a wall of hay bales. Now I have heard of searching for a needle in a haystack but wow, a castle? But think about it , can you find the “castle” in your root cause analysis when it is right in front of your eyes? Unfortunately, this is the problem we have when using cause and effect diagrams and 5 why’s where you fill in the questions needed to be asked. If you are not familiar with human factors engineering and human behavior in systems, you might as well be looking for a “needle”.

 Illusions Youngladyoldlady
Why are these other root cause tools ineffective you ask? WITHOUT getting technical, our own “rules-of-thumb” prevent us from seeing or recognizing anything that does not match our current understanding of the world we live in. Look at the picture above, do you see a young woman or an elderly woman? The mind prevents us from seeing one image over the other at the same time. A good root cause analysis prevents us from investigating an incident or reoccurring problem using our past understanding of limited subject matter expert experience. When I say limited, the implication is that the operator, safety officer, manager, and quality inspector only understand their part of the company processes; while good at what they do, total system influences on human performance is usually limited. A good root cause analysis should ask questions at the system level creating a new way of looking at the “castle”. This is why TapRooT® is a root cause analysis system and training that helps solve problems both reactively and proactively. Call us at 865.539.2139 if you are tired of looking for the “needle”.

Fire in Vegas Hotel….Good Time to Perform Proactive Audits in Nearby Hotels

Friday, January 25th, 2008

Just finishing up another successful 5-Day TapRooT® Advanced Root Cause Analysis Team Leader Training in Edmonton, I saw this headline, “Fire Eases at Vegas’ Monte Carlo”. First question, does the hotel on fire perform proactive Safeguards Analyses? Second question, does the hotel scheduled for the TapRooT® Summit in June perform proactive Safeguards Analyses? Watching news before I fly to San Diego for another 5-day TapRooT® course, the news reported recent remodeling may be a clue for the fire. Will the Monte Carlo perform a Change Analysis I wonder? If this was your hotel, do the analyses listed above sound familiar? If not, contact us at System Improvements, Inc. at 865.539.2139.

Healthcare Root Cause Analysis is Secret!

Friday, January 25th, 2008

An interesting story from American Samoa points out that hospitals can’t release information on a healthcare root cause analysis unless the patient consents.

See:

http://www.pacificmagazine.net/news/2008/01/25/lbj-medical-center-wont-release-information-on-governor

for the whole story.

More on 777 Crash Investigation

Friday, January 25th, 2008

See:

http://seattletimes.nwsource.com/html/businesstechnology/2004143439_web777crash24.html

CSB Concludes Field Phase of T2 Blast Investigation in Jacksonville, FL — Higher Number of Offsite Injuries Found

Friday, January 25th, 2008

Press release from the Chemical Safety Board:

Washington, DC, January 25, 2008 - Investigators from the U.S. Chemical Safety Board (CSB) today concluded the initial field investigation of the fatal accident at T2 Laboratories Inc. Among investigators’ findings thus far is that that the number of people injured was more than double what was known immediately after the accident.

Investigators say that 33 people were injured in the massive explosion and fire at the Jacksonville, Florida, chemical plant on December 19. Many of these injuries resulted from flying and falling debris due to structural damage to offsite buildings. The team plans to return to Washington, DC, later today to continue the investigation of the causes of the accident.

The explosion resulted in the death of four workers; preliminary findings indicate that the accident occurred as a result of a runaway chemical reaction during the production of a gasoline additive called methylcyclopentadienyl manganese tricarbonyl (MCMT or Ecotane®).  The loss of control of the reaction probably occurred during the first step of the process where more than half a ton of metallic sodium was reacted in a steel vessel with other raw materials, producing hydrogen gas as a byproduct.  T2 is a small company with about a dozen employees and the single production site in Jacksonville.

The reactor eventually overpressured and ruptured at a pressure of several thousand pounds per square inch.  The contents of the reactor immediately ignited creating a fireball and mushroom cloud rising approximately 2000 feet high.

CSB Supervisory Investigator Robert Hall, P.E., said, ‘As a result of our interviews, the CSB has discovered that over 30 people were injured, versus the 14 reported the first few days following the accident.’ After conducting over 50 interviews CSB investigators determined the significantly higher number of injuries. Initial media reports of 14 injuries did not count individuals who sought medical attention on their own.  Most of the injuries occurred off-site when a powerful blast wave swept through surrounding businesses; only 9 people were at the T2 site when the accident occurred.

Mr. Hall said, ‘We will conduct laboratory testing to quantify the amount of heat and pressure released by the reaction.  Our goal is to discover what went wrong on December 19 and to prevent a similar accident from happening again.’

For more information, please contact Public Affairs Specialists Hillary Cohen at (202) 261-3601 or Jennifer Jones at (202) 261-3603.

Information on the Investigation of the Boeing 777 Crash in London

Friday, January 25th, 2008

 Media Images 44379000 Jpg  44379767 Boeing Pa203B

See this BBC report:

http://news.bbc.co.uk/1/hi/england/london/7208126.stm


 Media Images 44367000 Jpg  44367794 Crane Pa

UK National Health System Admits Error - Patient Given Kidney of Wrong Blood Type - Root Cause: “Human Error”

Friday, January 25th, 2008

A story in The Mail on Sunday, a UK paper said:

Elizabeth Ward, of the British Kidney Patients Association, said: “I’m quite sure it’s the first time this has happened in this country. It’s hard to understand how this could have happened.”
What was she talking about? A kidney transplant patient was forced to have the new organ removed after just a few hours – when it was discovered that the patient’s blood type had been incorrectly recorded on a computer database.

The incident, which was only revealed in response to a Freedom of Information request, comes just days after Gordon Brown called for a system in which individuals are presumed to consent to the use of their organs for transplant unless they specifically stipulate otherwise.

The error took place three years ago and would have remained secret had The Mail on Sunday not seen a confidential report into the “profound error”.

The internal investigation did not name the hospital involved. The report concluded that the initial data entry mistake was “human error” but said “there was no means of identifying” who did it, or where the incorrect information had been entered.

Although the mistake was made by Hospital Trust staff, the report blamed UK Transplant for failing to set up a standard nationwide system for entering patient details. It said: “During this investigation it became apparent that any number of professionals could have entered the blood results on to the computer.

“UK Transplant do not have a uniform system in place. [They] have not been prescriptive in dictating practice, and have allowed local Trusts the freedom to adopt whatever systems they deem fit.”

But a spokeswoman for UK Transplant said the report was “misleading” as the organization had no responsibility for the way Trusts entered information. “We need to be clear that the mistake here was not with UK Transplant,” she said.

“Information that Trusts provide is what goes into the national database. In this case, we have correctly recorded incorrect data. Our system has been in place for several years and can be viewed by Trusts at any time to check the data we’re holding.”

Once again, BLAME (rather than a fix for the problem) seems to be a major issue.

A source at UK Transplant said the mistake was “extremely rare” as fewer than five of the 20,000 organ transplants in the past seven years were made in error.

Hmmm … 5 in the past seven years? That sounds like more than “This has never happened before.” And if the reports aren’t made public, how can this error rate be verified?

For the complete article, see:

http://www.mailonsunday.co.uk/pages/live/articles/news/news.html?in_article_id=509289&in_page_id=1770

Music Video Can Make Accidents Funny

Friday, January 25th, 2008

Car accidents usually are NOT funny. but add a little music, and speed it up to sound like the chipmunks, and … anything can be funny.

Exelon CEO Named Best Electric Utility CEO in America by Institutional Investor

Thursday, January 24th, 2008

Exelon, a long-time Licensed TapRooT® User, was honored when their CEO, John Rowe, was named Best Electric Utility CEO by Institutional Investor.

John said: “Exelon has been one of the most consistently profitable companies in the electricity industry, having grown our operating earnings an average of about 12 percent per year over the past seven years. I’m honored to be recognized by the financial community and Institutional Investor for our success. It’s my job and the job of Exelon’s management team to deliver sustainable value to our shareholders, and I believe Exelon is uniquely positioned to continue on a successful path in the years ahead.”

To arrive at its list of Best U.S. CEOs, Institutional Investor surveyed portfolio managers, analysts and other investment professionals. It asked these individuals to name the best U.S. CEOs in the sectors in which they invest. Some 900 people at 425 institutions responded, offering first, second and third place votes in each of the sectors with which they were familiar. These votes were weighted to produce a score for each executive that Institutional Investor used to compile the rankings.

Additional information can be found at www.iimagazine.com and in the January issue of the magazine.

Exelon Corporation is one of the nation’s largest electric utilities with more than $15 billion in annual revenues. The company has one of the industry’s largest portfolios of electricity generation capacity, with a nationwide reach and strong positions in the Midwest and Mid-Atlantic. Exelon distributes electricity to approximately 5.4 million customers in northern Illinois and Pennsylvania and natural gas to approximately 480,000 customers in the Philadelphia area. Exelon is headquartered in Chicago.

Part of Exelon’s success is due to their efforts to improve performance both reactively and proactively by finding the root causes of human performance and equipment problems. As part of the TapRooT® Summit, Exelon will be sharing one of their performance improvement programs - Exelon’s Error Free Performance Tool.

For more information about the TapRooT® Summit, see:

http://www.taproot.com/summit.php

NTSB Blames Inadequate Safeguards in Two Fatal Metro Accidents

Thursday, January 24th, 2008

For the story from ABC see:

http://www.wjla.com/news/stories/0108/490262.html

For a video report, see:

http://www.wjla.com/news/stories/0108/490262_video.html?ref=newsstory

That Helpless Feeling of Drive on Sheer Ice

Thursday, January 24th, 2008

Watch this and then think about the accident investigation …

Side-Mounted Lifeboat Hooks Need Modification

Thursday, January 24th, 2008

Picture 4-1

Marine Information Notice (MIN) 315 published December 2007describes MCA research project 555 which is a study into the safety of davit-mounted, side launched ships’ lifeboats and their launching systems. The primary objective of the study was to make proposals for measures to improve the hardware performance of lifeboats and contribute to the prevention of accidents.

For more info see:

http://maritimeaccident.wordpress.com/2008/01/24/lifeboat-hooks-not-fit-for-purpose-worldwide/

Job Opening: Augusta, GA - Ingersoll Rand (Club Car) - Senior Mechanical Design Engineer - Needs Root Cause Analysis Skills

Thursday, January 24th, 2008

For complete details, see:

http://jobboard.asme.org/jobdetail.cfm?job=2789544

Job Opening: St. Louis - Director of Quality - Needs Six Sigma/Root Cause Analysis Skills

Thursday, January 24th, 2008

ISO certified small manufacturing company is looking for a Director of Quality that has Six Sigma and Root Cause Analysis skills. For more information, see:

http://www.asqstlouis.org/job_postings/2008/01/director-of-quality-st-louis-area.html

To get advanced root cause analysis training, see:

http://www.taproot.com/courses.php

Plane Crashes After Aviation Safety Meeting

Thursday, January 24th, 2008

You know it’s a bad day when your plane carrying people back from an aviation safety conference crashes. For the whole story see:

http://www.cnn.com/2008/WORLD/europe/01/23/poland.crash/index.html

Summit Safety & Risk Management Best Practice Track

Thursday, January 24th, 2008

Are you interested in improving safety and risk management at your facility?

Would you like to learn safety and risk management best practices from industry leaders from around the world?

Happy02-1

Would you like to network with people from a wide variety of industries who face similar challenges to the ones that you face and who may be able to share unique insights and new solutions to help your company improve?

Generalsession01-2

Then you should be planning to attend the Safety & Risk Management Best Practices Track at the TapRooT® Summit.

The Summit has 9 Best Practice Track sessions and 5 Keynote Speakers. The Safety & Risk Management Best Practice Track sessions include:

Wednesday 10:30-12: Hazard Recognition: The First Step in Safety & Risk Management - Peter Berkholz, Engineering Manager, Capability Resources Australia

Wednesday 1-2:20: CHANGE
1)
Change Dealing with Obstacles that Make Change Difficult - Hal Curry, Consultant, Hal Curry & Associates
2)
Managing the Risks Associated with Change - Malcolm Gresham, Principal Consultant, Practical Solutions Group, Australia; & Jim Whiting, Managing Director, Risk @ Workplaces Pty., Ltd. Australia

Wednesday 2:40-3:55: Accident Investigation Examples
Root Cause Analysis of Major Accidents:

1)
Lexington Airport Runway Mixup - Ken Turnbull, Consultant
2)
Cameco Cigar Lake Mine Flood - Mark Wittrup, Cameco
3)
Texas City Refinery Explosion - CSB Speaker (invited)

Thursday 9:15-10:25: Advanced Behavioral Management: Developing a Modern Safety Culture - Bob King, Director HSE Training/Consulting, Woodland Grange, UK, & Neil Roberts, Consultant, Woodland Grange, UK

Thursday 10:25-10:40: Panel Discussion - Is There a Tradeoff Between Process Safety & Industrial Safety?
Panelists
Brian Hennesey, ConocoPhillips
Valerie Barnes (US NRC)
Bob King (Woodland Grange, UK)
Ken Turnbull (Consultant)

Thursday 1-2:20: TapRooT® User Success Stories from Healthcare & Industry - Linda Unger & Barbara Phillips (Facilitators)
(Three Success Stories to be presented by industry and healthcare users of TapRooT®)

Thursday 2:40-3:55: The Good, The Bad, & The Ugly: Rating Improvement Programs & Incident Investigations - Michele Lindsay, Principal Consultant, P2, Canada; & Mark Paradies, President, System Improvements

Friday 9:15-10:25: Senior Executive Involvement in Safety
1)
Bringing Safety to the Corporate Board - Dave Prewitt, VP, FedEx
2)
What the Corporate Board Needs to Know About Safety - Bob King & Darby Alan - Woodland Grange, UK

Friday 10:35-11:55: Planning Your Improvements
(Improvement planning session with help from experienced TapRooT® Consultants)

In addition to these smaller group discussion sessions, you will also attend 5 Keynote Speaker sessions:

Wednesday
Lt. Col. Ralph Hayles (retired), Gulf War Veteran, Lessons Learned from Friendly Fire
Nikki Stone, Olympic Aerial Skiing Gold Medal Winner, Overcoming Setbacks to Achieve Olympic Success

Thursday
Carolyn Griffiths, UK Rail Accident Investigation Branch Chief Inspector, Lessons from Setting Up an Independent Accident Investigation Organization
Ed Frederick, Exelon Nuclear (Board Operator at TMI during the accident), The Accident at Three Mile Island - An Insider’s Perspective

Friday
Marcia Wieder, Doctor of Dreams, You Can Make Improvement Happen

Where will this exciting and useful Summit be held? Las Vegas on June 25-27, 2008.

How can you find out more?

See:

http://www.taproot.com/summit.php

Sanjayteaching-1

In Response to Criticism that Plea Agreement is too Lenient, BP Says Plea Agreement is ‘Harshest Option’

Wednesday, January 23rd, 2008

The BP Texas City Refinery explosion case drags on (since 2005). An AP story about the BP plea agreement with Federal Prosecutors says:

“Federal prosecutors took the harshest option available in brokering a $50 million fine proposed as criminal punishment for BP PLC’s deadly 2005 Texas City refinery explosion, the company and the government said in court filings Tuesday.”

For the whole story see:

http://www.chron.com/disp/story.mpl/ap/fn/5476163.html

U.S. District Judge Lee Rosenthal is expected to make a decision on the plea agreement by Febuary 4.

Job Opening: El Segundo - Electrical/Systems Engineer - Needs Root Cause Analysis & Corrective Action Experience

Tuesday, January 22nd, 2008

Job opening requires knowledge of radar systems. For more information, see:

See the job posting here.

Job Opening: Saudi Arabia - Industrial Engineer - Needs Root Cause Analysis Skills

Tuesday, January 22nd, 2008

For job posting, see:

http://www.bayt.com/job/job.adp?xid=769096

Why Healthcare Safety Doesn’t Improve

Tuesday, January 22nd, 2008

Sometimes you read stories and you just can’t believe what you are reading.

For example, a New York Times story explained that a government office - the Office for Human Research Protection - shut down a John Hopkins University research project.

The project was using checklist to reduce post-operative infections. Using 5-step checklist had cut the rate of bloodstream infections acquired in the I.C.U by two-thirds. Over 18 months, the program saved 1,500 lives and $200 million dollars.

So why did the government shut it down? The study was breaking the rules. What rules?The NY Times article said that:

“…by introducing a checklist and tracking the results without written, informed consent from each patient and health-care provider, they had violated scientific ethics regulations.”

Here is the logic for the finding reported by the NY Times:

“A checklist is an alteration in medical care no less than an experimental drug is. Studying an experimental drug in people without federal monitoring and explicit written permission from each patient is unethical and illegal. Therefore, it is no less unethical and illegal to do the same with a checklist. Indeed, a checklist may require even more stringent oversight, the administration ruled, because the data gathered in testing it could put not only the patients but also the doctors at risk — by exposing how poorly some of them follow basic infection-prevention procedures.”

By this tortured logic, I’m surprised that any study or improvement efforts are allowed in the medical field. No wonder improvement in the medical industry progresses so slowly.

Heart Attack Victim Survival Rate Good In Canada Despite Long Waiting Times in Health Care

Monday, January 21st, 2008

“Canada ranks 23rd out of 30 countries surveyed in “consumer friendliness” of its health-care system” cites a report by European and Canadian researchers in the Canadian Press. Having more in common with publicly financed and governed European health-systems, the “think tank” researchers wanted to compare Canada with like populations in this first annual “consumer index”. Not including publicly-commercially financed countries such as the United States would provide a better base-line of performance for Canada.

What will the affect of this study be? Canada performed well in survival rates of heart attack, cancer, and other medical procedures, but failed in areas such as treatment waiting times, range of services available, and access to new diagnosis tools and new medicine. First question to ask is whether there were countries that performed well in the latter categories but failed in survival rates? As a medical consumer, what is more important to you, survival rate or “friendliness”? As a medical business, what is important, survival rates or “friendliness indexes” that would bring new customers to your business or longer term survival rates? If business operation policy is changed to perform well in this survey, this will also affect how you perform future sentinel investigations.

As a medical health-system provider, should you chance changing your policy and procedures based on this survey? When business risk assessments and hazard risk assessments diverge this is bad practice. This practice tends to split quality, safety, and operation personnel reducing a one-company mission. How can you prevent this company split? Ensure sentinel investigations and corrective actions are based on accurate human performance and equipment root cause analyses? If you see this bad practice occurring in your medical health service, you may find TapRooT® an effective solution. Contact us from this site to learn what medical health providers have taken on this challenge with TapRooT®.

Monday Accident & Lessons Learned: What To Do When the “Facts” Don’t Agree Part II

Monday, January 21st, 2008

Back in December, I wrote about an accident investigation that was never completed because the “facts” didn’t agree. I asked “How would readers complete the investigation” and asked for comments. The comments can be seen at:

http://www.taproot.com/wordpress/2007/12/10/monday-accident-lessons-learned-what-to-do-when-the-facts-dont-agree/

Having conflicting information is a common problem when investigating an accident.

The best way to detect conflicting information (facts that don’t match) is to put the information collected on a SnapCharT®.

Using a SnapCharT® to display the information sometimes will make the non-factual information obvious (it doesn’t agree with the other stories or the physical evidence). Other times, either story is possible, and you can display how each set of facts is plausible.

What do you do when you have two sets of plausible stories? I try to analyze each possibility, develop causal factors for both stories, analyze each stories root causes, and then look at the potential corrective actions. If I can develop corrective actions that correct the root causes for BOTH stories, I don’t have to know which one is right. If I can’t develop effective corrective actions that will prevent the recurrence of both stories, then I need two sets of corrective actions, one for each story.

In my experience, the main reason (although not the only reason) for conflicting stories is that people are trying to avoid blame and are are either:

1. Telling the investigator a story that won’t get them in trouble.

OR

2. Telling the investigator what they think the investigator wants to hear (to keep the interviewee out of trouble).

The best way to avoid people “telling stories” is to develop a “just culture” or “no blame” environment where accident/incident investigations are seen as performance improvement opportunities rather than witch-hunts. Making this change requires senior management support.

WHAT DO YOU THINK?

Are my suggestions a practical way to deal with conflicting “facts.”

Leave a comment and let me know what you think.