As every developer knows, there are the paper specifications for a product design, and then there are the real requirements. The paper specs are dry, bland, and rigidly numeric, making them great as metrics but a poor guide to creating a design that will function properly in real-world conditions. Only experience can show you the real requirements a design must meet.
Take the specification categories to which we assign electronics parts and systems: commercial, industrial, and military grade. On paper, these relate to metrics such as shock and vibration tolerance, operating environment temperature, and voltage isolation capacity. In reality, such metrics represent only a small part of what a design must endure. Of far greater significance are the characteristics of the equipment's human operator.
Early in my working life, when I was a design engineer at JHU/APL, I got a lot of experience working on military-grade equipment designs. Beyond the typical MIL-SPEC requirements of wide operating temperature ranges and substantial shock and vibration resistance, the designs had to tolerate military (in particular, US Navy) personnel.
Most of the designs were not for mission- or life-critical systems, so they needed to tolerate rapid setup and breakdown, insufficient (or no) time spent reading operational manuals, and an attitude toward the equipment that often ranged from indifference (at best) to outright resentment. It's easy to understand why; my equipment mostly represented an additional burden on already overworked users in potentially life-threatening situations.
I learned to do things like making sure no two external connectors were identical (to avoid misconnected cables) and making sure that the housing could double as a stepstool. My project managers further trained me in the "two dumb thing" rule: My designs couldn't fail unless the user made two simultaneous dumb mistakes, like spilling coffee on the interior while holding the circuit breaker in a closed position when the chassis was powered and open for maintenance. In short, I needed to make my equipment as fault tolerant and "sailor-proof" as possible.
Of course, it's impossible to imagine all the possible contingencies, much less design for them. And it's the height of folly to imagine that you have done so. One of my co-workers went shipboard with a design he proudly described to a chief petty officer as sailor-proof. The chief took the equipment, examined it carefully, and then threw it over the railing into the ocean.
"Doesn't float," he observed. "Not sailor-proof."
Consumer-grade design is a lot more tolerant. For the most part, consumers figure that, if they break something while doing anything much beyond normal use of the equipment, it's their fault and thus their loss. There are exceptions, of course. The recent buzz about the iPhone 6 bending when people sat with it in their back pocket shows that consumers expect at least some degree of latitude in what constitutes "normal" use.
Industrial-grade equipment falls somewhere between those extremes. The equipment must be fairly rugged and tolerant of human abuse, but mostly not the type of abuse the military can inflict. Where exactly industrial equipment is within that range, though, only you who have industrial equipment design experience can really say.
To read the rest of this article, visit EBN sister site EETimes.