Hi Amund, Under your scenario, the AC/DC adapter is just an external power supply of your main unit. Your product is operating on safe level of DC. If you don’t sell the adapter together with the main unit, you may avoid declaring it in your DoC.
If you have to sell your product together with EPS, you have to include it (main unit and do not need to specially mention the ESP) in the DoC. You are unable to avoid the accountability on the components of your product even though you are not manufacturing them. You got the right to find a trusted component and purchase under a commercial contract that is a legally binding agreement. Did you remember Samsung Galaxy Note 7 recall due to rechargeable battery? Samsung purchased the battery from a supplier and ultimately bore the recall consequence. Because the conformance of your product is only valid with that specific adapter, you have to state it in the rating plate and IB. If not, you may have the risks that the user may use the adapter for other purpose and your main unit may be breach with LVD, EMC, etc. in case the user uses other adapter with your main unit. Regards, Scott Sent from Mail for Windows 10 From: Amund Westin Sent: Wednesday, 5 September 2018 12:09 PM To: [email protected] Subject: [PSES] DoC - 3rd party device to be included? We buy AC/DC adapters form a major power supply manufacturer. It has all the papers in place as DoC, CB test reports and CB certificate. This adapter has been used under the EMC, LVD and RED tests of our product. There have been some questions if the adapter should be included in the DoC, because conformance of our product is only valid with that specific adapter. Even though the adapter has its own DoC, I think it is correct to include the adapter in our DoC since both parts are put together on the marked as a combined solution (in the same package). Do we take any unnecessary adapter manufacturer responsibilities by including the adapter type designation on our DoC? Any thoughs? Looked into the Blue Guide, but could not find any discussions about this. BR Amund - ---------------------------------------------------------------- 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://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 <[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://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 <[email protected]> Mike Cantwell <[email protected]> For policy questions, send mail to: Jim Bacher: <[email protected]> David Heald: <[email protected]>
