Re your point 1, the crunch is that Design and Compliance have a shared
goal, instead of being potentially antagonists (especially over product
cost). Yes, other things have to be set up correctly.
Re your point 2, by 'dinosaur' I mean 'resistant to change'. Perhaps
'Lingula' would be more apt (a marine creature that hasn't altered
significantly in 500 million years), but not a lot of people know that.
John Woodgate OOO-Own Opinions Only
J M Woodgate and Associates www.woodjohn.uk
Rayleigh, Essex UK
On 2018-09-14 18:03, Brian O'Connell wrote:
Has been my (anecdotal) experience that those that are refusing or delaying
pre-comp scans tend to be the younger designers and managers. And have been
associated with a project team bereft of physics that was under the management
of a young software 'engineer'.
1. Am not certain assigning responsibility to the project leader improves
probability of success in absence of formal, rote test policies.
2. Am not certain that the "dinosaurs" are the problem. The distribution of
poor thinkers would seem to be evenly distributed across most demographics. So the
principle marker for poor engineering decisions and processes seems to be low experience.
Brian
From: John Woodgate [mailto:j...@woodjohn.uk]
Sent: Friday, September 14, 2018 9:45 AM
To: EMC-PSTC@LISTSERV.IEEE.ORG
Subject: Re: [PSES] How to lose another million dollars
It's inevitable that there still are some dinosaurs around who don't see the
need for both making the project leader internally responsible for compliance
(so that Development and Compliance share interests instead of being opposed)
and for the need for pre-compliance checks on the first 'good' engineering
model (not the first model that 'sort-of' works, that's too early).
John Woodgate OOO-Own Opinions Only
J M Woodgate and Associates www.woodjohn.uk
Rayleigh, Essex UK
On 2018-09-14 17:03, Pete Perkins wrote:
James, Oh yes, I have another real life story. In dealing with the compliance
issues on a product I recommended that they run a pre-compliance EMC check and
the chief electrical engineer rebutted that it was so straightforward that they
would do that last, just before releasing the product to marketing. His
position was that this is basic engineering stuff and any competent design
engineer would get it right to begin with or a simple fix would take care of
it. With a little backpressure the pre-scan was done and the product failed
miserably. Needless to say, it took a number of trials to get it all properly
fixed to pass; the release date was missed and the chief electrical engineer
lost his job over it. So we see: lunacy runs both ways.
:>) br, Pete
Peter E Perkins, PE
Principal Product Safety & Regulatory Affairs Consultant
PO Box 23427
Tigard, ORe 97281-3427
503/452-1201
IEEE Life Fellow
p.perk...@ieee.org
From: James Pawson (U3C) <ja...@unit3compliance.co.uk>
Sent: Friday, September 14, 2018 8:00 AM
To: EMC-PSTC@LISTSERV.IEEE.ORG
Subject: Re: [PSES] How to lose another million dollars
Hi John,
Is this an actual true story? I'm lost for words...
James
From: John Woodgate <j...@woodjohn.uk>
Sent: 14 September 2018 12:57
To: EMC-PSTC@LISTSERV.IEEE.ORG
Subject: [PSES] How to lose another million dollars
Prepare for sob story. Company X has implemented the sensible policy of making the project leader internally responsible for EMC and safety compliance, i.e., when the product is tested by the compliance experts, it passes or has only minor defects.
So John Doe takes his engineering model, scheduled for production in 9 months
time to Compliance and asks for pre-compliance checks. No can do, is the reply.
Our new policy is that only products whose planned release date is 4 months or
less ahead can be checked.
Truly, nothing is fool-proof because Nature keeps producing more and more
ingenious fools.
-
----------------------------------------------------------------
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 <sdoug...@ieee.org>
Mike Cantwell <mcantw...@ieee.org>
For policy questions, send mail to:
Jim Bacher: <j.bac...@ieee.org>
David Heald: <dhe...@gmail.com>
