Talk about preference. I asked a question this month that could have gotten just as many responses as people responding. The question was "When you sit down to start a brand new design, what's the first thing you do?"
Of course, the answer has a lot to do with what you are designing and what's been done before. For example, if it's a portable device, I may start to think about the power requirements. If it's a medical device, I'd probably start by making a list of all the standards bodies I need to be in touch with and all the regulations I need to comply with. There's also the question of the geography in which the design will be deployed. Hence, there are likely even more answers than people answering the question.
Regardless, I thought the question would bring some intriguing responses from our readers, and I was right. For example, Eduardo Viramontes said:
I talk to colleagues and team members about the project to get their input and ideas. Some people will focus on very fine details like, "remember to put a pull-down resistor in such and such pin." Others will likely have more high-level ideas like, "you should put a bunch of LEDs here to display a smiley face." These types of unedited ideas, unburdened by the development of the project, will generally only come up in the beginning, when there's no bias about the specifics of the project. And they can save a lot of time down the road.
Emilijan Iljoski said, "I first review my previous designs and analyze the existing designs of others that may be related to the subject matter. De facto, to design something innovative, you must know what has been already done."
That makes sense to me. Basically, that's saying that you don't want to repeat the mistakes of others. Rather, you want to learn from them.
Soumanou Eusebio said:
I like to start with a literature review of existing design, then hold a brainstorming session with my group. We put down all the ideas; regardless of whether we think they are good ideas or bad ideas at this point. Finally, I will narrow the ideas down to three concepts that I will study, test, and compare. From there, I get my final concept for prototyping.
Edna Elizabeth Ramos Cienfuegos said:
To begin my design, I have to know the "voice" of the customer, which I translate into specifications. At the beginning of the design project, it's important to have targets regarding cost, time, quality, and the segment of the market that your product (or service) will be deployed. For example, in France they have "cahier des charges." This is similar to the idea of customer-to-customer, or C2C in the US. It's also related to Advanced Product Quality Planning (APQP) or Concurrent Product and Process Design (CPPD), or any process that requires the understanding of the inputs to trace the boundaries of the design.
And finally, from our own Jon Titus: "I make sure that I have clear objectives and requirements written and agreed upon by all concerned parties. You can't start a project without a clear 'map.'"
Readers, where do you start? Tell us in the comment section below.
As a small company, and the chief technologist (old engineer) I like to gather all the known specifications from the client, make a few suggestions, have them consider some limitations or restrictions, and then push him/her to nail the specifications/requirements down a solidly as possible. Then I have something to work with that isn't a moving target.
Then I take out a blank sheet of paper (my favorite part) and start putting subassemblies together to see how it might just come together.
One of the issues in design is the question of when a "project" is started. Most of the responses you mention assume that the "customer" has a solid list of requirements. In projects involving mostly hardware that seems to be the case. The "customer" takes the time to figure out what they want. In the software world that is often not the case. There are various methods used to deal with this situation. I hear tell of them making their way into the engineering world. I am not sure that is a good thing.
Great question to pose and it will be interesting to hear the community's response. I'm also curious how much of that brainstorming and feedback is being transferred over to some of the newer collaboration technologies and Web-based platforms as opposed to happening in face-to-face meetings with pen and paper in hand. My guess is that since engineering teams no longer sit side by side in the same building, there needs to be some sort of forum for early ideation, and technology is certainly evolving to support that objective.
Are they robots or androids? We're not exactly sure. Each talking, gesturing Geminoid looks exactly like a real individual, starting with their creator, professor Hiroshi Ishiguro of Osaka University in Japan.
Truchard will be presented the award at the 2014 Golden Mousetrap Awards ceremony during the co-located events Pacific Design & Manufacturing, MD&M West, WestPack, PLASTEC West, Electronics West, ATX West, and AeroCon.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.