EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

10.12.10

Guest Article: Windows NT and the Deepwater Horizon

Posted in Microsoft, Windows at 2:48 am by Dr. Roy Schestowitz

Microsoft blue ribbon

Summary: An analysis of the causes that led to the Deepwater Horizon blowup (or what failed to prevent it), based on the long inquiry

THE previous post spoke about Stuxnet, which endangers many people whose company/authority/personal computer runs Microsoft Windows. Another recent disaster where Windows got some blame was the Deepwater Horizon blowup [1, 2, 3, 4]. An anonymous Techrights contributor wrote an update on the topic — one which we publish below.

“Here’s an update on the Deepwater Horizon story, “he writes, “New testimony spurred me to look up transcripts that had not been published at the time. There were several bombshells worth sharing and thinking about. For example, Windows NT is named and shamed by the expert witness. Windows was not mentioned in most press coverage but it seems to have played a more central roll than even I expected.”

Here is the report in question PDF and corresponding interpretation:


Windows NT and the Deepwater Horizon

A buggy control system left drillers and the rig blind and might even have damaged a critical safety system on the sea floor.

Microsoft Windows may have been directly responsible for Deepwater Horizon catastrophe. Previously, Techrights showed that Microsoft Windows played a crucial role. A 824 page transcript from the July 23 Deepwater Horizon investigation has been posted and we can see that things were as Techrights guessed. Mr. Williams describes Windows NT, “a very unstable platform” as the root cause of most problems. This buggy Windows based control system left drillers blind when it crashed daily was responsible for safety system bypasses and may have destroyed the annular seal. New testimony from Andrea Fleytas, who operated the alarm panels on the doomed bridge and jumped from the flaming deck with Mr. Williams, shows that the drilling team may have had time to escape if the alarms were not inhibited. This interpretation of her testimony, with some quotes, was published by the Times Picayune. The consequences of this disaster and ongoing cover up are well reported in the Florida Oil Spill Law blog.

Mr. Williams describes typical Windows problems in three identical, malfunctioning control systems, A Chair, B Chair and C Chair, on pages 42 and 101. There’s incompatibility, instability, harmful bugs and worries about viruses. On page 42, Mr. Williams talks about the systems, their importance and how broken they were.

The A-chair is located in the dog house. That is the main operating point for the driller to control all drilling functions. It controls everything from mud pumps to top drive, hydraulics. It controls everything.

For three to four months we’ve had problems with this computer simply locking up. [sometimes it was a blue screen, sometimes a frozen display] … We had ordered replacement hard drives from the manufacturer. We had actually ordered an entire new system, new computers, new servers, new everything to upgrade it from the very obsolete operating system that it was using. Those computers were actually using Windows NT, which is a very unstable platform to begin with.

Between the manufacturer and the rig, they could not get the bugs worked out of the new operating system. They couldn’t get the old software to run correctly on the new operating system. Our sister rig, the NAUTILUS, was going through those growing pains kind of for us. We had already ordered all the equipment. We were just waiting on them to figure it all out so that we could copy their learnings and make it work on our rig.

Meanwhile, we were limping along with what we had. We had ordered new hard drives. They came in. We replaced the images on the hard drives for the software imaging, got them back running, the chair would run for two, three days, and they would crash again. … I can’t tell you how many hours or days he [electrical supervisor, Tommy Daniels] spent focused entirely on getting these chairs resolved. … He was still working towards that up until the time of the explosion. It had not been resolved.

In the same discussion, Mr. Williams attributes the blowout to the failure of this system by referencing a previous incident.

[in another accident] It was internally discussed that the chair crashing caused the kick, because they lost all — They lost all communications to the drill package. They had no way to monitor anything for several seconds, and before they could get the B Chair up, they had taken a kick.

On pages 103 and 104, he also describes how a “blue screen of death” could lead to a “kick” while waiting for the backup system to boot and be informed by “servers”. Operators complained about this loss of control every day and it happened at all hours of the day and night.

It should be noted that the problem with the alarms was not the sensors but it could have been viruses. Mr. Williams describes how he made sure all of those were working properly on pages 66 and 68 to 70. On page 77, Williams says, “The chairs themselves were completely independent and isolated from the entire rig network, so there was no chance of infection, virus, hacking, there was no opportunity for that.” This tells us that the rest of the network had problems that might have been carried to the control system via physical media, like USB drives or floppies.

