HOME  |  NEWS  |  BLOGS  |  MESSAGES  |  FEATURES  |  VIDEOS  |  WEBINARS  |  INDUSTRIES  |  FOCUS ON FUNDAMENTALS
  |  REGISTER  |  LOGIN  |  HELP
Oldcarguy
User Rank
Silver
RE: Simple solutions could solve this problem
Oldcarguy   6/27/2011 8:17:08 PM
NO RATINGS
1 saves

It is management’s job to define the desired product attribute list including assigning a weighted importance to each attribute from costing to FMEA and everything in between. It is then clear to the engineers how to approach a first article or straw man. Efficiency can only be realized if an early focus is placed on the weighting of attributes, not just the desired attributes alone.

Likely constraints and exceptions will start to be discovered early in the process from this point on and without a closed loop to management at this point, things can go wrong quick. Focus on the weighting of each attribute more than the attributes themselves, as this process, done right can elicit new and as of yet unthought of attributes by simple material and process evaluation.

Also, the engineers must keep in mind the end user documentation for the product, as many times attributes can be improved by better documentation and signage on the product in lieu of adding costly physical elements in the mash up (not so much these days with safety attributes IE “keep hand out of blades” doesn’t cut it anymore).

Management will ultimately decide on the weighting and will likely alter the weighting based on engineering’s ability to match the weighted attributes and solve for constraints and exceptions in unique ways.


TJ McDermott
User Rank
Blogger
Re: Simple solutions could solve this problem
TJ McDermott   6/23/2011 10:08:22 PM
NO RATINGS
I usually get to commission my projects, so get feedback from the initial operator.  I also frequently get to see the systems after 6 months to a year, and thus get to learn what I did wrong and improve future designs.

sensor pro
User Rank
Gold
keeping the goal in mind
sensor pro   6/23/2011 9:36:41 PM
NO RATINGS




I found that the biggest problem with 

projects that i was involved, was clearly explaining 

to the customer that his specs are abit over reaching 

and that his goal could be reached with a much more relaxed tolerance. 


 


 

I found that each level in the sub-contractinh group was shifting the bulk of error budget to the next level, creating bottlenecks and progress delays.

In many cases the client himself was not clearly aware of what the final design should be and work. In some cases the coordinating manager was more interested in financel then performance.

WaltL
User Rank
Iron
A True Balancing Act
WaltL   6/23/2011 7:14:16 PM
NO RATINGS
As much as I'd like to dream about the "ideal" design process - collaborative and streamlined - some new product projects end up more like a battle between departments and egos. I have managed many projects where no matter how well the plan is conceived, specified, documented, managed, and implemented, it all boils down to how the executive group views the R&D process and nurtures the development team.  Most manufacturing companies that I have worked for, treat the development process/team as a luxury, a kind of necessary evil that saps valuable resources away from more interesting, glamorous, and quick-revenue generating opportunities.

On a positive note, I have experienced a few projects where the executive team member clearly stated the general goals for the project and expectations for each team member.  Nothing too complex or demanding, just plainly stated, in-writing, and communicated to the team, in-person.  Sometimes the exec would leave the team alone and only make an appearance when asked, or for milestone presentations.  Again, this is a HUGE topic (or set of topics) and I've experienced a wide array of functional / dysfunctional teams and management groups.

I'd like to hear stories from other readers about how other companies and individuals experience the development process.  The good, the bad, and the "what ifs?"!

Charles Murray
User Rank
Blogger
stubborn problem
Charles Murray   6/23/2011 6:32:25 PM
NO RATINGS
Part of this goes back to the old "throw-it-over-the-wall" mentality. As much as we write about it, talk about and strategize ways to eliminate it, it still happens.

Beth Stackpole
User Rank
Blogger
DFMA Forum
Beth Stackpole   6/23/2011 1:00:45 PM
NO RATINGS
You raise some interesting points around getting feedback loops earlier in the design process. I know the DFMA Forum was also home to some lively discussion around applying lean and DFMA practices early in design to help drive down the cost of products and level the playing field when it comes to outsourcing. Stay tuned to my story on how these kinds of engineering workflows can accelerate and support the effort to reshore manufacturing back to US soil. Should be up on the new Design News site shortly!

