The 787 Scenario: How Data Can Solve Epic Messes



The 787 Dreamliner Scenario: How Data Can Solve Epic Messes (via slashdot)

Following reports of battery failures onboard Boeing’s 787 Dreamliner, the Federal Aviation Administration (FAA) has issued an “emergency airworthiness directive” temporarily grounding the airliners. That’s supremely bad news for Boeing, which poured millions of dollars into the 787’s development…



About nick kolakowski

Nick Kolakowski is a senior editor at Slashdot. His work has appeared in The Washington Post, McSweeney’s, Playboy, WebMD, Trader Monthly, Carrier Pigeon, and other venues. He is the author of "How to Become an Intellectual" (Adams Media, 2012), a work of comedic nonfiction.

Comments

  1. BY Fred Bosick says:

    “And at the moment, Boeing has a big data job on its hands…”

    No, they have an outsourcing problem! Big data wouldn’t even be a contemplated fix if they had used the institutional data already held by US based suppliers, and unionized labor in Everett, WA.

    It’s not just batteries, there are occasional fuel leaks. Probably from inexperienced assemblers who don’t know that just because the parts fit in the CAD files doesn’t mean they will when you start to bend and fasten metal.

    Many of us in IT know outsourcing is a problem. But managers don’t care as long as their bonuses come in. What happens when an airplane falls out of the sky?

    • BY Mark Feffer says:

      Fred, I think what you’re saying is a red herring. What this story is really about is how Boeing and General Electric, American companies, are using data in more intensive ways. Seems to me that you’re making some generalizations here based on speculation. The fuel leaks, from what I’ve read, have been traced to a valve failure – not an assembly failure. The unit’s manufacturer is in the UK.

Post a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>