Professional Documents
Culture Documents
Superposition
SOFiSTiK | 2020
MAXIMA
Superposition
SOFiSTiK AG
This manual is protected by copyright laws. No part of it may be translated, copied or reproduced, in any form or by
any means, without written permission from SOFiSTiK AG. SOFiSTiK reserves the right to modify or to release
new editions of this manual.
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: Queensferry Crossing | Photo: Bastian Kratzke
Contents | MAXIMA
Contents
Contents i
SOFiSTiK 2020 i
MAXIMA | Contents
ii SOFiSTiK 2020
Contents | MAXIMA
5.1 Check List of the Actions and Load Case Selection . . . . . . . . . . . . . . 5-1
5.2 Check List of the Generated Load Cases . . . . . . . . . . . . . . . . . . . . 5-3
5.3 Output of the Used Load Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.4 Output of the Superposition Factors . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.5 Plate Internal Forces and Beddings . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.6 Internal Forces of Shells and Disks . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.7 Stresses in Plane Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.8 Stresses in 3-D Continuum Elements . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.9 Internal Forces, Displacements and Beddings of Beams . . . . . . . . . . 5-8
5.10 Internal Forces and Displacements of Design Elements . . . . . . . . . . . 5-9
5.11 Displacements, Support Forces and Reactions . . . . . . . . . . . . . . . . 5-9
5.12 Truss Members and Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.13 Springs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.14 Forces of the Kinematic Constraints . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.15 Tendon Stresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.16 Velocities and Accelerations of Nodes . . . . . . . . . . . . . . . . . . . . . . 5-12
5.17 Relevant Superposition Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.18 Special Features for Superposition with an Objective Function . . . . . . 5-12
5.19 Result Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.20 Storey Results of the Seismic Design . . . . . . . . . . . . . . . . . . . . . . 5-13
iv SOFiSTiK 2020
Task Description | MAXIMA
1 Task Description
The results which were calculated with the SOFiSTiK programs are stored in the database.
The task of the program MAXIMA is the determination of extreme values of the internal forces,
stresses, displacements and support reactions.
Different methods according to the partial safety concepts of the Eurocode and international
design codes and according to the conventional method without partial safety factors can be
used to determine the maximum values. Here MAXIMA finds the most unfavourable action
effect and applies the combination factors automatically.
To achieve this, the superposition is done in two steps. In the inner step MAXIMA finds the
extreme value from different load cases of the action effect and in a second outer process the
action effects are combined.
The load cases to be superimposed may be defined unconditionally (e.g. dead load) or condi-
tionally (e.g. live load). In a conditional superposition each load case is only applied if it has an
unfavourable contribution. The definition of loads which exclude each other (alternate loads)
or of loads with changing sign is also possible.
The load cases which are used for the superposition can be combined through arbitrary com-
binations of the calculated load cases. This occurs via the definition of subsequent load cases,
which leads to an absolute superposition with the previous load cases. Each load case may be
multiplied with a scaling factor, so that normalised loads can be used during the static analysis.
The loads of non-linearly calculated load cases have to be include already the correspond-
ing combination coefficients and safeties. A superposition with action effects (record ACT) is
therefore not implemented. However, it is possible to make an alternative selection via the
load cases only (record LC). Load cases which have been analysed non-linearly can only be
superimposed as individual alternate load cases (TYPE AG1) with the factor 1.
The results are printed and stored in the database for later design or visualisation purposes.
The extent of the output can mainly be controlled by the user.
The user should check the superposition by investigating random samples! With the
input of LOAD and FACT in record ECHO all the defined and determined factors and the used
load cases are output for every individual superposition value. Only the relevant superposition
values are printed with all involved factors, if ECHO CHCK is input.
2 Theoretical Principles
The user has to specify the design code used for the superposition rule at the beginning of the
task. This can be done in the program AQUA (record NORM) or, in the case of an interactive
input, with SOFiPLUS or SSD. MAXIMA then automatically uses the design code which is
available in the database.
The actions are already defined during the input of the loads (program SOFiLOAD). The cor-
responding load cases have to be allocated to the actions. The action can be only modified
temporarily in MAXIMA. The superposition is done with partial safety factors and combination
coefficients for actions defined by arbitrary load cases. These load cases or combinations of
them will be superimposed to define an action effect.
A superposition contains all action effects which are defined by a combination rule with the
record COMB.
The most unfavourable variable action is designated as the leading variable action. MAXIMA
selects the most unfavourable one and considers it according to the chosen combination rule.
When using the explicit defined combination with action groups the determination of three
leading variable actions is possible.
The leading variable actions are marked with a * at sumQ1/sumQ2/sumQ3 (sum of the loads
leading variable action) in the output with ECHO FACT FULL. This variable action which has
the largest difference between sumL (sum of the loads leading variable action) and sumQI
(sum of the loads acting variable) is used as leading variable action! The remaining variable
actions are multiplied with the combination coefficient for the accompanying variable action in
dependence on the combination rule.
The default equations 2.1 till 2.7 correspond to the combinations which are given in the EN
1990 (except for equation 6.10a and 6.10b) and in the DIN 1055-100 / DIN-Fachberichte. For
the special equations 6.10a and 6.10b of the EN 1990 and their use variants in the National
Annexes it is recommended to use the explicit defined combinations.
For design codes, which are used other equations for the combinations e.g. BS 8110, BS
5400, Australian Standard, Indian Standard, US Standards, it is recommeded to use the explicit
defined combination.
If superposition defaults are available in the INI file for the selected design code, these defaults
are used then in MAXIMA without input for COMB, ACT, ADD, LC and SUPP or in WinMAX.
Precondition for this is the usage of the default actions of the record ACT (SOFiLOAD) or of
the Loadcase Manager.
The number of processable load cases is limited to 999999. Upon request, the user can re-
peatedly overwrite previously stored load cases or can recombine the load cases from different
The results can be stored under a new load case number. Possible available results of former
calculations are deleted, unless, something else is requested with the input CTRL DELE.
The superposition is made separately for each node and for each element or beam section in
the database.
The superposition takes place for all nodes or elements even when not all of them have been
selected. This is necessary for the sequential internal storage of the results by the program.
However, only the results for the selected nodes or elements are printed out.
When the values to be superimposed are close to zero, then some problems arise for the
imposed loads, in the calculation of the corresponding internal forces. This is handled by the
program MAXIMA in the following manner: If the actual absolute value is less than 10E-6 of the
maximum value of all load cases encountered, then the imposed load cases do not participate
in the superposition.
If however the derivation of the quantity being superimposed is known, e.g. the shear force
in the case of a superimposed bending moment, then an imposed load case is used if the
corresponding derivation is positive.
Fundamental combination for the ultimate limit state (EN 1990 equation 6.10):
X X
Ed = E γG,j · Gk,j ⊕ γP · Pk ⊕ γQ,1 · Qk,1 ⊕ γQ, · ψ0, · Qk, (2.1)
j≥1 >1
As alternative possibility the EN 1990 provides the superpositions with the equations 6.10a and
6.10b which are available in different variants in some National Annexes using the reduction
factor ξ and the reliability factor KF .
The realization of the equations 6.10a and 6.10b is done in each case via an explicit defined
combination. More information can be found in chapter 2.3 and in chapter 3 at COMB, ADD
und ADA.
The partial safety factor γg,A for the permanent actions and γA for the accidental actions is
determined with the input GAMA in record ACT. The default for both partial safety factors is
defined in dependence on the selected design code in the INI file and is automatically available.
The EN 1990 plans the use of ψ2,1 · Qk,1 (= all variable actions with ψ2 ) as a second variant
for the accidental design combination. This variant has to be done with the explicit defined
combination COMB EXTR EXPL. An input variant is for example:
Actions with type seismic action (E) and accidental actions (A) are processed also in equation
2.1, if the used design code has not planned superpositions according to equation 2.2 and
2.3.
Infrequent combination for the serviceability limit state (EN 1990 / German DIN-FB101):
X X
Ed,nƒ req = E Gk,j ⊕ Pk ⊕ ψ1,nƒ q · Qk,1 ⊕ ψ1, · Qk, (2.6)
j≥1 >1
For design codes which do not plan the combination coefficient ψ1 (e.g. OEN 4700 accidental
combination) the leading variable action is determined and multiplied by ψ2 . If a higher co-
efficient ψ2 than ψ1 is input, this higher coefficient ψ2 is used for the leading variable action.
MAXIMA uses here the maximum (ψ1 ,ψ2 ). In analog mode the maximum (ψ1 ,ψ2 ,ψ1,nƒ q ) is
considered for the leading variable action for a superposition of the infrequent combination
(equation 2.6).
The user should be aware that only the sum of all load cases defines the partial safety factor
which is valid for an action effect (see record ACT).
With the record ADA only certain actions which are available in the database can be used
for an explicit defined combination with action groups (e.g. ADD {Q1}) bzw. {QI}) ... for
variable actions). Without the selection with the record ADA, all actions are considered from
the database.
An example for the use of the explicit defined combination is the superposition for design
according to the Swiss code SIA 262. According to SIA 260 a superposition at which only
ψ0 and no γ are to be considered for the accompanying variable actions is necessary for the
check at ultimate limit state:
X X
Ed = E γG,j · Gk,j ⊕ γP · Pk ⊕ γQ,1 · Qk,1 ⊕ ψ0, · Qk,
j≥1 >1
An input for the explicit defined combination with permanent and variable actions, where only
Q, W and S should be used as variable actions, reads for example:
ADA Q,W,S
ADD {QI} FACU PSI0 FACF 0.0
ADA Q,W,S
The definition is done here via action groups, where it is defined at {Q1} that a leading variable
action is available. The leading variable action is considered in the unfavourable case with the
corresponding partial safety factor γ. The following actions {QI} get only the combination
coefficient ψ0 as unfavourable factor.
Another possibility is to prescribe a special action as leading variable action (e.g. according to
French BAEL). A possible input with single actions is for example according to BAEL (D2.2,1
design resistance for buildings, first line of the table):
The leading variable action is here QB with the factor (γ) 1.5 in the unfavourable case. The
accomanying variable actions W and S are considered with the factor γ · ψ0 in the unfavourable
case and T_1 with 0.8.
For a combination which uses ADD it is also possible to input together actions and action
groups. For example it is useful, if a specific variable action is the leading variable action and
all other defined variable actions are the accompanying variable actions. With the input:
all permanent actions (action group {G}) are combined with the leading variable action W and
all other variable actions as accomanying variable actions (action group {QI}).
You can find further examples on the home page of the SOFiSTiK AG - Support - Link Infoportal
http://www.sofistik.com/infoportal/
check:
either: consideration of only one variable action Q with the partial safety factor γ
or: consideration of all variable actions Q with the partial safety factors γ · ψ (e.g. for German
DIN 18800 = 1.5 · 0.9 = 1.35)
X
S = γg · Gk ⊕ γq, · ψq, · Qk, (2.9)
Both superpositions have to be analysed according to the design code. Only the most un-
favourable superposition is decisive. MAXIMA processes internally both equations and output,
however, only the more unfavourable superposition.
If an action with type seismic action (E) is available, then this action is processed with equation
(8) and (9) because an explicit superposition with seismic combination is not planned here.
For accidental combinations according to German DIN 18800 and Austrian OENORM 4300
the permanent actions G are used, however, with γg = 1.0 and all variable actions Q, however,
with γ = 0.9 (= 0.9 · 1.0) according to the equations 2.8 and 2.9. Additionally the accidental
action FA is considered as follows:
with γF = 1.0
Sr = Gk ⊕ Qk,1 (2.11)
or: consideration of all variable actions Q with the combination coefficient ψ (e.g. for German
DIN 18800 ψ = 0.9)
X
Sr = Gk ⊕ ψq, · Qk, (2.12)
If an action with type seismic action (E) is available, then this action is processed with equation
(11) and (12) because an explicit superposition with seismic combination is not planned here.
For comparison the intermediate superposition with explicit MAXIMA definitions is shown in
the example file maxima_intermediate-superposition.dat.
In a first step the extreme values of this loading are generated when the imposed loads and
the crane loads are superimposed in three alternative groups. This requires, that one of the
imposed load cases covers the full load.
PROG MAXIMA
HEAD EXTREMAS OF DEAD AND LIVE LOADS
TXA Time History
COMB 1 STAN
LC 1,2 G 1.2 $Dead load$
4,5,6 A1 0.6 $Imposed load$
(101 136 1) A2 0.36 $crane I$
Now the seismic loads are added. These have been analyzed with the program DYNA. First
a lot of results which are based on the response spectra method and separated with respect
to the three coordinate axis (301,304 and 307) are generated. For the design of the structural
elements these loads with alternating sign of the maximum have to be considered and in ad-
dition in the combinations at the corner as well as in the combinations horizontal and vertical.
The vertical loading is scheduled in this case either fully with a factor 1.3 or additionally to the
horizontal loading only with a factor of 0.5.
Furthermore a time response analysis of 6 discrete acceleration profile with artificial generated
base accelerations exists there. These are 36 extreme value load cases which are combined
into global extreme values in a second calculation of MAXIMA first of all.
PROG MAXIMA
HEAD ABSOLUTE EXTREMAS OF TIME HISTORY
TXA Time History has been performed with three sets of base
TXA accelerations each of them with
TXA
TXA a) 1.3 times the horizontal acceleration in x and
TXA 0.5 times the vertical acceleration
TXA
TXA b) 1.3 times the horizontal acceleration in y and
TXA 0.5 times the vertical acceleration
TXA
TXA The maximum and minimum evaluation of these cases has been
TXA done for normal force and both moments. This are six load-
TXA cases for each of the six histories.
TXA (LC 311-322, 331-342 and 351-362)
TXA
TXA absolute extremas of these 36 loadcases are evaluated now.
COMB 2 STAN
LC (311 322 1) A1 1.0
LC (331 342 1) A1 1.0
LC (351 362 1) A1 1.0
LC (311 322 1) A1 -1.0
LC (331 342 1) A1 -1.0
LC (351 362 1) A1 -1.0
SUPP 2 MAX ETYP BEAM TYPE N LC 391
SUPP 2 MAX ETYP BEAM TYPE MY LC 393
SUPP 2 MAX ETYP BEAM TYPE MZ LC 395
SUPP 2 MAX ETYP TRUS TYPE N LC 397
END
The following data which allow a superposition of all previous extreme values result now in the
third input block of MAXIMA. The increase of environment variable CDBASEMEM to a value of
about 2 million may reduce the CPU time from several days to less than an hour for a system
like the given system with more than 40 000 unknowns.
PROG MAXIMA
HEAD EXTREMA FOR EARTHQUAKE USING RESPONSE SPECTRA + TIME HISTORY
TXA Time History
COMB 3 STAN
LC (81 86 1) A1 1.0 $Combinations from before$
1. If a partial safety factor and/or a combination coefficient is modified for a load case
(SOFiLOAD record LC) and no modification of the action is done in MAXIMA, then the
value for the load case which was input in SOFiLOAD LC wins during the superposition.
2. If a partial safety factor and/or a combination coefficient is modified for a load case
(SOFiLOAD record LC) and a modification of the action is done in MAXIMA (record
ACT), then the in MAXIMA modified value for the action wins during the superposition
and not the value from the load case (SOFiLOAD).
Example:
SOFiLOAD: action snow - unfavourable partial safety factor GAMU with default 1.5, modified
only for load case 6 to 1.4
ACT S
LC 5
$load input for LC 5$
LC 6 gamu 1.4
$load input for LC 6$
Case 1: no further modification of GAMU in the MAXIMA input MAXIMA printout Design fun-
damental combination DESI default - without modification in MAXIMA for ACT S:
Case 2: The unfavourable partial safety factor is input now for the action in MAXIMA with 1.6
The above described procedure is different for an explicit defined combination with COMB
EXTR EXPL and ADD: The action/action groups are defined in MAXIMA with record ADD for
the explicit defined combination. For such a combination only an unfavourable and a favourbale
factor has to be defined. That means, that the factors are available for all load cases of the
action which is defined with record ADD or all load cases have the same factors FACU and
FACF for the action at ADD.
3 Input Description
[mm] Explicit unit. Input defaults to the specified unit. Alternatively, an explicit as-
signment of a related unit is possible (eg. 2.5[m] ).
[mm] 1011 Implicit unit. Implicit units are categorised semantically and denoted by a cor-
responding 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 (Eu-
rocodes, NORM UNIT 5).
Record Items
CTRL OPT VAL
COMB NO EXTR BASE TYPE COMC TITL
ACT TYPE GAMU GAMF PSI0 PSI1 PSI2 PS1S
PART SUP TITL
ADD TYPE FACU FACF
ADA TYPE
LC NO TYPE FACT
SUPP COMB EXTR ETYP TYPE FROM TO INC
X SELE LC CSAV TITL OPT
SUM COMB LC TITL
EXPO OPT TO PASS
ECHO OPT VAL
TRAC LC ETYP ELEM X SELE OPT
The records HEAD, END and PAGE are described in the general manual SOFiSTiK: ’Basics’.
The records COMB and SUPP should be input. If the actions (record ACT) and the load
cases (record LC) should be taken over without modifications from the database (from program
SOFiLOAD), the records ACT and LC do not have to be input then. If, however, an action or
a load case should get a modification in MAXIMA, the complete superposition definition (all
records ACT and LC) has to be input here.
It is to be noted that the actions (record ACT) and the relevant load cases can be only se-
lected and possible modified in MAXIMA. They have to be defined before with the program
SOFiLOAD.
General procedure diagram for the definition of superpositions with actions (record ACT, not
for explicit defined combinations with COMB EXPL and record ADD):
SelectionuofuanuactionuwithurecorduACTu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuactionu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuactionu
.u .u .u
SelectionuofuanuactionuwithurecorduACTu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuactionu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuactionu
.u .u .u
.u .u .u
DefinitionuofutheusuperpositionuwithurecorduSUPPu
Procedure diagrams for the definition of superpositions for explicit defined combinations with
COMB EXTR EXPL and record ADD):
Selectionuofuanuaction withurecorduADDu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuexplicituactionu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuexplicituactionu
.u .u .u
Selectionuofuanuaction withurecorduADDu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuexplicituactionu
SelectionuofuauloaducaseuwithurecorduLCu
forutheuchosenuexplicituactionu
.u .u .u
.u .u .u
DefinitionuofutheusuperpositionuwithurecorduSUPPu
Selectionuofuanuactionufromutheudatabaseuwithu
recorduADAu
Selectionuofuanuactionufromutheudatabaseuwithu
recorduADAu
.u .u .u
Selectionuofuanuactionufromutheudatabaseuwithu
recorduADAu
Selectionuofuanuactionufromutheudatabaseuwithu
recorduADAu
.u .u .u
.u .u .u
DefinitionuoftuheusuperpositionuwithurecorduSUPPu
Algorithm for a combination without input of actions (record ACT) and load cases (record LC):
Combination rule
COMB
yes available no
in CDB
Procedure diagram for the definition of a standard combination (combination only with load
cases, no actions) COMB EXTR STAN and record LC):
Special feature of the record TRAC - Combination Tracing: One or more records TRAC have to
be input in an own MAXIMA run for the printout of the load case tracing about the combinations
for specific element. The determination of the load case tracing have to be done after the
corresponding superpositions. As an example, an input looks like this:
PROG MAXIMA
HEAD Loadcase tracing
TRAC LC 2129 ETYP BEAM ELEM 3 x 1[-] OPT 'IF'
TRAC LC 2229 ETYP BEAM ELEM 8 x 1[-] OPT 'IF'
END
All combinations EXTR DESI, ACCI, EARQ, RARE, FREQ, NONF and PERM according to the
equations 2.1 - 2.7 can be also input with the explicit defined combination EXTR EXPL.
3.3.1 EN - Eurocodes
EN 1992-2004, EN 1993-2005, EN 1994-2004, EN 1995-2005, EN 1996-2005, EN 1992-1991
DIN 1045
OEN 4300
IS IR112
NF BAEL
SS BBK-04, SS BRO-2004
DS 411, DS 411-BRO
NS 3472, NS 3473
PROG MAXIMA
HEAD
ECHO ... $(not urgently necessary)$
END
the defaults of the INI file are activated for the selected design code. Precondition for this is
the usage of the preset actions of the record ACT (SOFiLOAD).
CTRL
An input for DELE only makes sense, if not all elements or nodes were selected and results
have already been stored. With CTRL DELE NO one stipulates that only the data generated in
the current program run is stored. However, it is necessary that results for all nodes, elements
and beam sections must have already been stored in the database, because the program can
not insert anything between two data records.
If for example two results from a concentrated load have to be stored for a beam section, then
they must already be present in the load case which is to be overwritten, otherwise an error
message (No. -3 in MUDS) occurs.
All combination rules and superposition commands which are available in the database are
deleted with an input CTRL INIT. Thus it is possible to calculate some MAXIMA input blocks
(e.g. with default from the INI file and manual inputs) twice and more without deletion of the
complete database.
DESI,ACCI,EARQ,PERM,RARE,FREQ,
NONF,STAN
H Primary loads
HZ Primary and additional loads
NONE Load cases are not assigned to any type
for EN 1995 (EC 5) and German DIN 1052-2004 (tim-
ber structures)
PT Permanent combination
LT Long term combination
MT Middle term combination
ST Short term combination
VT Very short term combination
for accidental combination fire
FIRE Combination fire
or
Type of an already existing action defined with record
ACT in program SOFiLOAD
A combination rule is selected with COMB. In general the action effects (record ACT or ADD
and ADA) with their relevant load cases (record LC) relate to this rule. The actions and the load
cases which are a part of the respective combination are to be input behind the corresponding
COMB record! Otherwise the default of the actions and load cases is activated. The actions
have to be already available in the database (definition in program SOFiLOAD) and can be only
modified in MAXIMA with the record ACT. It is also possible to define combinations without
actions.
MAXIMA takes the design code to be used for the combination rule from the database. The
user has to specify the design code right at the beginning of the task, either in the program
AQUA (record NORM) or in the case of an interactive input with the SSD at System Informa-
tion.
If using an explicit combination with EXTR EXPL the definition of actions or action groups must
follow with the records ADD and ADA. An input of the record ACT after COMB EXTR EXPL is
not allowed.
DESI, ACCI and EARQ are to use for checks in ultimate limit state and PERM, RARE, FREQ
and NONF for checks in serviceability limit state.
For the simplified superpositions (e.g. German DIN 18800, OENORM 4300) DESI-V, ACCI-V
or RARE-V have to be input. The Russian SNIP 2.01.07-85 allows the superpositions DESI-V,
ACCI and RARE-V.
STAN - unspecified design combination should be used for design codes without partial safety
factors and combination coefficients (e.g. German DIN 1045 old).
NONL is planned for a combination with non-linear calculated load cases (determination of an
enveloped). Action (record ACT) are not allowed here. The input load cases are considered
compulsorily with TYPE AG1 in record LC.
In the following table the input possibilities for EXTR are printed with the relevant defaults for
TYPE:
(TYPE must be
explicitly input
here)
With that it is also possible to use the result load cases for further superposition. The literals
which exist in record ACT can be used here for TYPE for an intermediate superposition. In
this case it is to be noted that the action has be defined already with a record ACT in program
SOFiLOAD. The definition of a new action is not possible in record COMB.
For design codes without partial safety factors and combination coefficients (e.g. German DIN
1045 old) and for German DIN 1052 also STAN - general design combination, H - primary
loads or HZ - primary and additional loads can be input.
With the EN 1995 (EC5) and the derived design codes correction factors kmod have been
introduced for the permissible stresses and kdeƒ for the deformations. The distinct value is
depending not only on the material but also on the service class and the duration of the loading.
The information about the duration of the loading has to be available at the superposition load
cases. This is done via an input of PT, LT, MT, ST or VT for TYPE.
If using a free defined combination rule with EXTR EXPL or the combination of non-linear
calculated load cases with EXTR NONL, the type of the resultant load cases must be explicitly
defined.
As type of the action one may use any literal with up to 4 characters, however some combina-
tions 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 partial 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 super-
position rule within the action category.
• Each action 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.6: Structure of the actions, their categories and their load cases
For example there are for road bridges in EN 1990 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 superimposed 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 cases however will be applied together as leading variable action.
It is only possible in MAXIMA to use actions which were already defined in program SOFiLOAD
and to modify single values of these actions (partial safety factors and combination coeffi-
cients). In the case of modification of the definitions for PART and SUP the following program
behaviour is to be noted: If only one of the values is specified in MAXIMA, the other value is
set to its default values.
Furthermore load cases which are a part of an action can be removed or other available load
cases can be selected for an action in MAXIMA. Anew definition of actions is not possible in
MAXIMA.
Modifications of the actions are only temporarily processed in MAXIMA. That means
The actions indicated in the table are used only as preset action, provided that they are avail-
able 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.
For the seiesmic action there is in EN 1998 an importance factor γ depending on the impor-
tance class to be selected by the user explicitly:
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 EN 1990
- L_T, Tandem Axle of LM 1 (γ = 1.35) [0.75] [0.75] [0.00]
GR_T
- L_U, UDL loading of LM 1 (γ = 1.35) [0.40] [0.40] [0.00]
GR_U
- 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] [1.00] [0.00]
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
- 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
Action ψ0 ψ1 ψ2
W: Wind for buildings [0.60] [0.20] [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" depending 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 superposition rules if specified in
SOFiLOAD.
With the specification of ACT all subsequent load cases in SOFILOAD will then have this action
type as default.
The item PART defines, to which action of the selected superposition equation the input ac-
tion 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 superposi-
tions 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, G_1 and G_2, 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).
Hint
All categories of an action must have the same definition of PART. E.g. categories Q_A
and Q_B of the variable action Q get PART Q. Only the load groups of a variable action
PART Q_1 till Q_9 can be different.
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), partial safety factor action-wise
PERC PERC always (permanent) with variable factors, partial safety factor load-
case-wise
COND Q conditional (only unfavourable)
EXCL A* mutually exculsive
EXEX Ano mutually exclusive but conditional inclusive categories (only within
an action), MAXIMA record LC only one alternative group number
Ano
UNSI W changing sign (e.g. seismic actions)
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 partial safety factor is used for all load cases of a permanent
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) partial safety factor is applied. In
the contrast to that the partial 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.
SUP ALEX defines a permanent alternative group (MAXIMA record LC TYPE AG1). Only
the load cases of an action or all load cases of the categories of an action are used for the
formation of a permanent alternative group. Here only a load case is considered for the super-
position, also if it has a favourable contribution. Load cases of different actions do not exclude
themselves mutually. If SUP ALEX is input for some actions, a load case is considered per
action.
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 associated 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 actions 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 defined with this record or via the SOFi-
PLUS 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 combination 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 categories with corresponding inputs for the
item SUP, then the intermediate superpositions and the following superpositions are done in
one MAXIMA run.
Example:
PROG SOFILOAD
HEAD
ACT XY_A gamu 1.4 0.0 0.6 0.4 0.2 0.6 PART Q_1 SUP excl
ACT XY_B gamu 1.3 0.0 0.5 0.3 0.1 0.5 PART Q_1 SUP excl
ACT XY_C gamu 1.45 0.0 0.6 0.3 0.0 0.6 PART Q_2 SUP exex
ACT XY_D 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_A
LC -1
ACT XY_B
LC -1
ACT XY_C
LC -1
ACT XY_D
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_A und XY_B 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 cate-
gories XY_C and XY_D 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.
The record ADD can be only used with COMB EXTR EXPL. The actions or action groups are
input here for the explicit defined combination.
The actions have to be input with SOFiLOAD record ACT and to be available in the database
after the calculation. The assignment of actions to an action group is controlled by the definition
of PART in record ACT.
A following record LC is only possible for an explicit input action. If using action groups the
program determines itself the corresponding load cases. Thus an input of a record LC is not
allowed after the input of an action group!
The assignment of a load case (record LC) to another action or category is not allowed with
record ADD. The calculation is interrupted with an error report.
If a numerical value or an literal with exception of the collecting literals is input for FACU, then
an input for FACF must follow, also if the value is 0.00.
Here it is also possible to define a specific variable action as leading variable action. The other
variable actions can be input then with action groups.
Example: Wind is the leading variable action with the factor FACU GAMU. A further leading
variable action which has the factor FACU PSIU should be determined from the remaining
variable actions. All other variable actions are considered with the factor FACU PS2U. The
input reads:
TYPE Designation the action from the selected action group LT4 !
The record ADA can be only used with COMB EXTR EXPL and the selection of an action
group (e.g. {QI} for all variable actions) at ADD. Only the actions which are selected here are
used during superposition for the action group. All actions which are available in the database
for the selected action group are considered without an input of ADA.
The actions have to be input with SOFiLOAD record ACT and to be available in the database
after the calculation. The assignment of actions to an action group is controlled by the definition
of PART in record ACT.
Only the actions G,Q,S,W are used in the following input example, also if more permanent and
variable actions are available in the database:
If e.g. the categories Q_A, Q_C and Q_E exist for the action Q, following input is also possible:
Different ADA records for the leading variable action {Q1} and for the accomanying variable
actions {QI} can be done:
FACT Factor with which the corresponding internal force of −/ LT 1.0
the initial load case is multiplied
With LC any desired combinations can be analysed or already combined load cases may be
defined for the superposition. Each load case can be used repeatedly for different load case
types. Therefore, under certain circumstances, it is possible to work with unit load cases in a
static analysis.
Examples:
Thus the default is here LC NO 0 = All loadcases with the same type as the action. That means
that the load cases 2 and 3 are allocated to the action Q without explicit input for LC.
If only categories, e.g. Q_B and Q_C, are defined for the action Q:
then the default for both categories is LC NO -1 = All loadcases of the same category.
In the third case the action and additionally categories with relevant load cases are input:
The default for the action Q and for the categories Q_1 and Q_2 is in each case LC NO -1 =
All loadcases of the same category, if an input for ACT is not done or if only ACT Q is input
in MAXIMA. This means that the load cases 2,3 are arranged to Q, the load cases 4,5 to Q_1
and the load cases 6,7 to Q_2.
ACT Q
LC -1 $all LC of the same category -> here only LC 2 and 3$
ACT Q_1
LC -1 $all LC of the same category -> LC 4 and 5$
ACT Q_2
LC -1 $all LC of the same category -> LC 6 and 7$
or
ACT Q
ACT Q_1
ACT Q_2
the categories are considered twice with their load cases (Q_1 with LC 4,5 and Q_2 with LC
6,7).
Caution:
With the input
ACT Q
LC 0 $all loadcases with the same type as the action$
the load cases of the categories Q_1 (LC 4,5) and Q_2 (LC 6,7) are arranged to the action
Q. This results in the consequence, that the definitions of Q_1 and Q_2 for SUP of the record
ACT are not considered anymore. Here the definition SUP of the action Q is valid. The partial
safety factors and combination coefficients are arranged, however, to the load case and they
do not changed.
TYPE PERM The decision whether all load cases of a permanent action with
PART G or P are taken into account as favourable or unfavourable
is effected by determination of sums. It means that either the
favourable or unfavourable factor is used for all load cases.
TYPE PERC The decision whether the load cases of a permanent action with
PART G or P are taken into account as favourable or unfavourable
is effected loadcase-wise. It means that the load cases can get
different factors within a permanent action.
A mixing of load case with TYPE PERC and other types (PERM, ALEX) is not recommended.
In this case, the load cases should be assigned to different permanent actions.
Consideration of load cases with TYPE AG1-AG99 or ALEX, if they are a part of a permanent
action e.g. G:
For load cases, which have the TYPE AG1-AG99 or ALEX and which are a part of a permanent
action and its categories, the sum of all values of the permanent action is decisive whether the
load cases are favourable or unfavourable. This is the same procedure as for TYPE PERM.
If a follow-up load case is defined, it is considered only, if the relevant main load case has a
part for the superposition.
Example:
If the load case 11 of the variable action W acts favourably and thus it does not have a part for
the superposition, then also the load case 12 is not considered.
The default depends on the default superposition of the load cases (SUP), which is input with
record ACT. All superpositions SUP PERM get the TYPE G, all superpositions SUP COND
get the TYPE Q, all superpositions SUP EXCL get the TYPE A1 ..., all superpositions SUP
UNSI get the type W, all superpositions SUP USEX get the TYPE X1.... and all superpositions
SUP ALEX get the TYPE AG1. SUP PERC of the record ACT corresponds to TYPE PERC.
Modifications of the types are only temporarily processed in MAXIMA. That means
these inputs are only considered in this MAXIMA calculation. The default from record
ACT SUP is overlaid then! In case of doubt it is recommended to use the default from
record ACT and not input a literal for TYPE at LC.
The default for the input with the standard combination (COMB EXTR STAN) is for TYPE as
follows:
load case 1: G
all other load cases: Q
Among the load cases of an alternative load case group, only the one with the most detrimental
effect is used for a superposition. The load case with the most detrimental effect among the
groups A1 to A99, X1 to X99 is handled as a live load, i.e. if none of the load cases has a
detrimental effect, these groups are not taken into consideration at all. However, one load case
is always considered for the permanent alternative load case groups AG1 to AG99. The as-
signment of the alternative groups to one or more ACT records is decisive for the superposition
result.
The superposition of non-linearly analysed load cases is only permitted, if they are superim-
posed using TYPE AG1 without the ACT record. If using the literal NONL for EXTR in record
COMB, the load cases are processed automatically with TYPE AG1. Then the program cal-
culates the effective load case as a selection from a series of non-linear analyses (extreme
values boundary lines).
If no record LC and no record ACT are defined, all load cases in the database, which were
analysed linearly, are used for the superposition. In this case either the definitions which are
already available in the database or, if no definitions are available, the defaults in MAXIMA are
used.
X X value of the beam axis or of the design element for [m] 1001 -
a specific beam section or SIR cut
Input of a value corresponds to a beam section in m
or input for the relative distance of the beam section
with [−] as a factor [−]
in [o/ o] [o/ o]
in [o/ oo] [o/ oo]
e.g. 0[−] is the beam start and 1[−] the beam end
The desired superposition values and their corresponding load case numbers are selected with
SUPP.
For the designation TITL 32 characters are available. The input designation can have, however,
only 18 characters, because the program uses automatically 9 characters for an information
about the superposition and 5 characters for an information about the element type at the be-
ginning of the designation (see Output Description: Check List of the Generated Load Cases).
The designation is saved in the database during the first calculation. This designation is not
overwritten in the database in the case of a modification!
There is also the possibility to select only certain element types and for these all scalar vari-
ables which are available for the superposition. In this case, a selection for elements or groups
can be made for the printout with FROM TO INC. An input for all scalar variable of e.g. beams
is then:
Input possibilities for TYPE in dependence of the element type ETYP and for LC preset
two-digit load case numbers:
The input possibilities for the static system are marked in the third column. A 3D means three-
dimensional system, 2D means plane frame/disk and 2DSL means plate/girder.
• for beams - ETYP BEAM, for design elements - ETYP DSLN and for external beam sections
- ETYP BSCT
The superposition of the pile bedding in transverse direction is done according to following
procedure:
1. The superposition factors are determined for the pile bedding in transverse direc-
tion PT.
2. Afterwards the corresponding values PTY and PTZ are calculated with these fac-
tors.
3. At the end PT is determined again by means of the Pythagoras.
The superposition of the spring force in transverse direction is done according to following
procedure:
1. The superposition factors are determined for the spring force in transverse direction
PT.
2. Afterwards all corresponding values as PTX, PTY and PTZ are calculated with
these factors.
3. At the end PT is determined again by means of the Pythagoras.
Equivalent stresses (Von Mises) for QUAD elements can be controlled with a literal or via
an objective function (chapter 3.11.7). When using the literal VMIS the plane stress state is
calculated:
r
σ = σ 2 + σy 2 − σ · σy + 3 · τy
2 (3.1)
As an example for shell stresses at the upper side for plane stress, the input for this objective
functions is as follows:
The superposition of the bedding stress in transverse direction is done according to fol-
lowing procedure:
1. The superposition factors are determined for the bedding stress in transverse di-
rection PT.
2. Afterwards the corresponding values PTX, PTY and PTZ are calculated with these
factors.
3. At the end PT is determined again by means of the Pythagoras.
The maximum bending moments m-xx of a plate (QUAD elements) should be determined in
the ultimate limit state for the ultimate design combination. BASE in record COMB and LC are
not input. With that the number 2101 is generated for the superposition load case max m-xx:
For superpositions without actions (without record ACT, e.g. German DIN1045old), the gener-
ated load cases are numbered as follows:
If several state variables which are separated with commas should be defined for TYPE and
if the generated load cases should get load case numbers which are different from the default
and which are not continuous (case 2: no input of BASE in record COMB and own definition
of LC), then the load case numbers are to be input for every state variable with LC separated
with a comma.
Example: The maximum and minimum values of N,VZ,MY should be determined for a frame
and girder system. The following load case numbers should be defined:
However, if the result load case numbers should be continuous, then it is sufficient to indicate
the first number for LC. Following input
defines the six result load case numbers from number 121 to 126.
Several records SUPP can be generated the same load case numbers, as long as they use
the same combination rule.
Using the preset combinations from an INI file the result load case numbers have a default
according to the chosen INI file. They can be modified in WinMAX (SSD: ’Define Combinations’
and ’Execute Superposition’.
Group selection:
Results of elements can be also printed groupwise. In this case the literal GRP has to be
choosen at FROM. The group number or the name of a secondary group can then be defined
A group selection is not possible for nodal results. If the internal forces and moments in the
nodes of plane and volume elements (ETYP QNOD, BNOD) should be printed groupwise, the
group number has to be defined at SELE.
Element selection:
If an element selection is desired, then the element or node numbers can be input at FROM
and TO whereat INC defines the increment. In the case of an input of only an element or node
number at FROM only the superpositon result of this number is printed.
Without an input at FROM, TO and INC and with a corresponding ECHO option (e.g. ECHO
FACT, ECHO QUAD, ECHO BEAM) the results for all elements or nodes are printed which are
available.
SUPP EXTR SRSS creates two load cases (SRMA for maximum and SRMI for minimum).
Only permanent or unfavourable load cases are considered here. In the case of variable load
case of the type Q or COND the sign is decisive, whether the load is used or not. For example
the maximum SRMA does not use initial values of a variable load case with a negative sign.
Corresponding values are generated proportionally.
Example:
COMB 2 STAN
LC 1,2,3,4 TYPE Q
SUPP 2 EXTR SRSS ETYP NODE TYPE PX FROM 1 LC 103
20.0
0.82 = p (3.2)
14.02 + 20.02
Compared to the example the load cases 3 and 4 are considered with the factor 1.0, if the input
SUPP ...
end
SUPP 1 EXTR max ETYP NODE from 309 TYPE pz LC 15 CSAV 55
end
SUPP 1 EXTR min ETYP NODE from 309 TYPE pz LC 16 CSAV 56
end
SUPP 55 EXTR max ETYP NODE TYPE pz LC 25
SUPP 56 EXTR min ETYP NODE TYPE pz LC 26
end
the maximum support reaction PZ of the node 309 is determined and stored in load case 15.
The factors are saved simultaneously in the new combination 55. Then the relevant support
reactions of the other nodes are determined in a new superposition with this combination 55
and stored in load case 25. Here an END has to be input before the new superposition defi-
nition with the saved combination. The determination of the minimum support reaction PZ in
node 309 and of the relevant other support reactions occurs with CSAV 56 in analog mode to
the maximum support reaction.
Then it is possible to generate loads for a load case with the program SOFiLOAD using the
combination factors which are saved at CSAV. For this the combination number and the com-
bination type COMB have to be input in record COPY of the program SOFiLOAD:
PROG SOFiLOAD
HEAD ...
LC 201
COPY 55 COMB
LC 202
COPY 56 COMB
END
In the case of the corners and the edge centres of the encasing rectangle an input in the
program AQUA record SPT can be omitted.
Y+Z- Z- Y-Z-
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Y+
Y Ï Ï Ï Ï Ï
Y-
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Y+Z+ Ï Ï Ï
Z+
Ï Ï
Y-Z+
Z
Figure 3.7: Cross section points
The definition of the cross section point is necessary for a superposition with the scalar vari-
ables normal stress in cross section point (TYPE SIG) and shear stress in cross section point
(TYPE TAU). MAXIMA superimposes here only internal forces and moments. That means, that
these internal forces and moments which fulfil the superposition criterion MAX-SIG, MIN-SIG,
MAX-TAU or MIN-TAU for the corresponding cross section point are determined.
If TYPE SIG or TAU is defined for some cross section points within one MAXIMA block, the
resultant load case numbers are increased about 1.
A objective function is generated with superposition values (described above at TYPE) and
perhaps with factors or defined variables (LET or STO variables). An objective function for
example for the resultant shear force of a plate reads as follows:
• The superposition values are to be combined reasonably. Only the superposition values of
one element type ETYP are to be defined.
• The rules for CADINP are valid. An objective function should be input with quotation marks
’...’. Blanks are avoid.
• The result load case number of a superposition with an objective function has to be input
manually.
The determination of an superposition result with an objective function runs exactly with a linear
function. For a quadratic function it is to be noted that following relationship is valid
( + y)2 > 2 + y 2
If a factor which is defined either explicitly or with a variable is input, it is to be noted that the
factor is used only for the weighting during processing of the objective function. This factor
does not come in into the numerical value of the superposition result! As an use for that the
determination of the boundary stresses is mentioned.
The user is even responsible for the superposition with an objective function. The user
should check the superposition here! With the input of LOAD and FACT in record ECHO
all the defined and determined factors and the used load cases are output for every individual
superposition value. Only the relevant superposition values are printed with all involved factors,
if ECHO CHCK is input.
For evaluation the literal RSET has to be input at ETYP, the respective ID of the single elements
at TYPE and the respective ID of the set (header in SOFiMSHA) at FROM. The ID of the set
(header in SOFiMSHA) and the respective single elements can be a number or a literal. It
is to be considered that an ID, which is defined as a number, can be input with or without
apostrophes both in the program SOFiMSHA and in MAXIMA. The input has to be identical in
both programs.
The results sets have to be input separately. Several result sets can be also defined as a
CADINP loop. An input for TO is not allowed.
The result load case number of a superposition with a results set has to be input manually. It
should be noted here, that different result load case numbers have to be defined for different
RSET.
In the example which is shown below the ID of the set is the number 2 and it is input in
MAXIMA at SUPP ... FROM. The IDs of the single sets are here ’PVER’ and ’PAXI’.
PROG SOFIMSHA
HEAD
...
RSET ID 2 TITL 'Bearing type 2'
RSET ID 'PAXI' NO 1002 SET SPRI\_RES P TITL 'longitudinal'
RSET ID 'PVER' NO 1003 SET SPRI\_RES P TITL 'transverse'
...
PROG MAXIMA
HEAD
ECHO RSET FULL
COMB ...
...
SUPP COMB EXTR ETYP TYPE FROM LC TITL='Bearing type 2'
1 MAMI RSET 'PVER' 2 2000
Using record SUM, sums of results from individual load cases with manually defined factors
can be determined. Therefore, the use of record SUM is only allowed for standard com-
binations COMB EXTR STAN and related initial load cases which have to be defined as
permanent. All defined initial load cases are always taken into account for the determination
of the sum, even if they have a favourable effect.
Example:
The superposition values are determined automatically for the respective system.
The combination rule is automatically deleted after calculation of the superposition results.
Only the superposition results are stored in the database. Therefore, it is not possible to
execute superpositions with record SUPP simultaneously with record SUM for such a special
combination.
For the designation TITL 32 characters are available. The input designation can have, however,
only 28 characters, because the program uses automatically 4 characters for an information
about the superposition at the beginning of the designation.
Output extent:
In addition to the default TABU YES in record ECHO, the extended output can be additionally
selected with ECHO FULL FULL or ECHO LOAD,FACT. A selection of individual elements
or the printout of the relevant values is not possible. For this purpose, the output of lists is
recommended in the Result Viewer.
EXPO
With the record EXPO you may export the superposition definitions for nodes and elements in
the database or in the INI file to an input file for MAXIMA. This may be useful in special cases.
If the filename is not specified the data will be appended to the most recently defined file or a
file with the name project_MAX.DAT is generated.
Hint:
It is to be noted, that only the superpositions (records SUPP) of the last MAXIMA block are
considered during the export. That means for the export from the SSD, that only the super-
positons of the task Superpositioning which was calculated at last are used for the export
file.
First two tables with the selected load cases including the load case factors as well as the de-
fined GAMMA and PSI values and the generated load cases (ECHO TABS YES = default) are
printed. Only these combinations which are used for the superpositions are output with ECHO
TABS YES. The printout of all combinations which are available in the database is done with
ECHO TABS FULL.
If only the combination rules are defined in a MAXIMA input without definitions for the super-
positions (without any record SUPP), it is possible to get the output of the combination rules
and the table ’Loadcase selection and actions’ with the explicit input of ECHO TABS FULL.
Then the superposition results are printed, if a corresponding input for ECHO is done explicitly.
An explicit input for ECHO must be positioned before the record SUPP! Thus the output extent
can be modified individually for each superposition. In the case of multiple ECHO records in a
row, the record name ECHO has to be repeated for each record in order to avoid confusion of
ECHO literals with identical record names.
The values of the used initial load cases are printed with the explicit input ECHO LOAD YES
or with ECHO FULL FULL before those of the superposition load cases.
The output of the partial safety factors and combination coefficients is controlled via an explicit
input of ECHO FACT. With ECHO FACT FULL all involved GAMMA and PSI values of the initial
load cases and the factors resulting from these are output in detail. Only the factors unequal to
zero are output with ECHO FACT YES. The default for FACT is FULL. Using both items (LOAD
and FACT) the user should check the superposition results by investigating random samples!
The input ECHO CHCK prints only the respective decisive point after the superposition (analo-
gous to ECHO LOAD and ECHO FACT). If an element or node selection with SUPP FROM TO
INC is used simultaneously with an input ECHO CHCK, then the relevant values only of this
selection are printed as superposition result. It can be clearer sometimes to use ECHO LOAD
YES for selected elements instead of ECHO CHCK, because only the factors unequal to zero
are printed with ECHO LOAD YES.
Using the Result Sets an input ECHO CHCK has no influence and ECHO RSET YES is set.
ECHO CHCK CSAV saves the factors of the load cases for each relevant value as combination
rule with the number of the resulting load case into the database. In this case the numbers
of the resulting load cases have to be from 1 to 999, because the maximum number of the
combination is 999 in the record COMB.
With the input of ECHO BSEC FULL even the results for beam sections are printed, which
should not be printed due to the input in the program SOFiMSHA.
Hint
In the case of big systems with a lot of elements we recommend to check the results with
the extensive output only for a special element. This can be done with ECHO CHCK or
with a definition of this element in record SUPP item FROM and ECHO LOAD,FACT. If
the extensive output e.g. with ECHO FULL FULL is chosen for all elements, this may lead
to a longer computational time and to a very large PLB file.
With the use of command TRAC, it is possible to trace a Combination and retrieve detailed
information on how a resulting Load Case has been generated, as an outcome of a MAXiMA
superposition. More specifically, this feature will discover and print out all the input Load Cases,
associated with a Combination, with their corresponding factors, that have been determined
by MAXiMA. This is especially useful in order to investigate, after a superposition has been
performed, how a critical Load Case on a specific element has been generated.
The required input parameters are the number of the resulting Load Case of interest, as well
as the element type and number. For BEAM elements, X position must be specified too, and, in
case a Load Case refers to cross section stresses (SIG / TAU), a stress point must be entered
in parameter SELE, analogously to the corresponding parameters of SUPP record. Parameter
SELE may be also used to specify a group number for nodes on QUAD or BRIC elements
(QNOD / BNOD). Finally, with parameter OPT it is possible to control the depth of the tracing,
ie. if intermediate superpositions should be resolved too or tracing should stop on the first level
of detected input Load Cases.
Using the above parameters, the corresponding SUPP and COMB information, which were
originally used during the superposition that generated the specified Load Case, will be initially
read from the database. With this information available, it is subsequently possible to retrieve
the associated input Load Cases, with their corresponding factors that have been used in
the superposition. In case the detected result type is stored in the database, as is in most
circumstances, TRAC will attempt to validate that the superposition result computed during
tracing matches to what has been actually stored in CDB, during the superposition. However,
in case of result types computed on-the-fly, such as stresses on stress points of BEAM’s cross
sections, or Von Mises stresses for QUAD elements, this is not possible.
Hint
Tracing must be performed in an individual MAXiMA run, as it cannot co-exist with the
standard superposition functionality.
Currently it is not possible to trace superpositions associated with Result Sets, Boundary
Elements and Tendon Stresses for Quad Elements, as well as superpositions according
to a user-defined function.
In the SSD there is the task Define Combinations on the one hand and to the second the task
Superpositioning.
With the task Superpositioning the user defines which maximum and/or minimum values of a
specific scalar variable for an element type which is to be input should be determined. The
quantity of output can be specified additionally.
The task Superpositioning can be inserted repeatedly in the SSD. So it is possible for example
to realize an intermediate superposition.
The input possibilities depend on the design code and the static system which were selected
at the beginning of the input process.
For the combinations and superposition a reasonable default is generated from the information
of the database according to the used design code (INI file).
a new combination rule is selected. The following preselection of the combination rules
is available:
For this purpose the Number and the Name may be modified opposite the default. The preset
combinations of the INI files are generated with number 100 and following.
The combination rule (formula) for the superposition is defined at Superposition Kind. The
combination rules are selectable here in dependence on used design code according to the
record COMB:
for simplified superpositions according to German DIN 18800 and other ones
ULS fundamental simplified corresponds to COMB DESI-V
ULS accidental simplified corresponds to COMB ACCI-V
(only for German DIN 18800 and Austrian OENORM B 4300)
SLS charact. (rare) simplified corresponds to COMB RARE-V
kind (e.g. design fundamental combination) is only possible, if no action groups are used for
the definition of actions. Using actions a modifcation is possible, however, the indicated factors
for the actions have to be checked by the user.
It follows the definition of the type of the result load cases at Type of resulting loadcases
(corresponds to TYPE record COMB). For design codes with superposition with safety factors
and combination coefficients the result load cases can be assigned here to the kinds of
superposition according to ultimate limit state and serviceability limit state (except for the
simplified superpositions):
Furthermore all actions defined in the Loadcase Manager or in SOFiLOAD are available for all
design codes. With no Type the result load cases do not get a type.
Using a simplified superposition (e.g. according to German DIN 18800 or Austrian OENORM
4300) following types of the result load cases are preset:
It follows the input of the load case numbers for the load cases to be generated at Numbers of
resulting loadcases. Three possibilities for the definition of the result load case numbers are
planned here:
2nd semi-automatic
A four-digit till six-digit load case base number which first two till four digits are defined at Offset
for loadcase number is selected here. A number divisible through hundred of a minimum of
100 and a maximum of 999900 can be input at Offset for loadcase number. The last two digits
of the result load case number are determined via the default at Superposition Commands ⇒
First Loadcase No. The procedure corresponds to case 1 described in record SUPP: BASE in
record COMB input and LC in record SUPP not input. Thus an input of the First Loadcase No.
at Superposition commands is not possible.
Result load case number:
3rd manually
The first freely optional load case number is input at Superposition Commands ⇒ First Load-
case No. If some result load cases are generated, than the load case numbers are numbered
continuously. The numbers 100 to 999999 can be defined as result load case numbers.
However, the calculation is interrupted with an error report, if numbers of the initial load cases
were used for the result load cases. The procedure corresponds to case 2 described in record
SUPP: BASE = not input in record COMB or input with zero and LC in record SUPP input.
Result load case number:
The inputs for the combination rule are taken over with the button . If the number of
the combination rule in the overview in the left window area is marked with a * (e.g. 1* :
Ultimate Design Combination), then this combination was generated manually or does contain
modifications of the user.
Definition of the Actions (corresponds to SOFiLOAD / MAXIMA record ACT, for userdefined
combination record ADD)
the actions are taken over from the database. Actions have to be defined before in
the Loadcase Manager in SOFiPLUS or in SOFiLOAD! Only the Kind of action and the
safety and combination coefficients of an already defined action may be changed in the
Superposition Manager.
The saved actions can be selected at Type. The Name of the action is taken over from the
Loadcase Manager or from SOFiLOAD. For a userdefined combination following action groups
are additionally available:
The definitions from the Loadcase Manager or from SOFiLOAD are taken over for Kind of
action. The Kind of action corresponds to the item PART in record ACT and it defines,
to which action of the selected superposition equation the input action belongs. Following
possibilities are available for Kind of action:
Following partial safety factors and combination coefficients are shown at Modify safety
factor or combination coefficient for the selected action:
The new definition of the corresponding coefficient is possible with a tick. A modification is
only effective for this combination rule in which the modification was done and it is not
taken over in the database!
The inputs for the action are taken over with the button .
If Standard Superposition at Superposition kind was selected for the combination rule, the
command Insert new element ⇒ Action omits then.
the load cases which appertain to an action are defined. The button Loadcase is not
selectable in the case of a definition of an userdefined combination (Explicitely defined
Combination). The load cases are allocated automatically to the action group or to the action
from the datebase information.
The load cases which are available in the database and which appertain to a before defined
action are shown at Loadcase. All load cases which are available for this action are selected
with Number 0 and All loadcases with same type as the action. Only the load cases which
are a part only of the relevant category are selected with Number -1 and All loadcases of
the same category. A detailed explanation is available in record LC of the MAXIMA input.
However, one or more load cases can be selected by marking for this action.
The selected load case number is announced at Number. Also load case numbers which are
available in the database and which were assigned to another action as the selected one can
be input here.
The Name of the load case is taken over from the definitions in the database. It can not be
modified here.
At Loadcase type it is defined, how the load case is considered for the combination (corre-
sponds to MAXIMA record LC TYPE). The default depends on the definitions at the actions,
which was input in the Loadcase Manager - Actions or in SOFiLOAD (corresponds to record
ACT item SUP). If Choose nonlinear Extrema was selected at Combination rule - Super-
position kind, the load cases must get the Load case type - add the most unfavourable
always (AG1-AG99)!
Modifications of the load case types are only temporarily processed in MAXIMA. That
means these inputs are only considered in this MAXIMA calculation. The default from
the Loadcase Manager - Actions or from SOFiLOAD (corresponds to record ACT SUP) is
overlaid then! In case of doubt it is recommended to use the default from the Loadcase
Manager or from SOFiLOAD and not input explicitly a load case type.
Following load case types are possible:
Here it means:
• add the most unfavourable always (AG1-AG99) - Only the most unfavourable load
case of a permanent alternative load case group is determined and added.
• add the most unfavourable (A1-A99) - The most unfavourable load case of the
alternative load case group is determined and it is only added, if it acts unfavourably.
• add the most unfavourable with unfavourable sign (X1-X99) - The most unfavourable
load case of the alternative load case group is determined with changing sign and it is
only added, if it acts unfavourably.
• additional contributing loadcase (F) - The contributing load case is added to the load
case which was defined before (main load case) and both load cases are superimposed
together, however only, if the main load case has a part for the superposition ⇒ record
LC.
If add the most unfavourable always (AG1-AG99), add the most unfavourable (A1-A99)
or add the most unfavourable with unfavourable sign (X1-X99) was selected at Loadcase
type, then the number of the alternative load case group can be defined at Number of the
alternative load case group.
A factor for the multiplication with the superposition values can be input additionally at Factor.
The inputs for the load case or load cases are taken over with the button .
Only the combination rule and the relevant load cases have to be input here.
The definition of the type of the result load cases is done then at Type of resulting loadcases
(corresponds to TYPE record COMB). If a design code without superposition with partial safety
factors and combination coefficients (e.g. German DIN 1045 old) is used, the result load cases
can get following types:
Design Combination
Comb. of principal loading
Comb. of princ.+suppl. loading
The load cases do not get a type with no Type. The Design Combination is the default for Type
of resulting loadcases.
window is opened:
The combination rules, actions and load cases can be inserted here in analog mode to the
commands at Insert new element. A combination rule can be copied, e.g. for changing
only the Superposition kind. In order to get a better overview it is possible to collapse or to
expand the combination rules. Single load cases, actions or a complete combination rule can
be deleted with Delete.
Only the preset combination rules which were modified are reinitialized with Reinitialzied. Com-
bination rules which were individually generated are not changed.
The combination rules are deleted and reinitialized according to the relevant defaults with
Delete all and reinitialize. It is to be noted that combination rules which are individually
generated or changed disappear!
4.3 Superpositions
The definition of the single superpositions is done in the task Superpositioning or in the
registry card Superposition Commands ( corresponds to record SUPP in MAXIMA). In the
SSD the calculation of the superpositions is also started here.
Reasonable superpositions for the default combinations of the available system are preset here
for the first processing. If the number of the superposition in the overview in the left window
area is marked with a * (e.g. 1* MAX/MIN PZ+MX+MY), then this superposition was generated
manually or does contain modifications of the user.
Several possibilities to define the input for this new superposition or to modify the inputs of an
already existing superposition are now available in the right part of the window. For this the
superposition which should be modified has to be marked in the overview of the left part. A
superposition command is active for the calculation, if a tick is set before the corresponding
superposition. The possibilities are in detail:
The information at
Number
Name
the designation of the superposition can be modified (corresponds to record SUPP TITL in
MAXIMA). The default is a designation which results from the definitions for Combination rule
as well as Control of Superposition, Result type and Result, where only the part of Result
is shown here (See also chapter Output Description.
Example for a preset designation of a superposition of the support reactions PZ with the com-
bination rule 1 in the ultimate limit state and the superposition extent maximum and minimum:
Support reactions PZ
1st El em en t t y p e
2n d Resu l t t y p e
3r d Resu l t
Figure 4.7: Diagram for the selection of the superposition variable
Element type
an element type is chosen (corresponds to record SUPP ETYP in MAXIMA). Following element
types are available:
Nodes
Constraints
Beams
External sections
Truss elements
Cable elements
Spring elements
Boundary elements
Sum of boundary elements
Area elements
Nodes at area elements
Volume elements
Nodes at volume element
Only the types which are available in the current system are offered for Element type.
At
Result type
all result types of the element type selected before are offered then. Following result types are
available for the single element types:
for Nodes:
Displacements
Support reactions
Velocities and accelerations
for Constraints:
Constraint forces
At last at
Result
A number for First Loadcase No. can be defined here in dependence on an input at Combi-
nation Rules - Combination - Number of resulting loadcases - manually. The procedure is
explained in chapter Combination Rules in the description for Number of resulting loadcases
- manually.
By setting of a tick at Maximum or Minimum it is selected, whether the maximum values, the
minimum values or both should be determined (corresponds record SUPP EXTR MAX/MIN/-
MAMI).
If for Element type - Nodes at area elements or Nodes at volume elements were defined, a
group for which the superposition should be done can be selected then at Group number by
deleting of the tick at All groups. The default is ALL for all groups.
If groups should be defined for other element types, it has to be done via Output - Startnum-
ber, Endnumber, Increment. If the result load case does not exit yet, the superposition is
done here for the elements of all groups, but only the selected elements are output then.
Furthermore the corners and the edge centres of the encasing rectangle are available at Cross
section point (see also: MAXIMA - Description for the item SELE in record SUPP):
Y+Z- Z- Y-Z-
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Y+
Y Ï Ï Ï Ï Ï
Y-
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Ï Ï Ï Ï Ï
Y+Z+ Ï Ï Ï
Z+
Ï Ï
Y-Z+
Z
Figure 4.9: Cross section points
the root from the sum of the squares of the superpositioned value is determined (corresponds
to SUPP EXTR SRSS).
and input of a combination number the factors of the first printed superposition are saved in
the new combination (corresponds to SUPP CSAV).
The full printout, however, only for the relevant superposition values occurs with a tick at Most
relevant values. It corresponds to the MAXIMA input ECHO CHCK.
The printout of the combination overview and of the list of the generated load cases occurs
with a tick at Table of loadcases (default). It corresponds to the MAXIMA input ECHO TABS
YES.
The printout of all initial load cases with their values which are necessary for the superposition
occurs with a tick at Values of used loadcases. It corresponds to the MAXIMA input ECHO
LOAD.
no output (default)
factors of actions and loadcases
extended factors of actions and factors of loadcases
additionally factors of loadcases even if zero
It corresponds to the possibilities of the MAXIMA input ECHO LOAD, FACT. If the output of
the Most relevant values (corresponds to ECHO CHCK) was selected, then these are printed
always with all factors. It is recommended to check the superposition by investigating
random samples with an extended output at Created loadcases and additionally factors
of loadcases even if zero at Output of factors!
Element Selection
The selection of single elements or nodes is done by marking of Node/Elementnumber and
Startnumber 1
Endnumber 999999999
Increment 1
Group Selection
By marking of Group a list is available with the primary and secondary groups which exist in
the system. Here it is possible to select a group for the output of the superposition results.
A group selection is not possible for nodal results. If the internal forces and moments in the
nodes at area and volume elements should be printed groupwise, the group number has to be
defined in the tab Control.
For beams or SIR cuts there is the possibility to define a beam section or a SIR cut which is
available in the database at Beam. With textbfX-Value the X value is defined as a length value
along the baem axis. With textbfFactor the X position of the beam cut is defined as a factor. A
0 describes the beginning of the beam and a 1 describes the end.
The superposition is done always for all elements, however, only the selected elements
are output.
Calculate immediately
Superpositions can be inserted or deleted here. The superpositions are deleted and reinitialized according to
with Delete all and reinitialize. It is to be noted that superpositions which are individually
• Single load cases which are used for the intermediate superposition have to be available
without an assignment to an action.
• The action to that one the result load cases of the intermediate superposition are assigned
has to be defined.
The information about the single load cases has to be defined either in SOFiPLUS (load case
manager) or with the program SOFiLOAD.
At first all combinations are input in the task Define Combinations. The combination for
the intermediate superposition can be defined here also at last (e.g. if using the defaults
from the INI file). The combination for the intermediate superposition is mostly a standard
superposition without use of actions ⇒ See chapter: Superpositions without Actions. Here
it is to be noted that for Type of resulting loadcases the action which the result loads are
supposed to appertain to has to be indicated. It is recommended to assign the result load
numbers manually or via semi-automatic, because double load case numbers can be possible
in connection with other combinations, if using fully automatic.
At the ’normal’ combinations the action with the result load cases is defined as follows:
If using the default combinations from the INI file with an in the INI file preset action the alloca-
tion is done automatically.
Figure 4.12: Combination rules with the combination for the intermediate superposition
After the calculation of the single load cases the intermediate superposition can occur then with
a first task Superpositioning. The preset superpositions of the ’normal’ combinations have to
be switched off here ⇒ remove the green ticks in the tree of the left-hand side. All superposition
values which are necessary for the following superpositions of the ’normal’ combinations have
to be defined here for the combination of the intermediate superposition, e.g. displacements
for a superposition for serviceability limit state, internal forces and moments as well as support
reactions for superposition for ultimate limit state.
Figure 4.13: Superpositions of the intermediate superposition only here superpositions for the
combination 1
For the last superposition step a second task Superpositioning has to be inserted in the SSD.
The superpositions for the ’normal’ combinations of the serviceability and ultimate limit state
are done here.
Figure 4.14: Superpositions for the serviceability and ultimate limit state here superpositions for
the combination 100 - 110
5 Output Description
The result output of the superposition is dependent on the definition of the record ECHO.
1st line:
Act Type (designation) of the action
Part Partition of the action
(item PART record ACT)
γ-u Partial safety factor for unfavourable effect
γ-f Partial safety factor for favourable effect
γ-a Partial safety factor accidental
ψ-0 Combination coefficient variable action (rare)
ψ-1 Combination coefficient frequent values
ψ-2 Combination coefficient quasi-permanent values
ψ-1’ Combination coefficient infrequent values
2nd line:
LC Load case number
Fact Factor with which the internal forces
were multiplied
Type Type of load case (superposition of the load
cases within the action)
PERM - permanent load grouped inactions
PERC - permanent load grouped in load cases
COND - conditional load
AGNo - exclusive load permanent
ANo - exclusive load
UNSI - unsigned conditional load
XNo - exclusive load with changing sign
F - additional contributing load case
If a load case has another partial safety factor or combination coefficient than the one which
was assigned for the action, then this factor or coefficient is printed in a second line of the
corresponding load case.
If the superposition is done with an explicit combination (COMB EXTR EXPL and record ADD),
the explicit defined formula is printed at the used superposition equation. The table Loadcase
Selection and Actions reads here as follow:
1st line:
Act Type (designation) of the action
Part Partition to which the action belongs
for input with action groups
item PART record ACT SOFiLOAD
for input with explicit action
EX - explicit defined
fac-u Factor unfavourable or factor unfavourable
for accomanying variable action
fac-f Factor favourable or factor favourable for
accomanying variable action
facu1 Factor unfavourable for 1st leading variable action
facf1 Factor favourable for 1st leading variable action
facu2 Factor unfavourable for 2nd leading variable action
facf2 Factor favourable for 2nd leading variable action
facu3 Factor unfavourable for 3rd leading variable action
facf3 Factor favourable for 3rd leading variable action
2nd line:
LC Load case number
Fact Factor with which the internal forces
were multiplied
Type Type of load case (superposition of the load
cases within the action)
PERM - permanent load grouped inactions
PERC - permanent load grouped in load cases
COND - conditional load
AGNo - exclusive load permanent
ANo - exclusive load
UNSI - unsigned conditional load
XNo - exclusive load with changing sign
Generated loadcases
The designation of the superposition load case is printed here. It is dependent on the used
combination rule and the superposition variable. The first part (9 characters) describes the
used combination rule and is printed also in the following output tables. The following outputs
are possible:
Example: The designation for the accidental design combination of the beam normal force N
is MAXA-N for the maximum value and MINA-N for the minimum value.
An information about the element type is printed in the second part (5 characters). Following
outputs are here possible:
The third part (18 characters) corresponds to the input TITL in record SUPP or to input Name
in the registry card Superposition Commands in WinMAX. For superposition with an objective
function then the objective function is printed here.
The summary of the initial load cases and their corresponding resultant factors is printed at the
end of this output:
Forces in nodes
Group
Node Node number
LC No. Number of the load case
Designation Designation of the load case
m-xx, m-yy, m-xy Bending / torsional moments of the plate
v-x, v-y Shear forces of the plate
Elastic bedding
Forces in nodes
Group
Node Node number
LC No. Number of the load case
Designation Designation of the load case
n-xx, n-yy, n-xy Internal forces of the membranes
m-xx, m-yy, m-xy Bending/torsional moments for the shells
v-x, v-y Shear forces for the shells
Stresses in nodes
Groupnumber
Node Node number
LC No. Number of the load case
Designation Designation of the load case
sigma-x, sigma-y,
tau-xy, sigma-z Stresses
Stresses in 3D elements
Groupnumber
Node Node number
LC No. Number of the load case
Designation Designation of the load case
sig-x, sig-y, sig-z Stresses
tau-xy, tau-xz, tau-yz Shear stresses
For the superposition of the normal stress and shear stress in a cross section point, which was
defined in record SUPP with SELE, the decisive internal forces and moments (forces in beam
elements) are printed.
For the superposition of the normal stress and shear stress in a cross section point, which was
defined in record SUPP with SELE, the decisive internal forces and moments (forces in beam
elements) are printed.
Nodal displacements
5.13 Springs
Tendon - stresses
Result-Sets
Number Number
Storey Displacements