Introduction - Computational Analysis and Design of Bridge Structures - page 14

First, the tedious routine work of establishing the mechanic models of a
bridge should be completely automated. Bridge engineers should be relieved
for more creative works. Taking advantage of modern database and visual-
ization technologies, establishing an engineering model of a true bridge proj-
ect should be the centerpiece of a bridge software system. It is true that an
engineering model is much more complicated than an abstracted mechanical
model; however, the goal is achievable when a commonly used bridge type
is the focus. Having the engineering model as the core, the engineers' inter-
face will only be editing parameters in a 3D scene that reflects parameter
changes in real time as a virtual bridge project. As illustrated in Figure 18.26,
engineers should be able to describe a bridge project starting from roadway
geometry to girder profiles. Modern visualization technologies should pro-
vide engineers instant realization of dimension changes in a virtual project.
The design or description process will be interactive and intuitive. For exam-
ple, an engineer can click a steel plate as shown in Figure 18.26 to pop up
a data form that allows verification or changes in its definitions on the fly.
When there is a need to perform a certain type of analysis, the questions
that need to be asked, such as “what type of analysis model is appropriate”
and “how do we establish the required FEA model,” will no longer be the
direct interest of engineers. The establishment of a required FEA model from
the engineering model should be automatic and instant. The analysis result
should be directly and instantly represented into the engineering model in
terms of engineering meanings, such as color-coded surface rendering that
reflects load ratings, rather than ordinary mechanical values. Figure 1.13
Figure 1.13 A hybrid view of a bridge model and its FEA model.