![INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN
ICED 01 GLASGOW.AUGUST21-23, 2001
IMPROVING ACCESS TO DESIGN SOLUTION SPACES USING
VISUALIZATION AND DATA REDUCTION TECHNIQUES
P M Langdon and AChakrabarti
Keywords: Visualisation, clustering, synthesis, design information management, information
analysis, classification and retrieval
1 Introduction
Designers only explore a few solutions in depth at the conceptual stage [1]. Despite this,
evidence suggests that a thorough exploration of a solution space is more likely to lead to
designs of higher quality [2]. FuncSION [3] is a computational tool that synthesises a wide
range of solutions to a class of mechanical design problems involving transmission and
transformation of mechanical forces and motions that are specified as inputs and outputs. It
uses a set of primary functional elements along with combination rules to create anexhaustive
set of solutions in terms of their topological and spatial configurations. Previous research has
demonstrated FuncSION's potential for generating novel solution ideas that designers had not
thought of. However, it was found that the large number of ideas generated could not be
meaningfully explored, while their representation proved too abstract to visualise. Effective
support for conceptual design should help designers obtain a thorough overview of the
solution space, as well as a detailed understanding of its individual solutions. However, the
greater the variety and number of solutions to be explored, the less likely it is that a detailed
understanding of the potential of all individual solutions will be achieved. The DESYN
software described in this paper encapsulates FuncSION with a Graphic User Interfacce
(GUI) [4]. The overall aim of this work is to test the extent to which DESYN is capable of
assisting designers in their exploration of large solution spaces such that an overview of the
entire space is obtained while at the same time facilitating understanding of the individual
solutions contained in it.
2 Background
A paper presented at ICED99 [4] described a scheme adopted in order to solve the above
problems. The problem of exploring large combinatorial spaces is an unresolved issue in
computer aided synthesis research, which is further complicated by the difficulty in displaying
large volume of information [5].
The approach adopted was a novel method of clusteringthe solution configurationsto reduce
the space of solutions that the designer needs to consider in order to get an overview of the
entire space of solutions [6]. This was done by presenting the designers with representative
solutions that were by-products of the clustering process. In this way, large numbers of
solutions can be summarised by a small number of cluster exemplars of prototypes.
ICED 01 - C586/223 3](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-22-320.jpg)
![A number of previous approaches have adopted rule-based heuristics for the generation of
solution compositions in an unconstrained space (See, for example, Campbell et al, 1999)[7]
[8][9]. However, the approach adopted here assumes exhaustive generation of solutions in a
partially constrained space with the use of clustering as a data reduction and representation.
Because of this, all solutions are, in principle, available to the designer through interaction
with the systems GUI.
In the authors' earlier paper, some initial validation of the cluster algorithm was reported
focussing on whether the system's clusterings of solutions were intuitive and whether the
clusterings suggested by the system correspond to designers' own partition of the solution
space. Initial experiments examined a number of DESYN clusterings of two sets of 20
solutions resulting from a synthis using 0-5 elements per solution from a choice of < 4
elements. Figure 1 is an example diagram of the outputs of the same clustering algorithm for a
smaller 6 solution set synthesised using the elements wedge, cam and lever mechanisms.
Clustering was based on a Euclidian distance metric operating on a count of features in each
solution from a feature set of all possible feature pairs.
Figure 1.Cluster table for 2 to 5 clusteringsof a 6 solutions for a problem using Wedge, Cam and Lever
elements.
The arrows indicate the solutions that leave the 3 cluster solution to form new clusters. On the
left of the diagram the six possible solutions output by the synthesiser are enumerated. The
vertical columns show increasing number of clusters in the solution set. The cells show the
cluster membership for each solution. Each cluster has a representative solution that is
denoted by circling. Finally,the box in the corner of cells shows the average distance of the
representative to all the other members of the cluster. The right hand diagram shows a Venn
type representation of the 3,4 and 5 cluster solutions. Solution sets for the larger 5 element
problems were presented to 5 subjects as printed words with illustrative diagrams.
Subjects were required to form groupings of the 20 solutions that corresponded to their
judgements of those that seemed to them to be similar on the basis of their engineering
experience. The subject's groupings were scored for the percentage similarity of groupings
with the DESYN clusterings of the same set. This was to test whether designers found the
system's clustering of solutions intuitive, and whether the clustering suggested by the
designers correspond to their own partition of the solution space. This clustering was based on
an element-pair feature count (focusing on the type of interfaces possible as design elements
in combination),and provided an average commonality, between designer's clustering and the
4 ICED 01 - C586/223](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-23-320.jpg)
![method's, of 74% in contrast to 55% commonality yielded by comparison with a random
clustering.
However, this evaluation was carried out using only the topology, rather than the 3-D
configurations of the solutions. Evaluation of the approach is further extended in this paper
(see section 3.2) using: (1) 3-D configurations displayed by the system as displays of force
and motion solution chains; (2) Graphic representations of the clustered solution space. The
goal of this evaluation is to find whether or not this clustering-based technique improves a
designer's overview of the entire solution space, and whether the software facilities assist
their understanding of the solution space.
3 Current Developments
Current developments include further development of the GUI and visualisation support, and
further evaluation of DESYN, which are described below.
3.1 User interface development
The visualisation utilises a 2D 'star' representation of clusters (Figure 2), and a pseudo-3D
display of a component chain schematic (Figure 3) that we have developed to improve access
to the functional synthesis software. The former is used to aid visualisation of the spatial
relationships between the component interfaces, while the latter is intended to aid the
understanding of the grouping of functional solutions by similarity [10, 11].
Figure 2. The DESYN Graphic User Interface Clustering Tool
In conjunction with this, a 3D visualisation for displaying an overview of the solution space
and the spatial layouts of selected solutions resulting from the synthesis is under development.
ICED 01 - C586/223 5](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-24-320.jpg)
![the screen. No indication of the total number of solutions was given and the solutions were
not presented in any ordering linked to their functional structure. Hence, the designers were
allowed to select as few or as many solutions as they liked. The task further required that the
designers selected individual solutions form the list (left, Figure 4) that they felt met the
criteria. This was made on a point-and-click basis and the resulting set stored in a further text
field (right, Figure 4).
Figure 4. The list representation experimentalgroup interface.
In the structured condition the designers performed the same task but interacted with a 2D
cluster representation of the solutions set. Dwelling the cursor on a central representative
"sun" member of a cluster lead to a list of the cluster solution members appearing in the upper
right text field. Dwelling on the numbered "planet" members highlighted the location of the
solution in the list.
Figure 5. The list representation experimentalgroup interface.
Again, the task further required that the designers select individual solutions form the list (top
right, Figure 5) that they felt met the criteria. This was made on a point-and-click basis by
clicking on the member "planets" and the resulting set stored in a further text field (bottom
right, Figure 5). In both conditions the designers were able to delete members of their
selected set at will.
3.3 Data analysis technique
Results in our previous study [4] suggested that the clustering solution for small problems had
some psychological validity as a grouping of the solution space correlated highly with
designers groupings. Therefore, in the present case, if a solution chosen by a designer
belonged to a cluster generated by the computer, then it was assumed that the designer had an
overview of at least that cluster. If there was a better match between the computed clusters
ICED 01 - C586/223 7](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-26-320.jpg)
![tested in these experiments. However, it was observed that the time to complete the task was
significantly shorter (about 50%) in the clustered condition. Although this was not measured
accurately, it may suggest that the list condition designers required more time to gain an
overview of the space than the designers for whom the solution space was spatially laid out.
The overwhelmingly popular solution represented three sub-mechanisms that give key two
element combinations that re-occur. These included mechanisms that allowed orthogonal
changes in force direction, such as lever to lever; lever to cam; or lever to screw links. The
reports collected from these designers suggested that the criteria applied was simplicity of
solutions, ignoring repetitions of sub-mechanisms and spatially translating force to force
elements such as tie-rods. The effect of prompting the designers for more solutions in these
cases led to the choice of variants on these mechanisms with tie-rods added to circumvent
possible spatial constraints.
The limitations of the evaluation lie in the small number of designers sampled and the use of a
single problem. In addition the previous evaluation [2] had established a commonalityof 75%
between the software-clustered groups and the designers intuitions as indicated by a paper-
based solution-sorting task. In addition, the clustering method was based on a feature based
on a count of pairs of solutionelements. Other features of the solution chain could be used for
clustering to further test the effectiveness of the clustering approach. It was also clear from
the designers performance that a more realistic task would involve a realistic design task
carried out over a longer period. In addition to this, the pseudo 3D visualisation software was
not integrated into the DESYN interface such that visualisation of individual solution chains
was possible during the trial. It was evident that such a visualisation tool would have assisted
the designers understanding of the individual solutions. Work is currently underway with a
larger group of designers, sampling a wider range of problems over a range of sizes of
mechanisms and difficulties of task.
6 Conclusions and further work
A software system for assisting the visualisation of alternative solutions to mechanical design
problems involving transmission and transformation of mechanical forces and motions was
successfully implemented. This utilised a clustering algorithm for the purpose of data
reduction and visualisation of a large solution space. An empirical evaluation of this system
examined whether the designers' sampling of the known solution space was effectively
assisted by an element-pair clustering represented in a 2D display of clusters, in conjunction
with a pseudo-3D visualisationtechnique.
There was no evidence for any improvement in the number of clusters sampled when the
interface provided a list of solutions as opposed to a 2D cluster membership diagram, though
a substantial improvement in time to complete the task was noted. Two strategies were
observed in the designers tested. The predominant strategy involved listing 'elemental' sub-
mechanisms that were capable of orthogonal changes in force direction. These designers
ignored repetitions of sequences or complex combinations as well as elements providing
linear or parallel force transformations. These second strategy group appeared to list solution
sets that were clearly distinctive sequences, because of simplicity or unique element
combinations.
The small number of designers sampled does not enable generalisation to designers at large as
the results may reflect individual strategies. It is also possible that designers' choices were
ICED 01 - C586/223 9](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-28-320.jpg)
![affected by the lack of a genuine engineering task in the short trials. Firmer conclusions will
be facilitated by the collection of further data using an enhanced assistive interface and more
realistic and rigorous design tasks.
7 References
[1] Chakrabarti, A. and Wolf, B., Reasoning with Shapes: Some Observations from a Case
Study", Proc. 1995 ASME Design Engineering Technical Conferences: (9th Intl. Conf.
on DTM), DE-Vol. 83, Vol.2, pp-315-322, 1995.
[2] Fricke, G., Experimental investigation of individual processes in engineering design,
Research in Design Thinking, (N.Cross, K. Doorst and N. Roozenburg eds.) Delft
University Press, pp 105-109, 1992.
[3] Chakrabarti A., and Bligh, T.P. "An Approach to Functional Synthesis of Design
Concepts: Theory, Application, and Emerging Research Issues", AI in Engineering
Design, Analysis and Manufacturing, Vol. 10, No. 4, pp-313-331, 1996.
[4] Langdon, P., and Chakrabarti A. "Browsing a large solution space in breadth and
depth", A. 12th International Conference on Engineering Design (ICED 99), Munich,
Germany, v3 p. 1865-1868, 1999.
[5] Johnson,B., & Shneiderman, B. "Tree-maps: A space-filling approach to the
visualisation of hierarchical information structures". Proc. IEEE Visualization'91.
IEEE, Piscataway, NJ, 284-291, 1991.
[6] Kaufman, L. & Rousseeuw, P.J., Finding Groups in Data. Wiley Series in Probability
and Mathematical Statistics. John Wiley and Sons, Inc., 1990.
[7] Campbell, M.I. ,Cagan, J., Kotovsky, K., A-Design: An Agent-Based approach to
conceptual design in a dynamic environment. Research in Engineering Design, Vol. 11,
pp 172-192, 1999.
[8] Finger, S., and Rinderle. J.R., A transformational approach to mechanical design usinga
bond-graph grammer. In Design Theory and Methodology, DTM 89, vDE Vol. 17. pp
107-115, 1989.
[9] Bracewell, R.H., Sharpe, J.E.E. Functional descriptions used in computer support for
qualitative scheme generation - Schemebuilder. AI EDAM Journal - Special Issue:
Representing Functionality in Design 10(4): p. 333-346, (1996).
[10] Robertson G.G., Card S.K., Mackinlay, J.D., Information visualization using 3D
interactive animation. Communications of the ACM, Apr 1993, Vol.36, No.4, pp.57-71,
1993.
[11] Mackinlay,J.D., Rao.R, Card, S.K., An Organic user interface for searching citation
links. Human Factors in Computing Systems (CHI) Conference Proceedings, Vol.1,
pp.67-73, ACM, New York, NY, USA. 1995.
Corresponding author's name: Dr. Patrick Langdon
Engineering Design Centre, Cambridge University Engineering Department, Trumpington
Street, Cambridge CB2 1PZ, UK, Tel: +44 1223 766961 Fax: 444 1223 332662, E-mail:
pml24@eng.cam.ac.uk, URL:http://www-edc.eng.cam.ac.uk/people/pml24.html
© Cambridge Engineering Design Centre2001
10 ICED 01 - C586/223](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-29-320.jpg)
![INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN
ICED 01 GLASGOW, AUGUST 21-23, 2001
SUPPORTING NON-STRUCTURED GRAPHICALINFORMATIONIN
INTEGRATED DESIGNTEAM
E Blanco and M Gardoni
Keywords: design information, design understanding, hypermedia and multimedia,
knowledge management
The aim of this paper is to focus on the use of draft and sketches in the group understanding
within Integrated-Team. We suggest specifications of a communication tool that supports and
structures numerical drafting and treatment for capitalisation of those drafts connected to
messages.
1 Evolution of Engineering Information Requirements
Traditionally, engineering activities are performed in a sequential order. Over the last ten
years, companies have tended to apply the Concurrent Engineering approach (CE) in order to
drastically reduce the time-to-market of their products [1]. This approach is opposed to the
sequential engineering approach because they have respectively two fundamental ways of
working. In sequential engineering approach, the work starts at the reception of the results of
the early stage when CE is based on information exchanges. Those exchanges are mainly
performed verbally face-to-face or on the phone. Unfortunately, this information is therefore
poorly controlled. This term "control" can be characterised in terms of four criteria [2] :
- Information Structuring: it relies on a formal conceptual scheme which organise
information at appropriate places. The evaluation criteria are the easyness to organise
information in an intuitive and logical way and to be able to manage information at
separate locations.
Information Sharing: ability of "pushing" information.
- Information Access: ability to "pull"information.
- Information Capitalisation: ability to store and process information for later re-use, we
assume that it must comply with the cycle of 'company knowledge capitalisation', i.e.
locate, memorise, use information and update information.
Taking into account these new requirements, we characterise the type of information
exchanged in Integrated Team. We will focus here on information Structuration model. In
order to meet the rigour needs of companies without going down on a too fine level of
granularity, we choose an instructional design of the information significance. We then
consider that the construction of a sentence corresponds to combine instructions formulated in
term of variables, which provide a sense to the statement. Exchanged information is then an
abstracted entity, a theoretical object which consists of [3]:
ICED 01 - C586/418 11](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-30-320.jpg)
![- Linguistic components which build the significance of information starting from
instructions.
- Rhetoric components which bring a sense to information by addition of contextual
information.
Figure 1. Instructional design of the information significance
Thanks to this instructional design of the information significance, we characterise different
types of information [2] :
Structured-Information (SI), linguistic and rhetoric components of the 57 are generally
imposed.
- Semi-Structured-Information (SSI), linguistic components of the SSI are little formalised
and rhetoric components could be parsimonious.
Non-Structured-Information (NSI), the NSI are very little formalised and the rhetoric
components can be very light if they ensure a sufficient degree of relevance for the
comprehension of information by the receiver.
The MICA approach [4] (a specific interactive messaging system) has been developed and
experimented in order to harness of NSI and to capitalise on relevant information exchanges.
Also a Groupware tool called MICA, was created through an Intranet. It has been
implemented and put into operation in an engineering team of twenty people in May 1998.
Some return on experience has already shown improvement of the efficiency of the Integrated
Team.
Nevertheless, this kind of capitalisation from linguistic data is limited because of the
graphical NSI lack. Sketching takes a large place in the group understanding of technical
problems. Goel [5] also argues that freehand sketches facilitate creative and explorative work
at the early stage of design, because they are ambiguous semantically and syntactically dense.
Sketches could be considered as Graphical Non Structured Information (GNSI). They are at
the same time models of the product and communication vectors. MICA only takes into
account linguistic data but does not take care of GNSI management. This is today one of the
actual limit of the MICA approach and more generally of Knowledge Management systems
[6]. Generally Groupware solutions for interactive sketching have to be improved.
2 GNSI in collaborative design
In order to analyse the role of GNSI in collaborative design we have carried out a design
experiment [7]. This experiment was based upon the distributed design model [8]. Three roles
12 ICED 01 - C586/418](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-31-320.jpg)
![were represented, the functional, structural and machining roles. A camera has recorded the
whole progress of the design. The work began with the requirement list supplied by the client
a few days before the experiment. It took six hours to implement the detailed drafts of each
part of the product in order to manufacture it.
2.1 Sketches as IntermediaryObjects of the designprocess
In order to observe and analyse the design processes, we suggest to start with the Intermediary
Objects (IO) which, circulating at any given moment between the actors of the process, can be
seen as resulting from their design work but also as supporting and highlighting it [9], [10].
In modelling the future product they also act as communication vectors between the product
designers. These two aspects are so indissociable in the reality of the process that we cannot
isolate one from the other without deforming their nature. Because of this hybrid nature,
intermediary objects are "analysers", making it possible to describe the actual design process.
All along the design task, the object can not exist without the actor and the actor without the
object. What we observe, see and feel in the design process, are objects being constructed,
talked about, manipulated, interpreted, transformed, etc. Considered separately, the objects
and actors are merely capacities for action. They are inert, static, mere?? "possibilities". It is
the action, or rather the inter-action in which they are engaged that endows them with force,
meaning and effective reality.
The intermediary objects are also mediating objects: first of all, because of the mode of
representation they use. This leads to a particular way of objectivising the idea or the intention
by inscribing it in a specific organised matter. Thus, for example, a drawing is not simply a
faithful representation of the mental idea or specifications : it is a translation, i.e. a realisation
and a transformation which has been carried out according to its specific constraints
(including those of the material used, which may vary depending on whether it is on paper or
on screen) and its own rules and conventions. Lastly, the way in which the Intermediary
Objects play the role of mediators in the design process is a result of their being
representations.
IO contents are mainly of cognitive nature : it results from the use of acquired knowledge by
the actors in their various fields. They also signal the gradual production of new knowledge
about the product as it is being designed. However, these contents are only of a cognitive
nature in a situation of action, oriented by a given project and made up by the choices of the
actors, the multiple negotiations that they are involved in, and the compromises and decisions
that result from these. Therefore the cognitive contents cannot be isolated from the context of
action
2.2 Classification of sketches in the collaborative process
The role of the objects like sketches in collaborative design process are quite complex.
Ferguson [11] identifies three kinds of sketches : thinking, talking, prescriptive. The situation
of the experiment that we have carried out emphases on the second category of sketches. The
collaborative activity involved many talking sketches. On the contrary, studies based on
single designer activity mainly point out the thinking role of sketches [12].
In the experiment, we had characterised sketches [6] through an axis from open object that are
able to support negotiation, to closed objects that mainly support prescriptions. We observed
ICED 01 - C586/418 13](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-32-320.jpg)
![that the same object can support different status even if some objects get materials and
cognitive characteristics that enhance opened or closed use. The situation of action as well as
the material and cognitive properties of the IO influence the status.
In the protocol, for example, we observed that the same sketch can be realised by an actor for
his own use and after a few minutes be proposed to the others for evaluation. It moves from a
private status (it is a thinking sketch), to a public one in the centre of the table. The existence
of the private area is very important for the designer. This area is the thinking area that allows
to explore ideas without judgement from the other. In a second step, the actor presents the
meaning of his sketch and the other actors can assess the solution in their own point of view.
This object then acts as a conjecture of solution. We can say that it is an externalisation of the
designer's solution mental image. But this talking phase is also a thinking phase for the group
that can make the sketch evolve. Every sketches are not built in a private area. Some are
drawn directly in the public area of the table.
A Sketch can also move from a talking to a prescriptive status. A sketch which has been the
instrument of solution negotiation and elaboration, can get a prescriptive status after the group
has built an agreement over it. For example, the sketch figure 2 got this prescriptive status by
the group agreement. This decision is confirmed by a mark on the object: One of the actor
underlined the word piston. This mark (detail Al) acts as the validation of the agreement. The
definition and the negotiation of this part is then closed.
Goel [5] suggests another way to characterise the evolution of sketches in he design process:
the transformations typology. He identifies two types of operations occurring between
successive sketches in the early stages of design: lateral and vertical transformations. A lateral
transformation movement goes from one idea to a slightly different idea. Vertical express a
movement from one idea to a detail or an extract of it.
Then we can say that the role of the sketches depends on their status and the evolution
between to successive sketches. The next table sum up the different categories of sketches we
have identified.
Thinking
Talking / open
Prescription / closed
Lateral transformation
Private new conjecture
Public new conjecture
New prescription
Vertical transformation
Private in depth conjecture
Public in depth conjecture
In depth prescription
The status of the sketch is important in the sense that they partially characterise the situation
of action where the actors are involved. Referring to the model presented figure 1, we can
notice that the perception of the situation allows the receiver to build the sense of the
information within the situation S. It act as a part of rhetoric components.
14 ICED 01 - C586/418
Table 1. Typology of sketches
Private area
Public area](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-33-320.jpg)
![2.3 Sketches as a process of building conventional support
For the explanation of this point, we must focus on the building process of those objects. The
Object presented in figure 3 is in fact an addition of different sketch steps. The building of
this sketch represents 20 minutes of group interaction during the design process. We consider
that it is in this object that emerges the solution principle developed during the next phases of
the experiment[7]. The first sketch (detail A) was drawn to put a end to a misunderstanding
between two actors. They did not have the same interpretation of the requirements. The three
sketches (A, B, C) allowed them to build a shared understanding of the problem. Then, from
this representation a third actor had doubt about the connection between the device and its
environment. This actor assessed the rubber tubing connection (detail D) as a non reliable
solution for this system. From this negative evaluation of the solution elements represented on
this sketch emerged a few minutes later a rigid and quick connection solution that is
represented (detail E) on the sketch. This move is a lateral transformation that highlight the
emergence process.
Then this solution offered new opportunities for the inter-connections system of blocks.
Finally a general overview of the system was drawn to visualise the ability of blocks
interconnection (detail F). This last view is a vertical transformation showing the same
solution from another point of view.
Figure 2. Status of object moves during the
process.
Figure 3. Different level of sketches in the same
draft...
This sketch shows that the knowledge of construction process is necessary to be able to
understand the sketch. In this sketch, aborted solutions and the solution chosen are
represented on the same level. Nothing but the knowing of the process allowed the actors to
differentiate the good from the aborted solution.
This point allows us to point out that this type of GNSI is not able to support a prescription
task. It failed as a memory of the process, In our protocol, we highlight that the actors
themselves had difficulties to re-use their own sketches out of the action process itself.[7]
The actors created, during the process, some symbolic devices which were connected to
semantic in a local convention. This allowed them to let some part of the device in a low
definition level: fuzzy and partial. The objects were used as "cognitive artefacts". The
participants did not describe precisely what they were talking about, they showed the different
elements they wanted to highlight with a finger or a pen and they used diectic words to point
them. For example, an actor said: "that will be difficult to manufacture" (showing the
elements concerned with his pen)
ICED 01 - C586/418 15](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-34-320.jpg)
![We want to highlight the fact that the sketches act as pragmatic conventional supports [13].
Those conventional supports are negotiated in the interactions between actors, even if they
can also use a higher level of convention as cultural ones, shared by the actors (the rules of
industrial drawing in our case).
The sense of the sketch is built in the action process and the conventions which allow this
interpretation are quite local. Rhetoric components of sketches are specific and part of the
linguistic components are built within the action itself.
This characteristic of GNSI is important in order to imagine design tool able to support GNSI
in an asynchronous communication process; furthermore, in order to involve sketches in a
knowledge capitalisation process as MICA does for textual NSI. Indeed local conventions
which allow interpretations are built in the interaction process. They won't be available to
actors that were not involved in the process itself.
3 Towards a communication tool MICA GRAPH
The first quality of a sketching device for designer seems to allow fast freehand sketch.
Previous studies have highlighted that the cognitive tasks of manipulating the sketching tool
have to be minimised [14]. Even if we can expect that the actors will learn the tool. That is
why the tool is based on a simple blackboard technic and uses a digital table with an
electronic pen. Indeed, when the designer needs formal drawing he will mainly use CAD or
Structured information tools. Sketches are just GNSI and support fuzzy and partial definitions
of elements. The functions that we offer are not supposed to help the drawing process but to
partially structure GNSI in order to capitalise and treat them in the knowledge process. We are
at the moment unable to manage a knowledge treatment directly on sketches. The principle
we develop here is to characterise GNSI, track the steps of the building process and to
associate textual and symbolic information that the data-mining techniques used by MICA are
able to treat. At the moment, a designer creates a new sketch, he creates a properties file
containing the legend of the file, type of the GNSI created and all the textual annotations
contained. All this textual information is able to be treated by the MICA data-mining
process [4].
3.1 Tracking the different steps of the object
We have highlighted the difficulty to track the different steps of a sketch out of the drawing
process. It is also impossible to identify in a sketch the valid elements from the aborted
solutions. It is important to follow the sketches modifications and to track the different sketch
levels and steps present in the same final draft. We also want to know who had drawn on it.
We propose to develop a structure of layers in order track the process. Each actor who wants
to draw on an existing draft has to open a new layer. He can chose two options:
"transparency" that allows him to sketch on the previous element or "blank" that opens a new
layer disconnected from the previous sketch. In order to track information about the sketch
contents and intentions, we characterise the type of opened layers. Six types of layers are
available corresponding to the typology proposed in table 1. Public layers and private layers
have different properties. When an actor wants to send a sketch, the public layers are
automatically sent. Private layers sending is optional. If the actor accepts to send them the
category changes moving from private to the public area.
16 ICED01-C586/418](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-35-320.jpg)
![In order to highlight decisions concerning a specific area of a sketch, actors can modify the
colour of this area. By drawing a boundary line around this area, they notify that it is fixed.
This materialises the compromise within the object.
3.2 The necessity to associate annotations on GNSI
In order to allow the actors to interpret the sketches in an asynchronous communication mode,
and to capitalise textual information about the content of the sketch, we propose different
devices to the users. Firstly an actor as to define a title to the sketch using few keywords. We
notice here that some contextual components (product, process, state, part etc. ) are already
identified in the MICA form.[2] [4]
It is important to give the actors the ability to express comments in the sketch itself. In a
synchronous interaction around sketches actors explain some elements of the solution they
focus on. Drawing is generally accompanied by a speech concerning the sketch. In an
asynchronous process, the speech does not exist. It is supported by writing in the message or
by a local annotation on the sketch.
In the same way, actors need to be able to focus the attention of the receiver on a specific area
and to associate elements that allow the receiver to interpret the sketch in the right way. They
have sometimes to explain some symbolic elements they have used to fuzzy represent an
element. Annotations can allow them to do it. The annotations are textual information that are
connected to the graphic properties.
A further step is to allow an actor to define different types of annotations using colour and
type of markers. Each time he defines a new type, he has to explain the legend of this
symbolic feature. Laureillard had pointed out the importance of what he called co-operative
feature in the co-operation between specialists [15][16]. Those symbols are local conventional
supports which refer to shared knowledge between the different actors. We don't have deeply
investigated the different types of annotation. Our proposition is to offer a toolbox to the
actors. They have to define themselves the relevant type co-operation feature.
4 Conclusions
The concepts developed in the MICA-GRAPH tool have to be improved in design practices.
The aim is not to suppress synchronous interactions but to complete the offer of asynchronous
communications tools for design activities. Engineering design needs visual representations:
structured (like CAD models) and non structured (like sketches). GNSI allows to manage
quick conjecture-evaluation process. We notice that the move from direct interaction to
textual explanation implies the risk of the deterioration of the contents. But the advantages of
textual information related to GNSI aretheir ability to be treated in a knowledge process.
References
[1] B. Prasad, Concurrent Engineering Fundamentals - Integrated product and process
organisation, Vol. 1, Prentice Hall, Englewood Cliffs, NJ, 1996
[2] M. Gardoni, M. Spadoni, F. Vernadat, "Information and Knowledge Support in
Concurrent Engineering Environments", 3rd
International Conference on Engineering
Design and Automation, EDA'99, Vancouver, B.C., Canada, August 1-4, 1999
ICED 01 - C586/418 17](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-36-320.jpg)
![[3] Moeschler, J. Modelisation du dialogue (representation de 1'inference argumentative),
Editions Hermes, Paris, 1989
[4] M. Gardoni, Maitrise de 1'information non structuree et capitalisation du savoir et du
savoir-faire en Ingenierie Integree - Cas d'etude Aerospatiale Matra, PhD thesis of Metz
University 1999
[5] Goel V, Sketches of thought MIT press Cambridge, MA 1995
[6] Gardoni M., Blanco E Taxonomy of information and capitalisation in a Concurrent
Engineering context 7th ispe international conference on concurrent engineering
(CE'2000), Lyon, France, July 2000
[7] Blanco E., 1'emergence du produit dans la conception distribute PHD thesis INP
Grenoble 1998
[8] Garro O., Salau I., Martin P., Distributed design theory and methodology, Concurrent
engineering: research and applications, vol 3/1/1995.
[9] Vinck D., Jeantet A., 1995 Mediating and commissioning objects in the sociotechnical
process of product design: a conceptual approach, pp111-129 in D. Mac Lean, P.
Saviotti, D. Vinck (eds), Management and new technology : Design, Networks and
Strategy. COST Social science serie. Bruxelles. Commission of european
[10] Blanco E., Garro O., Brissaud D., Jeantet A., Intermediary object in the context of
distributed design CESA Computational Engineering in systems applications, IEEE-
SMC, Lille, July 96
[11] Fergusson E,S, Engineering and the Mind's Eye MIT press Cambridge, MA 1992
[12] Rodgers PA, Green G., McGownA. Using concept sketches to track design progress in
Design studies 21 N°5 pp 465-481 sept 2000
[13] N. Dodier, les appuis conventionnels de I'action elements de pragmatique sociologique
Reseaux n°62 edition CNET, 1993
[14] Aytes G., Comparing Drawing Tools and Whiteboards: An Analysis of the Group
Process in CSCW 4: 51-71,1996
[15] Laureillard P., conception integree dans I 'usage, PHD thesis INP Grenoble 1999
[16] Boujut, Blanco The role of objects in design co-operation: communication throught
virtual or physical objects. In COOP 2000 conferences Workshop Sophia Antipolis
May 2000
Dr Blanco Eric
Soils Solids Structures laboratory, Domaine Universitaire, BP 53, 38041 GRENOBLE Cedex
9, France, Tel: (33)-4-76-82-70-11, Fax (33)-4-76-82-70-43, mail - eric.blanco@hmg.inpg.fr
Dr Gardoni Mickael
GILCO laboratory, ENSGI, 46 avenue Felix Viallet, 38031 Grenoble Cedexl, France, Tel
(33) (0)4 76 57 43 33, Fax (33) (0)4 76 57 46 95, mail: gardoni@gilco.inpg.fr
(c)IMechE2001
18 ICED 01 - C586/418](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-37-320.jpg)
![INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN
ICED 01 GLASGOW, AUGUST 21-23,2001
AUTOMATIC COMPOSITIONOF XML DOCUMENTSTOEXPRESS
DESIGN INFORMATION NEEDS
A Dong, S Song, J-L Wu, and A MAgogino
Keywords: Information analysis, classification and retrieval; information representation;
design information management
1 Introduction
Engineering design is an information intensive activity. It is reported that designers spend in
excess of 50% of their time in handling information [7]. Thus, the efficiency and the quality
of the design process depend considerably on how well designers are able to handle large
amounts of information. One study [8] of the information required by design engineers to
complete their jobs indicated that less than 50% of that information was actually available and
only 20% could be provided by the existing specialized applications. Directing the right
information to the right person at the right time is a complicated but crucial task.
Design information management has received increasing attention in recent years as a result
of these findings and the recognition that lacking sufficient or missing key design information
may lead to sub-optimal decision-making and design [2,4]. Much of the existing research has
focused on the capture, storage, indexing and presentation of design information including
informal information [3,9]. Less work has been done on information retrieval based on an
understanding of individual designers, their experience, their skills and the ways in which
they use information in the context of their design task [1]. One key step in finding the right
information is expressing information needs in context. This paper presents a methodology to
generate an XML (extensible Markup Language) document that expresses the information
needs of a design engineer. XML documents and their underlying Document Type Definition
(DTD) offer an efficient structure for the organization of design information [5] and
representation of information needs. Through declarations of XML entities and the inherent
structural hierarchy of XML documents, XML documents can express the designer's
information needs while framing the design's structural hierarchies. For example, an element
in the DTD may permit the design engineer to express a preference for formal company
documents of past designs (e.g., technical memos) rather than informal design notes. The
data in the XML document may be drawn from a repository of semi-structured or
unstructured text documents that the design engineer has retrieved and placed into a personal
information store by using an information retrieval system.
Our methodology draws from the computational linguistics techniques of natural language
processing and latent semantic analysis (LSA). We assume there exists some underlying
information needs that are expressed by the type of information the engineering designer
wishes to view and download into a personal information store. The "type of information"
will be distinguished primarily by subject but may include other identifiers such as the format
of the information and the intended audience. By applying these linguistic techniques, we can
ICED 01 - C586/422 19](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-38-320.jpg)
![construct an XML document that is descriptive of this underlying need and contains
information directly from the documents that is consistent with the major patterns of
information preferences of the designer.
2 Methodology
2.1 Technical Approach
The methodology for automated composition of the XML documents proceeds along two
axes: 1) explicitly solicit information needs from the designer through standard information
retrieval means; 2) implicitly monitor the information retrieval behaviour of the designer to
information sources including the type, quality and information contained in the documents
the designer chose to retrieve. We test this methodology on access to unstructured
engineering data, such as full-text, because unstructured, textual documents are the principal
mode of communication by engineers. Before proceeding to a detailed discussion of our
methodology, we discuss two core technologies to the methodology: mining of transaction
logs to learn information needs implicitly and computational linguistics.
2.2 Learning Information Needs Implicitly
Many difficulties exist in determining what information a person wants to see as well as
modelling user information needs. Most information retrieval systems require that people
express information needs through a set of keywords or key phrases. However, ascertaining
information needs simply by a word or two is inadequate and subject to loss of contextual
information. For engineering design, studies have shown varying information needs of
designers depending on level of expertise and stage of the design [1,6]. Our approach in
modelling user information needs is based on a human-centred computing. Our methodology
examines the user's document access patterns, that is, the user's personal information store
and transaction history in an information retrieval system, for patterns of information
preference. The basic approach is to examine the user's session information over all sessions
while using the information management system. In learning information needs implicitly,
we are primarily interested in discovering the similarity between documents that the user has
downloaded into a personal information store. The assumption is that the user's particular
choices of documents to store locally are indicative of information needs. Thus, instead of
requiring the designer to a priori categorize the information, the system attempts to learn a
similarity mapping using contextual clues such as project name, engineering discipline, and
document format. Similar categorisation strategies have also been found in the classification
of supplier information practised in industry [12].
To ascertain relevance, the system records each document downloaded into the user's
personal information store. This is an accurate indicator of relevance because, in our system,
before the user may download the document, the user has already read a brief description of
the content of the document containing meta-information such as abstract, author, document
type, and subject. The assumption is that during any single session utilizing the information
retrieval system, the user has a dominant goal (information need) in mind that is expressed by
the type(s) of documents the user decides to download. Similar assumptions exist in other
studies [13] of information retrieval systems.
We use the vector space approach [14] for document and query representation. We
analytically modelled information needs as a linear combination of the vectors representing
20 ICED 01 - C586/422](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-39-320.jpg)
![the query and the relevant document. The weighted vector average (arithmetic mean) of all
combined vectors consisting of the query and relevant documents is called the "centroid" of
the user's intended information needs. The centroid is then used as a representation of the
dominant information need of the user. The maximum angle between the document vectors
or query string vector and the centroid is used as an indication of the variation in the user's
information needs.
2.3 ComputationalLinguisticApproaches
Our methodology employs two computational linguistics techniques, natural language
processing and latent semantic analysis, to extract and summarizethe primary topic of a set of
similar documents.
Natural Language Processing
While we use the designer's past transactions as an indication of information need, the
structured information contained in the documents that are referenced in the transactions
needs to be discovered and refined before it can be utilised effectively. The key phrase
retrieval process helps in crosschecking the indexed subjects and compacting the size of the
aggregated XML document by representing paragraphs of text with just a few representative
noun phrases. As the designer adds documents to a personal information store, we do not
need to concatenate all the textual information about the document to the XML document, just
the extracted noun phrases that are not already in there and plug them under the appropriate
tags. By identifying the noun phrases in the document, we are able to find the corresponding
contents for each XML tag in the text. Additional rules and procedures are needed other than
standard noun phrase retrieval process to perform this task for all tags. This latter component
forms a part of future research.
Extracting from the full-text content-bearing noun phrases documents that can be used in
profiling and indexing involves 3 steps: tokenization, part-of-speech (POS) tagging and noun-
phrase identification. Tokenization is a procedure that identifies sentence boundaries and
removes extraneous punctuations. POS taggers then take the processed corpus and tag each
word with their POS information. Taggers that operate following semantic rules or just
statistical information were developed. After the text corpus has been tagged with POS
information, we could use the contextual information to identify noun phrases. The extracted
noun phrases are then attached to the corresponding DTD elements of the document.
Latent Semantic Analysis
Latent Semantic Analysis (LSA) [9] is a statistical model of word usage that permits
comparisons of semantic similarity between pieces of textual information. The idea is that the
totality of information about all the word contexts in which a word does and does not appear
provides a set of mutual constraints that largely determines the similarity of meaning of words
and sets of words to each other. The primary assumption of LSA is that there exists an
underlying or "latent" structure in the pattern of word usage across documents. LSA uses the
matrix technique of singular value decomposition (SVD) to reflect the major associative
patterns of words in the document and to ignore the smaller influences. The ability for LSA
to remove the obscuring "noise" makes LSA useful as an analytical tool for discovering the
primary conceptual content of documents. We use LSA to help us to categorize and group the
documents by topic material that the user has downloaded and revealed as relevant and useful.
Once these principal groupings are identified, we can then apply the rest of our methodology
ICED 01 - C586/422 21](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-40-320.jpg)
![to express information needs for each "centroid" of documents within a semantic locality
through a single XML document.
2.4 ComposingXML Documents
The system initiates by asking the user to specify an XML DTD containing metadata elements
(XML entities) that express information needs. For this study, we asked that users express
their information needs using a well-known metadata set, the IEEE Learning Object Metadata
(LOM) [10], and in particular the core 20 elements. The LOM defines the information
required to manage, locate and evaluate learning resources. Having a standards-based XML
DTD allows us to assess our methodology's completeness and efficacy and for comparison
against other systems. Because of the analogous human cognitive processes of information
processing and learning [11], the LOM serves as a reasonable model for describing
information needs.
Once the user has specified an XML DTD, the user must now utilise the information
management system, retrieving and downloading design documents. The system implicitly
monitors the information retrieval transactions of the user, eventually formulating a seed an
XML document containing information from the user's session. Typically, the XML
document is seeded with the initial query the user posed to the system.
The implicit stage contains two phases. In phase one, the system applies latent semantic
analysis to characterize the knowledge conveyed by the all documents the person chose to
view. To perform this phase, we analysed the transaction logs containing the transactions of
both the current user and all other users of the system. The user's query and document(s)
downloaded are recorded for each visit. The latter information identifies the relevant
documents necessary for phase two. Using a similarity measurement, the system identifies
topics represented by the documents the user viewed. By doing this step, the system
ascertains the topic locality of the various documents the person viewed. This is a critical step
because the user may have multiple and widely varying information needs. Then, for each
topic locality, the system augments the XML document expressing the user's information
needs with the metadata elements from each relevant document. In practice, the information
management system will contain most of the information required to complete the tagging
such as Author, Title, Date, and Format. Subject and Description information are generated
automatically from the second phase. This matching can be done by exact one-to-one
correlation, i.e., both the tag and attribute match, or via a crosswalk between the information
about the document contained in the information management system and the XML DTD.
Both of these techniques will have required some prior means of tagging the documents in the
information management system.
In the second phase, we apply natural language processing techniques to ascertain the
principal subject of the documents within each topic as discussed in Section 2.3. The process
repeats until all possible elements in the user's original XML DTD are filled, resulting in a
fully marked up XML document. The completed DTD is now an expression of the
information needs of the designer, based upon the available information stores and the pattern
of information retrieval undertaken.
In summary, a designer's information needs can be found implicitly by looking at the set of
documents the designer has deemed relevant and useful and stored in a personal information
store. We use LSA to find signatures of similarity in this set of documentation. Once we find
the signatures, we look at what the original information needs were to find the centroid of the
22 ICED01 - C586/422](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-41-320.jpg)
![5 References
[1] Lowe, Alistair, McMahon, Chris, and Shah, Tulan, Culley, S., "A Method for The
Study of Information Use Profiles for Design Engineers," Proceedings of the 1999
ASME Design Engineering Technical Conferences. September 12-15, 1999, Las Vegas,
Nevada.
[2] Court, A.W., Culley, S.J., and McMahon, C. A., "The Influence of IT in New Product
Development: Observations of an Empirical Study of the Access of Engineering Design
Information, International Journal of Information Management, 17(5), 1997, p359-375.
[3] Dong, Andy and Agogino, Alice M., "Text analysis for constructing design
representations." Artificial Intelligence in Engineering. 11, 1997, p65-75.
[4] Rangan, R.M., and Fulton, R.E., "A data management strategy to control design and
manufacturing information." Journal of Engineering with Computers. 7, 1991, p63-78.
[5] Rezayat, M., "Knowledge-based product development using XML and KCs,"
Computer-Aided Design. 32, 2000, 299-309.
[6] Ullman, David G., Dietterich, Thomas G., and Stauffer, Larry A., "A Model of the
Mechanical Design Process Based on Empirical Data", Artificial Intelligence in
Engineering Design and Manufacturing.2(1), 1988, p33-52.
[7] Williams, Ruth L., and Cothrel, Joseph, "Four smart ways to run online communities,"
Sloan Management Review. 41(4), Summer 2000, p81-91.
[8] Wood, William H., Yang, Maria, et al., "Design information retrieval: improving access
to the informal side of design," Proceedings of the ASME Design Engineering
Technical Conferences. 1998.
[9] Deerwester, Scott, Dumais, Susan T., Furnas, George W., Landauer, Thomas K., and
Harshman, Richard, "Indexing by Latent Semantic Analysis," Journal Of The American
Society For Information Science. September 1990, 41(6), p391-407.
[10] Learning Object Metadata, http://ltsc.ieee.org/doc/wgl2/LOMdoc2_4.doc.
[11] In Klahr, David and Kotovsky, Kenneth, (Eds.), Complex Information Processing: The
Impact of Herbert A. Simon, Lawrence Erlbaum Associates, Hillsdale, New Jersey,
1989.
[12] Culley, Stephen J., Boston, Oliver P., and McMahon, Christopher A., "Suppliers in New
Product Development: Their Information and Integration," Journal of Engineering
Design, 10(1), 1999, 59-75.
[13] Cooper, William S., 1976, "The Paradoxical Role of Unexamined Documents in the
Evaluation of Retrieval Effectiveness," Information Processing and Management, 12,
367-375.
[14] Salton, Gerald and McGill, Michael J., 1983, Introduction to Modem Information
Retrieval, New York: McGraw-Hill Book Company.
Dr. Andy Dong, Lecturer
University of California, Berkeley, Department of Mechanical Engineering, 5138 Etcheverry
Hall, Berkeley, CA 94720-1740 USA, Tel: +1 510 643 1819, Fax: +1 510 643 1822, E-mail:
adong@me.berkeley.edu
© IMechE 2001
26 ICED 01 - C586/422](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-45-320.jpg)
![INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN
ICED 01 GLASGOW, AUGUST 21-23, 2001
DESIGN COMMUNICATION USING A VARIATION OF THE DESIGN
STRUCTURE MATRIX
J C Lockledge and F A Salustri
Keywords: concurrent engineering, automotive engineering, design information management,
workflow management.
1 Introduction
As reported in earlier work[1]
, the authors have constructed a mechanism for structuring
design communications at a leading American automobile maker using a variation of the
Design Structure Matrix (DSM). This paper provides a formal process to create similar
matrices and outlines a mechanism for keeping participants updated on the design status. The
original work was carried out in collaboration with, and implemented at, a major American
automobile manufacturer. The new work reported herein is a prototype which has as yet to be
implemented in an industrial setting.
Many major industries base their design organizations on teams of design engineers (DEs).
The use of team-based engineering practices can substantially improve the effectiveness of
design processes, but they also introduce new complexities in terms of communications
between team members and management of tasks carried out by the teams. This is
particularly true in major industries, like the automotive industry.
Thus, while modern design practices have improved the nature of the products being
developed, they have also increased the administrativeand management burden arising from
increased complexity; what is gained in one respect can be easily lost in the other. Because
these complexities are not product complexities but, rather, complexities of design and
designing, they were not immediately recognized as important performance issues. Recently,
however, more and more interest has been shown in North America to seek a deeper
understanding of the complexities of modem design as they arise largely from these issues of
communications and task management. The authors are developing a means of managing the
design process to ensure appropriate communication between design team members is
facilitated, that task management is streamlined, and that all this can be done without placing
further burdens on the designers.
Different enterprises choose different strategies to achieve these goals. One leading
automobile manufacturer chose the strategy of re-defining its design process. While the car
manufacturer currently designs world class engines, they felt a need to reduce their time to
market. As part of this overall effort, they identified their engine design process as one for
examination andimprovement.
The authors undertook to assist the company by developing a tool to help the company's
design engineers manage engine design information more efficiently and reduce the initial
design time. We focused on the following stages of the process: the initial steps in identifying
1CED 01 - C586/584 27](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-46-320.jpg)
![a desired engine to be designed (needs analysis), coordinating the initial design (conceptual
design), and the day-to-day design process (design information flow). In particular, the
authors noted that information regarding design changes was propagated wholesale to all DEs.
This forced DEs to spend valuable time deciding if a particular design change affected the
components or systems for which they were responsible. The authors conducted interviews
with many DEs involved in engine design at the auto maker. Based on analysis of these
interviews and background research into the company's practices, the authors concluded that
a successful tool would have to be extremely flexible to respond to mid-program changes in
design priorities and objectives. The tool also had to be very simple to use so as not to burden
the DEs further with extra work.
Our solution was a variation of Steward's Design Structure Matrix (DSM)[2]
. The DSM was
chosen for of its simplicity of presentation and of construction. It essentially allows designers
to capture the relationships between structural elements, systems, subsystems, etc. of a
product in an easily understood matrix form. Once in this form, various manipulationscan be
performed on the matrix to discover features of the design, such a clusters of very high
interaction between product components. The analogy between simple matrix operations,
which all engineers understand, and design information management make the DSM quite a
useful tool.
The authors modified the DSM in two ways. First, we distinguished between the physical
components of an automobile engine (listing them on one axis) from the functional systems
and subsystems of the engine (listing them on the other axis). Identifying interactions in the
modified matrix now results in identifying the functional dependencies of the structural
components. By linking structure and function in this way, the matrix was used to identify
the stakeholders that needed to be notified of design changes or decisions. Put another way,
DEs whose tasks or designs are not affected by a design change will not be informed of the
change. This means that change information is more efficiently managed.
28 ICED 01 - C586/584
Table 1: Example Design Process Matrix (DPM)
Manufacturing
Process
Lubrication
Combustion
Cooling
Power
Conversion
Delivery
Return
Intake
Exhaust
Fuel
Delivery
Chamber
X
c
0
CO
X
X
X
8
CD
X
X
X
X
X
X
TD
I
X
X
X
X
X
X
X
X
c
'a
H
1
CO
>
X
X
X
X
X
X
CD
§
o
%
ca
X
Connecting
Rod
X
X
X
Crankshaft
X
X](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-47-320.jpg)
![2.1 Constructing a Hierarchical, Component Based DSM
The construction of a Component DSM (CDSM) has been discussed in detail by Eppinger[5]
.
In general, the first task is collecting the relevant component names and determining which
components define others. Rules for the construction of hierarchical, component DSMs has
been delineated by Sabbaghian[6]
in his work with Boeing. He points out that in constructing a
DSM that has components and sub-components, any interaction between sub-components
from different components implies an interaction between the components they belong to.
This is illustrated in Table 2 by the interaction between the Connecting Rod and the Piston
that causes the interaction with the Piston Assembly. Interactions between sub-components
both belonging to a single component do not affect the relationship of the component. This
can be seen in the interaction between the Rocker Arm and the Intake and Exhaust Valves.
These sub-components are all part of the valve train and therefore these relations do not
influence other components.
A hierarchical DSM permits a larger number of components to be addressed without
overwhelming those who are indicating the relationships. A hierarchical DSM is necessary
because the larger number of components (and sub-components) allows finer granularity of
the relationships, and the granularity of the dependencies affects how specific the messages to
users can be. It also affects the number of messages a user is likely to receive, since courser
granularity implies that all of the people involved in a component will receive information on
changes to any related component.
30 ICED 01 - C586/584
Table 2: Hierarchical ComponentDSM
Components
Connecting
Rod
Valve Train
Components
Piston
Assembly
Exhaust
Valve
Intake
Valve
Rocker
Arm
Piston
Piston
Ring
Connecting
Rod
Valve
Train
Components
1 >
-C flj
X >
W
X
<U O
II
X
<5 -
J* C
!<
Piston
Assembly
X
c
E
X
1g>
E"2](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-49-320.jpg)
![2.5 Adding Process Based Communication
Not all of the individuals who are responsible for a product have design releaseresponsibility.
Some are involvedin the later stages of manufacturing, distribution, marketing, and customer
service. Concurrent engineering [7]
discusses the need for these parties to be involved in the
design process. During this step, individuals who should be aware of design changes, but
who may not be central to the process, are added to the matrix. Additional roles are added to
the matrix above the components, indicating their interest in those specific components.
Messages will be routed to these parties as if they had release responsibility, but they are not
required to respond to the changes unlessthey see an opportunity or problem.
3 Assisting Communication
These three matrices and two mappings are the starting point for the communication routing
system. When a DE makes a change in their (sub-)component (which we'll call M) the
system will react by establishingthe following sets:
SM The systems of which M is part (from the DPM),
CM The components that M affects (from the CDSM),
Sc The systems shared by M and components of C, and
Ssc The systems that interact with systems in SC (from the SDSM).
Using the RCM messages can be routed to the individualsresponsible for components inCM
who will need to be aware of this change. The change can also be routed through the RSM to
the monitors of the system in SM. The messages to DEs would contain a statement that M was
changing and which systems (Sc) would likely be affected both directly and indirectly (from
Ssc).
An example makes this somewhat complex process clearer. Suppose we had the CDSM,
SDSM, and DPM shown in Table 4, Table 5, and Table 1. In this case, the components are
not given hierarchicallyto conserve space. If a DE made a change in the Crankshaft, we
would know from Table 1 that the Lubrication Delivery System and Power Conversion
systems would be affected and that Manufacturing would like to be kept aware of any
changes.
32 ICED 01 -C586/584
Table 4: Example Component DSM (CDSM)
Component
Piston
Block
Head
Valve Train
Valve Cover
Connecting Rod
Crankshaft
c
o
"«
h
X
X
X
.*:
8
m
X
X
X
T3
ra
03
T
X
X
X
X
Valve
Train
X
X
Valve
Cover
X
X
Connecting
Rod
X
X
Crankshaft
X
X](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-51-320.jpg)
![4 Conclusion
This paper is a formalisation of a system to route messages between members of a design
team based on a hybrid of the DSM. The routing is accomplished by examining the
underlying physical and functional requirements of the product and the interconnections
between them. This routing restricts updates to interested parties to avoid overloading the
participating engineers with data concerning every change being made in the program. The
system does this while following the same minimalist philosophy of the DSM and thus does
not require extensive data gathering or modelling. A less formally developed precursor to this
system was integrated into the design approach of a major automotive manufacturer and the
authors believe this formalisation allows this work to be replicated in other areas.
References
[1]
Lockledge, J.C. and Salustri, F.A., "Defining the engine design process", Journal of Engineering Design, 10,
1999, pp. 109-124.
[2]
Steward, D. (1981) System Analysis and Management: Structure, strategy and Design, 3, (New York,
Perocelli).
[3]
Hubka, V and Eder, E., "Engineering Design: General Procedural Model of Engineering Design", Heurista,
Zurich, Switzerland, 1992.
[4]
Steward, Donald V., "The Design Structure System: A Method for Managing the Design of Complex
Systems" IEEE Transactions on Engineering Management, vol. 28, pp. 71-74, 1981a.
Pimmler, Thomas U. and Eppinger, Steven D., "Integration Analysis of Product Decompositions",
Proceedings of the ASME Sixth International Conference on Design Theory and Methodology,
Minneapolis, MN, Sept., 1994. Also, M.I.T. Sloan School of Management, Cambridge, MA, Working Paper
no. 3690-94-MS, May 1994.
[6]
Sabbaghian, N, Eppinger, S. and Murman, E, "Product Development Process Capture and Display Using
Web-Based Technologies", Proceedings of the IEEE InternationalConference on Systems, Man, and
Cybernetics, Par 3 (of 5), pp. 2664-2669, Oct 11-14, 1998.
[7]
Kusiak, Andrew, Engineering Design: Products, Processes, and Systems, Academic Pr, 1999.
Corresponding Author: Jeffrey C. Lockledge
Institution: Wayne State University
Department: Department of Industrial andManufacturing
Engineering
Address: ManufacturingEngineering Building,
4815 Fourth St.,
Detroit, MI 48202
Phone: 313 577 3507
Email: j_lockledge@wayne.edu
© IMechE2001](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-53-320.jpg)
![Keywords :product model, design process model, functional design, knowledge management,
information management, collaborative design, co-ordination, life cycle
1 Introduction
Concurrent engineering consists in fastening development time by executing in a parallel
mode design, analysis, and industrial tasks while they were executed sequentially in
traditional development methods. This results in a shortened time to market [7]. Automotive
industry has applied successfully concurrent engineering to the most recent range of cars.
However, concurrent engineering has not taken into account the dramatic evolution in
information systems technology as the new WEB based tools allow to distribute and share
technical information through all partners involved in a project [2] [7]. This will lead to new
distributed organisations in design teams, to more innovative designs as design hypothesis can
be more quickly tested and validated by all actors at Project Wide level. For any design
problem, the best specialists from extended enterprises and partners can be appealed with full
access to authorised design data with adequate viewpoint. Those new organisations, namely
"shared engineering" or "collaborative engineering", will be supported by new "Product
Information Systems" that directly take benefits from the information technology and the
power of semantic support to information. Information technology must take into account all
legacy systems to ensure of continuous data and service access to users: amongst those legacy
systems, calculus worksheets, previously developed pieces of software... Further, many
efforts have been provided in knowledge engineering for design activities [4] [12]. Design,
like other very creative tasks, makes extensive use of many pieces of knowledge [11]. Those
pieces of knowledge must be maintained, as knowledge in design is very evolutive.
Knowledge is expressed either in the product model or in the tasks of engineering. This
knowledge must be accessible to all actors involved in the design process, must be executable
in the available design software, and must be maintained by accredited staff.
This paper provides concepts for knowledge and information product sharing during the
redesign. The second section describes what functional design and redesign are. The third
section is dedicated to the presentation of the knowledge management approach employed in
the study. The model is presented in section four. The fifth section details the web based tool
that have been used to support the methodology. In section six, the application case is
presented. Finally some conclusions and open issues conclude the paper.
ICED 01 - C586/021 35
INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN
ICED 01 GLASGOW, AUGUST 21-23, 2001
MULTI - A TOOL ANDA METHOD TO SUPPORT COLLABORATIVE
FUNCTIONAL DESIGN
S Menand and M Tollenaere](https://image.slidesharecdn.com/1166769-250603035734-a99262b9/85/Design-Management-Process-And-Information-Issues-Iced-Issues-V-1st-Edition-S-Culley-54-320.jpg)
Design Management Process And Information Issues Iced Issues V 1st Edition S Culley
- 1. Design Management Process And Information Issues Iced Issues V 1st Edition S Culley download https://ebookbell.com/product/design-management-process-and- information-issues-iced-issues-v-1st-edition-s-culley-2333538 Explore and download more ebooks at ebookbell.com
- 2. Here are some recommended products that we believe you will be interested in. You can click the link to download. Design Management Managing Design Strategy Process And Implementation Required Reading Range 1st Kathryn Best https://ebookbell.com/product/design-management-managing-design- strategy-process-and-implementation-required-reading-range-1st- kathryn-best-2341544 Design Management Managing Design Strategy Process And Implementation 2nd Edition Kathryn Best https://ebookbell.com/product/design-management-managing-design- strategy-process-and-implementation-2nd-edition-kathryn-best-5506908 Process Management In Design And Construction Rachel Cooper Ghassan Aouad https://ebookbell.com/product/process-management-in-design-and- construction-rachel-cooper-ghassan-aouad-4310798 Design And Control Of Workflow Processes Business Process Management For The Service Industry Hajo Reijers https://ebookbell.com/product/design-and-control-of-workflow- processes-business-process-management-for-the-service-industry-hajo- reijers-56902808
- 3. Process Management In Education How To Design Measure Deploy And Improve Organizational Processes Robert W Ewy And Henry A Gmitro https://ebookbell.com/product/process-management-in-education-how-to- design-measure-deploy-and-improve-organizational-processes-robert-w- ewy-and-henry-a-gmitro-5308170 Alarm Management For Process Control A Bestpractice Guide For Design Implementation And Use Of Industrial Alarm Systems 2nd Ed Rothenberg https://ebookbell.com/product/alarm-management-for-process-control-a- bestpractice-guide-for-design-implementation-and-use-of-industrial- alarm-systems-2nd-ed-rothenberg-9952062 The Whole Process Of Ecommerce Security Management System Design And Implementation 1st Edition Ronggang Zhang https://ebookbell.com/product/the-whole-process-of-ecommerce-security- management-system-design-and-implementation-1st-edition-ronggang- zhang-49061928 Business Model Management Design Process Instruments 2nd Ed Bernd W Wirtz https://ebookbell.com/product/business-model-management-design- process-instruments-2nd-ed-bernd-w-wirtz-22505694 Process Management A Guide For The Design Of Business Processes Jrg Becker https://ebookbell.com/product/process-management-a-guide-for-the- design-of-business-processes-jrg-becker-4200298
- 6. Design Management - Process andInformation Issues
- 7. WDK Publications WDKl WDK 2a WDK 2b WDK 3 WDK 4a WDK4b WDK 4c WDK 5 WDK 6 WDK 7 WDK 8 WDK 9 WDK 10 WDK 11 WDK 12 WDK 13 WDK 14 WDK 15 WDK 16 WDK 17 WDK 18 WDK 19 WDK 20 WDK 21 WDK 22 WDK 23 WDK 24 WDK 25 WDK 26 WDK 27 WDK 28 Principles of Engineering Design Bibliography of Design Science Bibliography of Design Science (continued) Terminology of the Science of Design Engineering in Six languages Case Examples(1-3) Case Examples (4-6) Case Examples (7-9) Design Methodology: Proceedings ICED 81, Rome Teaching Engineering: Proceedings ICED 81, Rome Conference Results - ICED 81,Rome J Dietrych about Engineering Design Tactics in Engineering Design (Readings) Proceedings ICED 83, Copenhagen Management of Engineering Design (Readings) Proceedings ICED 85, Hamburg Proceedings ICED 87, Boston Methodical Design of Machine Elements (Readings) Reliability of Technical Systems Proceedings ICED 88, Budapest EVAD - Evaluation andDecision inDesign (Readings) Proceedings ICED 89, Harrogate Proceedings ICED 90, Dubrovnik Proceedings ICED 91, Zurich Engineering Design Education (Readings) Proceedings ICED 93, The Hague Proceedings ICED 95, Prague EDC - Engineering Design andCreativity, Workshop Proceedings Proceedings ICED 97, Tampere Proceedings ICED 99, Munich Manual for Design Engineering (Selected preprint) Proceedings ICED 01, Glasgow
- 8. 13th International Conference on Engineering Design - ICED 01 Design Management - Process and Information Issues 21-23 August 2001 Scottish Exhibition and Conference Centre, Glasgow, UK Organized by The Institution of Mechanical Engineers (IMechE) Sponsored by BAE SYSTEMS Co-sponsored by The Institute of Engineering Designers The American Society of Mechanical Engineering (ASME) Published by Professional Engineering Publishing Limited for The Institution of Mechanical Engineers, Bury St Edmunds and London, UK.
- 9. First Published 2001 This publication is copyright under the Berne Convention and the International Copyright Convention. AH rights reserved. Apart from any fair dealing for the purpose of private study, research, criticism or review, as permitted under the Copyright, Designs and Patents Act, 1988, no part may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, electrical, chemical, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. Unlicensed multiple copying of the contents of this publication is illegal. Inquiries should be addressed to: The Publishing Editor, Professional Engineering Publishing Limited, Northgate Avenue, Bury St Edmunds, Suffolk, IP32 6BW, UK. Fax: +44 (0) 1284 705271. © 2001 The Institution of Mechanical Engineers, unless otherwise stated. ISBN 1 86058 355 5 A CIP catalogue record for this book is available from the British Library. Printed by The Cromwell Press, Trowbridge, Wiltshire, UK The Publishers are not responsible for any statement made in this publication. Data, discussion, and conclusions developed by authors are for information only and are not intended for use without independent substantiating investigation on the part of potential users. Opinions expressed are those of the Author and are not necessarily those of the Institutionof Mechanical Engineers or its Publishers.
- 10. Conference Organizing Team Steve Culley, Bath University,UK Alex Duffy, Strathclyde University,UK Chris McMahon, Bristol University,UK Ken Wallace, Cambridge University, UK Scientific Advisory Board A Chakrabarti, University of Cambridge, UK R Anderl, Technische Universitat Darmstadt, Germany R Andrade, Universidade Federal do Rio de Janiero, Brasil M M Andreasen, Technical University of Denmark, Denmark E K Antonsson, Caltech, USA P Badke-Schaub, Universitat Bamberg, Germany A H Basson, University of Stellenbosch, South Africa H Birkhofer, Technische Universitat Darmstadt, Germany L T M Blessing, University of Cambridge, UK G Blount, Coventry University, UK A Breiing, Swiss Federal Institute of Technology, Switzerland S Burgess, University of Bristol, UK J Busby, Cranfield University, UK M Cantamessa, Politecnico di Torino, Italy H H C M Christiaans, Delft University of Technology, The Netherlands P J Clarkson, Universityof Cambridge, UK J Deans, University of Auckland, New Zealand P Deasley, Cranfield University, UK W E Eder, Royal Military College of Canada, Canada K Ehrlenspiel, Technische Universitat Munchen, German) S D Eppinger, Massachusetts Institute of Technology, USA D G Feldmann, Technische Universitat Hamburg- Harburg, Germany S Finger, Carnegie Mellon University, USA P Frise, University of Windsor, Canada I Gibson, National University of Ireland, Ireland H Grabowski, Universitat Karlsruhe, Germany G Green, University of Galsgow, UK K-H Grote, Otto-von-Guericke-Universitat Magdeburg, Germany P H K Hansen, Aalborg University, Denmark I Horvath, Delft University of Technology, The Netherlands St Hosnedl, University of West Bohemia in Pilsen, Czech Republic V Hubka, Heurista, Switzerland B Ion, University of Strathclyde, UK D Jiati, 720 Lab, Bejing University of Aeronautics and Astronautics, Peoples' Republic of China N Juster, University of Strathclyde, B Katalinic, TU Vienna, Austria T Kiriyama, Stanford University, USA S S Kok, Nanyang Technological University, Singapore L Leifer, Stanford Centre for Design Research, USA B Lewis, University of Melbourne, Australia Yn Li, Sichuan University, Peoples' of Republic China Uo Lindemann, Technische Universitat Munchen, Germany M L Maher, University of Sydney, Australia M Mantyla, Helsinki University of Technology, Finland D Marjanovic, University of Zagreb, Croatia H Meerkamm, UniversitatErlangen-Nurnberg, Germany M Meier, ETH-Zurich, Switzerland F Mistree, Georgia Institute of Technology, USA M Norell, Royal Institute of Technology, Sweden M Ognjanovic, University of Belgrade, Yugoslavia K Otto, Massachusetts Institute of Technology, USA U Pighini, University of Rome 'La Sapienza', Italy D F Radcliffe, The University of Queensland, Australia Y Reich, Tel Aviv University, Israel A Riitahuhta, Tampere University of Technology, Finland R Rohatynski, Technical University of Zielona Gora, Poland N Roozenburg, Delft University of Technology, The Netherlands E Rovida, Politecnico di Milano, Italy A Samuel, University of Melbourne, Australia J W Schregenberger, ETH Honggerberg, Switzerland P Sen, University of Newcastle, UK M Simon, Sheffield Hallam University, UK J Simmons, Heriot-Watt University, UK L Stauffer, University of Idaho, USA K G Swift, University of Hull, UK O Tegel, TU Berlin, Germany G Thompson, UMIST, UK D L Thurston, University of Illinois at Urbana- Champaign, USA M Tollenaere, ENS Genie Industriel, France T Tomiyama, The University of Tokyo, Japan D G Ullman, Oregon State University, USA S Vajna, Otto-von-Guericke-Universitat Magdeburg, Germany C Weber, Universitat des Saarlandes, Germany M P Weiss, TECHN1ON, Israel P M Wognum, University of Twente, The Netherlands K Wood, The University of Texas, USA M M F Yuen, Hong Kong University of Science and Technology, Peoples' Republic of China
- 11. Industrial Advisory Board R Bodington, BAE Systems Advanced Technology Centre, UK D Knott, Rolls-Royce plc, UK N Brenchley, Forward Industries, UK I Liddell, Buro Happold, UK M Brown, BAE Systems Research Centre, UK P W Liddell, Lockheed/BAe, USA P Burnell, EPSRC, UK K Mashford, Interfacing Limited, UK I Chatting, GKN Westland Aerospace, UK I Milbum, Nissan European Technology Centre Limited, UK A Court, Portacel, UK J Mudway, TRW ASG Lucas Aerospace, UK P Fearis, The Generics Group Limited, UK Y Neuvo, Nokia Group, Finland P Ferreirinha, MIRAKON, Switzerland F O'Donnell, Scottish Enterprise Lanarkshire, UK D Foxley, Royal Academy of Engineering, UK C Pearce, INBIS Group plc, UK E Frankenberger, Heidelberger Druckmaschinen AG, B Prasad, CERA Institute, USA Germany D Rimmer, Pilkington Optronics Limited, Denbighshire, UK N Grant, BAE Systems Operations, UK D Robson, Scottish Enterprise, UK J Gunther, Hilti AG, Liechtenstein M Shears, Ove Arup Partnership, UK C Hales, Triodyne Inc., USA L Styger, STYLES RPD, UK L Hein, Technical University of Denmark, Denmark I Yates, UK N Kohlhase, LEWA Herbert Ott GmbH + Co., Germany
- 12. Contents Preface Knowledge and Information Management Information Management Improving access to design solution spaces using visualization and data reduction techniques P M Langdon and A Chakrabarti Supporting non-structured graphical information in integrated design team E Blanco and M Gardoni Automatic composition of XML documents to express design information needs A Dong, S Song, J-L Wu, and A M Agogino Design communication using a variation of the design structure matrix J C Lockledge and F A Salustri Multi - a tool and a method to support collaborative functional design S Menand and M Tollenaere Information flow in engineering companies - problems andtheir causes C M Eckert, P J Clarkson, and M K Stacey Design case relevance in quantity dimension space for case-based design aid T Murakami, J Shimamura, and N Nakajima A web-based information tool for application engineering J Schmidt and D G Feldmann Knowledge Representation andManagement An agent environment to support co-ordination between design actors P Girard and C Merlo Developing a support system for novice designers in industry S Ahmed and K M Wallace Using domain knowledge to support design requirements elicitation M J Darlington, S J Culley, and S Potter Towards pragmatic approaches for knowledge management in engineering - theory and industrial applications K-D Thoben, F Weber, and M Wunram Effective abstraction of engineering knowledge for KBE implementation P Bermell-Garcia, I-S Fan, G Li, R Porter, and D Butter 3 3 11 19 27 35 43 51 59 67 67 75 83 91 99 xii
- 13. New techniques for design knowledge exploration - a comparison of three data grouping approaches P C Matthews, P M Langdon, and K M Wallace Computer-supported systematic design and knowledge in the early design phase E Frankenberger DEKAS - an evolutionary case-based reasoning system to protection scheme design G West, S Strachan, J McDonald, A H B Duffy, J Farrell, and B Gwyn Knowledge for product configuration K Hadj Hamou, E Caillaud, J Lamothe, and M Aldanondo An operational model for design processes M Y Ivashkov and C W A M van Overveld Classifications and Taxonomies A common language for engineering design practice and research A Samuel, J Weir, and W Lewis Using situation theory to model information flow in design Z Wu and A H B Duffy Shape matching and clustering S Lim, A H B Duffy, and B S Lee The product develoment process ontology —creating a learning research community P K Hansen, A Mabogunje, O Eris, and L Leifer The application of an automatic document classification system to aid the organizers of ICED 2001 A Lowe, C A McMahon, T Shah, and S J Culley Analysis and classification methodology for objectifications in collective design processes A Verbeck and K Lauche Design Reuse Modularity in support of design for re-use J S Smith and A H B Duffy Capturing and classifying information in undergraduate design team projects P A Rodgers Incorporating incentives into design documentation tools T Lloyd and L Leifer 107 115 123 131 139 147 147 155 163 171 179 187 195 195 203 211
- 14. Scaling-up domain knowledge representation in the development of knowledge intensive CAD for proactive design for manufacture X-T Yan, J Borg, and F Rehman Re-using knowledge - why, what, andwhere J S Smith and A H B Duffy Documentation and evaluation in early stages of the product development process L Schwankl Mapping experience - learning from experience of peers through socio- technical interactions T Liang, D G Bell, and L J Leifer Transfer of experience in critical design situations P Badke-Schaub, J Stempfle, and S Wallmeier Organization and Management of Design Project Management Product development models for shorter lead times and more rational processes - its effects on the work situation for project managers and project group A Zika-Viktorsson and J Pilemalm A multi-project management approach for increased planning process F Marie and J-C Bocquet Applying conceptual design methods to engineering management P Hughes, C Burvill, and R Hughes Finding and implementing best practices for design research activities M Gardoni and C Frank Project Strategy and Management Late point differentiation analysis for configurable products T A Lehtonen, A O Riitahuhta, and J M Malvisalo On the design of services R Andrade Functional products create new demands on product development organizations O Brannstrom, B-O Elstrom, and G Thompson How missions determine the characteristics of product development methodologies B Bender, B Bender, and L T M Blessing 219 227 235 243 251 261 261 269 277 285 293 293 299 305 313
- 15. Planning and Workflow Management Visualization techniques to assist design process planning P J Clarkson, A F Melo, and C M Eckert A product and process model supporting main and sub-supplier collaboration B Fagerstrom and H Johannesson Identifying and analysing changes in a dynamic company S Suistoranta Design process planning using a state-action model A F Melo and P J Clarkson Concurrent Engineering and Integrated Product Development Integrated newproduct development - a case-based approach R Valkenburg and J Buijs Material instrumentation forinter-trade co-operation - a source of innovation: application in the domain of painting and varnish finishes N Stoeltzlen, D Millet, and A Aoussat Geometry users from a process perspective F Fuxin Concurrent design of product and package- extending the concept of IPD C Bramklev, R Bjarnemo, and G Jonson Distributed Design/Supply Chain Integration A framework for distributed conceptual design A Schueller and A H Basson A system for co-ordinating concurrent engineering R I Whitfield, G Coates, A H B Duffy, and W Hills Distributed product development - a case study in inter-organizational SME business networks J Pilemalm, S Gullander, P Norling, and A Ohrvall-Ronnback Organizational design - a tool for evaluating alternative extended enterprise structures A McKay and A de Pennington Design Teams Cultural issues in aerospace engineering design teams K H Payne and P J Deasley Supporting the teamwork by new means of the information technology A M Kunz, S Muller, T Kennel, K Lauche, and K Mbiti The importance of informal networks to effective design management N J Brookes, P Smart, and F Lettice 321 321 329 337 345 353 353 361 369 377 385 385 393 401 409 417 417 425 433
- 16. Managing uncertainty in design communication M K Stacey and C M Eckert Managing the integration between design, research, and production in the automobile industry H V de Medina and R M Naveiro Researching the thinking process in design teams - an analysis of team communciation J Stempfle and P Badke-Schaub Towards a science of engineering design teams A Mabogunje, K Carrizosa, S Sheppard, and L Leifer Dimensions of communication in design C M Eckert and M K Stacey A statistical study of how differing levels of diversity affect the performance of design teams A G Carrillo Management of the Clarification Phase Requirements engineering - laying thefoundations for successful design G A Thomson The organization and management of engineering tenders G Barr, J H Sims Williams, S C Burgess, and P J Clarkson Modification of a methodological design tool for the developing country scenario - a case study in product definition K M Donaldson and S D Sheppard An approach for structuring design specifications for complex systems by optimization C Grante, M Williander, P Krus, and J-O Palmberg An engineering approach for matching technology to product applications J B Larsen, S P Magleby, and L L Howell Performance Evaluation Financing innovation in co-operation projects P Link and S Spiroudis Performance management at design activity level F J O'Donnell and A H B Duffy A metrics methodology developed in co-operation with industry M W Lindley, M Muranami, and D G Ullman Improvement of engineering processes S Vajna, D Freisleben, and M Schabacker 441 449 457 465 473 481 489 497 505 513 521 529 529 537 545 553
- 17. Process performance measurement support - a critical analysis M K D Haffey and A H B Duffy Risk and Uncertainty Management The methodology for system integrity in design J K Raine, D Pons, and K Whybrew Change prediction for product redesign P J Clarkson, C Simons, and C M Eckert Survey of current UK practice in managing technical design risk R Crossland, C A McMahon, and J H Sims Williams Development of an 'IDEA' for safety D Vassalos, I Oestvik, and D Konovessis How mutual misconceptions between designers and operators cause accidents in hazardous installations J S Busby, R E Hibberd, P W H Chung, B P Das, and E J Hughes A project view of the handling of uncertainties in complex product development organizations R Olsson Decision-making - howto avoid dysfunctions? Howto analyse dysfunctions? How to improve an organization by its dysfunctions? J Stal-le Cardinal, M Mekhilef, and J-C Bocquet Preliminary design of a risk management decision tool J M Feland Authors' Index 561 569 569 577 585 593 601 609 617 625 633
- 18. Preface This is one of four books resulting from the contributions to the 13th International Conference on Engineering Design (ICED 01). The conference was held in August 2001 in the Scottish Exhibition and Conference Centre located on the River Clyde in Glasgow - the ideal place to hold the first ICED of the nowmillennium. The ICED conference series was initiated by Workshop Dcsign-Konstruktion (WDK) in 1981 with the first conference in Rome. From the very beginning, the aim of ICED was to offer a platform for the discussion of new trends, developments, and research findings in the areas of new product development, design support techniques, design processes, design science, and design education. The conferences have been held in eleven different countries and have become one of the most pre-eminent conferences in the field of Engineering Design, with the last two conferences being held in Tampere, Finland, in 1997 and in Munich, Germany, in 1999. Both these conferences attracted well over 500 delegates from both academic institutions and industrial organizations. Nearly all the leading authorities in the field of Engineering Design attend to report their latest findings and exchange current ideas with colleagues. All conferences have focussed on the process of planning, developing and designing technical systems and products. ICED covers all aspects and disciplines of engineering design, from general product development and innovation to feature-based geometric reasoning and design for later life-phases. As engineering design is a process to which many disciplines are contributing, an additional emphasis has been placed on design management, organization, teams, and individuals. Over the years ICED conferences have become the forum for establishing, maintaining, and improving contacts and co-operation between researchers and engineers from countries all over the world. It is self evident that the engineering design process has changed to meet the challenges of globalization, increasing international competition, and the need for sustainable development. Equally the performance and quality of engineering products have improved in many aspects, time to market, performance, reliability, reduced environmental impact, etc. If the improvements are to be maintained, the elements that contribute to the product development process must continue to be studied and enhanced. Improvements in the engineering design and its process have been supported by theories and methods developed by research groups around the world. The research is beginning to mature into an overall and consistent understanding of engineering design as will be seen in the pages of the four books. However the results are still fragmented and there is a need to unify the findings, and to ensure that these findings are transferred into industry. The theme chosen for ICED 01 was Unifying Engineering Design - Building a Partnership between Research and Industry. The organizing team received 664 Abstracts and this resulted in some 325 full papers. All papers are eight pages in length and went through a double blind review of the abstracts and a double review of the full papers. The books consist of contribution papers from some 35 countries. xiii
- 19. DESIGN MANAGEMENT This book consists of some 13 topics and really has an overarching theme of the management of the process and the information that supports the process. It covers knowledge and information management at all levels and the organization and management issues associated with the design activity itself. Books in the series Book 1 Design Research Book 2 Design Management Book 3 Design Methods Book 4 Design Applications A large number of people and organizations have helped with the conference. The organizing team would like to express their thanks to all who have contributed to the content and execution of ICED01 in whatever way. Steve Culley Alex Duffy Chris McMahon Ken Wallace
- 20. Knowledge and Information Management Including sub-sections: Information Management Knowledge Representation and Management Classifications and Taxonomies Design Reuse
- 21. This page intentionally left blank
- 22. INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN ICED 01 GLASGOW.AUGUST21-23, 2001 IMPROVING ACCESS TO DESIGN SOLUTION SPACES USING VISUALIZATION AND DATA REDUCTION TECHNIQUES P M Langdon and AChakrabarti Keywords: Visualisation, clustering, synthesis, design information management, information analysis, classification and retrieval 1 Introduction Designers only explore a few solutions in depth at the conceptual stage [1]. Despite this, evidence suggests that a thorough exploration of a solution space is more likely to lead to designs of higher quality [2]. FuncSION [3] is a computational tool that synthesises a wide range of solutions to a class of mechanical design problems involving transmission and transformation of mechanical forces and motions that are specified as inputs and outputs. It uses a set of primary functional elements along with combination rules to create anexhaustive set of solutions in terms of their topological and spatial configurations. Previous research has demonstrated FuncSION's potential for generating novel solution ideas that designers had not thought of. However, it was found that the large number of ideas generated could not be meaningfully explored, while their representation proved too abstract to visualise. Effective support for conceptual design should help designers obtain a thorough overview of the solution space, as well as a detailed understanding of its individual solutions. However, the greater the variety and number of solutions to be explored, the less likely it is that a detailed understanding of the potential of all individual solutions will be achieved. The DESYN software described in this paper encapsulates FuncSION with a Graphic User Interfacce (GUI) [4]. The overall aim of this work is to test the extent to which DESYN is capable of assisting designers in their exploration of large solution spaces such that an overview of the entire space is obtained while at the same time facilitating understanding of the individual solutions contained in it. 2 Background A paper presented at ICED99 [4] described a scheme adopted in order to solve the above problems. The problem of exploring large combinatorial spaces is an unresolved issue in computer aided synthesis research, which is further complicated by the difficulty in displaying large volume of information [5]. The approach adopted was a novel method of clusteringthe solution configurationsto reduce the space of solutions that the designer needs to consider in order to get an overview of the entire space of solutions [6]. This was done by presenting the designers with representative solutions that were by-products of the clustering process. In this way, large numbers of solutions can be summarised by a small number of cluster exemplars of prototypes. ICED 01 - C586/223 3
- 23. A number of previous approaches have adopted rule-based heuristics for the generation of solution compositions in an unconstrained space (See, for example, Campbell et al, 1999)[7] [8][9]. However, the approach adopted here assumes exhaustive generation of solutions in a partially constrained space with the use of clustering as a data reduction and representation. Because of this, all solutions are, in principle, available to the designer through interaction with the systems GUI. In the authors' earlier paper, some initial validation of the cluster algorithm was reported focussing on whether the system's clusterings of solutions were intuitive and whether the clusterings suggested by the system correspond to designers' own partition of the solution space. Initial experiments examined a number of DESYN clusterings of two sets of 20 solutions resulting from a synthis using 0-5 elements per solution from a choice of < 4 elements. Figure 1 is an example diagram of the outputs of the same clustering algorithm for a smaller 6 solution set synthesised using the elements wedge, cam and lever mechanisms. Clustering was based on a Euclidian distance metric operating on a count of features in each solution from a feature set of all possible feature pairs. Figure 1.Cluster table for 2 to 5 clusteringsof a 6 solutions for a problem using Wedge, Cam and Lever elements. The arrows indicate the solutions that leave the 3 cluster solution to form new clusters. On the left of the diagram the six possible solutions output by the synthesiser are enumerated. The vertical columns show increasing number of clusters in the solution set. The cells show the cluster membership for each solution. Each cluster has a representative solution that is denoted by circling. Finally,the box in the corner of cells shows the average distance of the representative to all the other members of the cluster. The right hand diagram shows a Venn type representation of the 3,4 and 5 cluster solutions. Solution sets for the larger 5 element problems were presented to 5 subjects as printed words with illustrative diagrams. Subjects were required to form groupings of the 20 solutions that corresponded to their judgements of those that seemed to them to be similar on the basis of their engineering experience. The subject's groupings were scored for the percentage similarity of groupings with the DESYN clusterings of the same set. This was to test whether designers found the system's clustering of solutions intuitive, and whether the clustering suggested by the designers correspond to their own partition of the solution space. This clustering was based on an element-pair feature count (focusing on the type of interfaces possible as design elements in combination),and provided an average commonality, between designer's clustering and the 4 ICED 01 - C586/223
- 24. method's, of 74% in contrast to 55% commonality yielded by comparison with a random clustering. However, this evaluation was carried out using only the topology, rather than the 3-D configurations of the solutions. Evaluation of the approach is further extended in this paper (see section 3.2) using: (1) 3-D configurations displayed by the system as displays of force and motion solution chains; (2) Graphic representations of the clustered solution space. The goal of this evaluation is to find whether or not this clustering-based technique improves a designer's overview of the entire solution space, and whether the software facilities assist their understanding of the solution space. 3 Current Developments Current developments include further development of the GUI and visualisation support, and further evaluation of DESYN, which are described below. 3.1 User interface development The visualisation utilises a 2D 'star' representation of clusters (Figure 2), and a pseudo-3D display of a component chain schematic (Figure 3) that we have developed to improve access to the functional synthesis software. The former is used to aid visualisation of the spatial relationships between the component interfaces, while the latter is intended to aid the understanding of the grouping of functional solutions by similarity [10, 11]. Figure 2. The DESYN Graphic User Interface Clustering Tool In conjunction with this, a 3D visualisation for displaying an overview of the solution space and the spatial layouts of selected solutions resulting from the synthesis is under development. ICED 01 - C586/223 5
- 25. When implemented, this will display a 3D schematic representation of individual solution chains with a symbolic convention used to indicate locations and directions of force and rotation. Elements will represented by shaded cylinders and interfaces between elements are represented by spheres. Figure 3. The Pseudo 3D visualisation interface The orientation, direction, and sense of forces will be represented by arrow triplets. The Nominal direction of rotation or force was represented by 2D sprites. Elements will be fitted into the mechanism boundaries by an algorithm that distributes the element lengths evenly into the available space. Figure 3 represents a schematic of a concept that has four elements, nominally oriented as shown by the arrows, such that an input rotation is taken by the first (shaft-like) element, and passed on to the second (crank-like) element, which passes the resulting translation via two tie rod-like elements to the output point. The 3D representation and facilities for manipulationof individual solutions are intended to provide designers a more detailed understanding of the individual solutions than that provided by the more abstract text-based representation. 3.2 Evaluation Each of two groups of designers (Gl and G2) were asked to individuallyinspect the solutions set generated by FuncSION in two conditions by using the softwares Graphic User Interface. The unstructured group were presented with a list representation of the solution set and the structured group received the representation in the form of 2D "sun-and-planet" graphic representing clusters calculated by the algorithm, the representative central member and the average distance of cluster members from that medoid (Figure 2). The task required the designers to select, using the representation available to them, a set of solutions to the specified problem that were both different from each other and formed a set completely representative of all solutions. In the unstructured condition the designers were given a text field on the interface into which they could fetch groups of solution on demand. This was managed by the use of a button that simply obtained five solutions from the total set and placed them at the bottom of the list on 6 1CED 01 - C586/223
- 26. the screen. No indication of the total number of solutions was given and the solutions were not presented in any ordering linked to their functional structure. Hence, the designers were allowed to select as few or as many solutions as they liked. The task further required that the designers selected individual solutions form the list (left, Figure 4) that they felt met the criteria. This was made on a point-and-click basis and the resulting set stored in a further text field (right, Figure 4). Figure 4. The list representation experimentalgroup interface. In the structured condition the designers performed the same task but interacted with a 2D cluster representation of the solutions set. Dwelling the cursor on a central representative "sun" member of a cluster lead to a list of the cluster solution members appearing in the upper right text field. Dwelling on the numbered "planet" members highlighted the location of the solution in the list. Figure 5. The list representation experimentalgroup interface. Again, the task further required that the designers select individual solutions form the list (top right, Figure 5) that they felt met the criteria. This was made on a point-and-click basis by clicking on the member "planets" and the resulting set stored in a further text field (bottom right, Figure 5). In both conditions the designers were able to delete members of their selected set at will. 3.3 Data analysis technique Results in our previous study [4] suggested that the clustering solution for small problems had some psychological validity as a grouping of the solution space correlated highly with designers groupings. Therefore, in the present case, if a solution chosen by a designer belonged to a cluster generated by the computer, then it was assumed that the designer had an overview of at least that cluster. If there was a better match between the computed clusters ICED 01 - C586/223 7
- 27. and solutions listed by the designers in the list condition (Gl) rather than with those listed by the designers in the clustered condition (G2),then it could be concluded that designers had a better overview of the solution space using clustering than without. This would indicate that a designer could miss innovative solutions when they did not use the data reduction technique. For the list of concepts written by each designer, solution clusters were generated using the clustering algorithm, taking the size of the list as the number of clusters. A comparison was then made between the list of concepts of the designer with the solution clusters generated by the algorithm to find how many solutions from the designer's list belong to distinct computed clusters. The proportion of the solution space covered by the designer, taken as a measure of the overview obtained by him, was then calculated as the ratio of the number of clusters 'covered' by the designer to the total number of clusters. An average proportion of solution space covered by designers in each group was then calculated by dividing the total of the ratios (for all the designers in the group) by the number of designers. 4 Results List Condition (G1) Subject S1 S2 S3 Total Average No. 3 3 7 13 4.3 Matched 1 1 6 8 2.7 Ratio 1/3 1/3 6/7 21/32 0.51 Clustered Condition (G2) Subject S4 S5 S6 Total Average No. 3 3 7 11 3.7 Matched 1 1 5 9 3.0 Ratio 1/3 1/3 5/7 21/29 0.46 Table 1. Cluster commonality data for the list conditionand clustered conditions The results obtained are tabulated in Table 1. Very little difference was obtained between the numbers of clusters sampled by the designers in each experimental group and this was reflected by the ratios of computed and designer sampled clusters (Table 1.). Although no inferential statistics were calculated due to the small size of the sample (n = 3 in each group) it is evident from the table that many of the designers in both groups chose a small set of three solutions that sampled only one cluster of the computed solutions. 5 Discussion There was no evidence that the designers sampled the solution space more effectively using the 2D cluster visualisation GUI when measured in terms of the similarity between the clusters they sampled and the complete optimal clusterings that had been previously found to correspond to designers' intuitive groupings. The principal result suggests that the use of an assistive aid combining data reduction technique with graphic visualisation did not lead to a more complete sampling of the solution space for the highly constrained synthesis problems 8 ICED 01 - C586/223
- 28. tested in these experiments. However, it was observed that the time to complete the task was significantly shorter (about 50%) in the clustered condition. Although this was not measured accurately, it may suggest that the list condition designers required more time to gain an overview of the space than the designers for whom the solution space was spatially laid out. The overwhelmingly popular solution represented three sub-mechanisms that give key two element combinations that re-occur. These included mechanisms that allowed orthogonal changes in force direction, such as lever to lever; lever to cam; or lever to screw links. The reports collected from these designers suggested that the criteria applied was simplicity of solutions, ignoring repetitions of sub-mechanisms and spatially translating force to force elements such as tie-rods. The effect of prompting the designers for more solutions in these cases led to the choice of variants on these mechanisms with tie-rods added to circumvent possible spatial constraints. The limitations of the evaluation lie in the small number of designers sampled and the use of a single problem. In addition the previous evaluation [2] had established a commonalityof 75% between the software-clustered groups and the designers intuitions as indicated by a paper- based solution-sorting task. In addition, the clustering method was based on a feature based on a count of pairs of solutionelements. Other features of the solution chain could be used for clustering to further test the effectiveness of the clustering approach. It was also clear from the designers performance that a more realistic task would involve a realistic design task carried out over a longer period. In addition to this, the pseudo 3D visualisation software was not integrated into the DESYN interface such that visualisation of individual solution chains was possible during the trial. It was evident that such a visualisation tool would have assisted the designers understanding of the individual solutions. Work is currently underway with a larger group of designers, sampling a wider range of problems over a range of sizes of mechanisms and difficulties of task. 6 Conclusions and further work A software system for assisting the visualisation of alternative solutions to mechanical design problems involving transmission and transformation of mechanical forces and motions was successfully implemented. This utilised a clustering algorithm for the purpose of data reduction and visualisation of a large solution space. An empirical evaluation of this system examined whether the designers' sampling of the known solution space was effectively assisted by an element-pair clustering represented in a 2D display of clusters, in conjunction with a pseudo-3D visualisationtechnique. There was no evidence for any improvement in the number of clusters sampled when the interface provided a list of solutions as opposed to a 2D cluster membership diagram, though a substantial improvement in time to complete the task was noted. Two strategies were observed in the designers tested. The predominant strategy involved listing 'elemental' sub- mechanisms that were capable of orthogonal changes in force direction. These designers ignored repetitions of sequences or complex combinations as well as elements providing linear or parallel force transformations. These second strategy group appeared to list solution sets that were clearly distinctive sequences, because of simplicity or unique element combinations. The small number of designers sampled does not enable generalisation to designers at large as the results may reflect individual strategies. It is also possible that designers' choices were ICED 01 - C586/223 9
- 29. affected by the lack of a genuine engineering task in the short trials. Firmer conclusions will be facilitated by the collection of further data using an enhanced assistive interface and more realistic and rigorous design tasks. 7 References [1] Chakrabarti, A. and Wolf, B., Reasoning with Shapes: Some Observations from a Case Study", Proc. 1995 ASME Design Engineering Technical Conferences: (9th Intl. Conf. on DTM), DE-Vol. 83, Vol.2, pp-315-322, 1995. [2] Fricke, G., Experimental investigation of individual processes in engineering design, Research in Design Thinking, (N.Cross, K. Doorst and N. Roozenburg eds.) Delft University Press, pp 105-109, 1992. [3] Chakrabarti A., and Bligh, T.P. "An Approach to Functional Synthesis of Design Concepts: Theory, Application, and Emerging Research Issues", AI in Engineering Design, Analysis and Manufacturing, Vol. 10, No. 4, pp-313-331, 1996. [4] Langdon, P., and Chakrabarti A. "Browsing a large solution space in breadth and depth", A. 12th International Conference on Engineering Design (ICED 99), Munich, Germany, v3 p. 1865-1868, 1999. [5] Johnson,B., & Shneiderman, B. "Tree-maps: A space-filling approach to the visualisation of hierarchical information structures". Proc. IEEE Visualization'91. IEEE, Piscataway, NJ, 284-291, 1991. [6] Kaufman, L. & Rousseeuw, P.J., Finding Groups in Data. Wiley Series in Probability and Mathematical Statistics. John Wiley and Sons, Inc., 1990. [7] Campbell, M.I. ,Cagan, J., Kotovsky, K., A-Design: An Agent-Based approach to conceptual design in a dynamic environment. Research in Engineering Design, Vol. 11, pp 172-192, 1999. [8] Finger, S., and Rinderle. J.R., A transformational approach to mechanical design usinga bond-graph grammer. In Design Theory and Methodology, DTM 89, vDE Vol. 17. pp 107-115, 1989. [9] Bracewell, R.H., Sharpe, J.E.E. Functional descriptions used in computer support for qualitative scheme generation - Schemebuilder. AI EDAM Journal - Special Issue: Representing Functionality in Design 10(4): p. 333-346, (1996). [10] Robertson G.G., Card S.K., Mackinlay, J.D., Information visualization using 3D interactive animation. Communications of the ACM, Apr 1993, Vol.36, No.4, pp.57-71, 1993. [11] Mackinlay,J.D., Rao.R, Card, S.K., An Organic user interface for searching citation links. Human Factors in Computing Systems (CHI) Conference Proceedings, Vol.1, pp.67-73, ACM, New York, NY, USA. 1995. Corresponding author's name: Dr. Patrick Langdon Engineering Design Centre, Cambridge University Engineering Department, Trumpington Street, Cambridge CB2 1PZ, UK, Tel: +44 1223 766961 Fax: 444 1223 332662, E-mail: pml24@eng.cam.ac.uk, URL:http://www-edc.eng.cam.ac.uk/people/pml24.html © Cambridge Engineering Design Centre2001 10 ICED 01 - C586/223
- 30. INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN ICED 01 GLASGOW, AUGUST 21-23, 2001 SUPPORTING NON-STRUCTURED GRAPHICALINFORMATIONIN INTEGRATED DESIGNTEAM E Blanco and M Gardoni Keywords: design information, design understanding, hypermedia and multimedia, knowledge management The aim of this paper is to focus on the use of draft and sketches in the group understanding within Integrated-Team. We suggest specifications of a communication tool that supports and structures numerical drafting and treatment for capitalisation of those drafts connected to messages. 1 Evolution of Engineering Information Requirements Traditionally, engineering activities are performed in a sequential order. Over the last ten years, companies have tended to apply the Concurrent Engineering approach (CE) in order to drastically reduce the time-to-market of their products [1]. This approach is opposed to the sequential engineering approach because they have respectively two fundamental ways of working. In sequential engineering approach, the work starts at the reception of the results of the early stage when CE is based on information exchanges. Those exchanges are mainly performed verbally face-to-face or on the phone. Unfortunately, this information is therefore poorly controlled. This term "control" can be characterised in terms of four criteria [2] : - Information Structuring: it relies on a formal conceptual scheme which organise information at appropriate places. The evaluation criteria are the easyness to organise information in an intuitive and logical way and to be able to manage information at separate locations. Information Sharing: ability of "pushing" information. - Information Access: ability to "pull"information. - Information Capitalisation: ability to store and process information for later re-use, we assume that it must comply with the cycle of 'company knowledge capitalisation', i.e. locate, memorise, use information and update information. Taking into account these new requirements, we characterise the type of information exchanged in Integrated Team. We will focus here on information Structuration model. In order to meet the rigour needs of companies without going down on a too fine level of granularity, we choose an instructional design of the information significance. We then consider that the construction of a sentence corresponds to combine instructions formulated in term of variables, which provide a sense to the statement. Exchanged information is then an abstracted entity, a theoretical object which consists of [3]: ICED 01 - C586/418 11
- 31. - Linguistic components which build the significance of information starting from instructions. - Rhetoric components which bring a sense to information by addition of contextual information. Figure 1. Instructional design of the information significance Thanks to this instructional design of the information significance, we characterise different types of information [2] : Structured-Information (SI), linguistic and rhetoric components of the 57 are generally imposed. - Semi-Structured-Information (SSI), linguistic components of the SSI are little formalised and rhetoric components could be parsimonious. Non-Structured-Information (NSI), the NSI are very little formalised and the rhetoric components can be very light if they ensure a sufficient degree of relevance for the comprehension of information by the receiver. The MICA approach [4] (a specific interactive messaging system) has been developed and experimented in order to harness of NSI and to capitalise on relevant information exchanges. Also a Groupware tool called MICA, was created through an Intranet. It has been implemented and put into operation in an engineering team of twenty people in May 1998. Some return on experience has already shown improvement of the efficiency of the Integrated Team. Nevertheless, this kind of capitalisation from linguistic data is limited because of the graphical NSI lack. Sketching takes a large place in the group understanding of technical problems. Goel [5] also argues that freehand sketches facilitate creative and explorative work at the early stage of design, because they are ambiguous semantically and syntactically dense. Sketches could be considered as Graphical Non Structured Information (GNSI). They are at the same time models of the product and communication vectors. MICA only takes into account linguistic data but does not take care of GNSI management. This is today one of the actual limit of the MICA approach and more generally of Knowledge Management systems [6]. Generally Groupware solutions for interactive sketching have to be improved. 2 GNSI in collaborative design In order to analyse the role of GNSI in collaborative design we have carried out a design experiment [7]. This experiment was based upon the distributed design model [8]. Three roles 12 ICED 01 - C586/418
- 32. were represented, the functional, structural and machining roles. A camera has recorded the whole progress of the design. The work began with the requirement list supplied by the client a few days before the experiment. It took six hours to implement the detailed drafts of each part of the product in order to manufacture it. 2.1 Sketches as IntermediaryObjects of the designprocess In order to observe and analyse the design processes, we suggest to start with the Intermediary Objects (IO) which, circulating at any given moment between the actors of the process, can be seen as resulting from their design work but also as supporting and highlighting it [9], [10]. In modelling the future product they also act as communication vectors between the product designers. These two aspects are so indissociable in the reality of the process that we cannot isolate one from the other without deforming their nature. Because of this hybrid nature, intermediary objects are "analysers", making it possible to describe the actual design process. All along the design task, the object can not exist without the actor and the actor without the object. What we observe, see and feel in the design process, are objects being constructed, talked about, manipulated, interpreted, transformed, etc. Considered separately, the objects and actors are merely capacities for action. They are inert, static, mere?? "possibilities". It is the action, or rather the inter-action in which they are engaged that endows them with force, meaning and effective reality. The intermediary objects are also mediating objects: first of all, because of the mode of representation they use. This leads to a particular way of objectivising the idea or the intention by inscribing it in a specific organised matter. Thus, for example, a drawing is not simply a faithful representation of the mental idea or specifications : it is a translation, i.e. a realisation and a transformation which has been carried out according to its specific constraints (including those of the material used, which may vary depending on whether it is on paper or on screen) and its own rules and conventions. Lastly, the way in which the Intermediary Objects play the role of mediators in the design process is a result of their being representations. IO contents are mainly of cognitive nature : it results from the use of acquired knowledge by the actors in their various fields. They also signal the gradual production of new knowledge about the product as it is being designed. However, these contents are only of a cognitive nature in a situation of action, oriented by a given project and made up by the choices of the actors, the multiple negotiations that they are involved in, and the compromises and decisions that result from these. Therefore the cognitive contents cannot be isolated from the context of action 2.2 Classification of sketches in the collaborative process The role of the objects like sketches in collaborative design process are quite complex. Ferguson [11] identifies three kinds of sketches : thinking, talking, prescriptive. The situation of the experiment that we have carried out emphases on the second category of sketches. The collaborative activity involved many talking sketches. On the contrary, studies based on single designer activity mainly point out the thinking role of sketches [12]. In the experiment, we had characterised sketches [6] through an axis from open object that are able to support negotiation, to closed objects that mainly support prescriptions. We observed ICED 01 - C586/418 13
- 33. that the same object can support different status even if some objects get materials and cognitive characteristics that enhance opened or closed use. The situation of action as well as the material and cognitive properties of the IO influence the status. In the protocol, for example, we observed that the same sketch can be realised by an actor for his own use and after a few minutes be proposed to the others for evaluation. It moves from a private status (it is a thinking sketch), to a public one in the centre of the table. The existence of the private area is very important for the designer. This area is the thinking area that allows to explore ideas without judgement from the other. In a second step, the actor presents the meaning of his sketch and the other actors can assess the solution in their own point of view. This object then acts as a conjecture of solution. We can say that it is an externalisation of the designer's solution mental image. But this talking phase is also a thinking phase for the group that can make the sketch evolve. Every sketches are not built in a private area. Some are drawn directly in the public area of the table. A Sketch can also move from a talking to a prescriptive status. A sketch which has been the instrument of solution negotiation and elaboration, can get a prescriptive status after the group has built an agreement over it. For example, the sketch figure 2 got this prescriptive status by the group agreement. This decision is confirmed by a mark on the object: One of the actor underlined the word piston. This mark (detail Al) acts as the validation of the agreement. The definition and the negotiation of this part is then closed. Goel [5] suggests another way to characterise the evolution of sketches in he design process: the transformations typology. He identifies two types of operations occurring between successive sketches in the early stages of design: lateral and vertical transformations. A lateral transformation movement goes from one idea to a slightly different idea. Vertical express a movement from one idea to a detail or an extract of it. Then we can say that the role of the sketches depends on their status and the evolution between to successive sketches. The next table sum up the different categories of sketches we have identified. Thinking Talking / open Prescription / closed Lateral transformation Private new conjecture Public new conjecture New prescription Vertical transformation Private in depth conjecture Public in depth conjecture In depth prescription The status of the sketch is important in the sense that they partially characterise the situation of action where the actors are involved. Referring to the model presented figure 1, we can notice that the perception of the situation allows the receiver to build the sense of the information within the situation S. It act as a part of rhetoric components. 14 ICED 01 - C586/418 Table 1. Typology of sketches Private area Public area
- 34. 2.3 Sketches as a process of building conventional support For the explanation of this point, we must focus on the building process of those objects. The Object presented in figure 3 is in fact an addition of different sketch steps. The building of this sketch represents 20 minutes of group interaction during the design process. We consider that it is in this object that emerges the solution principle developed during the next phases of the experiment[7]. The first sketch (detail A) was drawn to put a end to a misunderstanding between two actors. They did not have the same interpretation of the requirements. The three sketches (A, B, C) allowed them to build a shared understanding of the problem. Then, from this representation a third actor had doubt about the connection between the device and its environment. This actor assessed the rubber tubing connection (detail D) as a non reliable solution for this system. From this negative evaluation of the solution elements represented on this sketch emerged a few minutes later a rigid and quick connection solution that is represented (detail E) on the sketch. This move is a lateral transformation that highlight the emergence process. Then this solution offered new opportunities for the inter-connections system of blocks. Finally a general overview of the system was drawn to visualise the ability of blocks interconnection (detail F). This last view is a vertical transformation showing the same solution from another point of view. Figure 2. Status of object moves during the process. Figure 3. Different level of sketches in the same draft... This sketch shows that the knowledge of construction process is necessary to be able to understand the sketch. In this sketch, aborted solutions and the solution chosen are represented on the same level. Nothing but the knowing of the process allowed the actors to differentiate the good from the aborted solution. This point allows us to point out that this type of GNSI is not able to support a prescription task. It failed as a memory of the process, In our protocol, we highlight that the actors themselves had difficulties to re-use their own sketches out of the action process itself.[7] The actors created, during the process, some symbolic devices which were connected to semantic in a local convention. This allowed them to let some part of the device in a low definition level: fuzzy and partial. The objects were used as "cognitive artefacts". The participants did not describe precisely what they were talking about, they showed the different elements they wanted to highlight with a finger or a pen and they used diectic words to point them. For example, an actor said: "that will be difficult to manufacture" (showing the elements concerned with his pen) ICED 01 - C586/418 15
- 35. We want to highlight the fact that the sketches act as pragmatic conventional supports [13]. Those conventional supports are negotiated in the interactions between actors, even if they can also use a higher level of convention as cultural ones, shared by the actors (the rules of industrial drawing in our case). The sense of the sketch is built in the action process and the conventions which allow this interpretation are quite local. Rhetoric components of sketches are specific and part of the linguistic components are built within the action itself. This characteristic of GNSI is important in order to imagine design tool able to support GNSI in an asynchronous communication process; furthermore, in order to involve sketches in a knowledge capitalisation process as MICA does for textual NSI. Indeed local conventions which allow interpretations are built in the interaction process. They won't be available to actors that were not involved in the process itself. 3 Towards a communication tool MICA GRAPH The first quality of a sketching device for designer seems to allow fast freehand sketch. Previous studies have highlighted that the cognitive tasks of manipulating the sketching tool have to be minimised [14]. Even if we can expect that the actors will learn the tool. That is why the tool is based on a simple blackboard technic and uses a digital table with an electronic pen. Indeed, when the designer needs formal drawing he will mainly use CAD or Structured information tools. Sketches are just GNSI and support fuzzy and partial definitions of elements. The functions that we offer are not supposed to help the drawing process but to partially structure GNSI in order to capitalise and treat them in the knowledge process. We are at the moment unable to manage a knowledge treatment directly on sketches. The principle we develop here is to characterise GNSI, track the steps of the building process and to associate textual and symbolic information that the data-mining techniques used by MICA are able to treat. At the moment, a designer creates a new sketch, he creates a properties file containing the legend of the file, type of the GNSI created and all the textual annotations contained. All this textual information is able to be treated by the MICA data-mining process [4]. 3.1 Tracking the different steps of the object We have highlighted the difficulty to track the different steps of a sketch out of the drawing process. It is also impossible to identify in a sketch the valid elements from the aborted solutions. It is important to follow the sketches modifications and to track the different sketch levels and steps present in the same final draft. We also want to know who had drawn on it. We propose to develop a structure of layers in order track the process. Each actor who wants to draw on an existing draft has to open a new layer. He can chose two options: "transparency" that allows him to sketch on the previous element or "blank" that opens a new layer disconnected from the previous sketch. In order to track information about the sketch contents and intentions, we characterise the type of opened layers. Six types of layers are available corresponding to the typology proposed in table 1. Public layers and private layers have different properties. When an actor wants to send a sketch, the public layers are automatically sent. Private layers sending is optional. If the actor accepts to send them the category changes moving from private to the public area. 16 ICED01-C586/418
- 36. In order to highlight decisions concerning a specific area of a sketch, actors can modify the colour of this area. By drawing a boundary line around this area, they notify that it is fixed. This materialises the compromise within the object. 3.2 The necessity to associate annotations on GNSI In order to allow the actors to interpret the sketches in an asynchronous communication mode, and to capitalise textual information about the content of the sketch, we propose different devices to the users. Firstly an actor as to define a title to the sketch using few keywords. We notice here that some contextual components (product, process, state, part etc. ) are already identified in the MICA form.[2] [4] It is important to give the actors the ability to express comments in the sketch itself. In a synchronous interaction around sketches actors explain some elements of the solution they focus on. Drawing is generally accompanied by a speech concerning the sketch. In an asynchronous process, the speech does not exist. It is supported by writing in the message or by a local annotation on the sketch. In the same way, actors need to be able to focus the attention of the receiver on a specific area and to associate elements that allow the receiver to interpret the sketch in the right way. They have sometimes to explain some symbolic elements they have used to fuzzy represent an element. Annotations can allow them to do it. The annotations are textual information that are connected to the graphic properties. A further step is to allow an actor to define different types of annotations using colour and type of markers. Each time he defines a new type, he has to explain the legend of this symbolic feature. Laureillard had pointed out the importance of what he called co-operative feature in the co-operation between specialists [15][16]. Those symbols are local conventional supports which refer to shared knowledge between the different actors. We don't have deeply investigated the different types of annotation. Our proposition is to offer a toolbox to the actors. They have to define themselves the relevant type co-operation feature. 4 Conclusions The concepts developed in the MICA-GRAPH tool have to be improved in design practices. The aim is not to suppress synchronous interactions but to complete the offer of asynchronous communications tools for design activities. Engineering design needs visual representations: structured (like CAD models) and non structured (like sketches). GNSI allows to manage quick conjecture-evaluation process. We notice that the move from direct interaction to textual explanation implies the risk of the deterioration of the contents. But the advantages of textual information related to GNSI aretheir ability to be treated in a knowledge process. References [1] B. Prasad, Concurrent Engineering Fundamentals - Integrated product and process organisation, Vol. 1, Prentice Hall, Englewood Cliffs, NJ, 1996 [2] M. Gardoni, M. Spadoni, F. Vernadat, "Information and Knowledge Support in Concurrent Engineering Environments", 3rd International Conference on Engineering Design and Automation, EDA'99, Vancouver, B.C., Canada, August 1-4, 1999 ICED 01 - C586/418 17
- 37. [3] Moeschler, J. Modelisation du dialogue (representation de 1'inference argumentative), Editions Hermes, Paris, 1989 [4] M. Gardoni, Maitrise de 1'information non structuree et capitalisation du savoir et du savoir-faire en Ingenierie Integree - Cas d'etude Aerospatiale Matra, PhD thesis of Metz University 1999 [5] Goel V, Sketches of thought MIT press Cambridge, MA 1995 [6] Gardoni M., Blanco E Taxonomy of information and capitalisation in a Concurrent Engineering context 7th ispe international conference on concurrent engineering (CE'2000), Lyon, France, July 2000 [7] Blanco E., 1'emergence du produit dans la conception distribute PHD thesis INP Grenoble 1998 [8] Garro O., Salau I., Martin P., Distributed design theory and methodology, Concurrent engineering: research and applications, vol 3/1/1995. [9] Vinck D., Jeantet A., 1995 Mediating and commissioning objects in the sociotechnical process of product design: a conceptual approach, pp111-129 in D. Mac Lean, P. Saviotti, D. Vinck (eds), Management and new technology : Design, Networks and Strategy. COST Social science serie. Bruxelles. Commission of european [10] Blanco E., Garro O., Brissaud D., Jeantet A., Intermediary object in the context of distributed design CESA Computational Engineering in systems applications, IEEE- SMC, Lille, July 96 [11] Fergusson E,S, Engineering and the Mind's Eye MIT press Cambridge, MA 1992 [12] Rodgers PA, Green G., McGownA. Using concept sketches to track design progress in Design studies 21 N°5 pp 465-481 sept 2000 [13] N. Dodier, les appuis conventionnels de I'action elements de pragmatique sociologique Reseaux n°62 edition CNET, 1993 [14] Aytes G., Comparing Drawing Tools and Whiteboards: An Analysis of the Group Process in CSCW 4: 51-71,1996 [15] Laureillard P., conception integree dans I 'usage, PHD thesis INP Grenoble 1999 [16] Boujut, Blanco The role of objects in design co-operation: communication throught virtual or physical objects. In COOP 2000 conferences Workshop Sophia Antipolis May 2000 Dr Blanco Eric Soils Solids Structures laboratory, Domaine Universitaire, BP 53, 38041 GRENOBLE Cedex 9, France, Tel: (33)-4-76-82-70-11, Fax (33)-4-76-82-70-43, mail - eric.blanco@hmg.inpg.fr Dr Gardoni Mickael GILCO laboratory, ENSGI, 46 avenue Felix Viallet, 38031 Grenoble Cedexl, France, Tel (33) (0)4 76 57 43 33, Fax (33) (0)4 76 57 46 95, mail: gardoni@gilco.inpg.fr (c)IMechE2001 18 ICED 01 - C586/418
- 38. INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN ICED 01 GLASGOW, AUGUST 21-23,2001 AUTOMATIC COMPOSITIONOF XML DOCUMENTSTOEXPRESS DESIGN INFORMATION NEEDS A Dong, S Song, J-L Wu, and A MAgogino Keywords: Information analysis, classification and retrieval; information representation; design information management 1 Introduction Engineering design is an information intensive activity. It is reported that designers spend in excess of 50% of their time in handling information [7]. Thus, the efficiency and the quality of the design process depend considerably on how well designers are able to handle large amounts of information. One study [8] of the information required by design engineers to complete their jobs indicated that less than 50% of that information was actually available and only 20% could be provided by the existing specialized applications. Directing the right information to the right person at the right time is a complicated but crucial task. Design information management has received increasing attention in recent years as a result of these findings and the recognition that lacking sufficient or missing key design information may lead to sub-optimal decision-making and design [2,4]. Much of the existing research has focused on the capture, storage, indexing and presentation of design information including informal information [3,9]. Less work has been done on information retrieval based on an understanding of individual designers, their experience, their skills and the ways in which they use information in the context of their design task [1]. One key step in finding the right information is expressing information needs in context. This paper presents a methodology to generate an XML (extensible Markup Language) document that expresses the information needs of a design engineer. XML documents and their underlying Document Type Definition (DTD) offer an efficient structure for the organization of design information [5] and representation of information needs. Through declarations of XML entities and the inherent structural hierarchy of XML documents, XML documents can express the designer's information needs while framing the design's structural hierarchies. For example, an element in the DTD may permit the design engineer to express a preference for formal company documents of past designs (e.g., technical memos) rather than informal design notes. The data in the XML document may be drawn from a repository of semi-structured or unstructured text documents that the design engineer has retrieved and placed into a personal information store by using an information retrieval system. Our methodology draws from the computational linguistics techniques of natural language processing and latent semantic analysis (LSA). We assume there exists some underlying information needs that are expressed by the type of information the engineering designer wishes to view and download into a personal information store. The "type of information" will be distinguished primarily by subject but may include other identifiers such as the format of the information and the intended audience. By applying these linguistic techniques, we can ICED 01 - C586/422 19
- 39. construct an XML document that is descriptive of this underlying need and contains information directly from the documents that is consistent with the major patterns of information preferences of the designer. 2 Methodology 2.1 Technical Approach The methodology for automated composition of the XML documents proceeds along two axes: 1) explicitly solicit information needs from the designer through standard information retrieval means; 2) implicitly monitor the information retrieval behaviour of the designer to information sources including the type, quality and information contained in the documents the designer chose to retrieve. We test this methodology on access to unstructured engineering data, such as full-text, because unstructured, textual documents are the principal mode of communication by engineers. Before proceeding to a detailed discussion of our methodology, we discuss two core technologies to the methodology: mining of transaction logs to learn information needs implicitly and computational linguistics. 2.2 Learning Information Needs Implicitly Many difficulties exist in determining what information a person wants to see as well as modelling user information needs. Most information retrieval systems require that people express information needs through a set of keywords or key phrases. However, ascertaining information needs simply by a word or two is inadequate and subject to loss of contextual information. For engineering design, studies have shown varying information needs of designers depending on level of expertise and stage of the design [1,6]. Our approach in modelling user information needs is based on a human-centred computing. Our methodology examines the user's document access patterns, that is, the user's personal information store and transaction history in an information retrieval system, for patterns of information preference. The basic approach is to examine the user's session information over all sessions while using the information management system. In learning information needs implicitly, we are primarily interested in discovering the similarity between documents that the user has downloaded into a personal information store. The assumption is that the user's particular choices of documents to store locally are indicative of information needs. Thus, instead of requiring the designer to a priori categorize the information, the system attempts to learn a similarity mapping using contextual clues such as project name, engineering discipline, and document format. Similar categorisation strategies have also been found in the classification of supplier information practised in industry [12]. To ascertain relevance, the system records each document downloaded into the user's personal information store. This is an accurate indicator of relevance because, in our system, before the user may download the document, the user has already read a brief description of the content of the document containing meta-information such as abstract, author, document type, and subject. The assumption is that during any single session utilizing the information retrieval system, the user has a dominant goal (information need) in mind that is expressed by the type(s) of documents the user decides to download. Similar assumptions exist in other studies [13] of information retrieval systems. We use the vector space approach [14] for document and query representation. We analytically modelled information needs as a linear combination of the vectors representing 20 ICED 01 - C586/422
- 40. the query and the relevant document. The weighted vector average (arithmetic mean) of all combined vectors consisting of the query and relevant documents is called the "centroid" of the user's intended information needs. The centroid is then used as a representation of the dominant information need of the user. The maximum angle between the document vectors or query string vector and the centroid is used as an indication of the variation in the user's information needs. 2.3 ComputationalLinguisticApproaches Our methodology employs two computational linguistics techniques, natural language processing and latent semantic analysis, to extract and summarizethe primary topic of a set of similar documents. Natural Language Processing While we use the designer's past transactions as an indication of information need, the structured information contained in the documents that are referenced in the transactions needs to be discovered and refined before it can be utilised effectively. The key phrase retrieval process helps in crosschecking the indexed subjects and compacting the size of the aggregated XML document by representing paragraphs of text with just a few representative noun phrases. As the designer adds documents to a personal information store, we do not need to concatenate all the textual information about the document to the XML document, just the extracted noun phrases that are not already in there and plug them under the appropriate tags. By identifying the noun phrases in the document, we are able to find the corresponding contents for each XML tag in the text. Additional rules and procedures are needed other than standard noun phrase retrieval process to perform this task for all tags. This latter component forms a part of future research. Extracting from the full-text content-bearing noun phrases documents that can be used in profiling and indexing involves 3 steps: tokenization, part-of-speech (POS) tagging and noun- phrase identification. Tokenization is a procedure that identifies sentence boundaries and removes extraneous punctuations. POS taggers then take the processed corpus and tag each word with their POS information. Taggers that operate following semantic rules or just statistical information were developed. After the text corpus has been tagged with POS information, we could use the contextual information to identify noun phrases. The extracted noun phrases are then attached to the corresponding DTD elements of the document. Latent Semantic Analysis Latent Semantic Analysis (LSA) [9] is a statistical model of word usage that permits comparisons of semantic similarity between pieces of textual information. The idea is that the totality of information about all the word contexts in which a word does and does not appear provides a set of mutual constraints that largely determines the similarity of meaning of words and sets of words to each other. The primary assumption of LSA is that there exists an underlying or "latent" structure in the pattern of word usage across documents. LSA uses the matrix technique of singular value decomposition (SVD) to reflect the major associative patterns of words in the document and to ignore the smaller influences. The ability for LSA to remove the obscuring "noise" makes LSA useful as an analytical tool for discovering the primary conceptual content of documents. We use LSA to help us to categorize and group the documents by topic material that the user has downloaded and revealed as relevant and useful. Once these principal groupings are identified, we can then apply the rest of our methodology ICED 01 - C586/422 21
- 41. to express information needs for each "centroid" of documents within a semantic locality through a single XML document. 2.4 ComposingXML Documents The system initiates by asking the user to specify an XML DTD containing metadata elements (XML entities) that express information needs. For this study, we asked that users express their information needs using a well-known metadata set, the IEEE Learning Object Metadata (LOM) [10], and in particular the core 20 elements. The LOM defines the information required to manage, locate and evaluate learning resources. Having a standards-based XML DTD allows us to assess our methodology's completeness and efficacy and for comparison against other systems. Because of the analogous human cognitive processes of information processing and learning [11], the LOM serves as a reasonable model for describing information needs. Once the user has specified an XML DTD, the user must now utilise the information management system, retrieving and downloading design documents. The system implicitly monitors the information retrieval transactions of the user, eventually formulating a seed an XML document containing information from the user's session. Typically, the XML document is seeded with the initial query the user posed to the system. The implicit stage contains two phases. In phase one, the system applies latent semantic analysis to characterize the knowledge conveyed by the all documents the person chose to view. To perform this phase, we analysed the transaction logs containing the transactions of both the current user and all other users of the system. The user's query and document(s) downloaded are recorded for each visit. The latter information identifies the relevant documents necessary for phase two. Using a similarity measurement, the system identifies topics represented by the documents the user viewed. By doing this step, the system ascertains the topic locality of the various documents the person viewed. This is a critical step because the user may have multiple and widely varying information needs. Then, for each topic locality, the system augments the XML document expressing the user's information needs with the metadata elements from each relevant document. In practice, the information management system will contain most of the information required to complete the tagging such as Author, Title, Date, and Format. Subject and Description information are generated automatically from the second phase. This matching can be done by exact one-to-one correlation, i.e., both the tag and attribute match, or via a crosswalk between the information about the document contained in the information management system and the XML DTD. Both of these techniques will have required some prior means of tagging the documents in the information management system. In the second phase, we apply natural language processing techniques to ascertain the principal subject of the documents within each topic as discussed in Section 2.3. The process repeats until all possible elements in the user's original XML DTD are filled, resulting in a fully marked up XML document. The completed DTD is now an expression of the information needs of the designer, based upon the available information stores and the pattern of information retrieval undertaken. In summary, a designer's information needs can be found implicitly by looking at the set of documents the designer has deemed relevant and useful and stored in a personal information store. We use LSA to find signatures of similarity in this set of documentation. Once we find the signatures, we look at what the original information needs were to find the centroid of the 22 ICED01 - C586/422
- 42. similarity. Finally, we construct a compound XML document that essentially reconstructs the full LSA space by combining information from all the similar documents, with some of the information filtered through NLP techniques to reduce the size of the document. Other information about the document indexed in the document database, such as document type, is added to the corresponding XML tag. This final XML document is then an expression of the designer's information needs. 3 ExperimentationandResults 3.1 Test Case The experiment and prototype evaluation was conducted on a digital library project for science, math, engineering and technology education. Students and educators use the digital library to download courseware into their personal information stores. The documents used in the study discuss the design of engineering devices and related scientific theories. The users of the system typically search for material on engineering education. This is their primary information need. 3.2 Results First, we validated the ability of our methodology to discover information needs. We conducted this study by analysing for the known information needs of all users of the digital library. Based on the fairly homogeneous content of the digital library (courseware on engineering design) and the known profile of the audience of the digital library, we expected that our methodology would reveal one dominant information need, namely courseware related to engineering education. We would not expect for the system to reveal numerous distinct clusters of information needs. We ran the latent semantic analysis over the entire usage database. Figure 1 illustrates the distribution of all users' information needs over multiple sessions. Figure 1. Information Needs Represented in LSA Space ICED 01 - C586/422 23
- 43. Each dot represents in LSA space the combined vector of the user's query and a downloaded document for one session. By visual inspection, one can note one dominant informationneed. Specifically, the most commonly downloaded documents by all users of the system were case studies and courseware on the design of disk drives, a specific subset of engineering education. This result corroborates the known informationneeds of users of the database. Second, we analysed for the information needs of individual users. Figure 2 illustrates the information needs of one sample user, specifically information on "control systems". The circle represents, in LSA space, the initial query to the information retrieval system whereas the boxed numbers indicate the documents downloaded by the user. One can then apply latent semantic analysis to ascertain the similarity between downloaded documents, the original query, and the documents themselves. Users may have multiple information needs despite using the same keyword to query the information retrieval system. In the example shown, document 165 is relevant to the user's query but not similar to the other documents, therefore potentially indicating different informationneeds. For this document set, we found that an angle of 71o between documents provided an adequate measurement of similarity. Based on the set of similar documents, we computed the centroid. Figure 2. One User's Information Needs Finally, we generated the XML documents to express the information needs. Portions of an XML document are illustrated in Figure 3. <!-- The Core IMS Learning Object Metadata in XML, a subset of the IEEE LOM V3.5. --> <metametadata> <metadatascheme>IEEELOM:1.0</metadatascheme> <language>en-US</language> </metametadata> <general> <title> <langstring> educational software engineering graphics tutorials engineering visual encyclopedia 24 ICED 01 - C586/422
- 44. mechanics virtual disk drive design studio </langstring> </title> <language>en-US</language> <description> <langstring> acme disk drive company <lifecycle> <contribute> <role> <langstring lang="en">Author</langstring> </role> <centity> BEGIN:vCard <?xml> Figure 3. Sample XML Document The XML document expresses out in human-readable format a summary of the user's information needs as an aggregation of the documents that the user found relevant and useful and that were related to each other. 4 Conclusions This research has established a basic framework for identifying and modelling engineers' information needs using XML documents. We performed latent semantic analysis over a collection of engineering resources to construct information needs as vectors in LSA space based on usage analysis. We visualized different information needs in multi-dimensional space. Based on a cluster of similar documents representing an information need, we generated an XML document using natural language processing techniques to express the information need. These results are encouraging. They show that latent semantic analysis can be applied to the task of ascertaining information needs by monitoring the information retrieval habits of a user. In order to assess the actual "truth" of the XML document in representing the user's information needs, we would need to have the user respond positively or negatively to suggested relevant information provided autonomously by the information retrieval system. We have projects in progress to incorporate this feedback. In addition, we are working on methods to incorporate reading time into the model of information needs and to predict the expected reading time of a document based on prior reading time. We expect this methodology to impact the use of information in design in several ways. First, the XML documents can be used as information filters to direct critical pieces of information to the designer as others generate them. In addition, intelligent software agents might use the XML document as a guide to search document repositories for new, useful information. The methodology may provide insight into the cognitive states of the designer over various stages of design, offering a tool to study how changes in information needs relate to the designer's understanding of the design problem. We are currently analysing the effect of time on information needs, particularly the rate of change of information needs. In addition, we are investigating learning the information needs of design teams by analysing team communication. Our methodology presents a new means for learning information needs through a combination of LSA, natural language processing and a human-centred approach which places emphasis on understanding what it is that the user is doing. ICED 01 - C586/422 25
- 45. 5 References [1] Lowe, Alistair, McMahon, Chris, and Shah, Tulan, Culley, S., "A Method for The Study of Information Use Profiles for Design Engineers," Proceedings of the 1999 ASME Design Engineering Technical Conferences. September 12-15, 1999, Las Vegas, Nevada. [2] Court, A.W., Culley, S.J., and McMahon, C. A., "The Influence of IT in New Product Development: Observations of an Empirical Study of the Access of Engineering Design Information, International Journal of Information Management, 17(5), 1997, p359-375. [3] Dong, Andy and Agogino, Alice M., "Text analysis for constructing design representations." Artificial Intelligence in Engineering. 11, 1997, p65-75. [4] Rangan, R.M., and Fulton, R.E., "A data management strategy to control design and manufacturing information." Journal of Engineering with Computers. 7, 1991, p63-78. [5] Rezayat, M., "Knowledge-based product development using XML and KCs," Computer-Aided Design. 32, 2000, 299-309. [6] Ullman, David G., Dietterich, Thomas G., and Stauffer, Larry A., "A Model of the Mechanical Design Process Based on Empirical Data", Artificial Intelligence in Engineering Design and Manufacturing.2(1), 1988, p33-52. [7] Williams, Ruth L., and Cothrel, Joseph, "Four smart ways to run online communities," Sloan Management Review. 41(4), Summer 2000, p81-91. [8] Wood, William H., Yang, Maria, et al., "Design information retrieval: improving access to the informal side of design," Proceedings of the ASME Design Engineering Technical Conferences. 1998. [9] Deerwester, Scott, Dumais, Susan T., Furnas, George W., Landauer, Thomas K., and Harshman, Richard, "Indexing by Latent Semantic Analysis," Journal Of The American Society For Information Science. September 1990, 41(6), p391-407. [10] Learning Object Metadata, http://ltsc.ieee.org/doc/wgl2/LOMdoc2_4.doc. [11] In Klahr, David and Kotovsky, Kenneth, (Eds.), Complex Information Processing: The Impact of Herbert A. Simon, Lawrence Erlbaum Associates, Hillsdale, New Jersey, 1989. [12] Culley, Stephen J., Boston, Oliver P., and McMahon, Christopher A., "Suppliers in New Product Development: Their Information and Integration," Journal of Engineering Design, 10(1), 1999, 59-75. [13] Cooper, William S., 1976, "The Paradoxical Role of Unexamined Documents in the Evaluation of Retrieval Effectiveness," Information Processing and Management, 12, 367-375. [14] Salton, Gerald and McGill, Michael J., 1983, Introduction to Modem Information Retrieval, New York: McGraw-Hill Book Company. Dr. Andy Dong, Lecturer University of California, Berkeley, Department of Mechanical Engineering, 5138 Etcheverry Hall, Berkeley, CA 94720-1740 USA, Tel: +1 510 643 1819, Fax: +1 510 643 1822, E-mail: adong@me.berkeley.edu © IMechE 2001 26 ICED 01 - C586/422
- 46. INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN ICED 01 GLASGOW, AUGUST 21-23, 2001 DESIGN COMMUNICATION USING A VARIATION OF THE DESIGN STRUCTURE MATRIX J C Lockledge and F A Salustri Keywords: concurrent engineering, automotive engineering, design information management, workflow management. 1 Introduction As reported in earlier work[1] , the authors have constructed a mechanism for structuring design communications at a leading American automobile maker using a variation of the Design Structure Matrix (DSM). This paper provides a formal process to create similar matrices and outlines a mechanism for keeping participants updated on the design status. The original work was carried out in collaboration with, and implemented at, a major American automobile manufacturer. The new work reported herein is a prototype which has as yet to be implemented in an industrial setting. Many major industries base their design organizations on teams of design engineers (DEs). The use of team-based engineering practices can substantially improve the effectiveness of design processes, but they also introduce new complexities in terms of communications between team members and management of tasks carried out by the teams. This is particularly true in major industries, like the automotive industry. Thus, while modern design practices have improved the nature of the products being developed, they have also increased the administrativeand management burden arising from increased complexity; what is gained in one respect can be easily lost in the other. Because these complexities are not product complexities but, rather, complexities of design and designing, they were not immediately recognized as important performance issues. Recently, however, more and more interest has been shown in North America to seek a deeper understanding of the complexities of modem design as they arise largely from these issues of communications and task management. The authors are developing a means of managing the design process to ensure appropriate communication between design team members is facilitated, that task management is streamlined, and that all this can be done without placing further burdens on the designers. Different enterprises choose different strategies to achieve these goals. One leading automobile manufacturer chose the strategy of re-defining its design process. While the car manufacturer currently designs world class engines, they felt a need to reduce their time to market. As part of this overall effort, they identified their engine design process as one for examination andimprovement. The authors undertook to assist the company by developing a tool to help the company's design engineers manage engine design information more efficiently and reduce the initial design time. We focused on the following stages of the process: the initial steps in identifying 1CED 01 - C586/584 27
- 47. a desired engine to be designed (needs analysis), coordinating the initial design (conceptual design), and the day-to-day design process (design information flow). In particular, the authors noted that information regarding design changes was propagated wholesale to all DEs. This forced DEs to spend valuable time deciding if a particular design change affected the components or systems for which they were responsible. The authors conducted interviews with many DEs involved in engine design at the auto maker. Based on analysis of these interviews and background research into the company's practices, the authors concluded that a successful tool would have to be extremely flexible to respond to mid-program changes in design priorities and objectives. The tool also had to be very simple to use so as not to burden the DEs further with extra work. Our solution was a variation of Steward's Design Structure Matrix (DSM)[2] . The DSM was chosen for of its simplicity of presentation and of construction. It essentially allows designers to capture the relationships between structural elements, systems, subsystems, etc. of a product in an easily understood matrix form. Once in this form, various manipulationscan be performed on the matrix to discover features of the design, such a clusters of very high interaction between product components. The analogy between simple matrix operations, which all engineers understand, and design information management make the DSM quite a useful tool. The authors modified the DSM in two ways. First, we distinguished between the physical components of an automobile engine (listing them on one axis) from the functional systems and subsystems of the engine (listing them on the other axis). Identifying interactions in the modified matrix now results in identifying the functional dependencies of the structural components. By linking structure and function in this way, the matrix was used to identify the stakeholders that needed to be notified of design changes or decisions. Put another way, DEs whose tasks or designs are not affected by a design change will not be informed of the change. This means that change information is more efficiently managed. 28 ICED 01 - C586/584 Table 1: Example Design Process Matrix (DPM) Manufacturing Process Lubrication Combustion Cooling Power Conversion Delivery Return Intake Exhaust Fuel Delivery Chamber X c 0 CO X X X 8 CD X X X X X X TD I X X X X X X X X c 'a H 1 CO > X X X X X X CD § o % ca X Connecting Rod X X X Crankshaft X X
- 48. The second modification was to build a secondary matrix above the first one to cover interactions between components and manufacturing processes. In this way, interactions between components and the systems needed to manufacture them can be made explicit. This extends the chain of interactions all the way from the functional systems, through physical components, to fabrication. Any change to one can be propagated to only those stakeholders in related aspects who need to know about the change. The authors refer to the resulting matrix structure, as shown in Table 1: Example Design Process Matrix (DPM), as the Design Process Matrix (DPM). With these changes in place, the modified DSM now represented a tool to help manage the design process: the interactions shown by the DPM are indicative of causal relations between systems, components, and manufacturing. For each of these, stakeholders can be identified. Therefore, the DPM is a model of the interrelationships between tasks as well as a model of the required interactions between stakeholders needed to carry out the design tasks. The researched sketched above was received by the automaker and integrated into their overall technical process. However, it was empirical and derived largely from the particular characteristics of the automaker's enterprise and corporate structure. The authors believe that a generalization of the DPM to a broader category of design enterprise could be very beneficial. In order to perform this generalization, a deeper understanding of the process of DPM construction is needed. This paper lays the foundations for such a generalization. 2 Approach to Constructing the Matrix The purpose of this process is to create a Design Structure Matrix analogue that can be used for automating communication in a complex design environment. This environment owes its existence to the design of a product (or group of products) that will be produced by the organization. To warrant using this process, the product is expected to be complex enough to have multiple functions and several components that must be manufactured. As pointed out by Hubka and Eder3 , the design intent (which are goals within specific constraints) is met by a series of functional systems. Each system exists by being embodied in one or more components (or more precisely organs). These components interact with each other, producing the desired effects through their functional systems. Within an organization individuals or teams (although typically a single individual) are assigned responsibility for releasing a component for production. As originally pointed out by Steward4 , the underlying component interaction can therefore be used to model the required interaction of those responsible for designing them. This process allows an Engineering Manager to create a mechanism that takes advantage of these underlying principles to route messages to the proper individuals in a design enterprise. The process is broken into 5 steps: • Constructing a Hierarchical, Component Based DSM • Constructing a Hierarchical, System Based DSM • Constructing a Human Role to Component Mapping • Adding Process Based Communication • ConstructingtheCommunicationMatrix • These steps will be defined in detail in the following sections. 1CED 01 - C586/584 29
- 49. 2.1 Constructing a Hierarchical, Component Based DSM The construction of a Component DSM (CDSM) has been discussed in detail by Eppinger[5] . In general, the first task is collecting the relevant component names and determining which components define others. Rules for the construction of hierarchical, component DSMs has been delineated by Sabbaghian[6] in his work with Boeing. He points out that in constructing a DSM that has components and sub-components, any interaction between sub-components from different components implies an interaction between the components they belong to. This is illustrated in Table 2 by the interaction between the Connecting Rod and the Piston that causes the interaction with the Piston Assembly. Interactions between sub-components both belonging to a single component do not affect the relationship of the component. This can be seen in the interaction between the Rocker Arm and the Intake and Exhaust Valves. These sub-components are all part of the valve train and therefore these relations do not influence other components. A hierarchical DSM permits a larger number of components to be addressed without overwhelming those who are indicating the relationships. A hierarchical DSM is necessary because the larger number of components (and sub-components) allows finer granularity of the relationships, and the granularity of the dependencies affects how specific the messages to users can be. It also affects the number of messages a user is likely to receive, since courser granularity implies that all of the people involved in a component will receive information on changes to any related component. 30 ICED 01 - C586/584 Table 2: Hierarchical ComponentDSM Components Connecting Rod Valve Train Components Piston Assembly Exhaust Valve Intake Valve Rocker Arm Piston Piston Ring Connecting Rod Valve Train Components 1 > -C flj X > W X <U O II X <5 - J* C !< Piston Assembly X c E X 1g> E"2
- 50. 2.2 Constructing a System Based DSM Constructing a System based DSM (SDSM) relies on first identifying the functional systems in the object being designed. The functional systems may also be modelled as being hierarchical in nature, for the same reasons given in the previous section. Table 3 shows some sample functional systems in relationship to each other. In this case, the Cooling system is shown as functionally related to both the Lubrication Delivery (in the case of an engine with an oil cooler) and Combustion Chamber systems. Table 3: Hierarchical System DSM Systems Lubrication Cooling Combustion Delivery Return Air Intake Exhaust Chamber Lubrication t > 1 E 2 (2 § ~Q 5 X X Combustion Air Intake 3 Jr w Chamber 2.3 Constructing a Human Role to Component/System Mapping In most design organizations, individuals are given final authority for releasing a component's design. Since they are the only actors in the system that can affect the design, the system must interact with them, making them recipients of messages concerning design changes. For the system to do this, these roles must be identified and specified in the Role/Component Mapping (RCM) and the Role/System Mapping (RSM). Identifying these roles (and/or the individuals responsible for them) should be straight forward, as each of the sub-components must have an individual responsible for releasing it. Assigning an individual to an entire component implies that they are the responsible party for all of the sub-components. The individual assigned responsibility will then receive and need to respond to all of the messages concerning their sub-components. Individuals may also be assigned to the systems. These functional systems are not usually viewed as "released parts" so that this position takes on a monitoring role. The person assigned this role would be responsible for keeping individual DE aware of theimplications to those systems of any design decisions. 2.4 Constructing the Communication Matrix. The third matrix, as illustrated in Table 1, is the DPM. This matrix ties together the functional systems and the components. It is constructed by assigning sub-components to functional systems. An assignment results from the system being embodied in the component and thus both defining it and being defined by it. ICED 01 - C586/584 31
- 51. 2.5 Adding Process Based Communication Not all of the individuals who are responsible for a product have design releaseresponsibility. Some are involvedin the later stages of manufacturing, distribution, marketing, and customer service. Concurrent engineering [7] discusses the need for these parties to be involved in the design process. During this step, individuals who should be aware of design changes, but who may not be central to the process, are added to the matrix. Additional roles are added to the matrix above the components, indicating their interest in those specific components. Messages will be routed to these parties as if they had release responsibility, but they are not required to respond to the changes unlessthey see an opportunity or problem. 3 Assisting Communication These three matrices and two mappings are the starting point for the communication routing system. When a DE makes a change in their (sub-)component (which we'll call M) the system will react by establishingthe following sets: SM The systems of which M is part (from the DPM), CM The components that M affects (from the CDSM), Sc The systems shared by M and components of C, and Ssc The systems that interact with systems in SC (from the SDSM). Using the RCM messages can be routed to the individualsresponsible for components inCM who will need to be aware of this change. The change can also be routed through the RSM to the monitors of the system in SM. The messages to DEs would contain a statement that M was changing and which systems (Sc) would likely be affected both directly and indirectly (from Ssc). An example makes this somewhat complex process clearer. Suppose we had the CDSM, SDSM, and DPM shown in Table 4, Table 5, and Table 1. In this case, the components are not given hierarchicallyto conserve space. If a DE made a change in the Crankshaft, we would know from Table 1 that the Lubrication Delivery System and Power Conversion systems would be affected and that Manufacturing would like to be kept aware of any changes. 32 ICED 01 -C586/584 Table 4: Example Component DSM (CDSM) Component Piston Block Head Valve Train Valve Cover Connecting Rod Crankshaft c o "« h X X X .*: 8 m X X X T3 ra 03 T X X X X Valve Train X X Valve Cover X X Connecting Rod X X Crankshaft X X
- 52. Turning our attention to Table 4 we can determine that the Crankshaft directly affects the Block and Connecting Rods. By going back to Table 1 we see that these components share the Lubrication Delivery System and Power Conversion systems. Further, by going to the SDSM (Table 5) we can find that the Lubrication Delivery system also interacts with the Lubrication Return system and that Power Conversion interacts with the Combustion Chamber. Table 5: Example System DSM (SDSM) System Lubrication Combustion Cooling Power Conversion Delivery Return Intake Exhaust Fuel Delivery Chamber Lubrication £• 0) > "o> Q X X c 3 "CD rr X Combustion CD ^ a C X X Exhaust X X £• > 0> Q 'ffl 13 LJ. X X Chamber X X D> _C "5 o o X X Power Conversion X We can now frame messages to the individualsin charge of the Block and the Connecting Rod that would read: A change was recently made in the Crankshaft: <Text generated by the DE who was changing the Crankshaft would appear here> This may impact Lubrication Delivery and Power Conversion. If so, these could cause also impact the Lubrication Return and/or the Combustion Chamber. Please verify the impact of this change on your component. Similar messages could be generated and sent to the individuals monitoring the systems. These messages are not intended to be diagnostic, rather they are to alert the DE that the design has changed and their attention may be required. Work is underway to construct a Web based tool to coordinate the communication between DE. This tool will permit users to either log into a server to be made aware of the current status of the design, or be sent daily emails that summarizethe changes. 1CED 01- C586/584 33
- 53. 4 Conclusion This paper is a formalisation of a system to route messages between members of a design team based on a hybrid of the DSM. The routing is accomplished by examining the underlying physical and functional requirements of the product and the interconnections between them. This routing restricts updates to interested parties to avoid overloading the participating engineers with data concerning every change being made in the program. The system does this while following the same minimalist philosophy of the DSM and thus does not require extensive data gathering or modelling. A less formally developed precursor to this system was integrated into the design approach of a major automotive manufacturer and the authors believe this formalisation allows this work to be replicated in other areas. References [1] Lockledge, J.C. and Salustri, F.A., "Defining the engine design process", Journal of Engineering Design, 10, 1999, pp. 109-124. [2] Steward, D. (1981) System Analysis and Management: Structure, strategy and Design, 3, (New York, Perocelli). [3] Hubka, V and Eder, E., "Engineering Design: General Procedural Model of Engineering Design", Heurista, Zurich, Switzerland, 1992. [4] Steward, Donald V., "The Design Structure System: A Method for Managing the Design of Complex Systems" IEEE Transactions on Engineering Management, vol. 28, pp. 71-74, 1981a. Pimmler, Thomas U. and Eppinger, Steven D., "Integration Analysis of Product Decompositions", Proceedings of the ASME Sixth International Conference on Design Theory and Methodology, Minneapolis, MN, Sept., 1994. Also, M.I.T. Sloan School of Management, Cambridge, MA, Working Paper no. 3690-94-MS, May 1994. [6] Sabbaghian, N, Eppinger, S. and Murman, E, "Product Development Process Capture and Display Using Web-Based Technologies", Proceedings of the IEEE InternationalConference on Systems, Man, and Cybernetics, Par 3 (of 5), pp. 2664-2669, Oct 11-14, 1998. [7] Kusiak, Andrew, Engineering Design: Products, Processes, and Systems, Academic Pr, 1999. Corresponding Author: Jeffrey C. Lockledge Institution: Wayne State University Department: Department of Industrial andManufacturing Engineering Address: ManufacturingEngineering Building, 4815 Fourth St., Detroit, MI 48202 Phone: 313 577 3507 Email: j_lockledge@wayne.edu © IMechE2001
- 54. Keywords :product model, design process model, functional design, knowledge management, information management, collaborative design, co-ordination, life cycle 1 Introduction Concurrent engineering consists in fastening development time by executing in a parallel mode design, analysis, and industrial tasks while they were executed sequentially in traditional development methods. This results in a shortened time to market [7]. Automotive industry has applied successfully concurrent engineering to the most recent range of cars. However, concurrent engineering has not taken into account the dramatic evolution in information systems technology as the new WEB based tools allow to distribute and share technical information through all partners involved in a project [2] [7]. This will lead to new distributed organisations in design teams, to more innovative designs as design hypothesis can be more quickly tested and validated by all actors at Project Wide level. For any design problem, the best specialists from extended enterprises and partners can be appealed with full access to authorised design data with adequate viewpoint. Those new organisations, namely "shared engineering" or "collaborative engineering", will be supported by new "Product Information Systems" that directly take benefits from the information technology and the power of semantic support to information. Information technology must take into account all legacy systems to ensure of continuous data and service access to users: amongst those legacy systems, calculus worksheets, previously developed pieces of software... Further, many efforts have been provided in knowledge engineering for design activities [4] [12]. Design, like other very creative tasks, makes extensive use of many pieces of knowledge [11]. Those pieces of knowledge must be maintained, as knowledge in design is very evolutive. Knowledge is expressed either in the product model or in the tasks of engineering. This knowledge must be accessible to all actors involved in the design process, must be executable in the available design software, and must be maintained by accredited staff. This paper provides concepts for knowledge and information product sharing during the redesign. The second section describes what functional design and redesign are. The third section is dedicated to the presentation of the knowledge management approach employed in the study. The model is presented in section four. The fifth section details the web based tool that have been used to support the methodology. In section six, the application case is presented. Finally some conclusions and open issues conclude the paper. ICED 01 - C586/021 35 INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN ICED 01 GLASGOW, AUGUST 21-23, 2001 MULTI - A TOOL ANDA METHOD TO SUPPORT COLLABORATIVE FUNCTIONAL DESIGN S Menand and M Tollenaere
- 55. Exploring the Variety of Random Documents with Different Content
- 56. remain freely available for generations to come. In 2001, the Project Gutenberg Literary Archive Foundation was created to provide a secure and permanent future for Project Gutenberg™ and future generations. To learn more about the Project Gutenberg Literary Archive Foundation and how your efforts and donations can help, see Sections 3 and 4 and the Foundation information page at www.gutenberg.org. Section 3. Information about the Project Gutenberg Literary Archive Foundation The Project Gutenberg Literary Archive Foundation is a non-profit 501(c)(3) educational corporation organized under the laws of the state of Mississippi and granted tax exempt status by the Internal Revenue Service. The Foundation’s EIN or federal tax identification number is 64-6221541. Contributions to the Project Gutenberg Literary Archive Foundation are tax deductible to the full extent permitted by U.S. federal laws and your state’s laws. The Foundation’s business office is located at 809 North 1500 West, Salt Lake City, UT 84116, (801) 596-1887. Email contact links and up to date contact information can be found at the Foundation’s website and official page at www.gutenberg.org/contact Section 4. Information about Donations to the Project Gutenberg Literary Archive Foundation Project Gutenberg™ depends upon and cannot survive without widespread public support and donations to carry out its mission of increasing the number of public domain and licensed works that can be freely distributed in machine-readable form accessible by the widest array of equipment including outdated equipment. Many
- 57. small donations ($1 to $5,000) are particularly important to maintaining tax exempt status with the IRS. The Foundation is committed to complying with the laws regulating charities and charitable donations in all 50 states of the United States. Compliance requirements are not uniform and it takes a considerable effort, much paperwork and many fees to meet and keep up with these requirements. We do not solicit donations in locations where we have not received written confirmation of compliance. To SEND DONATIONS or determine the status of compliance for any particular state visit www.gutenberg.org/donate. While we cannot and do not solicit contributions from states where we have not met the solicitation requirements, we know of no prohibition against accepting unsolicited donations from donors in such states who approach us with offers to donate. International donations are gratefully accepted, but we cannot make any statements concerning tax treatment of donations received from outside the United States. U.S. laws alone swamp our small staff. Please check the Project Gutenberg web pages for current donation methods and addresses. Donations are accepted in a number of other ways including checks, online payments and credit card donations. To donate, please visit: www.gutenberg.org/donate. Section 5. General Information About Project Gutenberg™ electronic works Professor Michael S. Hart was the originator of the Project Gutenberg™ concept of a library of electronic works that could be freely shared with anyone. For forty years, he produced and distributed Project Gutenberg™ eBooks with only a loose network of volunteer support.
- 58. Project Gutenberg™ eBooks are often created from several printed editions, all of which are confirmed as not protected by copyright in the U.S. unless a copyright notice is included. Thus, we do not necessarily keep eBooks in compliance with any particular paper edition. Most people start at our website which has the main PG search facility: www.gutenberg.org. This website includes information about Project Gutenberg™, including how to make donations to the Project Gutenberg Literary Archive Foundation, how to help produce our new eBooks, and how to subscribe to our email newsletter to hear about new eBooks.
- 59. Welcome to our website – the perfect destination for book lovers and knowledge seekers. We believe that every book holds a new world, offering opportunities for learning, discovery, and personal growth. That’s why we are dedicated to bringing you a diverse collection of books, ranging from classic literature and specialized publications to self-development guides and children's books. More than just a book-buying platform, we strive to be a bridge connecting you with timeless cultural and intellectual values. With an elegant, user-friendly interface and a smart search system, you can quickly find the books that best suit your interests. Additionally, our special promotions and home delivery services help you save time and fully enjoy the joy of reading. Join us on a journey of knowledge exploration, passion nurturing, and personal growth every day! ebookbell.com