So where’s an auditor when you need one?
Follow this scenario: You are patronizing a test lab operated by a huge, big-name, prestigious, multi-national corporation. The tech is having trouble getting the custom in-house software to control the test equipment. The tech supervisor then becomes involved. Much watching as the tech keeps entering the control data while the equipment doesn’t quite respond. I ask if I could look at the software operation manual while they are trouble-shooting the setup. The tech supervisor replies “It’s in my head.” Ed Price [email protected] <blocked::mailto:[email protected]> WB6WSN NARTE Certified EMC Engineer Electromagnetic Compatibility Lab Cubic Defense Applications San Diego, CA USA 858-505-2780 Military & Avionics EMC Is Our Specialty From: [email protected] [mailto:[email protected]] On Behalf Of Derek Walton Sent: Monday, January 24, 2011 7:26 PM To: Bob Richards Cc: [email protected] Subject: Re: my last lab audit Hi Folks, I have to take issue with a few things here, because, well, that's what I do.... So, first, an assessor is quite within "his" rights to ask for evidence that software was verified as correctly functioning before being employed in a laboratory. A response such as "Yea, I've done that" doesn't meet MY expectations.... It is generally accepted that the functions of COTS software like excel, or TILE! are exempt from being proven. HOWEVER, user spreadsheets, or test sequences built with such software, is not. If you don't document your verification process, shame on you. Second, An auditors job is not to check every line of code you write, if you have one that is capable of doing that you're lucky. "His" job is to VERIFY that YOU have done what YOU are supposed to do. It's only if you do not follow the published standards paths does an assessor typically dig in deep. Third, I'm not aware of any fellow assessors that are on "POWER TRIPS", quite the contrary. Consider that an assessor has but a short window to learn YOUR way of doing things and ensure you meet the requirements. An assessors opinions and preferences are immaterial ( look at an assessors lip to see how often it's been bitten! ), all that matters, technically, is that you comply. Having assessed over a hindered labs, I am frequently humbled by the talent, intellect, creativity and work ethic of people that I'm to evaluate ( OK, I also admit the opposite is true too ). On many occasion I have left a laboratory thinking.... Wow! Being a lab assessor is a privileged position. Few other people are "welcomed" into a laboratory and allowed to probe the details of their operation. I would hope, and I believe this is the case, that my fellow assessors feel their activities in a laboratory increases the proficiency of the laboratory. This isn't a power trip, it's giving back. Fourth, assessors are not infallible. I believe labs are encouraged to provide feedback on assessors. I reiterate you need to do that: if you don't, you are condoning shoddy work. Fifth, and finally for now, I have often said that everyone in a lab should "play auditor" now and again. It's amazing how much more sympathetic you get when you have walked in the others shoes... I hope someones copying Dilbert, I'd love to see his take on this... Shalom, Derek Walton On 1/24/2011 8:38 PM, Bob Richards wrote: - ---------------------------------------------------------------- This message is from the IEEE Product Safety Engineering Society emc-pstc discussion list. To post a message to the list, send your e-mail to <[email protected]> All emc-pstc postings are archived and searchable on the web at http://product-compliance.oc.ieee.org/ Graphics (in well-used formats), large files, etc. can be posted to that URL. Website: http://www.ieee-pses.org/ Instructions: http://listserv.ieee.org/request/user-guide.html List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher <[email protected]> David Heald <[email protected]>
