Professional Documents
Culture Documents
1 Lecture overview
This lecture examines the topic of multi-disciplinary design optimization (MDO), which
consists of a family of methods that can be used to perform decision support for the
design of complex engineered products, such as vehicles or critical infrastructure.
In this lecture, we will cover:
• The motivation for using MDO within a decision system;
• A detailed look at a specific MDO architecture known as collaborative optimiza-
tion;
• Ensure that the overall design is internally consistent – i.e. that all design teams
are using the same assumptions about the shared design variables and inter-
faces. This is equivalent to saying that the design is, in principle, physically
realisable;
3 Collaborative Optimization
3.1 Design scenario
Consider a generic engineering design problem with two design teams, i 1 and
i 2. We will assume that each design team is responsible for its own local design
variables, x1 and x2 respectively, and that there are additional global design variables
x0 that are shared by the teams.
We will further assume that each design team has a number of inequality con-
straints that its local designs need to satisfy, i.e. g1,2 p.q ¤ 0, and that there is an
overall objective f p.q that the integrated, global design is aiming to minimise.
System problem
choose x̂ 0, â1, â2
minimise objective f
s.t. consistency constraints
x0,1
* , a*
1 x0,2
* , a*
2
x̂ 0, â1, â2
Finally, we assume that, in addition to the coupling between the teams introduced
by the shared design variables x0 , there is further coupling relating to parameters
needed by the teams to evaluate their constraints and also the overall objective – i.e.
that team 1 produces interdisciplinary information a1 needed by team 2, and that team
2 produces interdisciplinary information a2 needed by team 1.
Note that, for simplicity, we are considering here only two design teams; however
the following description is generalisable to problems with greater than two teams.
3.2 Architecture
Collaborative Optimization (CO) is a popular architecture that attempts to deliver the
three aims of MDO described in Section 2.2. CO defines a subsystem problem for
each design team and a further system problem that coordinates the subsystems. A
schematic of the architecture is given in Figure 1.
We will also now introduce star notation to indicate the choices presently made by
each subsystem and the corresponding results of subsystem analyses:
To evaluate the consistency of the subsystems with respect to the global problem,
CO defines a set of equality constraints, known as consistency constraints based
on discrepancy functions that calculate the squared Euclidean distance between the
subsystem choices/results, and the system-level targets. The overall system problem
formulation is therefore given by:
where:
c1 px̂, â1 , â2 q
1
2
||x0,1 x̂0 ||2 ||a1 â1 ||2
c2 px̂, â1 , â2 q
1
2
||x0,2 x̂0 ||2 ||a2 â2 ||2 (2)
minimise D1
x0,1 ,x1
12 ||x0,1 x̂0 ||2 ||A1 px0,1 , x1 , â2 q â1 ||2
subject to g1 px0,1 , x1 , A1 px0,1 , x1 , â2 qq ¤ 0 (3)
where A1 p.q is the disciplinary analysis for subsystem 1 that provides a1 , together
with any other variables needed to evaluate the local constraints (for notational sim-
plicity, these additional variables are not shown).
There is an analogous problem for the second subsystem. Its problem formulation
can be expressed as:
minimise D2
x0,2 ,x2
12 ||x0,2 x̂0 ||2 ||A2 px0,2 , x2 , â1 q â2 ||2
subject to g2 px0,2 , x2 , A2 px0,2 , x2 , â1 qq ¤ 0 (4)
3.3 Process
CO is a bi-level architecture, in which the system is the upper-level problem and the
subsystems are lower-level problems. There is therefore a requirement to solve the
subsystem problems for every candidate set of targets generated by the system prob-
lem. The sequencing works as follows:
4 Example
4.1 Overview of the design problem
To illustrate the application of collaborative optimization, consider the design of a long-
span bridge. The organisation tasked with designing the bridge operates with two
design teams:
1. The superstructure team, who will design the towers and supporting cables for
the bridge;
2. The deck team, who will design the deck of the bridge.
The decision problem is to find a consistent design for the bridge which minimises
the build cost, subject to constraints on the strength of the bridge. In this example, the
two design teams do not share any design variables, but they do have interdisciplinary
couplings resulting from the forces that the deck exerts on the superstructure and vice
versa.
The overall configuration is shown in Figure 2; the notation used in the figure is
introduced during the following discussion.
p q
concepts shown in Fig. 1. Let us assume that the cases: 1) lane load across entire bridge, and 2) lane load
4.3.3 Interdisciplinary coupling variables a2 and disciplinary analysis A2 x0,2 , x2 , â1
As mentioned in Section 4.2.3, the deck generates vertical force on the superstructure.
The force is equal across the superstructure, due to the prismatic geometry of the deck
and (pre-determined) equal spacing of the cables, so can be represented as a scalar
– here denoted v. The deck will also be subjected to horizontal forces that depend on
cable angles arising from the chosen cabling concept – since the choice of concept is
unknown to the deck team, these forces are provided as copies â1 – here denoted as
h1 .
The disciplinary analysis provides the vertical force v, together with the other
forces needed to evaluate the local constraints.
4.3.4 Discrepancy
harp cable diametre
function D2 and local (same
constraints
for all cables)g2 . pq d plateweb thickness
girder
web depth
tweb
d
semi-harp cable diametres (i = 1 to 19) di bottom flange width bbot
The deck subsystem
suspension attempts
vertical cabletodiametre
minimise the ddeviation
v of its interdisciplinary cou-
bottom flange thickness tbot
parabolic cable diametre dp
pling variable v from a target. Like the superstructure subsystem, stiffener
it also spacing
attempts
crossbeam standard size
sstiff
Scross
to minimise tower
deviation from
(same for
tower height
a target build cost,dHwhich
cross-sectional depth
tower places a requirement
slab thicknesson the tslab
tower
disciplinary analysis
all four to cross-sectional
compute the widthbuild cost w oftower
the deck.reinforced
The overall discrepancy
slab thickness tslab
concepts) d
function is denoted area of main reinforcing steel Atower concrete soffit thickness tsoffit
deck .
spacing of shear stirrups
In the deck subsystem, local constraints gdeck . relate
stower
pq box interior web thickness
to a variety
girder of flexural
exterior web thickness
tint
text
strengths, shear strengths and deflections. section depth d
on centre span only. The design constraints considered deck longitundial reinforcement Aslablong
by the deck group for the steel plate girder concept in- deck transverse reinforcement Aslabtran
clude combined axial/flexural strength in the plate girder soffit longitudinal reinforcement Asoffit
4.4 System problem at locations of maximum positive and negative moment,
shear strength in the plate girder, deflection in the plate
The systemgirder,
problem forinthe
the bridge manages the targets for the interdisciplinary
bars, and $31 150 cou-
/m3 for steel in the plate
h1 andinv 1the
buckling plate girder web and flanges, flex- reinforcing
pling variables:
ural strength . There areflexural
slab, and no shared
strengthdesign
in the variables to manage,
girder, crossbeam, and the
and cables.
crossbeam.
system problem doesThenot design constraints
concern considered
itself with bythe
the subsystem
deck design variables xsuper
group for the reinforced concrete box girder include com-
and xdeck , these being left to the individual teams.
bined axial/flexural strength with moment magnification 3
Unlike inat alocations
conventional
of maximum CO architecture,
positive and negativethe system Collaborative
moment, node in thisoptimization
example does
not directly shear strength
evaluate in the
the webs, transverse
objective to beflexural strength–inin this case, total build cost for
minimised
3.1
the bridge. the slab, and deflection.
Rather, it decomposes the total cost into targets
The overall system objective was the1 minimization
for the superstructure
and deck subsystems to meet,
of cost. We considered given
only by fsuper andcosts.
volume-proportional
1 respectively.
fdeck
Disciplinary analysis
This approach
is close in spirit to the
These costs MDOmaterial
included architecture
costs and known
some labor ascosts.
analytical target cascading
The analyses (ATC) group and the deck
for the superstructure
3 3
The unit costs were $78.5 /m
that is used widely in the automotive industry. for concrete, $4200 /m for group are shown in Fig. 4. The scalar isuper is an integer
The system problem aims to minimise the sum of the subsystem build cost targets,
1
i.e. fsuper 1 . To produce a consistent bridge design, the discrepancy terms must
fdeck
be reduced to zero in each of the subsystems. The system problem therefore includes
equality constraints dsuper 0 and ddeck 0.
modelled, across teams – with potentially serious consequences for the validity of the
objective and constraints assessments.
Collaborative optimization is an example of an IDF architecture. Other examples
include analytical target cascading (mentioned in Section 4.4) and quasi-separable
decomposition (QSD).
6 Further reading
• Martins J.R.R.A., Lambe A.B. Multidisciplinary design optimization: A survey of
architectures. AIAA Journal 2013;51:2049–2075.
• Balling R., Rawlings M.R. Collaborative optimization with disciplinary conceptual
design. Structural and Multidisciplinary Optimization 2000;20:232–241.