I agree with Dave.  I would not include the adapter on your DoC for your end 
product.  However, your test reports/technical file should state what adapter 
is used for end product compliance.  And instructions/information to the user 
should state that the product must only be used with the adapter provided.

Jim Hulbert

From: Nyffenegger, Dave [mailto:[email protected]]
Sent: Wednesday, September 05, 2018 12:22 AM
To: [email protected]
Subject: **External**Re: [PSES] DoC - 3rd party device to be included?

This email originated from outside the organization. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.


Amund,

I’d think (since your product conformance is only valid with specific adapter) 
your adapter must be included with your product when doing all the applicable 
testing to harmonized standards and in the technical file as a critical 
component and therefore would be inherently included in your DoC.  But it 
wouldn’t be separately identified on your DoC.  Nor  would I think your DoC 
would simply include the same conformity statements to the directives and 
standards listed on the adapter DoC.

I have seen other products that do not include the adapter in their product 
DoC.  For  example the product DoC would declare to EMC, RED, RoHS but would 
not declare to LVD that would clearly apply to the adapter.  Likely in those 
cases the manufacturer chooses to have the option of using different adapters 
without changing  their product certification.

-Dave

From: Amund Westin [mailto:[email protected]]
Sent: Wednesday, September 05, 2018 12:09 AM
To: [email protected]<mailto:[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]<mailto:[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)<http://www.ieee-pses.org/list.html>
List rules: http://www.ieee-pses.org/listrules.html

For help, send mail to the list administrators:
Scott Douglas <[email protected]<mailto:[email protected]>>
Mike Cantwell <[email protected]<mailto:[email protected]>>

For policy questions, send mail to:
Jim Bacher <[email protected]<mailto:[email protected]>>
David Heald <[email protected]<mailto:[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]<mailto:[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)<http://www.ieee-pses.org/list.html>
List rules: http://www.ieee-pses.org/listrules.html

For help, send mail to the list administrators:
Scott Douglas <[email protected]<mailto:[email protected]>>
Mike Cantwell <[email protected]<mailto:[email protected]>>

For policy questions, send mail to:
Jim Bacher <[email protected]<mailto:[email protected]>>
David Heald <[email protected]<mailto:[email protected]>>

This email message may contain confidential, proprietary and/or privileged 
information. It is intended only for the use of the intended recipient(s). If 
you have received it in error, please immediately advise the sender by reply 
email and then delete this message. No one other than the intended recipient 
may disclose, copy, distribute or use the information contained in this message.




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

Reply via email to