Hello Peter,
You do not need to update your DoC for every ECO. Your DoC is your declaration to the outside world that you declare your particular product (or several model variations of products) compliant with the EC Directive. If you make a component change (or any other reason for your ECO), yet your model number remains the same as stated on your current DoC, then a new DoC is certainly not required. You would, of course, need to record the effect of the ECO in your technical file, which backs up the DoC and this is where your control should concentrate (i.e. your “internal production control” under the 2004/108/EC). My one-day EMC Goggles training course addresses such issues relating to the EMC Directive, amongst many other aspects of EMC, including a clear understanding of the effects of interference, design for compliance and EMC testing. It’s a complete all-round course with many tips included from my 20 years spent working in EMC. I am giving this course at San Jose, California, on Monday 18th October – that’s just next week! If anyone is interested in attending, or knows of someone within their organisation who needs to be brought up to speed on EMC, please email me separately. There are a few places available. Best Regards, John From: peterh...@aol.com [mailto:peterh...@aol.com] Sent: 11 October 2010 16:38 To: EMC-PSTC@LISTSERV.IEEE.ORG Subject: [PSES] Updating EU DoC Hello group, I am looking to see how you folks generate and update your EU DOC. We use the typical MS Word template and every time there is a need for an update, we update this document and have to go through ECO (Engineering Change Order) since it is a controlled document and I found this process to be very time consuming and not really efficient in particular when you have over 100 DOC's to maintain. Is there any easier way? Is there an automated process out there? Do we really need to have it under control revision? Thank you Peter - ---------------------------------------------------------------- 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.ieeecommunities.org/emc-pstc 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 <emcp...@radiusnorth.net> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher <j.bac...@ieee.org> David Heald <dhe...@gmail.com> -- This message has been scanned for viruses and dangerous content by MailScanner <http://www.mailscanner.info/> , and is believed to be clean. - ---------------------------------------------------------------- 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.ieeecommunities.org/emc-pstc 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 <emcp...@radiusnorth.net> Mike Cantwell <mcantw...@ieee.org> For policy questions, send mail to: Jim Bacher <j.bac...@ieee.org> David Heald <dhe...@gmail.com>
