Beruflich Dokumente
Kultur Dokumente
SOFiSTiK 2016
SOFiLOAD
Loads and Load Functions
SOFiSTiK AG
The manual and the program have been thoroughly checked for errors. However, SOFiSTiK
does not claim that either one is completely error free. Errors and omissions are corrected as
soon as they are detected.
The user of the program is solely responsible for the applications. We strongly encourage the
user to test the correctness of all calculations at least by random sampling.
Front Cover
Project: MILANEO, Stuttgart, Germany | Client: Bayerische Hausbau and ECE | Architect: RKW Rhode Kellermann Wawrowsky
| Structural Engineering for Bayerische Hausbau: Boll und Partner | Photo: Dirk Mnzner
Contents | SOFiLOAD
Contents
Contents i
1 General 1-1
Literature 2-3
SOFiSTiK 2016 i
SOFiLOAD | Contents
ii SOFiSTiK 2016
Contents | SOFiLOAD
iv SOFiSTiK 2016
General | SOFiLOAD
1 General
Loads are organized in load cases, which are members of a unique action. Load
cases are addressed via a number, while the action is designated by up to 4
characters, 48 combinations have been reserved for designated types of ac-
tions.
The combination of the load cases within the actions may be done in a very gen-
eral way, there are however three predefined combination methods: permanent,
optional, exclusive.
The final combination of the actions is then done within MAXIMA or AQB via
combination coefficients () and safety factors (), which may vary in there value
from load case to load case, but will be always applied with the same kind of
factor.
The loads are either already in the database or may be defined via SOFiLOAD.
If the element mesh is changed, SOFiLOAD has to repeat the elemental assign-
ment. Beside that you may specify nodal or elemental loads directly as known
from other finite element systems. Those loads will be deleted however if the
element mesh is changed or explicit redefinition of a load case takes place.
Record names and items have been change compared to former definitions
in SOFiSTiK to become more simple and unified. Thus it is not possible in
general to copy old CADINP-data, but the export-function may be helpful in many
cases. All input load values will be converted according to the units defined in
SOFiSTiK. DIM.
There are also possibilities to generate loads from results in the database.
These are especially support forces converted to loads, imperfections, creep
deformations or prestressing effects.
This manual starts with the simple nodal and elemental loads, will then cover
the geometric load definitions and finally come to the more complex load gener-
ators.
2 Theoretical Principles
When the mesh density is increased, you will have different load patterns for a
distributed load, but the same for a point load. This indicates also that a given
mesh has a distinct resolution for load distributions. The coarser mesh can not
distinguish between two point loads, a distributed load or a point load between
the nodes.
On the other side this states that a load may be specified as a single nodal load
only if the size of load is less than the element mesh size. If you refine the mesh
near that load point you will get higher and higher stresses or forces, as the
finite elements will approximate you infinite solution better and better. So you
choose either a mesh size not smaller than the minimum load distribution area
(thickness for plates for example) or you have to specify the loads as distributed
loads.
From that we conlude further, that the generated nodal loads by SOFiLOAD may
be only as accurate as the given Finite Element mesh.
For beam loading we have the special case, that loading is also defined within
the element having an effect on all internal forces. But we have to distinguish
between a standard FE-Beam-Element having only cubic displacement func-
tions and a more generalized Beam Element according to the Transfer-Method.
The first will require a finer mesh to model complex loading accurately, the latter
may have restrictions on the modelling of the stiffness. (Piece-wise constant in
STAR2 e.g).
Cables and trusses will be prestresses by some external influence. For fixed
ends these strains will introduce the prestress, for flexible supports you will get
deformations diminishing your given prestress. If you want to achieve a given
value of prestress you have to define external loading or use an element with
low stiffness and the given prestress.
For beams you may specify a statically determinate part of the prestress by the
tendon force and its eccentricity and inclination. The distribution along the axis is
linear for the stress, but cubically for the eccentricity. The effect of the prestress
has to aspects. First we have the additional forces within a section, second we
have deformations, introducing new forces if constraints exist.
Literature
[32] E. Miranda and V.V. Bertero. Evaluation of Strength Reduction Factors for
Earthquake-Resistant Design. Earthquake Spectra, 10(2):357379, 1994.
[33] R. C. Nelson. Depth limited design wave heights in very flat regions .
Coastal Engineering, 23, 1994.
[34] N.M. Newmark and W.J. Hall. Earthquake Spectra and Design. Engineering
monographs on earthquake criteria, structural design, and strong motion
records. Earthquake Engineering Research Institute, 1982.
[35] US Army Corps of Engineers. Coastal engineering manual (CEM), 2008.
[36] A.M. Reinhorn. Inelastic Analysis Techniques in Seismic Evaluations. In
P. Fajfar and H. Krawinkler, editors, Seismic Design Methodologies for The
Next Generations of Codes Structures, pages 277287. Balkema, Rotter-
dam, 1997.
[37] G. Rosemeier. Winddruckprobleme bei Bauwerken. Springer-Verlag,
Berlin-Heidelberg-New York, 1976.
[38] H. Ruscheweyh. Dynamische Windwirkung an Bauwerken. Bauverlag,
Wiesbaden/Berlin, 1982.
[39] H. Schmidt. Meteorologische Grundlagen der Windlastermittlung in der
Bundesrepublik Deutschland, .
[40] L. Skjelbreia and J. Hendrickson. Fifth Order Gravity Wave Theory. Pro-
ceedings of 7th Coastal Eng. Conf., pages 184196, 1961.
3 Input Description
[mm] 1011 Implicit unit. Implicit units are categorised semantically and de-
noted by a corresponding identity number (shown in green). Valid
categories referring to the unit length are, for example, geodetic
elevation, section length and thickness. The default unit for each
category is defined by the currently active (design code specific)
unit set. This input default can be overridden as described above.
The specified unit in square brackets corresponds to the default for
unit set 5 (Eurocodes, NORM UNIT 5).
Record Items
GRP NO VAL CS WIND CW CFR
ACT TYPE GAMU GAMF PIS0 PSI1 PSI2 PS1S
GAMA PART SUP TITL
LC NO TYPE FACT FACD DLX DLY DLZ
GAMU GAMF PIS0 PSI1 PSI2 PS1S
GAMA CRI1 CRI2 CRI3 TITL
NODE NO TYPE P P2 P3 P4 P5
P6 P7 FRAD EXX EYY EZZ
CABL FROM TO INC TYPE PA PE
TRUS FROM TO INC TYPE PA PE
BEAM FROM TO INC TYPE PA PE A
L EYA EZA EYE EZE REF
REFT
BEPL FROM TO INC TYPE P A
EY EZ REF REFT OPT
QUAD FROM TO INC TYPE P X Y
Z DPX DPY DPZ NTYP VTYP
BRIC FROM TO INC TYPE P X Y
Z DPX DPY DPZ NTYP
COPY NO FACT TYPE FROM TO INC REF
DX DY DZ ALPH WIDE YEX
PROJ
LAR NO NAR GRP GRP1 GRP2 GRP3 M
N T X1 Y1 Z1 X2
Y2 Z2 X3 Y3 Z3 X4
Y4 Z4
POIN REF NO TITL PROJ WIDE NREF TYPE
P X Y Z
LINECURV REF NO TITL PROJ WIDE NREF TYPE
Table continued on next page.
Record Items
P1 X1 Y1 Z1 P2 X2
Y2 Z2 ...
P6 X6 Y6 Z6
AREA REF NO TITL PROJ WIDE NREF TYPE
P1 X1 Y1 Z1 P2 X2
Y2 Z2 ...
P6 X6 Y6 Z6
VOLU REF NO TITL TYPE P1 X1 Y1
Z1 P2 X2 Y2 Z2 P3
X3 Y3 Z3
EXPO NO TO PASS
EVAL TYPE NO NAME IND
CTRL OPT VAL V2 V3 V4
ECHO OPT VAL
RESP TYPE CLAS MOD SA SB SMIN TB
TC TD TE K1 K2 ZONE AG
AH AV BEZ
FUNC T F T1 TMIN TMAX S F2
T2 F3 T3 F4 T4 TITL
ACCE TYPE NO AX AY AZ AXX AYY
AZZ WXX WYY WZZ REF REFX REFY
REFZ ARED AH GH LINF
STEP N DT LCST TITL
GAX NO S X Y Z R A
R2 NX NY NZ ALF INCL INCR
TYPE TITL
LANE NO TYPE WR WL SA SE YCA
YCE YRA YLA YRE YLE L HSA
HSE INCA INCE HEFF BEFF DEFF INCD
ASL
TRAI TYPE P1 PFAC WIDT PHI PHI2 PHIS
PHI4 V FUGA XCON YEX DIR DIRT
Table continued on next page.
Record Items
FRB DAB BOGI FRBO DABO WHEE FRWH
DAWH
TRPL P PB PW PF PFAC DIST A
DPOS DMIN DMAX Y Y2 HW ZW
HF PHI B BW LW SNO FRB
DAB BOGI FRBO DABO WHEE FRWH DAWH
CONT
TRBL P PB PW PF PFAC VARI A
L LMAX LDEL Y Y2 HW ZW
HF PHI B BW LW SNO FRB
DAB BOGI FRBO DABO WHEE FRWH DAWH
TREX NO GRP SNO NODE OPT
WAVE TYPE H T D SWL DX DY
DZ UC EXPU RHO NF TMIN TMAX
GAM ALF SIGA SIGB S PHI
WIND CODE ZONE CLAS DX DY DZ XREF
YREF ZREF DXR DYR DZR GH HMIN
VR VB
WPRO H V VBOE TLON TLAT TVER LLON
LLAT LVER
WROU SEA A1 R1 A2 R2 ... ...
A9 R9
WTOP TYPE XM YM ZM DX DY DZ
H B
WSPE TYPE A1LO A2LO A3LO BLO CLO
A1LA A2LA A3LA BLA CLA A1VE
A2VE A3VE BVE CVE C3E KUU KUV
KUW KVU KVV KVW KWU KWV KWW
WGEN LCG SPEC LCOH HIST T DT FMIN
FMAX FDEL HTYP NR0 NR1 NR2 NR3
NR4 NR5 NR6 NR7 NR8 NR9 TO
Table continued on next page.
Record Items
WIPT X Y Z GRP TOL ELIM MNAM
GRP
Without specification all elements will be used. If defining values only the se-
lected groups will be used for the following load cases. This selection will be
needed only for those cases where the geometric selection is not sufficient.
The selection of groups may be different for different load cases. For very com-
plex load patterns you may generate the loading within several load cases and
combine them then via the command COPY to a single load case.
Values WIND to EIGT will be needed only for wind loading. Hereby the re-
quested option for static wind is the peak value (GUST), while the dynamic wind
needs the mean value. (MEAN). The values EIGB and EIGT will be needed only
for the evaluation of the derivativa, see WGEN.
The value CW defines a global factor to the wind pressure coefficients. The
pressure coefficients are defined for plane elements via the record name QUAD,
for beam elements they are defined with the sections. Reduction factors are
f.e. defined for chimneys as a function of the total height.
The value CFR defines the frictional coefficients cfr according Table 10.13.1. of
EC 1 part 2-4:
With CS you may select between different variants of cross sections defined in
AQUA with different wind loading areas and roughness values.
As type of the action one may use any literal with up to 4 characters, however
some combinations are reserved for special purpose. They are defined in the
corresponding INI-files and will follow the designation of the selected design
code as close as possible. An overview is given in the table below. Furthermore,
it is possible to subdivide each action with up to two characters in categories,
designated with a character from A to Z, each having distinguished combination
coefficients or safety factors. The category will be appended with an underscore
to the name of the action.
Each category has its own combination values and its own load cases and a
default superposition rule within the action category,
Each Category comprehends all its categories, i.e. one may select either a
sub category on its own or all categories by the generic name of the category.
(Q selects all Q_?)
act ion G
loadcase
loadcase
act ion Q
loadcase
loadcase
loadcase
loadcase
Figure 3.1: Structure of the actions, their categories and their load cases
For example there are for road bridges in EC1-3 for the uniform life load UDL and
the movable double axle different combination coefficients. For simple cases
one will define a load case for every span of type L_U (UDL), to be superim-
posed conditionally, while the discrete load cases of different load positions of
the double axle will be defined as type L_T and exclude each other. All load
Finally any individual load case may have its own combination factors assigned
in SOFiLOAD. (see LC). This should be avoided however and a definition of
combination coefficients in MAXIMA is then at least ambiguous and of little use
therefore.
The actions indicated in the table are used only as preset action, provided that
they are available in the INI-file of the selected design code.
The entries within one row with preceding Z for additional loading and S for
special loading may be treated in AQB as belonging to the same action.
Further there is an action GA for dead weight for the check of stability (Buoyancy,
overturning etc.) with = 1.10/ 0.90 instead of = 1.35/ 1.00.
Action 0 1 2
Q: Payload for buildings [0.70] [0.50] [0.30]
- Q_A Housing [0.70] [0.50] [0.30]
- Q_B Offices [0.70] [0.50] [0.30]
- Q_C Assembly rooms [0.70] [0.70] [0.60]
- Q_D Sales rooms [0.70] [0.70] [0.60]
- Q_E Storage rooms [1.00] [0.90] [0.80]
Live load for buildings
- Q_F truck load < 30kN [0.70] [0.70] [0.60]
- Q_G 30kN < truck load < 160kN [0.70] [0.50] [0.30]
- Q_H Roofs [0.00] [0.00] [0.00]
L: Live loads according EC 1.3 etc.
- L_T Tandem Axle of LM 1 [0.75] [0.75] [0.20]
- L_U UDL loading of LM 1 [0.40] [0.40] [0.20]
- L_C Load model UIC 71 ( = 1.45) [0.80] [0.80] [0.00]
- L_D Load model SW/0 ( = 1.45 [0.80] [0.80] [0.00]
- L_E Load model SW/2 ( = 1.20) [0.00] [0.80] [0.00]
Action 0 1 2
Live load for buildings
- L_F truck load < 30kN [0.70] [0.70] [0.60]
- L_G 30kN < truck load < 160kN [0.70] [0.50] [0.30]
- L_H Roofs [0.00] [0.00] [0.00]
S: Snow for buildings [0.60] [0.20] [0.00]
- S_L = buildings up to 1000m elevation [0.50] [0.20] [0.00]
- S_H = buildings above 1000m elevation [0.70] [0.50] [0.20]
- For SIA 260 with PSI0 as elevation h 1-60/ h 1-250/ h 1-1000/ h
W: Wind for buildings [0.60] [0.50] [0.00]
T: Temperature (no fire) for buildings [0.60] [0.50] [0.00]
F: Settlements [1.00] [1.00] [1.00]
Other actions [0.80] [0.70] [0.50]
A definition of ACT will reinitialize the action with the defaults defined in the
INI-file depending on the category of the design code. Values GAMU to PS1S
replace the predefined values. The user should check the defaults in all cases.
Deviations of the PSI-values for wind and temperature especially for bridges
or other non buildings are to be expected as all values are "boxed values" de-
pending on individual or country dependant settings. For example you will find
in OENORM B 4750 categories with trucks between 30 and 60 kN with values
augmented by 0.1 for 1 and 2 .
For all EN codes as well the SIA codes there are two defaults for the live load for
buildings with the categories F,G and H. The user can choose, whether the live
load for buildings should be in an own action L (with categories L_F, L_G and
L_H) or whether these categories should be a part of the action Q in addition to
the payloads for buildings (categories Q_A till Q_H).
If the category of the design code or the design code is changed in AQUA, all
actions should be redefined. ACT INIT deletes all defined actions and superpo-
sition rules if specified in SOFiLOAD.
With the specification of ACT all subsequent load cases in SOFILOAD will then
have this action type as default.
PART defines, to which action of the selected superposition equation the input
action belongs. The actions in the superposition equations are distinguished
according to their temporal variances:
Thus the item PART allows the correct classification of user-defined actions, but
also of special cases as for example PART G SUP ALEX (always but exclusive,
it means, that only one load case is always used). Exclusively the item SUP
controls, how the load cases which are a part of the actions are used for the
superposition (always, conditional, mutually exclusive).
Meant for example PART P, that the input action is used in the equation part
Pk for superpositions for ultimate and serviceability limit state (EC,DIN, DIN-FB,
see manual MAXIMA, chapter 2).
The item PART depends on TYPE for preset actions. For example PART G is
the default for the actions G, G1 and G2, PART P for the actions P and C, PART
Q for the actions Q and L, PART A for the action A and PART E for the action E.
The item PART has to be input for user-defined actions. Otherwise the user-
defined actions get PART Q (default).
The item SUP defines the default treatment of multiple load cases within an
action. The default will be taken from the INI-File, but for free defined types of
actions it is EXCL in general, if the type of the action has a leading Q it will
become COND and for a leading G it will be PERM.
In MAXIMA one may overwrite this for any particular load case of an action or
recombine load cases (e.g. 0.7*LC_101(Ex)+0.5*LC_102(Ey)). Due to historic
reasons there are special literals at record LC in MAXIMA in addition to the
literals of SUP:
SOFiLOAD MAXIMA
Remark
ACT SUP LC TYPE
PERM G always (permanent), safety factor action-wise
PERC PERC always (permanent) with variable factors, safety fac-
tor load-case-wise
COND Q conditional (only unfavourable)
EXCL A* mutually exculsive
EXEX Ano mutually exclusive but conditional inclusive cate-
gories (only within an action), MAXIMA record LC
only one alternative group number Ano
UNSI W changing sign (e.g. earthquake)
USEX X* changing sign, mutually exclusive
ALEX AG1 always but exclusive (only within an action)
F additional load case to be combined
Using SUP PERM the same safety factor is used for all load cases of a perma-
nent action (e.g. ACT G). In this case the sum of the values of the single load
cases is decisive, whether the unfavourable (GAMU) or the favourable (GAMF)
safety factor is applied. In the contrast to that the safety factors are considered
load-case-wisely, if SUP PERC is defined. Here one load case of the permanent
action can get GAMU and another GAMF.
SUP EXEX excludes only categories against each other within an action
(no exclusion of different actions). If for example the categories X_1 and X_2
of the action X are defined with SUP EXEX, then only the most unfavourable load
case is used either from X_1 or from X_2 and also only, if it has an unfavourable
contribution. In the contrast to that an unfavourable load case from X_1 and an
unfavourable load case from X_2 are used for the input of SUP EXCL.
The total mechanism of the defaults for the action types is governed by the
following rules:
By selecting a design code within AQUA all definitions given in the asso-
ciated INI-File in the [action] -section will become available. If no such file
is available, defaults in the program are available for all EC and newer DIN
(since year 2000). For all other cases there are exactly two predefined ac-
tions G and Q without any coefficients or factors.
When addressing an action, a copy of this definition is created in the
database which has then the possibility of deviating factors if explicitly de-
fined with this record or via the SOFiPLUS menus.
When creating a load case, the factors are copied from the action definition
to the load case. However those factors may be modified for any individual
load case.
For special design purposes the factors may be changed temporarily when
using the load cases in AQB.
The load groups PART Q_1 till Q_9 can be used for a better formation of combi-
nation without intermediate superpositions in MAXIMA e.g. for the load models
of the bridge design (EN 1990/A1). If different load groups are defined for cate-
gories with corresponding inputs for the item SUP, then the intermediate super-
positions and the following superpositions are done in one MAXIMA run.
Example:
PROG SOFILOAD
HEAD
ACT XY_1 gamu 1.4 0.0 0.6 0.4 0.2 0.6 PART Q_1 SUP excl
ACT XY_2 gamu 1.3 0.0 0.5 0.3 0.1 0.5 PART Q_1 SUP excl
ACT XY_3 gamu 1.45 0.0 0.6 0.3 0.0 0.6 PART Q_2 SUP exex
ACT XY_4 gamu 1.35 0.0 0.5 0.2 0.0 0.5 PART Q_3 SUP exex
...
PROG MAXIMA
HEAD
COMB 1 desi TYPE desi BASE 2100
ACT XY_1
LC -1
ACT XY_2
LC -1
ACT XY_3
LC -1
ACT XY_4
LC -1
or
First of all three load groups Q_1, Q_2 and Q_3 are defined with PART in the
program SOFiLOAD. The categories XY_1 und XY_2 are a art of the load group
1. Their load cases are mutually exclusive only within the respective category
about the input SUP EXCL. The categories XY_3 and XY_4 are a part of the
load groups 2 and 3. All load cases of both categories are mutually exclusive
about the input SUP EXEX.
With one of the MAXIMA combinations then the superposition is done as follows:
First of all MAXIMA searches which load cases of the load group 1 are decisive
(possible one ore two or no load case = first intermediate superposition).Then
the decisive load case of the load groups 2 and 3 is determined (possible one
or no load case = second intermediate superposition). In the last step the final
superposition is done. Either the decisive load cases of the load group 1 or the
decisive load case of the goups 2 and 3 are here the final result.
LC
The factor of the load case has (despite the wind load generator) no specific
influence in SOFiLOAD and may be changed later at any time by any analysis
program. Loads will be multiplied by this factor only when used in the analysis
itself. The factor FACT affects all forces and moment loadings, however, not
temperature, strain and prestressing loadings! It does also not affect dead load
factors FACD, DLX, DLY or DLZ.
The components of the dead weight will be in the positive direction of the re-
quested global axis. You have to enter the correct sign for DLX to DLZ. If you
specify only FACD, SOFiLOAD will apply the dead load in the direction defined
as the gravity direction. A definition will delete all loads of this load case auto-
matically.
As type of the load case on may specify the name of an action. Only predefined
or explicitly defined actions may be used with LC (see ACT). If the load case is
supposed not to be assigned for an action, the literal NONE or - has to be input
for TYPE. There are also some special literals possible, assigning a (e.g. non
linear) load case to be of a spcific type used for special design tasks:
Values GAMU to PS1S belong to the action TYPE in general. However they
may have individual values for every specific load case. Thus at the time of the
creation of a load case, the current values from the action will be taken as default
for the individual load case for Version 23. Starting with version 2010 however
only the explicitly defined values will be kept, all other values will adopt to those
of the action itself if the action is changed.
Values CRI1 to CRI3 are very general parameters of the load case. They may be
used freely for postprocessing via DBVIEW. You may specify them in advance
or set them after the analysis by reading some results from the database. (e.g.
a system dimension, a strength reduction etc.) TALPA uses CRI1 for the safety
factor of the material needed by analysis according to Fellenius.
A load case imperfection will be defined with TYPE IMP. The load cases of this
type allow to use imperfection loads for the definition of load case combinations
for the analysis according to second order theory. These load cases can not be
used for a linear analysis of single load cases with ASE, STAR2 and also not for
a superpositon of the linear load cases with MAXIMA.
Defining TYPE EINF a load case will be declared as influence line. You have to
specify at least one load to select the value, the influence line is intended for.
You need a separate load case for any value to be treated, but then the influence
line will have all components of loading available. For an influence line load case
only deformations in global coordinates are printed in general.
Example for the influence line for moment MY at beam 1001 at location 2.0 to
be saved as load case number 91:
LC 91 EINF
BEPL 1001 DY 1.0 2.0
Via this concept you may compute very special influence lines. If you want to
know the influence line for the upper normal stress of a section = N/A - M/W,
you may define this via (Area A is #A, momentum resistance W is #W:
LC 92 EINF
BEPL 1001 WX 1.0/ #A 2.0
BEPL 1001 DY -1.0/ #W 2.0
For plates and shells there are special load types for QUAD, allowing the neces-
sary dirac-delta load to be defined.
To a establish and to evaluate many or all possible influence lines, the proce-
dures provided by program ELLA are far more easier and faster.
P1 Load values [] !
P2 up to seven depending on load type [] -
P3 [] -
P4 [] -
P5 [] -
P6 [] -
P7 [] -
FRAD Radial factor for load values LT -
R multiply with radius
RR multiply with square of radius
Local load directions require nodes with a local coordinate system (SOFiMSHC).
Only nodes which are input as structural points (SPT points) with a local coor-
dinate system in SOFiMSHC can be used here. If no such system is found, the
global coordinate directions will be used instead.
For special cases you may multiply the load values with the radius (e.g. centrifu-
gal forces, internal pressures etc) or with the square of the radius. The radius is
the distance of the node to the global axis which has been selected as gravity
direction.
In the case of axial symmetry load values are interpreted as circumference re-
lated, e.g. a radial load of 2 kN/m must be provided as PYY 2.0. The program
then automatically accounts for the radial position of the load application point.
CABL is loading a range of cable elements with the same loading. Instead of
a number FROM you may enter the literal GRP and the group number at TO to
select all elements of a group.
TRUS is loading a range of truss elements with the same loads. Instead of a
number FROM you may enter the literal GRP and the group number at TO to
select all elements of a group.
Loading on truss elements will be converted to nodal loads, as the element has
no basic bearing capacity transverse to the element. Thus it is recommended to
insert nodes at all important points of a truss.
See also: LC, NODE, TRUS, CABL, QUAD, BRIC, COPY, free-loading, BEAM, BEPL
Loading on Beams will be defined either via trapezoidal loads via BEAM or as
Point loads via BEPL or as general variant loading via multiple BEPL function
values.
The extensions of the loading will be referenced always to the total set of se-
lected beam elements. The position within the section is always based on the
beam axis. I.e. for a centric beam this will be the gravity axis, for an eccen-
tric beam it will be the reference axis which is in the origin of the cross section
coordinate system. The default however is always "gravity center". The input
reference system may be changed for every single beam loading.
The beams will be appended despite their position in space in the sequence of
their element numbers from start node to end node. Numbers may be missing
within the sequence. If the coordinates of two successive beams do not match
a message will be issued if the value of INC is defined explicitly.
PE
PA
Via REF you may select different systems for the definition of the loading extent
(A and L). The extend will be converted in such cases to local beam coordinates
immediately. In general the distances are relative to the beginning node of the
beam sequence, if the following possible literals are specified with a preceeding
"-" sign, the extend will be measured in the reverse direction beginning at the
end node of the beam sequence.
XY
YY
y
z
Special attention has to be paid in those cases where the beam is not monotone
within the selected reference System. This is the case for all circular or general
closed liner systems. As the reference system is always using absolute values in
adding up the total length, we will have a total length of 2H in the depth direction
if the height of the structure is called H. A variant load depending on the depth
on both sides of the system is thus to be defined via two variant loads of length
H on the total beam system.
H
Y
Emax
Emax
The action point of the load within the cross-section can be controlled by means
of the excentricities EYA/ EYE and EZA/ EZE. Interpretation of these load ex-
centricities defaults to:
However, via the item REFT an explicit reference measure may be specified
(change of default behaviour). For REFT there are the following possibilities:
The Literal CONT for item TYPE will activate defaults from the last record:
This input defines a load ascending from 0 to 100 within the length of 2, then up
to 120 within the length five and descending than to the end.
The eccentricities of the load are defined in the local beam coordinate system
with reference to the connecting line between the nodes. This is the so called
reference axis. If not defined explicitly, this will be the center line of gravity.
Loads of type P will create moments if eccentricities are present. For nonlin-
ear analysis there will be additional geometric stiffness and forces. There is a
difference between loads acting on the upper or lower side of a section.
In all other cases, the ordinates ZA,ZE are interpreted as relative measures
and will be scaled to the actual cross-sectional dimension.
Positive values of DTY and DTZ mean that the temperature raises in the positive
direction of the corresponding y resp. z axis. Example: For a beam cross section
the temperature decreases, if 40 C are available at the side -y and 10 C at the
side +y. Thus the input reads DTY -30 [ C] . This load type is only applicable for
sections having a distinct extension or geometry.
The prestressing loadings PNX, PMY and PMZ are the result of a special im-
posed strain or curvature. If the element is fixed, the resulting forces and mo-
ments will be identical to those of the loading. However, if the element may
deform the prestress is then reduced. The opposite behaviour is given for the
tendon prestress definable with BEPL, an eigen stress state which needs de-
formability to become active. For very special cases this type of prestressing
may be also defined with load type PNXI for a whole beam in record BEAM.
The eccentricities of the load are defined in the local beam coordinate system
with reference to the connecting line between the nodes. This is the so called
reference axis. If not defined explicitly, this will be the centre line of gravity.
Loads of type P will create moments if eccentricities are present. For nonlin-
ear analysis there will be additional geometric stiffness and forces. There is a
difference between loads acting on the upper or lower side of a section.
STEL may be used to specify some standard load distributions. With a defini-
tionb of one of the following Literals at OPT a distributed loading will be defined
with a maximum value at a distinct location:
With these load types of the above table you may also specify (depending on
the number of vertices) constant, linear, quadratic or cubic distributions of the
loading along the sequence of the beams. All other vertices have to follow im-
mediately with the load type CONT. The selection information of these records
(FROM TO INC) will not be evaluated.
Attention: STAR2 combines all load definitions with the same number, this ap-
proach is not possible in SOFiLOAD. The use of TYPE CONT is mandatory but
provides more flexibility.
The loading will be only applied within the defined abscissae, you need at least
two data points therefore. If you specify only one single value, additional values
will be supplied with 0.0 for imperfections at the beginning and the end. Thus
only one value at one of the ends will create a linearly varying distribution, while
one in the middle will generate a quadratic parabola. All other load types will
become constant along the total beam sequence.
For the load type PNX the cubically interpolated eccentricities Ey and EZ will
generate moments and shear forces. It has been shown, that correct shear
forces require separate definitions for every tendon with different geometry.
Example:
defines a cubic parabola with a maximum imperfection of 1/200 at the end of the
beam sequence 101 to 110.
Table 3.19: Other special types converting data from the database
The values A, EY, EZ and REF will not be used in those cases.
With the definition of TYPE PRE the user may create prestressing loading from
the tendon stored in the database. This is normally done by TENDON. For
changes of the system or tendons defined via AQBS, SOFiLOAD will perform
this task. With OPT -1 the prestress of the reinforcement defined within AQUA
will be used.
The definition of TYPE U will generate from the displacements in the database
a similar imperfection. This is useful to generate imperfections from buckling
forms as a difference between first and second order theory. Another task is
the effect of creep on the imperfection. There are different views about how to
chose the factor P in those cases, and the question if the imperfections should
enter in the calculations twice. If needed you may subtract the old imperfections
with a factor of -1.0
N
= P (3.1)
EA
My Ez Mz Eyz
ky = P 2
(3.2)
Ey Ez Eyz
Mz Ez My Eyz
kz = P 2
(3.3)
E Ez Eyz
With the type PRIM the program will generate strains and curvatures from the
forces of load case OPT:
P= (3.4)
P = 1.0 (3.5)
All elements within the given range of numbers will be loaded. The range may be
larger than the existing numbers but must contain at least one element. Instead
of a number FROM you may enter the literal GRP and the group number at TO
to select all elements of a group.
With DPX to DPZ the user specifies global varying loads (like earth or water
pressure), P is then the value at (X,Y,Z), while DPX to DPZ describe the incre-
ment in the global coordinate directions. The Unit will be converted by the load
and the geometry unit (1001).
With NTYP the user may define additional data for the loading like a reference
number of prestress or special actions for wind loading.
Some loads, e.g. T for a fire design may be specified with a function describing
the value along the local z-axis. Up to 16 values may be defined as a pair of a
thickness and a factor. Their are three cases to be distinguished: If all ordinates
are positive, they are referred absolutely to the uppermost fibre of the QUAD-
element, if they are all negative they are referred to the lowermost fibre. In all
othe cases the reference is the mid surface of the QUAD element. If the real
thickness of the QUAD element does not match the load definition, the definition
will be scaled with a warning for the third case.
The loading types of prestress will generate a stress state and the corresponding
strains and curvatures to calculate the constraining contributions.
Load type PRE (Prestress from TENDON) will generate the loading due to ten-
don with prestress stage NTYP within the selected QUAD-elements. The load
value P should be 1.0, but other values may be useful if you want to get the
required prestress. However, the prestress in the database will not be changed
by this factor. In ASE the user has to select the appropriate construction stage
number CS in record GRP. The Input
will generate the prestress loading of the first stage on the net section. The
calculated deformations will not create additional stresses in the tendons.
For the influence areas the loading will generate a dirac-delta strain within the
centre of the elements. Load value will be 1.0 in general. The deformation of the
mesh is the required influence area. However, directly in the point of interest the
FE- approach will smooth out the singularity of the theoretical influence area.
For wind loading NTYP may specify special patterns of wind factors derived from
the inclination of the inward normal direction of the QUAD, the direction of the
gravity and the wind direction.
STD Factors according DIN 1055 Table 11/Pict 12 fpr closed buildings, but
without the extra lift off at edges and corners. These effects and wind
load on interior areas have to be specified in addition. (VTYP has no
Meaning)
CYL Wind factors for cylinders based on Reynoldsnumber (DIN/EC)
where VTYP = equivalent diameter of cylinder for Reynold number
to be evaluated from VREF (see WIND) The type CYLR allows the
direct definition of the Reynolds number at VTYP.
CYLF Wind factors for cylinders (some other design codes)
Indische Norm IS 875: load value is slenderness h/D
load value < 1.0 = IS 11510 (cooling towers).
CYLK Wind pressure for cooling towers according to VGB-Richtline BTR-
1997 Table 1
VTYP = 1.0 / 1.1 / 1.2 / 1.3 / 1.4 / 1.5 / 1.6
For the literals CYL and CYLR the pressure coefficients will be interpolated
depending on the Reynolds number between (Re = 5105 , cpmn = 2.2) and
(Re = 1107 , cpmn = 1.5). The load value should then become the reduction
factor according to EN 1991-1-4, Pict. 17.36 resp. DIN-1055-4 [9], Pict. 14:
For the literals CYLK the load value should be specified as the product of the
For wind loading the pressure at the top of the building for suction can be consid-
ered , if selected e.g. with -STD|-CYL|-CYR|-CYK where - works on suction
only, + on pressure only and * on all values.
There are the following load types available for HYDRA / DOLFYN:
T Absolute temperature K
ENTH Enthalpy Wsec/ kg
SRAD Radiosity
MIXF,FUEL,OXID Fractions for combustion
LFR Liquid fraction
QT Heat quantity W/ m2
The value of NTYP is then a number for the balances (see HYDRA manual)
All elements within the given range of numbers will be loaded. The range may be
larger than the existing numbers but must contain at least one element. Instead
of a number FROM you may enter the literal GRP and the group number at TO
to select all elements of a group.
With DPX to DPZ the user specifies global varying loads (like earth or water
pressure), P is then the value at (X,Y,Z), while DPX to DPZ describe the incre-
ment in the global coordinate directions. The Unit will be converted by the load
and the geometry unit (1001).
There are the following load types available for HYDRA / DOLFYN:
The value of NTYP is then a number for the balances (see HYDRA manual)
COPY will transfer loading from other load cases to the current load case. All
types of loading including generated loads by other programs will be copied. The
self weight created by the factors DLX-DLZ of record LC will be copied only if
not yet defined in this load case directly or with another COPY command within
this load case. The generated nodal loads from self weight will never be copied
even with TYPE INTE.
Without specification of a project name, the support forces will be read from the
current database, otherwise the loads will be taken from that database.
All load cases of an action are copied with the input of the action name for load
case number NO.
Load functions may not be copied, as every load case must have a unique load
function.
The load case NO may be created within a previous or the same input block.
All loads may be copied with a factor. As the global load factor of LC is not
applied to the loads in the database itself, the old global load factor remains out
of scope.
For a nonlinear analysis one needs the combination of several load cases with
factors normally taken from the extreme value of some important force or mo-
ment. If MAXIMA has saved this combination with the combination number nn,
it is possible to use those factors with a definition of COPY nn COMB.
However, with a literal for the item FACT the user may apply the building of a
combination of load cases for nonlinear analysis using safety factors and com-
bination coefficients. This is not a superposition like MAXIMA does. The user
has to specify the load cases in the correct sequence and selection. There is
available:
For the variable actions Q the first given load case will be treated with the special
combination value, all other will be assigned the right most coefficients.
Instead of those semi automatic values it is also possible to define literals for the
saved combination coefficients:
It is possible to select special nodes or elements. This is done with the FROM
TO range in increments of INC. For free loading (POIN, LINE, AREA or VOLU)
this will filter on the given selector.
When copying loads, it will be remembered the source of the loadings, thus
a restart (LC nn REST) will repeat the copy process and use the current load
definitions. With CTRL COPY 256 this will be supressed, the loads are then
taken as currently defined and will be treated as explictly defined loadings.
If the load case to be copied contains a load train definition TRAI, NREF must
be an identifier of a reference axis, with the specification of one of the possible
lanes with number 0 to 9 appended as additional decimal digit. DX is again the
station value along the axis.
Loads of a loadtrain will be clipped at the edges of the traffic lane. This may be
used to apply wide special trains across several lanes. The value YEX shifts all
loadings only in lane 0, in all other lanes it is applied selectively. For Railway
loadings UIC it controls the distribution of the loading on the two rails.
It has to be pointed out however, that SOFILOAD is not able to model all fancy
details of loadings as implemented in ELLA. The reason for this are for ex-
ample that a point or tandem load in ELLA may be treated at the same posi-
tion to be before or behind a point at the same time or that ELLA may decide
about favourable/unfavourable elementary based on all load components, while
SOFILOAD has to select based on the vertical loading only.
Spans will be defined with placements along the axis, if those do not exist the
segmenst defined with LANE will be taken instead. The values FROM to TO
select the spans of the lane with a loading pattern controlled by a DELT input
(the dotted line indicates the load train position specified):
4 MAX
4 MIN
3 4 MAX
3 4 MIN
1 2 3 4 5 6 7
Without definition of INC only the selected interval will be loaded, where the de-
faults for FROM and TO are the total lane. A definition of INC will change the
default to the region containing the selected DX point. If INC is zero, only the
selected range is loaded. If MAX is defined for INC also every second span
outside the range is loaded. MIN will always reverse the selected pattern. A re-
ally correct evaluation for complicated loading should be performed via influence
lines and module ELLA.
Loads will be copied as default with a factor of one, but one may specify for FACT
one of the literals DESI, RARE, FREQ, NONF, PERM to select the combination
coefficients of the load case to be multiplied with. As an alternate or additional
mean one may select with TYPE combinations for load groups according to the
EC1 or DIN Fachbericht. While without entry all loads are taken, the possible
values are:
The distribution and the reference of the loading may be controlled with CTRL
COPY.
A reference load case contains all loaded areas with their real size as AREA
loading of TYPE WIND. For more details see record AREA.
For a specific wind load case one has to specify with record WIND the direc-
tion of the wind and the profile of the wind speed along the height.
Then a COPY TYPE WIND (or the default ALL) will create the detailed pres-
sure distributions according to tables 4 to 6 of DIN 1055-4 resp. tables 10.2.1
to 10.2.4 of EN 1991-1-4 depending on the defined geometry and wind di-
rection. A positive factor selects for those regions with changing sign the
suction, a negative factor will select the pressure value. To define the load-
ing areas the outer dimensions of the building are needed. As these values
may not be derived from the load areas, SOFILOAD will use the outer box of
all active groups to evaluate these values.
Hint: The wind profile of the design codes define the air velocity along the height
for the undisturbed flow. For a slender building this distribution will be seen on
the front side (region D according picture 7.5 of EN 1991-1-4), however the rear
and the other sides (regions A,B,C and E according picture 7.5 of EN 1991-1-
4) have a rather constant suction which is referenced to the nominal reference
pressure at the top of the building. This is clearly stated in the remark of section
7.2.2. (1).
For compact buildings (H/B < 1) the same effect is observed for the front side.
The constant pressure is again referenced to the value at the top of the building
which is accounted for.
For the wave loading a COPY will create the loadings with the Morrison equa-
tion and the defined force coefficients. A shift off the wave kinematics may be
specified by the global coordinates (DX,DY,DZ). However in this case an explicit
scalar definition for DX (0.5[-] or 50[%]) will shift the wave by this fraction of the
wave length.
Free loading is a very convenient method to place loads at any location within the
structure and let the program decide how to convert it. This is especially useful
for the import of geometrically defined loading from a CAD model. The loads
will be converted by SOFiLOAD to equivalent nodal and elemental loading. For
this purpose the program will also work with pure geometrical elements having
no stiffness at all like the outer hull of a frame work. Eccentric loading may
create moments, but moments will not be transferred into a pair of forces by this
approach.
Free point and line loadings will be applied exactly once within a system. For
area loading the algorithm for that would be extremely complicated, so it has
not been implemented and there is the chance for an area loading to be applied
more than once.
3.15.1 References
If not otherwise specified (e.g. beam loading) the loading will be distributed in
general via quadrilateral elements, which may be taken from:
For all references one has to distinguish between group based types (BGRP,
QGRP and VGRP resp FGRP) and the geometric references (GPT, GLN, GAR,
GVO, GFA as well as LAR). The geometric reference will be defined automati-
cally with SOFiMSHC, but may be also defined explicitly with SOFiMSHA. This
information will be saved with the elements and the nodes.
The load may be specified to act only on certain types of structure. It may
be useful to specify if a load is intended to become a beam load or should
be converted to nodal loads. For curved reference elements it also makes a
difference and the total load sum if the eccentricities are taken relative to the
curved reference axis/area or to the polygon edges of the elements.
If no element type is specified (AUTO), the program will try to use all possible
reference types. The difference is apparent for point loads, where a AUTO-load
will always be attached to the nearest node in the end, while an area or linear
reference may decide, that this load is now off the structure.
For the search of possible elements, the following rules are implemented:
Explicit references are always unique. The load will be applied with particular
reference to the selected element.
References on geometric or element types will choose between all possible
elements to find the best fit. For AREA loading this might create multiple
loading within the same loading area, for point and line loads the elements
nearest to the load will win, a definition of WIDE is ignored if an explicit
reference REF has been given.
For an unspecific reference to a geometric item. SOFiLOAD will first try to
use the structural references, but if this fails it will switch to the corresponding
finite element. Thus GPT will become NODE, GLN to BGRP and GAR to
QGRP.
For an automatic reference the program will work first on explicit load dis-
tribution areas LAR, then GAR resp QUAD, then on GLN resp. BEAM and
last on GPT resp NODE elements. The load must be within the dimensions
of the element, only for the final loop over all nodes the value WIDE will be-
come effective. The reference MOVE will not cycle over the nodes, thus it
will discard all loads of a load train outside the structure.
Loadings on TRUS and CABL elements are applied with a ranking following all
beam elements, as these elements can not account corretcly for partial loadings
or load excentricities. Thus some selection by a reference number, a group
number or a limited value for WIDE is always necessary. This behaviour is
manadatory to avoid loading on cables of an external tendon.
WIDE WIDE
The load may be defined e.g. with a certain offset from the structure itself. It will
then act on all elements within a certain range WIDE before or behind the load
plane, even those which are perpendicular to the projection plane of the load.
The load value will be interpolated within the plane of the load definition. WIDE
will not cut through the elements, it will only select them by a logical decision to
be within the range or not. The load itself can act in any local or global direction,
however.
For the decision if a load will be attached to a specific element, the geometric
size of the point (column head or prescribed mesh size), the section of a geo-
metric line or the thickness and eccentricity of the area for QUAD elements will
be used.
For curved surfaces the user should always specify the surface GAR if the load
points are within that structural area, or select a global projection if the loading
is separate from the structure. The latter will select only elements within the
projection. The load type has no influence on this process. If WIDE has been
specified only elements before and behind the load area will become loaded. A
selection via GAR may also be used for projective loads, it will then select the
elements of this region, but will not affect the projection of the load values.
This method is based on load distribution influence areas, constructed from re-
gions either already subdivided in quadrilaterals or to be established automati-
cally in simple cases of four edges. There is a tiny plate-bending FE-program
involved creating the support forces for supported edges or edges with a beam
section. These values are permanently saved to the database.
If now an arbitrary loading is defined it will be first converted to nodal loads for
the distribution mesh of the distribution region and then within a second step it
is converted to support forces and eventually beam loading along the edges of
the area.
The other methods will load only a single distinct beam for any created part of
the loading area. For point and line loads there is a hierarchic search method,
where beams are selected based on their distance to the load. In this sequence
the load will be projected onto the beams, subdividing line loads if necessary. A
point load will be always applied entirely on one beam.
For area loading however a primary and secondary span direction is selected
(automatically or explicitly). Loading will be distributed in the secondary span
direction.
With the literals DXY, DYZ or DZX instead of an X-value it is possibel to specify
coordinates relative to the first defined load point. With literals DDXY, DDYZ and
DDZX the differences are taken relative to the last load point.
It is not required to specify a load value in all load points. Missing load values
will be interpolated before saving the load (e.g. linear variant load value along a
complex geometric curve)
The problem of multiple loading may occur if the user has defined overlapping
elements or there are multiple nodes with the same coordinates. For Point and
LINE-loads there is a rather easy way to assure, that no part of the loading will
be applied more than once. However, for QUAD-elements this is a very difficult
task. Therefore the program will load all possible elements. The user has to
define a WIDE-value which defines all elements within a distance WIDE before
or behind the load plane will be treated as loaded. For special cases a sound
group selection may be helpful.
For all loading the percentage of the active load area based on the defined
loading area respective length will be calculated and printed. A value deviating
from 100 percent will be marked. With ECHO LOAD the generated loads may
be printed and controlled.
Load distribution areas for beam systems can be generated with the record LAR.
So it is possible to define forces as free point, line and area loads at their ac-
tion position. These loads are converted then via load distribution areas into
equivalent beam loads acting on the corresponding beams. Other load types
Single beam groups can be selected with GRP1, GPR2 and GRP3. Only the
selected beam groups get then a loading. Thus e.g. a loading can be allocated
only to the transverse or the longitudinal girders within a load distribution areas.
Use of all beam groups is the default.
Every load distribution area gets a local z direction. The positive z direction re-
sults from the defined sense of rotation in analog mode to the QUAD elements.
Thus it is possible to use free loads with the load type PZ - load in local z direc-
tion.
Generationa
The coordinates of the four corners may be defined in absolute coordinates or
taken from a structural node with the definition GPT nn. Further it is possible
to enter for Z2, Z3 or Z4 one of the literals DXY, DYZ or DZX. The other two
coordinates are then taken as increments within the specified plane to the first
point. A definition of only the first two points will create a rectangle within the
appropriate coordinate planes.
For every load distribution area a load case number 10000 + NO is generated. It
can be used exclusively for the graphical check and output of the load distribution
area in the ANIMATOR or with WinGRAF.
The load distribution areas should not be defined too large, because otherwise
deductional loads will arise. A load distribution area possibly with an overhang
shown in the following pictures for a four-span bridge should be input per span.
In case of one continuous load distribution area deductional forces can arise in
the neighbouring span due to a single load.
On the other hand deductional forces are generated as planned always inside
for external loads, because they are necessary for the equilibrium.
sofiload_LAR_girder.dat
LAR_Rahm.dat
POIN is a single point load or a similar load type acting independent from the
element mesh. The program will search for points, lines or regions where to put
the load.
POIN-Loads are not singel loads with a singularity at the tip, but an energetic
equivalent for loadings in the vicinity of a node of the FE mesh. If the mesh is
refined at the tip of the POIN load, the singularities become more visible. As the
transverse loading of a plate or shell may be always spreaded to the mid surface
of the plate or shell, there is the following simple rule:
POIN loadings and point supports may be used without concerns if the element
size is larger that the plate thickness. If the mesh size becomes smaller all
loading ha to be defined as areal loading and all supports as areal support with
the true dimensions.
Explicit references are always unique. The load will be applied with particular
reference to the selected element including eccentricities if possible.
For an unspecific reference to a geometric item. SOFiLOAD will first try to
use the geometric references based on their dimensions, but if these fail
SOFiLOAD will switch to the corresponding FE-element. Thus GPT will be-
come NODE, GLN to BGRP and GAR to QGRP.
For an automatic reference the program will work on LAR/GAR resp QUAD,
then on GLN resp. BEAM and last on GPT resp NODE elements.
If the reference is NODE with an explicit number, the defaults of the coordinates
will be those of that point. Eccentricities will generate moments at the node.
For REF GLN/BGRP the eccentricities will be copied to the beam loading if
beams become active or transformed to moments in case of lines without
beams.
For REF GAR/QGRP the load will always converted to up to four nodal loads
without any eccentricities.
If several elements are possible, the first element (with the lowest number) will
win.
For the influence areas the loading will generate a dirac-delta strain within the
centre of the elements. Load value will be 1.0 in general. The deformation of the
mesh is the required influence area. However, directly in the point of interest the
FE- approach will smooth out the singularity of the theoretical influence area.
LINE and CURV describe a polygon or a curved smooth line load independent
from the element mesh. Missing load values will be interpolated by a coarser
spline in a first step for both cases.
If the reference SLN,EDG or BGRP is used with an explicit number NO, the
coordinates may be omitted. The load is then uniform along the whole line. For
the first two types non uniform load distributions may be selected with NREF.
For EDG the polygonal geometry of the line will be used, while SLN follows the
real curved geometry. If a SLN has been subdivided only in parts with beam
elements, the load will be applied only on those generated beam elements. If
the total line should be loaded, either coordinates have to be defined or the REF
EDG has to be used to generate nodal loads only.
It is possible to define more than 6 (up tp 63) data points. As there are possible
only 6 per record, the following points have to specified with continuation record
with load type CONT:
LINE may be also used to specify some standard load distributions. With a
definitionb of one of the following Literals at NREF a distributed loading will be
defined with a maximum value P1 at a distinct location:
Further it is possible to enter for X value from the 2nd load point one of the literals
DXY, DYZ or DZX. The other two coordinates are then taken as increments
within the specified plane to the first point.
For the projection of the load there are the principal possibilities:
In all cases the program has a sort of Hidden-Line algorithm to ensure that no
part of the loading is active more than once.
For the loading on load distribution areas or QUAD-Elements the program pro-
ceeds as follows:
A projection of the loading will be done into the requested region if a GAR
reference type has been chosen. All calculations will be done within the
projected area. Load segments will be treated only for the area itself.
If a global projection is selected, all calculations will be made in the global
projective plane. The load may hit several elements which should be se-
lected via the WIDE item.
Without projection and reference area the projection will be done into the
local element plane.
For an automatic reference the program will first work on areas and then on
lines.
At the element level of a QUAD even curved loading lines will be converted
to straight segments. As long as a data-point is within a QUAD element that
will establish no problems, but if the curved geometry touches the element only
slightly this will not be considered further. A finer mesh will create different load
patterns for those cases therefore.
Table 3.35: Further types of the free Line Loading for REF SLN/BGRP
Positive values of DTY and DTZ mean that the temperature raises in the positive
direction of the corresponding Y resp. Z axis. This load type is only applicable
for sections having a distinct extension or geometry.
For the prestress type of loading the load value is the force of the tendon. All the
forces, moments, curvatures and strains will be established using the geometry
of the reference axis.
Factors of WIND define additional factors for the wind pressures calculated from
the wind speed and the drag coefficients to allow the description of additional
areas or shadowing effects. (cnf. input record WIND)
For DOLFYN and HYDRA are also the same load types available in 2D for
boundary elements (SLN) as specified for the record QUAD.
AREA describes general polygon loading areas independent from the element
mesh. The load does not need to be specified in all points, missing values will
be interpolated with a least square distribution accounting for the load projection
definition. Thus up to four points with a suitable pattern will define a bilinear
(4 coefficients) distribution, more points will allow a quadratic (6 coefficients) or
bicubic (10 coefficients) distribution, but sufficient points have to be defined in
at least two directions to allow the evaluation of all coefficients. If this is not
the case, the highest degree is selected which yields unique coefficients without
further notice.
Kinks in the load values have to be defined via separate load areas.
Loading on areas (e.g. fillings with liquids and silos) may be defined with VOLU
very efficiently.
Further it is possible to enter for X value from the 2nd load point one of the literals
DXY, DYZ or DZX. The other two coordinates are then taken as increments
within the specified plane to the first point. A definition of only two points will
create a rectangle within the appropriate coordinate planes.
For the projection of the load there are the principal rules:
not defined, the program will check all areas. So multiple instances of the
loaded area might occur. However only those areas are used, where the
load is completely within the volume defined by the elements of the area.
All Interpolations and geometric calculations will take place in the projected
area. For GAR and PROJ N this is the region, which might be curved. The
data points of the load should be on that surface therefore. For a global
projection however the loading area may be situated somehow away from
the real structure.
For a automatic reference, the program will start with any defined load dis-
tribution areas, then any defined QUAD elements and structural areas and
finally work on beam elements.
The loading on beam elements is best done via load distribution areas LAR or
real QUAD elements. If such are not present, the program will establish a main
girder direction and distribute the load transverse to them on those beams fully
or partial within the loading area. Eccentricities of the load will be established as
it would be without any transverse girders. However the user has CTRL options
STOL and COTB to influence this processing.
The difference between PXX and PXP is given by the fact, that PXX is a load
referenced to the true area (e.g. dead weight) while PXP is referenced on the
projection into the XY-plane (e.g. snow). However, for planar systems there
will be no difference as the loads are always referenced on the true surface.
The component loadings define a load direction derived from a projection of the
normal of the area into the specified global projection plane (e.g. diverting forces
of tendons). The local loads based on a global load projection are required to
define earthquake loadings on fillings of tanks. A load type PXPZ will define
a horizontal projecting pressure applied in the normal direction Z of the plane.
In general the sign of the load value will be taken on the global component.
However with projection XXL, YYL or ZZL the sign of the load value will define
the local component. Thus specifying PXPZ on a circle with PROJ XX will define
a load acting depending on the orienation of the local z-axis, while PROJ XXL
will define a load acting everywhere in the same direction e.g. inwards.
For load types P and M equivalent nodal forces and moments will be established
by integrating the element shape functions.
For all other loads, creating initial stress (like temperature) over the whole el-
ement, the selection will be by hitting the loading area with the centre of the
element. This is why for irregular meshes the sum of the loading area might
deviate from the 100 % aim.
Using load distribution areas with REF LAR a moment loading is not considered!
For DOLFYN and HYDRA are the same load types available as specified for the
record QUAD.
specified TITL.
If the title is not defined or starts with the letters "CP", no conversion will be
performed.
If the title contains the text MEAN or GUST, the pressures will be created
based on the mean or gust value which can be used than with LAR areas for
beam systems, otherwise the load type WIND will be unchanged.
A number within the title is used for flat roofs as follows:
>0 The height of an Attica in m
<0 The reduction of the eaves either with an angle in degree or the
ratio of a curvature r/h
There are of course some requirements on the geometry of the loading areas:
The loading require the total outer extend of the building, defined by all
groups active for wind loading.
A planar load area may have as many load points as possible, but all points
have to be defined, that they are counter clockwise if you look from the out-
side on the surface.
A double pitched roof (saddle or through) requires at least six load points.
The first point has to be on the ridge or groove, which is required to be hori-
zontal and the inclination of the roof must match along all edges everywhere.
3
4 3
2
5 4
5
1 2
1
6 6
If a load area can not be treated an error message occurs, but it is strongly
recommended to check the load values especially if the wind attack is not
perpendicular to the structure.
It is possible to enter for X1, X2 or X3 one of the literals DXY, DYZ or DZX. The
other two coordinates are then taken as increments within the specified plane to
the first point.
A geometric description like the LINE and AREA loading is not available, be-
cause this would be to much effort. Therefore the selection of elements is only
by a sheared cube, defined by three selectable directions p1-p, p3-p2, p5-p4,
which must not be colinear.
P5
P3
P1
P
P2
P4
The load values will be interpolated within the sheared coordinate system and
added for all three directions. In most cases it will be sufficient to define only
load values P and P1 and to use the other four points only to limit the loading
ares. If the user does not supply coordinates for a direction, the program will try
to add the missing directions and treat the load value as an increment.
For the common case of a fluid pressure it is thus sufficient to define the free
surface (X or Y or Z) and the weight of the fluid at entry P1.
For DOLFYN and HYDRA are the same load types available as specified for the
records QUAD and BRIC.
For this special load type the load values have other meanings:
Values for granular fillings are given in EC1-4 Table 7.1 or DIN 1055 part 6 Table
1. For the EC lower (0.90) and upper (1.15) bounds have to be considered.
The definition of a value A/U activates the nonlinear distribution along the height
caused by the wall friction. zo defines the values in infinite depth as limit value.
A
z0 = (EC5.6/ DN5) (3.13)
Ks U
p (z) = z0 1 e(z/ z0 ) (EC5.4/ DN3)
(3.14)
ph (z) = Ch Ks z0 1 e(z/ z0 ) (EC5.3/ DN2)
(3.15)
p (z) = C Ks z0 1 e(z/ z0 ) (EC5.2/ DN1)
(3.16)
Further this definition will apply the factor Cb 1.2 for all flat base plates (<
20 degree) according to equation EC-5.14/DIN-14. For hoppers (> 20 and
< 70 degree) the transition from the walls to the hopper will be detected au-
tomatically and the load distribution according to equations EC (5.15) to (5.18)
will be established. Here DIN has slightly different formulas (16) to (23).
EXPO
With the command EXPO you may write the loads form load cases in the
database to a input file for SOFiLOAD. This may be useful in special cases,
but you have to keep in mind that during the input processing always some infor-
mation gets lost (e.g. local to global transformations), so the user should check
the resulting data to be sure that nothing is missing.
If the filename is not specified the data will be appended to the most lately de-
fined file or set to project_LFD.DAT.
1 only nodal and elemental loads will be exported, but including all
generated loads.
1024 only those free loadings are exported which have not been applied
with 100 %.
With command EVAL one may evaluate expressions with the actual load vector
of defined or generated nodal forces with displacements of other load cases in
the database and supply these values to CADINP for the next input block (after
the END-record) as a variable. This is an evaluation of an influence area or an
integral over a given displacement function and is very helpful for some special
loading.
If for example a constant area load with value 1.0 is specified, the result of RU
will be the integral of that area within the loaded area. EVAL may be also helpful
for a fast evaluation of different loads on a calculated influence line.
3 . . .
4 BEAM ... TYPE T EZA #zn PA #dTzn ...
5 EVAL TYPE TEQV
This load is saved in the database and can be used for the computation of the
beam reactions.
Hint
The determination of the equivalent linear temperature load is possible only
for the finite-element cross sections.
The temperature induced axial strain (thermal strain) of the beam cross section
at the position along the beam axis can be described by the following expres-
sion:
t (, y, z) = t (, y, z) T(, y, z) , (3.17)
Under the constrained conditions, the temperature induced strains will cause
corresponding axial constraint stresses to develop in the beam, i.e.:
From now on we restrict ourselves to the case where the temperature only varies
along the z-axis of the cross-section.
Axial force of the beam under the constrained conditions due to thermal strains
can now be determined as
Z Z
t
N () = t (, y, z) dA = E(, y, z) t (, z) dA
A A
Z
= [E(, y, z) t (, z) T(, z)] dA . (3.19)
A
z
T(z) Tcons = Teq Tne (z) = Tz,eq Tnon (z)
h
T(z1 )
T(z2 )
neutral axis
T(z ) h
z
T(zn )
Teq Tz,eq
where EA and T are the elastic axial stiffness and the coefficient of thermal
expansion of the gross cross-section of the beam.
By comparing the two expressions for axial force, Eq. 3.19 and Eq. 3.21, we
can finally derive the equivalent uniform temperature change along the x-axis of
the beam Teq ()
[E(, y, z) t (, y, z) T(, z)] dA
R
A
Neq () = N () t
Teq () = . (3.22)
EA() t ()
Again, by comparing the bending moments from Equations 3.20 and 3.23, we
can derive the equivalent temperature difference in local z-direction along the
x-axis Tz,eq ():
Hint
In order to list the determined equivalent linear temperature load in the
SOFiSTiK Report Browser, ECHO LOAD EXTR is required.
CTRL
With CTRL you may specify some control options for the analysis. A definition
for CTRL is evaluated sequentially within the input. The control values have to
be input therefore before the load cases.
Default: 0
DIST Distribution of loads for beam elements:
0 on single beam elements only
1 distributed between beam elements (AREA BGRP)
(explicit direction dx,dy,dz definable with V2,V3,V4)
2 distributed via influence areas only
+4 suppress torsional moments as much as possible
WIND Control pattern for Wind loads
1 Create wind loading even for static wind as wind velocities
(ASE/DYNA only)
Default: 0
SUML saves the sums of the generated nodal forces
PX, PY, PZ in CRI1, CRI2, CRI3 of the load case header (see LC)
the three consecutive values are factors for the PX, Py and PZ, while
the fourth value is an angle to rotate the resultants PX, PY (useful for
drag coefficients)
SUML fak1 fak2 fak3 alf genrates factorised and for 2D also rotated
integrals of the forces from WIND.
Default: 0
LAR Variation of LAR-support
> 1.0 rigid support
< 1.0 soft support
For example LAR 2.0 creates a stiffer elastic support for the load
distribution areas.
Default: 1.0
CFDL Selection of a load case of the CFD results
The selection of a load case of the CFD results is done independently
from the generated load cases.
The following options are intended only for internal purpose up to now.
COTB minimum Cotangent of angle between beam and load directions for
DIST 1
Default: *
With this record it is possible to save coordinates for a given point or node num-
ber in a variable. Due to technical reasons it is not possible to access the nodal
coordinates directly from CADINP. But defining COOR allows to save and use
these coordinates in arithmetic expresssions.
the variables #XYZ(1),#XYZ(2) and #XYZ(3) will contain the coordinates of node
5121, the variables #XYZ(4),#XYZ(5) and #XYZ(6) will contain the coordinates
of node 5122 and the variables #CEN(0),#CEN(1) and #CEN(2) will contain the
coordinates of node 5120. The variable #XYZ is finally saved to the data base
permanently.
ECHO
4 Dynamic Loads
In all cases you need a loading, in many cases generated by some unit acceler-
ations (ACCE).
A spectrum defines the response for a single degree of freedom system depend-
ing on the eigenfrequency period and may be used for systems with multiple
degrees of freedom with statistical algorithms.
For a dynamic analysis one or more load cases will be combined via time func-
tions to a complete loading, which is then subdivided into discrete time steps.
The tasks to do are:
The last task is much more effective for linear dynamics (DYNA) within the time
stepping algorithm, but for more general cases, like nonlinear dynamics with non
conservative loading it will become necessary to save all the loading within the
database for ASE with the command STEP.
Hint
The options RESP, FUNC and STEP are only available with a special li-
cense for dynamic effects.
cnod
S
M
Sp
P
Sdp Sd
M Vb
cnod
Vb
cnod
Vb
where (t), (t) and (t) are the relative displacement, relative velocity
and relative acceleration vectors, respectively, while M and C are mass
and damping matrices of the structure. s () denotes the nonlinear in-
ternal resistance force of the structure. Right hand side represents the
effective earthquake forces, where is the unit directional vector and
g (t) is the ground acceleration.
ized modal mass and damping. This is general true only if the assumed
displacement shape corresponds to one of the natural modes, but for
convenience sake the same terminology will be used herein regardless
of the chosen displacement shape. s = T s and m = T M are
the nonlinear resisting force and mass of the equivalent SDOF system.
Introducing a new reference SDOF displacement D(t) as follows
m |D(t)| = Sd (T , ) , (4.10a)
m |A(D(t))| = Sp (T , ) ,
(4.10b)
Now we can transform the Vb cnod pushover curve of the MDOF sys-
tem to the Sp Sd capacity diagram of the equivalent SDOF system
(Fig. 4.3).
S = Vb / (2 m) D(t)
Vb
m
c
s (D)
Figure 4.3: Conversion of the pushover curve to capacity diagram (A-D format)
Considering the Eqs. 4.2, 4.5 and 4.10a the absolute maximal displace-
ment of the control node of the MDOF system cnod can be related to
2 Where there is no possibility for confusion, the notation S will also be used to denote the
pseudo-acceleration spectral response Sp .
3 As further noted by R EINHORN [36], for a SDOF system with bi-linear resisting force -
deformation characteristics, the envelope of the force maxima and associated maximal dis-
placements will exactly follow the bi-linear relationship.
p=M , (4.14)
From statics it follows that the internal forces s are equal to the applied
external loads p, i.e.
s = p . (4.16)
Taking the Eqs. 4.14, 4.15 and 4.16 into consideration, the maximal
nonlinear resisting force of the equivalent SDOF system s can be writ-
ten as
m Vb (cnod )
s (Sd ) = T s = T M = m = = . (4.17)
Equations 4.13 and 4.18 are used to convert the Vb cnod pushover
curve from the stage 4a to the SDOF system spectral acceleration
(c) Elastic response spectrum can also be transformed from the traditional
spectral acceleration S versus period T format to the spectral acceler-
ation S versus spectral displacement format Sd (a.k.a. A-D format or
ADRS format) to obtain the elastic demand diagram by utilizing the well
known relation
2
S T
Sd = = S . (4.19)
2 2
Figure 4.4 shows the conversion of the elastic response spectrum from
traditional to A-D format. In A-D format the lines radiating from the origin
have constant periods.
T = cons S T = cons
S
T Sd = S (T/ 2)2
Figure 4.4: Conversion of elastic response spectrum to A-D format (elastic de-
mand diagram)
S
El. Demand Diagram
Performance Point
Capacity Diagram
Sp
Demand Diagram
Sdp Sd
(cnod,p , Vb,p ) is performed with the help of the Eqs. 4.12 and 4.18, i.e.
s = m Sp = m Sp
Vb,p = s = 2 m Sp
Figure 4.6: Transformation of the seismic demand of the SDOF system to the
seismic demand of the MDOF system
Pushing the structure until reaching the target displacement level of the
control node cnod,p is performed with ASE analog to the stage 3. If the
pushover analysis in the stage 3 is performed with the reasonably small
load increments then the user could take one of the two load cases in be-
tween which the control node displacement level cnod,p is located as the
final performance (demand) load case.
Finally the global structural performance can be assessed by performing
checks that the structural and nonstructural components are not damaged
beyond the acceptable limits of the performance objective for the level of
forces and deformations corresponding to the displacement demand cnod,p
(ATC-40 [1]).
SA Rigid acceleration (T = 0) *
SB Constant acceleration *
S 0 for elastic Spectra
S 0 / q for design spectra
SMIN Minimum acceleration threshold *
TB Time value sec *
TC Time value sec *
TD Time value sec *
TE Cut-Off Time value sec *
K1 Exponent TC < T < TD *
K2 Exponent T > TD *
For the complete loading definition you need the direction of the acceleration
specified with the record ACCE. Please note that the spectra may be defined
in absolute accelerations or as a fraction of the gravity acceleration g or a base
acceleration g . The second approach is more straight, as we have the theoret-
ical value of 1.0 for T = 0 (perfect rigid structure). Thus this approach is chosen
for all spectra beside the UBC and the Chinese and Japanese spectra. It might
happen that SA is less than 1.0 for some design codes due to soft soils.
In general you are using only one spectra, but it is possible to define multiple
spectras with different modal damping ratios. The response is then interpolated
between the adjacent curves for any eigenmode.
For those design codes using different spectra for vertical and horizontal re-
sponse (Eurocode), two factors AH and AV are provided. However only one of
these factors should be defined, but a definition of AH 0.0 will preset the value
AV to the default of the design code.
All values will be preset according to the selected type and Parameter CLAS,
but may be changed as desired. Thus the total spectra has the following shape:
T
0 < T < TB : S = SA + (SB SA ) (4.21)
TB
TB < T < TC : S = SB (4.22)
k 1
TC
TC < T < TD : S = SB Smn (4.23)
T
k 1 k 2
TC TD
TD < T < TE : S = SB Smn (4.24)
TD T
TE < T : S=0 (4.25)
If the value TD = 0, the parameter k2 is not used as above, but for the first
segment as follows (e.g. JRA):
k 2
T
0 < T < TB : S = m SA , SB (4.26)
TB
The values of the spectra depend also from the damping or the behaviour fac-
tor q. The plateau of the spectra is modified in general with one of the following
factors on the modal damping or behaviour factor:
With damping :
v
u 1.0
= (4.27)
t
0.55
0.5 + 10
If no definitions are made for MOD, the modal damping of the eigenforms will
be used to factorize the response with the factor of formula 4.27. If values
are specified it is possible to interpolate the response between various spectra
depening on the specified damping.
Hint
The following remarks do not allow to skip the study of the design codes for
earthquake. Some remarks below will necessarily make no sense if one
has not read the corresponding paragraphs of the design code. Further
it has to be stated, that we can not claim that our readings of the design
codes are always complete or correct.
4.2.1 Eurocode EC 8
While the original version had only three different types of spectras, still available
with TYPE EC-0, the manifold of the later versions requires now more parame-
ters do be defined. For TYPE one may select between EC-1 (Type 1) or EC-2
(Type 2, for M < 5.5) and for CLAS the soil classes A to E accounting for the
following soils:
Soil class A
Rock or other stiff formations with shear wave velocities above 800 m/sec
with at most 5 m soft strata on top as well as stiff soils of several ten meters
with an increase of soil values with depth reaching a shear wave velocity of
400 m/sec in a depth of 10 m.
Soil class B
Stiff deposits with mean shear wave velocities above 360 m/sec (former 200
m/sec in 10 m depth and above 350 m/sec in 50 m depth).
Soil class C
Medium dense or medium stiff soils with shear wave velocities above 180
m/sec (former below 200 m/sec in the uppermost 20 m)
Soil class D (since 2001, former C)
Loose cohesionless soil deposits or deposits with predominant soft-to-
medium stiff cohesive soils with shear wave velocities below 180 m/sec.
Soil class E (since 2001)
Soil made up of superficial alluvial layer (C and D) 5 to 20 m covering stiffer
deposits (A).
The acceleration g is ruled by the local site and has to be specified with the
record ACCE. An explicit definition of MOD>1.0 will automatically select the
design spectra. A direct or indirect definition of AV will switch to the vertical
spectra parameters.
The IBC defines in detailed maps the basic acceleration for a short period Ss
and at 1 sec S1 . From these and the soil class all parameters of the spectra are
defined according to equations 16-38 to 16.43. The user specifies this by the
soil class and a literal of the form s.ss/t.tt for the seismic zone, where s.ss and
t.tt are the values for Ss and S1 .
For the UBC the Zone-Factor is derived from table 16-I according to the seismic
zone value 1, 2A, 2B, 3 or 4. From that table 16-Q and 16-R yield the values
C and C. The near source factor of table 16-S and 16-T as well as the mod-
ifications for isolated systems in zone 4 have to be specified with parameters
explicitly.
The acceleration you have to specify at ACCE is then for both cases required to
be given as g = 10.0.
Hint
Modification of the UBC/IBC spectra with a factor based on the modal
damping (Eq. 4.27) or the behaviour factor q (Eq. 4.28) is not supported.
The old DIN 4149 (TYPE RDIN) however has a rather simple spectra for the
seismic zones 1 to 4 with acceleration values of 0.25, 0.40, 0.65 und 1.0m/ sec2 .
Those values however have to be multiplied with a soil factor between 1.0 and
1.4 and thus should be explicitly given via ACCE.
An explicit definition of D> 1.0 will select the design spectra. The importance
factor r may be accounted for either by a modified SA-value or as safety factor
within the superposition.
Without a soil class the spectra of the old SIA for medium stiff soils is taken
where we have the value of TC = 0.5sec, which should be changed for stiff soils
to 0.33sec.
For the NORM B 4015 (TYPE OEN) the default is the spectra for medium stiff
soil. You have to specify the corresponding accelerations with ACCE.
All time values and spectral response values are then established based on
these values. If AH is specified as 0.0, the vertical spectra will be generated.
As soil classes CLAS we have (I=hard, II=medium and III=soft, without = speci-
fication according to old code from 1984).
In Fig. 2 elastic spectra for several soil classes are given and reduction factors
for damping ratios in Table 3, which may be selected by several RESP records.
They are the same for all seismic zones (ag ), Importance (I, Table 6: 1.5 for
important buildings, 1.0 for all other) and Response reduction (R, Table 7, values
between 1.5 and 5.0). The acceleration you have to specify at ACCE is then
given by:
g
Ah = g (4.29)
2R
S = cZ cD S0 (4.30)
1.5
cD = 0.5 + (4.31)
1 + 40d
According to Table 3.2.2. the basic accelerations are given according to the
seismic intensity 6, 7, 8 or 9 with two subclasses as factors of g as follows:
Intensity 6 7, 7a 8, 8a 9
a/g 0.05 0.10 0.15 0.20 0.30 0.40
m (frequently) 0.04 0.08 0.12 0.16 0.24 0.32
m (rarely) - 0.50 0.72 0.90 1.20 1.40
The spectra maximum value m according Table 5.1.4-1 follows the same
scheme. The spectra is referenced to the maximum value SB=2 m . The
shape of the spectra is given in picture 5.1.5 with the damping and the values
of TG=TC according to table 5.1.4.-2: (Characteristic natural period values (s))
The spectra defined here may be imported in WSPE or may be used for an ex-
plicit evaluation. The latter is done in DYNA by associating to a load case with a
wind spectrum individual load vectors to every eigen form with MODB in record
LC. The load values should be specified according to the coherence distribution
with a pressure value of q0 kp , the product of the mean pressure, the peak fac-
tor and the relevant turbulence intensity. The spectrum will be evaluated in that
way, that every frequency the background and resonance repsonse will be eval-
uated and combined with the SRSS method. We have to distinguish depending
on the numbers of spectra defined in the basic load case function:
If those items have not been defined, the spectrum will not be evaluated.
This deviation is not necessary in DYNA. With RESP EXMC the qk factors may
be defined directly with consecutive FUNC records where the number of the
mode has to be defined instead of the time value.
The scaling of the eigen forms has to be selected properly. If default (modal
masses = 1.0) has not been used, the definition of an appended character can
select the direction where the maximum component should be assumed to be
1.0.
Each load case may obtain free selectable time functions for dynamic response
analysis. A load function may be defined in different ways:
Hint
Please note, that the phase is now relative to the start time TMIN and is
defined as a time value and not in degrees or fractions of , allowing to use
the same CADINP-variable and unit for T and T1 to T3.
If the series are given with cosinus functions, the phases have to be reduced by
a quarter of the cycle time.
cos( t ) = sin + ( t ) = sin t 0.25 T (4.38)
2 2
If the user defines multiple functions for a load case, he should precede all the
functions with a record FUNC MULT or FUNC ADD to specify if the function
values should be multiplied or added. This headder allows also to specify the
unit of that function with a value at F with a unit sepcification, e.g. 1 [mm/ sec] .
If this factor s is defined within the range from 0.0 and +1.0 or as the literal
WALK, the four values and phases given by Seiler/Httner (Bauingenieur, 2004,
S. 483-496) are preset, but the coefficients (F1 etc.) may be specified explicitly.
Values between -1.0 to 0.0 selects the three coefficients and phases according
or (for values s < 1.5) according to Bachmann as pure half sine function:
|s| G sin t t < tc =
T
F(t) = t c 2 |s|
(4.41)
0 tc < t T
As these functions are only usable for a transient analysis it is possible to select
the first case with the Literals FRUN or FJMP also as Fourier series for a modal
analysis.
TM AX
TM AX
EXPO
(t) = F eF2 t eF3 t
Figure 4.9: EXPO,
TM AX
The time T defines the total duration, while the time values T1, T2 and T3 define
the duration of the three phases (Plateau, Lead-In, Lead-Out). The factors F2
and F3 define the shape of the lead-in and lead-out according to the above
formulas.
Load type ACCE defines a translational and rotational acceleration and the cen-
trifugal acceleration of a uniform rotation. This can be saved as nodal accelera-
tions or as element loads to all active element groups. The acceleration will act
on all masses defined in the database and will create nodal loads or loads on
beam, cables and truss elements. This feature can be used not only for vari-
ant earthquake loading and loads on moving structural parts, but also just for
creating all the loads from self weight.
If the basic reference value of the acceleration has been defined with RESP
already, ACCE is only needed to define the direction. This may be selected
with the literals DIR / DIRN / DIRC / DIRE instead of NODA / NODE / NODC /
ELEM. The defined values AX to AZ will be multiplied then with the horizontal
and vertical acceleration components defined with the last RESP before.
If an eccentricity or any definition for the reference point is specified for a trans-
lational acceleration, an additional torsional moment will be created by an addi-
An additional influence function LINF may be applied to account for special ef-
fects. Different accelerations for different footings are described either by in-
fluence functions, which are established by the deformations caused by a unit
displacement in the appropriate supports or the accleration is only applied to a
single node NO.
For a structure with three supports aimed to get different accelerations a defini-
tion may be as follows:
+PROG SOFILOAD
HEAD LC FOR Influence Lines
LC 101 TYPE NONE TITL ' ug1 =1 ' ; NODE NO 1 TYPE WZZ P1 $$
1.0 [ m]
LC 201 TYPE NONE TITL ' ug3 =1 ' ; NODE NO 3 TYPE WZZ P1 $$
1.0 [ m]
LC 301 TYPE NONE TITL ' ug5 =1 ' ; NODE NO 5 TYPE WZZ P1 $$
1.0 [ m]
END
+PROG ASE
HEAD COMPUTE iL 'S
LC 101 ,102 ,103
END
Once the influence vectors are know, we can use them to define the effective
forces by specifying the load case of the corresponding influence vector in the
LINF option-
+PROG SOFILOAD
HEAD p_eff ( t )
$$
LC 1100 TYPE NONE TITL ' p_eff_X_1 = -M * i1 * ag1 ( t ) '
ACCE TYPE NODA NO 0 AX 1 LINF 101
FUNC T F
. . .
LC 1200 TYPE NONE TITL ' p_eff_X_2 = -M * i3 * ag3 ( t ) '
ACCE TYPE NODA NO 0 AX 1 LINF 201
FUNC T F
. . .
LC 1300 TYPE NONE TITL ' p_eff_X_3 = -M * i5 * ag5 ( t ) '
ACCE TYPE NODA NO 0 AX 1 LINF 301
FUNC T F
. . .
$$
END
With ARED and the values AH and GH a reduction of the acceleration with the
depth may be defined for underground structures as given in the Indian design
code. The value ARED (e.g. 0.5) is the factor to be applied at a depth of AH, i.e.
where the coordinate of the gravity direction has this value. At the coordinate
GH is the surface and the factor becomes 1.0, between those two coordinates a
linear interpolation is used. Discrete loadings should be selected for that option.
Pushover Load
In order to perform the pushover analysis the pushover load must be defined
first. Pushover load case must contain additional information (e.g. participation
factor, modal mass, displacement shape vector, etc.) which needs to be saved in
mn n pn = mn n n = n
... ... ... ...
mk k pk = mk k k = k
... ... ... ...
m1 1 p1 = m1 1 1 = 1
the database. This additional data is later used in the pushover post-processing
stage where the pushover performance is determined (see PUSH). Therefore
pushover load is defined and the necessary additional information are saved in
database by specifying negative value for LINF.
The pushover static load should be able to represent the inertia forces that the
structure will be experiencing when subjected to earthquake ground motion as
accurately as possible. The load pattern is usually assumed to be proportional to
some assumed displacement shape vector . Most commonly, the chosen load
pattern is proportional to the fundamental eigenmode of the structure. However,
any other reasonable displacement shape can also be used (Figure 4.12).
For the displacement based pushover analysis (TYPE DISP), the load as the
prescribed displacements is directly taken from the specified displacement
shape vector (Figure 4.11d), that is
=. (4.43)
If the loads are in form of forces (TYPE NODE; force based pushover analysis),
the displacement shape vector is additionally weighted by the mass matrix M in
order to simulate the inertia forces (Figure 4.11c), i.e., the load pattern p is
p=M . (4.44)
Hint
The mass matrix M is based on the masses which are currently active,
i.e. which are specified before the current SOFiLOAD block. It is therefore
recommended to run one ASE/DYNA eigenvalue analysis with all the nec-
essary additional masses prior to the definition of the pushover loads, in
order to ensure that the correct mass matrix is taken into consideration.
the displacement shape vector for the definition of the pushover load pattern,
e.g. (Figure 4.12d)
For a general dynamic analysis all selected load cases and time functions within
an input block may be combined to generate the transient loading for all time
steps to be used then in a load case loop for ASE and DYNA. Possibilities are:
All the load cases for a nonlinear dynamic analysis are created and saved to the
database.
random phase values (based on the load case number) will be generated and
with the help of an intensity function will yield an accelerogram, adjusted with a
target damping D to the response spectra with an iterative process. The base
acceleration AG has to be selected to match the spectra. The default is 9.81
m/ sec2 . However the most common case is to switch off the scaling of the
accelerogram altogether. This can be achieved by specifying the negative value
for AG (e.g. SIMQ ... AG -1) (see sofiload.dat/english/simq.dat). If the
value AG is specified as 0.0, the function of the power spectra is created instead
of the accelerations.
Hint
It is strongly recommended, as a way of checking the validity of
the generated accelelogram, to always calculate a response spectrum
from a generated accelerogram and compare it with a target spectrum
(LSPE). This can be achieved with the help of the command REVA (see
sofiload.dat/english/simq.dat).
REVA allows the calculation of a response spectra for a given load or accelera-
tion function. This is done by the response analysis of a single mass oscillator
within a given frequency range and showing the maximum results depending on
the frequency or period.
The duration of the evaluation is determined by the highest time value of the
excitation value. A somewhat longer time range with exciting function 0.0 should
thus be defined in the case of high frequency excitation.
When TYPE FREQ is input, the values TMIN, TMAX and TDIF of the RESP
input are interpreted as frequencies too.
General workflow and theoretical background behind the pushover analysis are
described in Section 4.1.
The pushover curve is passed to SOFiLOAD by specifying the basis load case
LCC0, first load case LCC1 and the number of the load cases NLCC of the
capacity as well as the number of the control node CNOD. E.g. the input
LC 5001
PUSH TYPE VB - U LCC0 301 LCC1 2301 NLCC 25 CNOD 4
will define a pushover curve with the base-shear and the displacement of the
node 4 taken from the calculated load cases 2301 to 2325 (Fig. 4.13). The
displacement degree-of-freedom of the node 4 is taken from the basis capacity
load case LCC0 301, which is defined in the Stage 2 with the help of the ACCE.
The basis load case LCC0 contains necessary information needed for the deter-
mination of the performance of the structure (participation factor, modal mass,
assumed displacement shape vector, etc.).
Vb [kN]
80.0
Capacity
60.0
40.0
20.0
0.0
u-cnod [mm]
0.000
50.000
100.000
150.000
200.000
250.000
300.000
350.000
400.000
450.000
Equations 4.45a-4.45b are used to convert the Vb cnod pushover curve from
the Stage 4a of the Subsection 4.1 to the SDOF system spectral acceleration
Sp - spectral displacement Sd coordinate system to obtain the capacity diagram.
cnod
Sd (T , ) = , (4.45a)
cnod
s (Sd ) Vb (cnod ) Vb (cnod )
Sp (T , ) =
= = . (4.45b)
m m 2 m
For example, the input
LC 5002
PUSH TYPE A - D LCC0 301 LCC1 2301 NLCC 22 CNOD 4 LCDM 11
will convert the pushover curve defined by the LCC0, LCC1, NLCC and CNOD
into A-D format (Fig. 4.14). Other analysis types TYPE (ATC or EC8) of the
PUSH command will perform this conversion as well.
Sa [m/sec2]
Tb = 0.2 Tc = 0.5
T = 1.0
10.00
Capacity T = 1.5
5.00
Td = 2.0
EC8-elastic
T = 3.0
T = 4.0
0.00
Sd [mm]
0.000
50.000
100.000
150.000
200.000
250.000
300.000
350.000
Figure 4.14: A-D Diagram
The elastic demand response spectrum in traditional format can be defined us-
ing the RESP command, e.g.
LC 11
RESP TYPE EC -1 CLAS B AG 4.0 TITL 'EC8 -5%- elastic '
ACCE TYPE DIR AX 1.0
Passing the load case of the elastic demand response spectrum to the demand
load case LCDM of the PUSH command and selecting one of the adequate
analysis types (A-D, ATC, EC8) will convert this spectrum to A-D format, e.g.
LC 5002
PUSH ... LCDM 11
In this section the underlying principle behind the ATC-40 procedure for formu-
lating and solving the equivalent inelastic SDOF system (Eq. 4.9) and deter-
mining the inelastic from the elastic seismic demand is described. This method
is also know as the capacity spectrum method (ATC-40 [1], F REEMAN ET AL .
[22], F REEMAN [21]) 4 .
The method is based on the elastic highly damped demand spectrum and an
elastic (linear) SDOF system with equivalent (herein effective) damping (e )
and period (Te ). These equivalent SDOF system properties are obtained from
the properties of the original MDOF system, whose nonlinear behavior is de-
scribed by the pushover curve (Fig. 4.15).
cnod
Vb S = Vb / (2 m) D(t)
e
e
Figure 4.15: Idealization of the MDOF system with the equivalent inelastic SDOF
system
4 ATC-40 [1] SOFiSTiK notation: 0 0 , e e , ESo ES
The starting point is the modeling of the equivalent INELASTIC SDOF system,
given by the Eqs. 4.6 and 4.9, with the equivalent ELASTIC (linear) SDOF
system, i.e.
The solution of Eq. 4.47 can be obtained from the elastic highly damped re-
sponse spectrum which represents the maximal response of the elastic SDOF
system with period of vibration Te and viscous damping e
where Sde (Te , e ) is the elastic spectral relative displacement response and
Se (Te , e ) is the elastic pseudo-acceleration spectral response.
The values Sdp and Sp are the coordinates of the Performance Point PP in the
A D coordinate system.
Hint
The performance point represents the solution of the Eq. 4.47 and the main
outcome of the analysis described herein. It defines the (probable) internal
state (internal forces, displacements, rotations, interstory drifts, etc.) of the
structural system under an earthquake demand. The performance point
can be described in different coordinate systems:
In order to determine the performance point PP, the effective damping e and
the effective period Te of the equivalent elastic SDOF system need to be related
Recalling that for the elastic SDOF systems, the following relation holds
The total damping of the inelastic SDOF system is comprised of the viscous
damping inherent in the structure str (PUSH ... DSTR) and the damping
which is proportional to the energy dissipation as a result of the inelastic force-
displacement hysteretic behavior s (D(t)). In order to linearize the equation of
motion of the inelastic SDOF system this hysteretic damping needs to be related
to the equivalent viscous damping of the linear system 0 . Hence for the total
effective damping of the linear SDOF system we can write e
e = str + 0 , (4.51)
Common way for determining the equivalent viscous damping of the linear sys-
tem 0 from the hysteretic damping is to equate the energy dissipated in one
vibration cycle of the inelastic system to that of the equivalent linear system.
Hence, 0 can be calculated as (C HOPRA [5])
1 ED
0 = , (4.52)
4 ES
where ED is the energy dissipated by damping of the inelastic SDOF system and
ES is the maximum strain energy of the system.
The hysteretic energy ED can be determined from the capacity diagram (Fig.
4.16). First the bi-linear representation of the capacity diagram at the perfor-
mance point PP can be established by equating the area underneath the capac-
ity curve Ec (Fig. 4.16a) and the area underneath the bi-linear representation of
the capacity curve Eb (Fig. 4.16b), i.e.
Z Sdp
Eb = Ec = S (Sd ) dSd . (4.53)
0
S S
2e
PP PP
Sp Sp
PY
Sy
Ec Eb
ES
Sdy Sdp Sd
ED
Figure 4.16: Derivation of the effective viscous damping e of the elastic SDOF
system due to hysteretic energy dissipation of the inelastic SDOF system
The initial branch of the bi-linear representation is taken in the direction of the
maximal tangent to capacity diagram at point (0, 0).
ED = 4 2EC Sdp Sp .
(4.54)
ES is the maximum strain energy of the system at the displacement Sdp and with
Table 4.12: Values for damping modification factor, (ATC-40 [1], Table 8-1)
SBT 0 [%]
16.25 1.00
A
> 16.25 1.130 0.510 (0 / 2)
25.00 0.67
B
> 25.00 0.845 0.446 (0 / 2)
C Any value 0.33
Once the values of the ED and ES are know, we can determine the 0 and e
from the Eqs. 4.52 and 4.51.
The damping modification factor is measure of the extent to which the actual
hysteretic behavior of the structure can be represented by the parallelogram of
Fig. 4.16c. It is intended to take into an account the cyclic degradation effects
such are the stiffness and strength degradation and the pinching effects. It de-
pends on the hysteretic behavior of the structure characterized by three types
(Table 4.12):
For more about the structural behavior types reader is advised to consult the
ATC-40 [1].
With the properties Te and e of the equivalent linear SDOF system know,
the solution of the Eqs. 4.48a and 4.48b can be obtained from the elastic highly
damped response spectrum, which is described next.
Spectral reduction factor SR(T, e , SBT) for different ranges of the response
spectrum is defined by
v
u SR
k1
SR (e , SBT) for T Tc0 = Tc
t
SR(T, e , SBT) = SR , (4.57)
SR (e , SBT) for T Tc0
Se (T) Se TC TC0
Se = SB k1
SB TC
SB Elastic 5% response spectrum
Se = SB
Se = S0B T
S0B = SR SB S0B
k1
TC0
Reduced response spectrum
Se = S0B
T
TC TC0 T Sde
The spectral reduction factors can be estimated from the effective viscous damp-
ing e using relationships developed by Newmark and Hall (N EWMARK AND
H ALL [34])
3.21 0.68 ln (e )
SR SR,mn , (4.58a)
2.12
2.31 0.41 ln (e )
SR SR,mn . (4.58b)
1.65
Minimum allowable values of the spectral reduction factors, SR,mn and SR,mn ,
depend on the structural behavior type and are given in the Table 4.13.
Table 4.13: Minimum allowable SR and SR values (ATC-40 [1], Table 8-2)
Intersection between the capacity diagram and the demand diagram represents
the performance point (4.18).
S
El. Demand Diagram
Performance Point
Capacity Diagram
Sp
Demand Diagram
Sdp Sd
The workflow for the determination of the performance point can be summarized
as follows:
The following input will determine the performance point according to the ATC-
40 procedure (TYPE ATC) of the structure with the structural behavior type B
(OPT SBTB) and the inherent damping str = 3.5% (DSTR 3.5%):
LC 5003
PUSH TYPE ATC OPT SBTB LCC0 301 LCC1 2301 NLCC 25 $$
CNOD 4 DSTR 3.5 [%] LCDM 21
The pushover curve for the control node 4 (CNOD 4) previously obtained by in-
cremental pushover analysis with the basis load case 301 (LCC0 301) and the
results saved in the load cases 2301 to 2325 (LCC1 2301 NLCC 25) is trans-
formed to the capacity diagram. The elastic 5% damped response spectrum,
previously defined with the help of the RESP command in the load case 21, is
transformed to the elastic demand spectrum (LCDM 21). The outcome of the
analysis is illustrated in the Fig. 4.19.
Sa [m/sec2]
Tb = 0.1 T = 0.5 Tc = 0.6 T = 1.0
Ty Tp
10.00
T = 1.5
Capacity
PP
5.00 PY T = 2.0
UBC-elastic
Td = 3.0
Demand,
T = 4.0 -eff = 16.56%
0.00
Sd [mm]
0.000
100.000
200.000
300.000
400.000
In this section the underlying principle behind the Eurocode 8 procedure for
formulating and solving the equivalent inelastic SDOF system (Eq. 4.9) and de-
termining the inelastic from the elastic seismic demand is described (EN1998-
1:2004 [13], FAJFAR [16], C HOPRA AND G OEL [6, 7]) 5 .
cnod
Vb S = Vb / (2 m) D(t)
c
s (D)
Figure 4.20: Idealization of the MDOF system with the equivalent inelastic SDOF
system
The principle idea behind the method is the solution of the equivalent inelastic
SDOF system with the help of the inelastic demand spectrum. The equivalent
SDOF system represents the idealization of the MDOF system, whose nonlinear
behavior under earthquake is characterized by the pushover curve obtained in
the incremental nonlinear static analysis (Fig. 4.20), as described in Section 4.1.
Mass m and damping c of the equivalent SDOF system are obtained from the
properties of the MDOF system (Section 4.1, Stage 4b), whereas the nonlinear
(inelastic) resisting force s (D(t))
The solution of Eq. 4.60 can be found with the help of the inelastic (design)
response spectrum representing the maximal response of the inelastic SDOF
system with elastic period of vibration T = 2/ , viscous damping = 5%
and nonlinear resisting force s as follows
where:
Hint
The performance point represents the solution of the Eq. 4.60 and the main
outcome of the analysis described herein. It can be described in different
coordinate systems:
(Hint continued...)
Formulas governing the transformation between these coordinate systems
are described in Section 4.1, Stage 4 and 5 of the pushover workflow.
In order to determine the performance point PP, the period T and the nonlinear
resisting force s of the equivalent elastic SDOF system need to be related to
the performance point coordinates Sdp and Sp .
As shown in Section 4.1, Stage 4b, the time-dependent nonlinear resisting force
- displacement behavior, s (D(t)), of the SDOF system can be characterized by
the time-independent monotonic maximal nonlinear force - maximal deformation
relationship s (Sd ) of the SDOF system (capacity diagram, Fig. 4.21a) used in
the response spectrum solution (Eq. 4.11).
The most common approach to solve the nonlinear Eq. 4.60 is to idealize the
maximal nonlinear resisting force - maximal displacement relationship s (Sd )
(capacity diagram) by a bi-linear model with the initial stiffness, k = 2 and a
yield strength limit sy . The bi-linear idealization of the capacity diagram accord-
ing to EN1998-1:2004 [13] is an elastic-perfectly plastic function (Fig. 4.21b).
The influence of moderate hardening is incorporated in the demand spectra (FA -
JFAR [17]).
s
S
m k = 2
sy PP PY PP
Sp
m Sy
E
c
E
m
the displacement of the idealized equivalent SDOF system Sdy (and the yield
The determination of the inelastic spectral response of the SDOF system with
the bi-linear force deformation relationship (PP (Sdp , Sp )) from the spectral re-
sponse of the corresponding linear elastic SDOF system (PE (Sde , Se )) is based
on the well know concept involving two additional parameters - the displacement
ductility factor, , and the (yield) strength reduction factor due to ductility, Ry (Fig.
4.22).
S T = Ty
se PE
Se =
m
sy PY PP
Sy = Sp =
m
The ductility factor is defined as the ratio of the maximal displacement of the
inelastic SDOF system Sdd = Sdp to its yield displacement Sdy
Sdd (T ) Sdp
= = . (4.66)
Sdy (T ) Sdy
The yield strength reduction factor (i.e. the reduction in strength demand due to
nonlinear hysteretic force-deformation behavior) Ry is defined as the ratio of the
6
elastic strength demand se to the inelastic strength demand sy
se Se (T ) Sde (T )
Ry = = = , (4.67)
sy Sy (T ) Sdy (T )
where Sde (T ) and Se (T ) represent the elastic spectral displacement and elas-
tic spectral acceleration responses of the equivalent SDOF system (Eq. 4.60)
with the period T and damping = 5%, respectively.
The strength reduction factor Ry and the displacement ductility are dependent
on each other. Several proposal have been made for the definition of the Ry
dependency. A comprehensive overview can be found in M IRANDA AND B ERT-
ERO [32]. In Eurocode 8 the following relationship is used
T
( 1)
+1 for T < TC
Ry = TC , (4.68)
for T TC
where TC represents the period which marks the transition between the con-
stant acceleration range (T TC ) and the constant velocity and constant dis-
placement range of spectrum (T TC ). Eq. 4.68 defines a bi-linear Ry T
spectrum (Fig. 4.25)7 .
Inverting the Eq. 4.68, the ductility demand can be expressed in terms of Ry
and T
TC
(Ry 1)
+1 for T < TC
= T . (4.69)
R
y for T TC
Substituting Eqs. 4.67 and 4.66 into Eqs. 4.62b and 4.62a, we obtain:
Sde (T )
Sdp = Sdd (T ) = Sdy (T ) =
, (4.70a)
Ry
Se (T )
Sp = Sd (T ) = . (4.70b)
Ry
The Eqs. 4.70a - 4.70b enable the determination of the inelastic spectral re-
sponse of the equivalent SDOF system (performance point, PP (Sdp , Sp )) from
the elastic response of the corresponding elastic system (PE (Sde , Se )). This
procedure is illustrated in Fig. 4.23.
6 Forinelastic SDOF system with elastic-ideal plastic resisting force-displacement relation-
(T ) represents also the ultimate strength.
ship the yield force sy
7 Note that for = 1 the following holds: = .
se sy
S T = Ty S
Tc Tc
Se T = Ty
PE
PE
Se
PY PP =1
Sp
=1
PY PP
Sp
>1 Sy
>1
(a) Short period range, T < TC (b) Medium and long range, T > TC
Figure 4.23: Determination of the performance point PP for the equivalent SDOF
system
The workflow for the determination of the performance point can be summarized
as follows:
(a) If NO Take the point PP as new trial performance point, i.e. PPt =
PP and return to step 1.
(b) If YES Analysis is finished and the performance point is
PP (Sdp , Sp ).
The following input will determine the performance point according to the Eu-
rocode 8 procedure (TYPE EC8):
LC 5004
PUSH TYPE EC8 LCC0 301 LCC1 2301 NLCC 22 CNOD 4 LCDM 11
The pushover curve for the control node 4 (CNOD 4) previously obtained by in-
cremental pushover analysis with the basis load case 301 (LCC0 301) and the
results saved in the load cases 2301 to 2325 (LCC1 2301 NLCC 25) is trans-
formed to the capacity diagram. The elastic 5% damped response spectrum,
previously defined with the help of the RESP command in the load case 11, is
transformed to the inelastic demand spectrum (LCDM 11). The outcome of the
analysis is illustrated in the Figures 4.24 and 4.25.
Sa [m/sec2]
Tb = 0.2 Tc = 0.5
T = 1.0
Ty
Tp
10.00
Capacity T = 1.5
PY PP
5.00
Td = 2.0
EC8-elastic
Demand, = 1.44
T = 3.0
T = 4.0
0.00
Sd [mm]
0.000
50.000
100.000
150.000
200.000
250.000
300.000
350.000
Ry
6.00 = 6.0
= 5.0
4.00 = 4.0
= 3.0
2.00 = 2.0
== 1.5
1.44
0.0 Tc = 0.5
T [sec]
0.0
2.00
4.00
6.00
8.00
10.0
Figure 4.25: EC8: Ry T Spectrum
The following input will set the global structural performance limits (SPL1-SPL5)
as the cnod displacements (VB-U coordinate system). If the analysis is of the
type which works with the A-D coordinate system (e.g. PUSH TYPE ATC, EC8,
etc. ), then the performance levels specified as the cnod displacements will be
converted into the spectral displacements of the equivalent SDOF system Sd
(Fig. 4.26).
LC 5003
PUSH TYPE ATC ... SPL1 0.10 [ m] SPL2 0.18 [ m] SPL3 $$
0.25 [ m] $ $
SPL4 0.35 [ m] SPL5 0.45 [ m]
Sa [m/sec2]
Tb = 0.1 T = 0.5 Tc = 0.6 T = 1.0
Ty Tp
SPL 1 SPL 2 SPL 3 SPL4 SPL5
10.00
T = 1.5
Capacity
PP
5.00 PY T = 2.0
UBC-elastic
Td = 3.0
Demand,
T = 4.0 -eff = 16.56%
0.00
Sd [mm]
0.000
100.000
200.000
300.000
400.000
Figure 4.26: Structural performance limits
5 Train Loading
5.1 General
Train loads for bridges are ruled by the fact, that the most unfavourable position
of the loading is different for every single element and reaction and not known in
advance.
The base of the moving load process is a lane geometry, described in the plan
view by straight, circular or clothoid segments and in the elevation as straight
or quadratic parabula. This can be taken from the database as defined by
SOFiMSHB or explicitly input with the record GAX. Each axis may have up to
nine separate lanes with the sub numbers 1 to 9 defined via LANE. For the
dynamic impact coefficients an effective length may be specified and the extra
width of the traffic area may be defined.
Each lane has two coordinate systems. There is a local system (x) at the lane
axis for real distances. However, the inputs for the positions along the lanes
are entered in a global system of stations (s) which defines an alignment of the
lanes to each other.
There are three principal approaches for the problem of finding the most un-
favourable load position:
One can generate numerous load cases with the train load at distinct po-
sitions and search for the maximum with the superposition tool MAXIMA.
For some load definitions this approach is not possible with acceptable effort
however.
More general one can establish the influence lines for the forces and mo-
ments of all or selected locations within the structure. In a second step
these influence lines may be evaluated with the load trains. The result are
direct extreme values of all forces and moments. This is performed with the
program module ELLA, highly optimized for this task.
Last not least a transient analysis of the load coursing the structure with
the program DYNA is possible. For the animation of this process the record
TREX is very helpful.
Depending on the system and the loading, the one or the other method will be
better. Special effects like a load which is not bound to the lane in transverse
direction (EC) or having independent wheels (DIN) may increase the number of
needed load cases considerably.
With this commands no loading will be applied to the structure yet. The load
definitions are saved under a load case number which should not be used oth-
erwise. It is the SOFiLOAD / COPY command that will transform the train to
individual loading. With a reference to a geometric line (GAX) and an associ-
ated lane (LANE) the following transformations will take place:
Hint
These functionalities require a license of ELLA or a special license TRAI.
Traffic area
type vertical loads horizontal loads
model LM1(TS) LM1(UDL) LM4 braking centrifugal
gr0 Charact.
grU Charact.
gr1 Charact. Charact. (*) (*)
gr2 frequent frequent Charact. Charact.
gr2n frequent frequent non non
frequent frequent
gr2f permanent permanent Frequent Frequent
gr3 Charact. on
sidewalks
Traffic area
type vertical loads horizontal loads
model LM1(TS) LM1(UDL) LM4 braking centrifugal
gr4 Charact.
UDL on
total area
gr5 LM 3 LM 1
charact. in frequent on
main lane other lanes
gr6 0.5 0.5 0.5 0.5
Charact. Charact. Charact. Charact.
The selection of a group will select individual factors for the components from a
complete load train definition. gr6 is used for the exchange of supports according
to DIN FB. For all combinations with other than the characteristic values the PSI-
factors of EC1 are used. Any deviation of this has to be build up with the special
groups and an explicit factor FACT.
Appendix C of DIN FB 101 states also for road bridges ("if not specified other-
wise"):
LM2 and the single loads on pathways should not combined with any other
life load
Neither snow nor wind should be combined with braking or load group gr2 or
gr3.
Snow or wind actions larger than o *FWk should not be combined with gr1 or
LM1.
Wind and temperature should not be applied together.
The life load groups for railway bridges 11 to 31 according to table 6.6. of DIN
FB 101 should be best evaluated with ELLA or MAXIMA and not with combined
explicit loading. For those bridges, wind and life load are bound together, thus
should act only at the position where the train is, but only if the wind load does
not exceed a certain threshold.
NX Direction vector *
NY *
NZ *
A general geometric axis with all details may be now defined in SOFIMSHC. For
SOFiLOAD / ELLA / TENDON only a simplified definition is provided as follows.
Definition with a length resp. station in the plan view For the first record of
an axis the start point (X,Y,Z) and the start direction (NX,NY,NZ), the length
S of the first segment and optional curvature and clothoidal parameter is
specified. All consecutive records contain only the next S-value and the
curvature parameters.
If a radius is defined, a transition element from the last radius to the current
value is generated. Positive values for R cause a curvature to the right-hand
side, whilst negative values a curvature to the left-hand side. If A is defined,
a clothoidal spiral transition curve is created where the curvature increases
for the positive values of A and decreases for the negative values. If the
The options to define the elevation or cross falls are now only available in
SOFiMSHC.
The total loading area will be subdivided in up to 99 individual traffic lanes rela-
tive to a given geometrical axis. These may be created automatically by a pre-
defined standard section or with explicit coordinates. One may subdivide each
segment with different widths and dynamic impact factors. All lanes have to be
defined together to an existing axis, any new definition will delete all previously
defined lane definitions.
The width of the lane is defined through the left and the right boundaries. The
lane can be widened or narrowed by different input data at different stations.
If the lane edges happen to intersect the lane, this should be defined only at
distinct points to allow for correct treating of torsional loading.
The width of the load train may be less than those of the lane. In that case
additional basic areas are established loaded by a constant load specified with
the load train. If the load train is larger than the lane width, reductions of the
applied loading are possible.
The lane 0 has to be defined always, for the following procedures two cases
have to be distinguished:
There is only lane 0, the width of the moving loading is defined only by the
load train.
There are other lanes within the curb stone limits. Then lane 0 defines the
total extend of the traffic load including pathways. The width of the moving
load is the maximum extend of the other lanes.
AXIS.1
Y 4.00 2.00
T 0.00
101 2.00 4.00 m
M 1 : 70
Default constant sections are available via literals as follows. If such type (with-
out blanc spaces) is given at the main lane, secondary lanes will be automati-
cally created:
For the following types the definition of the curbstone coordinates is always re-
quired, which is constant along the total lane.
If the lanes have all the same width, they will be aligned from the right (positive
y-values) starting with number 1. However if this is not the case, lane 1 is always
the central lane with the total traffic area, more lanes with numbers 2 to 9 will
be created aside. together with lane 1. Additional lanes will be created right
adjusted starting with number 10 and left adjusted with number 20. If those lanes
are identical to the primary lane definitions, the numbers are just synonyms. For
TMH7 lanes 11,12,13 resp. 19,18,17 with extreme eccentricity will be created.
AXIS.11
AXIS.10
Y 4.00
T 102
2.00 0.00
T 2.00
101 4.00 m
M 1 : 70
Figure 5.4: Two lanes adjusted to the right loaded and residual area
AXIS.20
AXIS.21
Y 4.00
T2.00
101 0.00
T 1022.00 4.00 m
M 1 : 70
Figure 5.5: Two lanes adjusted to the left loaded and residual area
Residual areas are the areas between the edges defined by the width of the
load train and the edges of the lane itself. The pathways are thus only included
in lane 0. Gaps between the lanes are NOT treated as residual loading areas.
For the loading of the lane in SOFiLOAD it will be subdivided in the longitudinal
direction into segments (e.g. each span). If several lane-definitions should be
combined to one single segment, the definition of L is only possible for the first of
the definitions, while specifying for all the others the literal CONT at this position.
For railway bridges there are detailed tables available within EC1 or DIN FB 101
how to select the governing length. Further there are detailed descriptions how
to calculate the effective pressures from the load which needs the input values
HEFF to ASL however which are definable in SOFiLOAD only.
+ INC
s
BEFF HEFF HS
INCD INCD y
YL z YR
Figure 5.6: Ballast and sleepers
The description of all available load trains can be found within the next pages.
If a value for the convoy distance is given (XCON), the specified train will be
applied multiple times with that given minimum distance between the last load
ordinate and the reference point of the consecutive loadtrain.
The the residual area loading P5 is applied without dynamic impact factors and
without centrifugal forces. It is applied only for:
Areas between the constant width of the load train and the polygonal
bounds of the lane. If the load train has no width (WIDT 0) there wont
be a residual area either (Railways)
Areas between the borders of lane 0 and all other lanes (e.g. pathways)
The total lane area for the load group GR4 (e.g. pedestrian bridges)
The wind loading is generally equal to P6 and acts horizontally upon a traffic
band with height P7. As there will be no traffic for strong winds, this is not the
maximum wind load on the structure itself. The sign of the wind load is defined
as positive if coming from the right in the moving direction, but option DIRT
allows a more specific definition. ELLA has the possibility in record POSL via
OPT to apply the wind load in the most unfavourable direction at its own, if DIRT
has allowed this. Both options are combined with a logical and-operation.
The load trains have a moving direction which is not only important for some of
the train loads but also for the direction of the braking load. Positive load values
are considered to be braking loads in traveling direction, negative load values
are accelerating loads in reverse direction. If DIR N is specified, no impact
factor will be applied and the brake and velocity and wind load will be preset to
zero.
The meaning of value P8 is different for each loading type. The sign of the
braking load will be taken from the moving direction. A changing sign (DIR B)
will be only possible for ELLA to take care of. ELLA and SOFILOAD allow to
change the direction or deactivate the loading.
HA HA according BS 5400
HB HB according BS 5400
All load trains may be extended with TRPL and TRBL definitions. If none of
the standard load elements of the rain should be used, but other properties like
impact factors should be retained, the literal USER may be defined for P1. The
user should take care of:
The default live load P5 should be deducted for the areas loaded by the
defined loading.
The distance to the last load of a standard train may be not as expected due
to automatically generated loads of those type and should be checked.
The Eurocode load model allows the loading to be moved across the lane within
some limits, each load will have therefore a range of possible eccentricities for
ELLA.
JRA Impact factor according to JRA are only distinct for T-Loading,
for L-loading there are deviations for standard concrete and
steel bridges.
cases.
LPHI should be defined for the axis via LANE. However ELLA may also use
the distance of the zero values of the influence line as a good approach to the
effective length. If no input for LPHI is given, the dynamic factor will be set equal
to the value with a minimum length and the width of the lane will be set equal to
0.0.
The forces calculated according to the laws of physics with vin [ m/sec] are:
2
P = P ; g = 9.80665 m/ sec2 (5.11)
Rg
For FUGA you may however specify an additional factor explicitly. Negative
factors will enforce the laws of physic to all type of load trains.
The double axle should be applied only in total. Thus all loads of the axles will
be set to be applied even if favourable.
Load Model 1
There is one double axle with a spacing of 1.2 m. For the different lane classes
it is generally recommended to use three different load trains with individual
adjustment factors q. These factors are specified in national annexes and are
defined in the INI-files. (e.g. DIN Fachbericht with a value of Q = 0.8, SIA with
a value of Q = 0.9). Other values may be specified with a direct load value if
needed.
The brake loading is calculated according to the length of the total lane and
distributed as uniform load along the line:
The upper limit is defined by the requests of the STANAG, it may be redefined
by a national annex or other means. This may be specified via a global variable
EN1991-2_QLMAX in the INI-file.
Load Model 2
This load model is a single axle taken from load model 1, but with a dynamic
impact factor and the wheels may act independently. As this load model is only
for local elements it should not be selected within ELLA, especially as it does
not work with influence areas (INT>2). A possible application is the accidential
load case of a vehicle on the pathway:
Load Model 3
This load model is for special cases of heavy load vehicles. We have to dis-
tinguish between the narrow version fitting within one lane (2 axles) and the
broader version for P2=240 (3 axles). For the latter case the loading of the
same load train in two synchronized lanes with special provisions of YEX should
be used. Parts of the load train not within the lane imits will be clipped automat-
ically.
The speed of the load train is a very important parameter, it does not only control
front and rear for some load trains, but it defines also if the load train is moving
slowly (v = 5 km/h) or with a regular speed (v = 70 km/h). This triggers if an
impact factor is applied or not.
As the coefficients 1 are different for UDL and TS, we use from this load case
the value 1 for TS, but for UDL and the residual loding the default value of 0.4
of the EN will be taken.
Load trains of the Special Types General Order (STGO) will be selected with
TYPE SV, where P1 defines the class (80, 100 or 196), P2 and P3 are not used,
alle other remarks especially about P4 remain valid:
Load trains of the Special Order (SO) will be selected with TYPE SOV:
Load Model 4
This is a pedestrian load model with a basic load area with a maximum value of
5.0kN/ m2 . For a loaded length greater 10 m the load value will be decreased:
120
q k = 2.0 + > 2.50 kN/ m2 (5.15)
L + 30
For the application of this load model the definition of the loadgroup is manda-
tory: GR3 or GR4 for the area loading and GR0 for the service vehicle.
P1 = 1 90 / 190 kN
P1 = 2 80 / 140 / 140 kN
P1 = 3 90 / 180 / 120 / 120 / 120 kN
P1 = 4 90 / 190 / 140 / 140 kN
P1 = 5 90 / 180 / 120 / 110 / 110 kN
This is a complete truck with two double axles P1 with a distance of 6.0 m
designed for the fatigue design.
P1 = 1 70 / 130 kN
P1 = 2 70 / 120 / 120 kN
P1 = 3 70 / 150 / 90 / 90 / 90 kN
P1 = 4 70 / 140 / 90 / 90 kN
P1 = 5 70 / 130 / 90 / 80 / 80 kN
Those classical load trains are used in several countries in Europe (DIN 1072,
OENORM B 4002, Spanische IAP and Brasilian NBR). National variants may
be selected with a country code. The width of the moving loading is 3.0 m
in general, for the OENORM it is 2.5 m and for the Spanish IAP a minimum
distance to the secondary truck suggests a width of 4.0 m. The rest of the traffic
band is loaded by P3, the remaining areas inside the lane are loaded with the
basic area loading P5. With DIR N one may select a secondary lane without any
dynamic factors.
The direct definition of a second load train beside with P2 und P4 can not be
supported for some of the recent features. It us strongly recommended to use
synchronized lanes instead, it is recommended to use two lanes with individual
All loads are divided to portions to the right and to the left of the lane axis, which
can act independently.
DIN 1072 defines a total brake loading with a maximum of 900 kN and a min-
imum of 30 % of the heavy load trains within the principal and secondary lane
or 25% of the total principal lane. As the brake loading is an other load class
than the standard life load it is not always possible to apply both loads within one
loadcase. IAP has a minimum of 140 kN and a maximum of 720 kN.
The value P1 specifies for H and HS the type of load train according to AASHTO.
The width of the train is 3.048 m. The following values are possible:
up to L = 50 m:
p = 36 L0.1 (5.17)
It is then possible that shorter loaded lengths could lead to higher forces. As
this can not be treated easily, ELLA uses an approximation by evaluating an ef-
fective length according to BD 37/01 figure 11. SBase lengths for highly cusped
influence linesT. In a first step the integral of the total positive and negative
contributions of the influence line will be evaluated, then the effective length is
caluclated:
(Area under IL)
Le = 2 (total length of IL) (5.18)
(value of maximum ordinate)
In Hong Kong (BS + Country code 852) the formulas are slightly different:
up to L = 70 m:
from L = 70 m:
The brake loading is also calculated according to the loaded length of the lane:
The loading NA (Bridge Design Code TMH7, South Africa 1981) is represented
by a uniform load P3 pu, with the magnitude depending on the length of the
p
loading and a concentrated load P1=144/ n kN (KEL). The value of P4 defines
the loaded length L as with the HA loading described above. P2 may be used
as with HA to generate a tandem loading.
up to L = 36 m:
p = 36 (5.22)
from L = 36 m:
The brake loading is also calculated according to the loaded length of the lane:
The Departmental Standard BD37/88 has other factors (Table 14). The default
value for P3 will be selected based on a nominal width bL of 3.048 m and the first
lane.
TMH7 applies the NB vehicle not combined with other life loads. Values P2 to
P4 will be ignored. The distance between the axis is 2.0 instead of 1.8 m.
Brake loading are % of the total load. If the train has a unique traveling direction it
is applied between the first and second axle. If the train travels in both directions
it is distributed in two separate blocks at both ends.
P8 = 0.25 (HB)
P8 = 0.20 (NB)
Hint
The basic area loading P5 is not deducted in the case of HA and HB load-
ing. It always acts upon the full width of the lane.
Figure 5.22: Load train HST (three axle truck, ed. 2002/2005)
The load train has a width of 3.048 m, the value of X can be between 4.267 and
9.144 m.
The traffic band load P3 has been specified in the 2002 edition as an alternate
loading, with the load model HL 98 of the 2005 edition it is now active on the full
longitudinal length.
18 m
0.25 m
(Typ.)
The value P1 defines the level of the load train (CL1, CL2, CL3) or with MV the
maintenace vehicle according 3.8.11.
The value P2 defines the class of the load train (default 625).
If the value P3 is defined ( 9.0, 8.0 or 7.0 for class A, B or C and D) a constant
lane load will be defined with reduced load values of the load train without any
dynamic allowance. For this loading a braking load P8 of min(700,180+0.1*L)
will be applied. So P8 should become zero for secondary lanes.
The height of the wind attack area P7 is 3.0[ m] , the zentrifugal force is acting
at P9=2.0[ m] aove the lane.
IRC AA - Heavy Loading for certain areas or highways This is a bogie of two
axles with a total weight of P2 (40t). There is only one lane loaded with this
train.
IRC AAT - Loading for certain areas or highways This is a tracked vehicle
with a total weight of P2 (70t). A convoy with a minimum distance of 90 m is
foreseen. There is only one lane loaded with this train.
IRC A - Loading for all permanent bridges This is a train with two trailers,
repeatable with a minimum distance of 18.5 m. The axle loading is P2 (27
kN), P3 (114 kN) and P4 (68 kN).
IRC B - Loading for timber bridges and temporary structures This is a train
with two trailers, repeatable with a minimum distance of 18.5 m. The axle
loading is P2 (16 kN), P3 (68 kN) and P4 (41 kN).
IRC nnR
All numbers refer to the hypothetical vehicles of appendix 1. An appended
R will select the wheeled trains, an appended S the four wheelers (only 3 to
24) and an appended T will select the tracked vehicle:
3, 5, 9, 12, 18, 24, 30, 40, 50, 60, 70
IRC PD for loading on footways is just a selectable type. The reduction
according to clause 209.4 dependant from width and length has to be done
by the user explicitly via parameter P5.
For the longitudinal effects of the loading the clause 208 establishes reduction
factor for multiple lanes. This effect should be taken into account during the
superposition of load cases.
The brake load with P8 (0.2 = 20 %) is defined as the fraction for the first load
train, while the other trains have only half of this value. P8 = 0.05 should be
applied in the case of more than two lanes to the other ones.
Load values P2 of JRAL are dependant on the length. In that case negative
values for P2 define factors to these basic values. Loads for pedestrian lanes
according to Tab. 2.2.4. have to be defined with type JRAL and P3=0.0.
AS_A 160 A single axle, including the special case of a single wheel W 80
for local effects.
and further a system with 12 axles and a variant length to be used with influence
lines.
If more than one lane is loaded, the second lane shall be loaded with a lane
factor of 0.8 all subsequent lanes with 0.4. For fatigue 70 percent of the A160 or
M1600 load without uniform load value P3 should be used.
The "heavy load platform" is given in AS 5100.7. It is a load with 16 axles with
200 kN each for the HLP 320 and 250 kN for the HLP 400. The have either a
uniform distance of 1.8 m or a variable distance between 6 and 15 m between
two groups of 8 axles each.
The Swedish load trains have the special feature of variant distances between
the loads which are best treated using influence lines. However the short dis-
tance of 1.5m will be fixed to that minimum value, as there are hardly cases to
be expected not yielding the most unfavourable value with that short distance.
Most train types have different load values for primary and secondary lanes. The
parameter P1 is used to specify an enumeration for the most important lane, the
secondary lane etc.
P1 Lane index 1 2 3
P2 Axle load [ kN] 250 170 0
P3 Line loading [ kN/m] 12 9 6
P4 explicit distance (minimum 6.0 m)
P5 area loading [ kN/m2 ] 4 3 2
The second train has a distance with minimum of 50 m, the individ-
ual loads with a minimum of 10 m
BROF Fatigue relevant load train of the Swedish BRO
The type UIC is considered for a train within a excellent maintained track. If
that is not the case, it is possible to select with type UICB a variant with impact
factors for the standard maintenance.
Loadings are defined with a possible eccentricity of 1/18 of the gauge according
to EC / DIN-Fachbericht, if not an explicit value is specified.
For a sleeper distance up to 0.8 m each load is converted to 3 single loads equal
to 0.25 PA, 0.50 PA and 0.25 PA at distances of P1 from each other. A value
greater 0.8 will yield a constant block load as follows:
Figure 5.29: Load train UIC = UIC 71 = RU (BS5400) - Constant Block Load
Aerodynamic loading due to trains passing and derailing loading are not avail-
able.
Hint
load trains SW will act also if their contributions have favourable effects.
Load values P2 to P3 are informative values only. These load trains will be ap-
plied as constant block load in general, but if you specify P4 = 0.0, all individual
axles (up to 96!) will be generated. The speed of the trains will default to the
values specified in the EC.
Defaults: P1 = 200 kN
P2 = 50 kN/m
P3 = 25 kN/m
Figure 5.33: Load train ASRT = Railway Loading 300LA according AS 5100
The load train 300LA of the AS 5100 consists of a locomotive and as many
vehicles as necessary, each of them with a variant length between 12 and 20 m.
Unfortunately even with influence line it is hardly possible to deal with an infinite
number of variables, thus the load train has always a finite number of vehicles.
For more than tow tracks, the loading in the third track is applied with a factor of
0.85, the fourth track with 0.70 and all other with 0.60.
For this load train different coefficients for dynamic allowances are specified, de-
pending on the type of the rail fixing. (Ballast or direct fixing). These information
is taken from the LANE definition.
MLC Load trains of the STANAG are given in the sixth edition in appendix A.
There are the classes P1 = 4, 8, 12, 16, 20, 24, 30 up to 150. For every class
we have available:
A2 A3 A4 A5
Figure 5.35: Freely defined load train
The centrifugal loading acts in the height hs, the constant horizontal force in the
height zw, thus creating torsional moments. If the load has a width B, this mo-
ment will be applied as a pair of forces on the lane surface, a torsional moment
along the lane axis will be generated otherwise.
PW hw
PFSv2/gR
hs
All load values will be treated as line loads in general. If the width of the load is
equal to the width of the train or option 16has been set, the load values will be
converted to a distributed load and applied on the current lane width. 12kN/m
distributed on 3m yield 4kN/m2, for a total lane width of 5m the resulting load
equals to 20kN/m. For standard load trains, the definition is taken from the code.
If the width B is smaller than the width, two line loads with the distance B will be
created. If only BW is defined, an area load is selected with a width BW less
than the width of the lane.
If only HW is specified a value for PW will be evaluated from the wind load given
with the load train wind definition.
Input values for multi-body-dynamics of line loads TRBL for record TREX will not
be used currently.
A load train may be used within DYNA as movable load (CONT). For the visu-
alisation with the Animator or for a multibody dynamic analysis it is possible to
create beam elements from any load train belonging to a selected special group
with separate nodes. All nodes may be along the global x-axis with the real dis-
tances of the loads or collapsed to the origin (0,0,0). In the latter case the load
elements will appear and disappear near the structure just before usage.
The properties of the bogie and the wheel are specified with a general model
for each axis based on the mass, the frequency and the modal damping as
specified with the TRAI record.
Body
Cb Db
Pbo Bogie
Cbo Dbo
Pwh Wheel
Cwh Dwh
(5.24c)
For the analysis only as loading a selection of those groups with a FAKS of 0.0
is recommended, to activate the group but without static properties. The section
may be defined as a contour of the train. For free defined load trains, any single
load may have its own section.
All TREX-definitions are treated together at the very end of the program run, old
definitions of those elements will be removed for the same specified load case.
For more complex cases the load train may be modelled with finite elements in
the classical way (beams, springs, dampers, masses). Then TREX needs not
to be used, but the train and all its loads should be specified with a user defined
TRAI and each single TRPL should have its contact node properly assigned.
6 Wind Loading
6.1 General
Wind is a randomly non deterministic dynamic loading. The flow of the air in-
duces a velocity pressure on the structure. Dynamic effects of natural wind are
mainly introduced by a variance of wind speed and thus wind pressure within
time and space.
The program SOFiLOAD allows to take into account and to simulate most of the
above effects. To use these features two extra licences are needed: SOFILOAD-
W for the static wind loading and SOFILOAD-WH for the dynamic wind loading
(especially WGEN) and NONL-DYN for the interaction analysis in DYNA.
As basic safety concept for the wind loaded structure it will be specified in the
design codes or especially for large projects in the submission that within a
given time (e.g. 50 or 100 years) the failure of the structure will be avoided
with a given safety factor. The analysis itself will be based on shorter interval
- in Europe: 10 minutes - which includes the maximum wind speed of the 50-
year-wind but is long enough to allow a considerable dynamic response for all
resonance frequencies. The wind speed within that interval may be described
as the sum of
a timely constant, but spatial variant basic mean wind speed (10-minute-
wind) and
a superimposed timely and spatial variant part of turbulence.
The treatment of dynamic wind effects is governed by the fact that turbulences
may be only described by statistical means: The real time-spatial wind speed is
within the statistical limits purely random. The usual analysis methods use prob-
abilistic analysis with power spectras (RUSCHEWEYH [38], DYRBYE AND H ANSEN
[10], R OSEMEIER [37], DAVENPORT [8]). As these methods do not use the time
but the energy content of the wind speeds, they yield clear and reliable basics for
the analysis. Several steps then provide the power spectra of the deformations
and forces within the structure. The probabilistic peak value will be the result
of an extremal analysis of the spectras. At the time being, most of wind loaded
structures will be analyzed via this approach. And all modern design codes for
wind use these methods to obtain wind pressures.
National and international Design codes nowadays however use strongly simpli-
fied methods (ECCS [11, 12]) [ 11, 12, 13] . The total map will be subdivided
with 3 or 4 wind zones with step-wise wind speeds. To facilitate the usage, sev-
eral wind parameters will be set up on the safe (unfavourable) side naturally. The
complex structure is reduced to a simple single one degree of freedom oscillator.
Even then working with wind loads is still difficult. Compared to the efforts, the
results will be unsatisfactory in numerous cases: The total dynamic effects will
be accounted for with a constant gust factor for the total structure which might be
rather faulty for individual elements. Structures with several sensible frequencies
(skeletons, towers with antennas, pedestrian and other types of bridges) are not
applicable for this simplified approach. The same holds for structures with tuned
damping elements and many more cases.
The complete spectral design - the so called stochastic analysis - is rather com-
plex and costly, it is thus applied only for very sensitive structures (cable stayed
bridges with large spans). On the other side the stochastic analysis is still un-
derestimating the ultimate load, because the spectral methods are purely linear
for the structure and especially for the wind loads and do not account for any
nonlinear effects. The linear relation between the angle of attack and the wind
force coefficients are seldom admissible. The stochastic analysis is further un-
precise for systems with close eigenfrequencies (e.g. tuned damper systems).
Further more it has only limited possibilities to account for interactivity (dynamic
response of the structure and its effect on the wind pressures or forces).
SOFiLOAD has been created to cope with more detailed and thus more eco-
nomic wind loading for the design of structures, overcoming the above limita-
tions. Two of the benefits of the new method to be stated are:
SOFiLOAD generates more precise wind profiles accounting for the environ-
ment of the structure - roughness, elevations - similar as but more precise
than it is foreseen partially in the most recent design codes like EC1.
DYNA evaluates more precise forces and moments via transient analysis,
accounting on one side for nonlinear effects like changes of the wind forces
when the cross section rotates and on the other side for interactive behaviour
like aerodynamic damping, potential flutter, galloping and torsional galloping
or discrete damping elements. The current version still uses stationary as-
The SOFiLOAD-user may create the wind profile - as the first method - by defin-
ing the appropriate atmospheric wind speed. To facilitate this we have provided
a a global wind map for the 10 min wind with a return period of 50 years. This
wind map has been established by us using older wind maps and meteorological
measurements. It allows a smooth interpolation of the atmospheric wind and is
therefore more elaborate than the rough subdivision in 3 or 4 wind zones of the
design codes.
The transformation of the atmospheric wind speed defined for a 50 year return
period to another time value - as it might needed for large bridges - has to be
performed by the user if needed. A rather good estimate is given by:
1 + 0.12 ln N
VN V50 (6.1)
1.47
The distribution of the wind speed over the height is depending on the terrain
roughness and topology. Within SOFiLOAD it is possible to define a distribution
of roughness (WROU), along the wind luv direction up to 200 km and geometric
simplified elements like a hill, edge or ridge. For the latter there are estimates
given in the literature, especially in Eurocode 1 part 4, and in the newest EDIN
1055-4, having been implemented in SOFILOAD.
The wind definition may be taken as a second choice based on a specific design
code. For special applications like large and sensitive structures, bridges and
towers it is also possible to define explicit wind profiles.
SOFiLOAD establishes from the wind definitions all other characteristic wind
data which are relevant for the description of the natural wind or the generation
of the artificial wind histories later on. The result of the wind profile thus has the
following elements
k = k Vmen , (6.2)
with k = u, v, w
Input and results are also displayed graphically. For any wind definition via
SOFiLOAD three pictures will be created:
Picture 1: Site overview and topology A plan view of the site with wind direc-
tion, coordinate axis, roughness and topologic formations etc.;
Picture 2: Wind speed in the boundary layer A side view of the site with
roughness profile along the luv wind direction and the complete V mean -
profile up to the atmospheric wind;
Picture 3: Distribution of speed, turbulences and effective wave lengths A
detailed side view of the structure with all characteristic values along the
structures height;
yielding the forces for a uniform velocity field or the steady state equivalent value
of the relative velocity of a structural component to the wind field. The definition
for a plane section is as follows:
F=CqA (6.4)
with:
The elements to be loaded with wind are selected via the GRP record. A purely
steady loading without any dynamic effects may be also created via SOFiLOAD.
The wind force coefficients for the element types beam, cable and truss may
be defined within AQUA for any section depending on the angle of attack. This
definition is strongly recommended for all dynamically sensitive structures or el-
ements sensitive for galloping or flutter. To obtain those values it is common
practise to perfom wind tunnel tests or use a CFD (Computational Fluid Dynam-
ics) analysis.
For standard steel shapes or buildings there are values given in the literature or
the design codes. AQUA generates for steel shapes simple functions depending
on the angle of attack but without any information about galloping. SOFiLOAD
has all values for rectangular and circular sections available. Without any spec-
ification only the component in wind direction is considered with a coefficient of
2.0.
SOFiLOAD has also the possibility via records BEAM, TRUS and CABL to define
additional factors to the defined force coefficients selectively for for those type
of elements individually. Further there is the record GRP with additional factors
available to define shadowing, influence ordinates etc.
For areas it is possible to define in SOFiLOAD via AREA or QUAD explicit wind
pressure or uplift values perpendicular to the area. For cylindrical shapes ac-
cording to many codes and for planar standard roofs and walls according to DIN
1055 Teil 4 values may be selected. If no such values are defined, all coefficients
are taken to be 1.0.
If the pressures are defined in several data points from a wind tunnel test, the
record WIPT allows a comfortable method with an external FE-mesh of the data
points to generate the required loading data. Especially in case of transient
loadings, this method is strongly recommended.
The turbulences are then the sum of an infinite large number of small harmonic
velocity frequencies. Their distribution along the axis of frequencies is charac-
terised by a power spectra.
The power spectras are the deterministic part of the wind load, the real kernel as
the Fourier-Integral of the turbulence time history. The power spectra of the nat-
ural wind may be described by simple formulas according to the general pattern
of the Karman spectra definition. If one chooses then a random phase distri-
bution for all the frequencies, it is possible to reconstruct the Fourier-Integral of
a clearly defined random time history and thus the time history itself. This is
exactly what SOFiLOAD does when generating a wind history.
The ratio between the turbulence in different locations in space are character-
ized by special similarity or coherence functions. These functions define in a
coarse sense the relation between gust wind velocity, the duration of the gust
and the size of the gust. It is clear that the spatial distribution of the gust has
a large influence on the forces within the structure. SOFiLOAD works with nat-
ural sizes of the gust which are otherwise overestimated in most design codes
considerably. (Davenports model with constant size of the gust in all heights).
The coherence algorithm of the wind history generation has to reflect that the
similarity between two natural wind histories in two points must become smaller
with larger distances. This decay of correlation is described in the literature in
different ways depending on the author of the publication, but may be general-
ized by the use of the half value distance (KOVCS ET AL . [29]), where the square
root of the coherence of the stochastic process has reduced from the full value
of 1.0 ( full coherence with distance zero) to a value of 0.5. Each turbulence
along any of the axis has the same function of similarity. Thus the coherence of
the natural wind is described by a 3 by 3 matrix of the half value distances. For
more details see notes for the record WSPE.
The first step of a wind analysis is always a static wind load (basic load case),
introducing all values needed for the wind history generation. Based on this
data the random time histories will be generated in a second step within time
and space.
The transient analysis in DYNA is nonlinear by using the nonlinear wind force
coefficients defined within AQUA. The analysis is interactive as it is considered
that the structure will move within the wind field and will thus modify the relative
wind speed in all cases by a vectoral superposition of the structural and the wind
velocity. Only by this feature important aerodynamic effects may be simulated
like aerodynamic damping or the bending galloping excitation.
The aerodynamic damping is introduced into the simulation with the den-Hartog
formulas, i.e. as a stationary approach automatically. (It should be noted here,
that despite the important effect it is hardly accounted for in German design
codes) Also the bending galloping excitation is automatically introduced in the
analysis if the wind force coefficients have been properly defined in AQUA.
The more enhanced possibilities to check for torsional galloping and general
flutter are only available with the inclusion of the Scanlan derivativa.
Last not least it should be pointed out, that the treatment of critical wind effects
is also a complicate matter of safety definitions (see e.g. KOVCS AND A NDR
[28]). This manual will not state any rules for that, the user will need to find its
The theoretical background of this map is the 2D wind profile from ESDU
[14, 15]. The term atmospheroc wind is the asymptotic value for the wind profile
allowing to extrapolate from the wind in low heights the velocity in the atmo-
sphere. The same term will be addressed in ESDU [14, 15] as gradient wind,
UG . However for UG there are more contradictory definitions in the literature (e.g.
as the wind speed in a height of 300 - 500 m for a roughness of the surface of
0.05). The new name should allow to distinguish this meaning from the other
definitions.
There are differences between the data. We had to judge on the reliability of the
data and will give more details about our selection:
Germany
In the region of north and Baltic sea, there are sufficient meteorological mea-
surements in S CHMIDT [39]. The statistical evaluation by the "Deutsche Wetter-
dienst" have been slightly modified (reduced Weibull coefficients)
In the region of the north sea there has been a good match between measure-
ments in S CHMIDT [39] and specifications in ECCS [11] , ECCS [12] and the
regional values in [ 13] . The regional values of Eurocode [ 12] /A however
appeared much to high and have been ignored (numbers from [ 12] /A are from
the very first version of [ 13] .
Control calculations for the German costal regions have shown that the rough-
ness for the offshore region with strong winds may be chosen to 0.005 m.
SOFiLOAD will use this value in all cases. design codes however quite often
use 0.01. So it might happen, that the program will evaluate 6 to 8 % higher
wind speeds for locations at the coast. This is also valid for all other coastal
regions. To get closer to the design codes it is recommended to add a region
with the roughness of 0.01 before the building.
For central Germany the ECCS iso lines ECCS [11], ECCS [12] are rather
on the conservative side. This is not only compared with french design codes
(a high jump at the boarder) [ 12] /A) but also compared to C ASPAR [3]. At
Rhine and in the Pfalz the isolines have been adopted to the regional values of
France. For eastern parts of central Germany mainly the evaluations of C ASPAR
[3] have been taken into account. The values from Caspar however have a rather
high variation of the yearly maximum, as the author has accounted for some
confidential corrections due to insufficient measurement data. The isolines are
based on a mean variation value of 12 % (Davenport suggests in general 10
%).
In Central Europe thus we have slower wind speeds than those of the design
codes. On the other side some values of the Caspar papers show that it is much
more important to account for the local topology.
South of the line Freiburg - Nuremberg the maps of ECCS [11], ECCS [12] have
been used. the values are rather close to the DIN assumptions.
France
Base was the regional map in [ 12] /A. Between the regions we have interpo-
lated. Compared to [ 12] /A the maps in ECCS [11], ECCS [12] show unrealistic
high wind speeds. (20 % deviations). [ 12] /A shows, that the wind speed at the
Biscaya is considerably lower than that of the North Sea.
The wind speeds according to ECCS [11], ECCS [12] are up to 25 % higher
than those of ESDU [14]; the difference is assumed to be caused by a inconse-
quent usage of reference roughness in ECCS [11], ECCS [12].
Italy, Greece
According to [ 11] . As these are regional maps, the wind speeds will be on the
conservative side, especially for the isles of the Aegis.
Spain, Portugal
Mainly according to ECCS [11], ECCS [12]; for Portugal additional data from [
12] /A) has been taken into account.
Eastern Europe
According to ECCS [12] with a transition to the Scandinavian codes in the Baltic
region.
Higher Altitudes
For the influence of the altitude ECCS [12] has a factor cALT , defined in the
national contributions to ECCS [12]/A. In general cALT will become greater 1.0 in
altitudes from 500 - 800 m. For example in Germany we have (for altitudes 800
- 1100 m):
This last increase has not been taken into account in the map. Thus it is recom-
mended to account for this effect in Great Britain via the topology.
A wind profile will be generated defining the wind speed along the height. The
type of the profile is selected via the item NORM. For the distribution of the wind
you may choose between:
the literal ATMO (the default), creating a profile based on the atmospheric
wind speed, which may be defined at item ZONE. The 50-year reference
value for ATMO may be taken from the wind map in paragraph 6.6 (Default:
60 m/sec for ZONE). The program generates a theoretical logarithmic profile
taking into account the roughness of the terrain based on the flow models
described in [ 8.1, 8.2] .
one of the listed classical design codes. The program then generates wind
profiles conforming to those design codes. Although the codes contain only a
static wind profile, it is possible for those standard wind profiles to perform a
transient dynamic analysis. The program will select the missing parameters
(gust speed, turbulence, coherences) automatically with a reasonable value.
an explicit profile along the height. The detailed definition is done via the
record WPRO. NORM does not need to be specified in that case, data en-
tered anyhow will be ignored respectively.
The classical design codes have in general 3 to 4 wind zones (ZONE) to be taken
from national wind maps or given in the appendices of the Eurocode. Some de-
sign codes allow also a more detailed specification via terrain categories CLAS
and with topological formations (WTOP). The following table shows an overview
of the possible classes. Any mismatch of classes or allowed numbers of the
topological elements will terminate the wind profile generation. It has to be
noted, that the Eurocode 1991 foresees the definition of the wind profiles within
the national annexes. Thus in Germany even an analysis according to Eurocode
has to select 1055, as this scheme has replaced the Eurocode formulation within
the NA.
It should be pointed out, that SOFiLOAD can use only physically reasonable
wind profiles, roughness and simplified topological models from the design
codes.
The Indian design code IS 875 provides a map with basic wind velocities. be-
tween 33 and 55 m/sec. The mean velocity and the gust wind speeds are ob-
tained from that value by three factors k1, k2 and k3. While the coefficient k2
is evaluated by SOFiLOAD, the other two have to be combined to a value VG0
= Vbk1k3 at this record. The specification of the wind zone I to VI itself is of
less importance. However for the categroy the structure class A (d < 20m), B
(20 < d < 50) or C (d > 50m) has to be combined with the terrain category 1 to 4
to a single input data 1A to 4C. The density of the fluid defaults with that design
code to 1.20 kg/m3 .
Some historic design codes are also still available. (Wind zones definable with
0 to IV, default is II):
The coordinate values DX, DY, DZ will define the direction of the mean wind in
the coordinate system of the building. The reference point REF and the direc-
tion DR are only of relevance for a dynamic wind history. The define a so called
vertical reference plane which should fulfill the coherence properties to the best
degree according to the wishes of the user. More details to this question are
given at record WSPE. For the definition of the above points, all three coordi-
nates are available as the orientation of the coordinate system of the structure
may have any orientation.
GH specifies the height of the terrain in structural coordinates. This is the origin
of the so called wind coordinate system to be used for all input and output. The
coordinates of the heights within the picture 3 created by SOFiLOAD are thus
measured not within the structural system but the wind coordinate system.
The density of the air defines the conversion between velocities and pressures.
It is depending on the temperature, the moisture and the air pressure respective
elevation. It is assumed to be constant for the total structure.
The geografical lattitude LAT defines via the Coriolis force (Ekmann-Spiral) the
height of the atmosperic boundary layer and the distribution of the mean wind
speed along the height. The default yields f=0.0001.
HMIN defines the height above ground which contains the constant part of the
wind profile. Below HMIN the profile is extended as constant and no special
turbulence properties will be developed. If the design code does not specify
such a value, 10.0 m will be the default.
Any single WPRO-definition will invalidate all recent NORM or ATMO definitions.
Only the explicit WPRO definitions will be used from then.
The input of the values does not need to be complete or consist of uniform types
of values. A simple value of H, V or VBOE will be sufficient. Gaps will be filled
by SOFiLOAD on its own as reasonable as possible. Physically contradictions
will be corrected as far as possible. Thus the following input definitions are
possible:
LC 100
WIND DY 1
WPRO 50 V 52.5
LC 8200
WIND DY 1
WPRO 15 V 30
WPRO 30 VBOE 58
enforces a not really sound or even matching set of all characteristic parame-
ters.
In such a case with not really clear definitions, which might be a real case if only
sparse data is available for the site of the structure, it is strongly recommended to
check the diagrams created by SOFiLOAD (especially picture No 3.) and modify
the input in such a way until a reasonable smooth wind profile is obtained.
The lateral and vertical turbulences as well as the corresponding wave length
will be needed only in case of a dynamic wind generation. Their input is of no
importance therefore for purely static wind design.
The wind profile is influenced by the distribution of the roughness of the terrain
on the luv side of the structure, called the roughness profile. A change of the
roughness in a distinct distance from the site will create a bench in the wind
velocity profile in a certain height and a jump in the profile of the gust wind
velocity, visible in the pictures created by SOFiLOAD (pict. 2):
The roughness profile may be specified with the record WROU against the luv
side of the structure up to a distance of -200 km. However a maximum of 9
sections with different roughness are allowed. The input for every section i has a
(negative) distance of the start of the section to the structure and the roughness
Ri = within that section. To specify the correct mean value for the effective
roughness an influence width should be taken into account within an aperture
angle of 60 respective to the structure.
The roughness value itself is equivalent to the roughness measure in the litera-
ture defining an integration constant for the differential equation of the fluid flow,
usually called z0 [ m] , but with no direct physical meaning. Values taken from
the literature for various terrain conditions are:
Roughness values larger than 1.0 m can not be treated by SOFiLOAD. The
default is a homogeneous roughness of z0 = 0.050 m.
The treatment of costal regions via SEA has the following background: the at-
mospheric wind is influenced only by the global roughness which is uniform for
sea and landside. At a coast like the northern sea there is a rather smooth tran-
sition. The wind from the seas side, which is the only important case will create
two boundary layers. The lower one is influenced by the land, while the upper is
governed by the sea. The limit between those layers is increasing in the height
when going to the interior of the landside. The limit will me manifested by a bend
in the wind profile. This point may be within the height of a structure. This spe-
cial case will be modelled by defining the SEA and prevent the over estimation
of the wind speed.
The definition of SEA will create a steadily increasing roughness profile derived
from measurements and statistical analysis of the German Weather Service
(DWD) in the North Sea region. Thus SEA is only usable to model the Ger-
man North or Baltic Sea or a similar flat coast region. For a steep or rocky coast
SEA should not be specified.
For wind profiles created from the atmospheric wind or from individual wind pro-
files, there are possibilities for geometric elements like hills, edges (sometimes
called steps) or ridges in the vicinity of the structure as well as on the luv as on
the lee-side. They influence the wind speed distribution which is accounted for
approximately based on the wind tunnel tests and evaluations given in M AIER -
E RBACHER [31].
For a hill the epi-centrum is at the top of the hill, for an edge or ridge it might be
chosen arbitrarily along the top line. The longitudinal axis of the hill or the top
line of an edge or a ridge is oriented in direction DX,DY,DZ. For an edge it is also
important to know about the sign of the direction. According to the next picture,
the foot line of the elevation is always on the right hand side of the direction
vector.
DX,DY
DX,DY
DX,DY
Figure 6.4: Topology: a) WTOP HILL XM 1000 500 DX 2 4.4 H 300 1400 2600,
b) WTOP RIDG YM 1000 DX -1 2 H 400 2500, c) WTOP EDGE 1000 0 DX 1.9 -1 H
500 2100
The influence of the topology is nonlinear and thus should not be superimposed
in general. To be more precise, the superposition will yield reliable results only if
the effect within the plan view is considerably different, i.e. the dimensions of the
elements are considerably different. Topology effects with more than 50 to 60 km
extensions are already included in the atmospheric wind map, the definition of
such elements would thus double the effects. Proper definitions do not contain
more than two elements, one of which has an extension of about 10- 30 km,
while the other (rather local) has not more than 1 to 2 km.
Wind definitions according to standard design codes will not allow for such pro-
visions in general. An exception is the EC, resp the 1991 and 1055, but even
then only a single edge or a ridge. Both codes use the same approach which
is implemented in SOFiLOAD. Both codes allow only one single formation and
the correction of the wind velocities is in general surely on the save side. H is
allowed only with a positive value if combined with a standard code. An improper
definition (number of elements, type and size of elements etc.) will always yield
an error message.
With WSPE the power spectra of the turbulence components of the wind and the
coherence for a dynamic wind generation are defined. The definition of TYPE
will select appropriate functions for all three directions. However it is possible to
select for any direction (LON, LAT, VER) an explicit typed spectra or a modified
spectrum defined with RESP.
6.11.1 Spectra
Spectra are defined in the scaled form introduced by Karman along the fre-
quency axis as follows:
S 1 X + 2 X 2 + 3 X 3
= (6.9)
2 (1 + b X c )d
L
X= = (6.10)
m V
where L is the effective wave length defined with the wind profile and thus fm
is the effective frequency of the turbulence. Spectra from Kaimal and Panofsky
use for X the Monin coordinates, replacing L by the height z. The spectra from
Fichtl/McVehil will be used with coefficients scaled to the Monin-coordinates as
well.
The shape of the spectra are different for different directions, therefore the six
coefficients a1, a2, a3, b1, b2, c are defined for three components. There are
other deviations dependent on the author or the type of spectra taken from
the literature. The most important are available and may be selected directly.
a1 a2 a3 b c d X
Karman longitudinal 4.000 0.0 0.0 70.8 2 5/6 L/
Karman lateral 4.000 0.0 3021 283.0 2 11/6 L/
CEN 6.800 0.0 0.0 10.2 1 5/3 L/
1200
Davenport 0.0 0.667 0.0 1.0 2 4/3 (10)
1800
Harris 0.374 0.0 0.0 0.5 2 5/6 (10)
The defaults for the longitudinal / lateral / vertical coefficients from type KARM
follow the approach introduced by Karman, which describes the reality in the
best way according to common practice. A deviation from that should be made
only in special cases. A second common approach is the Eurocode-Spectra
(part 2-4 Appendix B.11, Type CEN), a simplified form of the Karman spectra
to become more important with the application of Eurocodes. There are two
classical spectra available, the spectra from Davenport (DAVE), which is very
popular in the above form in Germany and Central Europe. Dave is not math-
ematical correct in its asymptotic behaviour, and has been corrected therefore
multiple times, however it is mostly used in its original form. DAVE describes as
well as EC or the Harris (HARR) spectra only the longitudinal component. The
missing two other directions are calculated with the Karman formulas therefore.
DAVE and HARR use a simplified scaling with small deviations from the Karman
approach.
C r fm
neutral longitudinal 6.198 (z/18)0.63 0.845 0.03(z/18)
neutral lateral 3.954 (z/18)0.35 0.781 0.1(z/18)0.58
unstable longitudinal 2.905 (z/18)0.14 1.235 0.04(z/18)0.87
unstable lateral 4.599 (z/18)0.04 1.144 0.033(z/18)0.72
SLongtdn 200 z
= (6.12)
2 (1 + 50 z )5/ 3
SLter 15 z
= (6.13)
2 (1 + 9.5 z )5/ 3
SVertc 3.36 z
= (6.14)
2 1 + 10 z5/ 3
z
z = (6.15)
U(z)
To compare the different formulas, the next picture shows the longitudinal com-
ponents of the implemented spectras: the relative displacement of the maximum
from DAVE, HARR and NASA compared to the Karman spectrum is a conse-
quence of the different scaling.
Any spectrum including the individual defined spectra have to fulfill as all other
implemented spectra the normalization condition:
S( )d
Z
= = 1.0 (6.16)
0
SOFiLOAD will check for any use of WGEN the normalization in the highest and
lowest point of the structure and will flag any deviation with more than +/- 5%
for . In those cases the simplest remedy is to scale the coefficients a1, a2,
a3 within a new definition of WSPE by 1/. For larger deviations a check of the
function definition is strongly recommended.
6.11.2 Coherence
The coherence function implemented in SOFiLOAD are according ESDU 86010
(ESDU [15], chapter 7, appendix A2).
p
coherence = () = exp (6.17)
V
p
coherence = (r) = exp 1.151.5
1
(6.18)
p
coherence = (r) = exp 0.651.3
1
(6.19)
For the Davenport formulation care should be taken, as there are also coeffi-
cients in use which are defined for the coherence 2k itself. These coefficients
are larger by a factor of 2.
A better approach are the modified exponential functions of Krenk DYRBYE AND
H ANSEN [10], which account for negative coherence as well as for the decay of
the coherence for zero frequencies for larger separation distances. A compari-
son can be done with the record WTST.
n n
(r , ry , rz , n) = 1 rc exp rc (6.21)
2U U
r
2
rc = (C r )2 + Cy ry + (Cz rz )2 (6.22)
v
2
U
u
n = +
t
n2 (6.23)
2L
The coherence () will thus be controlled via the half value distance factor 1 ,
thus the distance where the square root of the coherence diminishes by a
factor of 2. This factors 1 have to be defined for the coherence factor kk . For
high frequencies and large heights we have:
V
HWDk = kk (6.24)
r
1 2 (6.25)
Vm
with:
If for example in picture A2 of the ESDU for the root of coherence = 0.5 a
value = 0.7 is taken. Then an approximate value of k = 0.7/ (2) = 0.11 is
obtained. The default of the elements of the Kj -Matrix is slightly conservative
taking into account measurements of the last 30 years. It is possible to change
single elements individually. The values define a homogenous coherence which
is stretched at the surface depending on the roughness.(ESDU [15]) The values
thus are larger than the original values from Davenport.
WX
WY
Referenzebene
Referenzpunkt
Windrichtung
Figure 6.6: wind reference systems
The axis WX, WY and the vertical gravity direction WZ define a skewed coordi-
nate system where the longitudinal, lateral and vertical turbulence is calculated
along the reference plane defined by WY and WZ following the coherence within
that plane. This pattern of turbulence moves than along the wind direction in a
frozen form passing the structure, ie. the coherence in wind direction is always
1.0, the history is identical only with a different phase. This approach may be in
rare cases to much on the safe side. Examples for this are structures repeating
itself along the wind direction showing a resonance with the frequency of the
excitement not observed in nature. In those cases a correction with a slightly
change of value C3E 6= 1.0 may help.
(Davenport, 1968)
n
(r , r , r , n)2 = exp rc
q
U
rc = (C r )2 + (C r )2 + (C r )2
(Davenport, 1977)
n
(r , r , r , n) = exp rc
q
U
rc = (C r )2 + (C r )2 + (C r )2
(Krenk, 1995)
n n
(r , r , r , n) = 1 rc exp rc
q
2U U
rc = (C r )2 + (C r )2 + (C r )2
v
U 2
u
n = n +
t
2
2L
Based on the wind profile and parameters including, turbulence and integral
length distributions, defined with the basic load case LFG a number of load
cases will be generated with random transient wind loading. The random prop-
erties are assured by the load case number, which is also used as the initializa-
tion value for the random sequence. The required number of wind histories has
to be derived from the safety concept of the building. For the common design
codes and safety factors for wind a number between 9 and 11 histories should
be adequate in most cases.
The wind definition thus starts with the basic wind load case, e.g..
It is highly recommended to check first this load case thoroughly in all details
and proceed then to the generation of the individual spectra and wind histories,
where it is recommended to reflect those dependencies within the load case
numbers, e.g. the wind histories with load cases 301,302,... should be derived
from the basic wind load case 300.
LC 301 W TITL ' Dynamic Wind ' ; WGEN 300 SPEK UVW $$
HIST UVW 620 0.1
LC 302 W TITL ' Dynamic Wind ' ; WGEN 300 SPEK UVW $$
HIST UVW 620 0.1
LC 303 W TITL ' Dynamic Wind ' ; WGEN 300 SPEK UVW $$
HIST UVW 620 0.1
....
It is possible to change the spectra individually for some histories. In that case
WSPE has to be defined with all parameters between the LC and the WGEN
definition again. It is also possible to import wind spectra or even complete
histories from a secondary data base FROM. If SPEC is selected only the base
wind data is imported. The default for HIST contains the same components as
the spectra, for REST and FROM the wind history will be imported to.
The generation of the wind history has two steps. The first step (spectra gener-
ation) will create form the energy spectra based on the theory given inKOVCS
AND A NDR [28], KOVCS [27] an individual Fourier-spectrum for this load case
(a discrete Fourier-Integral) for all turbulence components of all nodal points of
the structure. The second step (history generation) will then create the discrete
wind history via a discrete Fourier-Retransformation. The spectras generated
once may be used for different wind histories: e.g. variant durations of wind,
variant time steps or the selection of lower or higher frequencies of turbulence
etc..
Some parameters of wind generation (e.g. DT, FMAX, FDEL) may be selected
by the user, they have to match however. The frequency step FDEL has to
be small enough, otherwise a non natural periodicity of the wind load may be
obtained. DT has to be chosen in such a way that all important frequencies of
the structure are properly addressed. An optional value of FMAX has then to be
larger that those important structural resonance frequencies. For the case of a
steady wind it is possible to specify DT 0.0 as special case.
The wind generation will become very costly on the other side if the parameters
are chosen to generous, thus it might be necessary to choose a best compro-
mise. FMAX and FDEL may be also changed for tests or prechecks in the eval-
uation phase of a project to have shorter response times. For the final design
however, the parameters should match the statistic necessaries. The defaults
are selected based on the needs for large bridges. for smaller structures mod-
ifications are necessary, e.g. reducing the value of DT, enlarging the value of
FMAX.
Within the generation of turbulence a decay of turbulence for the end point of
an element based on the local decay of coherences along the beam axis is
implemented allowing an easier generation of beam loading. For checks of the
turbulence it might be requested to switch this option off via the definition of
LCOH OFF.
For the inclusion of the Scanlan derivativa into the wind dynamics it is neces-
sary to have the sections defined with those wind coefficients in AQUA and an
estimated value for EIGB and EIGT has to be specified in the GRP-record.
For the lowest and the highest point of the wind profile the total spectra will ready
for graphical evaluation. Without definition of components for SPEC and HIST,
the analysis is terminated at that stage.
It is also recommended to start with a primary load case in DYNA / ASE based
on the static wind to keep the disturbances of the start up period as low as
possible.
The volume of the data may become rather large, because a nonlinear history
will create an own loadcase for every time step. That is why we recommend
to use a separate copy of the database for every history. With the definition of
the TO item, a clone of the current database is created containing all necessary
data for the wind history analysis. After performing the analysis and all super-
positions, the extreme values may be imported into the master via the program
DBMERG.
Using a wind tunnel experiment a model of the building is tested yielding integral
forces or pressures in discrete points. They vary along time and it is depending
on the structure if the loading may be taken as quasi static mean value or if the
dynamic effects should be modelled. To convert those pressures to loadings the
recommended procedure is as follows:
Assuming that we have an area of the hull of our structure with several measure-
ment data points, we may create a coarse mesh of triangles or quadrilaterals in
two ways. We have either the possibility to create this mesh to have each data
point near the center of one element (a) or in the corners or near the corners of
a bilinear mesh (b):
(a) (b)
Than the coordinates of that selected data point are specified with WIPT.
SOFILOAD will create an areal load pattern with the selected shape of the in-
fluence function. If the point is inside the element a constant pressure for the
whole element is created. if the point is near the edge (ELIM) a bilienar shape
function is assumed with the value 1.0 in the data point and 0.0 in the distant
nodes. Thus the node nearest to the data point will have an extrapolated value
> 1.0.
The influence functions may be then used directly within DYNA or may be con-
verted with STEP to single load cases for ASE.
Values for ELIM, TOL and MNAM are retained as default for all following defini-
tions.
7 Wave Loading
7.1 General
Waves on the ocean are primarly created by wind over longer distances. They
are an essential loading for embedded structures in the coastal regions or off-
shore. Similar to the wind a large scale stochastic wave field is generated, in-
fluenced substantially by sea currents and the shape of the coast. For these
problems special software (e.g. SWAN) is available.
For the loading of a structure a local design wave or wave spectra is provided,
which is saved in SOFiLOAD in an individual load case number. The SOFiSTiK
solution separates the wave model from the structure similar as in the previous
chapter. The water flow is calculated as if there is no structure present. For the
evaluation of the forces however the movement of the structure will be accounted
for by taking the relative velocities and accelerations by the Morison equation.
1 U
F = Fd + F = Cd D U2 + Chyd D2 (7.1)
2 4 t
c
z
x
Fi Fd
vy
vx
7.2 Introduction
Oceanic waters are deep waters, such that the waves are unaffected by the
Waves on the surface of the ocean, with periods usually between 3 to 25 sec, are
a fundamental feature of coastal regions. Other wave motions exist on the ocean
including internal waves, currents, tides, and edge waves. The term waves will
here apply only to surface gravity waves, to water with idealized physical prop-
erties and motions and with gravitation as the only external force [35].
Knowledge of these waves and the forces they generate is essential for the
design of offshore structures. An overview of the theories and mathematical
formulas for describing ocean surface waves and the forces, accelerations, and
velocities due to them, is given here, and two main wave categories are treated:
regular waves and irregular waves.
When wave heights become larger, the linear theory may not be adequate and
finite amplitude wave theories have to be used. These theories are nonlinear
and allow formulation of waves that are not purely sinusoidal in shape. For
steep waves or waves in shallow water, e.g. waves with flatter troughs and
peaked crests, higher order theories will be described such as the Stokes wave
theory and the Cnoidal wave theory. Furthermore, the stretching of linear theory
is introduced, which compensates for the small amplitude assumption and maps
Adopting a wave theory, care must be taken to ensure that the wave phe-
nomenon of interest is described reasonably well by the theory, since offshore
design depends on the ability to predict sufficiently wave surface profiles and
water motion.
z
H
x SWL d
d
L h
The particle velocities can readily be obtained from the velocity potential as
/ = and / z = z and the accelerations as the time derivative of the
velocities / t = and z / t = z . The alongwave horizontal and ver-
tical z velocity and the horizontal and vertical z acceleration, at position z
measured from the Still Water Level (SWL), in water depth d, are given by:
cosh [k (z + d)]
= cos (k t) (7.4)
sinh(kd)
sinh [k (z + d)]
z = sin (k t) (7.5)
sinh(kd)
cosh [k (z + d)]
=2 sin (k t) (7.6)
sinh(kd)
sinh [k (z + d)]
z = 2 cos (k t) (7.7)
sinh(kd)
where g is the acceleration due to gravity. For deep water tnh (kd) 1 while
kd , whereas for very shallow tnh (kd) kd while kd 0, leading to further
simplification of the above equations.
d 1 d 1
Wave property Shallow Water < Deep Water >
L 25 L 2
Dispersion 2 = g k 2 d 2 = g k
relation
g
L=T L=
p
Wave Length - gd T 2 1.56 T 2
2
Period relation
Horizontal = cos (k t) = ekz cos (k t)
kd
velocity
z+d
Vertical z = sin (k t) z = ekz sin (k t)
d
velocity
2
Horizontal = sin (k t) = 2 ekz sin (k t)
kd
acceleration
z+d
Vertical z = 2 cos (k t) z = 2 ekz cos (k t)
d
Acceleration
Stokes waves are an extension to Airys wave theory and therefore are also
formulated in terms of the velocity potential. For the Stokes 5th order waves the
potential reads:
5
c X
= G cosh [ k (z + d)] sin [ (k t)] (7.10)
k =1
Accordingly, the water particle velocities and accelerations, as well as the sur-
face elevation, are given by [40]:
5
X
=c G cosh [ k (z + d)] cos [ (k t)] (7.11a)
=1
X5
z =c G sinh [ k (z + d)] sin [ (k t)] (7.11b)
=1
5
X
= c 2 G cosh [ k (z + d)] sin [ (k t)] (7.11c)
=1
5
X
z = c 2 G sinh [ k (z + d)] cos [ (k t)] (7.11d)
=1
5
1 X
= F cos [ (k t)] (7.11e)
k =1
For a design wave, and k are to be determined by virtue of the following pair
of equations:
gT 2 2d
L= 1 + 2 C1 + 4 C2
tnh (7.13a)
2 L
H =L + 3 B33 + 5 (B35 + B55 )
(7.13b)
7.3.3 Cnoidal Wave Theory: 3rd Order and 5th Order Iwagaki approxi-
mation
Korteweg and de Vries (1895) developed a wave theory termed the cnoidal the-
ory. The cnoidal theory is applicable to finite-amplitude shallow-water waves and
includes both nonlinearity and dispersion effects. The theory is defined in terms
of the Jacobian elliptic function, cn, hence the name cnoidal. Cnoidal waves are
periodic with sharp crests separated by wide flat troughs. Many advancements
have been made since the initial theory and the cnoidal wave theory presented
byF ENTON [19] (1990), [20] (1999) is included here, both the full 3rd order as
well as the 5th order Iwagaki approximation.
In F ENTON [20] (1999) the underlying method relies on the expansion in two
main parameters: the wave height relative to the trough depth = H/ h and
the shallowness parameter = 42 / 3. The symbol cn is used to denote
cn(X/ h|m) = cn(( ct)/ h|m), where is a coefficient given in terms of . The
parameter m, the modulus of the elliptic function, is determined by the geometry
of the wave through an iterative process. The surface elevation for Cnoidal 3rd
order is given by:
2 3 3 2 4
3
=1 + m cn + m cn + m cn +
2 2 2
h m m 4 4 m
(7.14)
61 2 111 3 61 2 53 3 101 3 6
m + m cn + 2
m m cn +
4
m cn
80 80 80 20 80
1 The expressions are given in S KJELBREIA AND H ENDRICKSON [40], but notice that in Skjel-
breias original expression for C2, the factor +2592 should be replaced by 2592, see
Nishimura & al. (1977), F ENTON [18] (1985), B HATTACHARYYA [2] (1995).
5 1 0 2j+1
z X X z
p =2 cn() sn() dn()
gh =1 j=0
h
(7.16b)
X k
cn2(k1) (( ct)/ h|m) jk
k=1
2j + 1
where the coefficients jk and the rest of the parameters and their definition,
can be found in F ENTON [19] (1990) and F ENTON [20] (1998) for both 3rd and 5th
order.
7.3.4 Stretching
AIRY-Theory is only defined up to the SWL and for waves of infinitesimal small
height. However, when extended to finite crest amplitudes the results above the
SWL are overestimated [4], [24]. To remedy this, either the values are extrapo-
lated or the results are stretched (or compressed) to the actual water level.
Wheeler Stretching: the profile of the fluid kinematics computed by the lin-
ear theory is effectively stretched or compressed to the instantaneous wave
d+z
surface. This is achieved by replacing z with z 0 = d d+ d in Eq. 7.11.
Chakrabarti Stretching
Vertical Stretching: for fluid particles located above the SWL, the values are
taken equal to those obtained at z = 0, hence are stretched vertically.
Linear Extrapolation
Hint
The stretching is a filtering technique, which modifies the small-amplitude
assumption of linear Airy wave theory. Its use is important for the irregular
waves, since they are composed by superposing linear Airy waves. With
this linear filtering method, a wave train of any length and any degree of
irregularity can be used in design of offshore structures.
Stretching is applicable to finite water. This means that when the full range
of irregular waves (Tmn - Tm ) is evaluated, the stretching scheme will only
be applied for those regular waves that will fall into finite water.
dH/HLH=H0.04 dH/HLH=H0.5
dH/HgTH=H0.00155 dH/HgTH=H0.0792
HShallowHwaterHHHHHHHHHHHHHHHHHHHHHFiniteHwaterHHHHHHHHHHHHHHHHHHHHHDeepHwater
0.1
Deep water H
breaking criterion = 0.142
H L
2
gT
Stokes 5th order
0.001
ar
lit
HL
26
So
0.0001
Linear wave theoryH5Airy3
Cnoidal
waves
Wave height is limited by both depth and wavelength. For a given water depth
and wave period, there is a maximum height limit above which the wave be-
comes unstable and breaks. This upper limit of wave height, called breaking
wave height, is in deep water a function of the wavelength. In shallow and tran-
sitional water it is a function of both depth and wavelength. Wave breaking is
a complex phenomenon and it is one of the areas in wave mechanics that has
been investigated extensively both experimentally and numerically.
The range over which periodic solutions for waves can occur is given in Figure
7.4, which shows limits to the existence of waves determined by computational
studies. The highest waves possible, H = Hm , are shown by the thick line, which
is the approximation to the results of Williams (1981), presented as Equation
7.17 in F ENTON [19] (1990):
2 3
L L L
0.141063 + 0.0077829
+ 0.0095721
Hm d d d
= 2 3 (7.17)
d L L L
1 + 0.0788340 + 0.0317567 + 0.0093407
d d d
Nelson has shown from experiments, that the maximum wave height achievable
(just below breaking) in practice is actually only Hm / d = 0.55, rather than 0.78
which is the theoretical maximum. According to N ELSON [33] (1994), the differ-
ence between ratios of H/ d 0.78 to 0.55 may lead to a significant reduction in
the wave loadings and the design crest levels above mean water level.
The degree of nonlinearity of waves is often quantified with the Ursell number U,
which combines wave steepness S = H/ L and relative water depth:
steepness (H/ L) HL2
U= = = (7.18)
(rete depth)3 (d/ L)3 d3
It has been pointed out that the Cnoidal theory should be applied for U > 40,
marking the boundary between Stokes and Cnoidal theory, as shown in Fig.
7.4. Furthermore, it is necessary to know the limiting value of wave heights
and wave steepness at different water depths to establish range of valid-
ity of a Stokes-type expansion. This is customarily done by comparing the
magnitude of each successive term in the expansion [35]. Each should be
smaller than the term preceding it. For example, if the third-order term is
to be less than 1 percent of theq second-order term, the limiting wave steep-
ness is H/ L = (1/ 7) sinh (kd) 1 + 8 cosh3 (kd). The maximum steepness is
3
Sm = 0.142 tnh(2d/ L), which leads to the deep water breaking wave limit of
H/ L = 0.142, as shown in Fig. 7.3.
1
Hm / d Solitary>Wave
0.8 U>40
0.6 H>/>d>=>0.55
Wave height / depth
H/d
0.4
0
1 10 100
Wavelength / depth
L/d
A dynamic analysis will then account for the fluid structure interaction according
to the assumptions stated before. A complete modeling of all effects requires
considerable numerical effort for a fluid structure interaction with field methods
(CFD).
Two methods are implemented here for the sampling of the spectrum and the
determination of the amplitude:
E() = ep (7.20)
5 4
approximated by
p 2 p
0.5 d/ g if d/ g < 1
(, d) =
p 2 p
1 0.5 2 d/ g if 1 d/ g < 2
p
1 if d/ g 2
Hughes gives also the following expressions for the parameters and in the
TMA spectrum based on shallow water data and applied here:
where = H/ (4L), H the significant wave height and L the wavelength at the
peak frequency, as defined by the linear theory.
!
G =C(s) coss (7.24)
2
p
(s/ 2 + 1)
C(s) = (7.25)
(s/ 2 + 1/ 2)
p
2
12.0
10.0
=7.0
8.0
=5.0
ES()
6.0
4.0 =3.3
=2.0
2.0
=1.0
0.0
0.2 0.4 0.6 0.8 1 1.2 1.4 1.6
Instead of the single design wave a complete spectra of an irregular wave field
may be used. In that case H is the siginficant wave height, while T is the peak
period of the spectra. The seed for the random generator is the load case num-
ber. Values of NF, TMIN, TMAX etc. are used only for that case.
Furthermore, the irrational frequency, rather than the default constant frequency
interval, can be applied for the calculation of the amplitudes, when using a spec-
trum. This is done by specifying the literal :I after the input spectra type, e.g.
JONS:I or with a stretching scheme JONS:IW.
For the TMA spectrum, the default values used here for the parameters and
are given by Eq. 7.23, as described by Hughes [26]. The main advantage of
this parameterization is the ability to specify the equilibrium wind sea spectrum
associated with a given energy level. Otherwise a standard input could be given
as in JONSWAP spectra, such as for example = 3.3 and = 0.0081, which
will just transform the corresponding JONSWAP to a shallow water spectrum.
The wave kinematics may be enhanced by a constant current. For this an expo-
nential distribution may be specified. For the exponent a value of 0.17 is found
in the literature.
z+d
U(z) = U (7.26)
d
8 Snow Loads
The snow loading in SOFiLOAD is just at the beginning of the total development.
Wehen defining the design code with NORM it is possible to define the snow
zone and the altitude about sea level. From those values a basic snow load is
derived according the provisions of the design codes.
Snowloads are available for all free loadings of type LINE and AREA as load type
SNOW. The load value then defines the form factor wich is used to be multiplied
with the basic snow load on the ground, depending on the inclination of the roof
and local aglomerations.
9 Output Description
The output extent can be controlled via the option ECHO LOAD. Following inputs
are possible here:
NO no printout at all
YES only printout of the most important load case information
FULL printout of all input loads
EXTR printout of all generated loads
Actions
The following values are only output, if they were defined in the input or if the
default was used via the input of a load case type:
If the loads are copied from previous load cases in the current one with the
record COPY, the output is done below the check list of load case selection.
Loads completely copied from load case ... with factor ...
or
Loads partially copied from load case ... with factor ...
Either the factor was defined explicitly or it was determined from the relevant
safety and combination coefficients according to the input superposition rule.
The used partial safety factors and the input superposition rule are printout after
the factor.
Meshfree Loading
The reference typ contains quite a lot of additional information. If given in capital
letters it is a definition by the user. If the first position of the reference type
is given as capital letter and the other ones are given in lower case, then the
reference type was selected by the user, however, without a reference or group
number. If the reference type is in lower case, it gives the type and identifier
of the object the program has selected automatically. If multiple ids have been
used a "-mult-" is given instead of a number. The literals for the reference types
are specified with the corresponding load definitition records.
Example:
The load case number is the number of the read load case from the database.
A warning is printout after the calculation, if a defined load was not considered
with 100% during generation.
9.9 Accelerations
If translational or rotational accelerations are used with the record ACCE, then
they are converted within the program in corresponding element loads and print-
out.
Wind loading
Roughness profile
D [km] Distance from building
r [m] Roughness
Hr [m] Relative height
Hi [m] Influence height
or
A graphic and/or a table is also printed before the output of the corresponding
load case for a definition of a time function with the record STEP.