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: I don't mind most audits. It is an opportunity to improve and to learn, and I have met several auditors that are very good in this respect. However, I know one auditor that was definitely on a power trip during an audit. Two of the labs I have worked for have forbid him from setting foot on their property due to his conduct during audits. There is one thing I think is interesting about audits. You can beg and scream for months that you need a particular piece of equipment to better perform your job - sometimes to no avail. But, if an auditor says you need it, it gets bought rather quickly. :-) Bob R. --- On Mon, 1/24/11, Doug Kramer <[email protected]> <mailto:[email protected]> wrote: From: Doug Kramer <[email protected]> <mailto:[email protected]> Subject: RE: my last lab audit To: "[email protected]" <mailto:[email protected]> <[email protected]> <mailto:[email protected]> Date: Monday, January 24, 2011, 4:49 PM Larry, Well stated, except for the power trip comment. -Doug -----Original Message----- From: [email protected] <http://us.mc1 .mail.yahoo.com/mc/[email protected]> [mailto:[email protected] <http://us.mc11.mail.yahoo.com/mc/[email protected]> ] On Behalf Of Larry Stillings Sent: Monday, January 24, 2011 2:37 PM To: '[email protected] <http:// s.mc11.mail.yahoo.com/mc/[email protected]> '; [email protected] <http://us.m 11.mail.yahoo.com/mc/[email protected]> Subject: RE: my last lab audit Brian, Hire a new auditor. I know, easier said then done. I lot of them are on a power trip, that's why they are auditors. Basically, you need to contact whomever runs your particular accreditation body and talk to them. Remember you are a paying customer, and have options to whom your choose for your audits. Larry -----Original Message----- From: Brian O'Connell [mailto:[email protected] <http://us.mc11.mail.yahoo.com/mc/[email protected]> ] Sent: Monday, January 24, 2011 3:31 PM To: [email protected] <http:/ us.mc11.mail.yahoo.com/mc/[email protected]> Subject: my last lab audit auditor: Your software does not meet 17025 - no test data. me: 'That' software is only for a windoze HMI, no data being collected, no data being analyzed, no data processed. auditor: But it displays test parameters. me: There are no reports or design decisions or TRFs being made from this displayed data. Instruments are calibrated and tracible, and the program that acquires and processes the data is subject to audit and a regression series for each rev. Here is the last CIG which included all test driver software. auditor: I want to see the 17025-based tests for 'this' software. me: Here is my test data (hand auditor the HMI source code). auditor: What am I supposed to do with this? I do not know anything about programming. Brian - ---------------------------------------------------------------- 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] <http://us.mc11.mai .yahoo.com/mc/[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] <http://us.mc11.mail.yahoo.com/mc/[email protected]> > Mike Cantwell <[email protected] <htt ://us.mc11.mail.yahoo.com/mc/[email protected]> > For policy questions, send mail to: Jim Bacher: <[email protected] <http: /us.mc11.mail.yahoo.com/mc/[email protected]> > David Heald: <[email protected] <http:/ us.mc11.mail.yahoo.com/mc/[email protected]> > - ---------------------------------------------------------------- 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] <http://us.mc11.mail yahoo.com/mc/[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] <http://us.mc11.mail.yahoo.com/mc/[email protected]> > Mike Cantwell <[email protected] <htt ://us.mc11.mail.yahoo.com/mc/[email protected]> > For policy questions, send mail to: Jim Bacher: <[email protected] <http: /us.mc11.mail.yahoo.com/mc/[email protected]> > David Heald: <[email protected] <http:/ us.mc11.mail.yahoo.com/mc/[email protected]> > - ---------------------------------------------------------------- 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] <http://us.mc11.mail yahoo.com/mc/[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] <http://us.mc11.mail.yahoo.com/mc/[email protected]> > Mike Cantwell <[email protected] <htt ://us.mc11.mail.yahoo.com/mc/[email protected]> > For policy questions, send mail to: Jim Bacher: <[email protected] <http: /us.mc11.mail.yahoo.com/mc/[email protected]> > David Heald: <[email protected] <http:/ us.mc11.mail.yahoo.com/mc/[email protected]> > - ---------------------------------------------------------------- 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]> - ---------------------------------------------------------------- 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]>