Non free software left BP engineers in the field divided and helpless. On page 102, Mr. Williams tells us, “There was no fixing bad software. We could simply manage it, try to keep it running.” So, BP’s management was told that all they could do was as the vendor says. Money and resources were being spent to fix the problems but they were wasted. When the vendor’s software failed, BP was stuck begging for more from a system that had to be bypassed.

Mr. Williams describes the general alarm, its inhibition and consequences starting on page 30. The whole rig was blind to real danger.

.

You have four states of alarms. You have a normal operating condition, you have an inhibited condition, which simply means that the sensory is active, it is sensing, and it will alarm and it will give the information to the computer but the computer will not trigger an alarm for it. It will give you the indication, but it won’t trigger the actual alarm. [other states described] …

there are several toxic and combustible gas sensors located in key areas, mainly around the drilling package. … When you get two detectors to go into a high state in one zone, what is supposed to happen is the ESD for that zone should trip, which is your emergency shutdowns [designed to prevent explosions], and you should also sound the generator alarm.

The general alarm is set up to inform the entire rig of any of three conditions. … Each one of those conditions has a distinct tone and a distinct visual light. We have light columns throughout the rig. One red — Within the column there’s a red, a yellow, and a blue, with the red being fire, yellow being toxic, blue being combustible. So you get an audio tone and a visual tone with every general alarm. [none of these were used in the accident because the computer was set so general alarms had to be triggered manually. As we will see, they failed to do this.]

… When I discovered it was inhibited about a year ago, I inquired as to why it was inhibited, and the explanation I got was that they — from the OIM down, they did not want people woke up at 3:00 o’clock in the morning due to false alarms.

On pages 40 and 41 we see that Emergency Shut Downs had been set to bypass because the system shut panels down frequently over false alarms. This left everyone at risk of explosion.

On page 37, Mr. Williams drops another bombshell, that the same system may have destroyed the blow out preventer without human input. A reasonable system would inhibit motion, even human directed motion, that would destroy itself. What they had left them wondering about everything.

it took me a few days to understand or to formulate why we were getting chunks of [annular] rubber back. There was an incident prior to that where we were in testing mode and the annular was closed around the drill pipe. I got a call from the night-time toolpusher to come investigate whether or not there was an input to the stick to hoist the block while the annular was closed, and I inquired as to why he needed to know that. He said, “Well, the block moved about 15 or 20 feet. We need to know why. We need to know if it was inadvertent stick movement or if it went up by itself.” [an informal investigation] got into the chair log data and dissected the data. What we determined was one of the sticks was moved in the positive direction. What we could not definitively determine was which stick. The tag system inside the log was not accurate enough. It simply said, “Joystick A, Joystick B,” …

All the logs prove to me is that the computer thought someone pushed the joystick. The signal was erroneous and might also have been spurious.

The most dreadful immediate consequence of all of this was that eleven men died in an explosion and fire. New testimony shows a situation that a more reasonable system should have been able to react to and save the day. The blow out preventer should never have been damaged. Alarms should have sounded, so people could escape. Panels and generator should have been shut down to prevent an explosion. What actually happened? David Hammer of the Times Picayune tells us.

Andrea Fleytas said she felt the rig jolt that evening and saw more than 10 magenta lights flash on her screen notifying her that the highest level of combustible gas had entered the rig’s shaker house and drill shack, critical areas where the rig’s drilling team was at work. … she was trained to sound a general alarm any time more than one indicator light flashed, but didn’t do so immediately in this case because she had never been trained to deal with such an overwhelming number of warnings. … she eventually “went over and hit the alarms” after the first or two large explosions.

[before pushing the alarms] Fleytas received a telephone call from crew members on the drill floor who said they were fighting a kick of gas and oil in the well; she took another call from the engine control room asking what was happening and she told them they were having a well control problem; and she continued to hit buttons on her console acknowledging the multiple gas alarms popping up in various sectors of the rig. … A few seconds after she got off the telephone with the engine room, there was a blackout on the rig. A few seconds after that, the first explosion rang out, Fleytas testified. It was then that she sounded the general alarm.

