Hi Brian, I have to repeat Rich's sentiment below, Good luck. Hopefully, he/she will have had some positive compliance exposure before the breaking in.
Best regards, Ron -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Brian Oconnell Sent: Thursday, March 29, 2012 12:25 PM To: [email protected] Subject: RE: [PSES] receiving/approval processes under fire Rich, Ron, John, et al, Many thanks for the sanity check (not me, the process requirements). Reminds me of (in another life) the boss's favorite retort: 'too many stupid people, not enough napalm.' Where we were also taught to immediately assault directly into an ambush. Intend to do that. I have received many off-line replies that indicate their design engineers had said the exact same thing to them. And just received another reply from an agency engineer I have known > 10 years. He says this he hears this stuff all the time from eng dept at companies not having a compliance person - "Never had to do anything like this at any other company." Time to go break in the new boss. This may hurt... Brian -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Richard Nute Sent: Thursday, March 29, 2012 10:24 AM To: 'John Woodgate'; [email protected] Subject: RE: [PSES] receiving/approval processes under fire Mr. Woodgate suggests: > What you do is make the design team leader *responsible*for the > compliance of the design. He/she doesn't do the tests but has to > understand the standards that apply enough to assess the test reports > and sign them off. Absolutely! I have successfully used this process for years! My designers have been very complementary. However, to do this, the compliance engineer must partner with the designer so as to offer various alternatives that complement his design, not just a one-size-fits-all. And, you must take some risk with the certification house so that your promises to the design engineer are fulfilled. To do this means you must also partner with the cert house at the same time to be certain that the design is certifiable. This means you join the design team in the very early stages of the design and jointly agree with the design team as to a safety design strategy -- BEFORE the design is developed to a physical model. This has another advantage: the very first prototypes comply with the requirements, and can be used for certification. This means that the certification timetable is not in the critical path to project completion. Good luck! 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]>
