Re: Regulatory General Discussion : ouput of Compliance group
I read in !emc-pstc that Andre, Pierre-Marie wrote (in <9985493A802AD5118C4E0090274627535EC2EE @swsmsx34.isw.intel.com>) about 'Regulatory General Discussion : ouput of Compliance group', on Mon, 17 Dec 2001: >The good argument is really in the FULL implication of the Compliance group >in the design process right ? with full power to sign off the design changes IMHO, the European EMC and Low Voltage Directives effectively require this to be the case. -- Regards, John Woodgate, OOO - Own Opinions Only. http://www.jmwa.demon.co.uk After swimming across the Hellespont, I felt like a Hero. --- This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ To cancel your subscription, send mail to: majord...@ieee.org with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Michael Garretson:pstc_ad...@garretson.org Dave Healddavehe...@mediaone.net For policy questions, send mail to: Richard Nute: ri...@ieee.org Jim Bacher: j.bac...@ieee.org All emc-pstc postings are archived and searchable on the web at: No longer online until our new server is brought online and the old messages are imported into the new server.
RE: Regulatory General Discussion : ouput of Compliance group
Doug, thanks you for your inputs. The good argument is really in the FULL implication of the Compliance group in the design process right ? with full power to sign off the design changes best regards to all compliance engineers Pierre-Marie Andre Senior Approval Engineer -Original Message- From: Doug McKean [mailto:dmck...@auspex.com] Sent: samedi 15 décembre 2001 01:26 To: EMC-PSTC Discussion Group Subject: Re: Regulatory General Discussion : ouput of Compliance group "Andre, Pierre-Marie" wrote: > > So has anybody some thoughts or argument on the measurement > or evaluation of an Compliance Group ? Well, I'd hate to let the dirty little secret out of the bag for those of us who would fall under such and evaluation. Important in such an evaluation would be that the company has allowed the compliance engineer to have significant input to the design/mfring processes. I've been in companies where evaluations from the compliance engineer amounted to nothing more than a suggestion. Very frustrating. Other places had the compliance engineer greatly involved as a signatory in product release and with ECR/ECOs. Start with an ideal world where the compliance engineer has complete planning, budgeting, signatory/approval powers with the complete product cycle from prototype-to-product release-to product obsolescence. Consider that as the complete model. Then, as the person has less and less involvement/approval power in those areas, they are thus less responsible for them and thus, they are not to be evaluated in those areas. You'll probably find the typical compliance engineer ends up in reality scheduling tests w/no approval powers, has input to ECR/ECOs but no signatory powers, inputs into product design by way of memos, sometimes are the last to know about significant design changes, and might answer to someone who knows little about compliance engineering. IMO, evaluation would be difficult. Regards, Doug McKean --- This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ To cancel your subscription, send mail to: majord...@ieee.org with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Michael Garretson:pstc_ad...@garretson.org Dave Healddavehe...@mediaone.net For policy questions, send mail to: Richard Nute: ri...@ieee.org Jim Bacher: j.bac...@ieee.org All emc-pstc postings are archived and searchable on the web at: No longer online until our new server is brought online and the old messages are imported into the new server. --- This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ To cancel your subscription, send mail to: majord...@ieee.org with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Michael Garretson:pstc_ad...@garretson.org Dave Healddavehe...@mediaone.net For policy questions, send mail to: Richard Nute: ri...@ieee.org Jim Bacher: j.bac...@ieee.org All emc-pstc postings are archived and searchable on the web at: No longer online until our new server is brought online and the old messages are imported into the new server.
Re: Regulatory General Discussion : ouput of Compliance group
Doug, You've described the poles-apart situations of regulatory compliance very well. I've worked in both types of situations, and can say that my contribution and worth to the company in the first example far exceeds anything that can be achieved in a company of your last example. I've felt underused and undervalued, and made haste to find another job. "Educating" management just did not work when they have their minds set otherwise. taniagr...@msn.com - Original Message - From: Doug McKean Sent: Friday, December 14, 2001 4:59 PM To: EMC-PSTC Discussion Group Subject: Re: Regulatory General Discussion : ouput of Compliance group "Andre, Pierre-Marie" wrote: > > So has anybody some thoughts or argument on the measurement > or evaluation of an Compliance Group ? Well, I'd hate to let the dirty little secret out of the bag for those of us who would fall under such and evaluation. Important in such an evaluation would be that the company has allowed the compliance engineer to have significant input to the design/mfring processes. I've been in companies where evaluations from the compliance engineer amounted to nothing more than a suggestion. Very frustrating. Other places had the compliance engineer greatly involved as a signatory in product release and with ECR/ECOs. Start with an ideal world where the compliance engineer has complete planning, budgeting, signatory/approval powers with the complete product cycle from prototype-to-product release-to product obsolescence. Consider that as the complete model. Then, as the person has less and less involvement/approval power in those areas, they are thus less responsible for them and thus, they are not to be evaluated in those areas. You'll probably find the typical compliance engineer ends up in reality scheduling tests w/no approval powers, has input to ECR/ECOs but no signatory powers, inputs into product design by way of memos, sometimes are the last to know about significant design changes, and might answer to someone who knows little about compliance engineering. IMO, evaluation would be difficult. Regards, Doug McKean --- This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ To cancel your subscription, send mail to: majord...@ieee.org with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Michael Garretson:pstc_ad...@garretson.org Dave Healddavehe...@mediaone.net For policy questions, send mail to: Richard Nute: ri...@ieee.org Jim Bacher: j.bac...@ieee.org All emc-pstc postings are archived and searchable on the web at: No longer online until our new server is brought online and the old messages are imported into the new server.
Re: Regulatory General Discussion : ouput of Compliance group
"Andre, Pierre-Marie" wrote: > > So has anybody some thoughts or argument on the measurement > or evaluation of an Compliance Group ? Well, I'd hate to let the dirty little secret out of the bag for those of us who would fall under such and evaluation. Important in such an evaluation would be that the company has allowed the compliance engineer to have significant input to the design/mfring processes. I've been in companies where evaluations from the compliance engineer amounted to nothing more than a suggestion. Very frustrating. Other places had the compliance engineer greatly involved as a signatory in product release and with ECR/ECOs. Start with an ideal world where the compliance engineer has complete planning, budgeting, signatory/approval powers with the complete product cycle from prototype-to-product release-to product obsolescence. Consider that as the complete model. Then, as the person has less and less involvement/approval power in those areas, they are thus less responsible for them and thus, they are not to be evaluated in those areas. You'll probably find the typical compliance engineer ends up in reality scheduling tests w/no approval powers, has input to ECR/ECOs but no signatory powers, inputs into product design by way of memos, sometimes are the last to know about significant design changes, and might answer to someone who knows little about compliance engineering. IMO, evaluation would be difficult. Regards, Doug McKean --- This message is from the IEEE EMC Society Product Safety Technical Committee emc-pstc discussion list. Visit our web site at: http://www.ewh.ieee.org/soc/emcs/pstc/ To cancel your subscription, send mail to: majord...@ieee.org with the single line: unsubscribe emc-pstc For help, send mail to the list administrators: Michael Garretson:pstc_ad...@garretson.org Dave Healddavehe...@mediaone.net For policy questions, send mail to: Richard Nute: ri...@ieee.org Jim Bacher: j.bac...@ieee.org All emc-pstc postings are archived and searchable on the web at: No longer online until our new server is brought online and the old messages are imported into the new server.
