I guess the first place I would look is your current PDM database vendor (e.g. Oracle, SAP) or your PDM front-end vendor (e.g. Agile) to see if their existing offerings do what you want or can be customized to give you what you want.  This would probably be the cleanest approach and keep all your data together without messing around with more vendors than you already have to deal with.  If you have an advanced enough IT department they may have the capability to do some customizing of your PDM system to add data fields and reports.
 
There are vendors that provide RoHS and similar services and databases (e.g. IHS, TotalParts, TUV) but they vary in complexity of exchanging data back and forth between your existing PDM system and their databases and their easiest path is usually using their web-based interface with a subset of your data in the cloud.  Keeping that synced up can be easy or hard depending on your PDM system and local IT expertise.
 
Good luck!
 
-- 
Dan Roman, N.C.E.
VP Communications Services
IEEE Product Safety Engineering Society
 
On 01/06/14, Kunde, Brian wrote:
 

Happy New Year!!!

 

My boss is looking for help and advice. He is in charge of tracking RoHS, Reach, County of Origin, etc. status on all components and assemblies our company deals with. He wonders if there is a Turn-Key software program or database system that is geared toward tracking this kind of information.  He feels to do a “thorough job” with RoHS, he needs to track the composition of every component.

 

Any suggestions? What does your company use? Is my boss making more work for himself than he needs to (he does that)??

 

Thanks in advance.

 

The Other Brian


LECO Corporation Notice:This communication may contain confidential information intended for the named recipient(s) only. If you received this by mistake, please destroy it and notify us of the error. Thank you.
-
----------------------------------------------------------------

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-pstc@ieee.org&GT;

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 <emcpstc@radiusnorth.net&GT;
Mike Cantwell <mcantwell@ieee.org&GT;

For policy questions, send mail to:
Jim Bacher <j.bacher@ieee.org&GT;
David Heald <dheald@gmail.com&GT;

-
----------------------------------------------------------------

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

Reply via email to