In message
<[email protected]>,
dated Thu, 11 Jul 2013, Charlie Blackham <[email protected]>
writes:
One approach that is taken is to have someone with responsibility for
EMC/approvals review all Engineering Change Notes prior to release.
This is more or less a requirement of the Directive. I sent my previous
post before I'd finished it properly:
Seriously, whoever is responsible for compliance should document all
changes that might affect EMC; that better be the Technical Director,
not the tame EMC expert, who doesn't have enough clout to prevent
changes being 'forgotten' or not documented and acted on.
--
OOO - Own Opinions Only. See www.jmwa.demon.co.uk
Why is the stapler always empty just when you want it?
John Woodgate, J M Woodgate and Associates, Rayleigh, Essex UK
-
----------------------------------------------------------------
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://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://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]>
