Absolutely essential! We would often end up "taking exception" to various EMC requirements in the procurement document, if it didn't make sense or didn't apply to their application. Assume everything is negotiable. We rarely redesigned our "COTS" T&M products for purely military applications and we were quite successful in selling products into the military. The biggest issue we had was the fact our marketing folks would tend to agree to anything prior to discussing the regulatory aspects with us, causing us to jump through a bunch of hoops later in the process! :-)
Ken Wyatt Technical Services, LLC 56 Aspen Dr. Woodland Park, CO 80863 Email: [email protected] Web: www.emc-seminars.com (719) 310-5418 (888) 212-4602 toll-free On Apr 13, 2009, at 8:35 AM, Price, Edward wrote: In real life, there are often vague and contradictory requirements that can be piled into a contract. I spend a lot of my time providing EMC inputs for our proposals and bids, trying to divine if the requirements set is really, really what the customer wants to do. When a customer gives you a detailed requirements list, you start out by assuming they know what they're doing. However, when the evidence suggests the customer is wandering in circles in the wilderness, then the best course is to arrive at a consensus through gentle questioning. - 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.ieeecommunities.org/emc-pstc Graphics (in well-used formats), large files, etc. can be posted to that URL. 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]>
