% Option Explicit Dim ReturnLink ReturnLink = Request.QueryString( "return" ) %>
|
|
||
|
|
Conceptual Design - United Technologies Corporation The Importance of Conceptual Design According
to Dr. Larry Zeidner, Group Leader of the Advanced Design Methods group
at UTRC, "it's crucial to treat the preliminary stages of any design or
re-design cycle very seriously. Integrated Product Development (IPD) teams
can get the most 'bang for the buck' innovating in the early stages of
design. In conceptual design, an IPD team evaluates customer/stakeholder
needs, identifies the product & process characteristics that best satisfy
those needs and ultimately comes up with a product concept and risk-reduction
plan. Once these basic elements of a product design are set, the detailed
designers take over. But they're bound to follow the overall path set
early on by the design concept. Alternatives overlooked in the initial
stages of design can be very costly to adopt downstream." The Challenge - Finding a Powerful and Flexible Design Tool
When people think of product-design tools, they often picture traditional CAD, CAM and CAE tools. But these tools aren't intended to represent product functionality, which is the focus of conceptual design. Rather, these tools support the detailed design phase, when engineers need specific answers to specific engineering questions in order to work out the details of product and process geometry. "But conceptual design often takes place before selecting specific technologies and implementations," said Zeidner. "It is important to have a flexible tool to focus our experts on the most important questions to brainstorm, and to quickly see how changes made to product functionality will affect the value that our products provide. We need a flexible way to visualize an entire product's functional model." The Solution - hierarchical netViz diagrams "netViz is a key tool in a new UTRC conceptual-design process called 'Collaborative Innovation' (CI)," says Zeidner. "Say a UTC IPD team is assembled to create or modify a product using CI. They first create a functional model of the product in netViz by placing graphical objects in netViz diagrams to represent each important system or process. A single netViz project can include different types of design elements such as mechanical or electronic systems, tools, information, people or processes. By drilling down on objects, the team decomposes each system or process into more
specific components,
eventually creating a 'tree' that describes the most important issues
to be taken into account during conceptual design. The team draws inter-diagram
links between all of the objects that will have real-world effects on
one other. Using this functional model, an IPD team works with product
experts in pre-brainstorming sessions to build models that capture the
design rationale behind the products and processes," says Zeidner. "This
is all a precursor to brainstorming sessions where we explore alternatives
to this current design rationale." Database connectivity
"UTRC also makes use of netViz's database connectivity to connect netViz models to complimentary Excel-based tools for other aspects of conceptual design. We've automated the linkage so that netViz and the other conceptual design tools feed each other automatically, says Zeidner." Data-driven graphics "UTRC uses netViz's data-driven graphics to keep track of the effect a product's sub-systems have on each other. Sub-systems affect one another in multiple ways, some usefully and some harmfully. In a functional model, netViz can represent this with multiple connections between the sub-systems and can use color to differentiate between useful and harmful functions. This provides an intuitive graphical sense of which design decisions are causing problems. For example, if we see a useful function (blue) that's causing a lot of harmful functions (red), we know that we need to take a closer look at that design decision; perhaps there are design alternatives that don't cause as many harmful functions requiring mitigation. As alternatives are tested, modifications to our model are automatically reflected by color, so the look of the diagram gives the team immediate feedback on whether we're making progress," says Zeidner. The bottom line According to Zeidner, "the stakes are highest at the so-called 'fuzzy front-end' of product design. Tools that enable us to focus our efforts and make more informed decisions, at that stage, increase our productivity and capacity for innovation. When UTC designs innovative products and processes that provide more value, we get a huge payoff in terms of quality, cost and customer satisfaction, and that affects the ultimate measure of our success - our bottom line."
Copyright
(c) 2001 Data Stream Solutions |
|