<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/platform.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d7964919\x26blogName\x3dBill+And+Dave+Are+Dead\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://billanddave.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://billanddave.blogspot.com/\x26vt\x3d4370529864444180878', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Saturday, December 25, 2004

Catch 22 Part Two

I was and still am confident we built good units the whole time. When the new written procedures finally hit the production floor, they were already outdated. They appeared to be even older than the LRIP3 documentation we were previously working off of. So as far as accuracy was concerned the LRIP3 paperwork was more valid. They had to go back and re-update all of the LRIP4 procedures to make them look just like the LRIP3 stuff. To me this seemed like it would be a really easy job, all they had to do was practically cut and paste. But in some cases this took these losers weeks, even months. The document control department at TDS is seriously lacking.

New procedures as they are released need to be rewritten to bring them up to date. Since February I am finding things in the documents that are too vague, items that were completely omitted, or just plain incorrect. Every time I find one that's jacked up I send it back. Manufacturing continues throughout all of this mayhem even though Richard ordered us to stop production as these situations arise.

What really angers me about all this is no one in management cares that the procedures are first and foremost a training resource for all of us factory peasants. All they are focused on is being able to show some Government auditor that revision letter B is on the traveler and on the corresponding procedure. I doubt any of them care what the procedure actually says, really. Most of the documentation is so poorly written that after reading one you would not be able to perform the job. You have to rely on the experience of others to get the information you need to perform the work properly. This isn't the way things should be. The written instructions should be so good that if you had to, you could read them and then do the job without any assistance from a trainer. The whole situation is so frustrating to me.

So many copies of procedures have flooded into the Closed Area that another problem arose almost instantly. How do you know the copy of the procedure you have in your hand is the most updated version? You don't. Master lists of the documentation showing each current revision that should be on the shop floor haven't been created. Just until two weeks ago we had four binders full of the exact same test procedure. In one example I went to find a copy of a particular test procedure and I came up with five different versions of how to do the job. So which one was I supposed to use?

0 Comments:

Post a Comment

<< Home