Keplinger said in his own testimony that it was after the explosion when he first “noticed a lot of gas in there and called” the shaker house to try to get whoever may have been there out, but nobody answered the phone.

Fleytas said she knew of no protocols for activating the emergency shutdown and no one activated it. Gas likely ignited in the drilling area, killing everyone there, and also caused the two active engines to rev so high that all power on the rig was lost, preventing fire pumps from working and keeping the rig from moving away from the spewing well.

Microsoft failure did not end when the rig sank. Those trying to fix things were also burdened with second rate software.

Since then, people from Texas to Florida have been sickened and harmed by the spill. Toxic levels of dispersant have shown up in people’s private pools, the beaches are contaminated with about 200 ppm of oil, oysters, crabs and shrimp have even more. The oil made its way into people’s blood. If the big spill in Mexico is a guide, the spill will linger for decades [2].

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. RecogniCorp v Nintendo is Another Nail in the Coffin of Software Patents in the United States

    A precedential new decision against software patents is terrible news for the patent microcosm -- something for them to spin or moan about for a long time to come



  2. Battistelli is Busy Securing the Vote of Countries Whose Support and Tickets Are Easy to 'Buy'

    Battistelli’s banana republic politics and tricks are viewed as his ticket to endless ‘leadership’ (domination by sheer force) of a sinking patent office, whose rules he repeatedly breaks (including lack of eligibility to run it, for multiple reasons)



  3. Patent Snake Oil From Brunel University London and PatentDive

    The ludicrous notion of replacing patent examiners (or searches by humans) with machines is seriously considered by some who should know better... but don't



  4. This is How 'Independent' the Boards of Appeal Are Under Battistelli

    A rather revealing new factoid about the interview that never happened (potentially contradicting a previous one with Battistelli), or why it did not happen



  5. Links 29/4/2017: Endless OS, Pinebook, and New Mozilla Foundation Board Members

    Links for the day



  6. Links 28/4/2017: Subsurface 4.6.4, GNOME Shell & Mutter 3.25.1

    Links for the day



  7. Kather Augenstein and Bristows Shift Attention to Germany in an Effort to Ram the Dying UPC Down Everyone's Throats

    Down the throat, hopes Team UPC, the Unitary Patent system will go, even though Britain cannot ratify, throwing the whole thing into grave uncertainty



  8. United for Patent Reform Defends USPTO Director Michelle Lee From Attacks by the Patent Microcosm

    Michelle Lee is finally (if not belatedly) shielded by a bunch of large technology companies; The deep-pocketed industry finally steps in line with our position, which is usually when things turn out the way we advocate for



  9. Team UPC and CIPA Are Lobbying, Publishing Puff Pieces, and Rewriting the Law for Unitary Patent (UPC) Behind Closed Doors

    A collection of the latest news and views on the UPC, which is being lied about by those who stand to benefit from it and is probably going nowhere because Brexit means that the UK stays out, in which case it must be reset and pertinent ratifications done all over again



  10. China's Suffering From Patent Maximalism Has Europe Forewarned

    The parasitic elements inside China -- those that just want lots of litigation (even if from patent trolls) -- are winning over, much to the detriment of the Chinese economy, and Team UPC threatens to do the same in Europe with help from Battistelli



  11. Links 27/4/2017: Mesa 17.0.5 RC1, Git 2.13.0 RC1, and Linkerd 1.0

    Links for the day



  12. The Latest Expensive PR Blitz of the EPO, Led by Jana Mittermaier and Rainer Osterwalder Under the 'European Inventor Award' Banner

    The PR agencies of the Corsican in Chief, who appears to be buying political support rather than earning any, are very busy this week, as yet another reputation laundering campaign kicks off



  13. Links 26/4/2017: SMPlayer 17.4.2, Libreboot Wants to Rejoin GNU

    Links for the day



  14. PatentShield is Not the Solution and It Won't Protect Google/Android From Patent Trolls Like Microsoft's

    A new initiative called "PatentShield" is launched, but it's yet another one of those many initiatives (Peer-to-Patent and the likes of it, LOT Network, OIN, PAX etc.) that serve to distract from the real and much simpler solutions



  15. Patent Quality Crisis and Unprecedented Trouble at the European Patent Office (EPO) Negatively Affect Legitimate Companies in the US As Well

    The granting en masse of questionable patents by the EPO (patent maximalism) is becoming a liability and growing risk to companies which operate not only in Europe but also elsewhere



  16. Blog 'Takeovers' by Bristows and Then Censorship: Now This Firm Lies About the Unitary Patent (UPC) and Then Deletes Comments That Point Out the Errors

    Not only are Bristows employees grabbing the mic in various high-profile IP blogs for the purpose of UPC promotion (by distortion of facts); they also actively suppress critics of the UPC



  17. Links 25/4/2017: Kali Linux 2017.1 Released, NSA Back Doors in Windows Cause Chaos

    Links for the day



  18. Astoundingly, IP Kat Has Become a Leading Source of UPC and Battistelli Propaganda

    The pro-UPC outlets, which enjoy EPO budget (i.e. stakeholders' money), are becoming mere amplifiers of Benoît Battistelli and his right-hand UPC woman Margot Fröhlinger, irrespective of actual facts



  19. EPO Fiasco to be Discussed in German Local Authority (Bavarian Parliament) Some Time Today as the Institution Continues Its Avoidable Collapse

    Conflict between management and staff -- a result of truly destructive strategies and violations of the law by Benoît Battistelli -- continues to escalate and threatens to altogether dismantle the European Patent Office (EPO)



  20. In the US and Elsewhere, Qualcomm's Software Patents Are a Significant Tax Everyone Must Pay

    The state of the mobile market when companies such as Qualcomm, which don't really produce anything, take a large piece of the revenue pie



  21. In South Asia, Old Myths to Promote Patent Maximalism, Courtesy of the Patent Microcosm

    The latest example of software patents advocacy and patent 'parades' in India, as well as something from IPOS in Singapore



  22. Links 24/4/2017: Linux 4.11 RC8, MPV 0.25

    Links for the day



  23. Why Authorities in the Netherlands Need to Strip the EPO of Immunity and Investigate Fire Safety Violations

    How intimidation and crackdown on the staff representatives at the EPO may have led to lack of awareness (and action) about lack of compliance with fire safety standards



  24. Insensitivity at the EPO’s Management – Part IX: Testament to the Fear of an Autocratic Regime

    A return to the crucial observation and a reminder of the fact that at the EPO it takes great courage to say the truth nowadays



  25. For the Fordham Echo Chamber (Patent Maximalism), Judges From the EPO Boards of Appeal Are Not Worth Entertaining

    In an event steered if not stuffed by patent radicals such as Bristows and Microsoft (abusive, serial litigators) there are no balanced panels or even reasonable discussions



  26. EPO Staff Representatives Fired Using “Disciplinary Committee That Was Improperly Composed” as Per ILO's Decision

    The Board of the Administrative Council at European Patent Organisation is being informed of the union-busting activities of Battistelli -- activities that are both illegal (as per national and international standards) and are detrimental to the Organisation



  27. Links 23/4/2017: End of arkOS, Collabora Office 5.3 Released

    Links for the day



  28. Intellectual Discovery and Microsoft Feed Patent Trolls Like Intellectual Ventures Which Then Strategically Attack Rivals

    Like a swarm of blood-sucking bats, patent trolls prey on affluent companies that derive their wealth from GNU/Linux and freedom-respecting software (Free/libre software)



  29. The European Patent Office Has Just Killed a Cat (or Skinned a 'Kat')

    The EPO’s attack on the media, including us, resulted in a stream of misinformation and puff pieces about the EPO and UPC, putting at risk not just European democracy but also corrupting the European press



  30. Yann Ménière Resorts to Buzzwords to Recklessly Promote Floods of Patents, Dooming the EPO Amid Decline in Patent Applications

    Battistelli's French Chief Economist is not much of an economist but a patent maximalist toeing the party line of Monsieur Battistelli (lots of easy grants and litigation galore, for UPC hopefuls)


CoPilotCo

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

CoPilotCo

Recent Posts