Hi John:

No comparison for IEC 60065.

Unfortunately, Ecma TC12 membership is dropping, so we don't
have resources to do the work.  And, TC12 should update the
existing document to the second edition of IEC 62368-1.

Let me know if you know anyone who would wish to join TC12
and help do the work!


Best regards,
Rich


On 2/25/2013 12:05 PM, Tyra, John wrote:
Thanks Rich,

Much appreciated.

Is there a similar dedicated document comparison for IEC60065 available?

Regards,

John

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Richard Nute
Sent: Monday, February 25, 2013 2:45 PM
To: EMC-PSTC
Cc: Thomas M Burke
Subject: Ecma TR-106 available

Posted on behalf of Tom Burke, UL:


More good news for those seeking to learn more about IEC 62368-1 as the ICT 
Industry prepares for the eventual transition from IEC 60950-1 (and IEC 60065) 
to IEC 62368-1. ECMA International, previously known as the European Computer 
Manufacturers Association, has just published its Technical Report TR/106, 
which provides guidance and comparison between
60950-1 and 62368-1. The report was published by ECMA's TC12 on Product Safety, 
and the effort to develop and publish the TR was very capably led by Mr. 
Richard Nute. Thank you Rich and members of ECMA TC12! ECMA has a strong 
interest in IEC 62368-1 since its industry standard,
ECMA-287 "Safety of electronic equipment," which was developed and published in 
the 1990s and which first introduced hazard-based concepts, was the core material that 
IEC TC108 used when it began it project developing IEC 62368-1 in 2002. It is believed 
that the availability of comparison documents like TR/106 from a variety of sources helps 
industry prepare for the pending transition and also helps clear up some of the 
misconceptions about the new standard. As has been discussed in this group previously, 
IEC 62368-1 has many familiar elements from 60950-1, including allowance for prescriptive 
constructions that have proven safe in 60950-1 and that may be used as an alternative to 
some of the performance based requirements in 62368-1. Provided below are links to 
information on ECMA TC12 and the TR/106 (available free of charge).

http://www.ecma-international.org/memento/TC12.htm

http://www.ecma-international.org/publications/techreports/E-TR-106.htm";


Best regards,
Rich

-
----------------------------------------------------------------
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]>

Reply via email to