Jennifer Campbell
User Rank
Gold
Re: Simple solutions could solve this problem
Jennifer Campbell   6/23/2011 1:00:31 PM
NO RATINGS
From what I see/read in my role as Design News's Managing Editor, design teams more often than not believe they know best and don't always keep the best interest of the user at heart.

I also wonder if there were consequences to the airline crew that overfilled the tank. Luckily it was caught and only led to flight delays and nothing more serious.

MBA-Motorsport
User Rank
Iron
Re: Simple solutions could solve this problem
MBA-Motorsport   6/23/2011 12:44:08 PM
NO RATINGS
One simple solution that springs to mind is the correct use of FMEA's.

A good FMEA should weed out the unintended consequences of a design, the problem is most engineers see FMEA's as a chore which is boring but has to be done to tick the box, if taken seriously and fully engaged with an FMEA can really help the design process, and has to be done early enough that the solutions can be implemented or the design is not cornered.

So you software people, make FMEA software that interacts with the design process easier and intuitivley and can be worked on in collaboration whilst the design is on-going, rather than making the team lock themselves away in dark room and go through a laborious catch up of all the things they've thought of or done anyway but not recorded.

Geoff

Rob Spiegel
User Rank
Blogger
Simple solutions could solve this problem
Rob Spiegel   6/23/2011 12:20:44 PM
NO RATINGS
What's needed for design problems like this is a feedback loop that alerts the design team of the unintended consequences of a design. The problem with the fuel overfill could be easily solved if the design team is aware of the problem.

One simple solution is for the design team to go online and find comments by frustrated users who are pulling their hair out over design problems. Comments on online forums pop up quickly when users  run into design SNAFUs.



Partner Zone
Latest Analysis
During a teardown of the iPad Air and Microsoft Surface Pro 3 at the Medical Design & Manufacturing Show in Schaumburg, Ill., an engineer showed this "inflammatory" video about the dangers of maliciously mishandling lithium-ion batteries.
The Window Watcher stops the burglar before he does damage or enters the house. House alarm service companies set off alarms and call the service only after the burglar has damaged and entered the house.
If you’re designing a handheld device or industrial machine that will employ a user interface, then you’ll want to check out the upcoming Design News Continuing Education Center course, "Engineering Principles Behind Advanced User Interface Technologies.”
Brooke Williams of Texas Instruments explains how TI’s new TDA3x chip will help future vehicles “see” all around themselves.
It's been two years since the Mac Mini's last appearance on iFixit's teardown table, but a newly revised version joins Apple's lineup this week.
More:Blogs|News
Design News Webinar Series
10/7/2014 8:00 a.m. California / 11:00 a.m. New York
9/25/2014 11:00 a.m. California / 2:00 p.m. New York
9/10/2014 11:00 a.m. California / 2:00 p.m. New York
7/23/2014 11:00 a.m. California / 2:00 p.m. New York
Quick Poll
The Continuing Education Center offers engineers an entirely new way to get the education they need to formulate next-generation solutions.
Oct 20 - 24, How to Design & Build an Embedded Web Server: An Embedded TCP/IP Tutorial
SEMESTERS: 1  |  2  |  3  |  4  |  5  |  6


Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.
Next Class: 10/28-10/30 11:00 AM
Sponsored by Stratasys
Next Class: 10/28-10/30 2:00 PM
Sponsored by Gates Corporation
Next Class: 11/11-11/13 2:00 PM
Sponsored by Littelfuse
Learn More   |   Login   |   Archived Classes
Twitter Feed
Design News Twitter Feed
Like Us on Facebook

Sponsored Content

Technology Marketplace

Copyright © 2014 UBM Canon, A UBM company, All rights reserved. Privacy Policy | Terms of Service