4 responses to “Catching Errors”

  1. Fluxor

    Intermittent failure on a tiny minority of parts is what has kept me busy the last month. Customers aren’t happy. We’re not happy. Hinsight’s 20/20. Maybe we could have caught this problem beforehand. Maybe not. Production is such a bitch.

  2. GEARS

    Sure, this kinda stuff happens all of the time and it takes a few million (in the VW case) to fix. But I’m going to take a shot a Civil Engineering for second here. Why does every construction project run years over planning and 10’s of millions over budget? It’s the same sorta thing that Fluxor just said, “Maybe we should have [budgeted] that beforehand”.

    I tend to laugh at the VW case but shake my head in shame at the CE project woes.

    1. FrauTech

      True but there’s also the F-35 running years behind and hundreds of millions overbudget (that US tax payers are paying for) not sure any one industry has the lead on poor planning.

  3. Ron Amundson

    In this case, I wonder if it part of it is do to a change in focus. Ie for years, the key locking mechanism was the primary method of theft deterrence, and thus a wealth of historical data was used to generate the qualification/verfication processes. As theft deterrence moved from mechanical ie tumblers etc to any number of RFID processes I’m guessing the qualification process likewise changed. I’m sure there was is a continuous push to save time by shifting the focus from the historical knowns (the mechanicals) to the unknown (RFID)…then add in shifting design and qualification of such modules more and more to the vendor, events such as these are not unexpected.