FWIW, I was always deeply skeptical of the “(Pass, Fail, N/A)” criteria in the TRF’s because those were, and generally still are, almost totally dependent on “the eye of the beholder”, i.e. whoever does the compliance assessment! An (absolutely terrible!) example of that was what I found (in a company for which I worked relatively recently) where a previous occupant of my job had stated that risk assessments were “N/A” to 61010-1 compliance assessments L.
And that, I am fairly convinced, is probably unfortunately still relatively true in quite a few test houses – and so is it not surprising that many company engineers take the same approach because they don’t/can’t understand the obscure and varied nuances of the standards (and those are many and various L) and so take the “easy route” to completing their reports. OTOH, I never did – and that rarely made me “popular” with my (and there were many L) managers L L. John E Allen W. London, UK From: John Woodgate [mailto:j...@woodjohn.uk] Sent: 14 December 2018 21:26 To: EMC-PSTC@LISTSERV.IEEE.ORG Subject: Re: [PSES] TRF Verdicts You appear to have uncovered a significantly unsatisfactory situation, where essential terminology is lacking formal definitions. TRFs are the responsibility of a branch of IEC, called IECEE (https://www.iecee.org/). I think that representations have to be made to IECEE to remedy this situation, as a matter of urgency. Best wishes John Woodgate OOO-Own Opinions Only J M Woodgate and Associates www.woodjohn.uk Rayleigh, Essex UK On 2018-12-14 21:03, Doug Powell wrote: I downloaded and searched for this terminology in all the OD documents available as well as "AD" documents, including all past revisions I could locate. Some 300+ documents. To set the stage, I always think of type testing as being an exercise in "cause and effect". That is, some defect (cause) potentially results in a hazard (effect). Saying there is a deficiency, fault or even failure has not identified a hazard. Here is what I found (or didn't find). "Fault" generally occurs in context of a device failure, fault condition or control fault. This seems to me like a condition of the equipment, not a verdict as such. Not a very satisfactory usage. "Deficiency" or "Deficient" do not occur anywhere. Also unsatisfactory... I also searched the IEC Electrotechnical Dictionary: "Fault" appears several times in Area 192 "Dependability", none of which are specifically referre3d to as a verdict or outcome of type testing. - ---------------------------------------------------------------- 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 <emc-p...@ieee.org> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) <http://www.ieee-pses.org/list.html> List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <sdoug...@ieee.org> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher <j.bac...@ieee.org> David Heald <dhe...@gmail.com> - ---------------------------------------------------------------- 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 <emc-p...@ieee.org> All emc-pstc postings are archived and searchable on the web at: http://www.ieee-pses.org/emc-pstc.html Attachments are not permitted but the IEEE PSES Online Communities site at http://product-compliance.oc.ieee.org/ can be used for graphics (in well-used formats), large files, etc. Website: http://www.ieee-pses.org/ Instructions: http://www.ieee-pses.org/list.html (including how to unsubscribe) List rules: http://www.ieee-pses.org/listrules.html For help, send mail to the list administrators: Scott Douglas <sdoug...@ieee.org> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher: <j.bac...@ieee.org> David Heald: <dhe...@gmail.com>
