Chapter 4 Design Concept
Chapter 4 Design Concept
9
DEVELOPING CONCEPTS
1 - Firming Up into Principle Solution Variants
rough calculations based on simplified assumptions
rough sketches or rough scale-drawings of possible layouts, forms, space requirements,
compatibility, etc.
preliminary experiments or model tests used to determine the main properties or to
obtain approximate quantitative statements about the performance and scope for
optimisation
construction of models in order to aid analysis and visualisation (for example, kinematic
models)
analogue modelling and systems simulation, often with the help of computers; for
example stability and loss analyses of hydraulic systems using electrical analogies
further searches of patents and the literature with narrower objectives
market research of proposed technologies, materials, bought-out parts, etc.
10
DEVELOPING CONCEPTS
2 – Evaluating Principle Solution Variants
A: When evaluating principle solution variants, the following steps are recommended.
Identifying Evaluation Criteria
to establish whether all of the proposals to be evaluated still satisfy the demands of the requirements list.
A number of requirements are minimum requirements. It is important to estab- lish whether or not these should
be exceeded. If they should, further evaluation criteria may be needed.
It is necessary to consider technical, economic and safety criteria at the same time.
Evaluation criteria are accordingly derived from:
1. The requirements list:
• Probability of satisfying the demands (how probable, despite which difficulties?)
• Desirability of exceeding minimum requirements (exceed by how much?)
• Wishes (satisfied, not satisfied, how well are they satisfied?)
2. General technical and economic characteristics from the checklist, see Figure 6.22 (to what extent are they
present, how well are they satisfied?)
It has proved useful in the past to list the identified evaluation criteria
in the sequence of the checklist headings and to assign the parameters
of the variants to them.
Whatever quantitative information is available at this stage should also
be included.
Since it is impossible to quantify all the parameters during the
conceptual phase, the qualitative aspects should be put into words and
correlated with the value scale.
KG22803 ENGINEERING DESIGN 15
DEVELOPING CONCEPTS
2 – Evaluating Principle Solution Variants
D: Assessing Values
Those using the 0–4 scale proposed in VDI Guideline 2225
may feel the need to assign intermediate values, particularly
when there are many variants, or when the evaluation team
cannot agree on a precise point.
The 0–10 scale, again, may suggest a degree of accuracy
that does not really exist. Here, arguments about a point are
often superfluous. If there is absolute uncertainty in the
attribution of points, which happens quite often during the
evaluation of concept variants, the point under consideration
should be indicated with a question mark
KG22803 ENGINEERING DESIGN 16
technical ratings
Rt is related to
the technical
capabilities.
Change
Company culture management, so
often overlooked