Just ensure the updated mandatory Essential Requirements. They are:- CE Marking LVD EMC ErP RoHS Recast WEEE Recast
Regards, Scott On 17/8/12 11:31 PM, "John Cotman" <[email protected]> wrote: > The CE marking process includes mandatory Essential Requirements, (written > into law), which change infrequently, and to support them, voluntary > standards, which are constantly being updated. > > There is nothing in these standards which brings about a cessation of > conformity with Essential Requirements, and therefore nothing which > automatically mandates retesting. The cessation dates are of the Presumption > of conformity, not the conformity itself. After that date, you cannot presume > that you conform, but most of the time, when you analyse the effect of an > amendment, you still will. > > The alternative approach, which would be to write the standards into the law, > would be very much more onerous and inflexible. > > John C > > > > From: Pearson, John [mailto:[email protected]] > Sent: 17 August 2012 15:13 > To: [email protected] > Subject: Re: [PSES] CE Marking Provoqium > > > Hi > > > > For the sake of discussion, I would like to open up for debate the suggestion > the EU process is one of the most unreasonably excessive in the world. > > > > With the exception of China and Brazil this is the one major region that > imposes retrospective recertification costs due to the introduction of new > Safety and EMC standards on an existing design. I would like to suggest that > the dates of cessation of conformity impose a requirement to reassess (test if > necessary depending on the variance to the old standard) which achieves little > and costs manufacturers unnecessarily. > > > > Can we discuss? > > > > Thanks > > > > John > > > > > > John Pearson, Senior Director, Corporate Product Compliance > > Polycom | Singleton Court Business Centre, Wonastow Road Ind. Est., Monmouth, > UK, NP25 5JA | T: +44-(0)1753-723165 | M: +44-(0)7968-064105 > > > > > This communication (including any attachments) may contain privileged or > confidential information of Polycom and is intended for a > specific individual. If you are not the intended recipient, you should delete > this communication, including any attachments without > reading or saving them in any manner and you are hereby notified that any > disclosure, copying, or distribution of this communication, > or the taking of any action based on it, is strictly prohibited. > > > > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Sykes, Bob > Sent: 17 August 2012 14:11 > To: [email protected] > Subject: RE: [PSES] EC vs EU suffix > > > > CE = Check Everything or Compliance Expensive.... > > > > ...It's Friday > > > > -Bob > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > <mailto:%5bmailto:[email protected]%5d> On Behalf Of Sundstrom, Michael > > Sent: Friday, August 17, 2012 8:45 AM > > To: Crane, Lauren; [email protected] > > Subject: RE: [PSES] EC vs EU suffix > > > > And here all these years I thought it meant: Compliance Extraordinary... > > > > > > Michael Sundstrom > > OHD TREQ Dallas > > Electronic Lab Analyst EMC Lead > > (214) 579 6312 office > > (940) 390 3644 cell > > KB5UKT > > > > -----Original Message----- > > From: Crane, Lauren [mailto:[email protected]] > <mailto:%5bmailto:[email protected]%5d> > > Sent: Thursday, August 16, 2012 4:50 PM > > To: [email protected] > > Subject: Re: [PSES] EC vs EU suffix > > > > The CE marking remains the same. > > > > The meaning is 'Caveat Emptor' ;-) > > > > Regards, > > Lauren Crane > > KLA-Tencor > > -----Original Message----- > > From: Brian Oconnell [mailto:[email protected]] > <mailto:%5bmailto:[email protected]%5d> > > Sent: Thursday, August 16, 2012 2:44 PM > > To: [email protected] > > Subject: Re: [PSES] EC vs EU suffix > > > > Conformité Européenne > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > <mailto:%5bmailto:[email protected]%5d> On Behalf Of Doug Powell > > Sent: Thursday, August 16, 2012 2:30 PM > > To: [email protected] > > Cc: [email protected] > > Subject: Re: [PSES] EC vs EU suffix > > > > > > And the "CE" mark, what happens to it? > > > > CE = Communauté Européenne > > > > -- > > Thanks, -doug > > > > Douglas E Powell > > [email protected] > > http://www.linkedin.com/in/dougp01 > > > > > > > > On 8/16/12, [email protected] <[email protected]> wrote: > >> > EU = European Union > >> > EC = European Community > >> > > >> > The Treaty of Lisbon which came into force in in December 2009 > >> > provided > > for > >> > the absorption of the entity known as the European Community by the > >> > European Union. > >> > > >> > Regards > >> > > >> > Peter. > >> > > >> > From: [email protected] [mailto:[email protected]] >> <mailto:%5bmailto:[email protected]%5d> On Behalf Of Scott > >> > Xe > >> > Sent: 16 August 2012 15:37 > >> > To: [email protected] > >> > Subject: EC vs EU suffix > >> > > >> > The EU regulations/decisions/directives published after 2010 have a > >> > suffix of EU rather than EC. Is there any particular reason for this >> change? > >> > > >> > Scott > > > > - > > ---------------------------------------------------------------- > > 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]> > > > > - > > ---------------------------------------------------------------- > > 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]> > > > > - > > ---------------------------------------------------------------- > > 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]> > > > > > > Please be advised that this email may contain confidential information. If > you are not the intended recipient, please notify us by email by replying to > the sender and delete this message. The sender disclaims that the content of > this email constitutes an offer to enter into, or the acceptance of, any > agreement; provided that the foregoing does not invalidate the binding effect > of any digital or other electronic reproduction of a manual signature that is > included in any attachment. > > > > - > > ---------------------------------------------------------------- > > 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]> > > > - > ---------------------------------------------------------------- > > 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]> > - > ---------------------------------------------------------------- > > 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]> > - ---------------------------------------------------------------- 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]>
