Shelldesign_UM

ShellDesign
DESIGN TOOL FOR REINFORCED

CONCRETE SHELL STRUCTURES
USER MANUAL - revision 7.0

From ShellDesign version 6.2.0
ShellDesign is owned, developed and
supported by Dr.techn.Olav Olsen AS.
No liability for consequential damages:

In no event shall Dr.techn.Olav Olsen AS or its suppliers be liable for any damages whatsoever
(including, without limitation, damages for loss of business profits, business interruption, loss
of business information, or other pecuniary loss) arising out of the use of or inability to use
this Dr.techn.Olav Olsen AS product, even if Dr.techn.Olav Olsen AS has been advised of
possibility of such damages.
Prepared by: Dr.techn. Olav Olsen

Date: 06.10.2022
Revision: 7.0
Number of pages: 237
E-mail support: software.support@DNV.com
E-mail sales: digital@DNV.com
SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 2 of 237

3
TABLE OF CONTENTS
1 INTRODUCTION ............................................................ 12
1.1 Program summary ......................................................................................12
1.2 Program limitations .....................................................................................13
1.3 License and Support....................................................................................13
2 SETUP FOR SHELLDESIGN EXECUTION ............................ 14

2.1 Input files ..................................................................................................14
2.2 Installation and execution ............................................................................16
2.3 Notepad++ ................................................................................................17
2.3.1 Syntax highlighting ...................................................................................17
2.3.2 Input statement suggestions and auto complete ...........................................18
2.4 Setup for CSM with shell elements ................................................................19
3 ANALYSIS AND DESIGN INTERACTION ............................ 20

3.1 Design based on User Input .........................................................................21
3.2 Design based on the Conventional Design Method (CDM) .................................21
3.2.1 CDM - Method ..........................................................................................21
3.2.2 CDM - Global FE-model ..............................................................................23
3.2.2.1 Limitations .........................................................................................23
3.2.2.2 Supported elements ............................................................................23
3.2.2.3 FE mesh .............................................................................................25
3.2.3 CDM - Post-processing model - Concrete model ............................................26
3.2.3.1 Limitations .........................................................................................26
3.2.3.2 Creating concrete model ......................................................................27
3.2.4 CDM - Water pressure in cracks ..................................................................29
3.3 Design based on the Consistent Stiffness Method (CSM) ..................................30
3.3.1 CSM - Motivation ......................................................................................30
3.3.2 CSM - Method...........................................................................................31
3.3.3 CSM - Global FE-model ..............................................................................33
3.3.3.1 Solid models .......................................................................................33
3.3.3.2 Shell models .......................................................................................34
3.3.4 CSM - Material Properties in FE-analysis ......................................................34
3.3.4.1 Concrete ............................................................................................34
3.3.4.1.1 Bi-linear material curve for concrete in tension .....................................35
3.3.4.1.2 Non-linear material curve for concrete in tension ..................................36
3.3.4.2 Reinforcement ....................................................................................37
3.3.4.3 Prestressed reinforcement ....................................................................37

3.3.5 CSM - Water pressure in cracks ..................................................................38
4
4 DESIGN CODES AND DESIGN CALCULATIONS .................. 39

4.1 DNV-ST-C502.............................................................................................41
4.1.1 DNV - Material properties ...........................................................................41
4.1.1.1 DNV - Concrete ...................................................................................41
4.1.1.2 DNV - Reinforcement steel ...................................................................43
4.1.1.3 DNV - Prestressing steel .......................................................................43
4.1.2 DNV - ULS Design .....................................................................................44
4.1.2.1 DNV - Design for in-plane forces ...........................................................45
4.1.2.2 DNV - Design for transverse Stresses.....................................................46
4.1.2.3 DNV - Water Pressure in Cracks ............................................................48
4.1.3 DNV - ALS Design .....................................................................................49
4.1.4 DNV - SLS Design .....................................................................................49
4.1.4.1 DNV - Calculation of uncracked or cracked sections .................................49
4.1.4.2 DNV - Calculation of Crack widths .........................................................50
4.1.4.3 DNV - Calculation of Crack Depths .........................................................52
4.1.4.4 DNV - Calculation of Compression Zone .................................................52
4.1.4.5 DNV - Through thickness cracks ............................................................53
4.1.4.6 DNV - SLS - Stresses in reinforcement and concrete ................................53
4.1.5 DNV - FLS Design .....................................................................................54
4.1.5.1 DNV - Stress-Strain Relations ...............................................................54
4.1.5.2 DNV - In-Plane Stresses .......................................................................54
4.1.5.3 DNV - Design for Transverse Stresses ....................................................56
4.1.5.4 DNV - Water Pressure in Cracks ............................................................57
4.2 NS 3473 ....................................................................................................58
4.2.1 NS - Material properties .............................................................................58
4.2.1.1 NS - Concrete .....................................................................................58
4.2.1.2 NS - Reinforcement steel ......................................................................59
4.2.1.3 NS - Prestressing steel .........................................................................60
4.2.2 NS - ULS Design .......................................................................................60
4.2.2.1 NS - Design for in-plane forces .............................................................61
4.2.2.2 NS - Design for transverse Stresses .......................................................62
4.2.2.3 NS - Water Pressure in Cracks ..............................................................65
4.2.3 NS - ALS Design .......................................................................................65
4.2.4 NS - SLS Design .......................................................................................65
4.2.4.1 NS - CRW - Crack widths calculation ......................................................65
4.2.4.2 NS - Calculation of Crack Depths ...........................................................68
4.2.4.3 NS - Calculation of Compression Zone....................................................68
4.2.4.4 NS - Through thickness cracks ..............................................................69
4.2.4.5 NS - SLS - Stresses in reinforcement and concrete ..................................69

4.2.5 NS - FLS Design........................................................................................70
5
4.2.5.1 NS - Stress-Strain Relations .................................................................70
4.2.5.2 NS - In-Plane Stresses .........................................................................70
4.2.5.3 NS - Design for Transverse Stresses ......................................................71
4.2.5.4 NS - Water Pressure in Cracks ..............................................................73
4.3 EuroCode 2 ................................................................................................74
4.3.1 EC2 - Material properties ...........................................................................74
4.3.1.1 EC2 - Concrete....................................................................................74
4.3.1.2 EC2 - Reinforcement steel ....................................................................75
4.3.1.3 EC2 – prestressing steel .......................................................................75
4.3.2 EC2 - ULS Design......................................................................................76
4.3.2.1 EC2 - Design for in-plane forces ............................................................77
4.3.2.2 EC2 - Design for transverse Stresses .....................................................78
4.3.2.3 EC2 - Water Pressure in Cracks .............................................................80
4.3.3 EC2 - ALS Design ......................................................................................81
4.3.4 EC2 - SLS Design ......................................................................................81
4.3.4.1 EC2 - Calculation of uncracked or cracked sections ..................................81
4.3.4.2 EC2 - CRW – calculation of crack widths – crack control ...........................81
4.3.5 EC2 - FLS Design ......................................................................................83
4.4 Modified Compression Field Theory (MCFT) ....................................................84
4.4.1 MCFT - Method description .........................................................................84
4.4.2 MCFT - Experimental verification and history ................................................87
4.4.3 MCFT - Limitations ....................................................................................88
5 FEATURES IN SHELLDESIGN........................................... 89
5.1 Shell Sections – Design Sections...................................................................89
5.2 Shell Sectional Stress Resultants – Section Forces ..........................................91
5.3 Strain components in a Shell Section ............................................................92
5.4 Node Displacements....................................................................................93
5.5 Load Cases ................................................................................................93
5.5.1 OLC – Original Load Case ...........................................................................93
5.5.2 ELC – Equilibrium Load Case – Definition of new support system ....................94
5.5.3 ILC – Input Load Case ...............................................................................96
5.5.4 PLC – Prestressing Tendon Load Case ..........................................................96
5.5.5 BAS – Basic Combination Load Case ............................................................97
5.6 Limit States ...............................................................................................98
5.7 Concrete and Reinforcement ........................................................................98
5.7.1 Concrete ..................................................................................................98
5.7.2 Reinforcement ..........................................................................................98
5.7.3 Shear reinforcement................................................................................ 101
5.7.4 Prestressing/tendon reinforcement types ................................................... 101

5.8 OLC-Files and DEC Files ............................................................................. 102
6
5.8.1 OLC-Files ............................................................................................... 102
5.8.2 DEC-files................................................................................................ 103
5.8.3 Scratch files ........................................................................................... 103
5.9 Result presentation ................................................................................... 105
5.9.1 Results in Tables ..................................................................................... 105
5.9.2 Graphical Results .................................................................................... 105
6 DESCRIPTION OF INPUT STATEMENTS........................... 108

6.1 Input File ................................................................................................. 108
6.2 Syntax Explanation ................................................................................... 108
6.3 Run Statements........................................................................................ 109
6.3.1 EXECD - order ShellDesign execution of current input data .......................... 109
6.3.2 NONLI – order CSM analysis to be carried out ............................................ 110
6.3.3 OLCFI – create, merge or read OLC files with FE-analysis results .................. 111
6.3.4 DECFI - create, merge or read DEC files with design results ......................... 112
6.3.5 DESEC - define or modify design section geometry ..................................... 113
6.3.6 RFILE - read Sestra FE analysis input file and/or FE analysis result file .......... 114
6.3.7 MFILE - attach a substructure M-file to CSM analysis ................................... 115
6.3.8 ABAFI - read ABAQUS result file ............................................................... 116
6.4 Material Properties Statements ................................................................... 117
6.4.1 CMPOS - define concrete material according to DNV-ST-C502 ...................... 117
6.4.2 CMPNS - define concrete material according to NS 3473 .............................. 119
6.4.3 CMPEC - define concrete material according to NS-EN 1992-1-1 ................... 121
6.4.4 CMPGM - define concrete material according to MCFT .................................. 122
6.4.5 CMPNL - define concrete material in CSM (non-linear) analysis ..................... 124
6.4.6 RMPOS – define rebar material according to DNV-ST-C502 .......................... 125
6.4.7 RMPNS – define rebar material according to NS 3473 .................................. 126
6.4.8 RMPEC – define rebar material according to NS-EN 1992-1-1 ....................... 127
6.4.9 RMPGM – define rebar material according to MCFT ...................................... 128
6.4.10 RMPNL – define rebar material in CSM (non-linear) analysis ...................... 129
6.4.11 TEMAT - define prestressing/tendon material in design ............................. 129
6.4.12 TMPNL - define prestressing/tendon material in CSM (non-linear) analysis .. 130
6.5 Design Parameter Statements .................................................................... 131
6.5.1 DEPAR - define global design parameters ................................................... 131
6.5.2 CRWOS - define crack width data according to DNV-ST-C502 ....................... 132
6.5.3 CRWNS - define crack width data according to NS 3473 ............................... 133
6.5.4 CRWEC - define crack width data according to NS-EN 1992-1-1 .................... 135
6.5.5 CRASP – define fixed crack spacing ........................................................... 135
6.5.6 TIGHT - define tightness criteria according to DNV-ST-C502 and NS 3473 ..... 136
6.5.7 FAPOS – define fatigue parameters (FLS) according to DNV-ST-C502 ............ 137

6.5.8 FAPAR – define fatigue parameters (FLS) according to NS 3473 .................... 138
7
6.5.9 WPARE - define areas with water pressure in cracks data ............................. 140
6.6 Section Statements ................................................................................... 142
6.6.1 SHSEC - create shell sections/design sections ............................................ 142
6.6.2 SHAXE – define local 1,2,3-axes for design sections .................................... 144
6.6.3 SHEXT – create extrapolated design sections.............................................. 145
6.6.4 BESEC - create beam sections and print of beam forces ............................... 148
6.6.5 LAREA - define location areas ................................................................... 150
6.6.6 SESET - define design section sets ............................................................ 150
6.7 Reinforcement Statements ......................................................................... 152
6.7.1 RETYP - define rebar layer types ............................................................... 152
6.7.2 RELOC - define rebar locations ................................................................. 153
6.7.3 RERES - define rebar area reservations ..................................................... 155
6.7.4 REFAC – define rebar area reservations, factor ........................................... 156
6.7.5 SRTYP - define shear reinforcement types .................................................. 157
6.7.6 SRLOC - define shear reinforcement location .............................................. 157
6.7.7 SRRES – define shear reinforcement reservations ....................................... 158
6.7.8 TETYP - define prestressing (tendon) layer types ........................................ 159
6.7.9 TELOC - define tendon layer data .............................................................. 160
6.7.10 TELAY – include prestressing (tendon) data generated with TenLoad .......... 161
6.8 Load Statements ...................................................................................... 162
6.8.1 LOADC – rename ordinary analysis load cases ............................................ 162
6.8.2 GRECO - define new support systems to the FE-model ................................ 163
6.8.3 LORES - define load resultants of analysis load cases .................................. 165
6.8.4 INPLC - define load case with user input forces ........................................... 166
6.8.5 BASCO - define load combinations ............................................................ 167
6.8.6 LDFAC - define location dependent load factors .......................................... 168
6.8.7 FSFAC - define factors to be used on forces and strains ............................... 169
6.8.8 STFOR - define additional forces in longitudinal reinforcement due to shear ... 172
6.8.9 WAVED - define wave (dynamic) distribution data for fatigue (FLS) ............... 173
6.9 Design Statements ................................................................................... 176
6.9.1 DECAS - define load cases to be code checked according to limit state .......... 176
6.10 Print/Status Statements ............................................................................ 178
6.10.1 LISTIN – print input file to output file for documentation ........................... 178
6.10.2 FILST - give file status for input files ...................................................... 178
6.10.3 SINST - give SIN-file status for input files ............................................... 179
6.10.4 HEADL - give text for table headings ...................................................... 179
6.10.5 PRIWF – define output .......................................................................... 180
6.10.6 TABLE - define print of results in tables................................................... 180
6.11 Plot Statements ........................................................................................ 184
6.11.1 XTFIL - define XTRACT plot ................................................................... 184

6.12 General statements................................................................................... 186
8
6.12.1 INCDF – reference to additional input file ................................................ 186
7 RESULT DESCRIPTION IN TABLES ................................. 187

7.1 Detailed Sectional Response Data – TAB=DR ............................................... 187
7.1.1 DR table output - ULS, ALS and SLS limit state ........................................... 187
7.1.2 DR table output – CRW limit state - crack widths ........................................ 191
7.1.3 DR table output – FLS limit state .............................................................. 194
7.1.3.1 Verification table – FLS limit state ....................................................... 195
7.1.4 DR table output for MCFT – ULS/ALS limit state .......................................... 197
7.2 Design Section Force Tables – TAB=XX ....................................................... 200
7.2.1 TABLE TAB=DF – Section forces for design cases ........................................ 200
7.2.2 TABLE TAB=WF – Water pressure in cracks design forces for design cases ..... 200
7.2.3 TABLE TAB=PF – Maximum and minimum section forces for design cases ...... 200
7.2.4 TABLE TAB=DP – Principial forces and moments for design cases.................. 200
7.3 Utilization Ratio Tables – UR=XX ................................................................ 201
7.3.1 TABLE UR=MAX – Summary of Max UR for all available capacities ................. 201
7.3.2 TABLE UR=CS – Summary of Max UR concrete capacity............................... 201
7.3.3 TABLE UR=RS – Summary of Max UR reinforcement layer capacity ............... 202
7.3.4 TABLE UR=RC – Summary of Min UR reinforcement layer capacity ................ 202
7.3.5 TABLE UR=CC – Summary of Max UR concrete capacity for shear compr. ...... 203
7.3.6 TABLE UR=VC – Summary of Max UR concrete capacity for shear tension ...... 203
7.3.7 TABLE UR=ST – Summary of Max UR shear reinforcement capacity .............. 203
7.3.8 TABLE UR=TS – Summary of Max UR prestressing reinforcement capacity ..... 204
7.3.9 TABLE UR=CW – Summary of Max UR for reinforcement crack widths ........... 204
7.3.10 TABLE UR=TW – Summary of Max UR for prestressing crack widths ........... 204
7.3.11 TABLE UR=CZ – Compression Zone Check .............................................. 205
7.3.12 TABLE UR=CT – Crack Width Check for Through Cracks ............................ 206
8 RESULT DESCRIPTION IN GRAPHICAL PLOTS ................. 207

8.1 Properties ................................................................................................ 208
8.1.1 Areas .................................................................................................... 208
8.1.2 Labeled Results ...................................................................................... 209
8.1.3 Thicknesses ........................................................................................... 209
8.1.4 Model Info ............................................................................................. 209
8.2 Design Case Result ................................................................................... 209
8.2.1 Sectional Forces ..................................................................................... 209
8.2.2 Principal Forces ...................................................................................... 209
8.2.3 Principal Strains ...................................................................................... 210
8.2.4 Utilization Ratios ULS, ALS and SLS limit state ............................................ 210
8.2.5 Utilization Ratios CRW limit state (crack widths and tightness) ..................... 210

8.2.5.1 CRW-F1 ........................................................................................... 211
9
8.2.5.2 CRW-F2 ........................................................................................... 211
8.2.5.3 CRW-TENDON-ID .............................................................................. 212
8.2.5.4 CZ-COMPZONE-DEPTH ....................................................................... 212
8.2.5.5 CZ-UR .............................................................................................. 213
8.2.5.6 CZ-FACE_CZ ..................................................................................... 213
8.2.5.7 CT-FACE_CT ..................................................................................... 214
8.2.5.8 CT-UR .............................................................................................. 215
8.3 Result Case – Peak Results ........................................................................ 216
8.3.1 Principal Forces ...................................................................................... 216
8.3.2 Principal Strains ...................................................................................... 216
8.3.3 Utilization Ratios ..................................................................................... 216
9 EXAMPLES OF SHELLDESIGN RUNS AND INPUT FILES ..... 217

9.1 Design based on User Input ....................................................................... 217
9.1.1 Example 1 – Common run – no DEC file saved ........................................... 218
9.1.2 Example 2 – Permanent DEC-file saved ..................................................... 220
9.1.3 Example 3 – Two Old DEC-files merged into a new file ................................ 221
9.2 Design based on the Conventional Design Method (CDM)............................... 221
9.2.1 Example 1 – no OLC-file and DEC-file saved ............................................... 222
9.2.2 Example 2 – OLC-file created and saved .................................................... 223
9.2.3 Example 3 – Old OLC-file called and no DEC-file saved ................................ 223
9.2.4 Example 4 – Old OLC-file called and DEC-file saved ..................................... 224
9.2.5 Example 5 – OLC-file and DEC-file saved ................................................... 225
9.2.6 Example 6 – Old OLC-file and DEC-file used to retrieve data ........................ 226
9.2.7 Example 7 – Old DEC-file used to retrieve data ........................................... 227
9.2.8 Example 8 – Two old DEC-files merged ...................................................... 227
9.3 Design based on the Consistent Stiffness Method (CSM) ................................ 228
9.3.1 Example 1 – Common run - No OLC-File and DEC-File Created ..................... 229
9.3.2 Example 2 – OLC-file and DEC-file saved ................................................... 230
10 REFERENCES .............................................................. 232
APPENDIX A .......................................................................... 233

TABLE OF FIGURES 10
Figure 2-1: Execution of ShellDesign in Sesam Manager ................................................................. 16

Figure 2-2: Default workspace for a new job with Sesam Manager ................................................... 16
Figure 2-3: Notepad++ «Define your language...» dialog ............................................................... 17
Figure 2-4: Notepad++ «Language» menu w/ShellDesign option ..................................................... 18
Figure 3-1: Required input to design calculations in ShellDesign ...................................................... 20
Figure 3-2: User Input design - Design flow .................................................................................. 21
Figure 3-3: CDM - Design flow based on the Conventional Design Method ......................................... 22
Figure 3-4: CDM - Limitations on element inclination in thickness direction ....................................... 23
Figure 3-5: CDM - Recommended meshing of FE-models to be post-processed in ShellDesign ............. 25
Figure 3-6: CDM - Non-perpendicular mesh not applicable for ShellDesign ........................................ 25
Figure 3-7: CDM - Perpendicular mesh applicable for ShellDesign .................................................... 26
Figure 3-8: CDM - Parts in a FE-model (D-regions) not applicable for ShellDesign .............................. 26
Figure 3-9: CDM - Definition of Parts and FS and HS numbering in a ShellDesign concrete model ........ 28
Figure 3-10: CDM - Water pressure in cracks in concrete model ...................................................... 30
Figure 3-11: CSM - The Consistent Stiffness Method - The iterative approach.................................... 31
Figure 3-12: CSM - Design flow based on the Consistent Stiffness Method ........................................ 33
Figure 3-13: CSM - Concrete compressions material curve in CSM analyses ...................................... 35
Figure 3-14: CSM - Bi-linear concrete tension material curve .......................................................... 35
Figure 3-15: CSM - Definition of effective area (red) and not effective area (grey) ............................. 36
Figure 3-16: CSM - Non-linear concrete tension material curve. a) effective b) not effective ............... 36
Figure 3-17: CSM - Reinforcement compression/tension material curve ............................................ 37
Figure 3-18: CSM - Prestressed reinforcement compression/tension material curve............................ 37
Figure 4-1: DNV-ST-C502 - Material curve in compression for normal and lightweight concrete ........... 41
Figure 4-2: DNV-ST-C502 – Linear material curve in compression for lightweight concrete ................. 42
Figure 4-3: DNV-ST-C502 - Material curve in tension/compression for reinforcement ......................... 43
Figure 4-4: DNV-ST-C502 - Material curve for prestressed reinforcement steel .................................. 44
Figure 4-5: DNV-ST-C502 - The in-plane forces and corresponding strain components ....................... 45
Figure 4-6: NS 3473 - Material curve in compression for normal weight concrete ............................... 58
Figure 4-7: NS 3473 - Material curve in compression for lightweight concrete ................................... 58
Figure 4-8: NS 3473 - Material curve in tension/compression for reinforcement steel ......................... 59
Figure 4-9: NS 3473 - Material curve for prestressed reinforcement steel ......................................... 60
Figure 4-10: NS 3473 - The in-plane forces and corresponding strains in a shell section ..................... 61
Figure 4-11: EC2 - Material curve in compression for normal weight concrete ................................... 74
Figure 4-12: EC2 - Material curve in tension/compression for reinforcement steel .............................. 75
Figure 4-13: EC2 - Material curve for prestressed reinforcement steel .............................................. 76
Figure 4-14: EC2 - The in-plane forces and corresponding strains in a shell section............................ 77
Figure 4-15: MCFT - Cracking along a reinforcement bar ................................................................ 86
Figure 4-16: MCFT - Tension stiffening in concrete ......................................................................... 86
Figure 4-17: MCFT - Average stress-strain curve of concrete ........................................................... 86
Figure 4-18: MCFT - Average vs. crack stresses............................................................................. 87
Figure 5-1: Shell Sections/Design Sections in a FE model ............................................................... 89
Figure 5-2: Concrete geometry in a shell section ........................................................................... 90
Figure 5-3: Section Forces in a shell section. The element is infinitesimal ......................................... 91
Figure 5-4: Strain components in a shell section ............................................................................ 92
Figure 5-5: Relationship between section forces, local axes, and reinforcement direction .................... 99
Figure 5-6 Define system environment variable TMP .................................................................... 104
Figure 5-7: Graphical Plot interface for ShellDesign results in DNV’s Xtract ..................................... 106
Figure 7-1: Mohr’s circle for calculation of principal strains and directions in ShellDesign .................. 189
Figure 7-2: Mohr’s circle for calculation of crack directions in ShellDesign ....................................... 193
Figure 8-1 Graphical Plots - Utilization Ratio scale ........................................................................ 207
Figure 8-2 Graphical Plots - Properties........................................................................................ 208
Figure 8-3 Graphical Plots - Properties - Areas ............................................................................ 208
Figure 8-4 Graphical Plots - Result Case – Design Case Result ....................................................... 209
Figure 8-5 Graphical Plots - Design Case Results - Utilization Ratios - CRW limit state ...................... 210
Figure 8-6 Graphical Plots - CRW-F1 Design Case Result ............................................................... 211
Figure 8-7 Graphical Plots - CRW-F2 Design Case Result ............................................................... 211

Figure 8-8 Graphical Plots - CRW-TENDON-ID Design Case Result ................................................. 212
Figure 8-9 Graphical Plots - CZ-COMPZONE-DEPTH Design Case Result .......................................... 212 11
Figure 8-10 Graphical Plots - CZ-UR Design Case Result ............................................................... 213
Figure 8-11 Graphical Plots - CZ-FACE_CZ Design Case Result ...................................................... 213
Figure 8-12 Graphical Plots - CT-FACE_CT Design Case Result....................................................... 214
Figure 8-13 Graphical Plots - CT-UR Design Case Result ............................................................... 215
Figure 8-14 Graphical Plots - Result Case – Peak Results .............................................................. 216

1 INTRODUCTION 12
ShellDesign is a design tool and post processor for reinforced concrete structures subjected to
stresses in and out of plane. ShellDesign is owned, developed and supported by Dr.techn. Olav
Olsen AS (OO).
The program is based on extensive development and project experience accumulated through
a large number of offshore concrete projects over the years and is an extension of the design
tool CONCODE. ShellDesign has since 2006 been used on several projects and has shown to
be applicable for small and large concrete structures, both offshore and inshore.
This User Manual is applicable from ShellDesign version 6.2.0. A ShellDesign Theory Manual
including verification is also available [1].
1.1 Program summary

ShellDesign performs design calculations (ULS, ALS, SLS, FLS code checks) based on geometry,
forces, amounts of reinforcement and material properties in predefined sections. Section
geometry and forces can either be user defined or results from a finite element analysis where
the model has been modelled with shell or solid elements. The nonlinear material behaviour
of reinforced concrete is included in the sectional design. The reinforcement amount is usually
user defined, but ShellDesign can also calculate the necessary reinforcement.
The implemented design codes are:
- DNV-ST-C502 Offshore Concrete Structures [2]. See Section 4.1

- NS 3473.E Concrete structures - Design and detailing rules 6th edition [3]. See
Section 4.2
- NS-EN 1992-1-1:2004+NA:2008: Design of Concrete Structures - General Rules and
Rules for Buildings (Eurocode 2) [4]. See Section 4.3. FLS is not yet included for EC2,
but will be implemented based upon request
The results are presented in tables and in 3D graphics (using Xtract), in the form of utilization
ratios of concrete and reinforcement, shear capacities, crack widths and other relevant design
requirements. Results such as geometry, forces and node displacement can also be presented.
Note that a detailed description of the results printed in tables, is found in Section 7.
The common practice is to use the Conventional Design Method (CDM) where the design
calculations are based on results from linear elastic structural FE analyses. This allows for use
of the principle of superposition, which is convenient when there are a lot of loads that must
be combined to several load combinations. The design calculations accounts for the nonlinear
behaviour of reinforced concrete due to cracking etc. when establishing the response of the
cross-section.
ShellDesign has also the capability to include the non-linear material behaviour of reinforced
concrete into the structural FE analysis (nonlinear FE-analysis). The method is based on an
iterative analysis/design process in interaction with FEM-analysis and is applicable for FE-
models with solid and shell elements. The method is named the Consistent Stiffness Method
(CSM). See Section 3.3.4 for more information about CSM analyses with ShellDesign.

“The Modified Compression Field Theory (MCFT)” [5] is also included in ShellDesign. MCFT
13
includes a full 3-axial material model in the program and enables a more consistent and
rational design for shear where the shortcomings in the simplified design rules for transverse
shear in the design codes are eliminated. See Section 4.5 for more information about design
with MCFT in ShellDesign.
Main ShellDesign tasks are in general:

▪ Combine load cases to simulate real load situations
▪ Perform design calculations (code checks) based on CDM or CSM
▪ Produce tables and plots for verification and documentation
Additional results such as beam section forces are also available.
1.2 Program limitations

ShellDesign is based on plate- and shell theory and only applicable for design of part of
structures where the in-plane dimensions is much larger than the out of plane dimension. Thus,
application to volumetric structures and beams may not be appropriate if criteria for this theory
is not met. However, both shell FE models and solid FE models may be used, or a combination.
See Section 3 for detailed description of application and limitations.
Note that the maximum number of characters in a single line in the input file to ShellDesign
cannot exceed 164 characters. Characters from 165 will not be read by ShellDesign and
without any error messages.
1.3 License and Support

License and support are managed by DNV. All questions regarding license fees, support etc.
should be sent to software.support@dnv.com.
Note that CSM and MCFT are special developed features and are not included in the basic
license of ShellDesign.
If there are questions, requests or errors found in the program, please contact Support/Help
Desk software.support@dnv.com.

2 SETUP FOR SHELLDESIGN EXECUTION 14
2.1 Input files

The basic input to ShellDesign is text-based file(s) with the ending .inp. These files are referred
to as input files.
A ShellDesign input file consists of data and commands. Inputs are given in the form of input
lines with alphanumerical data. All input lines start with a code word, termed “input statement”,
which identifies what sort of data the line contains. One or many sets of variables, termed
“parameters”, are associated with each input statement. Each input statement and its
corresponding parameters are described in Section 6.
Note: The maximum number of characters in a single line in the input file cannot exceed 164.
Characters from 165 will not be read by ShellDesign and without any error messages.
All input data to ShellDesign should be kept on a main input file. Additional input files may be
referenced from the main input file by use of the incdf command in the main input file followed
by the path to the additional file and name. Note that there cannot be spaces in the path name
to where additional input files are located.
Example:
incdf Global_Input_files\Material-properties\CMPNS.inp
The main input file includes typically additional input files to make the main input file easy to
follow, especially for large projects where there will be a lot of different input statements and
several input lines. Although the input statements can be sorted randomly in ShellDesign, it is
recommended to sort the input statements in a proper way. An example of a typical main input
file for a larger project is shown on the next page.
All files included with “incdf” in the main input file are located on typically the project server.
The global input files are files that different project members have the responsibility to make
sure is in accordance with the correct project data input etc. One recommended way of an
arrangement of global input files on a project server is shown below. The ShellDesign output
file prints the status of all files included, hence it is easy to see the versions of the files used
in the design run.
% --------------------------------------------------------------------------------------
FILST NAME=RETYP VERS=2.1 DATE=12.02.2019 RESP=BESNY
%----------------------------- Change log --------------------------------------------
% Version: Release Date: Resp: Changes: Checked:
% 1.0 03.10.2012 BSN File created
% 2.0 22.01.2013 BSN Changes due to verification
% 2.1 12.02.2013 BSN Added types
% --------------------------------------------------------------------------------------

% --------------------------------------------------------------------------------------
HEADL PROJECT 15
HEADL PART
HEADL ULS DESIGN
% --------------------------------------------------------------------------------------
% Read OLC-file:
OLCFI OF=..\GLOBAL-INPUT-FILES\OLC-FILES\SHAFT-ALL.OLC
% --------------------------------------------------------------------------------------
% Part to be designed:
DESEC PA=SHAFT HS=155-209
% --------------------------------------------------------------------------------------
% Load Resultants from GFEA:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\LOAD-COMBINATIONS\LORES-R400.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\LOAD-COMBINATIONS\LORES-R500.inp
% --------------------------------------------------------------------------------------
% Load Combinations and ldfac:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\LOAD-COMBINATIONS\LoadCombinations.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\LOAD-COMBINATIONS\LDFAC.inp
% --------------------------------------------------------------------------------------
% Material properties
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\MATERIAL-PROPERTIES\CMPNS.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\MATERIAL-PROPERTIES\RMPNS.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\MATERIAL-PROPERTIES\TEMAT.inp
% --------------------------------------------------------------------------------------
% Reinforcement types:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\REINFORCEMENT-TYPES\RETYP.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\REINFORCEMENT-TYPES\SRTYP.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\REINFORCEMENT-TYPES\TETYP.inp
% --------------------------------------------------------------------------------------
% Reinforcement location:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\REINFORCEMENT-LOCATIONS\RELOC-SHAFT.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\REINFORCEMENT-LOCATIONS\SRLOC-SHAFT.inp
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\REINFORCEMENT-LOCATIONS\TELOC-SHAFT.inp
% -------------------------------------------------------------------------------------
% Tolerances for concrete thickness and cover:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\TOLERANCES\TOLERANCES.inp
% -------------------------------------------------------------------------------------
% Water pressure in cracks:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\WP-IN-CRACKS\WPARE-ULS.INP
% --------------------------------------------------------------------------------------
% Design Combination
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\LOAD-COMBINATIONS\DesignComb-ULS.inp
% --------------------------------------------------------------------------------------
% Design Cases:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\DESIGN-CASES\DECAS-TOS-ULS-ALL.inp
% DECAS DWP=4 LS=ULS PHA=45 BAS=83410:A
% -------------------------------------------------------------------------------------
% Tables:
TABLE UR=MAX FM=
TABLE UR=CS FA=ALL TV=1.01
TABLE UR=RS RL=ALL TV=1.01
TABLE UR=ST TV=1.01
% -------------------------------------------------------------------------------------
% Design parameters:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\DESIGN-PARAMETERS\DEPAR.inp
% -------------------------------------------------------------------------------------
% Xtract plot file:
XTFIL FN=PART-ULS PA=SHAFT PV=
% -------------------------------------------------------------------------------------
% Execution mode:
EXECD DM=V
% --------------------------------------------------------------------------------------

2.2 Installation and execution 16
ShellDesign is installed via the InstallShield Wizard. This is started by double clicking on
setup.exe in the distribution from DNV. The license is managed through DNVs license server
FLEXlm. ShellDesign is run through Sesam Manager as illustrated in Figure 2-1 below. The
general application must be used.
Figure 2-1: Execution of ShellDesign in Sesam Manager
The default workspace is set up as shown in Figure 2-2. The top level inp-file referenced in
Figure 2-1, must be placed in the folder “ShellDesign” (this is the name given in the box
indicated by the number 3 above). The resulting text output file (out-file) and graphical result
file (vft-file) will be placed in this folder as well. It is a recommended practice to put SIN- and
FEM-files in the folder “_repository” and reference this by “PRE=..\_repository” in the RFILE-
statement, especially for CSM.
Figure 2-2: Default workspace for a new job with Sesam Manager
The execution of ShellDesign could also be done with a BAT-file with the following context:
"C:\Program Files\DNV\ShellDesign V6.1-01\Bin\SDC.exe" analysis.inp. Here the path must
be updated to the correct location and the name of the inp-file should also be modified to the
correct filename. I no inp-file is given, ShellDesign will first search for sdc.inp and if not found,
ask for the name of the file in the command window. The BAT-file should be placed in the
same folder as the top level inp-file.

2.3 Notepad++ 17
The input to ShellDesign is text based commends. For ease of use with Notepad++, please
follow the below instructions in order to get syntax highlighting and autocomplete.
2.3.1 Syntax highlighting
A.1 Copy the content of Appendix A into an empty text file (using e.g. Notepad) and save
as «SHELLDESIGN_usrlan.xml» somewhere on your computer. Skip this step if
«SHELLDESIGN_usrlan.xml» has already been provided for you.
A.2 Install and run Notepad++.
A.3 From the «Language» menu, choose «Define your language…».
A.4 In the «Define your language…» dialog, click «Import» and point to
«SHELLDESIGN_usrlan.xml». Click «OK» and make sure you get the «Import
successful» message. See figure below.
Figure 2-3: Notepad++ «Define your language...» dialog
A.5 Restart Notepad++ and select «SHELLDESIGN» which should now have appeared
toward the bottom of the «Language» menu. Refer to below.

18
Figure 2-4: Notepad++ «Language» menu w/ShellDesign option
A.6 ShellDesign syntax highlighting should now be enabled. «SHELLDESIGN_usrlan.xml» is

no longer needed and may be deleted.
2.3.2 Input statement suggestions and auto complete
C.1 Make sure you have completed steps A.1 through A.6 above and that Notepad++ is not
running.
C.2 Copy the content of Appendix A into an empty text file (e.g. using Notepad) and save
the file in the «…\Notepad++\plugins\APIs»-folder as «SHELLDESIGN.xml». This folder
is located in the directory where Notepad++ has been installed. The full path is usually
«C:\Program Files (x86)\Notepad++\plugins\APIs». If «SHELLDESIGN.xml» has
already been provided for you, simply copy it to the above path.
C.3 Restart Notepad++ and make sure you have selected SHELLDESIGN from the
«Language» menu (refer to point A.5).

2.4 Setup for CSM with shell elements 19
When CSM analysis is carried out for FE-models with shell elements, the FEM- and SIN-file is
updated in each iteration until convergence. See Section 3.3 for detailed description of CSM
analyses. If the FEM-and SIN-files are put directly in the same folder containing the top level
inp-file (the folder “ShellDesign” in the default folder structure form Sesam Manager described
above), the analysis cannot be run more than one time without updating these files. It is
therefore recommended to put these files in a subfolder as described in Section 2.2 above.
SESTRA.inp is an input file containing the Analysis Control Data and must be prepared in
advance. This file must be present in the folder of the top level inp-file. An example can be
seen in the example 3 in the doc folder of the installation (by default saved in C:\Program
Files\DNV\ShellDesign Vx.x-xx\doc\).
SESTRA.exe must also be located on the computer (by default saved in C:\Program
Files\DNV\Sestra Vx.x-xx\bin\) This path can be changed in the NONLI statement with the
SPA= input.
All Input Interface Files (T-files) for each superelement must be included in the ShellDesign
execution. There will be one Input Interface File for each superelement. The file names follow
a predefined name convention in order to be found by Sestra. The names are composed of a
letter T, the superelement number and the file extension FEM; Tn.FEM.
All Loads Interface Files (L-Files) must be included in the execution as well. Loads Interface
Files have the same naming convention as the Input Interface Files, with the T replaced by an
L.
A Result Interface File (R-File) must also be involved. The Results Interface File is the result
file from Sestra. The file will be Rn.SIN where n is the superelement number.
The Sestra Print File will appear as .LIS.

3 ANALYSIS AND DESIGN INTERACTION 20
ShellDesign performs design calculations (code checks) based on section geometry, section
forces, amount of reinforcement and material properties.
The reinforcement amounts and material properties are fetched from user input only. However,
the section geometry and section forces may be fetched from either user input or results of a
finite element analysis (or a combination of both), The results from a finite element analysis
are either fetched from the Conventional Design Method (CDM) or the Consistent Stiffness
Method (CSM). See Figure 3-1 below. The different methods to carry out design calculations
are hence:
1. Design based on User Input. See Section 3.1

2. Design based on the Conventional Design Method (CDM). See Section 3.2
3. Design based on the Consistent Stiffness Method (CSM). See Section 3.3
Section
Geometry
Section
Forces
FEM
User Input
Result File
Reinforcement
amount
Material
properties
Figure 3-1: Required input to design calculations in ShellDesign
The implemented design codes are:
• DNV-ST-C502 Offshore Concrete Structures [2]

• NS 3473.E Concrete structures - Design and detailing rules 6th edition [3]
• NS-EN 1992-1-1:2004+NA:2008: Design of Concrete Structures - General Rules and Rules for
Buildings (Eurocode 2) [4]
Detailed description of how the different design codes are implemented in ShellDesign are
found in Section 4.

3.1 Design based on User Input 21
The design calculations will be executed based on user input only. Section geometry, section
forces, reinforcement amounts and material properties are hence defined by the user. Non-
linear sectional design due to the non-linear material behaviour of reinforced concrete is
performed based on the given input.
The design flow when ShellDesign reads user input only is shown in Figure 3-2 below. Note
that graphical plots are not available for this type of run as element data from a FE-model is
not available.
Input File
ShellDesign
Results in
Tables
Figure 3-2: User Input design - Design flow
3.2 Design based on the Conventional Design Method (CDM)

The Conventional Design Method (CDM) is design based on results from a linear elastic
structural FE analysis. This allows for use of the principle of superposition, which is convenient
when there are a lot of loads that must be combined to several load combinations. The design
calculations accounts for the nonlinear behaviour of reinforced concrete due to cracking etc.
when establishing the response of the cross-section.
3.2.1 CDM - Method
The design calculations will be executed based on a result file from a FE analysis. Structural
geometry, stresses and node displacements are directly extracted from the result file and input
to ShellDesign defines the link between the elements in the FE analysis and the shell sections.
See Section 5.1 for description of shell sections.
ShellDesign reads FE results from:

▪ DNV’s structural analysis program SESTRA [6]
▪ ABAQUS
The design flow when ShellDesign reads results from a FE analysis is shown in Figure 3-3
below. Results from the FE analysis can also be stored in OLC-files and results from the design

calculation can be stored in design files (DEC-files) generated with ShellDesign. See Section
22
5.8 for description of OLC- and DEC-files.
FEM OLC File

Result File Design File
Input File
Graphical
ShellDesign
Module
OLC File
Design File
Results in Plot File Results in

Tables Plots
Figure 3-3: CDM - Design flow based on the Conventional Design Method
The FE-model may consist of curved shells, slabs and walls as well as beams. The FE-model
can comprise any type and combination of elements and the structure may be a combination
of steel and concrete. However, ShellDesign will only create a post-processing model of the
elements defined with the SHSEC statement. Se sections below for supported elements and
recommendations when creating the ShellDesign concrete model.

3.2.2 CDM - Global FE-model
23
3.2.2.1 Limitations
Quasi static and time domain analysis

ShellDesign is tested and verified for Static analysis in Sestra. ShellDesign is not verified Quasi
static and time domain analysis.
Load history file (Sn.FEM) from Wadam

Sn.FEM file containing analysis control data from hydrodynamic programs (Wadam & Wasim)
cannot be included in the Sestra analysis if ShellDesign is used as post-processor.
Element inclination in thickness direction

ShellDesign is based on plate and shell theory and is only applicable for design of sections with
moderate variations of the element thickness. It is recommended to only use ShellDesign for
design of sections where the degree of slope, β, is less than 15 degrees. See Figure 3-4 below.
Care must be taken for design of elements subjected to more extreme slopes where the errors
due to the design assumption are no longer negligible. For large slopes, D-region design of
such discontinuous sections is required, see Section 3.2.3.1, but the stiffness in the shell
sections can be used to update the CSM analyses with correct stiffness in the FE analysis.
Figure 3-4: CDM - Limitations on element inclination in thickness direction
3.2.2.2 Supported elements

The global FE-model can consist of any type of element, but the ShellDesign concrete model
supports only the element types listed below when the concrete post-processing model is
established for SESAM or ABAQUS models.

SESAM
24
ShellDesign supports these types of elements from the DNV`s SESAM element library when
ShellDesign reads results from a linear FE-analysis:
Shell elements:
• 8 nodes shell elements (SCQS)
• 6 nodes shell elements (SCTS)
Solid elements:
• 20 nodes isoparametric hexahedron solid element solid elements (IHEX). (Maximum
10 elements in the thickness direction)
• 15 nodes isoparametric triangular prism solid element (IPRI) (Maximum 10 elements
in the thickness direction.
It is however in general recommended to avoid triangular elements for those elements that
should be post-processed in ShellDesign. The generation of the ShellDesign concrete model
for models with triangular elements will also be more time consuming to create, as these
elements must be manually defined.
ShellDesign is tested and verified for Static analysis in Sestra, however it is not verified for
Quasi static and time domain analysis
Sn.FEM file containing analysis control data from hydrodynamic programs (Wadam & Wasim)
cannot be included in the Sestra analysis if ShellDesign is used as post-processor.
ABAQUS
ShellDesign supports these types of elements from the ABAQUS element library. The element
types are:
• 8 nodes thick shell elements, reduced integration (S8R)
• 20 nodes quadratic brick, reduced integration (C3D20R)
Triangular elements are not supported.
The following output variable must be present in an analysis using shell elements (S8R) in
ABAQUS:
- Field value element output: Coord, SF, SM and STH
- Field value node output: U
The Simpsons integration rule should also be used when integrating over the thickness of the
shell.
For a solid element model (C3D20R) in ABAQUS it is enough to include the following output:
- Field value element output: Coord and S
- Field value node output: U
ShellDesign supports several load combinations if a static linear perturbation analysis is

performed for both Sestra and ABAQUS analyses. However, ShellDesign will for all other
analysis types (static general etc.) that can be performed with ABAQUS, only import analysis
results for the last frame of the last step in the ABAQUS analysis.

3.2.2.3 FE mesh
25
It is recommended to have as regular mesh as possible for the elements that will be included
in the ShellDesign concrete model described in Section 3.2.3. Examples of recommended
meshing are shown in Figure 3-5.
It is also important to have the mesh in the thickness direction of the plate/shell of solid models
perpendicular to the middle section. Examples are shown in Figure 3-6 and Figure 3-7, where
the non-perpendicular mesh is not suitable for design calculations in ShellDesign. Note that
this is only relevant for the thickness direction, the in-plane mesh may have angle variations.
Figure 3-5: CDM - Recommended meshing of FE-models to be post-processed in ShellDesign
Figure 3-6: CDM - Non-perpendicular mesh not applicable for ShellDesign

26
Figure 3-7: CDM - Perpendicular mesh applicable for ShellDesign
3.2.3 CDM - Post-processing model - Concrete model
A ShellDesign post-processing model of the reinforced concrete structure is generated based

on the global FE-model (GFEM). Limitations and recommendations are shown in the following.
3.2.3.1 Limitations
The ShellDesign post-processing model should only represent elements from the GFEM
representing reinforced concrete and classified as B-regions and should not be applied to D-
Regions (Disturbed or Discontinuity). B-Regions are parts of a structure in which Bernoulli's
hypothesis of straight-line strain profiles applies. D-Regions are parts of a structure with a
complex variation in strain. D-Regions include portions near abrupt changes in geometry
(geometrical discontinuities) or concentrated forces (statical discontinuities).
Example of a FE-model where grey areas are typically D-regions and should not be included
in the ShellDesign concrete model, is shown in Figure 3-8 below.
Figure 3-8: CDM - Parts in a FE-model (D-regions) not applicable for ShellDesign
Note that ShellDesign is a very useful tool to find the loads to be applied in a D-region
evaluation. Forces can be extracted from ShellDesign to the chosen interfaces or can be
integrated up to beam sections. The D-region design can be done as hand calculations with a
truss model (strut and tie method) or by using fem software. There are softwares made
especially for D-region design. The purpose of the D-region check is to show that the D-region
can transfer the loads found in the FE-analysis. It should include bond of ended bars, forces
on the concrete from bent bars, Forces at T-heads etc.

Also note that if a CSM analysis is carried out, it might be important to update the D-regions
27
in the FE-analysis with non-linear stiffness and then include these in the ShellDesign concrete
model.
3.2.3.2 Creating concrete model

It is recommended to decide prior to creating the post-processing model, how the model should
be divided in different Parts and the FS and HS numbering system. See Section 5.1 for
description of PA, FA and HS. The terms HS and FS date back to the design of Condeep
structures with circular domes and walls. The HS is a Horizontal section corresponding to an
elevation or distance from center. The FS is a (FI)-section representing an angle counting
counterclockwise.
It is recommended that there is a logical system for Part names and FS and HS numbering,
hence it will be easy for the users to navigate in the model. Remember to also include the
extrapolated design sections when planning the system for FS and HS numbering.
For all design sections a local coordinate system must be defined. The system is called the 1,
2, 3 axis system and it is an important system because all results in ShellDesign refers to this
system. It is common practice to define the local axis system to correspond to the direction of
the reinforcement if applicable, but this is not a requirement. ShellDesign can place the
reinforcement in any direction relative to the 1, 2, 3 axes.
The 1, 2, 3 axis system and its relation to the section forces is more explained in Section.
Figure 8, Figure 9 and Figure 10 also denotes how the 1, 2, 3 axes are defined in the respective
figures.
Some examples from previous projects are shown below. Note that the gaps seen in the models,
is typically D-regions (The FE-model includes elements in these regions, but should be included
in the ShellDesign concrete model).

28
Figure 3-9: CDM - Definition of Parts and FS and HS numbering in a ShellDesign concrete
model

The input to ShellDesign can be generated when the numbering system of the design sections
29
and the local axis are determined. The related statements and an example of input to
ShellDesign are shown below.
% -------------------------------------------------------------------------------------------
% DESIGN SECTIONS FOR BASE SLAB - SHAFT BETWEEN AXIS 4 AND 7 (BS-SHAFT)
% -------------------------------------------------------------------------------------------
% Cylindrical local 1,2,3 axis with origin in center of CGS
%
% -------------------------------------------------------------------------------------------
% FILE STATUS AND VERSIONS
% -------------------------------------------------------------------------------------------
FILST NAME=BS-SHAFT-SECTIONS-axis47 VERS=8.0 DATE=14.04.2015 RESP=BESNY
%
% ----------------------------- Change log -------------------------------------------------
% 1.0 30.09.2014 BESNY File created
% 6.0 26.01.2015 BESNY Sections graphically verified FREJE
% 8.0 14.04.2015 FREJE Geometry change slab/shaft BESNY
% -------------------------------------------------------------------------------------------
% DESIGN SECTIONS
% -------------------------------------------------------------------------------------------
% Sector 7-6:
% -------------
SHSEC PA=BS-SHAFT SE=20001 EL=11216 XF=0,1,0 XH=1,0,0 FS=1-2 HS=2-25 NE=3 ET=VS
%
% -------------------------------------------------------------------------------------------
% EXTRAPOLATED SECTIONS
% -------------------------------------------------------------------------------------------
% Sector 7-6:
% -------------
% H-SECTIONS:
% Extrapolated sections towards CGS center:
SHEXT PA=BS-SHAFT EHS=1,4,3,2 FS=1-2 XP=0,0,0 XA=-1,0,0
% Extrapolated sections towards SHAFT wall:
SHEXT PA=BS-SHAFT EHS=44,41,42,43 FS=1-2 FACE=1/2
%
% -------------------------------------------------------------------------------------------
% LOCAL 1,2,3 AXIS
% -------------------------------------------------------------------------------------------
% Cylindrical with origin in center of CGS:
SHAXE PA=BS-SHAFT XC=0,0,0 XA=0,0,1 AL=90
% -------------------------------------------------------------------------------------------
3.2.4 CDM - Water pressure in cracks
When water pressure is applied as a pressure load to the FE-model, the linear FE-analysis will
not take into account that all concrete structures exposed to water (i.e. fluid pressure) will
have water pressure let into potential pores/cracks when tension in the concrete is present.
As the concrete cracks, due to the effect of loads acting on the structure, high expanding
pressures, p, will act on the cracked surfaces where the concrete is exposed to seawater. This
pressure will expand the existing crack and the effect is called “water pressure in cracks”, W p.,
and is a local removal of the beneficial pre-stressing effect caused by the water pressure. The
effect is especially important for offshore structures installed at deep water, such as the Troll

A platform shown in Figure 3-10. For these structures, the effect of water pressure in cracks
30
cannot be neglected when the capacity is evaluated, and the effect can be included by
ShellDesign in the design calculations with the WPARE statement.
The effect of Wp is included in the non-linear sectional analysis where the sectional forces due
to Wp and the sectional forces from linear elastic analyses are summarized to determine the
non-linear sectional response. Pressure, p, is introduced in all cracked design sections in
accordance with the calculated crack depth, dcr, to calculate the sectional forces from Wp, see
Figure 3-10. Thus, both a normal force and a bending moment is introduced in the section.
This is a well-known industry practice and used in the conventional design method.
Figure 3-10: CDM - Water pressure in cracks in concrete model
3.3 Design based on the Consistent Stiffness Method (CSM)

The Consistent Stiffness Method (CSM) is a practical and efficient nonlinear structural analysis
carried out with ShellDesign in corporation with a linear equation solver. CSM analyses for
shell models are carried out in corporation with DNV’s structural analysis program, Sestra [6].
CSM analyses for solid models are carried out in corporation with an internal equation solver
in ShellDesign, named OOsolver [1]. Structural geometry, stresses and node displacements
are directly extracted from the result file and input to ShellDesign defines the link between the
elements in the FE analysis and the shell sections.
3.3.1 CSM - Motivation
Structural analyses giving load effects as input to concrete design calculations are normally
based on linear elastic FE analyses, allowing use of the principle of superposition. This method
is usually called the “Conventional Design Method”. A linear elastic design approach assumes
constant element stiffness. The design calculations accounts for the nonlinear behaviour of
reinforced concrete due to cracking etc. when establishing the response of the cross-section.
The resulting state of strain is however not consistent with the strain profile from the linear FE
analysis upon which the design is based and in the general case, represents other stiffness
properties.
The motivation with CSM analyses in ShellDesign is to eliminate this inconsistency by

implementing an iterative FE analysis and concrete design procedure which ensures that the

stiffness parameters used in the linear FE model are consistent with the stiffness obtained in
31
the cracked section analysis. Hence, the method assures consistency between the assumptions
that were made as input to the FE analysis and the results of the design. The concrete
structure’s nonlinear behaviour is modelled in a more accurate way, allowing for a realistic
simulation of the actual strains and stresses throughout the structure.
The method takes thus into account the redistribution of forces resulting from change in initial
section stiffness due to cracking, reinforcement yielding, compression softening etc. The
method also assures a better handling of deformation loads and temperature effects.
Membrane load effects arising from structural restraints such as relocation of neutral axis and
arch action will be included.
3.3.2 CSM - Method
CSM builds on an iterative linear elastic procedure, in which the element stiffness matrix is
progressively refined for the non-linear material response until a specified stiffness
convergence criterion is satisfied, see Figure 3-7. The stiffness parameters calculated in the
sectional design is fed back to the FE analysis, which is rerun several times until stiffness
convergence, or the maximum number of iterations (set by the user) is reached.
The stiffness parameters are updated based on the secant stiffness for all degrees of freedom
at each design section for each iteration. The cracked section analysis is based on an element
subdivided into membrane layers (user defines how many should be used) with constant
strains and stresses.
The response to the six force components giving stresses in the plane of the member, that is
the three membrane forces and the three bending moments, is found assuming a linear strain
distribution over the thickness of the section. At convergence, the finally obtained non-linear
structural response is then compatible with the cracked section response for the actual load
level and reinforcement layout.
Figure 3-11: CSM - The Consistent Stiffness Method - The iterative approach

The design flow in Figure 3-12 below shows how ShellDesign interacts with FEM-analysis in
32
the iterative mode.
The first step is to create a new FEM-file where the shell or solid elements are replaced with
linear elastic elements reflecting the reinforced concrete stiffness. In the next step, the
stiffness's in the FEM-file are updated based on the reinforced concrete sectional analysis.
Then a linear FE-analysis is carried out. This process loops until stiffness convergence or the
maximum set number of iterations is reached.
The final sectional design and code check will be based on the FE results from last element
analysis. Note that the units in the analysis model must comply with the units in ShellDesign
when running in CSM mode i.e. meters, kilo Newtons and tonnes.
If desirable, the user may specify a subset of elements on which non-linear behaviour are
going to be accounted for in the analysis. The rest of the elements will then be run with linear
elastic stiffness. Since most of the run-time is associated with the equation solver, this will in
general probably not lead to significant reduction in run-time.
FEM-file
FEM Analysis
(SESTRA)
Sectional Stiffness
FEM
Result File
(SIN -file)
Input File
Graphical
ShellDesign Module
OLC File
Design File
Results in Plot File Results in

Tables Plots

33
Figure 3-12: CSM - Design flow based on the Consistent Stiffness Method
3.3.3 CSM - Global FE-model
ShellDesign supports CSM analyses for both solid and shell FE-models for SESAM models. CSM
analysis for ABAQUS models are not provided. The same limitations and recommendations as
for CDM, described in Section 3.2, applies also for FE models for CSM analyses in addition to
the following described limitations.
3.3.3.1 Solid models

CSM analysis with solid elements is possible because the development of a linear equation
solver for 20 and 15 nodes elements where the where the reinforced concrete stiffness is
reflected.
Supported Elements
The global FE-model can only consist of the types of elements listed below. If there are
structural parts with other elements in the FE-model, a matrix interface file (M-file) must be
created.
• 20 nodes isoparametric hexahedron solid element solid elements (IHEX). (Maximum 10 elements in
the thickness direction)
• 15 nodes isoparametric triangular prism solid element (IPRI) (Maximum 10 elements

in the thickness direction - linear stiffness only
• M-file - matrix interface file reflecting stiffness from other structural parts. Supernode
definition is also supported.
Supported loads
The CSM solid analyses supports the following loads:
• Gravitational Load (BGRAV) (real)

• Line Load (BELLO2) (real, imag)
• Surface Load (BEUSLO) (real, imag)
• Temperature (BEISTE) (real)

• Node Load (BNLOAD) (real, imag)
34
• Node Acceleration (BNACCLO) (real, imag)
Supported boundary conditions

CSM solid analyses supports only pinned boundary conditions in global axes. Springs,
connection of nodes, symmetry conditions, axis transformation etc. are not supported as
boundary conditions.
3.3.3.2 Shell models

The CSM analysis with shell elements is possible because the FE-model is updated using a
special linear elastic element type where the reinforced concrete stiffness is reflected.
Supported Elements
The global FE-model can consist of any type of element, but the FE-analysis will only be
updated with reinforced concrete stiffness for these elements
• 8 nodes shell elements (SCQS)

• 6 nodes shell elements (SCTS) - linear stiffness only
Supported loads
• Gravitational Load (BGRAV) (real)
• Line Load (BELLO2) (real, imag)
• Surface Load (BEUSLO) (real, imag)
• Temperature (BEISTE) (real)
• Node Load (BNLOAD) (real, imag)
• Node Displacements (BNDISPL) (real, imag)
• Node Acceleration (BNACCLO) (real, imag)
• Rigid body acceleration (BRIGAC) (real, imag)
Supported boundary conditions

All boundary conditions supported.
3.3.4 CSM - Material Properties in FE-analysis
The material properties for concrete, reinforcement and prestressed reinforcement used for
calculation of the stiffness in the structural FE analysis are based on the input in the CMPNL
and RMPNL and TMPNL statements respectively. Note that no material factors are included.
3.3.4.1 Concrete
The material curve for concrete in compression can either be in accordance with the design
code compression curve, as defined in Section 4, or in accordance with NS-EN 1992-1-1:2004,
Figure 3.2 as shown in Figure 3-13 below.

35
Figure 3-13: CSM - Concrete compressions material curve in CSM analyses
There are two material curves available for concrete in tension as described in sections below.
Notice should be made to the relation between stiffness used in the structural FE analysis and
in the design calculations.
The updated element stiffness fed back to the structural FE analysis, as illustrated in Figure
3-12, is based on stiffness from a non-linear sectional analysis where contribution from tensile
stresses in the concrete are included. However, the design calculations carried out after the
iterative FE analysis are performed according to the description in Section 4, where tensile
stresses in the concrete are neglected when design is based on either DNV, NS or EC2 design
codes.
3.3.4.1.1 Bi-linear material curve for concrete in tension

The bi-linear concrete tension material curve is shown in Figure 3-14 below. The tensile
strength is defined with the FTA parameter in the CMPNL statement. The E-modulus in the
material curve is defined with the ECM parameter.
Figure 3-14: CSM - Bi-linear concrete tension material curve

3.3.4.1.2 Non-linear material curve for concrete in tension
36
The definition of the non-linear concrete tension material curve is based on two different
stress-strain diagrams for the effective and not effective parts of a cross-section. The effective
area of a cross-section is defined as the area in which normal reinforcement or prestressing is
located, as seen in Figure 3-15. The extent of the effective area is defined in NS3473, Sec.
A.15.6.2.1 a), DNV-ST-C502, Sec. E.1.2.2 and EC2, Sec. 7.3.2 (3).
Figure 3-15: CSM - Definition of effective area (red) and not effective area (grey)
In the effective area of the section, the concrete will contribute with tensile capacity until
cracking occur. After cracks have appeared, the concrete tensile capacity drops to zero at the
exact location of the crack. However, the concrete tensile stress is assumed to reach its
maximum value midway between cracks, resulting in an average concrete tensile capacity of
50 % of pre-cracking capacity. As a simplification, this corresponds well with the basis for the
calculation of mean concrete tensile strain as defined in NS3473, Sec. A.15.6.2.1 b), DNV-ST-
C502, Sec. E.1.4.1 and EC2, Sec. 7.3.4 (2).
For strains larger than reinforcement yield strains, it is assumed that the concrete does not
contribute with any tensile capacity. This corresponds to the work documented in [9]. The
resulting stress-strain diagram for concrete in tension in the effective area is shown in Figure
3-16 a). In the area not defined as effective as described above, the post-cracking stress-
strain diagram is based on exponential softening described in Section 2.4.1.2 of the Guidelines
for Nonlinear Finite Element Analysis of Concrete Structures [7]. The curve can be seen in
Figure 3-16 b) and shows that the concrete tensile contribution approaches zero for large
strains.
a) b)
Figure 3-16: CSM - Non-linear concrete tension material curve. a) effective b) not effective
The definition of the ultimate strain is dependent on the ultimate fracture energy and the
equivalent length of the structure. The calculation of these properties is complicated, and a
simplified approach, assuming the ultimate strain to be twice the value of the cracking strain
is used as a basis for the stress-strain diagram implemented in ShellDesign. This is represented
by the dashed line in Figure 3-16.

The formula for the tension softening is given below.
37
where ft = maximum allowed concrete tensile stress, εcr = strain – cracking strain and εu =
ultimate strain – cracking strain.
The maximum allowed concrete tensile strength is defined with the FTM parameter in the
CMPNL statement. The E-modulus in the material curve is defined with the ECM parameter.
3.3.4.2 Reinforcement
The material curve for reinforcement is defined as shown in Figure 3-17. Hardening may also
be defined.
Figure 3-17: CSM - Reinforcement compression/tension material curve
3.3.4.3 Prestressed reinforcement

The material curve for prestressed reinforcement is defined as shown in Figure 3-18 below.
Hardening may also be defined.
Figure 3-18: CSM - Prestressed reinforcement compression/tension material curve

3.3.5 CSM - Water pressure in cracks
38
The water pressure in crack method applied for the conventional design method described in
Section 3.2.4, is only correct for statically determined structures. For statically indeterminate
structures, this method will lead to an overestimation of the Wp effect.
The CSM analyses in ShellDesign is developed to account for water pressure in cracks in the
global structural FE analysis by including the effect as node loads in the FE-analysis. The
method takes hence into account the effect of stiffness variation and boundary conditions in
the same way for both loads and Wp. This approach results in a more correct structural
response and more rational design. As far as we know, there are no other commercial software
tools available that includes the effect of water pressure in cracks in non-linear analyses of
concrete shell structures.
Water pressure in cracks in CSM analysis is defined with WAC=1 parameter in the NONLI
statement.

4 DESIGN CODES AND DESIGN 39
CALCULATIONS
ShellDesign performs design calculations based on section geometry, section forces, amount
of reinforcement and material properties. As described earlier, the reinforcement amounts and
material properties are fetched from user input only, but the section geometry and section
forces may be fetched from either user input or results of a finite element analysis (or a
combination of both).
The purpose of the design calculations is to check that the criteria set by a specific design code
is fulfilled. The implemented design codes in ShellDesign are:
1. DNV-ST-C502 Offshore Concrete Structures [2], see Section 4.2

2. NS 3473 “Concrete Structures”, 6th edition Sep. 2003. [3], see Section 4.3
3. EC2 - NS-EN 1992-1-1:2004+NA:2008. [4], see Section 4.3
In addition, there is a general method based on MCFT. Note that MCFT is not a separate design
code but an alternative to the calculations in other design codes where transverse shear design
is handled by separate empirical formulas.
Note also that DNV-ST-C502 and NS 3473 are very similar regarding the design calculations
performed in ShellDesign. The main differences are the difference between the concrete
material strengths and material factors for ULS.
The execution of design calculations is specified through the EXECD statement with the DM=V
parameter. The limit states available and the corresponding checks carried out in ShellDesign
are shown in Table 4-1 below.
Table 4-1: Limit states available and corresponding checks carried out in ShellDesign
Limit state Checks carried out
- Relates to the risk of failure or large inelastic displacement or strains of a

Ultimate - ULS failure character.
- Stresses in concrete and reinforcement, and shear capacity of the cross
section are calculated
- Relates to the risk of failure or large inelastic displacement or strains of a

failure character for events with a very low probability to occur.
Accidental - ALS
- Stresses in concrete, stresses in reinforcement and shear capacity of the
cross section are calculated
- Relates to requirements regarding concrete cracking and deflections, in

Serviceability - SLS order to ensure normal use and durability of the structure.
- Stresses in concrete and reinforcement are calculated (executed with
LS=SLS in DECAS statement). Crack widths and depths are calculated.

Limit state Checks carried out 40
- Relates to the risk of failure due to effects of repeated loading.

- Stress range tests based on a cumulative linear damage theory (miner’s
Fatigue - FLS sum) for concrete and reinforcement are calculated.
- Not applicable in ShellDesign for EC2. Will be implemented based upon
request.
ShellDesign is also able to calculate the necessary reinforcement and the corresponding
utilization ratios (UR). When calculating the necessary reinforcement, ShellDesign will search
a user-specified range of possible reinforcement arrangements. The search will go on until
either all the UR are less than 1.0 or there are no more alternatives to investigate.
The search for the NR may be organized in two ways:

▪ The NR is determined for each section independently (useful for determining suitable
areas of constant reinforcement)
▪ The NR is determined taking into account the user-defined areas for which the
reinforcement is presumed to be constant
The execution of design calculations, when necessary reinforcement should be calculated, are
specified through the EXECD statement with the DM=A parameter. The execution of design
calculations is specified through the EXECD statement. However, the most common way is to
include a general reinforcement amount and use the DM=V parameter in EXECD statement,
and then review the utilization ratios for this general reinforcement.
Note that the results from ShellDesign printed in tables are described in Section 7.

4.1 DNV-ST-C502 41
This Section describes the implementation of the DNV-ST-C502 February 2018, [2], (DNV)
design code in ShellDesign. Interpretations of rules and regulations and special features
offered by ShellDesign are explained.
ShellDesign performs design calculations based on DNV when DEPAR D_COD=OS is defined
in the ShellDesign input file.
4.1.1 DNV - Material properties
The material properties defined in ShellDesign are in accordance with DNV Sec. 4.3 and Sec.
6.3.
4.1.1.1 DNV - Concrete

The CMPOS statement is used for the concrete material input.
The normal weight concrete is implemented according to DNV Sec. 4.3.3 and Table 4-2 and
formulas given in DNV Sec. 6.3.2 and Figure 6-1. See Figure 4-6 below.
Figure 4-1: DNV-ST-C502 - Material curve in compression for normal and lightweight
concrete
Where design values are:
𝐸𝑐𝑑 = 𝛼𝑐 𝐸𝑐𝑛 /𝛾𝑐

𝑓𝑐𝑑 = 𝛼𝑐 𝑓𝑐𝑛 /𝛾𝑐
𝑓𝑡𝑑 = 𝛼𝑡 𝑓𝑡𝑛 /𝛾𝑐
Where the factor αc is 0.85 for ULS, ALS and SLS and 1.0 for FLS. αt is 1.0 for all limit states.
The factors are not changeable in the current version of ShellDesign.
The lightweight concrete is implemented according to DNV Sec. 4.3.3 and Table 4-3. The
density of the unreinforced lightweight aggregate, ρ, must be is user input in the CMPOS
statement to activate the lightweight concrete material curve. The fcn, ftk and ftn for normal
concrete is then multiplied by the factor η according to DNV Sec. 4.3.3.6 Table 4-3:
𝜌
𝜂 = 0.15 + 0.85
𝜌1

The user has the possibility to define lightweight concrete grades between LC30-LC80 and the
42
default material curve is the same as for normal weight concrete shown in Figure 4-1. The
Young’s modulus, Ecn, is reduced according to DNV Sec. 5.5.2.5 with:
𝜌
( )2
𝜌1
The limitations in DNV Sec. 4.3.3.7 are also implemented.
A linear material curve according to DNV Sec. 6.3.2.4 can also be activated with the FIG=6-3
parameter in the CMPOS statement as shown in Figure 4-2. The following interpretations is
then applied.
Figure 4-2: DNV-ST-C502 – Linear material curve in compression for lightweight concrete
The maximum strain limit is defined as:
0.7𝜌
𝜖𝑐𝑢 = 𝜖1 (0.3 + )
𝜌1
Where the ε1 = -3.5 ‰ and ρ1=2200 kg/m3.
Note that the values of all the parameters in the figures above can be specified by the user in
the CMPOS statement if default values should not be used.
In design sections where there is tension in one principal direction and compression in the
other principal direction for both normal and lightweight concrete, the concrete compression
capacity is reduced to fc2d according to in DNV Sec. 6.8.1.7:
𝑓𝑐𝑑
𝑓𝑐2𝑑 = ≤ 𝑓𝑐𝑑
0.8 − 100𝜀1
As default, the minimum concrete capacity, fc2d, will not be less than 0.3*fcd if the principal
tensile strain, ε1, is large enough. Using the TSD= parameter in the CMPOS statement, the
0.3 factor can be changed by the user. This reduction is applied for ULS, ALS and SLS (CRW),
but not for FLS.

In sections where there is compression in both principal directions, DNV does not allow the
43
concrete compression capacity to increase, except for structural members made of grout which
can have increase in compression strength up to 30%. Hence, default value in ShellDesign is
no increase. The 30% increase may be changed with the CSD= parameter in the CMPOS
statement and applied to both normal weight and lightweight concrete. The increase is included
for ULS and ALS only.
If the user decides to use the nonlinear material curve for lightweight concrete and the stress
situation in the considered section results in change in the in situ concrete compression
strength (fcn), due to compression stiffening or the fc2d effect, both the characteristic
compressive cylinder strength (fcck) and the Young’s modulus (Ecn) are updated according to
the formulas given in DNV Sec. 6.3.2.1.
4.1.1.2 DNV - Reinforcement steel

RMPOS is used for the reinforcement material input (both longitudinal and shear
reinforcement).
The reinforcement steel is implemented according to DNV Sec. 6.3.4 and Figure 6-4. See
Figure 4-3 below.
Figure 4-3: DNV-ST-C502 - Material curve in tension/compression for reinforcement
the RMPOS statement if default values should not be used.
The reinforcement material exhibits by default the same behaviour in both tension and
compression, but the behaviour in tension may be modified to have a different ultimate tensile
strength (fsk) than the yield strength (fsy)). In addition, the yield strength in compression may
be changed with a compression capacity factor CCF= for ULS and ALS.
4.1.1.3 DNV - Prestressing steel

TEMAT is used for the prestressed reinforcement material input.
DNV does not explicit define any material curve for the prestressing reinforcement steel, but
DNV Sec. 4.8 states that prestressing steel as a product shall comply with ISO 6934 and/or
relevant international standards. DNV Sec. 4.8.3 states that for prestressed reinforcement,
the characteristic strength is equal to the yield strength fsy or the 0.1-proof stress determined
as the 5% defective fractile.

The prestressing steel is implemented as a linear curve as shown in Figure 4-4 below where
44
fsy and Esk is input in the TEMAT statement. In addition, the initial strain, ε0, (prestressing
strain) must be defined for each type of prestressed tendon. This parameter is defined in the
TETYP statement and when prestressing steel is utilized as ordinary reinforcement, only the
material curve starting from ε0 is utilized.
Figure 4-4: DNV-ST-C502 - Material curve for prestressed reinforcement steel
4.1.2 DNV - ULS Design
The rules and regulations for the ULS code checks carried out are given in DNV Sec. 6.4, 6.6
and 6.8. ShellDesign performs ULS code checks when LS=ULS parameter is specified in the
DECAS statement.
Default material factors used in the calculations are in accordance with DNV Sec. 6.3.1, except
for prestressing steel. The material factors can be specified by the user in the CMPOS, RMPOS
and TEMAT statements. The design values are calculated as:
The ULS code checks performed for the normal reinforcement, post-tensioned reinforcement
and concrete are related to given maximum allowable stresses. The calculated stresses are
based on the state of equilibrium established for the in-plane forces. The calculation of the
state of equilibrium is described in Section 4.2.3.2. The stress-strain relationships for concrete
and reinforcement are in accordance with Section 4.2.2.
Tensile stresses in the concrete between cracks are not taken into account in the design for
the in-plane forces. However, Section 4.5 describes a design method available in ShellDesign
where the tensile stresses in the concrete between cracks are taken into account. The design
method implemented is the Modified Compression Field Theory (MCFT) [5] and is supported in
DNV Sec. 6.8.
The ULS code checks performed for the shear capacity of the concrete and for the shear
reinforcement are based on the simplified method for design of transverse stresses described
in Section 4.2.3.3, where utilizations are calculated based on the actual shear capacity. MCFT
may however be used instead of the simplified method where MCFT allows to include the
transverse forces, V1 and V2, in the non-linear sectional response. MCFT including transverse
shear is supported in DNV Sec. 6.6.1.3 and Sec. 6.8.

Minimum eccentricity of membrane forces given in DNV Sec. 6.4.1.4 is not automatically
45
included in the calculations. Eccentricities may be specified by the user, using the LDFAC
statement.
4.1.2.1 DNV - Design for in-plane forces

The design for in-plane forces is implemented according to DNV Sec. 6.8. The in-plane forces
include the six section forces N1, N2, N12, M1, M2 and M12 as shown in Figure 4-5. The
corresponding six in-plane strain components, ε1, ε2, γ12, Κ1, Κ2, Κ12 are also shown in Figure
4-5 and forms the basis for the capacity control.
M 12
face 2 V2
(+ 3 face )
3. N2
M2
N 12
2.
V1
N 12
1.
N1
face 1 M1
(- 3 face) M 12
Figure 4-5: DNV-ST-C502 - The in-plane forces and corresponding strain components
The calculation of the in-plane strains and stresses in a design section is based on non-linear
sectional response due to the non-linear material behaviour of reinforced concrete. The
transverse section forces, V1 and V2 (and corresponding strains γ13 and γ23), are ignored when
establishing the sectional response and handled separately as described in Section 4.2.3.3.
The non-linear sectional analysis is based upon the following assumptions:
▪ Section forces due to load effects are known; N1, N2, N12, M1, M2 and M12.
▪ Plane sections remain plane after loading.
▪ Linear strain distribution over the thickness of the shell section.
▪ The stress-strain relationships for concrete and reinforcement are known (non-linear).
These assumptions lead to six non-linear equilibrium equations with six strain components as
unknown quantities. The shell section is divided into layers with equal thickness, t. 10 layers
are used as a default value. The number of layers can be specified by the user in the DEPAR
statement.
A Newton-Raphson iteration method is used to find the sectional response within a specified
degree of accuracy. The strains are assumed constant within each layer, and by applying the
material laws for concrete and reinforcement and ensuring the fulfilment of the assumed “plane
sections remain plane”-criteria, a state of equilibrium with external loading is established. The
stresses are then derived based on the results from the non-linear sectional response. The
result of the sectional design is a state of strain satisfying the input values describing the
section geometry, the section forces, the amount and arrangement of reinforcement and the
material properties.

4.1.2.2 DNV - Design for transverse Stresses
46
The design for transverse stresses is performed according to the simplified method in DNV Sec
6.6.2. Detailing of shear reinforcement as described in DNV Sec. 6.17 must be taken into
account by the designer.
When calculating the maximum utilization of the transverse capacity, “one dimensional”
formulas are implemented. If no in-plane membrane forces (N1, N2, N12) is present, the
section is designed in the direction with the maximum principal shear force, ref. DNV Sec.
6.6.1.7.
The “one dimensional”/uniaxial condition (Nα,Mα,Vα) is established for “all” directions (steps of
5°) according to DNV Sec. < The formulas applied, and used in the following pages, are:
𝑁𝛼 = 𝑁1 cos(𝛼)2 + 𝑁2 sin(𝛼)2 + 2𝑁12 sin⁡(𝛼)cos⁡(𝛼)
𝑀𝛼 = 𝑀1 cos(𝛼)2 + 𝑀2 sin(𝛼)2 + 2𝑀12 sin⁡(𝛼)cos⁡(𝛼)
𝑉𝛼 = 𝑉1 cos⁡(𝛼) + 𝑉2 sin⁡(𝛼)
𝐴𝑠𝛼 = 𝐴𝑠𝑥 ∗ 𝑐𝑜𝑠(𝛼)4 + 𝐴𝑠𝑦 ∗ 𝑠𝑖𝑛(𝛼)4
Shear capacity at tensile failure without shear reinforcement
The shear capacity without shear reinforcement is calculated in accordance with DNV Sec.
6.6.2 and applies as follows.
1. If Nα is zero:
DNV Sec. 6.6.2.2 applies:
𝑘𝐴 𝐴𝑠𝛼
𝑉𝑐𝑑𝛼 = 𝑉𝑐0𝛼 = 0.3 (𝑓𝑡𝑑 + ) 𝑏 𝑑𝑘 ≤ 0.6𝑓𝑡𝑑 𝑏𝑤 𝑑𝑘𝑣
𝛾𝑐 𝑏𝑤 𝑑 𝑤 𝑣
with: 𝑘𝐴 = 100⁡𝑁/𝑚𝑚2
𝑑 𝑑
𝑘𝑣 = 1.5 − = 1.5 − ≥ 1.0 ≤ 1.4
𝑑1 1.0𝑚
𝐴𝑠𝛼 is the cross section area of properly anchored reinforcement on the concrete face with
maximum tension. ⁡𝐴𝑠𝛼 is taken as the sum of the reinforcement cross section on both sides if
no moments are present.
𝑏𝑤 is the width of the beam and taken as 1 m in ShellDesign.
d is taken as the distance from the reinforcement on the side with maximum tension to the
opposite surface and taken as the maximum value found for all reinforcement layers regardless
of reinforcement orientation. d is calculated as the distance from the surface with the smallest
total longitudinal reinforcement amount to the location of the reinforcement on the opposite
side if no moments are present.
2. If Nα is negative (compression)
DNV Sec. 6.6.2.3 applies:
𝑉𝛼 𝑁𝛼
𝑉𝑐𝑑𝛼 = 𝑉𝑐0𝛼 + 0.8𝑀0 | | ≤ (𝑓𝑡𝑑 𝑘𝑣 − 0.25 ) 𝑏𝑤 𝑧1
𝑀𝛼 𝐴𝑐

𝑊𝑐
with: 𝑀0 = −𝑁𝛼 47
𝐴𝑐
𝑁𝑓
≤ 0.4𝑓𝑐𝑑
𝐴𝑐
𝐼𝑐
𝑧1 = max⁡ (0.7𝑑; )
𝑆𝑐
𝑏𝑤 is the width of the beam and taken as 1 m in ShellDesign. This also means that Ac, Wc, Ic
and Sc are calculated based on a 1.0 m wide cross section.
3. If Nα is positive (tension)
DNV Sec. 6.6.2.4 applies. If the total reinforcement strains are higher than ε sy for one or
several longitudinal reinforcement directions, the shear capacity of concrete is zero. If the total
reinforcement strains are less than εsy, the shear capacity is calculated with the following
formulas:
𝑁𝛼 𝜀𝑠𝛼
𝑉𝑐𝑑 = max⁡ [0; 𝑉𝑐𝑜 (1 − ) ; 𝑉𝑐𝑜 (1 − )]
1.5𝑓𝑡𝑑 𝐴𝑐 𝜀𝑠𝑦
Vco is calculated as bullet point 1.
Ac is calculated based on a 1.0 m wide cross section.
When the “one dimensional” formulas are applied, the reinforcement strain, εsα, is applied as
the strain in the regarded direction, α, at the level of the most utilized reinforcement. If the
direction, α, deviates from the directions of the longitudinal reinforcement, the reinforcement
strain, εsα, is reduced as:
𝜀𝑠𝛼
𝜀𝑠𝛼,𝑟𝑒𝑑 =
sin(𝛼) + cos⁡(𝛼)
Shear capacity at tensile failure with shear reinforcement

The shear capacity of a section with shear reinforcement is calculated in accordance with DNV
Sec. 6.6.2.6 and is taken as Vcd + Vsd, where Vcd is calculated according to the formulas for
shear capacity without shear reinforcement, using a value of kv equal to 1.0.
The shear capacity of the shear reinforcement, Vsd, is calculated as:

𝑓𝑠𝑑 𝐴𝑠𝑣
𝑉𝑠𝑑 = 𝑧(1 + cot⁡(𝛽))
𝑠
with: 𝛽 = 90°
z is taken equal to 0.9 d if the cross section has a compressive zone. If the entire cross section
has tensile strain, z is taken equal to the distance h' between the outermost longitudinal
reinforcement groups (centroid) at the upper and lower face.

The shear reinforcement area Asv/s is given in m2/m2, and in accordance with the input of the
48
shear reinforcement amount in the SRTYP statement. All shear reinforcement bars are
assumed placed with 𝛽 = 90°.
Shear capacity for compression failure

The check of shear compression failure is in accordance with DNV Sec. 6.6.2.7:
𝑉𝑐𝑐𝑑 = 0.30𝑓𝑐𝑑 𝑏𝑤 z(1 + cot⁡(𝛽)) ≤ 0.45𝑓𝑐𝑑 𝑏𝑤 𝑧
with: 𝛽 = 90°
All calculations in ShellDesign are performed per meter, thus b w is equal to 1.0 m.
Additional forces in longitudinal reinforcement due to shear forces

Additional tensile forces in the longitudinal reinforcement due to shear forces, ref. DNV Sec.
6.6.4, are not automatically accounted for in ShellDesign, but may be included in the design
calculations with STFOR and DECAS statement.
The additional tensile forces, FSV, are calculated as:
𝐹𝑆𝑉 = 𝑉𝐹 − 0.5𝑉𝑠𝑑 ∙ (1 + cot 𝛼) ≥ 0
Where Vf is the applied design shear force (V1 and/or V2) and Vsd is the shear capacity of the
shear reinforcement. See above. Note that the additional tensile forces are not included in the
shear capacity, Vcd.
DNV Sec. 6.6.4.2 states that the maximum force in the longitudinal reinforcement on the
tension side shall not be taken at greater value than the value corresponding to the highest
absolute moment in combination with the axial force found on the same part of the moment
curve as the section examined. As ShellDesign is a “point design” program, this cannot
automatically be accounted for by the program, but may be accounted for by defining a
maximum moment, Mmax, in the STFOR statement by the user. ShellDesign will then include
tensile forces, FSV, as:
𝑀𝑚𝑎𝑥 𝑀𝐹
𝐹𝑆𝑉 = min [[𝑉𝐹 − 0.5𝑉𝑠𝑑 ∙ (1 + cot 𝛼)]⁡, − ⁡]
𝑧 𝑧
Where MF is the applied design moment. Note also that these additional forces in the
longitudinal reinforcement due to shear forces are implicit taken into account in the MCFT
described in Section 4.5.
4.1.2.3 DNV - Water Pressure in Cracks

The effect of water pressure acting in the cracks is taken into account in the state of equilibrium
established in Section 4.2.3.2 when both the WPARE statement and DWP=id in the DECAS
statement is included in the ShellDesign input file. See Section 3.2.4 for description of water
pressure in cracks in the conventional design method.
The water pressure effect is included as additional sectional tensile forces/moments in a design
section when the present external forces give tension in the section; i.e. when the concrete
strain is positive. Sectional forces due to water pressure in cracks are then added to the
external sectional forces. Through repeated iterations, a state of equilibrium is established,
accounting for simultaneous development of cracks and water pressure effects.

49
Note that water pressure in cracks can also be included in the CSM analyses. See NONLI,
WPARE and DECAS statement. See Section 3.3.5 for description of water pressure in cracks
in CSM analyses.
4.1.3 DNV - ALS Design
The rules and regulations for the ALS code checks carried are given in DNV Sec. 6.14.
ShellDesign performs ALS code checks when LS=ALS is specified in the DECAS statement.
Default material factors used in the calculations are in accordance with DNV Sec. 6.3.1. The
material factors can be specified by the user in the CMPOS, RMPOS and TEMAT statements.
Default values of εcu and εsu correspond to those given in DNV Sec. 6.3.2.
DNV Sec. 6 N 101 states that the design calculations can be performed according to the rules
in Sec. 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 6.11, 6.12 and 6.16, hence the same design
calculations as described in Section 4.2.3 apply also for ALS in ShellDesign, but with different
material factors.
However, there are some differences in material properties for high frequency loads and high
temperature loads, see DNV Sec. 6.14.2 and 6.14.3. This is not implemented in the DNV
ShellDesign code and must be taken into account by the designer.
4.1.4 DNV - SLS Design
The rules and regulations for the SLS code checks carried out are given in DNV Sec. 6.15. The
design resistance in SLS is normally related to criteria for:
— durability
— limitation of cracking (checked in ShellDesign with CRWOS statement)
— tightness (checked in ShellDesign with TIGHT statement)
— limitation of deflections and vibrations
ShellDesign performs SLS code checks when LS=CRW or LS=SLS is specified in the DECAS
statement, where ShellDesign performs calculations regarding limitation of cracking and
tightness when LS=CRW is specified. The LS=SLS check is only related to stresses in concrete
and reinforcement.
Default material factors used in the calculations are in accordance with DNV Sec. 6.3.1, except
for prestressing steel. The material factors can be specified by the user in the CMPOS, RMPOS
and TEMAT statements.
4.1.4.1 DNV - Calculation of uncracked or cracked sections

The criteria determining whether a section is cracked is according to DNV Sec. 6.15.8.1 and
defined as uncracked if the principal stress σ1 does not exceed ftn/k1.
With combined axial tensile force and bending moment the criteria is defined as:
𝑘𝑤 𝜎𝑁 + 𝜎𝑀 ⁡ < 𝑘𝑤 ⁡𝑓𝑡𝑛 /𝑘1
With combined axial compression force and bending moment the criteria is defined as:

50
𝜎𝑁 + 𝜎𝑀 ⁡ < 𝑘𝑤 ⁡𝑓𝑡𝑛 /𝑘1
where:
σN = stress due to axial force (tension positive)
σM = edge stress due to bending alone (tension positive)
ftn = normalized structural tensile strength of concrete (Table 4-2 and Table 4-3)
k1 = constant used in calculations of crack width (Table 6-12)
kw = coefficient dependent on cross-sectional height:
kw = 1.5 – h/h1 ≥ 1.0, where h1 = 1.0 m.
The k1 parameter is set to a default value of 1.0. The value of this parameter can be specified
by the user in the CRWOS statement. It is important that the designer defines the correct k1
parameter according to Table O4 with the CRWOS statement.
The calculated stresses are based on the same state of equilibrium established and described
in Section 4.2.3.2, using SLS material factors. The stress-strain relationships for concrete and
reinforcement are in accordance with Section 4.2.2, but where also the tensile capacity of the
concrete is taken into account if LS=CRW.
Prior to cracking, the concrete tensile stresses are taken as ε*Ecn. After cracking, a mean
tensile stress between cracks, βsftk, is taken into account and included in the state of
equilibrium established according to the general method in DNV E.1.4.
βs is set to a default value of 0.4. The factor may be changed by the user in the CRWOS
statement. Water pressure in cracks are considered as described in 4.2.3.4, but where the
water pressure in cracks are only applied if the principal stress σ1 does not exceed the cracking
strain defined above.
The following interpretation is made:
1. The principal strain directions are calculated at both faces of the cross sections; φface1
and φface2.
2. N(φface1), M(φface1) and N(φface2), M(φface2) are established and used for calculating
σN(φface1), σM(φface1), and σN(φface2), σM(φface2).
4.1.4.2 DNV - Calculation of Crack widths

Limitation of cracking is performed taking into account all longitudinal and prestressed
reinforcement present in the section. Calculated crack widths are compared to maximum
allowable crack widths specified by the user in the CRWOS statement.
The check is carried out when LS=CRW is specified in the DECAS statement. The calculations
are performed according to DNV Sec. 6.15.3, Sec. 6.15.8 and App. E. The CRWOS statement
and DCW= in the DECAS statement must be included when crack widths and crack depths
should be calculated.
When a section is considered cracked according to the criteria in Section 4.2.5.2, the following
formulas applies for the calculation of the maximum crack widths for longitudinal reinforcement
and prestressing reinforcement.
The characteristic crack width for the longitudinal reinforcement is calculated according to DNV
Sec. 6.15.8.2 as:

𝑤𝑘 = 𝑙𝑠𝑘 (⁡𝜀𝑠𝑚 − ⁡ 𝜀𝑐𝑚 − 𝜀𝑐𝑠 )
51
lsk is the influence length of the crack where a slip between reinforcement and concrete is
assumed to occur.
εsm is calculated as the mean principal tensile strain in the reinforcement in the cracks influence
length at the outer layer of the reinforcement. The calculation of εsm is calculated with the
contribution of concrete tensile strength of βsftk between the cracks according to the general
method in DNV E.1.4.
εcm is calculated as βsftk/Ecn according to the general method in DNV E.1.4. βs is set to a default
value of 0.4. The factor may be changed by the user in the CRWOS statement.
The free shrinkage strain, εcs, is set to zero, but can be included with CS= in the CRWOS
statement.
For a stabilized crack pattern, lsk is taken to be equal to the characteristic crack spacing
according to DNV E.1.2.2 as:
𝑓𝑡𝑘
𝑙𝑠𝑘 = 𝑠𝑟𝑘 = 1.7[𝑠𝑟𝑜 + ( )𝑘 𝑘 ℎ 𝑆 /(𝜋𝑛ø)
𝜏𝑏𝑘 𝑏 𝑐 𝑐𝑒𝑓 𝑏
sro = 20 mm
ftk /τbk = 0.75 . The factor may be changed in RETYP statement.
Acef = b ∙hcef where b is the width of the concrete section in mm and set to 1000 mm in
ShellDesign.
hcef = the height of the effective concrete area = 2.5(h-d), where (h-d) is the distance from
the concrete surface on the tension side to the centre of gravity of the reinforcement. For
tension zone with reinforcement of single tensile bars in one layer, h cef = 2.5(c + φ/2).
hcef is less than the height of the tensile zone (h-x), where x is the distance from the concrete
edge on the compression side to the neutral axis and h is the total cross-sectional height.
For double reinforce cross-sections with through going tensile stresses, hcef is calculated for
each side, hcef shall in this case never be larger than h/2.
kc = a coefficient which accounts for the strain distribution within the cross-section.
kc = (1 + εII/ εI)/2 where εII/ εI is the ratio between minimum and maximum strain in the
effective concrete area calculated for cracked cross-section. For a cross-section with through
going tensile stresses, kc =1.0. Note that the concrete section in ShellDesign is checked for

through going tensile stresses in all directions. If the maximum principal stress for each
52
concrete layer checked is larger than 1e-6, the layer is considered to have tensile stresses.
kb = 0.15 n + 0.85, a coefficient which accounts for reduced bond of bundled reinforcement.
c = the concrete cover for the reinforcement under investigation. Taken from RETYP
statement.
φ = the diameter of the reinforcement bar. Taken from the RETYP statement.
sb = the distance between reinforcement bars or bundles of bars, maximum value in the
calculation 15φ (for bundles of reinforcement 15φn1/2). Is calculated based on parameters in
RETYP statement.
n = number of bars in a bundle. Taken from the RETYP statement.
The crack spacing, srk, is not calculated larger than 2.5(h-x) and not less than 2.5c where
c<(h-x).
If the principal strain deviates from the reinforcement direction, the crack spacing S rk in the
principal direction is calculated according to DNV E.1.3.1 as:
1
𝑆𝑟𝑚 = ( )
𝑠𝑖𝑛⁡𝑣/𝑆𝑟𝑚𝑥⁡ ⁡ + ⁡𝑐𝑜𝑠⁡𝑣/𝑆𝑟𝑚𝑦
𝑤𝑘 is adjusted due to the nominal and real cover according to DNV Sec. 6.15.3.6 as:
𝐶1
𝑤1𝑘 = 𝑤𝑜𝑘 ⁡ > 0.7𝑤𝑜𝑘
𝐶2
The crack widths for prestressed reinforcement are calculated according to DNV Sec. 6.15.3.7
as:
𝜀𝑠2
𝑤2𝑘 = 𝑤1𝑘 ⁡
𝜀𝑠1
Where 𝜀𝑠1 is the principal strain in the height of the most utilized reinforcement at the face and
in the direction corresponding to the face and direction with maximum crack width. 𝜀𝑠2 is the
tensile strain at the level of the prestressed reinforcement (defined in TELOC statement).
4.1.4.3 DNV - Calculation of Crack Depths

The crack depth is calculated where each layer is checked according to the cracking criteria
specified in Section 4.2.5.2. If the layer is cracked, the thickness of this layer is included in
the crack depth. The calculation is carried out when LS=CRW is specified in the DECAS
statement.
In this check, the shell section is divided into layers of 0.01 m thickness by default. The number
of layers can be specified by the user with the N_LAY= parameter in the DEPAR statement if
more accurate results are required.
4.1.4.4 DNV - Calculation of Compression Zone

Tightness is related to compression zones and specified in DNV Sec. 6.15.6. Calculated
compression zones are compared to minimum compression zones specified by the user in the
TIGHT statement. The calculation is carried out when LS=CRW is specified in the DECAS
statement and the results are shown in the UR=CZ table and/or graphical in plots.

53
The minimum allowable depth of the compression zone (CZ-min) is user input, where the CZ-
min is the lesser of X1 and X2*h, where h is the section thickness. If X2 is not input by the
user, only X1 parameter is used as minimum depth. Deafult values of X1 is 0.0 and default
value of X2 is 0.0.
The compression zone is calculated by calculating the non-linear sectional response and first
checking the principal strain, εp, on both face 1 and face 2, where the criteria ε<0 defines if
the layer has compression or not. If both faces have ε p>0, the compression zone is set to zero.
If both faces have εp<0, the compression zone is set to the design section thickness.
If one face has compression and the other face has tension, the principal strain, εp, for each
layer in the design section is checked for whether compression or tension. If a layer has
compression (ε<0), the thickness of this layer is included in the compression zone.
In this calculation, the shell section is divided into layers of 0.01 m thickness by default. The
number of layers can be specified by the user with the N_LAY= parameter in the DEPAR
statement if more accurate results are required. Note that the layers will not be larger than
0.01 m.
Note that the non-linear sectional response is calculated with the concrete tensile strength, f ck.
Also note that the Compression Zone, CZ, cannot be compared to the calculated crack depth
in the DR table for CRW, as this crack depth is calculated based on the criteria described in
4.1.4.3.
4.1.4.5 DNV - Through thickness cracks

Tightness may also be connected to limit crack widths for through thickness cracks. Although
this criteria is not explicit defined in DNV Sec. 6.15.6, through-thickness cracks is calculated
in ShellDesign based on the following criterias. The calculation is carried out when LS=CRW is
specified in the DECAS statement and the results are shown in the UR=CT table and/or
graphical in plots.
The tightness criteria are related to limit the crack widths to a value wk1, where wk1 varies with
the hydrostatic head to the wall thickness. The parameters must be specified by the user in
the TIGHT statement. Through thickness crack calculations are carried out for sections where
the section thickness is equal to the crack depth as calculated in Section 4.2.5.4.
4.1.4.6 DNV - SLS - Stresses in reinforcement and concrete

The SLS code checks (SLS) are performed for the normal reinforcement, post-tensioned
reinforcement and concrete and are related to given maximum allowable stresses. The
calculated stresses are based on the same state of equilibrium established and described in
Section 4.2.3.2, using SLS material factors. Tensile stresses in the concrete between cracks
are not taken into account in the design for the in-plane forces.
The stress-strain relationships for concrete and reinforcement are in accordance with Section
4.2.2. No code checks for shear forces are performed in the SLS design calculations. Water
pressure in cracks is considered as described in 4.2.3.4.

4.1.5 DNV - FLS Design
54
The rules and regulations for the FLS code checks carried out are given in DNV Sec. 6.13.
ShellDesign performs FLS code checks when LS=FLS is specified in the DECAS statement. In
addition, the FAPOS and WAVED statement must be included.
Default material factors used in the calculations are in accordance with DNV Sec. 6.3.1.2,
except for prestressing steel. The material factors can be specified by the user in the CMPOS,
RMPOS and TEMAT statements.
The code check is a stress range test based on a cumulative linear damage theory. The
requirements in this hypothesis, the linear damage accumulation law, are given in DNV Sec.
6.13.1 and are as follows:
𝑘
𝑛𝑖
𝐷=∑ ≤𝜂
𝑁𝑖
𝑖=1
where:
η: the limit for the cumulative damage ratio (the safety factor for fatigue utilization)
k: the number of stress blocks used (≥10) per load ratio
ni: the number of cycles in stress block i
Ni: the number of uniform cycles with the same mean, stress range and duration which causes
failure.
The default value for η in ShellDesign is 0.33 according to DNV Table 6-7 but may be changed
in FAPOS statement. The k and ni parameter are specified through the WAVED statement.
4.1.5.1 DNV - Stress-Strain Relations

The state of equilibrium is established assuming a linear distribution of concrete stresses within
the compression zone, where the modulus of elasticity for concrete is taken as EC=0.8*Ecn
according to DNV Sec. 6.13.3.2.
Due to a gradient of strains across the compressive zone, DNV 6.13.3.2 permits an increase
of the reference value of the concrete compressive strength, frd:
𝑓𝑟𝑑 = 𝛼𝑓𝑐𝑑
where:
𝛼 = 1.3 − 0.3𝛽 ≥ 1.0
β = the ratio between the numerically smallest and largest stresses acting simultaneously in
the local compressive concrete zone. The distance between the points used when calculating
β shall not exceed 300 mm (0 < β < 1.0).
4.1.5.2 DNV - In-Plane Stresses

Concrete compression failure:
The number of cycles, N, causing fatigue failure, is calculated according to DNV Sec. 6.13.2.1.
The design life of concrete is as follows:
𝜎𝑚𝑎𝑥
1−
𝐶5 ∙ 𝑓𝑟𝑑
𝑙𝑜𝑔10 𝑁 = 𝐶1 𝜎
1 − 𝑚𝑖𝑛
The value of the C1 parameter is set assuming that the construction is located in water. C1 is
10.0 for structures in water for those stress-blocks having stress variation in the compression-
compression range and 8.0 for structures in water for those stress-blocks having stress
variation in the compression-tension range. The value of the C5 parameter is by default set to

1.0 corresponding to reinforced concrete. The values for C1 and C5 may be changed in FAPOS
55
statement.
If the calculated design life, 𝑙𝑜𝑔10 𝑁, is larger than the value given of:
𝐶1
𝑋=
𝜎𝑚𝑖𝑛
(1 − + 0.1𝐶1 )
The design life, 𝑙𝑜𝑔10 , should be multiplied with:

𝐶2 = 1 + 0.2(𝑙𝑜𝑔10 𝑁 − 𝑋) > 1.0
As the direction of σmax will vary from block to block, this procedure implies that the
contribution to the linear damage accumulation law is conservatively calculated for different
directions and added together.
The utilization ratio statement in ShellDesign is based on (face 1 and face 2):
𝐷1,2
𝑈𝑅1,2 =
𝜂
where D and η is as defined in Section 4.2.6.1.
Reinforcement failure:
The verification of fatigue capacity of the reinforcement bars is based on stresses calculated
as for SLS.
The number of cycles, N, causing failure of reinforcement is calculated according to DNV Sec.
6.13.2.2 as follows:
𝑙𝑜𝑔10 𝑁 = 𝐶3 − 𝐶4 𝑙𝑜𝑔10 ∆𝜎
The default values of C3 and C4 are set to 19.6 and 6.0, respectively, but may be changed in
FAPOS statement. The maximum stress σmax in the reinforcement shall be less than fsk/γs,
where γs is the reinforcement material factor defined with MFF=mf in RMPOS statement.
The utilization ratio statement for each reinforcement layer in ShellDesign is based on:
𝐷
𝑈𝑅 =
𝜂
UR is assumed infinite if N>2*108.

4.1.5.3 DNV - Design for Transverse Stresses
56
The design for transverse stresses is performed in accordance with the “one
dimensional”/uniaxial condition (Nα,Mα,Vα) and shear capacities are based on the “Simplified
method” as described in Section 4.2.3.3.

“Fictitious” beams representing all directions are checked according to the “one dimensional”
fatigue failure criteria equation described in the following.
The linear damage accumulation law is calculated for all beams and the one achieving the
highest value is deemed governing, i.e represents the fatigue utilization of the shell section.
The number of cycles, N, causing fatigue tension failure in concrete is calculated according to
DNV Sec. 6.13.4 as follows:
𝑉
1 − 𝑚𝑎𝑥
𝐶5 ∙ 𝑉𝑐𝑑
𝑙𝑜𝑔𝑁 = 𝐶1
𝑉
1 − 𝑚𝑖𝑛
where Vcd is defined as in Section 4.2.3.3.
For those stress blocks where the shear force changes sign, the equation above becomes:
𝑉𝑚𝑎𝑥
1−
𝑉
1 + 𝑚𝑖𝑛
Default values for C1 and C5 is given as described above.

fatigue failure criteria described in the following.
The concrete carries a shear force proportional to the concrete contribution to the shear
𝑉𝑐𝑑
capacity (𝑉 = ).
𝑉𝑐𝑑 +𝑉𝑠𝑑
Vcd is calculated according to DNV Sec. 6.13.4.3 using a reduced tensile strength of the
concrete equal to 0.5*ftd.
Vsd is calculated according to DNV Sec. 6.13.4.4.
The number of cycles, N, causing concrete shear tensile fatigue failure is then calculated as
for the “No shear reinforcement method” described above.
The utilization ratio statement for concrete shear in ShellDesign is:
𝐷
𝑈𝑅 =
𝜂
The shear reinforcement carries a shear force proportional to the shear reinforcement
𝑉𝑠𝑑
contribution to the shear capacity (𝑉 = ).

Vcd and Vsd are calculated as described above. The stress range in the shear reinforcement is
57
calculated on this basis.
The number of cycles, N, causing shear reinforcement fatigue failure is then calculated as for
the longitudinal reinforcement. The default values of C3 and C4 are set to 15.9 and 4.8,
respectively, but may be changed in FAPOS statement.
When the shear changes direction, the stress in shear reinforcement will always be tension.
This affects the number of cycles, i.e. the size and number of stress ranges experienced by
the shear reinforcement. This is accounted for in design.

The fatigue verification for compression failure is as prescribed in DNV Sec. 6.13.4.6.
In addition, DNV Sec. 6.13.4.7 is also included in the design calculations where formulas
including frd are replaced with fcd.
4.1.5.4 DNV - Water Pressure in Cracks

The effect of water pressure acting in the cracks is included in the FLS code check as described
for ULS in Section 4.1.2.3 when WPARE and DWP=id in the DECAS statement are included.
Pore pressure for FLS can be included in the FAPAR statement with FA=f, in addition to
WPARE and DWP=id in DECAS statement. Pore pressure means water/gas present in pores
in the concrete also when compression is present in the design section.

4.2 NS 3473 58
This Section describes the implementation of the NS 3473, 6th edition, [3] (NS) design code in
ShellDesign. Interpretations of rules and regulations and special features offered by
ShellDesign are explained.
Note that NS 3473 is a withdrawn design code, but is still used in design where other design
codes have shortcomings, especially for offshore structures, and therefore still available in
ShellDesign. Note also that the DNV-ST-C502 is practically a copy of the NS 3473 design code
regards to calculations in ShellDesign.
ShellDesign performs design calculations based on NS 3473 when input statement DEPAR
with the parameter D_COD=NS is defined in the ShellDesign input file.
4.2.1 NS - Material properties
The material properties in ShellDesign are in accordance with NS 3473 Sec. 11.
4.2.1.1 NS - Concrete
The CMPNS statement is used for the concrete material input.
The normal weight concrete is implemented according to NS 3473 Sec. 11.3.1 and Figure 2.
See Figure 4-6 below.
Figure 4-6: NS 3473 - Material curve in compression for normal weight concrete
The lightweight concrete is implemented according to NS 3473 Sec. 11.3.3 and Figure 4. See
Figure 4-7 below.
Figure 4-7: NS 3473 - Material curve in compression for lightweight concrete

59
ρ1=2200 kg/m3 and ρ has to be user input in the CMPNS statement to activate the lightweight
concrete material curve. ρ is the oven-dry density of concrete. The limitation in NS 3473 sec.
11.1.1 for lightweight concrete is also included.
the CMPNS statement if default values should not be used. Note also that for SLS and CRW
design, the material curve is a linear elastic material curve with modulus of elasticity taken as
Eck according to NS 3473 Sec. 15.1.2 and without any plastic area.
In design sections where there is tension in one principal direction and compression in the
other principal direction for both normal and lightweight concrete, the concrete compression
capacity is reduced to fc2d according to in NS 3473 Sec. 12.5.2:
𝑓𝑐𝑑
0.8 − 100𝜀1
As default, the minimum concrete capacity, fc2d, will be reduced to minimum 0.3*fcd if the
principal tensile strain, ε1, is large enough. Using the TSD= parameter in the CMPNS
statement, the 0.3 factor can be changed by the user. This reduction is applied for only ULS
and ALS limit states.
In sections where there is compression in both principal directions, the concrete compression
capacity is increased by 0.75 times the smallest principal compressive stress according to NS
3473 Sec. 11.1.4. The increase is limited to 15% of the compression capacity f cd and limited
for grades up to and including grade B55. The increase in concrete capacity is not included for
lightweight concrete. The 15% increase may be changed with the CSA= parameter in the
CMPNS statement.
4.2.1.2 NS - Reinforcement steel

RMPNS is used for the reinforcement material input (both longitudinal and shear
reinforcement).
The reinforcement steel is implemented according to NS 3473 Sec. 11.3.6 and Figure 5. See
Figure 4-8 below.
Figure 4-8: NS 3473 - Material curve in tension/compression for reinforcement steel

60
the RMPNS statement if default values should not be used.
The reinforcement material exhibits by default the same behaviour in both tension and
compression, but the behaviour in tension may be modified to have a different ultimate tensile
strength than the yield strength fsk. In addition, the yield strength in compression may be
changed with a compression capacity factor CCF= for ULS and ALS.
4.2.1.3 NS - Prestressing steel

NS does not explicit define any material curve for the prestressing reinforcement steel, but NS
Sec. 7.7 states that prestressing steel, the individual components and the execution specified
in the project specifications shall be such that the requirements in NS 3465 are fulfilled.
In ShellDesign, the prestressing steel is implemented as a linear curve as shown in Figure 4-9
below where fsy and Esk is input in the TEMAT statement. In addition, the initial strain, ε0,
(prestressing strain) must be defined for each type of prestressed tendon. This parameter is
defined in the TETYP statement and when prestressing steel is utilized as ordinary
reinforcement, only the material curve starting from ε0 is utilized.
Figure 4-9: NS 3473 - Material curve for prestressed reinforcement steel
4.2.2 NS - ULS Design
The rules and regulations for the ULS code checks carried out are given in NS 3473 Sec. 12
[3]. ShellDesign performs ULS code checks when LS=ULS parameter is specified in the DECAS
statement.
Default material factors used in the calculations are in accordance with NS 3473 Sec. 10.4,
Table 4. The material factors can be specified by the user in the CMPNS, RMPNS and TEMAT
statements.
and concrete are related to given maximum allowable stresses. The calculated stresses are
based on the state of equilibrium established for the in-plane forces. The stress-strain
relationships for concrete and reinforcement are in accordance with Section 4.3.2.

Tensile stresses in the concrete between cracks are not considered in the design for the in-
61
plane forces. However, Section 4.5 describes a design method available in ShellDesign where
the tensile stresses in the concrete between cracks are considered. The design method
implemented is the Modified Compression Field Theory (MCFT) [5] and is supported in NS Sec.
12.5.1 and Sec. A.12.5.
reinforcement are based on the simplified method for design of transverse stresses described
in Section 4.3.3.3, where utilizations are calculated based on the actual shear capacity. MCFT
may however be used instead of the simplified method where MCFT allows to include the
transverse forces, V1 and V2, in the non-linear sectional response. MCFT including transverse
shear is supported in NS Sec. 12.5.1 and Sec. A.12.5.
Minimum eccentricity of membrane forces given in NS 3473 Sec. 12.1.2 is not automatically
included in the calculations. Eccentricities may be specified by the user, using the LDFAC
statement.
Capacity calculations are based on the entire concrete area of a section, disregarding the
reduction in concrete area given in NS 3473 Sec. 12.1.3 due to large compression
reinforcement amounts. Detailing of compression reinforcement according to NS 3473 Sec.
12.1.4 must be considered by the designer.
4.2.2.1 NS - Design for in-plane forces

The design for in-plane forces is implemented according to NS 3473 Sec. 12.5. The in-plane
forces include the six section forces N1, N2, N12, M1, M2 and M12 as shown in Figure 4-5. The
M 12
face 2 V2
(+ 3 face )
3. N2
M2
N 12
2.
V1
N 12
1.
N1
face 1 M1
(- 3 face) M 12
Figure 4-10: NS 3473 - The in-plane forces and corresponding strains in a shell section
See Section 4.5 for a design method available in ShellDesign where the transverse forces, V1
and V2, are included in the non-linear sectional response. The design method implemented is
the Modified Compression Field Theory (MCFT) [5].

62
statement.
4.2.2.2 NS - Design for transverse Stresses

The design for transverse stresses is performed according to the simplified method in NS 3473
Sec. 12.3.2. Detailing of shear reinforcement as described in NS 3473 Sec. 12.3.1.5 must be
taken into account by the designer.
formulas are implemented in accordance with NS 3473 Sec. A.12.3.1.6 as follows. If no in-
plane membrane forces (N1, N2, N12) is present, the section is designed in the direction with
the maximum principal shear force, ref. NS 3473 Sec. 12.3.1.6.
The “one dimensional”/uniaxial condition (Nα,Mα,Vα) is established for “all” directions (steps of
5°) according to NS 3473 Sec. A.12.3.1.6. The formulas applied, and used in the following
pages, are:
𝑁𝛼 = 𝑁1 cos(𝛼)2 + 𝑁2 sin(𝛼)2 + 2𝑁12 sin⁡(𝛼)cos⁡(𝛼)
𝑀𝛼 = 𝑀1 cos(𝛼)2 + 𝑀2 sin(𝛼)2 + 2𝑀12 sin⁡(𝛼)cos⁡(𝛼)
𝑉𝛼 = 𝑉1 cos⁡(𝛼) + 𝑉2 sin⁡(𝛼)
𝐴𝑠𝛼 = 𝐴𝑠𝑥 ∗ 𝑐𝑜𝑠(𝛼)4 + 𝐴𝑠𝑦 ∗ 𝑠𝑖𝑛(𝛼)4
The shear capacity without shear reinforcement is calculated in accordance with NS 3473 Sec.
12.3.2.1, 12.3.2.2 and 12.3.2.3 and applies as follows.
4. If Nα is zero:
NS 3473 Sec. 12.3.2.1 applies:
𝑘𝐴 𝐴𝑠𝛼
𝑉𝑐𝑑𝛼 = 𝑉𝑐0𝛼 = 0.3 (𝑓𝑡𝑑 + ) 𝑏 𝑑𝑘 ≤ 0.6𝑓𝑡𝑑 𝑏𝑤 𝑑𝑘𝑣
𝛾𝑐 𝑏𝑤 𝑑 𝑤 𝑣
with: 𝑘𝐴 = 100⁡𝑁/𝑚𝑚2

𝑑 𝑑
𝑘𝑣 = 1.5 − = 1.5 − ≥ 1.0 ≤ 1.4 63
𝑑1 1.0𝑚
𝐴𝑠𝛼 is the cross section area of properly anchored reinforcement on the side with maximum
tension. ⁡𝐴𝑠𝛼 is taken as the sum of the cross section on both sides if no moments are present.
𝑏𝑤 is the width of the beam and taken as 1 m in ShellDesign.
5. If Nα is negative (compression)
NS 3473 Sec. 12.3.2.2 applies:
𝑉𝛼 𝑁𝛼
𝑉𝑐𝑑𝛼 = 𝑉𝑐0𝛼 + 0.8𝑀0 | | ≤ (𝑓𝑡𝑑 𝑘𝑣 − 0.25 ) 𝑏𝑤 𝑧1
𝑀𝛼 𝐴𝑐
𝑊𝑐
with: 𝑀0 = −𝑁𝛼
𝐴𝑐
𝑁𝑓
≤ 0.4𝑓𝑐𝑑
𝐴𝑐
𝐼𝑐
𝑧1 = max⁡ (0.7𝑑; )
𝑆𝑐
𝑏𝑤 is the width of the beam and taken as 1 m in ShellDesign. This also means that Ac, Wc, Ic
and Sc are calculated based on a 1.0 m wide cross section.
opposite surface, and taken as the maximum value found for all reinforcement layers
regardless of reinforcement orientation. d is calculated as the distance from the surface with
the smallest total longitudinal reinforcement amount to the location of the reinforcement on
the opposite side if no moments are present.
6. If Nα is positive (tension)
NS 3473 Sec. 12.3.2.3 applies. If the total reinforcement strains are higher than ε sy for one or
several longitudinal reinforcement directions, the shear capacity of concrete is zero. If the total
reinforcement strains are less than εsy, the shear capacity is calculated with the following
formulas:
𝑁𝛼 𝜀𝑠𝛼
𝑉𝑐𝑑 = max⁡ [0; 𝑉𝑐𝑜 (1 − ) ; 𝑉𝑐𝑜 (1 − )]
1.5𝑓𝑡𝑑 𝐴𝑐 𝜀𝑠𝑦
Vco is calculated as bullet point 1.
Ac is calculated based on a 1.0 m wide cross section.
According to NS 3473 A.12.3.1.6 the reinforcement strain, ε sα, is the strain in the regarded
direction, α, at the level of the most utilized reinforcement. If the direction, α, deviates from
the directions of the longitudinal reinforcement, the reinforcement strain, ε sα, is reduced
according to NS 3473 Sec. A.12.3.1.6 as:

𝜀𝑠𝛼
𝜀𝑠𝛼,𝑟𝑒𝑑 = 64
sin(𝛼) + cos⁡(𝛼)

The shear capacity of a section with shear reinforcement is calculated in accordance with NS
3473 Sec. 12.3.2.4 and is taken as Vcd + Vsd, where Vcd is calculated according to the formulas
for shear capacity without shear reinforcement, using a value of kv equal to 1.0.
The shear capacity of the shear reinforcement, Vsd, is calculated as:

𝑓𝑠𝑑 𝐴𝑠𝑣
𝑉𝑠𝑑 = 𝑧(1 + cot⁡(𝛽))
𝑠
with: 𝛽 = 90°
The shear reinforcement area Asv/s is given in m2/m2, and in accordance with the input of the
shear reinforcement amount in the SRTYP statement. All shear reinforcement bars are
assumed placed with 𝛽 = 90°.

The check of shear compression failure is in accordance with NS 3473 Sec. 12.3.2.5:
𝑉𝑐𝑐𝑑 = 0.3𝑓𝑐𝑑 𝑏𝑤 z(1 + cot⁡(𝛽)) ≤ 0.45𝑓𝑐𝑑 𝑏𝑤 𝑧
with: 𝛽 = 90°
All calculations in ShellDesign are performed per meter, thus b w is equal to 1.0 m.
Limitation of the shear compression capacity given in NS 3473 Sec. 12.3.1.8 is disregarded.

Additional tensile forces in the longitudinal reinforcement due to shear forces, ref. NS 3473
Sec. 12.3.4, are not automatically accounted for in ShellDesign, but may be included in the
design calculations with STFOR and DECAS statement.
The additional tensile forces, FSV, are calculated as:
𝐹𝑆𝑉 = 𝑉𝐹 − 0.5𝑉𝑠𝑑 ∙ (1 + cot 𝛼) ≥ 0
Where Vf is the applied design shear force (V1 and/or V2) and Vsd is the shear capacity of the
shear reinforcement. See above. Note that the additional tensile forces are not included in the
shear capacity, Vcd.
NS 3473 Sec. 12.3.4.3 states that the maximum force from moment and shear in the
longitudinal reinforcement on the tension side shall not be taken at greater value than the
value corresponding to the highest absolute moment found on the same part of the moment
curve as the section examined. As ShellDesign is a “point design” program, this cannot
automatically be accounted for by the program, but may be accounted for by defining a
maximum moment, Mmax, in the STFOR statement by the user. ShellDesign will then include
tensile forces, FSV, as:
𝑀𝑚𝑎𝑥 𝑀𝐹
𝐹𝑆𝑉 = min [[𝑉𝐹 − 0.5𝑉𝑠𝑑 ∙ (1 + cot 𝛼)]⁡, − ⁡]
𝑧 𝑧

Where MF is the applied design moment.
65
Note also that these additional forces in the longitudinal reinforcement due to shear forces are
implicit taken into account in the MCFT described in Section 4.5.
4.2.2.3 NS - Water Pressure in Cracks

established in Section 4.3.3.2 when both the WPARE statement and DWP=id in the DECAS
statement is included in the ShellDesign input file. See Section 3.2.4 for description of water
pressure in cracks in the conventional design method.
The water pressure effect is included as additional sectional tensile forces/moments in a design
section when the present external forces give tension in the section; i.e. when the concrete
strain is positive. Sectional forces due to water pressure in cracks are then added to the
external sectional forces. Through repeated iterations, a state of equilibrium is established,
accounting for simultaneous development of cracks and water pressure effects.
If POR= in addition to DWP=id is included in the DECAS statement, the effect of pore pressure
is taken into account in the calculation of the tensile shear capacity of the concrete (Vcd). The
pore pressure effect means that the water pressure is also let into pores in the concrete when
compression. Note that POR= is only applicable for NS 3473 design code in ShellDesign.
Note that water pressure in cracks can be included as a load case in the CSM analyses. See
NONLI, WPARE and DECAS statement. See Section 3.3.5 for description of water pressure
in cracks in the CSM analyses.
4.2.3 NS - ALS Design
The rules and regulations for the ALS code checks carried are given in NS 3473 Sec. 14.
ShellDesign performs ALS code checks when LS=ALS is specified in the DECAS statement.
Table 4. All material factors can be specified by the user in the CMPNS, RMPNS and TEMAT
statements. Default values of εcu and εsu correspond to those given in NS 3473 Sec. 11.3.
NS 3473 Sec. 14.1.1 states that the calculations can be performed according to the rules in
Sec. 12, hence the same design calculations as described in Section 4.3.3 apply also for ALS
in ShellDesign, but with different material factors.
4.2.4 NS - SLS Design
The rules and regulations for the SLS code checks carried out are given in NS 3473 Sec. 15.
ShellDesign performs SLS code checks when LS=SLS and/or LS=CRW is specified in the DECAS
statement.
Table 4. All material factors can be specified by the user in the CMPNS, RMPNS and TEMAT
statements.
4.2.4.1 NS - CRW - Crack widths calculation

Code check of crack widths (CRW) is performed taken into account all longitudinal and
prestressed reinforcement present in the section. Calculated crack widths are compared to

maximum allowable crack widths specified by the user in the CRWNS statement. Crack depths
66
are also calculated. The calculations are performed according to NS 3473 Sec. 15.2.4, 15.6
and A.15.6.2.1. The CRWNS statement must be included when crack widths and crack depths
should be calculated.
The calculated stresses are based on the same state of equilibrium established and described
in Section 4.3.3.2, using SLS material factors. The stress-strain relationships for concrete and
reinforcement are in accordance with Section 4.3.2, but a simplified (linear) stress-strain
diagram for normal weight concrete is used according to NS 3473 Sec. 15.1.2, where the
modulus of elasticity is taken as Eck. Compressive stresses and strains for lightweight concrete
are calculated based on the simplified diagram also used for ULS/ALS with modulus of elasticity
equal to 0.002/fcd (see Figure 4-7).
The tensile stresses in the concrete between the cracks are taken into account and included in
the state of equilibrium established according to the general method in NS 3473 Sec.
A.15.6.2.1 b). The mean tensile stress, β sftk, is used in the calculations where β s is set to a
default value of 0.4. The factor may be specified by the user in the CRWNS statement.
Water pressure in cracks is considered as described in 4.3.3.4, but where the water pressure
in cracks is only applied if the concrete strains exceed the cracking strain defined in NS 3473
Sec. 15.6.1.
Determination of uncracked or cracked sections

The criteria determining whether a section is cracked is according to NS 3473 Sec. 15.6.1 and
defined as:
𝑘𝑤 𝜎𝑁 + 𝜎𝑀 ⁡ < 𝑘𝑤 ⁡𝑓𝑡𝑛 /𝑘𝑡
The kt parameter is set to a default value of 1.0. The value of this parameter can be specified
by the used in the CRWNS statement. The following interpretation is made:
1. The principal strain directions are calculated at both faces of the cross sections; φface1
and φface2.
2. N(φface1), M(φface1) and N(φface2), M(φface2) are established and used for calculating
σN(φface1), σM(φface1), and σN(φface2), σM(φface2).
Calculation of crack widths for cracked sections

If a section is considered cracked, the following formulas applies.
The characteristic crack width for the longitudinal reinforcement is calculated according to NS
3473 Sec. 15.6.2 as:
𝑤𝑘 = 𝑙𝑠𝑘 (⁡𝜀𝑠𝑚 − ⁡ 𝜀𝑐𝑚 − 𝜀𝑐𝑠 )
εsm is calculated as the mean principal strain in the reinforcement. The calculation of εsm is
calculated with the contribution of concrete tensile strength of βsftk between the cracks
according to the general method in NS 3473 Sec. A.15.6.2.1 b).
εcm is calculated as βsftk/Eck according to the general method in NS 3473 Sec. A.15.6.2.1 b).
The free shrinkage strain, εcs, is set to zero, but can be included with CS= in the CRWNS
statement.
lsk is the influence length of the crack where a slip between reinforcement and concrete is
assumed to occur. For a stabilized crack pattern, thus length is taken to be equal to the
characteristic crack spacing according to NS 3473 Sec. A.15.6.2.1 a) as:

𝑓𝑡𝑘 67
𝑙𝑠𝑘 = 𝑆𝑟𝑘 = 1.7[𝑆𝑟𝑜 + ( )𝑘 𝑘 ℎ 𝑆 /(𝜋𝑛ø)
𝜏𝑏𝑘 𝑏 𝑐 𝑐𝑒𝑓 𝑏
sro = is set equal to the concrete cover defined in RETYP statement.
ftk /τbk = 0.75 . The factor may be changed in RETYP statement.
Acef = is the effective concrete area according to the figure below and equal b ∙h cef where b is
the width of the concrete section in mm and set to 1000 mm in ShellDesign.
hcef = the height of the effective concrete area = 2.5(h-d), where (h-d) is the distance from
the concrete surface on the tension side to the centre of gravity of the reinforcement. For
tension zone with reinforcement of single tensile bars in one layer, h cef = 2.5(c + φ/2).
hcef is less than the height of the tensile zone (h-x), where x is the distance from the concrete
edge on the tensile side to the neutral axis and h is the total cross-sectional height.
For double reinforce cross-sections with through going tensile stresses, hcef is calculated for
each side, hcef shall in this case never be larger than h/2.
kc = a coefficient which accounts for the strain distribution within the cross-section.
kc = (1 + εII/ εI)/2 where εII/ εI is the ratio between minimum and maximum strain in the
effective concrete area calculated for cracked cross-section. For a cross-section with through
going tensile stresses, kc =1.0. Note that the concrete section in ShellDesign is checked for
through going tensile stresses in all directions. If the maximum principal stress for each
concrete layer checked is larger than 1e-6, the layer is considered to have tensile stresses.

kb = 0.15 n + 0.85, a coefficient which accounts for reduced bond of bundled reinforcement.
68
c = the concrete cover for the reinforcement under investigation. Taken from RETYP
statement.
φ = the diameter of the reinforcement bar. Taken from the RETYP statement.
sb = the distance between reinforcement bars or bundles of bars, maximum value in the
calculation 15φ (for bundles of reinforcement 15φn1/2).
n = number of bars in a bundle. Taken from the RETYP statement.
c<(h-x).
If the principal strain deviates from the reinforcement direction, the crack spacing S rk in the
principal direction is calculated according to NS 3473 Sec. A.15.6.3 as:
1
𝑆𝑟𝑚 = ( )
𝑠𝑖𝑛⁡𝑣/𝑆𝑟𝑚𝑥⁡ ⁡ + ⁡𝑐𝑜𝑠⁡𝑣/𝑆𝑟𝑚𝑦
𝑤𝑘 is adjusted due to the nominal and real cover according to NS 3473 Sec. 15.2.4 as:
𝐶1
𝑤1𝑘 = 𝑤𝑜𝑘 ⁡
𝐶2
The crack widths for prestressed reinforcement are calculated according to NS 3473 Sec.
15.2.4 as:
𝜀𝑠2
𝑤2𝑘 = 𝑤1𝑘 ⁡
𝜀𝑠1
Where 𝜀𝑠1 is the tensile strain in the longitudinal reinforcement on the side with the largest
strain and 𝜀𝑠2 is the tensile strain at the level of the prestressed reinforcement (defined in
TELOC statement).
4.2.4.2 NS - Calculation of Crack Depths

The crack depth is calculated where each layer is checked according to the cracking criteria
specified in Section 4.2.4.1 If the layer is cracked, the thickness of this layer is included in
the crack depth. The calculation is carried out when LS=CRW is specified in the DECAS
statement.
In this check, the shell section is divided into layers of 0.01 m thickness by default. The number
of layers can be specified by the user with the N_LAY= parameter in the DEPAR statement if
more accurate results are required.
4.2.4.3 NS - Calculation of Compression Zone

Tightness is related to compression zones and specified in NS A.15.5. Calculated compression
zones are compared to minimum compression zones specified by the user in the TIGHT
statement. The calculation is carried out when LS=CRW is specified in the DECAS statement
and the results are shown in the UR=CZ table and/or graphical in plots.
The minimum allowable depth of the compression zone (CZ-min) is user input, where the CZ-
min is the lesser of X1 and X2*h, where h is the section thickness. If X2 is not input by the

user, only X1 parameter is used as minimum depth. Deafult values of X1 is 0.0 and default
69
value of X2 is 0.0.
the layer has compression or not. If both faces have ε p>0, the compression zone is set to zero.
In this calculation, the shell section is divided into layers of 0.01 m thickness by default. The
number of layers can be specified by the user with the N_LAY= parameter in the DEPAR
statement if more accurate results are required. Note that the layers will not be larger than
0.01 m.
Note that the non-linear sectional response is calculated with the concrete tensile strength, f ck.
in the DR table for CRW, as this crack depth is calculated based on the criteria described in
4.1.4.3.
4.2.4.4 NS - Through thickness cracks

Tightness may also be connected to limit crack widths for through thickness cracks. Although
this criteria is not explicit defined in NS, through-thickness cracks is calculated in ShellDesign
based on the following criterias. The calculation is carried out when LS=CRW is specified in the
DECAS statement and the results are shown in the UR=CT table and/or graphical in plots.
The tightness criteria are related to limit the crack widths to a value wk1, where wk1 varies with
the hydrostatic head to the wall thickness. The parameters must be specified by the user in
the TIGHT statement. Through thickness crack calculations are carried out for sections where
the section thickness is equal to the crack depth as calculated in 4.1.4.3.
4.2.4.5 NS - SLS - Stresses in reinforcement and concrete

The SLS code checks (SLS) are performed for the normal reinforcement, post-tensioned
reinforcement and concrete and are related to given maximum allowable stresses. The
calculated stresses are based on the same state of equilibrium established for ULS, using SLS
material factors. Tensile stresses in the concrete between cracks are not taken into account in
the design for the in-plane forces.
The stress-strain relationships for concrete and reinforcement are in accordance with Section
4.3.2, but a simplified (linear) stress-strain diagram for normal weight concrete is used
according to NS 3473 Sec. 15.1.2, where the modulus of elasticity is taken as Eck. Compressive
stresses and strains for lightweight concrete are calculated based on the simplified diagram
also used for ULS/ALS with modulus of elasticity equal to 0.002/fcd (see Figure 4-7). No code
checks for shear forces are performed in the SLS design calculations.

4.2.5 NS - FLS Design
70
The rules and regulations for the FLS code checks carried out are given in NS 3473 Sec. 13.
ShellDesign performs FLS code checks when LS=FLS is specified in the DECAS statement. In
addition, the FAPAR and WAVED statement must be included.
Table 4. The material factors can be specified by the user in the CMPNS, RMPNS and TEMAT
statements.
Default material factors used in the calculations are in accordance with the SLS values of the
material factors in NS 3473 Sec. 10.4, Table 4. All material factors can be specified by the
user in the CMPNS, RMPNS and TEMAT statements with the material factors MFF.
The code check is a stress range test based on a cumulative fatigue damage hypothesis,
modified Miner’s hypothesis. The requirements in this hypothesis are given in NS 3473 Sec.
13.1.2 and are as follows:
𝑘
𝑛𝑖
𝑚𝑠 = ∑ ≤𝜂
𝑁𝑖
𝑖=1
where: η: the degree of utilization for fatigue

The default value for η in ShellDesign is 0.5 (safety factor of 2.0).
4.2.5.1 NS - Stress-Strain Relations

The state of equilibrium is established assuming a linear distribution of concrete stresses within
the compression zone, where the modulus of elasticity for concrete is taken as EC=0.8*Eck.
Strains and stresses are calculated as for SLS, see Section 4.3.5.2, for both concrete and
reinforcement.
Due to a gradient of strains across the compressive zone, NS 3473 Sec. 13.3.2 permits an
increase of the reference value of the concrete compressive strength, frd:
𝑓𝑟𝑑 = 𝛼𝑓𝑐𝑑
where: 𝛼 = 1.3 − 0.3𝛽 ≥ 1.0
4.2.5.2 NS - In-Plane Stresses
Concrete compression failure:

The number of cycles, N, causing fatigue failure, is calculated according to NS 3473 Sec. 13.2.1.
The design life of concrete is as follows:
𝜎𝑚𝑎𝑥
1−
𝑓𝑟𝑑
𝑙𝑜𝑔𝑁 = 𝐶1 𝜎𝑚𝑖𝑛
1−
𝑓𝑟𝑑
where: 𝛼 = 1.3 − 0.3𝛽 ≥ 1.0
The value of the C1 parameter is set assuming that the construction is located in water. If the
calculated design life, 𝑙𝑜𝑔𝑁, is larger than the value given of:
𝐶1
𝑥=
𝜎𝑚𝑖𝑛
(1 − + 0.1𝐶1 )
𝑓𝑟𝑑

71
The design life, 𝑙𝑜𝑔𝑁, should be multiplied with:

𝐶2 = 1 + 0.2(𝑙𝑜𝑔𝑁 − 𝑥) > 1.0
As the direction of σmax will vary from block to block, this procedure implies that the
contribution to Miner’s sum is conservatively calculated for different directions and added
together.
The utilization ratio statement in ShellDesign is based on (face 1 and face 2):
𝑚𝑠1,2
𝑈𝑅1,2 =
𝜂
where ms and η is as defined in Section 4.3.6.1.
Reinforcement failure:
The verification of fatigue capacity of the reinforcement bars is based on stresses calculated
as for SLS.
The number of cycles, N, causing failure of reinforcement is calculated according to NS 3473

Sec. 13.2.2 as follows:
𝑙𝑜𝑔𝑁 = 𝐶3 − 𝐶4 𝑙𝑜𝑔∆𝜎
The default values of C3 and C4 are set to 19.6 and 6.0, respectively.
The utilization ratio statement for reinforcement in ShellDesign is based on:
𝑚𝑠
𝑈𝑅 =
𝜂
UR is assumed infinite if N>2*108.
4.2.5.3 NS - Design for Transverse Stresses

The design for transverse stresses is performed in accordance with the “one
dimensional”/uniaxial condition (Nα,Mα,Vα) and shear capacities are based on the “Simplified
method” as described in Section 4.3.3.3.

fatigue failure criteria equation described in the following.
Miner’s sum is calculated for all beams and the one achieving the highest value is deemed
governing, i.e represents the fatigue utilization of the shell section.
The number of cycles, N, causing fatigue tension failure in concrete is calculated according to
NS3473 Sec 13.4.1 as follows:

𝑉𝑚𝑎𝑥
1− 72
𝑉𝑐𝑑
𝑉𝑚𝑖𝑛
1−
𝑉𝑐𝑑
where Vcd is defined as in Section 4.3.3.3.
For those stress blocks where the shear force changes sign, the equation above becomes:
𝑉𝑚𝑎𝑥
1−
𝑉𝑐𝑑
𝑉𝑚𝑖𝑛
1+
𝑉𝑐𝑑

fatigue failure criteria described in the following.
The concrete carries a shear force proportional to the concrete contribution to the shear
𝑉𝑐𝑑
capacity (𝑉 = ).
Vcd is calculated according to NS 3473 Sec. 12.3.2, using a reduced tensile strength of the
concrete equal to 0.5*ftd as given in NS3473 Sec. 13.4.2.
Vsd is calculated according to NS 3473 Sec 12.3.2.4.
The number of cycles, N, causing fatigue failure is then calculated as for the “No shear
reinforcement method” described above.
The utilization ratio statement for concrete shear in ShellDesign is:
𝑚𝑠
𝑈𝑅 =
𝜂
The shear reinforcement carries a shear force proportional to the shear reinforcement
𝑉𝑠𝑑
contribution to the shear capacity (𝑉 = ).
Vcd and Vsd are calculated as described above. The stress range in the shear reinforcement is
calculated on this basis.
The number of cycles, N, causing fatigue failure is then calculated as in Section 4.3.6.3. The
default values of C3 and C4 are set to 15.9 and 4.8, respectively.
When the shear changes direction, the stress in shear reinforcement will always be tension.
This affects the number of cycles, i.e. the size and number of stress ranges experienced by
the shear reinforcement. This is accounted for in design.

The fatigue verification for compression failure is as prescribed in NS 3473 Sec. 13.4.3.

4.2.5.4 NS - Water Pressure in Cracks
73
The effect of water pressure acting in the cracks is included in the FLS code check as described
for ULS in Section 4.2.2.3 when WPARE and DWP=id in the DECAS statement are included.
Pore pressure for FLS can be included in the FAPAR statement with FA=f, in addition to
WPARE and DWP=id in DECAS statement. Pore pressure means water/gas present in pores
in the concrete also when compression is present in the design section. Note that pore
pressure with POR= in DECAS statement will not affect the FLS calculations, only ULS and ALS
as described in Section 4.2.2.3.

4.3 EuroCode 2 74
This Section describes the implementation of the EuroCode 2 design code, [4], (EC2) in
ShellDesign. Interpretations of rules and regulations and special features offered by
ShellDesign are explained. EC2 are implemented with parameters defined in the Norwegian
National Annex, but many parameters may be changed by the user.
ShellDesign performs design calculations based on EC2 when DEPAR D_COD=EC is defined in
the ShellDesign input file.
4.3.1 EC2 - Material properties
The material properties in ShellDesign are in accordance with EC2 Sec. 3 for normal and high
strength concrete and reinforcement, and Sec.11 for lightweight aggregate concrete. Creep
and shrinkage are not implemented.
4.3.1.1 EC2 - Concrete

The CMPEC statement is used for concrete material input.
The normal weight concrete is implemented according to EC2 Table 3.1, Sec. 3.1.6, 3.1.7 and
Figure 3.3. The figure is shown in Figure 4-11 below.
Figure 4-11: EC2 - Material curve in compression for normal weight concrete
The design compressive strength is defined as:
𝑓𝑐𝑑 = 𝛼𝐶𝐶 ⁡𝑓𝑐𝑘 /𝛾𝐶 ⁡⁡⁡⁡⁡⁡⁡
where αCC is default 0.85 according to the Norwegian National Annex. The factor may be
changed in the CMPEC statement
All the parameters in Figure 4-11 can be specified by the user in the CMPEC statement if
default values should not be used.
EC2 gives no regulations for reduction of the compression capacity for design sections where
there is tension in one principal direction and compression in the other principal direction. If
the user wants to include this effect, the same as defined in DNV-ST-C502 may be activated

by changing the TSD= parameter in CMPEC statement. For both normal and lightweight
75
concrete, the concrete compression capacity is hence reduced according to:
𝑓𝑐𝑑
0.8 − 100𝜀1
The minimum concrete capacity, fc2d, will be reduced to minimum TSD=tsd if the principal
tensile strain, ε1, is large enough. This reduction is applied for ULS, ALS and SLS (CRW).
Sec. 3.1.9 gives formulas for increasing the concrete capacity if there is compression in both
principal directions. This is however not implemented in ShellDesign and EC2.
Lightweight concrete is implemented according to EC2 Sec. 11.3.
4.3.1.2 EC2 - Reinforcement steel

The RMPEC statement is used for reinforcement input (both longitudinal and shear
reinforcement).
The reinforcement steel is implemented according to EC2 Sec.3.2 and the idealized curve in
Figure 3.8. The figure is shown in Figure 4-13 below.
Figure 4-12: EC2 - Material curve in tension/compression for reinforcement steel
The reinforcement material exhibits the same behavior in both tension and compression. The
design strength is defined as:
𝑓𝑦𝑑 = 𝑓𝑦𝑘 /𝛾𝑆 ⁡⁡⁡⁡⁡⁡⁡
where the value fyk must be input by the user. By default Es is 200 MPa and εud is 0.10% (fyd/Es
for SLS). The maximum stress at εud is default the same as fyd, but may be changed by the
user in the RMPEC statement.
4.3.1.3 EC2 – prestressing steel

In ShellDesign, the prestressing steel is implemented as a linear curve as shown in Figure 4-14
below where fsy and Esk is input in the TEMAT statement. In addition, the initial strain, ε0,
(prestressing strain) must be defined for each type of prestressed tendon. This parameter is

defined in the TETYP statement and when prestressing steel is utilized as ordinary
76
reinforcement, only the material curve starting from ε0 is utilized.
Figure 4-13: EC2 - Material curve for prestressed reinforcement steel
4.3.2 EC2 - ULS Design
The rules and regulations for the code checks carried out are given in EC2 Sec. 6. ShellDesign
performs ULS code checks when LS=ULS is used in the DECAS statement.
Default material factors used in the calculations are in accordance with the Norwegian National
Annex Sec. NA.2.4.2.4 Table NA.2.1N. The material factors can be specified by the user in the
CMPEC, RMPEC and TEMAT statements.
and concrete are related to given maximum allowable stresses and strains. The calculated
stresses are based on the state of equilibrium established for the in-plane forces. The stress-
strain relationships for concrete and reinforcement are in accordance with Section 4.4.2.
Tensile stresses in the concrete between cracks are not considered in the design for the in-
plane forces. However, Section 4.5 describes a design method available in ShellDesign where
the tensile stresses in the concrete between cracks are considered. The design method
implemented is the Modified Compression Field Theory (MCFT) [5].
reinforcement are based on the methods described in Section 4.4.3.3, where utilizations are
calculated based on the actual shear capacity.
Minimum eccentricity of membrane forces given in EC2 Sec. 6.1(4) is not automatically
included in the calculations. Eccentricities may be specified by the user in the LDFAC statement.
Limitations of the concrete strain in concentrically loaded parts of a cross-section, as stated in

EC2 Sec. 6.1(5), is not included in the calculations.
Capacity calculations are based on the entire concrete area of a section, disregarding the
reduction in concrete area due to large compression reinforcement amounts.

4.3.2.1 EC2 - Design for in-plane forces
77
The design for in-plane forces are implemented according to EC2 Sec. 6.1. The in-plane forces
include the six section forces N1, N2, N12, M1, M2 and M12 as shown in Figure 4-5. The
M 12
face 2 V2
(+ 3 face )
3. N2
M2
N 12
2.
V1
N 12
1.
N1
face 1 M1
(- 3 face) M 12
Figure 4-14: EC2 - The in-plane forces and corresponding strains in a shell section
See Section 4.5 for a design method available in ShellDesign where the transverse forces, V1
and V2, are included in the non-linear sectional response. The design method implemented is
the Modified Compression Field Theory (MCFT) [5].
statement.

4.3.2.2 EC2 - Design for transverse Stresses
78
The design for transverse stresses is performed according to the procedures in EC2 Sec. 6.2.1,
Sec. 6.2.2 and Sec. 6.2.3.
formulas are implemented. The design value of the shear force is calculated according to the
eq. in the note in EC2 Sec. NA.6.2.2:
0.5
𝑉𝜑 = (𝑉1 2 + 𝑉2 2 )
and the direction of principal shear is found as:
𝑉2
tan 𝜑 =
𝑉1
The “one dimensional”/uniaxial condition is established for the principal direction φ0. The
formulas applied, and used in the following pages, are:
𝑁φ = 𝑁1 cos(φ)2 + 𝑁2 sin(φ)2 + 2𝑁12 sin⁡(φ)cos⁡(φ)
𝑀φ = 𝑀1 cos(φ)2 + 𝑀2 sin(φ)2 + 2𝑀12 sin⁡(φ)cos⁡(φ)
𝐴𝑠φ = 𝐴𝑠𝑥 ⁡𝑐𝑜𝑠(φ)2 + 𝐴𝑠𝑦 ⁡𝑠𝑖𝑛(φ)2
Shear capacity of members not requiring design shear reinforcement

The shear capacity of members not requiring design shear reinforcement is calculated
according to EC2 Sec. 6.2.2 and applies as follows:
1
𝑉𝑅𝑑,𝑐 = max [[𝐶𝑅𝑑,𝑐 ⁡𝑘⁡(100⁡𝜌𝐼⁡ 𝑓𝑐𝑘 )3 + 𝑘1 ⁡𝜎𝑐𝑝 ]𝑏𝑤 𝑑⁡⁡⁡;⁡⁡⁡[𝑉𝑚𝑖𝑛 + ⁡ 𝑘1 𝜎𝑐𝑝 ]𝑏𝑤 𝑑⁡]]⁡⁡
where:
200
𝑘 = 1 +⁡√ ≤ 2.0⁡
𝑑
𝑑 = effective⁡depth⁡of⁡cross⁡section⁡in⁡meter.⁡
d⁡is⁡taken⁡as⁡the⁡distance⁡from⁡compression⁡side⁡to⁡the⁡first⁡reinforcement⁡layer⁡at⁡the⁡opposite⁡face.⁡
If⁡M = 0, d⁡is⁡taken⁡as⁡the⁡distance⁡between⁡the⁡two⁡outside⁡reinforcement⁡layers⁡at⁡face⁡1⁡and⁡face⁡2.⁡
𝐴𝑠𝑙
𝜌𝐼 = ⁡ ≤ 0.02⁡
𝑏𝑤 𝑑
𝑏𝑤 = width⁡of⁡beam⁡and⁡1m⁡in⁡ShellDesign
𝐴𝑠𝑙 = the⁡cross⁡sectional⁡area⁡of⁡the⁡tensile⁡reinforcement⁡on⁡the⁡side⁡with⁡largest⁡tension.⁡
If⁡M = 0, the⁡cross⁡sectional⁡area⁡is⁡the⁡average⁡of⁡the⁡reinforcement⁡at⁡face⁡1⁡and⁡face⁡2.
𝑁𝜑
𝜎𝑐𝑝 = ⁡ ≤ 0.2⁡𝑓𝑐𝑑⁡ where⁡𝑁𝜑 ⁡is⁡positive⁡for⁡compression⁡
𝐴𝑐
𝐴𝑐 = area⁡of⁡concrete⁡cross⁡section⁡
𝑘2 0.15
𝐶𝑅𝑑,𝑐 = = ⁡⁡⁡where⁡k 2 ⁡⁡may⁡be⁡changed⁡in⁡CMPEC⁡statement⁡
𝛾𝑐 𝛾𝑐

𝑘1 = 0.15⁡if⁡compression;⁡0.3⁡if⁡tension
79
𝑉𝑚𝑖𝑛 = 0.035⁡𝑘 2/3 ⁡⁡𝑓𝑐𝑘 1/2 ⁡⁡where⁡fck ⁡is⁡not⁡larger⁡than⁡65⁡MPa⁡
If the occurring shear force, Vφ, exceeds VRd,c, design shear reinforcement will be required.
The regulations in EC2 Sec. 6.2.2(2) is not included in the design calculations.
EC2 Sec. 6.2.2(6) eq. 6.5 is not included in the design calculations. Instead, the shear
compression capacity is calculated as for sections requiring shear reinforcement, according to
EC2 Sec. 6.2.3(3) eq. 6.9 (see section below). This approach is conservative as EC2 Sec.
6.2.3(3) eq. 6.9 will always yield a lower shear capacity than EC2 Sec. 6.2.2(6) eq. 6.5.
Shear capacity of members requiring design shear reinforcement

The shear capacity of members requiring design shear reinforcement is calculated according
to EC2 Sec. 6.2.3 eq. 6.8 and eq. 6.9 as:
𝐴𝑠𝑤
𝑉𝑅𝑑,𝑠 = min [⁡ 𝑧⁡𝑓𝑦𝑤𝑑 ⁡𝑐𝑜𝑡𝜃⁡⁡⁡;⁡𝛼𝑐𝑤 𝑏𝑤 𝑧⁡𝑣1 𝑓𝑐𝑑 ⁡/(cot 𝜃 + tan 𝜃)⁡]⁡⁡
𝑠
where:
𝐴𝑠𝑤
= ⁡the⁡input⁡to⁡SD⁡for⁡shear⁡reinforcement⁡in⁡m2/m2)
𝑠
𝑓𝑦𝑤𝑑 = design⁡yield⁡strength⁡of⁡reinforcement
𝑧 = inner⁡lever⁡arm,⁡usually⁡0.9d
𝑓𝑐𝑘
𝑣1 = 0.6(1 − )
250
In⁡sections⁡without⁡compression:
𝛼𝑐𝑤 = 1⁡⁡
In⁡sections⁡with⁡compression:
𝜎𝑐𝑝
𝛼𝑐𝑤 = (1 + ⁡) ⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡if⁡⁡0 < ⁡ 𝜎𝑐𝑝 ⁡ ≤ 0.25⁡⁡𝑓𝑐𝑑 ⁡
𝑓𝑐𝑑
𝛼𝑐𝑤 = 1.25⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡if⁡⁡0.25 < ⁡ 𝜎𝑐𝑝 ⁡ ≤ 0.5⁡⁡⁡𝑓𝑐𝑑 ⁡
𝜎𝑐𝑝
𝛼𝑐𝑤 = 2.5 (1 − ⁡) ⁡⁡⁡⁡⁡if⁡⁡0.5 < ⁡ 𝜎𝑐𝑝 ⁡ ≤ 1.0⁡⁡⁡𝑓𝑐𝑑 ⁡
𝑓𝑐𝑑
𝜎𝑐𝑝 = is⁡the⁡mean⁡compressive⁡stress⁡in⁡the⁡section⁡
due⁡to⁡design⁡axial⁡force,⁡positive⁡for⁡compression,
taking⁡the⁡reinforcement⁡into⁡account.⁡
The⁡reinforcement⁡is⁡not⁡taken⁡into⁡account⁡in⁡ShellDesign.⁡
𝜃 = is⁡the⁡angle⁡between⁡the⁡concrete⁡compression⁡strut⁡
and⁡the⁡beam⁡axis⁡perpendicular⁡to⁡the⁡shear⁡force⁡and⁡can⁡be⁡set⁡to⁡
1⁡ ≤ cot 𝜃 ≤ 2.5
cot 𝜃 ⁡is⁡default⁡2.5⁡(21.8°)⁡in⁡ShellDesign,⁡but⁡may⁡be⁡changed⁡by⁡the⁡user⁡in⁡CMPEC⁡statement.⁡
21.8°⁡will⁡give⁡the⁡highest⁡shear⁡capacity⁡for⁡expression⁡(6.8)⁡for⁡the⁡shear⁡reinforcement.⁡
NB!⁡The⁡designer/project⁡must⁡decide⁡which⁡angle⁡that⁡should⁡be⁡used.⁡
Note⁡that⁡if⁡ cot 𝜃 ⁡is⁡defined⁡larger⁡than⁡1.25⁡and⁡𝜎𝑡 ≥ 𝑓𝑐𝑡𝑘,0,05
cot 𝜃 ⁡is⁡changed⁡to⁡1.25⁡according⁡to⁡EC2⁡Sec. NA6.2.3⁡eq. NA. 6.7. bN.

80
The maximum effective cross-sectional area of shear reinforcement is calculated as:
𝐴𝑠𝑤,𝑚𝑎𝑥⁡ ⁡𝑓𝑦𝑤𝑑 1
⁡ ≤ ⁡ ⁡𝛼𝑐𝑤 ⁡𝑣1⁡ ⁡𝑓𝑐𝑑
𝑏𝑤 ⁡𝑠 2
ShellDesign does not include inclined shear reinforcement as defined in Sec. 6.2.3(4).
Additional forces in the longitudinal reinforcement due to shear forces, ref. EC2 Sec. 6.2.3(7),
are not automatically accounted for in ShellDesign, but may be included in the design
calculations with STFOR and DECAS statement. The additional forces included in the design
calculations are calculated according to annex LL in Eurocode 2: Part 2 Concrete bridges [8]:
where
0.5
𝜗𝐸𝑑𝑜 = 𝑉𝜑 = (𝑉1 2 + 𝑉2 2 )
𝜗𝐸𝑑𝑥 = 𝑉1
𝜗𝐸𝑑𝑦 = 𝑉2
Note also that these additional forces in the longitudinal reinforcement due to shear forces are
implicit taken into account in the MCFT described in Section 4.5.
4.3.2.3 EC2 - Water Pressure in Cracks

established in Section 4.4.3.2 when the WPARE statement is included in the ShellDesign input
file and when DWP= is included in the DECAS statement. Note that water pressure in cracks
can be included as a load case in the CSM analyses. See NONLI, WPARE and DECAS
statement.
Water pressure is let into potential pores/cracks when concrete tension is present, ε>0.
Sectional forces due to water pressure in cracks are added to the given sectional forces.

Through repeated iterations, a state of equilibrium is established, accounting for simultaneous
81
development of cracks and water pressure effects.
4.3.3 EC2 - ALS Design
The rules and regulations for the ALS code checks carried are the same calculations as
described in Section 4.4.3 for ULS design but with different material factors. ShellDesign
performs ALS code checks when LS=ALS is specified in the DECAS statement.
4.3.4 EC2 - SLS Design
The rules and regulations for the code checks carried out are given in EC2 Sec. 7. The section
covers the common serviceability limit states. These are:
— stress limitation
— crack control
— deflection control
Other limit states (such as vibrations) may be of importance but are not covered in EC2.
ShellDesign performs SLS code checks when LS=CRW or LS=SLS is specified in the DECAS
statement, where ShellDesign performs calculations regarding crack control and tightness
when LS=CRW is specified. The LS=SLS check is only related to stresses in concrete and
reinforcement.
4.3.4.1 EC2 - Calculation of uncracked or cracked sections

The criteria determining whether a section is cracked or uncracked is not specified in EC2 and
is in ShellDesign defined as uncracked if the principal stress σ1 is compressive stress. Note
that this procedure is different for DNV-ST-C502 and NS 3473 where formulas for uncracked
sections are given.
4.3.4.2 EC2 - CRW – calculation of crack widths – crack control

Limitation of cracking is performed taken into account all longitudinal and prestressed
reinforcement present in the section. Calculated crack widths are compared to maximum
allowable crack widths specified by the user in the CRWEC statement.
The check is carried out when LS=CRW is specified in the DECAS statement. The calculations
are performed according to EC2 Sec. 7.3.4. The CRWEC statement and DCW= in the DECAS
statement must be included when crack widths and crack depths should be calculated.
The crack width for the longitudinal reinforcement is calculated according to EC2 Sec. 7.3.4(1)
and 7.3.4(2):

𝑤𝑘 = 𝑠𝑟,𝑚𝑎𝑥 (⁡𝜀𝑠𝑚 − ⁡ 𝜀𝑐𝑚 )
82
where:
𝑓𝑐𝑡,𝑒𝑓𝑓
𝜎𝑠 − 𝑘𝑡 (1 + 𝛼𝑒 𝜌𝑝,𝑒𝑓𝑓 )
𝜌𝑝,𝑒𝑓𝑓 0,6𝜎𝑠
𝜀𝑠𝑚 − ⁡𝜀𝑐𝑚 = ⁡ ⁡≥⁡
𝐸𝑠 𝐸𝑠
σs = is the stress in the tension reinforcement in a cracked section (no tension stiffening
included).
αe = Es/Ecm
ρp,eff=(As+ ξ12 Ap, ) / Ac,eff
fct,eff = fctm
Ap, = area of prestressing within Ac,eff
Ac,eff = is the effective area of concrete in tension surrounding the reinforcement or prestressing
tendons of depth, hc,ef , where hc,ef is the lesser of 2,5(h-d), (h-x)/3 or h/2 (see Figure 7.1),
but not lesser than (h-d+1.5φ).
ξ1 = is the adjusted ratio of bond strength taking into account the different diameters of
𝜑𝑠
prestressing and reinforcing steel: = √𝜉 . ξ ratio of bond strength of prestressing and
𝜑𝑝
reinforcing steel,according to Table 6.2 in 6.8.2. φs largest bar diameter of reinforcing steel φp
equivalent diameter of tendon according to 6.8.2. If only prestressing steel is used to control
cracking, 𝜉1 = √𝜉
kt = 0.4 ,but may be changed in the CRWEC statement.
The maximum crack spacing, sr,max, is calculated according to Sec. 7.3.4(3) as:
𝑘1 𝑘2 𝑘4 𝜑
𝑠𝑟,𝑚𝑎𝑥 = 𝑘3 𝑐 +
𝜌𝑝,𝑒𝑓𝑓
Where:
φ = bar⁡diameter⁡defined⁡in⁡RETYP⁡statement
c = cover⁡to⁡the⁡longitudinal⁡reinforcement⁡defined⁡in⁡RETYP⁡statement
𝑘1 = 0.8⁡, but⁡may⁡be⁡changed⁡in⁡CRWEC⁡statement
𝑘2 = 0.5⁡⁡⁡⁡⁡⁡⁡if⁡the⁡principal⁡strain⁡at, at⁡least⁡one⁡face, is⁡compression
𝜀1 + ⁡ 𝜀2
𝑘2 = ⁡ ⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡if⁡the⁡principal⁡strain⁡at⁡both⁡faces⁡is⁡tension
2𝜀1
𝑘3 = 3.4
𝑘4 = 0.425
𝑓 = 𝑋⁡, but⁡the⁡facor⁡may⁡be⁡changed⁡in⁡the⁡CRWEC⁡statement.⁡

83
c<(h-x). This is implemented according the same regulations in NS 3473 to avoid an unrealistic
large crack spacing.
If the principal strain deviates from the reinforcement direction, the maximum crack spacing,
Sr,max, in the principal direction is calculated according to EC2 Sec. 7.3.4(4):
1
𝑆𝑟,𝑚𝑎𝑥 = ( )
𝑠𝑖𝑛⁡𝑣/𝑆𝑟,𝑚𝑎𝑥,𝑥⁡ ⁡+ ⁡𝑐𝑜𝑠⁡𝑣/𝑆𝑟,𝑚𝑎𝑥,𝑦
where ν is the angle between the reinforcement in the y direction and the direction of the
principal tensile stress.
4.3.5 EC2 - FLS Design
Not included in ShellDesign. Can be implemented based upon request.

4.4 Modified Compression Field Theory (MCFT) 84
Based on the shortcomings of the shear design methods found in current design codes,
Dr.techn.Olav Olsen (OO) was motivated to implement a design method that enables a
consistent and rational shear design. The new method had to include in-plane forces and
transverse shear forces in the non-linear sectional response, and it was concluded that the
"Modified Compression Field Theory" (MCFT) [9] was the most suitable model for
implementation.
MCFT has been developed at the University of Toronto and is a method capable of predicting
the shear response of cracked reinforced and prestressed concrete. MCFT is based on principal
stresses and strains. Tension stiffening is included through average stresses by adding post-
cracking tensile stresses to the stress-strain curve of the concrete. Modelling tension stiffening
by averaged stresses requires the inclusion of a “crack check”. The crack check ensures that
no concrete tensile stresses are necessary to obtain equilibrium at the location of a fully
developed crack.
The implementation of MCFT in SD is mostly based on the work of Bentz [10]. The
implementation of the MCFT has already been done by Bentz for both 2D and 3D through the
Response-2000 and Shell-2000 programs. The technique has been successfully applied in SD,
both for 2D and 3D, and it is possible to display shear stress profiles through the section depth.
The verification of MCFT in SD is performed against the existing analysis program Shell-2000,
two of the design codes used today, NS 3473 [3] and Eurocode 2 [4], and experimental results.
The verification shows that the implementation in SD correlates well with the existing analysis
program. Compared to results from existing design codes, expected differences have been
revealed. When comparing the results of SD against experimental results, the difficulties in
predicting the shear capacity of reinforced concrete structures is evident. However, the results
are reasonably close to the experimental observations and in general conservative.
MCFT in SD reflects a consistent and rational shear design and will, in addition to providing a
more correct answer, give engineers a tool that increases the understanding of the structure's
behavior.
ShellDesign performs design calculations based on MCFT when DEPAR D_COD=GM is defined
in the ShellDesign input file. The material data is defined with the CMPGM and RMPGM
statements. If CSM analysis is also wanted A_COD=GM must be included in DEPAR as well.
4.4.1 MCFT - Method description
MCFT is based on principal stresses and strains. In each material point (design section) in
question, principal strains are calculated and the corresponding material stress in each
direction is found from uniaxial stress-strain curves through numerical iterations. The response
from all applied loads is directly captured and evaluated on a material level, thus the use of
simplified and inaccurate shear design methods found in existing design codes is avoided.
The stress-strain curves are expressed in terms of average values, representing the integrated
response of a finite area of the concrete. The inhomogeneous nature of concrete is therefore
not modelled directly. Some important assumptions in MCFT, along with consequent
implications, are listed in Table 4-2.

Table 4-2: Assumptions in MCFT and implication for design
85
Assumption Implication
For each state of strain there exists only one Reversed loading and load history is not taken
corresponding stress state. into account.
Stresses and strains can be considered in The area associated with each design section
terms of average values when taken over should be larger than the crack distance.
areas or distances large enough to include
several cracks.
The concrete and the reinforcing bars are Anchorage breaks and bond strength are not
perfectly bonded together. taken into account.
The effect of the reinforcement is smeared Variations in reinforcement arrangement

across the section width. across the width of a design section is not
taken into account.
The reinforcement is assumed only to have Dowel action of reinforcement is not taken
normal stiffness, i.e. no shear stresses are into account. Neglecting dowel action is
directly resisted by the reinforcing bars. conservative.
The direction of principal strains and principal Local deviations between the stress and strain
stresses are assumed to coincide, and cracks directions are not predicted.
open in the direction of the principal tensile
strain.
Uncracked concrete is treated as a linear-elastic material in MCFT. Thus, the elastic modulus
completely defines the material behaviour prior to cracking. When the concrete cracks, the
material behaviour is more complex. In compression, the concrete response softens and the
presence of any lateral tensile stresses reduces the ultimate stress and the corresponding
strain.
Treating the concrete behaviour in this way is not exclusive to MCFT, as most present design
codes are able to reproduce the compression response of concrete with sufficient accuracy.
However, the response in tension is usually simplified by neglecting the tensile strength of
concrete and ascribing the entire tensile capacity of a section to the reinforcement. Thus
overlooking the tension stiffening effect which is an important effect in predicting the stiffness
of reinforced concrete.
Tension stiffening is best explained through the example of a single un-casted reinforcement
bar. When stretched, the response of the bar can be illustrated by the lower of the stress-
strain curves in Figure 4-17, as is expected for a steel bar. If the bar is cast in concrete, as
illustrated in Figure 4-16 and stretched, the response can be illustrated by the upper of the
stress-strain curves in Figure 4-17. The influence of bond between concrete and reinforcement
allows multiple minor cracks to form along the bar. Concrete tensile stresses are transferred
across these minor cracks, as well as in the un-cracked concrete in between the cracks.
These tensile stresses stiffen the bar response, and the integrated effect is called tension
stiffening. At the location of a fully developed crack, no tensile stresses can be transferred
through the concrete, and thus the ultimate capacity of the bar is determined by the steel
capacity alone and is therefore unchanged. In other words, the bar response is stiffer when
cast in concrete compared to a un-casted bar, but the ultimate bar capacity is equal to the
capacity without concrete.

86
Figure 4-15: MCFT - Cracking along a reinforcement bar
Figure 4-16: MCFT - Tension stiffening in concrete
Neglecting tension stiffening will not yield the correct stiffness in a concrete structure. In MCFT,
tension stiffening is included through average stresses by adding post-cracking tensile stresses
to the stress-strain curve of the concrete as shown in Figure 4-18.
Figure 4-17: MCFT - Average stress-strain curve of concrete
Modelling tension stiffening by averaged stresses requires the inclusion of a “crack check”. The
crack check ensures that no concrete tensile stresses are necessary to obtain equilibrium at
the location of a fully developed crack, as no concrete tensile stresses can be transferred
through the crack when the strain exceeds the crack strain. Once cracking has been initiated,
the calculated average tensile stresses in the concrete, illustrated by f c1 to the left in Figure
4-19, are transferred across a crack either by increasing the calculated average reinforcement
stresses or by including shear stresses on the crack, as illustrated by fscr and vci to the right in
Figure 4-19, respectively.

87
Figure 4-18: MCFT - Average vs. crack stresses
Shear stresses on a crack surface are caused by intermediate sliding of the crack surfaces
resisted by the aggregate particles in the concrete, a phenomenon termed “aggregate
interlock”. The occurrence of such a sliding motion contradicts the assumption that cracks
open in the direction of the principal tensile strain. Thus, a local rotation of the stresses at a
crack is necessary after the opening of a crack, although this rotation is not explicitly estimated
in MCFT.
The amount of shear that can be transferred through aggregate interlock is determined by the
aggregate size, the crack width and the amount of compressive stresses across the crack.
Transferring of stresses across cracks is a complex mechanism and no single solution is the
correct one. In short, the task at hand is to find a statically equivalent system at the crack,
illustrated to the right in Figure 4-19, to that calculated for the average stresses, illustrated to
the left in Figure 4-19. This statically equivalent system in the crack check is quite straight
forward to implement for two-dimensional cases, but when extending the crack check to the
three-dimensional case, the complexity increases.
4.4.2 MCFT - Experimental verification and history
Since the original development of MCFT in 1986, the theory has been extensively tested
against experiments and implemented in numerous finite element algorithms. Today, the
theory is widely accepted as a rational approach towards safe shear design of reinforced
concrete structures. The original MCFT was based on a series of tests on reinforced concrete
panels subjected to in-plane forces [9].
The formulation was given for two-dimensional stress conditions. Suggestions for the
extension of MCFT to three-dimensional stress conditions have been published by Vecchio and
Selby in 1991 [11] and by Adebar and Collins in 1994 [12], among others. Numerous analytical
shear design methods have also been formulated based on MCFT [13, 14, 15, 16, 17] to
eliminate the shortcomings of various shear provisions found in design codes.

Recently, MCFT was implemented in a series of sectional analysis programs developed by Bentz
88
[10], capable of calculating the response of membranes, shells, and tri-axially loaded concrete
sections.
4.4.3 MCFT - Limitations
Some limitations to the use of MCFT in SD exist and the most important ones are listed below.
1. The implementation of a strain-based estimation of tension stiffening will yield un-conservative

predictions of the strength of deep, sparsely reinforced members. Predicting the capacity of such
members demands a consideration, and possibly an adjustment, of the tension stiffening effect
across the depth of the member.
2. Non-orthogonal reinforcement is not yet supported, i.e. the reinforcement must be placed in the 1,
2, 3 axis system in SD.
3. No confinement effects on the compression response of concrete is included in the implementation.
4. No downward adjustment of the tensile strength of the concrete is performed. This may cause
insufficient capacity of reinforcement in the crack check of some sections, when a non-linear finite
element analysis is performed. In such an analysis it may be more appropriate to reduce the tensile
strength of the concrete to allow for redistribution of forces to occur, and thus lower the stresses
that are transferred to the reinforcement in the crack check. The current version of SD does not
perform such an adjustment.
5. No hardening or strain beyond the yield strain is allowed for the shear reinforcement material. Thus,
the response of the shear reinforcement is purely elastic. Allowing the shear reinforcement to yield
and consequent large shear strains to occur, is not desirable due to the brittle nature of shear
failures.

5 FEATURES IN SHELLDESIGN 89
5.1 Shell Sections – Design Sections

A shell section is, by definition, a line through the shell/membrane/plate structure, in most
cases perpendicular to the middle surface. All design calculations refer to the shell sections,
also called design sections.
The identity of a shell section consists of three items:

▪ Part id. (up to 8 characters)
▪ F-section no. (range 1 to 999)
▪ H-section no. (range 1 to 999)
When ShellDesign is used independently of a finite element analysis, the design sections are
defined by the user through the program input file.
When ShellDesign is used in connection with a finite element analysis, the design sections are
related to the stress points (Gauss-points) of the finite elements. The finite element mesh,
together with the element type, decides the section mesh. In addition, extrapolated design
sections may be created, normally at boundaries and fixations. See Figure 5-1.
Figure 5-1: Shell Sections/Design Sections in a FE model

To start generation of sections, the start element is defined together with F and H generation
90
directions. Alternatively, the start element coordinates may be given instead of the element
number.
For both the 8 nodes shell element and the 20 nodes solid element, there are 8 stress points
in one element, but 2 of the stress points are located at the same “line” through the element
thickness, hence only 4 design sections; the design section is a section through these pairs of
Gauss points. Within each design section, the stress distribution is assumed to vary linearly
over the element thickness and determined by the stresses in the Gauss points.
The design section properties are calculated in ShellDesign, based on the element geometry
and user defined parameters for geometry adjustment if necessary. The concrete geometry is
described with the thickness h and thickness variation parameters t11, t12, t21, t22. The meaning
of the thickness parameters in the shell section is explained below and in Figure 5-2.
 h2  h1  h2  h1
t 21 = t 11 = t 22 = t 12 =
 x1  x1  x2  x2
Figure 5-2: Concrete geometry in a shell section
In addition, a local coordinate system for each design section must be defined by the user,
called the 1, 2, 3 axis system. It is common practice to define the local axis system to
correspond to the direction of the reinforcement. The 1, 2, 3 axis system is more explained in
section 2.2.
The main tasks when generating design sections in connection with a FE-model may be as
follows:
• Find the location of all wanted design sections, called F-sections and H-sections.
• Decide where to position extrapolated sections.
• Determine the main reinforcement directions.
• Generate design sections.
• Generate extrapolated sections
• Define a local coordinate system, 1, 2, 3 axis-system, based on the reinforcement
directions.
• Verify the design section geometry including local 1,2,3 axis directions.

The generation of design sections are specified through the SHSEC statement, the generation
91
of extrapolated sections are specified through the SHEXT statement and the 1, 2, 3-axis are
specified through the SHAXE statement.
5.2 Shell Sectional Stress Resultants – Section Forces

The shell sectional stress resultants, also denoted section forces, are forces and moments in a
shell section (design section). The section forces for a shell section are:
N1 N2 N12 M1 M2 M12 V1 V2
The stress resultants are expressed in units of force/moment per unit length (kN/m and
kNm/m), instead of the true force and moment as the case for beams.
The section forces refer to the local section coordinate system, the 1, 2, 3-axis system, defined
by the user. This coordinate system defines hence the basis for all design results.
The relationship between the 1, 2, 3-axis and the section forces are shown in the figure below.
M 12
face 2 V2
(+ 3 face )
3. N2
M2
N 12
2.
V1
N 12
1.
N1
face 1 M1
(- 3 face) M 12
Figure 5-3: Section Forces in a shell section. The element is infinitesimal
When ShellDesign is used independently of a finite element analysis, the section forces are
defined by the user through the program input file, see Section 3.1
When ShellDesign is used in connection with a finite element analysis, the section forces are
related to the stress points (Gauss-points) of the finite elements (design sections) and refer
to the local 1, 2, 3-axis. ShellDesign first prepares the FEM results by calculation of design
section geometry and shell section forces before further design calculations are carried out.
The main tasks when ShellDesign reads stresses from a FE analysis are:
• Transform stresses to the local coordinate system (1, 2, 3).

• Integrate stresses to stress resultants, section forces.
• Extrapolate stress resultants to extrapolated sections.
Please note the definition of face 1 and face 2 of the shell:

▪ The 3-axis points from face 1 towards face 2. See Figure 5-3
92
The units of the stress resultants are presumed to be

▪ membrane forces : kN/m
▪ plate moments : kNm/m
▪ transverse shear : kN/m
Note that the default input to the FE analysis should be kN, m and tonnes. If other units are
applied, the LUN and FUN parameters in RFILE statement must be used. Note that for CMS
analyses, the input must be defined in kN, m and tonnes.
5.3 Strain components in a Shell Section

The strain components for a shell section are:
ε1, ε2, γ12, γ13, γ23, Κ1, Κ2, Κ12
The relationship between the strain components and the 1, 2, 3 - axis is shown in Figure 5-4.
For linear elastic behaviour, where the material is linear, the connection between these strain
components and the stress resultants in Section 5.2, is found through linear elastic formulas.
However, when the stress-strain relations for concrete and reinforcement is non-linear, the
connection between the strain components and the stress resultants are based on stress-strain
curves specified in the current design codes and iteration procedures. See Section 4 for more
information of the procedures of calculations of these strain components.
Figure 5-4: Strain components in a shell section

5.4 Node Displacements 93
Node displacements refers to the global coordinate system of the finite element analysis
(X,Y,Z).
The node displacements for a shell section are:
Displacement Description
Δx translation x - direction (defined in analysis)
Δy translation y - direction (defined in analysis)
Δz translation z - direction (defined in analysis)
The units of displacements are:

▪ translations :m
5.5 Load Cases

ShellDesign defines the following load cases:
▪ OLC : Original Load Case

▪ ELC : Equilibrium Load Case
▪ ILC : Input Load Case
▪ PLC : Prestressing Load Case
▪ BAS : Basic combination
OLC: Load cases from a finite element analysis.
ELC: Load cases derived from the OLC’s, but where structure equilibrium (through the use
of load cases only) has been established.
ILC: Load cases defined by the user through input.
PLC: Load cases defined to include the prestressing effect from prestressed reinforcement.
BAS: Load cases defined by scaling and combining load cases.
All the load cases above includes the 8 section forces, N1, N2, N12, M1, M2, M12, V1 and V2.
5.5.1 OLC – Original Load Case
The OLC’s are load cases retrieved from the finite element analysis and are the load cases
stored on OLC-file(s) if such file is attached to a ShellDesign run. See section 2.8.1 for more
information about OLC-files. It is useful to create OLC files when the structure is large and
there are many load cases. In addition, different OLC files generated from different global
analyses may be merged to one OLC-file to account for results from different construction
phases.
As the ShellDesign model is divided in different Parts, it is common practice to create OLC files
for each Part respectively. These OLC files are later referenced in the ShellDesign input file.

94
It is also common practice to rename the analysis load case (ALC) numbers to new load case
(OLC) numbers in ShellDesign with the LOADC statement to define different load groups, e.g
water pressure load cases have numbers between 1200-1299. Example of ShellDesign input
is shown below:
% -------------------------------------------------------------------------------------------
% ALC TO OLC=
% -------------------------------------------------------------------------------------------
%
% LOADC ALC_nr = OLC=_nr
LOADC RN=1 LC=1,1200 % Hydro pressure up to elevation 123.000m (Wadam)
LOADC RN=1 LC=2,1100 % Global Uniform Acceleration (1.0*G) in Positive X-direction
LOADC RN=1 LC=3,1101 % Global Uniform Acceleration (1.0*G) in Positive Y-direction
LOADC RN=1 LC=4,1102 % Global Uniform Acceleration (1.0*G) in Positive Z-direction
LOADC RN=1 LC=96,1276 % External water pressure, 331.82 kN/m2 at z= 0.0
%
% -------------------------------------------------------------------------------------------
5.5.2 ELC – Equilibrium Load Case – Definition of new support system
If the supports of the finite element model are supposed to be real, there is no reason to create
ELC.
ELC load cases are OLC load cases from the finite element analysis, but where the OLC
response are re-calculated based on another support system than defined in the original FE-
model. ELC load cases are hence load cases where the support system is defined with
ShellDesign input though BASCO, LORES and GRECO statements.
The global load resultants of the original load cases OLC’s, are specified through the LORES
statement. The OLC’s simulating the new support system/ground reactions are scaled and
combined through the BASCO statement. The GRECO statement combines these basic load
combinations with the OLC’s for which equilibrium is desired. A version letter to each GRECO
is also defined.
It has for example been a common practice for the design of large offshore structures to
include the soil reaction response later on through the load combination system. In this way,
the designer may define many different soil reaction types (e.g., more vertical pressure on the
outer base slab), and the designer can decide which soil reactions different load combinations
should be combined with, instead of carry out several different FE-analyses.
Another example is for floating structures, where the structure is in real life supported by water
pressure where the internal and external loads are in equilibrium. However, the FE-analysis
needs a support system for the analysis to be run, and this fictious support system will lead
to some concentrated load effects in the support nodes, even when the loads are combined to
real load situations. In these cases, ELC’s are also applied where typically external water
pressure is used as new support system in ShellDesign.
How to define this system in ShellDesign is described in the following.
To create ELC’s, ShellDesign needs input on the Global Load Resultants of the OLC’s in the FE-
analysis as input to the ShellDesign calculations in order to eliminate the effect of the fictitious
supports in the FE-model. This information is typically found in the output file from the analysis.
For example, the sestra.lis file when SESAM/Sestra analyses are carried out. Or the input can
automatically be created with ShellDesign with the LORES SIN= statement.

Example of ShellDesign input with the LORES input statement is shown below. Note that all
95
OLC’s from the analyses that will be used in the ShellDesign post-processing must be included.
% -------------------------------------------------------------------------------------------
% LOAD RESULTANTS
% -------------------------------------------------------------------------------------------
%
% LC X-LOAD Y-LOAD Z-LOAD X-RMOM Y-RMOM Z-RMOM
LORES 1200 REAL 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00 0.0000E+00
LORES 1100 REAL 1.9291E+06 0.0000E+00 0.0000E+00 0.0000E+00 4.9895E+07 -6.7025E-01
LORES 1101 REAL 0.0000E+00 1.9291E+06 0.0000E+00 -4.9895E+07 0.0000E+00 -3.9670E+00
LORES 1102 REAL 0.0000E+00 0.0000E+00 1.9291E+06 6.7025E-01 3.9670E+00 0.0000E+00
LORES 1103 REAL 0.0000E+00 5.0861E+06 -6.8323E-02 -4.2523E+08 -4.5235E+00 -9.8688E+00
LORES 1104 REAL -5.0861E+06 0.0000E+00 -4.0439E-01 -4.5235E+00 -4.2523E+08 -5.6309E-01
LORES 1105 REAL 6.8323E-02 4.0439E-01 0.0000E+00 -9.8688E+00 -5.6309E-01 -2.9318E+08
%
% -------------------------------------------------------------------------------------------
Then a new support system must be defined through the ShellDesign input. The user must
define 6 basic load combinations of OLC's to represent a new support system, one BAS ID
representing FX support, one BAS ID representing FY support and so on. The OLC’s simulating
the new supports are hence scaled and combined through the BASCO statement.
The GRECO statement combines these basic load combinations with the OLC’s for which
equilibrium is wanted. A version letter to each GRECO must also be defined, and then different
letter defines specific support systems. Example of ShellDesign input is shown below:
% -------------------------------------------------------------------------------------------
% GRECO A - UNIFORM PRESSURE, HORIZONTAL REACTION FX AND FY, LINEAR MOMENTS MX, MY AND TORSION
% -------------------------------------------------------------------------------------------
BASCO ID=4001 LF=1.0 OLC=1503 % FX
BASCO ID=4002 LF=1.0 OLC=1504 % FY
BASCO ID=4003 LF=1.0 OLC=1500 % FZ
BASCO ID=4004 LF=1.0 OLC=1510 % MX
BASCO ID=4005 LF=1.0 OLC=1511 % MY
BASCO ID=4006 LF=1.0 OLC=1512 % MZ
%
GRECO ID=A BAS=4001-4006
% -------------------------------------------------------------------------------------------
With the use of the Global Load Resultants in the LORES input, ShellDesign will calculate the
required reaction forces for each OLC in such a way that the support forces are eliminated for
all active OLC's. The resulting effects are called ELC’s. ShellDesign will automatically calculate
all load factors for all ELC's, using the Global Load Resultants in the LORES input for all OLC's
together with the specified GRECO.
When the system above is defined, the user defines in the DECAS statement which type of
new support system to be used in the design calculations. Example of ShellDesign input is
shown below:
% -------------------------------------------------------------------------------------------
% DESIGN CASES
% -------------------------------------------------------------------------------------------
DECAS LS=ULS BAS=15001:A
DECAS LS=ULS ELC=15002:A
DECAS LS=ULS BAS=16001:K
DECAS LS=ULS ELC=16002:K
% -------------------------------------------------------------------------------------------
For example, the response for load combination 15001 is calculated based on the support
system with version letter A.

It is also possible to define more complex support systems than the system above. Example
96
of ShellDesign input of a more complex GRECO is shown below.
% -------------------------------------------------------------------------------------------
% GRECO F - UNIFORM PRESSURE, HORIZONTAL REACTION FX AND FY, MOMENTS MX, MY
WITH PEAK AT OUTER PERIMETER AND UNIFORM TORSION ON BASE SLAB
% -------------------------------------------------------------------------------------------
BASCO ID=4051 LF=1 OLC=1503 % FX
BASCO ID=4052 LF=1 OLC=1504 % FY
BASCO ID=4053 LF=1 OLC=1500 % FZ
BASCO ID=4056 LF=1 OLC=1512 % MZ
%
GRECO ID=F BAS=4051-4056
% -------------------------------------------------------------------------------------------
The new support system for MX and MY moments are calculated based on two OLC’s instead
of one. Note that the GRECO calculations are independent of the sign of the OLC’s, but the
absolute value must be correct when more OLC’s are combined.
5.5.3 ILC – Input Load Case
ILC’s are stress resultants specified by the user through input statements. These stress
resultants are specified through the INPLC statement. The sectional forces have the
dimensions kN/m for the membrane forces (N1, N2, N12) and the transverse Shear forces
(V1,V2). The dimensions for the bending moments (M1, M2, M12) are kNm/m. Example of
ShellDesign input is shown below:
% -------------------------------------------------------------------------------------------
% Sectional Forces: N1 N2 N12 M1 M2 M12 V1 V2
% -------------------------------------------------------------------------------------------
%
INPLC ID=15102 -15402 -17920 2089 1162 6766 133 -4537 9825
%
% -------------------------------------------------------------------------------------------
5.5.4 PLC – Prestressing Tendon Load Case
The common practice is to define the prestressing loads as OLC’s in the analysis. However,
ShellDesign has also the capability to calculate the prestressing effect in a design section based
on PLC load cases. This option should be used when the prestressing loads are not available
through the analyses.
PLC’s are load cases derived from the description of the prestressing tendons. The prestressing
tendons specified through the TEMAT, TETYP and TELOC statement and the load case PLC is
specified through the PLC command in the BASCO statement. This option should be used when
the prestressing loads are not available through the analysis.

5.5.5 BAS – Basic Combination Load Case
97
The load situation for a structure at any given time is normally complex. A FE-analysis may
consist of several independent load cases denoted OLC (original load cases) in ShellDesign.
The design check of a structure needs to consider the complete load combination at any given
time. To comply with this, ShellDesign offers the possibility to scale and combine load cases,
called the basic combinations; BAS. Hence the purpose with BAS is to combine single load
effects to present real load situations
Basic combinations (BAS) are the general basic tool for scaling and combining load types. All
load types (OLC, ELC, ILC, PLC) as well as other BAS may be used to create a BAS. A BAS is
specified through the BASCO statement.
When defining a BAS, the referenced load cases may optionally be marked as one of the
following:
- ordinary load effect

- wave effects: turn/return wave (representing the wave crest and trough of real/imaginary
wave)
The reasons for this classification are:
- Wave effects represent the variable part when investigating fatigue (FLS)
- Real/imaginary waves give the opportunity to step through 24 phase angles in order to
find the most unfavourable ones with respect to the utilization of concrete and
reinforcement
- The wave response is calculated as:
𝑊𝑎𝑣𝑒⁡𝑅𝑒𝑠𝑝𝑜𝑛𝑠𝑒⁡⁡= 𝑅𝑊 ∙ 𝑐𝑜𝑠(α) +/−⁡⁡𝐼𝑊 ∙ 𝑠𝑖𝑛(α) α=0, 15, 30…⁡
- The sign of the imaginary part (𝑰𝑾 ∙ 𝒔𝒊𝒏(α)) must be defined in DEPAR statement with the
I_WAV parameter. No default value.
Each BAS must be given an identification number between 1 and 99999. The BAS combinations
are calculated as:
ai ⁡⁡=⁡⁡multiplication factor
𝐵𝐴𝑆 = ∑ 𝑎𝑖 ∙ 𝐿𝐶𝑖 ⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡⁡
LCi ⁡⁡=⁡⁡load case (OLC, ELC, ILC, PLC, BAS)
𝑖
The multiplication factors may be a fixed number, specified with the LF command in the BASCO
statement or a location dependent number specified with the LDFAC statement and with LDF
command in the BASCO statement.
Note that when OLC’s should be combined with a specific GRECO, the OLC’s must be referenced
as an ELC instead of an OLC in the BASCO statement. Example of ShellDesign input is shown
below:
% -------------------------------------------------------------------------------------------
%
BASCO ID=501 LF=0.23 ELC=1800 LF=1.2 OLC=1500 LF=1.2 BAS=101 LF=0.3 ILC=1
%
% -------------------------------------------------------------------------------------------
This means that OLC=1800 will be re-calculated to the response of the new support system,
but OLC=1500 will still have the response from the original support system.

The version letter in the DECAS statement, defines which GRECO system to be applied:
98
% -------------------------------------------------------------------------------------------
%
DECAS LS=ULS BAS=501:P
%
% -------------------------------------------------------------------------------------------
5.6 Limit States

The following limit states are supported in accordance with the implemented design codes:
▪ Ultimate limit state : ULS

▪ Accidental limit state : ALS
▪ Serviceability limit state : SLS, CRW
▪ Fatigue limit state : FLS (not implemented for EC2 [4])
ULS: The ordinary ultimate limit state relates to the risk of failure or large inelastic strains of
a failure character.
ALS: The accidental limit state is identical to the ultimate limit state but with optionally other
material coefficients.
SLS: The serviceability limit state relates to the criteria governing normal use or durability.
The intention is to limit the cracking to ensure acceptable corrosion resistance of
reinforcement, adequate shear transfer capabilities and water and air tightness. Note
that limit state CRW is referenced in ShellDesign for crack width calculations.
FLS: The fatigue limit state relates to the risk of failure due to effects of cyclic loading.
The limits states are specified through the DECAS statement.
5.7 Concrete and Reinforcement
5.7.1 Concrete
The different concrete types available are types specified according to the rules in the
implemented design codes, where each concrete type can be modified by the user if necessary.
See Section 4 for description of the different design codes available in ShellDesign.
5.7.2 Reinforcement
There are three different reinforcement types available:

▪ Normal reinforcement
▪ Prestressed reinforcement
▪ Shear reinforcement
The properties of the reinforcement steel are specified according to the rules in the
implemented design codes. See Section 4 for description of the different design codes available
in ShellDesign. Normal reinforcement is specified through RETYP and RELOC statement,
prestressed reinforcement is specified through TETYP and TELOC statement and shear
reinforcement is specified through SRTYP and SRLOC statement.

The reinforcement direction is defined for each design section, for both normal reinforcement,
99
shear reinforcement and prestressed reinforcement. The reinforcement direction refers to the
local 1, 2, 3 axis system. See figure below.
Figure 5-5: Relationship between section forces, local axes, and reinforcement direction
A recommended input file for normal reinforcement (RETYP.inp) is shown below.

% -------------------------------------------------------------------------------------------
FILST NAME=RETYP VERS=1.0 DATE=06.08.2014 RESP=BESNY
%
%----------------------------- Change log -------------------------------------------------
% -------------------------------------------------------------------------------------------
%
% ------------------------------------------------------------------------------------------------
% ID MATERIAL INTENSITY COVER LAYER REBAR BARS IN BOND LABEL
% THICKNESS DIAMETER BUNDLE COEFF. NAME
% ------------------------------------------------------------------------------------------------
%
% Cover 60 mm:
% -----------
RETYP ID=00001 MP=1 AR=0001.E-8 C2=0.060 TH=0.400 DI=0.030 NR=1 BC=0.75 LB=Spacer_40mm
%
RETYP ID=25101 MP=1 AR=2500.E-6 C2=0.060 TH=0.030 DI=0.025 NR=1 BC=0.75 LB=1.0D25_c200
RETYP ID=25151 MP=1 AR=3750.E-6 C2=0.060 TH=0.030 DI=0.025 NR=1.5 BC=0.75 LB=1.5D25_c200
%
% Cover 70 mm:
% -----------
RETYP ID=00002 MP=1 AR=0001.E-8 C2=0.070 TH=0.400 DI=0.030 NR=1 BC=0.75 LB=Spacer_40mm
%

100
The reinforcement area is defined per unit meter; hence input to ShellDesign is in [m 2/m].
Examples of intensities for typical reinforcement systems are shown in the table below:
Table 5-1: Reinforcement intensities as input to ShellDesign
Rebar Input to ShellDesign [m2/m]
1Ø25c200 0.002454
2Ø25c200 0.004908
0.5Ø32c200 0.002011
1Ø32c200 0.004021
1.5Ø32c200 0.006032
2Ø32c200 0.008042
The ID number for each RETYP statement can be defined as above and then describes the type
of reinforcement based on a system ID=UUVVX as explained below. Note that the ID may
have 8 characters; hence more numbers can be included to define more variations if applicable
than this example.
UU VV X
rebar diameter number of bars in the layer refers to a defined
e.g: 20/25/30/35 e.g: 00/05/10/15/20 actual cover
The numbers of bars in layer means:
Real layout:
05 = 0.5 bars →
10 = 1.0 bars → c = centre distance between bundles
15 = 1.5 bars →
20 = 2.0 bars →
c
The RETYP statement defines also the reference to concrete cover (C2) for normal
reinforcement. There may be different concrete cover for different structure parts/concrete
faces in a structure. Therefore, the letter X can define a special ID to a specific concrete cover.
Note that so called “spacers” (ID=00001) are also defined. These are fictitious rebars, with no
action other than as a spacer between two rebars in the same direction but in different layers.
It is important that the rebars are placed with correct center of gravity to make the design
results as accurate as possible.
Note also that the above recommended ID input is user defined and ShellDesign will not use
any areas, concrete cover, thicknesses etc. based on this number. All input data to ShellDesign
calculations has to be defined in the MP, AR, C2, TH, DI, NR, BC syntaxes.
The label name (LB) will be seen on category plots in the graphical post-processor, Xtract.

5.7.3 Shear reinforcement
101
A recommended input file for shear reinforcement (SRTYP.inp) is shown below:
% --------------------------------------------------------------------------
% --------------------------------------------------------------------------
FILST NAME=SRTYP VERS=1.0 DATE=06.08.2014 RESP=BESNY
%
%----------------------------- Change log --------------------------------
% 1.0 06.08.2014 BESNY File created
% --------------------------------------------------------------------------
%
% ---------------------------------------------------------------------------
% ID MATERIAL INTENSITY LABEL NAME
% ---------------------------------------------------------------------------
SRTYP ID=101042 MP=1 AR=1250.E-6 LB=1.0D10_c400c200
% -------------------------------------------------------------------------------------------
The ID number for each SRTYP statement describes the type of shear reinforcement based on
a system ID=UUVVXW as explained below. Note that ID may have 8 characters; hence more
numbers can be included to define more variations if applicable than this example.
UU VV X W
rebar diameter number of bars in one bundle Center distance 1 Center distance 2
e.g: 20/25/30/35 e.g: 00/05/10/15/20
Note that the above recommended ID input is user defined and ShellDesign will not use any
areas etc. based on this number. All input data to ShellDesign calculations has to be defined
in MP and AR syntaxes.
The label name (LB) will be seen on category plots in the graphical post-processor, Xtract.
5.7.4 Prestressing/tendon reinforcement types
A recommended input file for prestressing reinforcement types (tendons) (TETYP.inp) is shown
below:
% -------------------------------------------------------------------------------------------
% -------------------------------------------------------------------------------------------
FILST NAME=TETYP VERS=1.0 DATE=06.08.2014 RESP=BSN
%
%----------------------------- Change log -------------------------------------------------
%--------------------------------------------------------------------------------------------
%
% Horizontal:
TETYP ID=101 MP=1 AR=1.E-6 E0=5.343E-3 OS=-0.140
% Vertical:
TETYP ID=201 MP=1 AR=1.E-6 E0=5.944E-3 OS=0
% -------------------------------------------------------------------------------------------

The ID number for each TETYP statement is not based on a very complicated system in this
102
case, but the first number tells if it is a vertical or a horizontal tendon. It is recommended to
define a proper system if applicable.
5.8 OLC-Files and DEC Files
5.8.1 OLC-Files
An OLC-file is a database generated with ShellDesign containing results fetched from a FE

analysis file, such as geometry and stress resultants (section forces) for each load case (OLC)
and node displacements.
The file is either a scratch file, a new permanent file or an old file:
▪ Scratch OLC-file:
− Internally created during a ShellDesign run when a FEM result file is attached. No
OLC-file saved.
▪ New permanent OLC-file:
− Internally created during a ShellDesign run when a FEM result file is attached. The
OLC-file is saved afterwards.
▪ Old OLC-file:
− A previously created permanent OLC-file. The file can be attached to a design run
instead of the FEM result file.
It is useful to create a permanent OLC-file and then use this file for later design runs when the
structure is large and there are many load cases. Run time will decrease since the result in the
FE analysis file is already converted to section data in OLC-file.
The creations of OLC-files are specified through the OLCFI statement.
As the ShellDesign model is divided in different Parts, it is common practice to create OLC files
for each Part respectively. These OLC files are later referenced in the ShellDesign input file.
Example of creating and merging OLC files are shown below.
Generating OLC-file:
% ---------------------------------------------------------------------------------
HEADL PROJECT
HEADL PART
HEADL GENERATING OLC-FILE
% ---------------------------------------------------------------------------------
% FEM result file:
RFILE FNM=R400 SUF=SIN
% ---------------------------------------------------------------------------------
% Design sections:
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\DESIGN-SECTIONS\PART.inp
% ---------------------------------------------------------------------------------
% OLC renumbering :
incdf P:\PROJECT\DETAIL-DESIGN\GLOBAL-INPUT-FILES\LOAD-COMBINATIONS\LOADC-R400.inp
% ---------------------------------------------------------------------------------
% Create OLC-file:
OLCFI NF=PART-400.OLC NAME=PART-400 VERS=X DATE=X RESP=BESNY
% ---------------------------------------------------------------------------------
% Execution mode:
EXECD DM=
% ---------------------------------------------------------------------------------

Merging OLC-files:
103
% ---------------------------------------------------------------------------------
HEADL PROJECT
HEADL PART
HEADL MERGING OLC-FILES
% ---------------------------------------------------------------------------------
% Merge OLC-files:
OLCFI OF=PART-100.OLC OF=PART-400.OLC MF=MERGED.OLC NAME=MERGED VERS=X DATE=X RESP=BESNY
% ---------------------------------------------------------------------------------
% Execution mode:
EXECD DM=
% ---------------------------------------------------------------------------------
5.8.2 DEC-files
A DEC-file is a database generated with ShellDesign containing design results, such as

reinforcement amounts, governing BAS combinations with corresponding UR for all design
sections etc.
The file is either a scratch file, a new permanent file or an old file:
▪ Scratch DEC-file:
− Created during a ShellDesign run and deleted afterwards. No DEC-file saved.
▪ New permanent DEC-file:
− Created during a ShellDesign run and saved afterwards.
▪ Old DEC-file:
− Previously created permanent DEC-file.
It is useful to create a permanent DEC-file to later fetch tables that for example where
forgotten in the main design run and especially when large runs have been executed.
The creations of DEC-files are specified through the DECFI statement.
5.8.3 Scratch files
ShellDesign uses the Windows Environment Variable TMP as directory for storage of temporary
scratch files. If the disk containing the scratch directory, has limited free space a write error
may occur in ShellDesign (IOSTAT=38). To avoid this, set the TMP folder to a disk with more
free space. A guide for setting this environmental variable is included in Figure 5-6.

1 104
2
3 4
Figure 5-6 Define system environment variable TMP

5.9 Result presentation 105
The results from the design calculations (code check) are typically expressed with the use of
utilization ratios (UR). The utilization of 1.0 indicates that the limit is reached. The limit refers
to maximum allowable concrete stress, reinforcement stress, shear capacity, crack widths etc.
Results such as section geometry, section forces, node displacements, principal forces etc. are
also available.
5.9.1 Results in Tables
All results in ShellDesign can be presented in tables. Examples of table formats are shown
below. The available results in tables are detailed described in Section 7.
maxUR Rebar layer maxStresses : TABLE UR=RS RL=ALL, area=(mm2/m), eps=(0/00)

PART mFS mHS TAB ID area LOAD-ID LIM PHA eps sig-u UR
CYLINDER 34 17 RS X11 8042 BAS101 ULS * 2.212 434783 0.88
CYLINDER 54 8 RS Z12 8042 BAS101 ULS * 2.353 434783 0.94
CYLINDER 20 1 RS X13 8042 BAS101 ULS * 0.869 434783 0.35
CYLINDER 56 1 RS Z14 8042 BAS101 ULS * 1.617 434783 0.65
TABLE TAB=DF : shell section design forces/moments

PART FS HS LOAD-ID LIM PHA N1 N2 N12 M1 M2 M12 V1 V2
CYLINDER 40 7 BAS101 ULS 823. 1311. 6688. 38. 225. -119. 39. 350.
CYLINDER 40 8 BAS101 ULS 753. 1127. 6828. 21. 158. -131. 19. 345.
CYLINDER 40 9 BAS101 ULS 574. 762. 7043. -6. 71. -142. -2. 314.
CYLINDER 40 10 BAS101 ULS 430. 489. 7154. -21. 24. -141. -19. 294.
CYLINDER 40 11 BAS101 ULS 267. 108. 7253. -36. -4. -135. -24. 277.
5.9.2 Graphical Results
The results from ShellDesign can be presented in 3D graphics in DNV’s Xtract. A detailed
manual for ShellDesign results in Xtract is found in the Xtract User Manual. The graphical
interface is typically shown in the figure below.

106
Figure 5-7: Graphical Plot interface for ShellDesign results in DNV’s Xtract
An input file to Xtract (*.vft) is generated with ShellDesign. This file might include the whole
model or just parts of the model. The ShellDesign input statement to generate plot is:
XTFIL FN=”FILE NAME” PA=”PART NAME”
If several (more than 50-100) load combinations is run, it is recommended to only save peak
values on the Xtract plot file by including PV= in the statement as:
XTFIL FN=”FILE NAME” PA=”PART NAME” PV=
Xtract is also a suitable tool to show line plots of ShellDesign outputs. Select type of result,
change the model to be a wire frame model and go to Results \ Design Section Diagrams.

107
To also include displacement results in the *.vtf-file, the following statement must be included
in the input file:
DECFI ND=ON
Displacements only refer to node results in the FE-model and not the design sections (gaussian
points). Note that line plots are not available for displacement plot.
Please contact software@DNV.com for more information. A license to Xtract must be

purchased separately.

6 DESCRIPTION OF INPUT STATEMENTS 108
6.1 Input File

Input for ShellDesign consists of data and commands. Inputs are given in the form of input
lines with alphanumerical data. All data are stored internally in ShellDesign and can be altered,
deleted and printed out at any time. When ShellDesign is closed, all internally saved data gets
lost. Input lines can be inserted from one or more files.
All input lines start with a code word, called input statement, which identifies what sort of data
the line contains. One or many sets of variables, called parameters, are associated with each
input statement. To separate the variables from each other, they are named with ‘=’ between
the name and the value.
Example: ID=material1 RT=5
If a design parameter is not entered, a predefined value is used (default value). This could be:
‘0’ ‘all’ ‘whole’ or similar.
All input data to ShellDesign should be kept on a main input file. Additional input files may be
introduced by use of the incdf command in the main input file followed by the path to the
additional file and name, like this:
incdf ..\Global_Input_files\Material-properties\CMPNS.inp
ShellDesign reads both uppercase and lowercase letters in the input file. The input statements
can be sorted randomly in the input file (except the EXECD-statement that need to be placed
at the end of the file). It is recommended to sort the input statements in a proper way as they
should in a well-arranged input file. Example of input files are shown in Section 9.
NB! The maximum number of characters in a single line in the input file cannot exceed 164.
Characters from 165 will not be read by ShellDesign and without any error messages.
A typical input line could look like this:

BASCO ID=2 LDF=12 OLC=1-5-1,8
Where BASCO is the statement, ID is a parameter to identify the entity for later reference.
LDF and OLC are also parameters. The OLC design parameter has a numerical definition, which
is interpreted as the OLC cases 1, 2, 3, 4, 5 and 8.
For all statements it is possible to write ? or ?? behind the statement, and respectively a
template line or a help text is printed in the out-file upon execution (example “BASCO ??”).
6.2 Syntax Explanation

Syntax explanations to the following description of input statements are:
▪ Normal text must be typed.

▪ Text in brackets () is not necessary.
▪ / means or. That is, one of the alternatives must be typed.
▪ Parameters belonging together is put in brackets of this type []

6.3 Run Statements 109
6.3.1 EXECD - order ShellDesign execution of current input data
_____________________________________________________________
Input Statement: EXECD

______________________________________________________________
Purpose: - order execution of the data defined in the input file. This statement must
always be included at the end of the top-level input file. This is the only
statement that needs to be placed in a defined location in the input file.
EXECD DM= /V/S/A
Parameters:
Conventional Design Method (CDM), see Section 3.2:
DM= : No design calculations are performed. Relevant when only OLC-files are created;
when the concrete model is created and sectional forces in design sections is
printed. No need for material data input such as CMPNS, RMPNS, RETYP, RELOC
for this run. Create OLC-files, see Section 5.8.1.
DM=V : Design calculations are performed by verifying the user defined reinforcement.
Material data input must be included. Create DEC-file (design file), see Section
5.8.2.
DM=S : Perform design calculations, but necessary section reinforcement is found by the
program by searching a user-specified range of possible reinforcement
arrangements.
DM=A : Perform design calculations, but necessary area reinforcement is found by the
program by searching a user-specified range of possible reinforcement
arrangements.
Consistent Stiffness Method (CSM) - Non-linear structural analysis run, see Section 3.3:
DM=V : Design calculations are performed based on the last linear elastic analysis run in
the CSM analysis. Design calculations are based on design material properties,
and CSM results are based on CSM material properties. See Section 6.3.2
concerning definition of CSM with the NONLI-statement.
Examples:
Run mode for creation of OLC files, design sections:

EXECD DM=
Run mode for verification/design calculations of user defined reinforcement:

EXECD DM=V

6.3.2 NONLI – order CSM analysis to be carried out
110
______________________________________________________________
Input Statement: NONLI

______________________________________________________________
Purpose: - define data concerning the Consistent Stiffness Method (CSM) with linear elastic
stiffness or updated non-linear stiffnesses in elements. Non-linear stiffness
elements are defined by: SHSEC .. ET=VS (cracked concrete), all other elements
will have constant elastic stiffnesses. Material parameters are defined with CMPNL,
RMPNL and TMPNL. See Section 3.3 for detailed description of CSM.
NONLI FEA=SES/OOS (SPA=spa) (NSR=no) (NDT=di) (LCO=) (WAC=alc)

NONLI (SSF=fac) (PRI=)
Parameters:
FEA=SES : If CSM analysis with shell elements should be executed.
SESTRA will be used as the FEA-program. During the analyses Sestra 8 has
the R-file and T-file are changed. Remember to always start a to be used
new CSM analysis with the original R- and T-file.
FEA=OOS : If CSM analysis with solid elements should be executed.

OOsolver will be used as the FEA-program.
SPA=spa : path to SESTRA executable when using FEA=SES

NB! Directory names with space must be enclosed by two ".
Example: C:\”Program Files”\DNV\”Sestra VXX.XX-XX”\
bin\Sestra.exe]
NSR=n : flags CSM analysis [default 10]

n=max number of analysis run per design case
Note that non-linear stiffness elements are defined by the
statement SHSEC .. ET=VS. ET=VS must be included.
n=0 flags linear analysis.
NDT=di : Iteration stop condition; node Displacement difference [default 0.0]

threshold value (m)
LCO= : loads will be combined on the FEM-file before Sestra is run. This [default off]
will save time if many load cases are present. Only applicable
for FEA=SES
IDK= : Initial deformations will be taken from the previous design case. [default off]
To be used when loads are increased from design case to design
case.
WAC=1 : Flags that water pressure in cracks should be included. Note

that this is only available for solid models. Node loads to be
applied in analysis is defined in WPARE and DECAS
statements.
SSF=fac : shear stiffness factor to be multiplied with elastic shear [default 1.0]
stiffness. Only applicable for FEA=SES.
PRI= : current NONLI data will be printed
Example: NONLI NSR=10 NDT=0.001 FEA=OOS

6.3.3 OLCFI – create, merge or read OLC files with FE-analysis results
111
______________________________________________________________
Input Statement: OLCFI

______________________________________________________________
Purpose: - define OLC-file data when OLC files are created, merged or read. See Section
5.8.1. An OLC-file is a database generated with ShellDesign containing results
from a FE analysis file, such as geometry and stress resultants (section forces)
for each load case (OLC) and node displacements.
OLCFI OF=fnm1/[NF=name (NAME=name VERS=vers DATE=date RESP=resp)]
Parameters:
If old file(s) shall be read (up to 16 files may be attached):
OF:fnm1 OF:fnm2 ….. : OLC-file path(s)
If a new file shall be created:
NF=fnm : path to the new OLC-file
NAME=name : name (max 48 characters)
VERS=vers : version (max 8 characters)
DATE=date : date of this version (max 12 characters)
RESP=resp : responsible (max 8 characters)
If two files shall be merged:
OF=fnm1 OF=fnm2 MF=fnm3 : merged files to be stored on fnm3
PRE=path : path to folder containing .OLC file(s). All files will be copied
to the work directory. Directory names with spaces must
be enclosed by " ".

The OLCFI NF= command must be combined with section statements, see Section 6.6, and
LOADC statement if the ordinary analysis load cases should be renamed.
Examples:
Example 1: a new file shall be created
OLCFI NF=DOMEA.OLC NAME=Lower_dome_A VERS=1.0 DATE=8jan-94 RESP=kf
Example 2: two old files shall be read

OLCFI OF=DOMEA.OLC OF=DOMEB.OLC
Example 3: two old files shall be merged

OLCFI OF=DOMEA.OLC OF=DOMEB.OLC MF=DOMEAB.OLC NAME=Lower_dome_AB OLCFI
VERS=1.1 DATE=8jan-94 RESP=BESNY

6.3.4 DECFI - create, merge or read DEC files with design results
112
______________________________________________________________
Input Statement: DECFI

______________________________________________________________
Purpose: - define DEC-file data when DEC files are created, merged or read. See Section
5.8.2. A Design file (DEC-file) is a database generated with ShellDesign
containing design results, such as reinforcement amounts, governing BAS
combinations with corresponding UR for all design sections etc.
DECFI OF=fnm/[NF=name (ND=ON/OFF NAME=name VERS=vers DATE=date

RESP=resp)]
Parameters:
If an old file shall be read:
OF:fnm : DEC-file path
If a new file shall be created:
NF=fnm : new file path
ND=ON/OFF : node data to be included or not. ND=OFF means [default OFF]

that no shape plot will be available. ND=OFF will
save run time.
NAME=iden : file identity (max 48 characters)
DATE=date : date of last revision (max 12 characters)
If two files shall be merged:
OF=fnm1 OF=fnm2 MF=fnm3 : merged files to be stored on fnm3

(only results may be merged, sections must be equal)
(if two design cases have same id. the results from fnm2
are stored)
Examples:
Example 1: a new file shall be created

DECFI NF=LDOMEA.DEC NAME=Lower_dome_A VERS=1.0 DATE=01.02.22 RESP=kf
Example 2: a new file shall be created at specified folder

DECFI NF=C:\projects\GBS\LDOMEA.DEC NAME=GBS VERS=1.0 DATE=01.02.22 RESP=kf

113
Example 3: an old file shall be read
DECFI OF=LDOMEA.DEC
Example 4: two old files shall be merged

DECFI OF=LDA.DEC OF=LDB.DEC MF=LDAB.DEC NAME=Lower_dome_AB VERS=1.1
DATE=01.02.22 RESP=kf
A XTRACT plot file contains data fetched from the OLC-file and the DEC-file. From the DEC-
file, the following information can be fetched:
- If EXECD DM= is given, a design-file (DEC-file) is created which contains section data
and reinforcement data.
- If DECAS also is given, the design.file will also include section forces.
- If EXECD DM=V and DECAS is given, the design-file will also include utilization ratios.
6.3.5 DESEC - define or modify design section geometry
______________________________________________________________
Input Statement: DESEC

______________________________________________________________
Case 1: - no OLC-file or FE result file attached:

DESEC statement define design sections, identity and geometry, hence used
when the analysis method described in Section 3.2 is applied.
Case 2: - FE result file or an OLC-file is attached:

DESEC statements define design sections to be stored on the DEC-file. If not
DESEC is defined, all design sections available will be used. DESEC statements
may redefine shell section design geometry. Used when the analysis method
described in Section 3.3 is applied.
Case 3: - CSM analysis:

DESEC statements may redefine shell section design geometry. Used when the
analysis method described in Section 3.3 is applied.
DESEC PA=pa (FS=i1-i2) (HS=j1-j2) (TH=th T11=t11 T12=t12 T21=t21 T22=t22)
Parameters:
Section identities:
PA=pa : structural part (max 8 char.)
FS=i1-i2 : F-section range [default all]
HS=j1-j2 : H-section range [default all]
Section geometry:
TH=th : shell thickness [m] [default 0]

T11=t11 : shell thickness gradient [dt1/dx1] [default 0]

T12=t12 : shell thickness gradient [dt1/dx2] [default 0] 114
X=x : X-coordinate [m] [default 0]
Y=y : Y-coordinate [m] [default 0]
Z=z : Z-coordinate [m] [default 0]
Examples:
Example: design sections = all OLC-sections for part = DOME

DESEC PA=DOME
Example: design sections = some OLC-sections for part = DOME

DESEC PA=DOME FS=1-30 HS=1-5
Example: design sections = all OLC-sections for part = DOME

Shell design thickness to be changed for some sections.
DESEC PA=DOME
DESEC PA=DOME FS=1-15 HS=5 TH=0.45
6.3.6 RFILE - read Sestra FE analysis input file and/or FE analysis result file
______________________________________________________________
Input Statement: RFILE

______________________________________________________________
Purpose: - read FE analysis input and/or result file from Sestra.
RFILE (PRE=path) FNM=fnm (TFI=tfi) (LFI=lfi) (LUN=n) (FUN=n)
Parameters:
PRE=path : path to folder containing input/analysis files. The file [default=same

will be copied to the work directory. Directory names as input file]
with spaces must be enclosed by " ". relative or full path
FNM=fnm : Sestra result file. Example FNM=R1.SIN
TFI=tfi : Sestra input file. Only necessary when CSM analysis is
carried out, and not CDM analysis. Example
FNM=T1.FEM. The T-file must be a sequential
formatted character file. This file will be changed during
the CSM run.
LFI=lfi : Sestra load input file for dynamic loads. Only necessary
when CSM analysis is carried out and if such files are
used in the load application. Example FNM=L1.FEM.
LUN=n : Number of mm in length unit. Not applicable for CSM [default=1000]
analysis. kN and m must be used as input in analysis
as default

FUN=n
: Number of Newton in force unit. Not applicable for CSM [default=1000] 115
analysis. kN and m must be used as input in analysis
as default.
Comments:
Not possible to use different units in FE-analysis and design when CSM is executed. Meters,
kN and tonnes in FE-model must be used for CSM analysis.
Examples:
RFILE PRE=C:\RPLATE\ FNM=R1.SIN
The result files are located in C:\RPLATE\ and is copied to the working directory by ShellDesign.
If FE-model is applied with m and N:

RFILE FNM=R1.SIN FUN=1
If FE-model is applied with mm and N:

RFILE FNM=R1.SIN LUN=1 FUN=1
6.3.7 MFILE - attach a substructure M-file to CSM analysis
______________________________________________________________
Input Statement: MFILE

______________________________________________________________
Purpose: - attach a substructure M-file to the CSM analysis. The M-file may consist of
top side etc.
MFILE (PRE=path) FNM=fnm (LCO=lof) (OFF=x,y,z)
Parameters:
PRE=path : path to folder containing M-file. The file will be copied [default=same
to the work directory. Directory names with spaces as input file]
must be enclosed by " ". relative or full path
FNM=fnm : FNM=fnm: example FNM=M2.SIF
If the substructure load numbering is different:

LCO=lof : Load case offset number [default 0]
OLC-load-No. = SUB-load-No. + lof
If the substructure coordinate system is different:

OFF=x,y,z : Offset coordinates [default 0]
Examples:
MFILE PRE=C:\RPLATE\ FNM=M2.SIF LCO=10 OFF=10,0,5

6.3.8 ABAFI - read ABAQUS result file
116
______________________________________________________________
Input Statement: ABAFI

______________________________________________________________
Purpose: - read an ABAQUS analysis result file
ABAFI (PRE=path) FNM=fnm SUF=suf
Parameters:
PRE=path : prefix to filename [default=same as input file]
FNM=fnm : filename for analysis result file
SUF=suf : suffix to filename
Example:
ABAFI PRE=C:\RPLATE\ FNM=Job-1 SUF=aba
The result file is called Job-1.aba and is located in C:\RPLATE\.

6.4 Material Properties Statements 117
6.4.1 CMPOS - define concrete material according to DNV-ST-C502
______________________________________________________________
Input Statement: CMPOS

______________________________________________________________
Purpose: - define concrete material property sets according to DNV-ST-C502 [2].

DEPAR D_COD=OS statement must also be included in input file. Most of the
parameters are optional. Values related to the chosen concrete quality
according to DNV-ST-C502 will then be used.
CMPOS ID=id GR=Cxx (RH=rh) ) (FIG=fig)

CMPOS ID=id (LA=lan) (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
CMPOS ID=id (FCN=fcn) (CSD=fac) (TSP=tsp) (TSD=fac) (FTK=ftk) (BTS=fac)
CMPOS ID=id (FTN=ftn) (ECN=Ecn) (EPU=epu) (MFU=mfu) (MFA=mfa) (MFF=mff)
CMPOS ID=id (ECK=Eck) (MFS=mfs) (CSA=fac)
CMPOS (PRI= /TAB)
Parameters:
ID=id : identity number
Normal weight concrete and heavy weight concrete:
GR=Cxx : C-grade: legal range 25-90 (integer)
Lightweight concrete
GR=Cxx : LC-grade: legal range 25-35 (integer)
RH=rho : Density, ρ, flags lightweight concrete [kg/m3]
FIG=fig : Define non-linear or linear material curve. [default non-

Default is non-linear (figure 6.1), hence if linear curve]
linear material curve is wanted, type FIG=6-3
The following data refer to DNV Sec. 6.3.2 Figure 6-1:
FCN=fcn : in situ compression strength [kPa]

(ULS/ALS/SLS/CRW)
ECN=ecn : modulus of elasticity (ULS/ALS/SLS/CRW) [kPa]
EPU=epu : ultimate compression strain (ULS/ALS) [-]
FTN=ftn : in situ tensile strength (ULS/ALS/SLS/CRW) [kPa]
Design properties:
CSD=fac : design compression strengthening factor. [-] [default 1.0]
TSP=tsp : design fc2d = fcd/(0.8+tsp*ept) [-] [default 100]
TSD=fac : design min(fc2d) = fac*fcd [-] [default 0.3]
FTK=ftk : characteristic tensile strength (CRW) [kPa]

FTN=ftn : nominal tensile strength (ULS/ALS/CRW) [kPa]

MFU=mfu : design material factor (ULS) [-] [default 1.5] 118
MFA=mfa : design material factor (ALS) [-] [default 1.3]
MFF=mff : design material factor (FLS) [-] [default 1.5]
MFS=mfs : design material factor (SLS/CRW)) [-] [default 1.0]
Location defined by LAREA statements:
LA=lan : LAREA id-number
Location defined by Part, F-section range and H-section range:
PA=part : structural part (max 8 characters)
FS=fs1-fs2 : F-section range [default all]
HS=hs1-hs2 : H-section range [default all]
PRI= : print data for all stored CMPOS sets
PRI=TAB : print data + stress/strain table
Examples:
CMPOS ID=1 GR=C45
CMPOS ID=2 GR=C35 FCN=28000 ECN=27174000 EPO=-2.01e-3 EPU=-3.48E-3

CMPOS ID=2 FTN=2000 MFU=1.4 MCP=1. ECK=27836000
CMPOS ID=3 GR=C45 RH=1350 LA=2

CMPOS PRI=
Different parameters have been given to different ID's. If different areas shall have different
parameters, there are two optionally ways to define the areas:
1) location defined by LAREA statement. Example: CMPOS ID=id LA=lan and then the
parameters. It is necessary to define the area(s) in a separate statement LAREA where
the ID numbering are the same as the CMPOS ID numbering.
2) location defined directly in CMPOS statement. Example: CMPOS ID=id PA=part
FS=fs1-fs2 HS=hs1-hs2 and then the parameters.
Related statements:
LAREA
DEPAR
RMPOS

6.4.2 CMPNS - define concrete material according to NS 3473
119
______________________________________________________________
Input Statement: CMPNS

______________________________________________________________
Purpose: - define concrete material property sets according to NS 3473 [3]. Most of the
parameters are optional. Values related to the chosen concrete quality
according to NS 3473 will then be used.
CMPNS ID=id GR=Bxx (RH=rh) (LA=lan) (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)

CMPNS ID=id (FCN=fcn) (CSD=fac) (TSP=tsp) (TSD=fac) (FTK=ftk) (BTS=fac)
CMPNS ID=id (FTN=ftn) (ECN=Ecn) (EPU=epu) (MFU=mfu) (MFA=mfa)
CMPNS ID=id (ECK=Eck) (MFS=mfs) (MFF=mff) (CSA=fac) (FTA=fta)
CMPNS (PRI= /TAB)
Parameters:
Normal weight concrete and heavyweight concrete (stress strain diagram according to figure
2 in NS 3473):
GR=Bxx : B-grade(mar-2004): legal range 10-95
Lightweight concrete (stress strain diagram according to figure 4 in NS 3473):
GR=Bxx : LB-grade(mars2004) : legal range 12-75
RH=rho : density, flags lightweight concrete: legal [kg/m3]

range depending on material class
The following data refer to Figure 2 NS 3473 (of figure 4 for lightweight concrete):

ECN=Ecn : modulus of elasticity (ULS/ALS) [kPa]
EPU=epu : ultimate compression strain (ULS/ALS) [-]
Design properties:
CSD=fac : design compression strengthening factor. [-] [1.15,1.0]

if GR>B55 and GR=LBxx CSD=1.0
if GR<=B55 CSD=1.15
TSP=tsp : design fc2d = fcd/(0.8+tsp*ept) [-] [default 100]
TSD=fac : design min(fc2d) = fac*fcd [-] [default 0.3]
FTK=ftk : characteristic tensile strength (CRW) [kPa]
FTN=ftn : in situ tensile strength (ULS/ALS/CRW) [kPa]
MFU=mfu : design material factor (ULS) [-] [default 1.4]
ECK=Eck : modulus of elasticity (SLS/CRW) [kPa]

MFS=mfs : design material factor (SLS/CRW) [-] [default 1.0]
MFF=mff : design material factor (FLS) [-] [default 1.2]

Location defined by LAREA statements: 120
PRI= : print data for all stored CMPNS sets
Examples:
CMPNS ID=1 GR=B45
CMPNS ID=2 GR=B35 FCN=28000 ECN=27174000. EPO=-2.01e-3 EPU=-3.48E-3

CMPNS ID=2 FTN=2000 MFU=1.4 MCP=1. ECK=27836000
CMPNS ID=3 GR=B45 RH=1350 LA=2

CMPNS PRI=
1) location defined by LAREA statement. Example: CMPNS ID=id LA=lan and then the
parameters. It is necessary to define the area(s) in a separate statement LAREA where
the ID numbering are the same as the CMPNS ID numbering.
2) location defined directly in CMPNS statement. Example: CMPNS ID=id PA=part
Related statements:
LAREA
RMPNS

6.4.3 CMPEC - define concrete material according to NS-EN 1992-1-1
121
______________________________________________________________
Input Statement: CMPEC

______________________________________________________________
Purpose: - define concrete material property sets according to EuroCode 2 [4]. Most of
the parameters are optionally. Values belonging to the chosen concrete quality
will then be used.
CMPEC ID=id GR=Bgr (RH=rho) (LA=lan) (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)

CMPEC ID=id (FCK=fck) (ECM=ecm) (FCN=fcn) (FTM=ftm) (EXP=n) (EC2=ec2)
CMPEC ID=id (ECU=ecu) (MFU=mfu) (MFA=mfa) (MFS=mfs) (K2=k2) (TSP=tsp)
CMPEC ID=id (TSD=tsd) (COT=cot) (ACC=acc)
CMPEC (PRI= /TAB)
Parameters:
Concrete grade definition:
GR=Bgr : concrete grade, legal range 12-90 (integer) [MPa]
RH=rho : density, flags lightweight concrete, range 1150- [kg/m3]

2150
Single data to be given if no concrete grade is defined:
FCK=fck : cylinder compression strength after 28 days [kPa]
ECM=ecm : secant modulus of elasticity [kPa]
FTM=ftm : in situ tensile strength [kPa]

ACC=acc : coefficient taking into account longterm effects [default 0.85]
(see EC2 clause 3.1.6 and NA.3.1.6(1)P)
The following data refers to Figure 3.3:
EXP=n : exponent n in equation 3.17
EC2=ec2 : strain at start stress plateau
EU2=ecu : ultimate strain
Design properties:
MFU=mfu : design material factor (ULS) [default 1.5]
MFA=mfa : design material factor (ALS) [default 1.2]
MFS=mfs : design material factor (SLS/CRW) [default 1.0]
K2=k2 : Shear parameter k2: see NA.6.2.2 [default 0.15]
COT=cot : Shear cot(theta). See Section 4.4.3.3. The correct [default 2.5]
value must be decided in project.
Cot=1.0 → 45°
Cot=2.5 → 21.8°

Reduced compression strength (fc2d effect if fac<1.0): 122
TSP=tsp : design fc2d = fcd/(0.8+tsp*ept) [default 100]
TSD=tsd : design min(fc2d) = fac*fcd . Default not activated. [default 1.0]
PRI= : print data for all stored CMPNS sets

Examples:
CMPEC ID=1 GR=B35 PA=PLATE FS=1-10 HS=15-21
CMPEC ID=2 FCN=29750 FTM=1870 EXP=2 EC2=0.002 ECU=0.0035 MFU=1.5 MFA=1.2

CMPEC PRI=
CMPEC PRI=TAB
Rule: if more than one set No. is found for a section, the last set will be chosen.
6.4.4 CMPGM - define concrete material according to MCFT
______________________________________________________________
Input Statement: CMPGM

______________________________________________________________
Purpose: - define concrete material property sets in accordance with MCFT [5]. Most of
the parameters are optionally. Values belonging to the chosen concrete quality
will then be used.
CMPGM ID=id GR=Bxx (LA=lan) (PA=part) (FS=fs1-fs2) (HS=hs1-hs2) (EPU=epu)

CMPGM ID=id (FTC=ftc) (AGS=dm) (MFU=mfu) (MFA=mfa) (MFF=mff) (MFS=mfs)
CMPGM (PRI= /TAB)
Parameters:
The following data refer to Section 4.5:
GR=Cxx : B-grade: legal range 10-90 (integer), Normal [MPa]

weight and heavyweight concrete
EPU=epu : ultimate compression strain [m/m]
FTC=ftc : tensile strength cracking strength [kPa]

if ftc=0 no crack check will be carried out 123
if ftc>0 a crack check will be carried out
AGS=dm : max. aggregate particle size. Used in the shear [m]

stress calculations in cracks if FTC>0.
MFU=mfu : design material factor (ULS) [-] [default 1.4]
MFS=mfs : design material factor (SLS/CRW/FLS) [-] [default 1.0]
Fixed crack spacing:
SP=id : reference to fixed crack spacing data CRASP stmts.

PRI= : print data for all stored CMPGM sets
Examples:
CMPGM ID=1 GR=B45
CMPGM ID=2 GR=B65 PA=DOME FS=1-48 HS=1-16
CMPGM ID=3 GR=B45 AGS=0.010 SP=1 LA=1

CMPGM PRI=TAB
CMPGM PRI=
1) location defined by LAREA statement. Example: CMPGM ID=id LA=lan and then
the parameters. It is necessary to define the area(s) in a separate statement LAREA
where the ID numbering are the same as the CMPGM ID numbering.
2) location defined directly in CMPGM statement. Example: CMPGM ID=id PA=part

6.4.5 CMPNL - define concrete material in CSM (non-linear) analysis
124
_____________________________________________________________
Input Statement: CMPNL

______________________________________________________________
Purpose: - define concrete material property sets in CSM (non-linear) analyses. All
parameters must be input, no automatically default values.
CMPGM ID=id CCC= /FCM=fcm ECM=ecm EC1=ec1 EU1=eu1

CMPGM ID=id (TSP=tsp) (FCL=fcl) (CSF=csf) (CSL=csl)]
CMPGM ID=id FTA=fta/FTM=ftm
CMPGM (PRI= /TAB)
Parameters:
Data for compressive stresses: See Section 3.3.4.1
1. In accordance with design code compression curve:
CCC= : Flags that concrete material will be in accordance

with CMPOS, CMPNS or CMPEC.
2. In accordance with NS-EN 1992-1-1:2004, Figure 3.2. See Section 3.3.4.1.
FCM=fcm : max concrete stress (kPa) [kPa]
ECM=ecm : secant modulus of elasticity [kPa]
EC1=ec1 : strain at max stress [-]
EU1=eu1 : ultimate strain [-]
Option to include reduced compression stress:
TSP=tsp : reduced stress: sig/(0.8+tsp*eps-t)
FCL=lim : min. reduced stress = lim*sig
Option to include increased compression stress:
CSF=fac : increased stress = sig-l + fac*sig-t
CSL=lim : max. increased stress = lim*sig
Data for tensile stresses. Two different curves:
1. Bi-linear tension material curve:
FTA=fta : max. tensile stress for bi-linear curve, ref. 3.3.4.1.1 [kPa]
ECM=ecm secant modulus of elasticity if CCC= is used [kPa]
2. Non-linear tension material curve:
FTM=ftm : max. tensile stress for non-linear curve, ref. 0 [kPa]
ECM=ecm secant modulus of elasticity if CCC= is used [kPa]

LA=lan : LAREA id-number 125
PRI= : print data for all stored CMPNL sets
Examples:
CMPNL CCC= FTA=1200 ECM=0.367E+08 → Design compression curve and bi-linear
tension
CMPNL FCM=53000 ECM=36.e6 EC1=0.0024 EU1=0.0035 FTM=3800 TSP=500 FCL=0.4
CMPNL PRI=TAB
6.4.6 RMPOS – define rebar material according to DNV-ST-C502
______________________________________________________________
Input Statement: RMPOS

______________________________________________________________
Purpose: - define rebar material property sets according to DNV-ST-C502 [2]. The ID
number is related to the MP statement in the RETYP statement. The other
parameters are optionally. Values belonging to the chosen steel quality
according to DNV-ST-C502 will then be used.
RMPOS ID=id GR=gra (ESK=Esk) (FSY=fsy) (FSK=fsy) (MFU=mfu) (EPU=epu)

RMPOS ID=id (MFA=mfa) (EPA=epa) (MFS=mfs) (EPS=eps) (MFF=mff) (CCF=fac)
RMPOS (PRI=)
Parameters:
ID=id : identity number (number)
GR=gra : steel grade, must be included before all [MPa]

other parameters.
ESK=Esk : modulus of elasticity [kPa] [default 200*E6]
FSY=fsy : yield stress [kPa] [default 1000gra]
FSK=fsk : ultimate tensile strength design [kPa] [default 1000gra]

Design properties: 126
MFU=mfu : design material factor ULS [default 1.25]
EPU=epu : ultimate tensile strain ULS [default 0.010]
MFA=mfa : design material factor ALS [default 1.10]
EPA=epa : ultimate tensile strains ALS [default 0.010]
MFS=mfs : design material factor SLS, CRW [default 1.00]
EPS=eps : ultimate tensile strain SLS [default eps-y]
MFF=mff : design material factor FLS [default 1.10]
CCF=fac : compression capacity factor, ULS, ALS [default 1.00]
PRI= : prints out all stored RMPOS sets
Examples:
RMPOS ID=1 GR=500
RMPOS ID=2 FSY=500.E3 ESK=200.E6

RMPOS ID=2 MFU=1.25 EPU=0.01
RMPOS PRI=
6.4.7 RMPNS – define rebar material according to NS 3473
______________________________________________________________
Input Statement: RMPNS

______________________________________________________________
Purpose: - define rebar material property sets according to NS 3473 [3]. The ID is
related to the MP statement in the RETYP statement. The other parameters are
optionally. Values belonging to the chosen steel quality according to NS 3473
will then be used.
RMPNS ID=id GR=gra (ESK=Esk) (FSY=fsy) (FSK=fsy) (MFU=mfu) (EPU=epu)

RMPNS ID=id (MFA=mfa) (EPA=epa) (MFS=mfs) (EPS=eps) (MFF=mff) (CCF=fac)
RMPNS (PRI=)
Parameters:

other parameters.
ESK=Esk : modulus of elasticity [kPa] [default 200*1.0E6]
FSY=fsy : yield stress [kPa] [default 1000gra]
FSK=fsk : ultimate tensile strength design [kPa] [default 1000gra]

Design properties: 127
EPU=epu : ultimate tensile strain ULS [default 0.010]
EPA=epa : ultimate tensile strains ALS [default 0.010]
EPS=eps : ultimate tensile strain SLS [default eps-y]
MFF=mff : design material factor FLS [default 1.10]
CCF=fac : compression capacity factor, ULS, ALS [default 1.00]
PRI= : prints out all stored RMPNS sets
Examples:
RMPNS ID=1 GR=500
RMPNS ID=2 FSY=500.E3 ESK=200.E6
RMPNS PRI=
6.4.8 RMPEC – define rebar material according to NS-EN 1992-1-1
______________________________________________________________
Input Statement: RMPEC

______________________________________________________________
Purpose: - define rebar material property sets according to Eurocode 2. The ID is related
to the MP statement in the RETYP statement.
RMPEC ID=id GR=gra (ESK=Esk) (FYK=fyk) (FSK=fsk) (MFU=mfu) (EPU=epu)

RMPEC ID=id (MFA=mfa) (EPA=epa) (MFS=mfs) (EPS=eps)
RMPEC (PRI=)
Parameters:
GR=gra : steel grade
FYK=fyk : yield strength [kPa]
FSK=fsk : ultimate strength (design) [kPa]
Design properties:
EPU=epu : ultimate tensile strain ULS [m/m] [default 0.010]
EPA=epa : ultimate tensile strains ALS [m/m] [default 0.010]

EPS=eps : ultimate tensile strain SLS [m/m] 128
PRI= : prints out all stored RMPEC sets
Examples:
RMPEC ID=1 GR=500
RMPEC ID=2 FYK=500.E3 ESK=200.E6 MFS=1.0 EPS=1.2E-3
RMPEC ID=2 MFU=1.25 EPU=10.E-3
RMPEC PRI=
6.4.9 RMPGM – define rebar material according to MCFT
______________________________________________________________
Input Statement: RMPGM

______________________________________________________________
Purpose: - define concrete material property sets in accordance with MCFT [5].
RMPGM ID=id GR=gra (ESK=Esk) (FSY=fsy) (FSU=fsu) (ESH=esh) (EPU=epu)

RMPGM ID=id (MFU=mfu) (MFA=mfa) (MFS=mfs) (AFU=afu) (AFA=afa) (AFS=afs)
RMPGM (PRI=)
Parameters:

other parameters.
ESK=Esk : modulus of elasticity [kPa]
FSY=fsy : yield stress [kPa]
FSU=fsu : ultimate stress [kPa]
ESH=esh : strain at strain hardening [m/m]
EPU=epu : strain at ultimate stress [m/m]
MFS=mfs : design material factor SLS/CRW [default 1.0]
PRI= : prints out all stored RMPGM sets
Examples:
RMPGM ID=1 GR=500

RMPGM ID=2 FSY=500.E3 FSU=581.E3 ESH=0.007 EPU=0.040
RMPGM PRI=

6.4.10 RMPNL – define rebar material in CSM (non-linear) analysis
129
______________________________________________________________
Input Statement: RMPNL

______________________________________________________________
Purpose: - define rebar material property sets for CSM (non-linear) analysis. The ID is
related to the MP statement in the RETYP statement.
RMPNL ID=id GR=gra (ESK=Esk) (FSY=fsy) (FSU=fsu)(EPU=epu)

RMPNL (PRI=)
Parameters:

other parameters.
FSY=fsy : yield strength [kPa] [default 500 000 kPa]
FSU=fs : ultimate tensile strength [kPa] [default 500 000 kPa
EPU=epu : ultimate tensile strain [m/m] [default 0.0750]
PRI= : prints out all stored RMPNL sets
Examples:
RMPNL ID=1 FSY=440.E3 FSU=440.E3 EPU=0.010
RMPNL PRI=
6.4.11 TEMAT - define prestressing/tendon material in design
______________________________________________________________
Input Statement: TEMAT

______________________________________________________________
Purpose: - define tendon (prestressing) material property sets. Linear curve. Same
material curve used for both DNV-ST-C502, NS 3473 and EC2
TEMAT ID=id FSY=fsy ESK=Esk MFU=mfu MFA=mfa MFS=mfs MFF=mff

TEMAT ID=id (AFU=afu) (AFA=afa) (AFS=afs)
TEMAT PRI=
Parameters:


MFU=mfu : design material factor ULS Default [1.0] 130
MFA=mfa : design material factor ALS Default [1.0]
MFS=mfs : design material factor SLS Default [1.0]
MFF=mff : design material factor FLS Default [1.0]
PRI= : prints out all stored TEMAT sets
Note that default material factors are 1.0 and should be specified based on the chosen design
code.
Example:
TEMAT ID=5 FSY=1670.E3 ESK=196.E6 MFU=1.15 MFF=1.15
TEMAT PRI=
The ID is a user defined name.

PRI= prints all the stored tendon material properties on the output.
Related statements:
TETYP
TELOC
6.4.12 TMPNL - define prestressing/tendon material in CSM (non-linear) analysis
______________________________________________________________
Input Statement: TMPNL

______________________________________________________________
Purpose: - define tendon (prestressing) material property sets in CSM (non-linear)

analysis
TMPNL ID=id FSY=fsy ESK=Esk FSU=fsu EPU=epu

TMPNL PRI=
Parameters:
FSU=fsu : ultimate strength [kPa]
EPU=epu : ultimate strain [-]
PRI= : prints out all stored TMPNL sets
Example:
TMPNL ID=5 FSY=1670.E3 ESK=196.E6
TMPNL PRI=

6.5 Design Parameter Statements 131
6.5.1 DEPAR - define global design parameters
_________________________________________________________
Input Statement: DEPAR

______________________________________________________________
Purpose: - define global structural analysis parameters and parameters. None of the
parameters must be typed. Default values will be used.
DEPAR (N_LAY=n) (N_ITE=n) (D_SIG=n) (T_TOL=t) (Z_TOL=z) (U_FAI=ur)

DEPAR (D_COD=NS/EC/OS/GM) (E_MOD=em) (P_RAT=pr) (I_WAV=sg) (PRI=)
Parameters:
N_LAY=n : number of integration layers through shell [-] [default 10]

thickness (for thicknesses larger than 1 m, N_LAY
should be increased).
N_ITE=n : max number of design iterations [-] [default 100]
D_SIG=s : max stress deviation before design iteration stops [kPa] [default 10]
T_TOL=t : shell thickness tolerance. Only included in ULS, [m] [default 0.0]
ALS and FLS, not for SLS and CRW. Decreases the
shell thickness equal on each side of the centre
line.
P_TOL=p : shell thickness tolerance in %. Only included in [%] [default 0.0]

ULS, ALS and FLS, not for SLS and (replaces T_TOL
if defined)
Z_TOL=z : rebar layer z-coordinate tolerance. [m] [default 0.0]

Only included in ULS, ALS and FLS, not for SLS and
CRW. Increases the cover to the reinforcement.
Z_CHE= rebar layer x3-coordinate check will not be carried [default, check
out ON]
U_FAI=ur : UR to be reported when design iteration failure has [-] [default=10]

occurred.
E_MOD=em : linear analysis modulus of elasticity. Only used in [kPa]

connection with BASCO TYP=F statement.
P_RAT=pr : linear analysis Poisson's ratio. Only used in [-] [default 0]

connection with BASCO TYP=F statement.
I_WAV=sg : imaginary wave sign: +1 or -1 [-] [default +1]

If I_WAV=+1, then:
→ X = RW*COS(α) + IW*SIN(α) α= 0, 15, 30, 45 ...
If I_WAV=-1, then:
→ X = RW*COS(α) - IW*SIN(α) α= 0, 15, 30, 45 ...
D_COD=NS : NS 3473 code used in design [-] [default]
D_COD=EC : Eurocode 2 code used in design [-]

D_COD=OS : DNV-ST-C502 code in design [-] 132
D_COD=GM : General Method / MCFT code in design [-]
PRI= : DEPAR data will be printed in the output-file [-]
Example:
DEPAR N_LAY=20 N_ITE=50 D_SIG=20 T_TOL=0.02 Z_TOL=0.02 D_COD=EC

DEPAR PRI=
6.5.2 CRWOS - define crack width data according to DNV-ST-C502
______________________________________________________________
Input Statement: CRWOS

______________________________________________________________
Purpose: - define crack width data according to DNV-ST-C502 [2]. If no parameters are
specified, the default values will be used.
CRWOS ID=id (CW=w/w1,w2) (KT=kt/kt1,kt2) (C1=c1/c11,c12) (C2=c2/c21,c22)

CRWOS ID=id (BS=beta-s) (CS= eps-cs)
CRWOS ID=id (S0X=sox/sox1,sox2) (SOY=soy/soy1,soy2)
CRWOS ID=id (FK=f/f1,f2) (SP=id)
CRWOS ID=id (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
CRWOS (PRI=)
Parameters:
ID=id : Identity No., referenced in DECAS statement.

Crack width limits, see Table 6-10:
CW=w : rebar crack width limit, both faces [m] [default 0.0003]
CW=w1,w2 : rebar crack width limit, face 1 and 2 [m] [default 0.0003]
W0=w0 : tendon crack width limit [m] [default 0.0002]
kt-factor, see Table 6-12:
KT=kt : kt-factor, both faces [default 1]
KT=kt1,kt2 : kt-factor, face 1 and 2 [default 1]
Minimum concrete cover, see Table 6-15:
C1=c1 : minimum concrete cover, both faces [m] [default 0.05]
C1=c11,c12 : minimum concrete cover, face 1 and 2 [m] [default 0.05]
Sro:
S0X=sox : constant length with assumed loss of bond, [m] [default 0.2]
direction 1, both faces
S0X=sox1,sox2 : constant length with assumed loss of bond, [m] [default 0.2, 0.2]
direction 1, face 1 and 2

S0Y=soy : constant length with assumed loss of bond, [m] [default 0.2] 133
direction 2, both faces
S0Y=soy1,soy2 : constant length with assumed loss of bond, [m] [default 0.2, 0.2]
direction 2, face 1 and 2
Srk factor:
FK=f : factor for calc. of Srk = f*Srm, both faces [default 1.7]
FK=f1,f2 factor for calc. of Srk = f*Srm, face 1 and 2 [default 1.7]
BS=beta-s : Mean tensile stress factor used in CRW. [default 0.4]
CS=eps-cs : shrinkage strain εcs, see DNV Sec. 6 802 [default 0]
Fixed crack spacing if not calculated by ShellDesign:
SP=id : reference to fixed crack spacing data in [-]

CRASP statement
Valid area:
PA=part : structural part (max 8 characters) [default all]
FS=fs1-fs2 : F-section range (number) [default all]
HS=hs1-hs2 : H-section range (number) [default all]
PRI= : CRWOS data will be printed in the output-file [-]
Example:
CRWOS KT=1.5 CW=0.3E-3 C1=0.035
The factor kt is set to 1.5, crack width limit is set to 0.0003 on both faces, and the minimum
concrete cover is set to 0.035 on both faces.
6.5.3 CRWNS - define crack width data according to NS 3473
______________________________________________________________
Input Statement: CRWNS

______________________________________________________________
Purpose: - define crack width data according to NS 3473. If no parameters are specified,
the default values will be used.
CRWNS ID=id (CW=w/w1,w2) (KT=kt/kt1,kt2) (C1=c1/c11,c12) (C2=c2/c21,c22)

CRWNS ID=id (BS=beta-s) (CS= eps-cs) (FK=f/f1,f2) (SP=id)
CRWNS ID=id (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
CRWNS (PRI=)
Parameters:

Crack width limits : see Table 12 NS3473:

CW=w : rebar crack width limit, both faces [m] [default 0.0003] 134
CW=w1,w2 : rebar crack width limit, face 1 and 2 [m] [default 0.0003]
kt-factor : see Table 13 NS3473:
KT=kt : kt-factor, both faces [default 1]
KT=kt1,kt2 : kt-factor, face 1 and 2 [default 1]
Minimum concrete cover : see Table 15a and 15b, NS3473:
C1=c1 : minimum concrete cover, both faces [m] [default 0.05]
C1=c11,c12 : minimum concrete cover, face 1 and 2 [m] [default 0.05]
Srk factor:
FK=f : factor for calc. of Srk = f*Srm, both faces [default 1.7]
FK=f1,f2 factor for calc. of Srk = f*Srm, face 1 and 2 [default 1.7]
BS=beta-s : Mean tensile stress factor, see NS3473 [default 0.4]

A.15.6.2.1b, for εcm and εsm in clause 15.6.2.
CS=eps-cs : shrinkage strain εcs, see NS3473 15.6.2. [default 0]
Fixed crack spacing if not calculated by ShellDesign:
SP=id : reference to fixed crack spacing data in [-]

CRASP statement
Valid area:
PRI= : CRWNS data will be printed in the output-file [-]
Example:
CRWNS KT=1.5 CW=0.3E-3 C1=0.035
The factor kt is set to 1.5, crack width limit is set to 0.0003 on both faces, and the minimum
concrete cover is set to 0.035 on both faces.

6.5.4 CRWEC - define crack width data according to NS-EN 1992-1-1
135
______________________________________________________________
Input Statement: CRWEC

______________________________________________________________
Purpose: - define crack width data according to Eurocode 2. If no parameters are

specified, the default values will be used.
CRWEC ID=id (CW=w/w1,w2) (CO=co/co1,co2) (CS=eps-cs)

CRWEC ID=id (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
CRWEC (PRI=)
Parameters:
Crack width limits: see Table 7.1N, page 117:
CW=w : same limit both faces [m] [default 0.0003]
CW=w1,w2 : different limit, face 1 and 2 [m] [default 0.0003]
CS=eps-cs : shrinkage strain, see 3.1.4 [m] [default 0]
KT=kt : mean stress factor, see 7.3.4-(2) [default 0.4]
K1=k1 : bond coefficient, equation (7.11) [default 0.8]
Valid area:
PRI= : CRWEC data will be printed in the output-file [-]
Example:
CRWEC CW=0.3E-3 CO=0.035
6.5.5 CRASP – define fixed crack spacing
______________________________________________________________
Input Statement: CRASP

______________________________________________________________
Purpose: - define fixed crack spacing for CRW for NS 3473 and DNV-ST-C502
CRASP ID=id (SX=Srx/Srx1,Srx2) (SY=Sry/Sry1,Sry2)

CRASP ID=id (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
CRASP (PRI=)

Parameters:
136
ID=id : Identity No., referenced in CRWNS/CRWOS/CRWGM
Fixed crack spacing (default calculated by ShellDesign):
SX=Srx : fixed crack spacing x-direction, both faces [m]
SX=Srx1,Srx2 : fixed crack spacing x-direction, face 1 and 2 [m]
SY=Sry : fixed crack spacing y-direction, both faces [m]
SY=Sry1,Sry2 : fixed crack spacing y-direction, face 1 and 2 [m]
Valid area:
PRI= : CRASP data will be printed in the output-file [-]
Example:
CRASP ID=1 SY=0.178 SX=0.089
Related statements:
CRWNS/CMPGM/CRWOS
6.5.6 TIGHT - define tightness criteria according to DNV-ST-C502 and NS 3473
_____________________________________________________________
Input Statement: TIGHT

______________________________________________________________
Purpose: - define tightness criteria related to compression zone calculation and crack
widths for trough thickness cracks for DNV-ST-C502 (ref. section 4.1.4.4 and
4.1.4.5), NS 3473 and EC2. If no parameters are specified, the default values
will be used.
TIGHT ID=id (TC=x1,x2) (WC=hf1,wk1,hf2,wk2)

TIGHT ID=id (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
Parameters:
ID=id : Identity number, referenced in DECAS

statement.
Tightness data:
TC=x1,x2 : x1=compression zone depth [m] [default 0]

x2=ratio compression zone depth/wall
thickness [default 0]
→ final compression zone depth =
min(x1,x2*h), h=section thickness

: hf1,hf2 : ratio hydrostatic head/wall [m] [5.0,0.0002,35.0,0 137
WC=hf1,wk1,hf2,wk2 thickness .00005]
wk1 : crack width limit when hf<= hf1
wk2 : crack width limit when hf>= hf2
WE= : Equivalent crack width to be used in

tightness check
Valid area:
Example:
TIGHT ID=1 TC=0.2,0.25 WC=5,0.0002,35,0.00005
Note that results from the tightness check are given in TABLE UR=CZ for compression zone
results and TABLE UR=CT for through cracks results.
Related statements:
DECAS
6.5.7 FAPOS – define fatigue parameters (FLS) according to DNV-ST-C502
______________________________________________________________
Input Statement: FAPOS

______________________________________________________________
Purpose: - define parameters for fatigue calculations (FLS) acc. to DNV-ST-C502 [2].
Description of the FLS calculations in ShellDesign for DNV-ST-C502 is described
in Section 4.1.5. If no parameters are specified, the default values will be used.
FAPOS (NB=nwbl) (CO=c11,c12,c5) (RE=c3,c4) (SH=c11,c12) (ST=c3,c4) (EL=el)

FAPOS (UL=ul) (FA=f) (PRI=)
If verification tables are wanted:
FAPOS PA=part FS=fs1 HS=hs1 VER=ON
Parameters:
NB=nwbl : If there are different soil reactions for small [-] [default: lowest
and large waves: (AB). For the first number GRECO for all blocks]
of wave blocks (nwbl), lowest GRECO version
is used (A), for the following wave blocks,
highest GRECO version is used (B)
Example from DECAS:

DECAS LS=FLS PHA=ALL BAS=60007:CD
GRECO C will be used for the first nwbl,
GRECO D for the rest.
CO=c11,c12,c5 : Concrete C1 factors [-] [default 10.0,8.0, 1.0]

c11: compression/compression
138
c12: compression/tension
c5: concrete/grout
RE=c3,c4 : Rebar C3 and C4 factors (for Δσ>235MPa, [-] [default 19.6,6.0,
235MPa≥Δσ>65MPa, Δσ≤65MPa) 19.6,6.0, 19.6,6.0]
SH=c11,c12 : Concrete shear C1 factors [-] [default 10.0,8.0]
c11: without sign change
c12: with sign change
ST=c3,c4 : Stirrup C3 and C4 factors (for Δσ>235MPa, [-] [default 15.9,4.8,
235MPa≥Δσ>65MPa, Δσ≤65MPa) 15.9,4.8, 15.9,4.8]
EL=el : LOG (reinf. Endurance limit) [-] [default 8.301]
UL=ul : Utilization limit, miner’s sum [-] [default 0.33]
FA=f : factor for water/gas pressure when [default 0.0]
compression. (as default pressure is acting
in cracks only). See Section 4.1.5.4.
PRI= : Prints FAPOS data
FS=fs : F-section range
HS=hs : H-section range
VER=ON
Example:
FAPOS NB=5 CO=9,7,2 SH=11,9
FAPOS PA=X FS=1 HS=2 VER=ON
Related statements:
WAVED
DECAS
6.5.8 FAPAR – define fatigue parameters (FLS) according to NS 3473
______________________________________________________________
Input Statement: FAPAR

______________________________________________________________
Purpose: - define parameters for fatigue calculations (FLS) acc. to NS 3473 [3].
Description of the FLS calculations in ShellDesign for NS 3473 is described in
Section 4.2.5. If no parameters are specified, the default values will be used.
FAPAR (NB=nwbl) (CO=c11,c12) (RE=c3,c4) (SH=c11,c12) (ST=c3,c4) (EL=el)

FAPAR (UL=ul) (FA=f) (PRI=)
FAPAR PA=part FS=fs1 HS=hs1 VER=ON

Parameters:
139
NB=nwbl : If there are different soil reactions for small [-] [default: lowest
and large waves: (AB). For the first number GRECO for all
of wave blocks (nwbl), lowest GRECO version blocks]
is used (A), for the following wave blocks,
highest GRECO version is used (B)
Example from DECAS:

DECAS LS=FLS PHA=ALL BAS=60007:CD
GRECO C will be used for the first nwbl,
GRECO D for the rest.
CO=c11,c12 : Concrete C1 factors [-] [default 10.0,8.0]
c11: compression/compression
c12: compression/tension
RE=c3,c4 : Rebar C3 and C4 factors [-] [default 19.6,6.0]
SH=c11,c12 : Concrete shear C1 factors [-] [default 10.0,8.0]
c11: without sign change
c12: with sign change
ST=c3,c4 : Stirrup C3 and C4 factors [-] [default 15.9,4.8]
EL=el : LOG (reinf. Endurance limit) [-] [default 8.301]
UL=ul : Utilization limit, miner’s sum [-] [default 0.5]
FA=f : Factor for water/gas pressure when [default 0.0]
compression. (as default pressure is acting
in cracks only). See Section 4.2.5.4
PRI= : Prints FAPAR data
VER=ON
Example:
FAPAR NB=5 CO=9,7,2 SH=11,9

FAPAR PA=X FS=1 HS=2 VER=ON
Related statements:
WAVED
DECAS

6.5.9 WPARE - define areas with water pressure in cracks data
140
______________________________________________________________
Input Statement: WPARE

______________________________________________________________
Purpose: - define areas with water pressure in cracks data. To be referenced with
DWP=id in DECAS statement otherwise water pressure in cracks will not be applied in the
design calculations. See Section 3.2.4 for description of water pressure in cracks in the
conventional design method. See Section 3.3.5 for description of water pressure in cracks in
CSM analyses. Note that WAC parameter in NONLI statement has to be included if WP should
be calculated in CSM analyses.
WPARE ID=id WC=pr,hh / WP=pr / WP=z0,wd,(zcn) (FA= /1/2)

WPARE ID=id (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
Parameters:
ID=id : Identification number. To be referenced with

DWP=id in DECAS statement.
WC=pr,hh : pr = constant pressure [kN/m2]
hh = hydrostatic head. Used for tightness [m]

calculations defined in TIGHT statement.
WP=pr : Constant pressure
[kN/m2]
same as for WC statement
WP=z0,wd,zcn : Variable pressure:
z0 = water level [m]
wd = water weight density =  x g [kN/m3]
Example:
wd = LF x  x g = 1.2x1.025t/m3x9.8066m/s2 =12.062 kN/m3
where LF is load factor on water pressure according to limit
state
zcn = global coor. axis (x=1, y=2, z=3) [3]
Formula used in ShellDesign:

WP = wd * max(0,z0-z), [kN/m2]
z=design section elevation; default global Z
direction (zcn=3)
FA= : pressure acts on both faces [default]
FA=1 : pressure acts on face 1
FA=2 : pressure acts on face 2

Area definition: 141
Example:
WPARE ID=1 WC=314 PA=DOME FS=1-30 HS=1-5
WPARE ID=2 WP=0,10 FA=1 PA=DOME
Related statements:
ID must be referenced in DECAS statement, otherwise no water pressure is included.
Note:
1. If only WP=pr is defined, this will be understood as a constant pressure. Same as the
WC=pr input.
2. Load factors must be included for the water density if load factors are applied in the
BASCO statement for the water pressure load case.
3. When different water pressure for Face1 and Face2 is specified, a linear variation over
the thickness is used. However, the use of this approach should be evaluated for each
project. It is most common to use the largest water pressure to act on both faces due
to pore pressures etc. (FA=).

6.6 Section Statements 142
6.6.1 SHSEC - create shell sections/design sections
______________________________________________________________
Input Statement: SHSEC

______________________________________________________________
Purpose: - order creation of shell sections/design sections
SHSEC PA=pa SE=se [EL=el]/[XP=x,y,z] (NS=ns/NE=ne) (ET=VS) XF=x,y,z

XH=x,y,z FS=i1-i2 HS=j1-j2 (TAB=ON/OFF) (VER=lc)
Parameters:
PA=pa : structural part name (

(max 8 characters) n
a
m
e
)
SE=se : start super element number

- 1000*type+index for SESAM
- type for Abaqus
Rectangular elements:
Alternative 1: start element number to be given:
EL=el : start element number (external)
Alternative 2: start element coordinates to be given:
XP=x,y,z : start element coordinates

Alternative 3: element set number to be given.
ELSET=n : element group n, FS=1-nel, HS=1-4 where nel is

number of elements in group. Valid for shell elements
only.
Alternative 4: element set name to be given (Sesam):
ELSETNAME=n : element group name, FS=1-nel, HS=1-4

Valid for shell elements only. Not valid for Abaqus.
Triangular elements: to be stored as a separate part

TE=el1-el2 : range of external element Nos.
One section per element, FS is fixed.
Range assumed ascending by 1:
TE=21-25 -> 21,22,23,24,25
Example: SHSEC PA=tri SE=1001 TE=113-250 FS=3

HS=1-138

See Section 3.2.2 for more information about the use of 143
triangular elements and its limitations. Rectangular
elements should be used before triangular elements is
used in the FE-model.
Define variable stiffness elements if CSM analysis:
ET= VS : stiffness to be calculated for cracked concrete. [default is

linear
stiffness]
Relevant only for solid elements:
NE=ne : wanted number of elements over thickness
(max=10)
TD=x,y,z : thickness direction vector, meaningful only if

number of wanted elements are lesser than
those available.
General:
XF=x,y,z : x,y,z-components of F-direction start vector

related to global coordinate system.
XH=x,y,z : x,y,z-components of H-direction start vector

related to global coordinate system.
FS=i1-i2 : F-section range
HS=j1-j2 : H-section range
NS=n : number of sections per element [4]
TAB=ON/OFF : element table wanted or not [default OFF]
VER=n : OLC number (n) to be verified, concerning

transformation and integration of stresses
Example:
SHSEC PA=plate1 SE=1001 EL=113 XF=1,0,0 XH=0,-1,0 FS=1-7 HS=2-5
Define the structure part to be named "plate1" and the super element number is taken from
the FEM analysis and multiplied with 1000 plus the index number. EL=113 is the logical
element to start defining sections and the number is also taken from the global model.
XF=1,0,0 means that the F-axis is in positive x-direction in the global coordinate system. The
H-axis is in negative global y-direction.
The area defined is from FS 1-7 and HS 2-5.
SHSEC PA=plate1 SE=1001 EL=113 XF=1,0,0 XH=0,-1,0 FS=1 HS=2 VER=3
The same definition as the example above, except the area is different. Only one section, FS
1 and HS 2 and an integration verification table for OLC load case 3 is requested.
For alternative 3 and 4, local shell axis system from the analysis is used as 123-axes if no
SHAXE-statement is given.

6.6.2 SHAXE – define local 1,2,3-axes for design sections
144
______________________________________________________________
Input Statement: SHAXE

______________________________________________________________
Purpose: - define data for creation of local 1,2,3-axes.
SHAXE [X1=x1,y1,z1 X2=x2,y2,z2 X3=x3,y3,z3]

SHAXE [XP=xp,yp,zp XA=xa,ya,za SY=R/SY=L AL=a]
SHAXE [XC=xc,yc,zc XA=xa,ya,za SY=R/SY=L AL=a] PA=pa (FS=i1-i2) (HS=j1-j2)
Parameters:
Alternative 1:
- 123-axes given as xyz-components:
X1=x1,y1,z1 : xyz-components of 1-axis
Alternative 2:
- 3-axis points towards point P, 1-axis is approximately parallel A-vector:
XP=xp,yp,zp : x,y,z-coordinates for the point P
XA=xa,ya,za : x,y,z-components of the A-vector
SY=R : 123-axes form a right hand system [default]
SY=L : 123-axes form a left hand system
AL=a : rotate 1-axis (a) degrees towards 2-axis

( x1=cos(a)x1+sin(a)x2, x2=cos(a)x2-sin(a)x1 )
Alternative 3:
- 1,2-axes form a polar coordinate system defined by a point (C) and a direction vector
(A). 1- and 2- axis are tangents to the shell plane. 1-axis=radial direction, 2-
axis=tang. direction, 3-axis=normal to shell plane, same direction as A-vector:
XC=xc,yc,zc : x,y,z-coordinates for the point C
XA=xa,ya,za : x,y,z-comp. of the direction vector A
SY=R : 123-axes form a right hand system [default]
SY=L : 123-axes form a left hand system
AL=a : rotate 1-axis (a) degrees towards 2-axis

(x1=cos(a)x1+sin(a)x2, x2=cos(a)x2-sin(a)x1 )
Valid area:
PA=pa : structural part (name)
FS=i1-i2 : F-section range [default all]
HS=j1-j2 : H-section range [default all]
Examples:
SHAXE PA=A1 X1=1,0,0 X2=0,1,0 X3=0,0,-1 FS=1-10 (Suitable where the axes are
independent of section location.)

145
SHAXE PA=A2 XP=0,0,0 XA=0,0,1 AL=-90. FS=1-10 HS=1-5 (Suitable for cylinder walls etc.)
SHAXE PA=A2 XC=0,0,0 XA=0,0,1 FS=1-10 HS=15-50 (Suitable for circular plates and domes
with radial and hoop reinf.)
For part A1 FS=1-10, the 1-axis is in positive global x-axis, 2-axis is in positive global y-axis
and the 3-axis is in negative global z-axis.
6.6.3 SHEXT – create extrapolated design sections
______________________________________________________________
Input Statement: SHEXT

______________________________________________________________
Purpose: - give data for creation of extrapolated sections.
SHEXT PA= part [EFSi,i1,i2,i3 HS=j1-j2]/[EHS=j,j1,j2,j3 FS=i1-i2]

SHEXT FACT=f1,f2,f3/DIST=d
SHEXT FACE=0/1/2/[XP=xp,yp,zp XA=xa,ya,za]/[XC=xc,yc,zc XA=xa,ya,za
SHEXT RA=r]/[XS=xs,ys,zs RA=r]
Parameters:
PA=pa : structural part (name) [default all]
New F-section:
EFS=i,i1,i2,i3 HS=j1-j2 : i: new F-section number
i1,i2,i3: F-sections to be
extrapolated from
j1-j2: H-section range
New H-section:
EHS=j,j1,j2,j3 FS=i1-i2 : j: new H-section number
j1,j2,j3: H-sections to be
extrapolated from
i1-i2: F-section range
Methods for determination of section location:
FACT=f1,f2,f3 : Factors given in input
DIST=d : Distance from last section
FACE= : Section located on a shell element

edge
FACE=1/2 : Section located on a solid element

surface
XP=xp,yp,zp XA=xa,ya,za : Section located on a plane surface

Defined by XP=plane point,
XA=plane normal

XC=xc,yc,zc XA=xa,ya,za : Section located on a cylindrical 146
RA=r surface
Defined by XC=axis point, XA=axis
direction, RA=radius
XS=xs,ys,zs RA=r : Section located on a spherical

surface
Defined by XS=center point,
RA=radius
The coordinates are explained with figures below:
Section located on a plane surface:
Section located on a cylindrical surface:
Section located on a spherical surface:

147
Example:
SHEXT PA=WY2 EFS=1,4,3,2 HS=1 XP=-31.6,0,0 XA=-1,0,0
• PA is the name of the structural part

• EFS defines the extrapolated section and the direction of the extrapolation, from FS 4
to FS 2
• HS defines the location in H-direction
• XP is a point at the plane
• XA gives the direction of the normal vector

6.6.4 BESEC - create beam sections and print of beam forces
148
______________________________________________________________
Input Statement: BESEC

______________________________________________________________
Purpose: - define data for creation of beam sections. Beam sections are created, and
corresponding beam forces are calculated based on integrated sectional forces
and printed. Note that the 1-axis must be perpendicular on the beam section,
otherwise the beam section forces are not calculated correctly!
BESEC BS=b1-b2 [B1=x1,y1,z1 B2=x2,y2,z2]/[BA=HR] (FVF=fnm)

BESEC (TAB=GE,FM,GR)
BESEC PA=part [FS=f1 HS=h1-h2]/[HS=h1 FS=f1-f2]
Parameters:
BS=b1-b2 : beam section range to be created
LOC=text : location text, max 4 characters
Fixed beam section axes:
B1=x1,y1,z1 : xyz-components of beam section 1-axis

The beam section 1-axis must be
perpendicular on the beam section. See
figure below.
B2=x2,y2,z2 : xyz-components of beam section 2-axis
Variable beam section axes:
OBS! : beam section 1-axis = average all shell

1-axes
PN=2 : 2-axis constant, 1- and 3-axes will vary
PN=3 : 3-axis constant, 1- and 2-axes will vary
Beam sections through one or more F-sections:
FS=f1,df : f1: first F-section No.

df: F-section step [1]
HS=h1-h2 : H-section range (= integration area)
Beam sections through one or more H-sections:
HS=h1,dh : first H-section

dh: H-section step [1]
FS=f1-f2 : F-section range (= integration area)
TAB=GE,FM,GR : order print of results
- GE : geometry data
- FM : forces and moments

- GR : forces and moments suitable for graphs

Note:
149
The beam section 1-axis must be perpendicular on the beam section. See figure below.
Data for one beam section range must be spread over two or more lines:
first line : BESEC BS= ......
next lines : BESEC PA= FS= HS= : integration areas
max 10 integration areas per section range
Examples:
Example 1: 12 sections, FS=2,3,...13, one integration area:
BESEC BS=1-12 B1=1,0,0 B2=0,-1,0 FVF=ex1
BESEC PA=A2 FS=2 HS=1-24
Example 2: one section, four integration areas:

BESEC BS=1 B1=1,0,0 B2=0,-1,0 TAB=GE,GR
BESEC PA=A2 HS=1 FS=1-10
BESEC PA=A2 HS=24 FS=1-10
Comments:
- shell section geometry is fetched from an OLC-file.
- shell section forces/moments are fetched from a DEC-file.
- i.e. both an OLC-file and a DEC-file must be attached.
- beam forces and moments for all design cases are created.

6.6.5 LAREA - define location areas
150
______________________________________________________________
Input Statement: LAREA

______________________________________________________________
Purpose: - define location areas with PA= FS= and HS=. The location areas can be
referenced in CMPNS, CMPOS, CMPEC to define different areas with different
concrete properties.
LAREA ID=id PA=part FS=fs1-fs2 HS=hs1-hs2
Parameters:
PA=part : structural part (max 8 characters) (name)
FS=f1-f2 : F-section range (number) [default all]
HS=h1-h2 : H-section range (number) [default all]
Examples:
LAREA ID=1 PA=SW1 FS=33-38 HS=20-22
Definitions of three areas where two areas will have the same parameters.
Note: One location ID may be defined by means of more lines.
Related statements:
CMPNS
CMPOS
CMPEC
6.6.6 SESET - define design section sets
______________________________________________________________
Input Statement: SESET

______________________________________________________________
Purpose: - define shell section sets with global coordinates or with FS and HS numbers.
When use of global coordinates, ShellDesign will find the corresponding FS and
HS numbers.
SESET ID=id PA=part XR=x1,x2 YR=y1,y2 ZR=z1,z2 / FS=fs1-fs2 HS=hs1-hs2
Parameters:
PA=part : part name (name)

FS=fs1-fs2 : FS-range (number) [default all] 151
HS=hs1-hs2 : HS-range (number) [default all]
XR=x1,x2 : x-range (number) [default all]
YR=y1,y2 : y-range (number [default all]
ZR=z1,z2 : z-range (number [default all]
PRI= : SESET data will be printed in the output-file
Example:
SESET ID=1 PA=BASE XR=1,30 YR=1,5
SESET ID=20 PA=TS FS=50-60 HS=1-8
SESET PRI=
Related statements:
RELOC
SRLOC
SHAXE

6.7 Reinforcement Statements 152
6.7.1 RETYP - define rebar layer types
______________________________________________________________
Input Statement: RETYP

______________________________________________________________
Purpose: - define rebar layer types to be referenced in RELOC statement.
RETYP ID=id MP=rp AR=area [OS=offs]/[C2=c2 TH=th] [(C2=c2)

RETYP ID=id (DI=diam) (NR=nreb) (BC=coef)] (LB=lb)
Parameters:
LB=lb : label for use in XTRACT plot file (max 16 char.)
ID=id : type number (max 8 digits)
MP=rp : rebar material property set to be used (see

RMPOS/RMPNS/RMPEC)
AR=area : cross section area/unit length [m2/m]
To define the position of layers within section, the following data combined with RELOC
data are used.
If fixed offset:
OS=offs : face 1/2 defined in RELOC: distance concrete [m]

face - rebar layer center
: face 0 defined in RELOC: section center – [m]

rebar layer center
If variable offset:
C2=c2 : actual nominal cover [m]
TH=th : thickness of rebar layer [m]
If crack widths shall be calculated (used in CRWOS, CRWNS and CRWEC statement):
C2=c2 : actual nominal cover. [m]
DI=diam : single rebar diameter [m]
NR=nreb : number of rebars in bundle [default 1]
BC=coef : bond coefficient [default 0.75]
Rules: (see also RELOC statement)

- to define a fixed position, give OS= or C2= and TH=
- to define a relative position, give TH=
- outer layers must be placed in a fixed position.
- inner layers may be placed in a fixed position or relative to the preceding layer.
Use TABLE TAB=RS to verify that layer data are correct.
Note: The unit depends on the input used in the GE analysis, but is normally [m].

Example:
153
RETYP ID=20101 MP=1 AR=2094.E-6 C2=0.060 TH=0.025 DI=0.020 NR=1 BC=0.75
The ID is a user defined name and it is important to notice that ShellDesign does not read a
system out of this ID. In a previous project, the following numbering system was used:
The ID number for each RETYP statement describes the type of reinforcement based
on a system ID=UUVVW as explained below.
UU VV W
rebar number of bars in internal surface / external surface
diameter the layer / section center
25 / 32 05 / 10 / 15 / 20 1 / 2 / 0
The numbers of bars in layer means

05 = 0.5 bars
10 = 1.0 bars
15 = 1.5 bars
20 = 2.0 bars
In this example, ID=201001, means 1ø20, internal surface.
MP refers to the ID given in RMPOS, RMPNS, RMPEC. That is, the reinforcement parameters
RMPOS/RMPNS/RMPEC ID=1 refers to MP=1. The reinforcement area, AR=2094 m 2/m. The
nominal concrete cover is C2=0.060 m, the thickness of the rebar layer is 0.025 m, the
diameter of the bar is 0.020 m, there are 1 bar in the bundle, NR=1 and the bond coefficient
is BC=0.75.
Related statements:
RMPOS
RMPNS
RMPEC
RELOC
6.7.2 RELOC - define rebar locations
______________________________________________________________
Input Statement: RELOC

______________________________________________________________
Purpose: - define rebar locations with PA, FS and HS or SS input.
RELOC ID=id RT=rt1-rt2 FA=face AL=alfa (RP=12/XY/XZ/YZ)

RELOC ID=id (PA=part) (FS=f1-f2) (HS=h1-h2) (SS)
Parameters:
ID=id : location identity, max 4 characters (name)

RT=rt1-rt2 : rebar type range, see RETYP (number)
FA=face : shell face (0/1/2) [default 0]

AL=alfa : direction angle (-90 to +90) [default 0] 154
OS=offs : This offset will overrule the one given in (m)
RETYP statement.
face 1/2: distance concrete face-layer centre
face 0: x3-coordinate layer centre
Reference plane for the direction angle AL:

- If an OLC-file is attached to the run, it is possible to define a global plane as reference
plane, default is the local 12-plane
- The angle is measured from the first axis towards the second axis
- Examples: from 1-axis towards 2-axis, from x-axis towards y-axis
RP=12 : reference plane is local 12-plane [default]
RP=XY : reference plane is global XY-plane
RP=XZ : reference plane is global XZ-plane
RP=YZ : reference plane is global YZ-plane
Location area alternative 1:

PA=part : part identity (name) [default all]
SS=ss : Section set No., see SESET statement, (number) [default all]
Examples:
RELOC ID=X11 RT=16101-20101 FA=1 FS=5-10 HS=3
RELOC ID=Y21 RT=20101 FA=2 AL=90
The ID in each RELOC statement is a user defined name and it is suitable to describe the
location of the chosen reinforcement type based on a system ID=ABC as shown below. Note
that this is a user defined ID number and ShellDesign does not read a system out of this ID.
In a previous project, the following system was used:
A B C
global direction of Concrete face Layer

rebar
X / Y / Z 0 / 1 / 2 1 / 2 / 3 / 4
The RT= parameter is based on the ID number from the RETYP statement, RETYP ID=20101
refers to RT=20101. FA refers to which face the reinforcement is located towards, or if it is in
the center of the section if FA=0. The angle AL is the direction of the rebar related to the local
1-axis as default. The Y21 reinforcement in the example is illustrated below.

155
If the location area is not used, the reinforcement will be a general reinforcement all over the
structure. If it is required to have another reinforcement intensity in a specific area, a second
line has to be typed with the necessary reinforcement and the input will overrule the given
input in the specific area. If the RT is set to a range, it is possible to use the option "find
necessary reinforcement"
Note: if two layers with equal identity are located in the same section, the first layer will be
replaced by the second layer if face and angle for both layers are equal. If not, an error
message is printed. There is a limit of 30 rebar layers per section, this may be increased.
Related statements:
RETYP
6.7.3 RERES - define rebar area reservations
______________________________________________________________
Input Statement: RERES

______________________________________________________________
Purpose: -define rebar layer cross section area reservations.
If extra reinforcement is required due to forces that is not ensured with the loads from global
FEM analysis, ShellDesign can with this statement, calculate the extra capacity of the ordinary
reinforcement without affecting the ordinary design results (UR=CS, UR=RS etc).
The utilization ratio is calculated as URtot= (Adesign+Arsv)/Atot
You will then see if extra reinforcement must be added in drawings or if the extra capacity
from ordinary design reinforcement is enough.
RERES ID=id(,ONLY) RA=ra [(PA) (FS=f1-f2) (HS=h1-h2)]
Parameters:
ID=id : rebar layer location identity, max 4 characters (name)
ID=id,only : only one layer is affected

RA=ra : reserved cross section area/unit area [m2/m] 156
Location area:
Example:
RERES ID=Y11 RA=147.E-6 PA=SW FS=50-65 HS=17-19
RERES ID=Y11,ONLY RA=147.E-6 PA=SW FS=50-65 HS=17-19
With the ID statement, ShellDesign finds the face and angle based on the Y11 definition in the
RELOC statement. If more layers in the same direction and face are present, ShellDesign add
this in the reserved reinforcement calculation as default. By typing ID=id, ONLY the
calculations will only be performed for the current layer (ID) and no other layers present. RA
is the needed extra reinforcement area, and PA, FS and HS are the location data where the
extra reinforcement is added.
Related statements:
RELOC
RETYP
SRRES
TABLE UR=RR
6.7.4 REFAC – define rebar area reservations, factor
______________________________________________________________
Input Statement: REFAC

______________________________________________________________
Purpose: - define rebar layer cross section area reservations with factor.
RERES ID=id RF=rf [(PA) (FS=f1-f2) (HS=h1-h2)]
Parameters:
ID=id : rebar layer location identity, max 4 characters. (name)

(name as defined by RELOC statements)
RF=rf : cross section area reduction factor [-] [default 1.0]
Location area:
Example:
REFAC ID=X1 RF=0.8 PA=A2 FS=5-10 HS=3

6.7.5 SRTYP - define shear reinforcement types
157
____________________________________________________________
Input Statement: SRTYP

______________________________________________________________
Purpose: - define shear reinforcement types to be referenced in SRLOC statement.
SRTYP ID=id MP=mp AR=area DI=diam LB=lb
Parameters:
ID=id : type number
MP=mp : material property set (see RMPNS statement)
AR=area : cross section area / unit area [m2/m2]
DI=diam shear reinforcement diameter [m]

LB=lb : label (max 16 characters)
Example:
SRTYP ID=1 MP=1 AR=2827.E-6 LB=1D12c200c200
Related statements:
RMPOS
RMPNS
RMPEC
6.7.6 SRLOC - define shear reinforcement location
______________________________________________________________
Input Statement: SRLOC

______________________________________________________________
Purpose: - define shear reinforcement location areas.
SRLOC ID=id ST=st [(PA) (FS=f1-f2) (HS=h1-h2)]
Parameters:
ID=id : location identity (name)
: stirrup type number (see SRTYP

ST=st
statement)


HS=h1-h2 : H-section range (number) [default all] 158
SS=ss : Section set No., see SESET statement (number) [default all]
Example:
SRLOC ID=stiA1 ST=5 FS=5-10 HS=3
The ID parameter is a user defined name.
Related statements:
SRTYP
6.7.7 SRRES – define shear reinforcement reservations
______________________________________________________________
Input Statement: SRRES

______________________________________________________________
Purpose: - define shear reinforcement cross section reservations.
If extra reinforcement is needed due to forces that are not ensured with the loads from the
global FEM analysis, ShellDesign can with this statement calculate the extra capacity of the
ordinary reinforcement without affecting the ordinary design results (UR=CS, UR=RS etc).
The utilization ratio is calculated as URtot= (Adesign+Arsv)/Atot
You will then see if extra reinforcement must be added in drawings or if the extra capacity
from ordinary design reinforcement is enough.
SRRES ID=id RA=ra [(PA) (FS=f1-f2) (HS=h1-h2)]
Parameters:
ID=id : location identity (name)
RA=ra : reserved cross section area/unit area (m2/m2)
Location area:
Example:
SRRES ID=ST RA=2500.E-6 PA=A1 FS=5-10 HS=3
With the ID statement, ShellDesign finds the ID given in the SRLOC statement.
RA is the needed extra shear reinforcement area, and PA, FS and HS are the location data
where the extra shear reinforcement is added.
Note : if reserved area > total area, an error message is also printed
(total area is defined by SRLOC statements)

159
Related statements:
SRLOC
RERES
TABLE UR=RR
6.7.8 TETYP - define prestressing (tendon) layer types
______________________________________________________________
Input Statement: TETYP

______________________________________________________________
Purpose: - define prestressing (tendon) layer types to be referenced in TELOC

statement.
TETYP ID=id MP=mp AR=area (E0=eps-0) (OS=offs)
Parameters:
ID=id : identification number (number)

MP=mp : material property set (number)
AR=area : cross section area [m2/m]
E0=eps-0 : initial strain [m] [default 0]
face 1/2: distance concrete face-layer centre
OS=offs : [m] [default 0]
face 0: x3-coordinate layer centre
Example:
TETYP ID=1 MP=1 AR=1350.E-6 E0=5.2E-3
The ID is a user defined name, all layers within a section must have different ID's. MP=1
relates to the TEMAT ID=1, which is the material properties defined in the TEMAT statement.
AR=1350.E-6 means a cross section area of 1350 mm2/m. The initial strain is defined as 5.2E-
3.
Related statements:
TEMAT
TELOC

6.7.9 TELOC - define tendon layer data
160
______________________________________________________________
Input Statement: TELOC

______________________________________________________________
Purpose: - define tendon (prestressing) layer data.
TELOC ID=id TT=tt [(FA=face) (TB=tb) (AL=alfa) (RP=XY/XZ/YZ)

TELOC ID=id (PA=part) TELOC (FS=f1-f2) (HS=h1-h2)]
Parameters:
ID=id : identification number (number)
TT=tt : tendon layer type No., see TETYP.
FA=face : offset from shell section face = 0/1/2, see [default 0]

TETYP.
TB=tb tang(beta) = dx3/dl [default 0]
AL=alfa : direction angle in 1-2 plane [default 0]
Reference plane for the direction angle alfa:

- If an OLC-file is attached to the run it is possible to define a global plane as reference
plane, default is the local 12-plane.
- The angle is measured from the first axis towards the second axis
- Examples : from 1-axis towards 2-axis, from x-axis towards y-axis
RP=XY : reference plane is global XY-plane
RP=XZ : reference plane is global XZ-plane
RP=YZ : reference plane is global YZ-plane
Location area:

Example:
TELOC ID=1 TT=1 AL=90 PA=LDOME-A FS=5-10 HS=3
Note:
All layers within a section must have different identity Nos. If not, an error message is printed.
There is a limit of 10 layers per section, may be increased
Related statements:
TETYP
TEMAT

6.7.10 TELAY – include prestressing (tendon) data generated with TenLoad
161
______________________________________________________________
Input Statement: TELAY

______________________________________________________________
Purpose: - opens a file containing prestressing tendon layer data created by TenLoad
program. The TELAY data supersedes TETYP and TELOC data, but TEMAT
must be included with the same ID numbers referenced in the TELAY input in
TenLoad.
TELAY OF=of PRE=path
Parameters:
OF=of : File name

Path to file name. File will be copied to work
[default: work
PRE=path : directory. NB! Directory names with space must
directory]
be enclosed by “ ”.
Example:
TELAY NF=TELAY.INP PRE=TEL-files\model1
Note that the TELAY input file must include reference to a tendon material ID (MP=id) which
is connected to the id in TEMAT statement when the file is generated in TenLoad program.
Related statements:
TEMAT

6.8 Load Statements 162
6.8.1 LOADC – rename ordinary analysis load cases
______________________________________________________________
Input Statement: LOADC

______________________________________________________________
Purpose: - rename original analysis load case numbers (ALC’s) in the FE-analysis result
file to new load case numbers in ShellDesign (OLC’s). If LOADC is not defined,
ShellDesign will automatically name the OLC’s to the same load case numbers
as the original ALC’s.
LOADC RN=n LC=i/LC=i1-i2/LC=i1-i2,j1

LOADC TAB=
Parameters:
RN=nr : run number
LC=i : ALC-no. |i| is wanted, OLC-no.=ALC-no.
LC=i1-i2 : ALC-Nos |i1-i2| wanted, OLC-Nos=ALC-Nos
LC=i1-i2,j1 : ALC-Nos |i1-i2| wanted, OLC-no.=|j1,j1+1,..|
TAB= : order a table of wanted load cases
Example:
LOADC RN=1 LC=2,1000
From run number 1 in SESTRA, analysis load case number 2 (ALC 2) is renamed to ShellDesign
OLC number 1000 (OLC 1000)
It is common practice to rename the global load case (ALC) numbers with new load case (OLC)
numbers in ShellDesign with the LOADC statement to define different load groups, e.g water
pressure load cases have numbers between 1200-1299. Example of ShellDesign input is shown
below:
% -------------------------------------------------------------------------------------------
% ALC TO OLC=
% -------------------------------------------------------------------------------------------
%
% LOADC ALC_nr = OLC=_nr
LOADC RN=1 LC=1,1200 % Hydropressure up to elevation 123.000m (Wadam)
LOADC RN=1 LC=2,1100 % Global Uniform Acceleration (1.0*G) in Positive X-direction
LOADC RN=1 LC=3,1101 % Global Uniform Acceleration (1.0*G) in Positive Y-direction
LOADC RN=1 LC=4,1102 % Global Uniform Acceleration (1.0*G) in Positive Z-direction
%
% -------------------------------------------------------------------------------------------
Related statements:
BASCO
OLCFI

6.8.2 GRECO - define new support systems to the FE-model
163
______________________________________________________________
Input Statement: GRECO

______________________________________________________________
Purpose: - define new support system to the FE-model with BASCO statement and ELC
load cases. See Section 5.5.2 for detailed description of how to define new
support systems
GRECO ID=sl BAS=i1-i2,../ELC=j1-j2

GRECO VER=
Parameters:
ID=v : version is identified by a single letter
BAS=i1-i2 : involved BAS combinations, max 6
ELC=j1-j2 : define relevant range of equilibrium load cases [default all]
VER= : ELC verification tables are printed
Example:
GRECO ID=B BAS=21,22,31-34 ELC=1-34
GRECO VER=
The GRECO statement combines basic load combinations with OLC’s for which equilibrium is
wanted. A version letter to each GRECO must also be defined, and then different letter defines
specific support systems. Note that the OLC’s in the BASCO defining the GRECO, must be an
OLC and not ELC. Example of ShellDesign input is shown below:
% -------------------------------------------------------------------------------------------
% GRECO A - UNIFORM PRESSURE, HORIZONTAL REACTION FX AND FY, LINEAR MOMENTS MX, MY AND TORSION
% -------------------------------------------------------------------------------------------
%
BASCO ID=4001 LF=1.0 OLC=1503 % FX
BASCO ID=4002 LF=1.0 OLC=1504 % FY
BASCO ID=4003 LF=1.0 OLC=1500 % FZ
BASCO ID=4006 LF=1.0 OLC=1512 % MZ
%
%
% -------------------------------------------------------------------------------------------
% GRECO F - UNIFORM PRESSURE, HORIZONTAL REACTION FX AND FY, MOMENTS MX, MY
WITH PEAK AT OUTER PERIMETER AND UNIFORM TORSION ON BASE SLAB
% -------------------------------------------------------------------------------------------
%
BASCO ID=4051 LF=1 OLC=1503 % FX
BASCO ID=4052 LF=1 OLC=1504 % FY
BASCO ID=4053 LF=1 OLC=1500 % FZ
BASCO ID=4056 LF=1 OLC=1512 % MZ
%
GRECO ID=F BAS=4051-4056
% -------------------------------------------------------------------------------------------

164
Related statements:
LORES

6.8.3 LORES - define load resultants of analysis load cases
165
______________________________________________________________
Input Statement: LORES

______________________________________________________________
Purpose: - define load resultants of the OLC’s where the response should be re-
calculated to a new support system defined with GRECO.
LORES lc REAL/IMAG r1 r2 r3 r4 r5 r6
Parameters:
lc=lc : OLC-number
REAL=real : real part
IMAG=imag : imaginary part
ri=ri : load resultant number i
The LORES input statements and parameters can automatically be generated with:
SIN= : -Include PRI=OLC to list OLC reaction forces. Defined by LOADC statement.
-Include PRI=ALC to list ALL reaction forces on SIN file
Example:
% OLC X-LOAD Y-LOAD Z-LOAD X-RMOM Y-RMOM Z-RMOM
LORES 1 REAL -9.7283E+02 4.1105E-09 4.8136E+05 -8.2269E-03 2.5802E+06 -4.9957E-08
LORES 2 REAL -4.5987E+02 -2.2554E+01 -5.1088E+03 1.1006E+03 -2.3625E+04 -6.0220E+02
LORES 2 IMAG -2.0579E+03 -2.9789E+00 2.7959E+03 4.1212E+03 -3.6255E+05 -4.0526E+03
The input listed above are output from SESTRA; the file named sestra.lis. The input can also
be automatically generated by ShellDesign with:
LORES SIN=
LORES PRI=OLC
Note 1: the number of load resultants must be in the range 1-6 and must be kept constant
for all LORES statements.
Note 2: if LORES is used with a merged OLC-file as input, all LORES statements MUST be
sorted according to OLC-numbers regardless of which OLC-file the loads are taken from!
Related statements:
GRECO

6.8.4 INPLC - define load case with user input forces
166
______________________________________________________________
Input Statement: INPLC

______________________________________________________________
Purpose: - define load case with input shell section forces/moments (user input).
INPLC ID=id
[N1=n1/N2=n2/N12=n12/M1=m1/M2=m2/M12=m12/V1=v1/V2=v2] /
[n1/n2/n12/m1/m2/m12/v1/v2]
Parameters:
ID=id : identification number
Layout 1:
N1=n1, N2=n2 N12=n12 : [kN/m, [default 0]

M1=m1 M2=m2 M12=m12 named components kNm/m]
V1=v1 V2=v2
Layout 2:
n1 n2 n12 m1 m2 m12 v1 : ordered components [kN/m, [default 0]

v2 kNm/m]
Location area:
PA=pa : structural part (max 8 characters) (name) [default all]
FS=i1-i2 : F-section range (numbers) [default all]
HS=j1-j2 : H-section range (numbers) [default all]
Note:
Components not given will have a value = 0.0.
Example:
INPLC ID=1 N1=1000 N2=-210 M1=500 PA=DOME FS=1-30 HS=1-5
INPLC ID=2 1000 -210 0 500 PA=DOME FS=1-30 HS=1-5
For part "dome"; FS=1-30 HS=1-5, N1=1000 kN/m, N2=-210 kN/m and M1=500kNm/m. The
other components are set to 0.

6.8.5 BASCO - define load combinations
167
______________________________________________________________
Input Statement: BASCO

______________________________________________________________
Purpose: - define load combinations. See Section 5.5.5 for description of the method.
BASCO ID=id (LF=fac) (LDF=j) (TYP= /TYP=R/TYP=I/TYP=F)

BASCO ID=id ILC=lc/OLC=lc/ELC=lc/BAS=lc/PLC=lc/BLC=lc (TXT=txt)
Parameters:
ID=id : identification number (0<id<10000)
LF=fac : load case factor = fac [default 1.0]
LDF=j : reference to Location Dependent Factor No j

defined with LDFAC statement
TYP= : Marks the load as an ordinary load. [default]
Note: if the OLC/ELC is ordinary a dynamic load

from the FE-analysis, ShellDesign will
automatically recognize this load as a dynamic
load with real and imaginary parts and there is no
need to type TYP=R/I in the BASCO statement as
shown below. Ordinary load in this sense, means
dynamic load if also in FE-analysis.
TYP=R : Marks the load as the real part of a complex wave.

Must be defined before OLC/ELC. Cannot be
defined before BAS.
TYP=I : Marks the load as an imaginary part of a complex

wave. Must be defined before OLC/ELC. Cannot
be defined before BAS.
TYP=F : Marks the load case to be handled with factors

according to FSFAC statement. A method to
account for different load factors on forces and
strains. See description of the method in FSFAC
statement.
Load cases:
- lc may be given as triplets (max 10 tripl.):
ILC=lc : load case source = ILC (input load case)
OLC=lc : load case source = OLC (original load case)
ELC=lc : load case source = ELC (equilibrium load case)
BAS=lc : load case source = BAS (BAS combination)
PLC=lc : load case source = PLC (prestressing load case)
TXT=txt : identification text, max 80 char.

Examples:
168
BASCO ID=1010 LF=-1.744 OLC=1100 LF=0.349 OLC=1101
BASCO ID=7010 LF=1 BAS=1000 LF=1 BAS=1010 LF=1 BAS=1020 LF=1 BAS=1030 LF=1
BAS=1040
In the BASCO statement, ILC, OLC, ELC BAS and PLC can all be combined with or without load
factors, but note that the last defined LF= will be used.
Note:
- Within one statement LF, LDF and TYP data keep their value until a new value is
entered.
- There is no data transfer between statements.
- The data for one BAS may be spread over two or more consecutive BASCO lines.
Related statements:
LOADC
LDFAC
FSFAC
INPLC
6.8.6 LDFAC - define location dependent load factors
______________________________________________________________
Input Statement: LDFAC

______________________________________________________________
Purpose: - define location dependent load factors. To be used when loads have different
load factors for different design sections and when there are different load
factors on the 8 sectional design forces.
LDFAC ID=id FA=fac/Fc1-c2=fac (EX=e) [(PA) (FS=f1-f2) (HS=h1-h2)]
Parameters:
ID=id : identification number
FA=fac : common factor for all 8 components
Fc1-c2=fac : factor for component numbers from c1 to c2
: eccentricity of membrane forces [m] [default 0 for

EX=e
all]
Location area:

Examples:
169
LDFAC ID=1 FA=1.3 PA=DOME FS=1-30 HS=1-5
LDFAC ID=2 F1-3=1.3 F4-6=1.0
All BASCO statements with a LDF=1 will have a load factor of 1.3 for all components (N1, N2,
N12, M1, M2, M12, V1 and V2) in the area FS=1-30, HS=1-5 in the structure part defines as
DOME.
All BASCO statements with a LDF=2 will have a load factor of 1.3 for N1, N2 and N12 while
the other components will have a factor of 1 (no changes compared to basis). This is valid for
all structure parts.
Note:
- Component numbers: 1=N1 2=N2 3=N12 4=M1 5=M2 6=M12 7=V1 8=V2
- Components not given a factor will have a factor = 0.0.
- The eccentricity is positive if forces are located towards face 2.
- If LDFAC is defined more than once for a section the last one is valid.
The 8 components are calculated as follows:

N1 = n1*f1
N2 = n2*f2
N12 = n12*f3
M1 = f4*m1-e*N1
M2 = f5*m2-e*N2
M12 = f6*m12-e*N12
V1 = v1*f7
V2 = v2*f8
Related statements:
BASCO
6.8.7 FSFAC - define factors to be used on forces and strains
______________________________________________________________
Input Statement: FSFAC

______________________________________________________________
Purpose: - define forces and strain factors to be used for TYP=F loads in BASCO
statement. See detailed description of the procedure below. Note that the
TYP=F loads are only applicable for ULS, ALS, SLS/CRW. In design checks in
FLS, TYP=F loads are neglected.
FSFAC ID=id (CCN=) (CCM=fac) (REN= fac) (REM= fac) (SHN= fac) (SHM= fac)
FSFAC ID=id (SHV= fac) (CWN= fac) (CWM= fac)
FSFAC ID=id (PA=part) (FS=fs1-fs2) (HS=hs1-hs2)
Parameters:
ID=id : set identification number.

CCN=fac : membrane force factor in ULS/ALS/SLS for concrete [default 1.0]
170
stress
CCM=fac : moment force factor in ULS/ALS/SLS for concrete stress [default 1.0]
REN=fac : membrane force factor in ULS/ALS/SLS for rebar stress [default 1.0]
REM=fac : moment force factor in ULS/ALS/SLS for rebar stress [default 1.0]
SHN=fac : membrane force factor in ULS/ALS for shear capacity [default 1.0]
SHM=fac : moment in ULS/ALS for shear capacity [default 1.0]
SHV=fac : shear factor in ULS/ALS for shear capacity [default 1.0]
CWN=fac : membrane strain factor in CRW for crack widths [default 1.0]
CWM=fac : curvature factor in CRW for crack widths [default 1.0]
ECT=fac : EC crack width factor in EC2 design code. 0.6*SigS/Es- [default 0.6]
ECT*epsT (Eq 7.9)
Area definition:
PRI= : print all stored FSFAC sets
Rule: if more than one set is found for a section, the last set is used.
Example:
FSFAC ID=1 CCN=0.5 CCM=0.5
FSFAC PRI=
Detailed description of the procedure:

The load must be marked as F load (TYP=F) in the BASCO statement. Depending on the actual
design checks, the effect from TYP=F load are combined with the other ordinary loads, either
as sectional forces or as strains. The strain εt in a layer located a distance z from the middle
plane of the shell, and in a direction defined by the angle a from the x-axis, equals:
The application of the forces in ShellDesign marked with TYP=F for CRW, SLS, ULS, ALS design
are described below. Note that the application of the method must be carefully considered and
understood when applied.
The referred factors below are found and changed in the FSFAC statement. Default factors is
1.
CCN, REN, SHN, CWN: Factors for membrane components.

[N1, N2, N12] and [ε1, ε2, γ12]
CCM, REM, SHM, CWM: Factors for moment.

[M1, M2, M12] and [κ1, κ2, κ12]

SHV: shear component
171
[V1, V2]
εL = strains from ordinary loads, strains based on the non-linear sectional response calculation.
εf = strains from TYP=F loads, linear elastic strains calculated based on linear E-modulus and
Poisson ratio. E-modulus and Poisson ratio is an input to ShellDesign and defined through
DEPAR statement.
FL = forces from ordinary loads
Ff = forces from TYP=F load
Factors related to CRW and crack width control:

CWN and CWM are strain factors; hence the response is calculated based on the strain:
ε1 = εL + [CWN,CWM]•εf
Utilization calculations are performed for the strain set shown above.
The strains, εf, from TYP=F loads are calculated from stress resultants and stiffness from the
linear elastic analysis; εf = f(Ff, Eanalysis , ν ). The resulting strains are then multiplied by
the relevant factors and added to the strain from ordinary loads, εL.
Factors related ULS/ALS/SLS and concrete and reinforcement control:

Note that the SLS control in ShellDesign is related to stresses in concrete and reinforcement
and not crack width control (CRW).
CCN/CCM and REN/REM are force factors and the response is calculated based on these sets
of forces:
F1 = FL + [CCN/CCM]•Ff
F2 = FL + [REN/REM]•Ff
Utilization calculations are performed for the two force sets as shown above and the following
algorithm is used:
URconcrete = URc(F1)
URreinforcement = URr(F2)
The utilization ratios for concrete and reinforcement are calculated with TYP=F load as part of
the total force, and for all runs there are ‘equilibrium’ between reinforcement and concrete.
Hence the TYP=F load forces are included in the non-linear sectional response calculation.
Factors related ULS/ALS for shear control:

The SHN and SHM factors are used both as a force factor and for calculation of strain in
longitudinal reinforcement. The response is calculated based on this set of forces:
F1 = FL + [SHN,SHM,SHV]•Ff
Utilization calculation is performed for the force set shown above and the following algorithm
is used:
URshear = URs(F1)
The utilization ratios for shear are calculated with FSFAC as part of the total force, and for all

runs there are ‘equilibrium’ between reinforcement and concrete. Hence the TYP=F load forces
172
are included in the non-linear sectional response calculation.
FLS:
In design checks in FLS, TYP=F loads are neglected.
6.8.8 STFOR - define additional forces in longitudinal reinforcement due to shear
______________________________________________________________
Input Statement: STFOR

______________________________________________________________
Purpose: - define additional forces in longitudinal reinforcement due to shear forces.

These forces are not automatically accounted for in ShellDesign but may be
included in the design calculations with STFOR and DECAS statement. See
detailed description of the method in Section 4.1.2.2 for DNV-ST-C502, Section
4.2.2.2 for NS 3473 and Section 4.3.2.2 for EC2.
STFOR ID=id (MMAX=mmax) (MMIN=mmin) (PA=part) (FS=f1-f2) (HS=h1-h2)
Parameters:
: identification number. Referenced in DECAS

ID=id
statement. (max=99999)
: maximum principal global bending moment [default 1e9]

MMAX=mmax
(ULS/ALS)
: minimum principal global bending moment [default 1e9]

(ULS/ALS). Note that MMAX and MMIN are
MMIN=mmin
only relevant for NS 3473 and DNV-ST-
C502.
Current area:
Examples:
STFOR ID=1 MMAX=500 MMIN=-100 PA=DOME FS=1-30 HS=1-5
STFOR ID=1 MMAX=200 MMIN=0 PA=DOME FS=1-30 HS=6-9
Related statements:
DECAS

6.8.9 WAVED - define wave (dynamic) distribution data for fatigue (FLS)
173
______________________________________________________________
Input Statement: WAVED

______________________________________________________________
Purpose: - define wave distribution data or other dynamic distribution data for fatigue
calculations (FLS). Typically presented in Metocean reports etc. with
information on sample distribution and wave scatter diagrams. ShellDesign
uses this data when calculation the stress range included in FLS capacity
checks formulas. See also Section 7.1.3.1 where the result table from FLS
design calculations are explained.
WAVED id fi ni
Parameters:
id : Distribution identity number. Same as the BAS-id.
fi : Wave/dynamic load factor in block i, fi, for BAS ID=id.
Note that this factor will only be used on the dynamic load for
each block. If static loads are defined in BASCO statement,
these will have the load factor as specified in the BAS
combination only.
The dynamic load will have both load factor from BASCO
statement and the factor, fi, for each block.
fi is used when calculating Ni in formula:

𝑘
𝑛𝑖
𝐷=∑ ≤𝜂
𝑁𝑖
𝑖=1
where Ni is the number of cycles causing fatigue failure
ni : Number of waves in block i.
ni in formula:
𝑘
𝑛𝑖
𝐷=∑ ≤𝜂
𝑁𝑖
𝑖=1
Note:
- Max. 20 wave blocks may be given for each distribution

- Distribution data may be spread over more lines
- The number of wave directions is determined by the maximum value of wave
distributions and is consistent with the number of FLS combinations.
- The WAVED ID must correspond to the same BASCO ID

Example 1:
174
Define BAS combination to be referenced in WAVED statement:
BASCO ID=5230 LF=1.2 BAS=120 LF=1.3 BAS=201
where BAS 120 is defined in a BASCO statement as a static load, and BAS 201 is fined in a
BASCO statement as a dynamic load with real/imaginary part. Note that if BAS 201 contains
dynamic load from FE-analysis (OLC), ShellDesign will automatically recognize this load as a
dynamic load. See BASCO statement.
Define dynamic load distribution data with i=2:

% BAS ID fi ni
WAVED ID=5230 0.25 123640
WAVED ID=5230 1.23 123640
The section forces as basis for calculating σmax, σmin, Vmin and Vmax when calculating Ni in
formula:
𝑘
𝑛𝑖
𝐷=∑ ≤𝜂
𝑁𝑖
𝑖=1
are hence:
Block i=1: SectionForcesBAS120*1.2 + SectionForcesBAS201*1.3*0.25

Block i=2: SectionForcesBAS120*1.2 + SectionForcesBAS201*1.3*1.23
Example 2:
19 blocks, id=6001, will be connected to BAS id=6001:

WAVED 60001 0.01753 32726374 % → Block 1 with dynamic load factor f1=0.01753 and n1=32726374
WAVED 60001 0.05259 20729671 % → Block 2 with dynamic load factor f2=0.05259 and n2=20729671
WAVED 60001 0.08765 7221759
WAVED 60001 0.12268 2235165
WAVED 60001 0.15781 680143
WAVED 60001 0.19292 216198
WAVED 60001 0.2279 74404
WAVED 60001 0.26301 27792
WAVED 60001 0.29994 11107
WAVED 60001 0.34581 4669
WAVED 60001 0.39776 2037
WAVED 60001 0.44881 913
WAVED 60001 0.49908 417
WAVED 60001 0.54922 193
WAVED 60001 0.60027 90
WAVED 60001 0.6543 42
WAVED 60001 0.71131 20
WAVED 60001 0.76935 9
WAVED 60001 0.86652 6

Examle 3, from project:
175
Related statements:
BASCO
DECAS
FAPOS
FAPAR

6.9 Design Statements 176
6.9.1 DECAS - define load cases to be code checked according to limit state
______________________________________________________________
Input Statement: DECAS

______________________________________________________________
Purpose: - define load cases to be code checked according to wanted limit state.
Additional input such as water pressure in cracks etc. related to the load case
is also defined. Numerous load cases (ILC, OLC, ELC, BAS) can be defined in
the input file, but the DECAS statement defines which to be calculated and
post-processed within ShellDesign.
DECAS LS=ULS/ALS/SLS/CRW (CW=id) (DWP=id) (DCW=id) (DTC=id) (PHA=tri)

(EMP=OK) (STL=id) ILC=tri/OLC=tri/PLC=tri/ELC=tri:V/BAS=tri:V
Parameters:
LS=lim : limit state, lim=ULS/ALS/SLS/CRW/FLS
If additional tensile forces due to shear forces should be included:
STL=id : Activates additional tensile forces according to the

design code specified in DEPAR statement. Id is
defined in STFOR statement.
If water pressure in cracks should be included in design:
DWP=id : Water pressure in crack ID for design calculations, see

WPARE statement. Must be included if the code check
should include the water pressure in crack effect.
POR= : Pore pressure for shear design in NS 3473. If POR= is

included, water pressure is included over the entire
section, wp*t for shear design in ULS and ALS. Will
not affect the in-plane design. See Section 4.2.2.3.
Only applicable for NS 3473 design checks.
If limit state is CRW:
DCW=id : crack width data id defined in

CRWNS/CRWEC/CRWOS statement
DTC=id : tightness data id defined with TIGHT statement
If waves/dynamic loads are present:
PHA=tri : wanted phase angles (integer 0-360)
tri: ph1,ph1-ph2-step (max 10 triplets)

max number of wave phases = 24
PHA=ALL: give 24 wave phase angles (0 15 30 ... 345)

General: 177
EMP=OK : BAS-combinations that does not exist allowed.
Example: DECAS LS=ULS EMP=OK BAS=101-199
ILC=tri : ILC-load cases. Related to INPLC statement.
OLC=tri : OLC-load cases. Related to RFILE and LOADC

statement.
PLC=tri : PLC-load cases. Related to TELOC statement.
ELC=tri:V : ELC-load cases. Related to RFILE, LOADC and GRECO

statement.
BAS=tri:V : BAS-combination. Related to BASCO statement, and

GRECO statement if use of version letter, V.
tri : lc1,lc2-lc3,lc4-lc5-step (max 10 triplets)
V : version letter(s), defined by GRECO statements. If

omitted, all versions are used.
TXT=txt : design case identification text, max 80 char.

TXT= must be the last item in the line, the
text is attached to all design cases defined in line.
if txt contains spaces, use TXT="t x t".
Note:
If CSM analyses is executed by a NONLI statement, only BAS-comb can be specified in DECAS.
Examples:
DECAS LS=ULS DWP=5 ILC=1-5
DECAS LS=SLS ILC=1,4,5-8,13-21-2
DECAS LS=ALS PHA=0,45,90 BAS=304:BC
DECAS LS=FLS PHA=ALL BAS=101-106
DECAS LS=CRW CW=1 ILC=1,4,5-8,13-21-2

6.10 Print/Status Statements 178
6.10.1 LISTIN – print input file to output file for documentation
______________________________________________________________
Input Statement: LISTIN

______________________________________________________________
Purpose: - print input file to output file for documentation
LISTIN LIST=ALL/MAIN
Parameters:
LIST=ALL : List all incdf files to output file
LIST=MAIN : List only main input file to outputfile
Example:
LISTIN LIST=ALL
6.10.2 FILST - give file status for input files
______________________________________________________________
Input Statement: FILST

______________________________________________________________
Purpose: - give file status for input files. The status will be printed at the end of the
ShellDesign output file.
FILST (NAME=name) (VERS=vers) (DATE=date) (RESP=resp) PRI=
Parameters:
NAME=name : file identity (max 48 characters)
VERS=vers : file version (max 8 characters)
RESP=resp : file responsible (max 4 characters)
PRI= : print all current FILST lines
Example:
FILST NAME=RETYP_Lower_domes VERS=1.0 DATE=8jan-94 RESP=kf

6.10.3 SINST - give SIN-file status for input files
179
______________________________________________________________
Input Statement: SINST

______________________________________________________________
Purpose: - give SIN-file status for input files.
SINST (RESP=resp) (DATE=date) (TIME=time)
Parameters:
RESP=resp file responsible (max 4 characters)
TIME=time : time of last revision (max 8 characters)
Example:
SINST RESP=nar DATE=12-Apr-07 TIME=16:41:41
6.10.4 HEADL - give text for table headings
______________________________________________________________
Input Statement: HEADL

______________________________________________________________
Purpose: - give text for table headings.
HEADL text
Note: Up to 3 headlines will be printed. Max number of characters is 64. Additional lines will
replace the third line.
Example:
HEADL this is headline no. 1
HEADL this will also be headline no. 3

6.10.5 PRIWF – define output
180
______________________________________________________________
Input Statement: PRIWF

______________________________________________________________
Purpose: - order direct output to file and/or screen.
PRIWF OF=fnm/NF=fnm (NF=) CW=ON/OFF) PRI=
Parameters:
OF=fnm : output to old file (append mode)
NF=fnm : output to new file
NF= : current output file is closed
CW=ON : output wanted in Command Window

CW=OFF : output not wanted in Command Window (default)
PRI= : print name of current output file
Example:
PRIWF NF=ex1.sdo CW=OFF
Output will be printed on a new file named ex1.sdo. No output is wanted in the Command
Window. This will save run-time.
6.10.6 TABLE - define print of results in tables
______________________________________________________________
Input Statement: TABLE

______________________________________________________________
Purpose: - order print of tables. See Section 8 for detailed description of the output
results from the tables listed below.
TABLE TAB/UR= ...........
Parameters:
Data fetched from OLC file (FEM-result file, EXECD= ):
TAB=NC : element node coordinates. DECFI ND=ON has to be included to print table.
SE=se : superelement No. (1000*type+index)
EL=el : element number

TAB=ND : node displacements. DECFI ND=ON must be included to print table.
SE=se : superelement No. (1000*type+index)

X1=x1,y1,z1 : X1 axis, node displ. = d1 181
X2=x2,y2,z2 : X2 axis, node displ. = d2
X3=x3,y3,z3 : X3 axis, node displ. = d3
ENR=n1-n2 : external node triplets
TAB=EL : element data.
TAB=IN : integration data.
TAB=EX : extrapolation data.
TAB=AX : 123 axes components.
TAB=GE : geometry data.
TAB=OL : List of all OLCs on OLC-file
CC=x,y : Cell centre coordinates. If radius and angle of section origo are wanted.
TAB=FM : shell section forces/moments for OLC/ELC.
TAB =ST : Element and sections stiffness data. Element number el must be included:
EL=el : External element number
Stiffnesses:
c = concrete
r = reinforcement
t = post-tensioned reinforcement
s = sum
BAS combination OLC/ELC factors (PA= FS= HS= must be included):
TAB=OC : OLC factors for BAS combinations.
TAB=EC : ELC factors for BAS combinations.
TAB=BC : BAS/OLC/ELC factors for first level below a BAS combination.
BAS=id : BAS combination identification.
PHA=ph : wave phase for combinations containing waves.
ph = lc1,lc2-lc3,lc4-lc5-step
(max 10 triplets)
Load Resultants (PA= FS= HS= must be included):
TAB=LR : load resultants for BAS combinations
BAS=id : BAS combination identification
PHA=ph : wave phase for combinations containing waves
ph = lc1,lc2-lc3,lc4-lc5-step
(max 10 triplets)
Data fetched from Design file (design calculations, EXECD=V):
TAB=CMP : concrete material properties for design cases.
section forces for design cases.

TAB=DF : Water Pressure forces/moments and haunch forces are included.
Forces due to temperature loads is not included.
TAB=WF : Water Pressure forces/moments for design cases.

TAB=PF : shell section peak forces/moments for design cases. 182
TAB=DP : principial forces/moments and directions for design cases.
TAB=PP : Peak principial forces/moments and directions for design cases.
TAB=DR : detail response data table for design cases.
TAB=DRV : design case verification table for General Method (MCFT).
Section Reinforcement area:
TAB=SR : each rebar layer area within design sections are printed.
TAB=RS : rebar layer areas sorted for each face and direction.
Reinforcement Quantity:
TAB=RQ : all reinforcement located in design sections are integrated.
Tables of peak utilization:
UR=MAX : Max UR for concrete and reinforcement over an area. Default max UR
for each Part.
UR=CS : concrete compressive stresses. (LS=ULS/ALS/SLS only)
UR=RS : max rebar layer stresses. (LS=ULS/ALS/SLS only)
UR=RC : min rebar layer stresses. (LS=ULS/ALS/SLS only)
UR=RR : capacity reserved area of rebar layers. (LS=ULS/ALS/SLS only)
UR=TS : prestressed reinforcement (tendon) layer stresses. (LS=ULS/ALS/SLS

only)
UR=VC : concrete shear tensile failure capacities. (LS=ULS/ALS only)
UR=CC : concrete shear compression failure capacities. (LS=ULS/ALS only)
UR=ST : stirrup shear capacities. (LS=ULS/ALS only)
UR=CW : crack widths face 1 and 2. (LS=CRW only)
UR=TW : prestressed reinforcement crack widths. (LS=CRW only)
UR=CZ : tightness based on min. compression zone defined in TIGHT statement

(LS=CRW only)
UR=CT : tightness based on max. crack widths defined in TIGHT statement

(LS=CRW only)
TV=tv : threshold value, only sections with peak UR>tv will be printed.
FM= : section forces and moments to be included.
Peak value sections:
SK=E : peak values are printed for each section [default]
SK=F : for each F-section peak values found in H-section range are printed
SK=H : for each H-section peak values found in F-section range are printed
SK=A : one section, where the peak value is found, is printed
Load cases to be printed:
ILC=tri : ILC load case range

OLC=tri : OLC load case range 183
ELC=tri:V : LC load case range
BAS=tri:V : BAS load case range
lc1,lc2-lc3,lc4-lc5-step
tri :
(max 10 triplets)
version letter(s), defined by GRECO statements. If omitted, all versions are

V :
printed
Limit State to be printed:
limit state (ULS,ALS,SLS,CRW,FLS)

LS=lim :
[default: all]
Rebar layer identities to be searched:
rebar location id.

RL=id :
[default: all]
RL=ALL : each present rebar location id.
Rebar layer direction angle to be searched:
Rebar direction angle

AL=alfa :
[default: all]
Section faces to be searched:
FA=id : id=1 or id=2
FA=ALL : both faces are printed
Tendon identities to be searched:
single tendon layer identity

TL=id :
[default: all]
TL=ALL : each present tendon layer
General for both OLC-file and design file:

Sections to be printed:
: current part
PA=part
[default: all]
: F-section range
FS=i1-i2
[default: all]
: H-section range
HS=j1-j2
[default: all]
Format for section forces and moments:
ND=0 : 0 digits after the decimal point
ND=3 : 3 digits after the decimal point
Print redirected to an old file:

OF=fnm : output to old file (append mode)

OF= : output to general output file 184
Print redirected to a new file:
NF=fnm : output to a new file
6.11 Plot Statements
6.11.1 XTFIL - define XTRACT plot
______________________________________________________________
Input Statement: XTFIL

______________________________________________________________
Purpose: - define XTRACT plot files.
Data is fetched from an OLC-file and optionally from a DEC-file.
XTFIL FN=fnm PA=pa (FS=i1-i2) (HS=j1-j2) (PI=LF) (PI=RC)
Parameters:
Data are fetched from an OLC-file and optionally from a DEC-file:
FN=fnm : name of plot file (max 32 characters)
Plot sections:
PA=pa : structural part – must be defined to create a plot (max 8 characters)
FS=i1-i2 : F-section range [default: all]
HS=j1-j2 : H-section range [default: all]

Default Plot Items fetched from OLC-file:
PI=AX : 123-axes
PI=FH : F- and H- section numbers
PI=TH : shell thickness
Default Plot Items fetched from DEC-file:
PI=RE : rebar layer cross section area
PI=RC : rebar configuration layer cross section areas
PI=TE : tendon layer cross section area
PI=ST : stirrup cross section area
Default items if design cases are present:
PI=ND : node displacements (only area plot)
PI=DF : design forces and moments

forces.
Water Pressure forces/moments and haunch forces
are included.

Forces due to temperature loads not included. 185
PI=PF : principal membrane forces
PI=PM : principal moments
PI=PS : principal shear forces
Default items if design calculations are present:
PI=PE : principal face strain
PI=CS : utilization ratio concrete stresses
PI=RS : utilization ratio rebar stresses
PI=TS : utilization ratio tendon stresses
PI=SC : utilization ratios shear capacity
PI=CW : utilization ratio crack widths
PI=TW : utilization ratio crack widths at tendons
Non-Default Plot Items (to be selected if wanted):
PI=LF : location dependent load factors
Peak value plot only:
PV= : only peak plots of all design cases are plotted

provided that more than one design case is stored.
Legend level tolerances :

areas within tolerance will be in same legend
REBTOL=n : rebar tolerance in mm2 (>0) [10]
TENTOL=n : tendon tolerance in mm2 (>0) [100]
THITOL=n : thickness tolerance in mm (>0) [10]
Legend level (number of levels on legend for rebar area and thickness)
NUMLEV=n (Default 64)
Turn of label plots :
REBLAB=OFF : No rebar labels are plotted [ON]
THILAB=OFF : No thickness labels are plotted [ON]
Time used for plotting (Default off) :
TIMEIT
Note:
- If more than one Part is included in DESEC statement or with OLCFI statement,
include the different PA/FS/HS also in XTFIL statement.
- Make just one selection: PI=AX,DF,UC......
- If the plot-file is defined by more than one statement, make the selection in just one
of them.
- Unknown items are ignored without any message.
- Line plots may be selected within the 3D plot in Xtract.

Examples:
186
One part:
XTFIL FN=bottom-slab PA=BS FS=1-30 HS=1-5
Two parts:
XTFIL FN=bottom-slab PA=BS1 FS=1-30 HS=1-5
XTFIL FN=bottom-slab PA=BS2 FS=1-30 HS=1-5
A range has to be selected for both F-sections and H-sections[NAR1][NAR2]
Comments:
- A Xtract plotfile contains data fetched from the OLC-file and the DEC-file.
- From the OLC-file, F-and H-sections, thickness, node -and element numbers as well
as 123-axis can be plotted.
- From the DEC-file, more information can be fetched.
- If EXECD DM= is given, a design-file (DEC-file) is created which contains section data
and reinforcement data.
- If DECAS also is given, the design file will also include section forces.
- If EXECD DM=V and DECAS is given, the design-file will also include utilization ratios.
6.12 General statements
6.12.1 INCDF – reference to additional input file
______________________________________________________________
Input Statement: INCDF

______________________________________________________________
Purpose: - opens an additional input file
INCDF (file)
Parameters:
path : file name or path see examples below.
Example:
INCDF analysis.inp
INCDF subfolder\analysis.inp
INCDF D:\ShellDesign\example\analysis.inp
Note that the full path to all additional inp-files will be written in the out-file for reference. In
the top example the referenced file is place in the same folder as the main inp-file. In the
second it is placed in a subfolder and the third example the full path is given.

7 RESULT DESCRIPTION IN TABLES 187
This section gives a description of the results in tables from ShellDesign. All results available
in ShellDesign can be presented in tables. See also Section 6.10.5 where all available tables
and input to ShellDesign are shown.
7.1 Detailed Sectional Response Data – TAB=DR

This result table is the most informative table in ShellDesign. The table is printed for the
relevant limit state and include detailed information of the response in a specific design section
according to chosen design code described in Section 4. All other tables give summary results
from this table.
Input:
TABLE TAB=DR
Output:
DR table output is different for ULS/ALS/SLS/CRW and FLS limit state and some differences
for the chosen design code. Only DR tables from DNV-ST-C502 are shown below, but the small
differences in the DR tables for NS 3473 and EC2 are self-explaining. However, for the MCFT
code, the DR table has some differences as explained in Section 7.1.4.
7.1.1 DR table output - ULS, ALS and SLS limit state

Detailed design response : TABLE TAB=DR
Shell Section : PART=TS FS=43 HS=20 XC=10.000 YC=4.606 ZC=0.000
Dimensions : thic t11 t12 t21 t22
0.500 0.000 0.000 0.000 0.000
Thickness tolerance : 0.000 Rebar position tolerance : 0.000
Load : BAS101 PHA : Limit State : ULS W-press. face 1,2 : 500. 500.
LE=load effect
WP=effect of water pressure in cracks (N,M) and/or haunches (V)
TE=total effect
Forces/moments :
N1 N2 N12 M1 M2 M12 V1 V2
LE 0. 0. 0. -1111. 0. 8. 940. -2.
WP 177. 173. -19. -12. 12. 1. 0. 0.
TE 177. 173. -19. -1123. 13. 9. 940. -2.
Design Code : DNV-ST-C502 Sept. 2012

Crack response*1000 (ft=0)
eps1 eps2 gamma12 kappa1 kappa2 kappa12 gamma13 gamma23
TE 3.594 0.177 -1.354 -29.988 -0.001 7.982
Concrete face stresses : face theta eps-c sig-c sig-cu URc
1 85.528 0.201 0. 0. 0.000
1 -4.472 -3.928 -21075. -18700. 1.127 **
2 -8.530 11.342 0. 0. 0.000
2 81.470 -0.074 -1231. -9668. 0.127
Rebar layer stresses :
id area 3-coor alfa eps-r sig-r sig-ru URr
X2 0.004908 0.200 0.000 9.592 434783. 434783. 1.000
Y2 0.004908 0.200 90.000 0.177 30719. 434783. 0.071
X1 0.004908 -0.200 0.000 -2.404 -418004. 434783. -0.961
Y1 0.004908 -0.200 90.000 0.176 30673. 434783. 0.071
Tendon layers :
id area 3-coor alfa 1000eps sigma-t sigma-u URt
11 0.005971 -0.050 0.000 6.885 1167395. 1451304. 0.804

Shear tensile failure :
alfa Valfa Vcd URcd Ast Vsd URst 188
-0.147 940.057 0.000 1.000 0.010908 1920.756 0.489
Shear compression failure :
alfa Valfa Vccd URcc
-0.147 940.057 2272.050 0.414
Section data:

0.500 0.000 0.000 0.000 0.000
Load : BAS101 PHA : Limit State : ULS W-press. face 1,2 : 500. 500.
XC = global X coordinate of the design section in FEM analysis

YC = global Y coordinate of the design section in FEM analysis.
ZC = global Z coordinate of the design section in FEM analysis.
thic = thickness of concrete shell section, h.
t11 = thickness variation at face 1 in dir. 1, t11. See Section 5.1
t12 = thickness variation at face 1 in dir. 2, t12 . See Section 5.1
Thickness tolerance = tolerance on section thickness.
Rebar position tolerance = tolerance on concrete cover C2 for rebar position.
Load = ILC, OLC, ELC, BAS – load combination number.
PHA = Phase angle is wave is present
Limit State = ULS, ALS, SLS
W-press = water pressure in cracks, [kN/m2] at face 1 and/or face 2.
Sectional forces/moments:
LE=load effect
TE=total effect
Forces/moments :
N1 N2 N12 M1 M2 M12 V1 V2
LE 0. 0. 0. -1111. 0. 8. 940. -2.
WP 177. 173. -19. -12. 12. 1. 0. 0.
TE 177. 173. -19. -1123. 13. 9. 940. -2.
LE = sectional forces due to input load case (ILC, OLC, ELC,

BAS) [kN/m].
WP = sectional forces due to water pressure in cracks and/or
haunches, [kN/m]. Water pressure forces are N1, N2,
N12, M1, M2 and M12. If V1 and V2 are included, these
forces are derived from haunches.
TE = Total effect. Sum of LE and WP. Total effect is the basis
for the design calculations and calculated response,
[kN/m].

Sectional response - state of strain with reference to mid-section:
189
Crack response*1000 (ft=0)
TE 3.594 0.177 -1.354 -29.988 -0.001 7.982
ft = concrete tensile strength used in the calculation of state

of strain.
eps1 = Strain in direction 1, ε1.
gamma12 = In-plane strain, γ12.
kappa1 = Curvature about 2 axis, κ1.
kappa12 = In-plane curvature, κ12.
gamma13/gamma23 = Out of plane strain, γ13, γ23 – out of plane response.
Concrete stresses and utilizations:
Concrete face stresses : face theta eps-c sig-c sig-cu URc

1 85.528 0.201 0. 0. 0.000
1 -4.472 -3.928 -21075. -18700. 1.127 **
2 -8.530 11.342 0. 0. 0.000
2 81.470 -0.074 -1231. -9668. 0.127
face = concrete face.

theta = Angle θ with reference to Figure 8-1.
eps-c = principal strain εI and εII with reference to Figure 8-1.
sig-c = concrete stress based on principal strain εI and εII.
sig-cu = maximum allowable concrete stress. Material factors and
fc2d included.
URc = utilization ratio of concrete - sig-c/sig-cu.
The calculations of principal strains and directions at the concrete face are performed in
accordance with Mohr’s circle as shown in Figure 8-1.
Figure 7-1: Mohr’s circle for calculation of principal strains and directions in ShellDesign

Reinforcement stresses and utilizations:
190
Rebar layer stresses :
id area 3-coor alfa eps-r sig-r sig-ru URr
X2 0.004908 0.200 0.000 9.592 434783. 434783. 1.000
Y2 0.004908 0.200 90.000 0.177 30719. 434783. 0.071
X1 0.004908 -0.200 0.000 -2.404 -418004. 434783. -0.961
Y1 0.004908 -0.200 90.000 0.176 30673. 434783. 0.071
id = reinforcement identity.
area = reinforcement cross section area [m2/m].
3-coor = distance from concrete center to rebar center.
alfa = rebar angle with reference to 1. direction. Angle measured
counter-clockwise from 1-axis.
eps-r = strain in rebar.
sig-r = stress in rebar.
sig-ru = maximum allowable reinforcement stress. Material factors
included.
URr = utilization ratio of reinforcement - sig-r/sig-ru.
Tendons (prestressed reinforcement):
Tendon layers :
id area 3-coor alfa 1000eps sigma-t sigma-u URt
11 0.005971 -0.050 0.000 6.885 1167395. 1451304. 0.804
id = tendon identity.
area = tendon cross section area [m2/m].
3-coor = distance from concrete center to tendon center.
alfa = tendon angle with reference to 1. direction. Angle
measured counter-clockwise from 1-axis.
1000eps = strain in tendon.
sigma-t = stress in tendon.
sigma-u = maximum allowable tendon stress.
URt = utilization ratio of tendon - sigma-t/sigma-u.
Shear reinforcement:
Tensile failure:
Shear tensile failure :

alfa Valfa Vcd URcd Ast Vsd URst
-0.147 940.057 0.000 1.000 0.010908 1920.756 0.489
alfa = angle α with reference to 1. direction. “one

dimensional”/uniaxial condition (V γ, N γ, M γ) is
established for different directions. The most utilized
direction is printed.
Valfa = transverse shear forces in direction α.
Vcd = shear capacity at tensile failure without shear
reinforcement.

URcd = utilization ratio for tensile failure in concrete without shear
191
reinforcement - Valfa/Vcd.
Ast = shear reinforcement cross section area [m2/m2].
Vsd = shear capacity of shear reinforcement.
URst = utilization ratio for tensile failure in concrete with shear
reinforcement
Compression failure:
Shear compression failure :

alfa Valfa Vccd URcc
-0.147 940.057 2272.050 0.414
alfa = angle α with reference to 1. direction. “one

dimensional”/uniaxial condition (V γ, N γ, M γ) is
established for different directions. The most utilized
direction is printed.
Valfa = transverse shear forces in direction α.
Vccd = shear capacity for compression failure
URcc = utilization ratio for compression failure in concrete -
Valfa/Vccd.
7.1.2 DR table output – CRW limit state - crack widths

0.500 0.000 0.000 0.000 0.000
Load : BAS100 PHA : Limit State : CRW W-press. face 1,2 : 500. 500.
LE=load effect
TE=total effect
Forces/moments :
N1 N2 N12 M1 M2 M12 V1 V2
LE 0. 0. 0. -656. 0. 4. 555. -1.
WP 169. 1. -12. -14. 0. 1. 0. 0.
TE 169. 1. -12. -670. 0. 5. 555. -1.

Average response*1000 ft= 1136.
TE 0.548 0.002 -0.079 -5.312 -0.010 0.487
Crack widths :
case face cr-depth Srk angle 1000epav 1000W 1000Wu URw
TE 2 0.330 0.314 -3.159 1.522 0.464 0.300 1.547 **
Tendon No. 11 0.285 0.087 0.200 0.435

Section data:
192
0.500 0.000 0.000 0.000 0.000
Load : BAS100 PHA : Limit State : CRW W-press. face 1,2 : 500. 500.

t11 = thickness variation at face 1 in dir. 1, t11. See Section 5.1.
t12 = thickness variation at face 1 in dir. 2, t12 . See Section 5.1.
PHA = Phase angle if wave is present
Limit State = CRW
LE=load effect
TE=total effect
Forces/moments :
N1 N2 N12 M1 M2 M12 V1 V2
LE 0. 0. 0. -656. 0. 4. 555. -1.
WP 169. 1. -12. -14. 0. 1. 0. 0.
TE 169. 1. -12. -670. 0. 5. 555. -1.

BAS) [kN/m].
are forces derived from haunches.
[kN/m].
2D sectional response - state of strain with reference to mid-section:

Average response*1000 ft= 1136.
TE 0.548 0.002 -0.079 -5.312 -0.010 0.487
ft = concrete tensile strength used in the calculation of state

of strain.

193
gamma13/gamma23 = Out of plane strain, γ13, γ23 – out of plane response. Not
included in 2D sectional response.
Crack widths and utilizations:

Crack widths :
case face cr-depth Srk angle 1000epav 1000W 1000Wu URw
TE 2 0.330 0.314 -3.159 1.522 0.464 0.300 1.547 **
Tendon No. 11 0.285 0.087 0.200 0.435
face = concrete face where cracks appear.

cr-depth = crack depth.
Srk = characteristic crack spacing.
angle = angle of crack direction normal (measured counter-
clockwise from 1-axis direction)
1000epav = Average strain, εsm, and calculated with the contribution
of concrete tensile strength of βsftk between the cracks.
1000W = calculated crack width with εcm included as βsftk/Eck
1000Wu = maximum allowable crack width.
The calculations of crack direction are performed in accordance with Mohr’s circle as shown in
Figure 8-2.
Figure 7-2: Mohr’s circle for calculation of crack directions in ShellDesign
The detailed response data table (TAB=DR) only prints results if there are crack width present
at either face 1 or face 2, or both. If no data is printed, the section is uncracked.

7.1.3 DR table output – FLS limit state
194
It must be noted that the DR table for FLS limit state reports a sum of Miner Sum results for
several BAS combinations, hence this table is relatively different from a DR table for ULS, ALS,
SLS and CRW limit state. For a more detailed table, see Section 7.1.3.1.
Fatigue design case : BAS=100-120

Shell Section : PART=SHAFT1 FS=1 HS=1 XC=0.000 YC=0.000 ZC=0.000
0.800 0.000 0.000 0.000 0.000
Water pressure in cracks, face 1/2 : 0. 0.
Limit Miners Sum 0.500 MIN-S UR

Concrete face 1 : 10.579 21.158**
Concrete face 2 : 199.614 399.227**
Rebar layer failure : X1 0.397 0.794
Rebar layer failure : X2 0.290 0.579
Rebar layer failure : Y1 0.931 1.863**
Rebar layer failure : Y2 5.437 10.873**
Shear tensile failure : 0.000 0.000
Shear compression failure : 0.000 0.000
Stirrup failure : 0.000 0.000
Fatigue design case = BAS combinations included in the Miner’s Sum calculations.
Water pressure in cracks = water pressure in cracks, [kN/m2] at face 1 and/or face 2.
Limit Miners Sum = Utilization limit, η, defined in FAPAR/FAPOS
MIN-S = Calculated Miner’s Sum. See also verification table in
section 7.1.3.1 below.
UR = MIN-S/Limit Miners Sum for the different checks; Concrete,
Rebar, Tendons, Shear
Note:
𝑘 𝑘
𝑛𝑖
MIN-S = 𝐷 = ∑ 𝑑𝑀𝑆𝑖 = ∑
𝑁𝑖
𝑖=1 𝑖=1
where:
k: the number of stress blocks used per load
ni: the number of cycles in stress block i
Ni: the number of uniform cycles with the same mean, stress range and duration which causes
failure.
𝐷 MIN-S
𝑈𝑅 = =
𝜂 Limit⁡Miners⁡Sum

7.1.3.1 Verification table – FLS limit state
195
The FLS results are a sum of stress variations for more than one load combination and if more
details are needed to understand the results, a verification table can be printed for a wanted
design section. The verification table is printed with the following input.
Input:
FAPAR PA=SHAFT1 FS=1 HS=1 VER=ON
Output:
Detailed tables for fatigue design case :
Section id. : PART = SHAFT1 FS = 1 HS= 1
Section thickness [m] : 0.780
Thickness tolerance [m] : 0.020 Rebar position tolerance [m] : 0.020
Water pressure [kPa] : Face1 = 0. Face2 = 0.
Pore Pressure factor : 0.00
I_WAV factor : -1.00
Contributions from BAS combination : BAS100

PHA N1 N2 N12 M1 M2 M12 V1 V2
STATIC 500. 0. 0. 500. 0. 0. 0. 0.
R-WAVE 4000. 0. 0. 300. 0. 0. 0. 0.
I-WAVE 0. 0. 0. 0. 0. 0. 0. 0.
WAVE 0.0 4000. 0. 0. 300. 0. 0. 0. 0.
WAVE 15.0 3864. 0. 0. 290. 0. 0. 0. 0.
WAVE 30.0 3464. 0. 0. 260. 0. 0. 0. 0.
WAVE 45.0 2828. 0. 0. 212. 0. 0. 0. 0.
WAVE 60.0 2000. 0. 0. 150. 0. 0. 0. 0.
WAVE 75.0 1035. 0. 0. 78. 0. 0. 0. 0.
WAVE 90.0 -0. 0. 0. -0. 0. 0. 0. 0.
WAVE 105.0 -1035. 0. 0. -78. 0. 0. 0. 0.
WAVE 120.0 -2000. 0. 0. -150. 0. 0. 0. 0.
WAVE 135.0 -2828. 0. 0. -212. 0. 0. 0. 0.
WAVE 150.0 -3464. 0. 0. -260. 0. 0. 0. 0.
WAVE 165.0 -3864. 0. 0. -290. 0. 0. 0. 0.
WAVE 180.0 -4000. 0. 0. -300. 0. 0. 0. 0.
WAVE 195.0 -3864. 0. 0. -290. 0. 0. 0. 0.
WAVE 210.0 -3464. 0. 0. -260. 0. 0. 0. 0.
WAVE 225.0 -2828. 0. 0. -212. 0. 0. 0. 0.
WAVE 240.0 -2000. 0. 0. -150. 0. 0. 0. 0.
WAVE 255.0 -1035. 0. 0. -78. 0. 0. 0. 0.
WAVE 270.0 0. 0. 0. 0. 0. 0. 0. 0.
WAVE 285.0 1035. 0. 0. 78. 0. 0. 0. 0.
WAVE 300.0 2000. 0. 0. 150. 0. 0. 0. 0.
WAVE 315.0 2828. 0. 0. 212. 0. 0. 0. 0.
WAVE 330.0 3464. 0. 0. 260. 0. 0. 0. 0.
WAVE 345.0 3864. 0. 0. 290. 0. 0. 0. 0.
BAS Block Factor N_Blocks

Block data : BAS100 1 0.0258 2560556
BAS = BAS combination for calculation of CAP_MAX and

CAP_MIN
Block = Block data line in WAVED input, 1 means first
distribution block line for BAS, 2 means second
distribution block line for BAS and so on. Max. 20 block
distributions lines may be given for each BAS
combination.
Factor = Load factor, fi, for dynamic load in Block, same as input
in WAVED statement
N_Blocks = Number of cycles, ni, in Block, same as input in WAVED
statement

ID dMS N MAX PHA_MAX CAP_MAX MIN PHA_MIN CAP_MIN MAX/MIN-UNITS
Concrete face 1 : 0.000000 0.468219E+11 -2137.72 180 17662.8 0.00 0 17662.8 [kPa]
Concrete face 2 : 0.000000 0.861578E+07 -5083.73 180 17069.8 0.00 0 17069.8 [kPa] 196
Rebar layer failure : X1 0.000367 0.272276E+04 464.00 0 454.5 -30.50 180 454.5 [MPa]
Rebar layer failure : X2 0.000000 0.348509E+07 95.56 0 454.5 -54.51 180 454.5 [MPa]
Rebar layer failure : Y1 0.000000 Infinity 0.00 0 454.5 0.00 0 454.5 [MPa]
Rebar layer failure : Y2 0.000000 Infinity 0.00 0 454.5 0.00 0 454.5 [MPa]
Shear tensile failure : 0 0.100E-19 0.100E+21 0.00 0 0.0 0.00 0 0.0 [kN]
Shear principal tens. fail.: 0/0 0.100E-19 0.100E+21 0.00 0 0.0 0.00 0 0.0 [kN]
Shear compression failure : 0 0.100E-19 0.100E+21 0.00 0 0.0 0.00 0 0.0 [kN]
Shear principal comp. fail.: 0/0 0.100E-19 0.100E+21 0.00 0 0.0 0.00 0 0.0 [kN]
Stirrup failure : 0.000000 Infinity 0.00 345 454.5 0.00 345 454.5 [MPa]
𝑛𝑖
dMS = for the specific stress block for the different capacity
𝑁𝑖
checks; where ni is Number of cycles, ni, as input in
WAVED statement and Ni is the calculated value Ni as
explained below.
N = the number of uniform cycles which causes failure, Ni,
and included in formula above. Calculated based on MAX
and MIN values and with formulas in chosen design
code. See Section 4.1.5 for DNV design code and Section
4.2.5 for NS design code.
MAX = Maximum stress when looping through all specified
phase angles of the dynamic load. Phase angles specified
in DECAS statement.
PHA_MAX = Corresponding dynamic phase angle which causes the
maximum stress
CAP_MAX = Maximum capacity for the relevant check; max concrete
capacity, rebar capacity etc.
MIN = Minimum stress when looping through all specified phase
angles of the dynamic load. Phase angles specified in
DECAS statement.
PHA_MIN = Corresponding dynamic phase angle which causes the
minimum stress.
CAP_MIN = Minimum capacity for the relevant check; max concrete
capacity, rebar capacity etc.

7.1.4 DR table output for MCFT – ULS/ALS limit state
197
The sectional response from the MCFT calculations is somewhat different than for DNV, NS and
EC2 design, hence the MCFT DR table are explained below. The main differences in the
calculations between DNV/NS and EC2 and MCFT, is the inclusion of the transverse force in
the sectional response instead of calculating the shear capacity according to simplified
formulas.
Section data:
Detailed analysis response : TABLE TAB=GM

Shell Section : Part=VERIFY FS=1 HS=1 XC=0.000 YC=0.000 ZC=0.000
0.700 0.000 0.000 0.000 0.000
Load : ILC1 Limit State : ULS W-press. face 1,2 : 500. 500.

PHA = Phase angle if wave is present
Limit State = ULS, ALS
LE=load effect
TE = total effect
Forces&moments : N1 N2 N12 M1 M2 M12 V1 V2
LE 2500. 0. 0. 800. 0. 0. 500. 0.
WP 198. 0. 0. 12. 0. 0. 0. 0.
TE 2698. 0. 0. 812. 0. 0. 500. 0.

BAS) [kN/m].
forces are derived from haunches.
[kN/m].

3D sectional response - state of strain with reference to mid-section:
198
Note that the concrete tensile strength is included in the calculation of state of strain. FTC
parameter in CMPGM statement.
Response*1000 : eps1 eps2 gamma12 kappa1 kappa2 kappa12 gamma13 gamma23

TE 1.148 0.000 0.000 4.150 -0.000 0.000 1.567 -0.000

gamma13/gamma23 = Out of plane strain, γ13, γ23 – out of plane response.
Calculated in 3D sectional response.
Concrete stresses and utilizations:
Note that shear compression failure is also presented in these results as the shear forces is
included in the 3D sectional response.
Concrete average compressive stresses

case 3-coord alfa theta eps-c sig-c sig-cu URc
TE face 1 -0.350 -90.000 0.000 -0.000 -0.
TE -0.265 -0.000 50.101 -0.060 -1041. -20605. 0.051
TE face 2 0.350 -0.000 0.000 -0.305 -7605. -30000. 0.253
3-coord = distance from concrete centre to concrete result. 3 rows

with results presented, as the most utilized concrete layer
may occur between Face 1 and Face 2 due to shear.
Alfa = In-plane angle
theta = Out of plane angle
eps-c = principal strain εI and εII
sig-c = concrete stress based on principal strain εI and εII.
sig-cu = maximum allowable concrete stress.
Reinforcement stresses and utilizations:
Note that shear reinforcement is also presented in the same way as the normal reinforcement
as the shear reinforcement stresses are included in the 3D sectional response. Simplified
methods and empirical formulas are hence not used.
Rebar layers - average and crack stress
case id area 3-coord alfa eps-ave sig-ave sig-ftc sig-tau sig-tot sig-ru URr
TE X1 0.006032 -0.270 0.000 2.268 453686. 49116. 22828. 525630. 500000. 1.051 **
TE Y1 0.006032 -0.238 90.000 -0.000 -0. 0. 0. -0. 500000. -0.000
TE X2 0.006032 0.270 0.000 0.027 5445. 42785. 24473. 72702. 500000. 0.145
TE Y2 0.006032 0.238 90.000 0.000 0. 0. 0. 0. 500000. 0.000
Stirrup stress
case id area 3-coord alfa eps-ave sig-ave sig-ftc sig-tau sig-tot sig-ru URr
TE STA 0.001000 -0.070 - 1.115 223028. 819132. -568199. 473961. 500000. 0.948
id = reinforcement identity.
area = reinforcement cross section area [m2/m].

3-coor = distance from concrete center to rebar center. For
199
stirrup stresses, the most utilized layer is printed.
alfa = rebar angle with reference to 1. direction. Angle
measured counter-clockwise from 1-axis.
eps-ave = average strain in rebar based on sectional response with
concrete tensile strength.
sig-ave = average stress in rebar based on sectional response with
concrete tensile strength.
sig-ftc = additional stress due to crack check; increase due to
loss of tensile stresses in crack. In a crack, the loss of
tensile stresses in the concrete is carried by the
reinforcement crossing the crack and shear stresses on
the crack surface.
sig-tau = additional stress due to crack check; increase due to
effect of crack shear stress.
sig-tot = the total stresses (average + increase due to loss of
tensile stress + effect of crack shear stress)
sig-ru = maximum allowable reinforcement stress. Material
factors included.
URr = utilization ratio of reinforcement - sig-tot/sig-ru.

7.2 Design Section Force Tables – TAB=XX 200
7.2.1 TABLE TAB=DF – Section forces for design cases
[HOLD]
7.2.2 TABLE TAB=WF – Water pressure in cracks design forces for design cases
[HOLD]
7.2.3 TABLE TAB=PF – Maximum and minimum section forces for design cases
Prints 16 lines for each design section, where each line presents the BAS combination which
gives the maximum or minimum section forces.
TABLE TAB=PF : peak shell section design forces/moments for part : Platedam
Effect of water pressure in cracks (N,M) and/or haunches (V) included
FS HS THIC XC YC ZC LOAD-ID PHA LIM M N1 N2 N12 M1 M2 M12 V1 V2
4 1 0.765 0.270 -7.585 -9.553 BAS403 * ULS K -0. 178. -31. -37. -38. -18. -31. -26.
4 1 0.765 0.270 -7.585 -9.553 BAS411 * ULS L -21. 25. -24. -22. -27. -12. -10. -10.
4 1 0.765 0.270 -7.585 -9.553 BAS401 * ULS M -16. 267. -36. -44. -46. -21. -36. -26.
4 1 0.765 0.270 -7.585 -9.553 BAS411 * ULS N -21. 25. -24. -22. -27. -12. -10. -10.
4 1 0.765 0.270 -7.585 -9.553 BAS409 * ULS O -18. 38. -15. -16. -19. -9. -12. -11.
4 1 0.765 0.270 -7.585 -9.553 BAS401 * ULS P -16. 267. -36. -44. -46. -21. -36. -26.
4 1 0.765 0.270 -7.585 -9.553 BAS409 * ULS Q -18. 38. -15. -16. -19. -9. -12. -11.
4 1 0.765 0.270 -7.585 -9.553 BAS401 * ULS R -16. 267. -36. -44. -46. -21. -36. -26.
4 1 0.765 0.270 -7.585 -9.553 BAS409 * ULS S -18. 38. -15. -16. -19. -9. -12. -11.
4 1 0.765 0.270 -7.585 -9.553 BAS401 * ULS T -16. 267. -36. -44. -46. -21. -36. -26.
4 1 0.765 0.270 -7.585 -9.553 BAS409 * ULS U -18. 38. -15. -16. -19. -9. -12. -11.
4 1 0.765 0.270 -7.585 -9.553 BAS401 * ULS V -16. 267. -36. -44. -46. -21. -36. -26.
4 1 0.765 0.270 -7.585 -9.553 BAS410 * ULS W -19. 33. -18. -17. -22. -9. -9. -7.
4 1 0.765 0.270 -7.585 -9.553 BAS401 * ULS X -16. 267. -36. -44. -46. -21. -36. -26.
4 1 0.765 0.270 -7.585 -9.553 BAS410 * ULS Y -19. 33. -18. -17. -22. -9. -9. -7.
4 1 0.765 0.270 -7.585 -9.553 BAS402 * ULS Z -19. 220. -34. -40. -42. -19. -33. -26.
First line gives the maximum N1 and corresponding BAS, second line the minimum N1 and
corresponding BAS and so on:
M max/min N1 N2 N12 M1 M2 M12 V1 V2

component
K N1max -0. 178. -31. -37. -38. -18. -31. -26.
L N1min -21. 25. -24. -22. -27. -12. -10. -10.
M N2max -16. 267. -36. -44. -46. -21. -36. -26.
N N2min -21. 25. -24. -22. -27. -12. -10. -10.
O N12max -18. 38. -15. -16. -19. -9. -12. -11.
P N12min -16. 267. -36. -44. -46. -21. -36. -26.
Q M1max -18. 38. -15. -16. -19. -9. -12. -11.
R M1min -16. 267. -36. -44. -46. -21. -36. -26.
S M2max -18. 38. -15. -16. -19. -9. -12. -11.
T M2min -16. 267. -36. -44. -46. -21. -36. -26.
U M12max -18. 38. -15. -16. -19. -9. -12. -11.
V M12min -16. 267. -36. -44. -46. -21. -36. -26.
W V1max -19. 33. -18. -17. -22. -9. -9. -7.
X V1min -16. 267. -36. -44. -46. -21. -36. -26.
Y V2max -19. 33. -18. -17. -22. -9. -9. -7.
Z V2min -19. 220. -34. -40. -42. -19. -33. -26.
7.2.4 TABLE TAB=DP – Principial forces and moments for design cases
[HOLD]

7.3 Utilization Ratio Tables – UR=XX 201
For large runs where several design combinations for numerous design sections are considered,
it is recommended to only print “peak” tables, ordered with syntax UR=XX in the ShellDesign
statement TABLE. These tables print only the governing design case and corresponding
capacity with UR’s for relevant design sections.
7.3.1 TABLE UR=MAX – Summary of Max UR for all available capacities
This is the most recommended table when several design combinations are run. The table
prints the maximum UR’s found for all relevant capacities, such as concrete compression,
concrete shear, normal reinforcement, shear reinforcement and corresponding design section
and design combination. The table is however only available for ULS, ALS and SLS limit state.
For CRW and FLS, the other available UR= tables must be used.
Input:
TABLE UR=MAX
Additional input that gives more information:
TABLE UR=MAX FM= DR= BC= → The table will also include forces, DR tables etc.
Output:
TABLE UR=MAX for concrete and reinforcement
Structure part : PA=TS FS=1-43 HS=1-43
PART FS HS TAB IDs th/ar LOAD-ID LIM PHA UR
TS 14 1 MAX C1 500 BAS101 ULS * 1.00
TS 34 10 MAX C2 500 BAS101 ULS * 0.77
TS 1 8 MAX VC 500 BAS101 ULS * 1.00
TS 1 22 MAX CC 500 BAS101 ULS * 0.32
TS 42 17 MAX X2 4908 BAS101 ULS * 1.00
TS 22 1 MAX Y2 4908 BAS101 ULS * 1.28 **
TS 22 22 MAX X1 4908 BAS101 ULS * 0.45
TS 22 22 MAX Y1 4908 BAS101 ULS * 0.45
TS 22 1 MAX ST 8936 BAS101 ULS * 1.30 **
7.3.2 TABLE UR=CS – Summary of Max UR concrete capacity
Input:
TABLE UR=CS → Concrete face with maximum UR is printed
TABLE UR=CS FA=ALL → Both face 1 and face 2 are printed
TABLE UR=CS FA=ALL FM= → Sectional forces are included
TABLE UR=CS FA=ALL TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR face Concrete Stresses : TABLE UR=CS FA=ALL, eps=(mm/m)
PART FS HS FA THIC LOAD-ID PHA LIM angle eps-c sig-c sig-u URsig
TS 40 20 1 0.500 BAS101 * ULS -7.802 -0.776 -19556 -27300 0.72
TS 41 20 1 0.500 BAS101 * ULS -6.665 -0.980 -22255 -27300 0.82
TS 42 20 1 0.500 BAS101 * ULS -4.994 -1.653 -26777 -27300 0.98
TS 43 20 1 0.500 BAS101 * ULS -4.135 -2.590 -27300 -27300 1.00
TS 40 20 2 0.500 BAS101 * ULS 69.376 -0.105 -2741 -26439 0.10
TS 41 20 2 0.500 BAS101 * ULS 72.049 -0.084 -2092 -25344 0.08
TS 42 20 2 0.500 BAS101 * ULS 77.810 -0.062 -1315 -21349 0.06
TS 43 20 2 0.500 BAS101 * ULS 80.817 -0.062 -1063 -17237 0.06

7.3.3 TABLE UR=RS – Summary of Max UR reinforcement layer capacity
202
Input:
TABLE UR=RS → Reinforcement ID with maximum UR are printed
TABLE UR=RS RL=ALL → All reinforcement ID’s are printed
TABLE UR=RS RL=ALL FM= → Sectional forces are included
TABLE UR=RS RL=ALL TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR Rebar layer Stresses : TABLE UR=RS RL=ALL, area=(mm2/m), eps=(mm/m)
PART FS HS ID area LOAD-ID PHA LIM eps sig sig-u URsig
TS 40 20 X2 4908 BAS101 * ULS 1.649 329717 500000 0.66
TS 41 20 X2 4908 BAS101 * ULS 2.033 406603 500000 0.81
TS 42 20 X2 4908 BAS101 * ULS 3.733 500000 500000 1.00
TS 43 20 X2 4908 BAS101 * ULS 6.258 500000 500000 1.00
TS 40 20 Y2 4908 BAS101 * ULS 0.201 40231 500000 0.08
TS 41 20 Y2 4908 BAS101 * ULS 0.187 37335 500000 0.07
TS 42 20 Y2 4908 BAS101 * ULS 0.156 31200 500000 0.06
TS 43 20 Y2 4908 BAS101 * ULS 0.144 28822 500000 0.06
TS 40 20 Y1 4908 BAS101 * ULS 0.214 42843 500000 0.09
TS 41 20 Y1 4908 BAS101 * ULS 0.184 36750 500000 0.07
TS 42 20 Y1 4908 BAS101 * ULS 0.162 32408 500000 0.06
TS 43 20 Y1 4908 BAS101 * ULS 0.159 31870 500000 0.06
7.3.4 TABLE UR=RC – Summary of Min UR reinforcement layer capacity
Input:
TABLE UR=RC → Reinforcement ID with minimum UR are printed
TABLE UR=RC RL=ALL → All reinforcement ID’s are printed
TABLE UR=RC RL=ALL FM= → Sectional forces are included
TABLE UR=RC RL=ALL TV=1.0 → Only UR>= 1.0 are printed
Output:
minUR Rebar layer Stresses : TABLE UR=RC RL=ALL, area=(mm2/m), eps=(mm/m)
TS 40 20 X2 4908 BAS101 * ULS 1.649 329717 500000 0.66
TS 41 20 X2 4908 BAS101 * ULS 2.033 406603 500000 0.81
TS 42 20 X2 4908 BAS101 * ULS 3.733 500000 500000 1.00
TS 43 20 X2 4908 BAS101 * ULS 6.258 500000 500000 1.00
TS 40 20 Y2 4908 BAS101 * ULS 0.201 40231 500000 0.08
TS 41 20 Y2 4908 BAS101 * ULS 0.187 37335 500000 0.07
TS 42 20 Y2 4908 BAS101 * ULS 0.156 31200 500000 0.06
TS 43 20 Y2 4908 BAS101 * ULS 0.144 28822 500000 0.06
TS 40 20 X1 4908 BAS101 * ULS -0.382 -76332 500000 -0.15
TS 41 20 X1 4908 BAS101 * ULS -0.496 -99240 500000 -0.20
TS 42 20 X1 4908 BAS101 * ULS -0.801 -160173 500000 -0.32
TS 43 20 X1 4908 BAS101 * ULS -1.197 -239458 500000 -0.48
TS 40 20 Y1 4908 BAS101 * ULS 0.214 42843 500000 0.09
TS 41 20 Y1 4908 BAS101 * ULS 0.184 36750 500000 0.07
TS 42 20 Y1 4908 BAS101 * ULS 0.162 32408 500000 0.06
TS 43 20 Y1 4908 BAS101 * ULS 0.159 31870 500000 0.06

7.3.5 TABLE UR=CC – Summary of Max UR concrete capacity for shear compr.
203
Input:
TABLE UR=CC → Reinforcement ID with minimum UR are printed
TABLE UR=CC FM= → Sectional forces are included
TABLE UR=CC TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR Concrete shear Compression failure : TABLE UR=CC
PART FS HS LOAD-ID PHA LIM alfa Valfa Vcc UR
TS 40 20 BAS101 * ULS 2.445 750.362 3187.958 0.24
TS 41 20 BAS101 * ULS 2.599 815.476 3187.958 0.26
TS 42 20 BAS101 * ULS 0.917 898.280 3187.958 0.28
TS 43 20 BAS101 * ULS -0.147 927.238 3187.958 0.29
7.3.6 TABLE UR=VC – Summary of Max UR concrete capacity for shear tension
Input:
TABLE UR=VC → Reinforcement ID with minimum UR are printed
TABLE UR=VC FM= → Sectional forces are included
TABLE UR=VC TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR concrete shear tensile failure : TABLE UR=VC
PART FS HS LOAD-ID PHA LIM alfa Valfa Vcc UR
TS 40 20 BAS101 * ULS 2.445 750.362 362.939 1.00
TS 41 20 BAS101 * ULS 2.599 815.476 361.922 1.00
TS 42 20 BAS101 * ULS 0.917 898.280 0.000 1.00
TS 43 20 BAS101 * ULS -0.147 927.238 0.000 1.00
7.3.7 TABLE UR=ST – Summary of Max UR shear reinforcement capacity
Input:
TABLE UR=ST → Maximum UR are printed
TABLE UR=ST FM= → Sectional forces are included
TABLE UR=ST TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR stirrup stresses : TABLE UR=ST, area=(mm2/m2)
PART FS HS ID area LOAD-ID PHA LIM alfa Valfa Vcd Vsd UR
TS 1 6 ST 8936 BAS101 * ULS 0.000 172.841 341.740 0.000 0.00
TS 1 7 ST 8936 BAS101 * ULS 0.000 254.407 336.331 0.000 0.00
TS 1 8 ST 8936 BAS101 * ULS 0.000 332.049 335.446 0.000 0.00
TS 1 9 ST 8936 BAS101 * ULS 15.000 433.153 348.436 1739.169 0.05
TS 1 10 ST 8936 BAS101 * ULS 15.000 502.870 347.687 1739.169 0.09
TS 1 11 ST 8936 BAS101 * ULS 5.000 601.113 368.432 1739.169 0.13
TS 1 12 ST 8936 BAS101 * ULS 5.000 658.439 367.723 1739.169 0.17
TS 1 13 ST 8936 BAS101 * ULS 5.000 720.107 366.902 1739.169 0.20
TS 1 14 ST 8936 BAS101 * ULS 5.000 764.047 366.272 1739.169 0.23
TS 1 15 ST 8936 BAS101 * ULS 5.000 810.200 365.547 1739.169 0.26
TS 1 16 ST 8936 BAS101 * ULS 5.000 842.075 364.993 1739.169 0.27
TS 1 17 ST 8936 BAS101 * ULS 5.000 873.742 364.348 1739.169 0.29

7.3.8 TABLE UR=TS – Summary of Max UR prestressing reinforcement capacity
204
Input:
TABLE UR=TS → Tendon ID with minimum UR are printed
TABLE UR=TS TL=ALL → All tendon ID’s are printed
TABLE UR=TS TL=ALL FM= → Sectional forces are included
TABLE UR=TS TL=ALL TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR Tendon layer Stress : TABLE UR=TS TL=ALL, area=(mm2/m), eps=(mm/m)
TS 40 20 11 5971 BAS101 * ULS 5.145 872472 1451304 0.60
TS 41 20 11 5971 BAS101 * ULS 5.212 883764 1451304 0.61
TS 42 20 11 5971 BAS101 * ULS 5.635 955491 1451304 0.66
TS 43 20 11 5971 BAS101 * ULS 6.299 1068118 1451304 0.74
7.3.9 TABLE UR=CW – Summary of Max UR for reinforcement crack widths
Input:
TABLE UR=CW FA=ALL → Maximum UR are printed
TABLE UR=CW FA=ALL FM= → Sectional forces are included
TABLE UR=CW FA=ALL TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR face Crack Widths : TABLE UR=CW FA=ALL, eps=(mm/m), W=(mm) Wu=(mm)
PART FS HS FA THIC LOAD-ID PHA LIM crd Srk angle eps W Wu UR
TS 40 20 1 0.500 * * CRW 0.000 0.000 0.000 0.000 0.000 0.000 0.00
TS 41 20 1 0.500 * * CRW 0.000 0.000 0.000 0.000 0.000 0.000 0.00
TS 42 20 1 0.500 * * CRW 0.000 0.000 0.000 0.000 0.000 0.000 0.00
TS 43 20 1 0.500 * * CRW 0.000 0.000 0.000 0.000 0.000 0.000 0.00
TS 40 20 2 0.500 BAS100 * CRW 0.330 0.427 -9.798 0.826 0.328 0.300 1.09
TS 41 20 2 0.500 BAS100 * CRW 0.330 0.437 -7.004 1.039 0.431 0.300 1.44
TS 42 20 2 0.500 BAS100 * CRW 0.330 0.449 -3.922 1.377 0.598 0.300 1.99
TS 43 20 2 0.500 BAS100 * CRW 0.340 0.365 -2.915 1.512 0.536 0.300 1.79
7.3.10 TABLE UR=TW – Summary of Max UR for prestressing crack widths
Input:
TABLE UR=TW TL=ALL → Maximum UR are printed for all TL layers
TABLE UR=TW TL=ALL FM= → Sectional forces are included
TABLE UR=TL TL=ALL TV=1.0 → Only UR>= 1.0 are printed
Output:
maxUR Tendon crack Widths : TABLE UR=TW TL= 11 eps=(mm/m), Wu=(mm)

PART FS HS ID THIC LOAD-ID PHA LIM crd Srk eps W Wu UR
TS 1 6 11 0.500 BAS100 * CRW 0.250 0.349 0.105 0.200 0.027 0.14
TS 1 7 11 0.500 BAS100 * CRW 0.280 0.351 0.162 0.200 0.046 0.23
TS 1 8 11 0.500 BAS100 * CRW 0.290 0.352 0.205 0.200 0.060 0.30
TS 1 9 11 0.500 BAS100 * CRW 0.300 0.354 0.258 0.200 0.078 0.39
TS 1 10 11 0.500 BAS100 * CRW 0.310 0.357 0.291 0.200 0.091 0.45
TS 1 11 11 0.500 BAS100 * CRW 0.310 0.359 0.337 0.200 0.108 0.54
TS 1 12 11 0.500 BAS100 * CRW 0.310 0.362 0.364 0.200 0.119 0.59
TS 1 13 11 0.500 BAS100 * CRW 0.320 0.366 0.398 0.200 0.133 0.67
TS 1 14 11 0.500 BAS100 * CRW 0.320 0.369 0.418 0.200 0.143 0.71
TS 1 15 11 0.500 BAS100 * CRW 0.320 0.286 0.443 0.200 0.118 0.59
TS 1 16 11 0.500 BAS100 * CRW 0.310 0.289 0.457 0.200 0.124 0.62
TS 1 17 11 0.500 BAS100 * CRW 0.310 0.294 0.473 0.200 0.132 0.66
TS 1 18 11 0.500 BAS100 * CRW 0.310 0.298 0.481 0.200 0.137 0.68

7.3.11 TABLE UR=CZ – Compression Zone Check
205
This table reports the compression zone check according to the criteria defined in TIGHT
statement and method described in Section 4.1.4.4 for DNV-ST-C502 and Section 4.2.4.3 for
NS 3473.
Input:
TABLE UR=CZ
Output:
peak tightness UR based on compression zone thickness (not through cracks) :

TABLE UR=CZ (m)
PART FS HS FA THIC LOAD-ID PHA LIM CZ CZ-min UR
PART1 1 1 0 0.500 ILC1 * CRW 0.000 0.100 100.00 **
WALL 1 2 1 1.000 BAS102 * CRW 0.260 0.050 0.19
THIC = Thickness of the design section in question [m].

LOAD-ID = Load, either ILC, OLC, ELC or BAS number.
PHA = Phase angle if LOAD-ID is a dynamic load
CZ = Calculated Compression Zone [m]
CZ-min = Minimum allowed compression zone defined in TIGHT
statement
UR = Utilization Ratio = CZ-min/CZ.
the layer has compression or not. If both faces have εp>0, the compression zone is set to zero.
Note that the non-linear sectional response is calculated with the concrete tensile strength, fck.
in the DR table for CRW, as this crack depth is calculated based on the cracking criteria and
not tension/compression criteria.
UR>1.0 means that the compression zone limit is reached.

UR=100 means that there is no compression zone and you will have through cracks that may
be checked with UR=CT table.

7.3.12 TABLE UR=CT – Crack Width Check for Through Cracks
206
This table reports the crack width check for through cracks according to the criteria defined in
the TIGHT statement and the method described in Section 4.1.4.5 for DNV-ST-C502 and
Section 4.2.4.4. Through cracks means that the crack depth is equal to the section thickness.
Input:
TABLE UR=CT
Output:
Peak tightness UR based on crackwidths (through cracks) : TABLE UR=CT (W=mm)

(Wu=mm) UR=max(W1,W2)/Wu
PART FS HS THIC LOAD-ID PHA LIM W1 W2 Wu UR
PART1 1 1 0.500 ILC1 * CRW 0.124 0.000 0.200 0.62
WALL 1 2 1.000 * * CRW 0.000 0.000 0.200 0.00
THIC = Thickness of the design section in question [m].

LOAD-ID = Load, either ILC, OLC, ELC or BAS number.
PHA = Phase angle if LOAD-ID is a dynamic load
W1 = Calculated crack width at face 1 [mm]
W2 = Calculated crack width at face 2 [mm]
Wu = Maximum allowable crack width defined in TIGHT
statement
UR = Utilization Ratio = max of Wu/W1 and Wu/W2.
If there are through cracks, the W1 and W2 are calculated in the same way as in the DR table
for CRW, described in Section 7.1.2.
UR>1.0 means that the crack widths are above the maximum allowed crack width.
UR=0 means that there is a compression zone and there is no through cracks.
Note that questions can be raised if results show that there is no compression zone in addition
that there is no through cracks. This is the result of two different calculation methods for
compression zone height and crack depth. See section 4.1.4.4 4.1.4.5 for DNV design code
and 4.2.4.3 and 4.2.4.4 for NS design code.

8 RESULT DESCRIPTION IN GRAPHICAL 207
PLOTS
The results from ShellDesign can be presented in 3D graphics in DNV’s Xtract with a plot file
(“FN”.vtf) created with the XTFIL statement in the ShellDesign input file. This section gives a
description of the results available in plots. Three different “result cases” are printed to the
plot file for the design sections available in the plot file:
1. Properties
2. Design Case Result
3. Peak Results
Example of input statement in ShellDesign:
Input:
XTFIL FN=DESIGN-PLATEDAM-NS PA=Platedam
Output vtf file:
→ Properties, Design Case Result and Peak Results (if more than one design case is run)
are printed to plot file.
Input:
XTFIL FN=DESIGN-PLATEDAM-NS PA=Platedam PV=
Output vtf file:
→ PV= flags that only Properties and Peak Results are printed to the plot file. Recommended
when a huge number of design cases are run in DECAS statement, and it will be too time
consuming to create the plot file.
Note that it is recommended to switch to “Min-Max” in “Result Settings” in Xtract when

utilization ratios plots are shown to reflect the UR capacity scale.
Figure 8-1 Graphical Plots - Utilization Ratio scale

8.1 Properties 208
Figure 8-2 Graphical Plots - Properties
8.1.1 Areas
“Areas” show the intensities in mm2/m for all reinforcement ID’s defined with RELOC statement,
prestressing reinforcement ID’s defined with TELOC/TELAY statement and shear reinforcement
ID’s defined with SRLOC statement.
Figure 8-3 Graphical Plots - Properties - Areas

8.1.2 Labeled Results
209
[HOLD]
8.1.3 Thicknesses
[HOLD]
8.1.4 Model Info
[HOLD]
8.2 Design Case Result

Design Case Result shows separate results for the design combinations and limit states defined
in DECAS statement in ShellDesign input file.
Figure 8-4 Graphical Plots - Result Case – Design Case Result
8.2.1 Sectional Forces
[HOLD]
8.2.2 Principal Forces
[HOLD]

8.2.3 Principal Strains
210
[HOLD]
8.2.4 Utilization Ratios ULS, ALS and SLS limit state
[HOLD]
8.2.5 Utilization Ratios CRW limit state (crack widths and tightness)
The available results for CRW limit states are shown in Figure 8-5 below.
Figure 8-5 Graphical Plots - Design Case Results - Utilization Ratios - CRW limit state

8.2.5.1 CRW-F1
211
Shows crack width utilization ratio for reinforcement at face 1 calculated according to the
criteria defined in the CRWOS, CRWNS or CRWEC statement. Reflects the same results as in
TABLE UR=CW FA=1.
Figure 8-6 Graphical Plots - CRW-F1 Design Case Result
8.2.5.2 CRW-F2
Shows crack width utilization ratio for reinforcement at face 2 calculated according to the
criteria defined in the CRWOS, CRWNS or CRWEC statement. Reflects the same results as in
TABLE UR=CW FA=2.
Figure 8-7 Graphical Plots - CRW-F2 Design Case Result

8.2.5.3 CRW-TENDON-ID
212
Shows crack width utilization ratio for prestressing reinforcement ID according to the criteria
defined in the CRWOS, CRWNS or CRWEC statement. Reflects the same results as in TABLE
UR=TW TL=”ID”
Figure 8-8 Graphical Plots - CRW-TENDON-ID Design Case Result
8.2.5.4 CZ-COMPZONE-DEPTH
Shows compression zone depth calculated according to the criteria defined in the TIGHT
statement. Reflects the same results as in TABLE UR=CZ.
Figure 8-9 Graphical Plots - CZ-COMPZONE-DEPTH Design Case Result

8.2.5.5 CZ-UR
213
Shows compression zone utilization ratio (UR) calculated according to the criteria defined in
the TIGHT statement. Reflects the same results as in TABLE UR=CZ.
Figure 8-10 Graphical Plots - CZ-UR Design Case Result
8.2.5.6 CZ-FACE_CZ
Shows which concrete face that has the compression zone according to the criteria defined in
the TIGHT statement. Reflects the same results as in TABLE UR=CZ.
Figure 8-11 Graphical Plots - CZ-FACE_CZ Design Case Result

8.2.5.7 CT-FACE_CT
214
Shows which concrete face that has the highest crack width utilization ratio for through cracks.
Reflects the same results as in TABLE UR=CT. Blue area shows that there is no through cracks;
crack depth < thickness.
Figure 8-12 Graphical Plots - CT-FACE_CT Design Case Result
Note that results can show that there is no through cracks (crack depth < thickness) in design
sections with no compression zone. This is the result of two different calculation methods for
crack depth and compression zone depth. See description in section 4.1.4.4 and 4.1.4.5 for
DNV design code and 4.2.4.3 and 4.2.4.4 for NS design code. See example below:

8.2.5.8 CT-UR
215
Shows crack width utilization ratio for through cracks calculated according to the criteria
defined in the TIGHT statement. Reflects the same results as in TABLE UR=CT; reflecting
the worst UR from W1 and W2. Through cracks means that the crack depth is equal to the
section thickness. Blue area shows no through cracks.
Figure 8-13 Graphical Plots - CT-UR Design Case Result

8.3 Result Case – Peak Results 216
Figure 8-14 Graphical Plots - Result Case – Peak Results
8.3.1 Principal Forces
[HOLD]
8.3.2 Principal Strains
[HOLD]
8.3.3 Utilization Ratios
[HOLD]

9 EXAMPLES OF SHELLDESIGN RUNS AND 217
INPUT FILES
As described in Section 3, ShellDesign performs design calculations (code checks) based on
section geometry, section forces, amount of reinforcement and material properties where there
are three different methods to carry out design calculations:
1. Design based on User Input. See Section 3.1

2. Design based on the Conventional Design Method (CDM). See Section 3.2
3. Design based on the Consistent Stiffness Method (CSM). See Section 3.3
The methods will be shown in the following sections with examples of run cases with
corresponding input files. Note that for large concrete structures where the FE model is large
and there are many load cases, it is recommended to create an OLC-file prior to the execution
of the design calculations.
The provided documentation which is automatically included when the program is installed
according to Section 2.2, three folders with Shelldesign examples could be found, including all
input necessary to run the examples. The folders are typically found here: C:\Program
Files\DNV\ShellDesign V6.1-00\Doc, with the path modified depending on the version and
installation preferences.
9.1 Design based on User Input

ShellDesign will be executed based on user defined input only, such as shell section thickness
and section forces/moments. The design/code check will be based on user input only. The
following input statements define this run case method:
▪ DESEC : define shell section identity and geometry from user.

▪ INPLC : define shell section forces and moments from user.
▪ DECAS/DECFI : define design cases to be calculated and stored on design file
(DEC-file).
▪ possible combinations with DECAS:
− no DECFI : no DEC-file will be saved.
− DECFI NF= : a permanent DEC-file will be saved.
− DECFI OF= : an old DEC-file will be read.
− DECFI OF= OF= NF=: two old DEC-files will be merged to a new DEC file and saved.

218
Note that graphical plots cannot be created for this run case method since no geometry is
available from a FE analysis.
9.1.1 Example 1 – Common run – no DEC file saved
ShellDesign will be executed based on user defined input with the use of the DESEC and
INPLC statements.
% ************************************************************************
% INPUT FILE USER INPUT ONLY
% ************************************************************************
HEADL SHAFTS
HEADL VERIFICATION OF SHELLDESIGN
%************************************************************************
% USER DEFINED INPUT FOR DESIGN SECTIONS
DESEC PA=SHAFTA FS=5 HS=2 TH=0.45
%************************************************************************
% MATERIAL PROPERTIES
% Concrete properties
CMPNS ID=1 GR=B60 MFU=1.25 MFA=1.1
CMPNS PRI=
% Reinforcement properties
RMPNS ID=1 GR=500 MFU=1.15 MFA=1.0
RMPNS PRI=
% ************************************************************************
% REINFORCEMENT TYPE
RETYP ID=32202 MP=1 AR=8042.E-6 C2=0.070 TH=0.036 DI=0.032 NR=2 BC=0.75 % 2.0D32 c200
% ************************************************************************
% REINFORCEMENT LOCATION
% Outer face:
RELOC ID=X11 RT=32202 FA=1 AL=0
RELOC ID=Z12 RT=32202 FA=1 AL=90
% Inner face:
% ************************************************************************
% USER DEFINED INPUT FOR SHELL SECTION FORCES/MOMENTS
INPLC ID=1 N1=1000 N2=-210 M1=500 PA=SHAFTA
% ************************************************************************
% LOAD COMBINATION
BASCO ID=101 LF=1.2 ILC=1
% ************************************************************************
% DESIGN COMBINATION
DECAS LS=ALS BAS=101
% ************************************************************************
% TABLES
TABLE UR=MAX
TABLE TAB=DR

% ************************************************************************
% PARAMETERS 219
DEPAR D_SIG=100 N_LAY=20 D_COD=NS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************

9.1.2 Example 2 – Permanent DEC-file saved
220
INPLC statements. A DECFI statement is included where a permanent DEC-file is created
during the run and saved.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% CREATE DESIGN FILE
DECFI NF=SHAFTA.DEC NAME=Shaft_A VERS=1.0 DATE=8jan-94 RESP=kf
% ************************************************************************
% USER DEFINED INPUT FOR DESIGN SECTIONS
DESEC PA=SHAFTA FS=1-30 HS=1-5 TH=0.45
% ************************************************************************
CMPNS PRI=
RMPNS ID=1 GR=500 MFU=1.15 MFA=1.0
RMPNS PRI=
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face
% ************************************************************************
% USER DEFINED INPUT FOR SHELL SECTION FORCES/MOMENTS
INPLC ID=1 N1=1000 N2=-210 M1=500 PA=SHAFTA
% ************************************************************************
% LOAD COMBINATION
BASCO ID=101 LF=1.2 ILC=1
% ************************************************************************
% ************************************************************************
TABLE UR=MAX
TABLE TAB=DR
% ************************************************************************
% PARAMETERS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************

9.1.3 Example 3 – Two Old DEC-files merged into a new file
221
INPLC statements. A DECFI statement is included where two old DEC-files are merged into a
new file.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% CREATE DECFI data
DECFI OF=SHAFTA1.DEC OF=SHAFTA2.DEC MF=SHAFTA3.DEC NAME=Shaft_A VERS=1.0 DATE=8jan-94
% ************************************************************************
% RUN MODE, NO DESIGN CALCULATIONS
EXECD DM=
% ************************************************************************
9.2 Design based on the Conventional Design Method (CDM)

ShellDesign will be executed based on results generated from a FE analysis. The design/code
check will be based on the shell section thickness and section forces/moments fetched from
the FEM result file. The following files and input statements define the run case method:
▪ RFILE/ABAFI : attach FEM result file to the run (Rx.SIN/xx.ABA).

▪ SHSEC/OLCFI : define shell section identification and stored on OLC-file.
▪ possible combinations with SHSEC:
− no OLCFI : no OLC-file will be saved.
− OLCFI NF= : a permanent OLC-file will be saved.
− OLCFI OF= : an old OLC-file is used to retrieve data
− OLCFI OF= OF= NF=: two old OLC-files will be merged to a new permanent OLC-file.
▪ DECAS/DECFI : define design cases to be calculated and stored on (DEC-file).
▪ possible combinations if DECAS is present:
− DECFI OF= : old DEC-file to be read.
− DECFI OF= OF= NF=: two old DEC files merged to a new permanent DEC-file.
Three run cases for this method are illustrated below when either a R1.SIN file, OLC file or
DEC file is attached:

Note that plots are only available when a R1.SIN file or an OLC-file is attached.
222
9.2.1 Example 1 – no OLC-file and DEC-file saved
A SHSEC statement is included, but no OLCFI statement or DECFI statement. A scratch OLC-
file is created and a scratch DEC-file is created during the run and deleted afterwards.
% ************************************************************************
% INPUT FILE LINEAR ANALYSIS
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% ANALYSIS FILE
RFILE FNM=R1.SIN
% ************************************************************************
CMPNS ID=1 GR=B60 MFU=1.25 MFA=1.1 TSA=1.
CMPNS PRI=
RMPNS ID=1 GR=500 MFU=1.15 MFA=1.0 EPK=0.01 FTK=0.520E+06
RMPNS PRI=
% ************************************************************************
% SECTIONS
SHSEC PA=SHAFT SE=1001 EL=79 XF=0,-1,0 XH=0,0,1 FS=1-104 HS=2-57 ET=VS
SHAXE PA=SHAFT XP=0,0,0 XA=0,0,1 AL=-90
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face
% ************************************************************************
% LOAD COMBINATION
BASCO ID=101 LF=1.2 OLC=2
% ************************************************************************
% ************************************************************************
TABLE UR=MAX
TABLE UR=RS SK=A
TABLE UR=CS SK=A
TABLE TAB=DF HS=2
TABLE TAB=DR FS=48 HS=2
% ************************************************************************
% PLOT FILES
XTFIL FN=SHAFT-ALL-SHL PA=SHAFT
XTFIL FN=SHAFT-52-SHL PA=SHAFT FS=1-52
XTFIL FN=SHAFT-HS2 PA=SHAFT FS=1-104 HS=2
% ************************************************************************
% PARAMETERS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************

9.2.2 Example 2 – OLC-file created and saved
223
A SHSEC statement, OLCFI statement is included in the input-file where a permanent OLC-
file is created.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% ANALYSIS FILE
RFILE FNM=R1.SIN
% ************************************************************************
% SAVE OLCFI data
OLCFI NF=SHAFTA.OLC NAME=Shaft_A VERS=1.0 DATE=8jan-94 RESP=kf
% ************************************************************************
% SECTIONS
% ************************************************************************
% RUN MODE, NO DESIGN CALCULATIONS
EXECD DM=
% ************************************************************************
9.2.3 Example 3 – Old OLC-file called and no DEC-file saved
An old OLC-file is called (created in Section 9.2.2 above) in the input-file to retrieve data. No
DECFI statement is included; hence a scratch DEC-file is created during the run and deleted
afterwards.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% RETRIEVE OLD OLCFI data
OLCFI OF=SHAFTA.OLC
% ************************************************************************
CMPNS PRI=
RMPNS PRI=
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face
% ************************************************************************
% LOAD COMBINATION
% ************************************************************************

DECAS LS=ALS BAS=101 224
% ************************************************************************
TABLE UR=MAX
TABLE UR=RS SK=A
TABLE UR=CS SK=A
TABLE TAB=DF HS=2
% ************************************************************************
% PLOT FILES
% ************************************************************************
% PARAMETERS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************
9.2.4 Example 4 – Old OLC-file called and DEC-file saved
An old OLC-file is called in the input-file to retrieve data and a new DEC-file is created, hence
a permanent DEC-file is saved.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% RETRIEVE OLD OLCFI DATA AND CREATE NEW DEC-FILE
OLCFI OF=SHAFTA.OLC
% ************************************************************************
CMPNS PRI=
RMPNS PRI=
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face
% ************************************************************************
% LOAD COMBINATION
% ************************************************************************
% ************************************************************************
TABLE UR=MAX

TABLE UR=RS SK=A
TABLE UR=CS SK=A 225
TABLE TAB=DF HS=2
% ************************************************************************
% PLOT FILES
% ************************************************************************
% PARAMETERS
% ************************************************************************
% RUN MODE
% Run mode for verification of fixed reinforcement
EXECD DM=V
% ************************************************************************
9.2.5 Example 5 – OLC-file and DEC-file saved
A SHSEC statement, OLCFI statement and a DECFI statement is included in the input-file
where a permanent OLC-file and DEC-file is created.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% ANALYSIS FILE
RFILE FNM=R1.SIN
% ************************************************************************
% SAVE OLCFI and DECFI data
OLCFI NF=SHAFTA.OLC NAME=Shaft_A VERS=1.0 DATE=8jan-94 RESP=kf
% ************************************************************************
CMPNS PRI=
RMPNS PRI=
% ************************************************************************
% SECTIONS
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face
% ************************************************************************
% LOAD COMBINATION
% ************************************************************************

DECAS LS=ALS BAS=101 226
% ************************************************************************
TABLE UR=MAX
TABLE UR=RS SK=A
TABLE UR=CS SK=A
TABLE TAB=DF HS=2
% ************************************************************************
% PLOT FILES
% ************************************************************************
% PARAMETERS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************
9.2.6 Example 6 – Old OLC-file and DEC-file used to retrieve data
No SHSEC statement is included, but an old OLC-file and DEC-file is called with the OLCFI
statement and DECFI statement in the input-file, hence an old OLC-file and DEC-file is used
to retrieve data.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% ANALYSIS FILE
RFILE FNM=R1.SIN
% ************************************************************************
% RETRIEVE OLCFI and DECFI data
OLCFI OF=SHAFTA.OLC
DECFI OF=SHAFTA.DEC
% ************************************************************************
CMPNS PRI=
RMPNS PRI=
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face
% ************************************************************************
TABLE UR=MAX
TABLE UR=RS SK=A

TABLE UR=CS SK=A
TABLE TAB=DF HS=2 227
% ************************************************************************
% PLOT FILES
% ************************************************************************
% PARAMETERS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************
9.2.7 Example 7 – Old DEC-file used to retrieve data
ShellDesign will be executed based on an old DEC-file.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% RETRIEVE DECFI data
DECFI OF=SHAFTA.DEC
% ************************************************************************
TABLE UR=MAX
TABLE UR=RS SK=A
TABLE UR=CS SK=A
TABLE TAB=DF HS=2
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************
9.2.8 Example 8 – Two old DEC-files merged
ShellDesign will be executed based on two DEC-files that will be merged.
% ************************************************************************
% ************************************************************************
HEADL SHAFTS
% ************************************************************************
% RETRIEVE DECFI data
DECFI OF=SHAFTA1.DEC OF=SHAFTA2.DEC MF=SHAFTA3.DEC VERS=4.0 DATE=8jan-94 RESP=kf
% ************************************************************************
TABLE UR=MAX
TABLE UR=RS SK=A
TABLE UR=CS SK=A
TABLE TAB=DF HS=2
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************

9.3 Design based on the Consistent Stiffness Method (CSM) 228
The design is based on results from CSM, a non-linear analysis performed with ShellDesign.
ShellDesign will be executed in interaction with SESTRA/OOsolver based on a FEM-file and a
SIN-file generated from the linear analysis. The design/code check will then be based on the
results on the SIN-file after the non-linear run. The following files and input statements define
the run case:
▪ RFILE : attach Rx.SIN file to the run.

▪ NONLI : define non-linear analysis data and attach Tx.FEM file to the run.
▪ SHSEC/OLCFI : define shell section identification and stored on OLC-file. (OLC-file will
only contain results from the last load case.)
▪ Possible combinations with SHSEC:
− no OLCFI : no OLC-file will be saved.
− OLCFI NF= : a permanent OLC-file will be saved.
− OLCFI OF= OF= NF= : two old OLC-files will be merged to a permanent OLC-file.
▪ DECAS/DECFI : define design cases to be calculated and stored on design file.
▪ Possible combinations with DECAS:
− DECFI OF= OF= NF= : two old DEC-files will be merged to a permanent DEC-file.
Note that Rx.SIN and Tx.FEM will be changed during the run. The OLC-file will only contain
results from the last load case run. The run case is illustrated below:
OOSolver

9.3.1 Example 1 – Common run - No OLC-File and DEC-File Created
229
A SHSEC statement is included, but no OLCFI statement or DECFI statement. A scratch OLC-
file and DEC-file is created during the run and deleted afterwards.
% ************************************************************************
% INPUT FILE NON-LINEAR ANALYSIS
% ************************************************************************
% HEADING
% ************************************************************************
HEADL Verification case cylinder
HEADL SHAFTS
% ************************************************************************
% ANALYSIS FILE
RFILE TFI=T1.FEM FNM=R1.FEM
% ************************************************************************
% MATERIAL PROPERTIES in DESIGN
CMPNS PRI=
RMPNS ID=1 GR=500 MFU=1.15 MFA=1.0 EPU=0.010
RMPNS PRI=
% ************************************************************************
% MATERIAL PROPERTIES in ANALYSIS
CMPNL CCC= FTA=2000 ECM=0.270E08
CMPNL PRI=TAB
RMPNL ID=1 ESK=0.200E09 FSY=500.E3 FSU=500.E3 EPU=0.010
RMPNL PRI=
% ************************************************************************
% SECTIONS
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face
% ************************************************************************
% LOAD COMBINATION
% ************************************************************************
% ************************************************************************
% TABLES
TABLE UR=MAX
TABLE UR=RS SK=A
TABLE UR=CS SK=A
TABLE TAB=DF HS=2
% ************************************************************************
% PLOT FILES

XTFIL FN=SHAFT-HS29 PA=SHAFT FS=1-104 HS=29 230
% ************************************************************************
% PARAMETERS
DEPAR D_SIG=100 N_LAY=20 D_COD=NS A_COD=NS
% ************************************************************************
% CSM ANALYSIS
NONLI NSR=10 NDT=0 FEA=OOS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************
9.3.2 Example 2 – OLC-file and DEC-file saved
A SHSEC statement, an OLCFI statement and DECFI statement is included in the input-file,
where a permanent OLC-file and DEC-file is created.
% ************************************************************************
% INPUT FILE NON-LINEAR ANALYSIS
% ************************************************************************
% HEADING
% ************************************************************************
HEADL Verification case cylinder
HEADL SHAFTS
% ************************************************************************
% ANALYSIS FILE
RFILE TFI=T1.FEM FNM=R1.SIN
% ************************************************************************
% SAVE OLCFI and DECFI data
OLCFI NF=SHAFTA2.OLC NAME=Shaft_A VERS=1.0 DATE=8jan-94 RESP=kf
DECFI NF=SHAFTA2.DEC NAME=Shaft_A VERS=1.0 DATE=8jan-94 RESP=kf
% ************************************************************************
% MATERIAL PROPERTIES in DESIGN
CMPNS PRI=
RMPNS ID=1 GR=500 MFU=1.15 MFA=1.0 EPU=0.010
RMPNS PRI=
% ************************************************************************
% MATERIAL PROPERTIES in ANALYSIS
CMPNL CCC= FTA=2000 ECM=0.270E08
CMPNL PRI=TAB
RMPNL ID=1 ESK=0.200E09 FSY=500.E3 FSU=500.E3 EPU=0.010
RMPNL PRI=
% ************************************************************************
% SECTIONS
% ************************************************************************
% ************************************************************************
% Outer face:
% Inner face

% ************************************************************************ 231
% LOAD COMBINATION
% ************************************************************************
DECAS LS=ALS BAS=101-104
% ************************************************************************
% TABLES
TABLE UR=MAX
TABLE UR=RS SK=A
TABLE UR=CS SK=A
TABLE TAB=DF HS=2
% ************************************************************************
% PLOT FILES
% ************************************************************************
% PARAMETERS
DEPAR D_SIG=100 N_LAY=20 D_COD=NS A_COD=NS
% ************************************************************************
% NON-LINEAR ANALYSIS
NONLI NSR=10 NDT=0 FEA=OOS
% ************************************************************************
% RUN MODE
EXECD DM=V
% ************************************************************************

10 REFERENCES 232
[1] Dr.techn. Olav Olsen AS, “ShellDesign Theory Manual, rev. 1.1,” 2021.
[2] Det Norske Veritas (DNV), “DNV-ST-C502 Offshore Concrete Structures,” 2018,
amended 2021.
[3] Norwegian Technology Standards Instituion, “NS 3473.E Concrete structures - Design
and detailing rules 6th edition,” 2004.
[4] Norwegian Technology Standards Instituion, “NS-EN 1992-1-1:2004+NA:2008: Design
of Concrete Structures - General Rules and Rules for Buildings,” December 2004.
[5] Vecchio, F. J., Collins, M. P., “The modified compression field theory for reinforced
concrete elements subjected to shear,” ACI Journal, Vol. 83, No. 2, March-April, pp. 219-
231, 1986.
[6] DNV GL SESAM, “https://www.dnvgl.com/services/linear-structural-analysis-sestra-
2276”.
[7] A. d. B. a. B. B. M. Hendricks, Report RTD:1016-1:2017 Guidelines for Nonlinear Finite
Element Analysis of Concrete Structures," Rijkswaterstaat Centre for Infrastructure,
2017.
[8] “Eurocode 2: Design of concrete structures - Concrete bridges - Design and detailing
rules - NS-EN 1992-2:2005”.
[9] F. J. V. o. M. P. Collins, “The Modified Compression-Field Theory for Reinforced Concrete
Elements Subjected to Shear,” ACI, 1986.
[10] E. C. Bentz, “Sectional Analysis of Reinforced Concrete Members,” University of Toronto,
2000.
[11] F. J. Vecchio and R. G. Selby, “Toward Compression-Field Analysis of Reinforced
Concrete Solids,” Jornal of Structural Engineering, vol. 117, no. 6, pp. 1740-1758, 1991.
[12] P. Adebar and M. P. Collins, “Shear Design of Concrete Offshore Structures,” ACI
Structural Journal, vol. 91, no. S32, pp. 324-335, 1994.
[13] F. J. Vecchio and M. P. Collins, “Predicting the Response of Reinforced Concrete Beams
Subjected to Shear Using Modified Compression Field Theory,” ACI Structural Journal,
vol. 85, no. S27, pp. 258-268, 1988.
[14] M. P. Collins, “The Use of Rational Design Methods for Shear,” ACI Special Publication,
vol. 157, pp. 351-377, 1995.
[15] M. P. Collins, D. Mitchell, P. Adebar and F. J. Vecchio, “A General Shear Design Method,”
ACI Structural Journal, vol. 93, no. S5, pp. 36-45, 1996.
[16] P. Adebar and M. P. Collins, “Shear Strength of Members Without Stirrups,” Canadian
Journal of Civil Engineering, vol. 23, no. 1, pp. 30-41, 1996.
[17] E. C. Bentz, F. J. Vecchio and M. P. Collins, “Simplified Modified Compression Field Theory
for Calculating Shear Strength of Reinforced Concrete Elements,” ACI Structural Journal,
vol. 103, no. S65, pp. 614-624, 2006.

APPENDIX A 233
«SHELLDESIGN_usrlan.xml»:
<?xml version="1.0" encoding="Windows-1252" ?>
<NotepadPlus>
<UserLang name="SHELLDESIGN" ext="inp" udlVersion="2.1">
<Settings>
<Global caseIgnored="yes" allowFoldOfComments="yes"
foldCompact="no" forcePureLC="0" decimalSeparator="0" />
<Prefix Keywords1="yes" Keywords2="yes" Keywords3="yes"
Keywords4="no" Keywords5="no" Keywords6="no" Keywords7="no" Keywords8="no" />
</Settings>
<KeywordLists>
<Keywords name="Comments">00% 01 02 03 04</Keywords>
<Keywords name="Keywords1">
BASCO
BESEC
BRFOR
BRSEC
CHSEC
CMPNS
CMPNS
CRWNS
DECAS
DECFI
DEPAR
DESEC
EXECD
FAPAR
FATIG
FILST
FVFIL
GRECO
HEADL
INCDF
INPLC
LAREA
LDFAC
LOADC
LORES
NONLI
OLCFI
PLFIL
RELOC
RERES
RETYP
RFILE
RMPEC
RMPNS
SHAXE
SHEXT

SHSEC
234
SINST
SRLOC
SRRES
SRTYP
TABLE
TELOC
TEMAT
TETYP
TIGHT
WAVED
WPARE
XTFIL
</Keywords>
AL
AR
A_CPR
B1
B2
B3
BA
BAS
BC
BDF
BDI
BS
BTS
C1
C2
CCF
CO
CS
CSA
CSD
CW
DATE
DFA
DI
DIST
DM
DR
DWP
D_CPR
D_SIG
E0
EC
ECK
ECN
EFS
EHS
EL
ELC

EMP
235
EPK
EPO
EPP
EPS
EPU
ESK
ET
EX
FA
FACE
FACT
FCN
FM
FN
FNM
FS
FSK
FSY
FTA
FTK
FTN
FVF
FWF
GR
HS
ILC
KS
KT
LA
LB
LC
LDF
LF
LS
M1
M12
M2
MFA
MFS
MFU
MP
N1
N12
N2
NAME
ND
NE
NF
NR
NS
NSR
N_ITE

N_LAY
236
Nos
OF
OLC
OS
PA
PHA
PI
PLC
PRE
PRI
RA
RE
RESP
RET
RL
RN
RT
SE
SH
SK
SPA
SSF
ST
SUF
SY
T11
T12
T21
T22
TAB
TB
TF
TFI
TH
TIME
TL
TSA
TSD
TSF
TT
TV
TYP
T_TOL
UL
UR
URT
V1
V2
VER
VERS
W0
WD

WP
237
X1
X2
X3
XA
XC
XF
XH
XP
XS
Z_TOL
axis
c2
lim
wd
wp
x1
x2
z
z0
</Keywords>
id
ID
</Keywords>
<Keywords name="Operators">
=
</Keywords>
</KeywordLists>
<Styles>
<WordsStyle name="LINE COMMENTS" fgColor="808080"
bgColor="FFFFFF" fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="KEYWORDS1" fgColor="FF0000" bgColor="FFFFFF"
fontName="" fontStyle="0" nesting="0" />
<WordsStyle name="KEYWORDS2" fgColor="0000FF"
<WordsStyle name="KEYWORDS3" fgColor="00FF00"
<WordsStyle name="Operators" fgColor="808080" bgColor="FFFFFF"
fontName="" fontStyle="0" nesting="0" />
</Styles>
</UserLang>
</NotepadPlus>

Shelldesign_UM

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Shelldesign_UM

Uploaded by

Copyright:

Available Formats

ShellDesign

DESIGN TOOL FOR REINFORCED

USER MANUAL - revision 7.0

No liability for consequential damages:

Prepared by: Dr.techn. Olav Olsen

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 2 of 237

2 SETUP FOR SHELLDESIGN EXECUTION ............................ 14

3 ANALYSIS AND DESIGN INTERACTION ............................ 20

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 3 of 237

4 DESIGN CODES AND DESIGN CALCULATIONS .................. 39

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 4 of 237

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 5 of 237

6 DESCRIPTION OF INPUT STATEMENTS........................... 108

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 6 of 237

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 7 of 237

7 RESULT DESCRIPTION IN TABLES ................................. 187

8 RESULT DESCRIPTION IN GRAPHICAL PLOTS ................. 207

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 8 of 237

9 EXAMPLES OF SHELLDESIGN RUNS AND INPUT FILES ..... 217

10 REFERENCES .............................................................. 232

APPENDIX A .......................................................................... 233

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 9 of 237

Figure 2-1: Execution of ShellDesign in Sesam Manager ................................................................. 16

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 10 of 237

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 11 of 237

1.1 Program summary

The implemented design codes are:

- DNV-ST-C502 Offshore Concrete Structures [2]. See Section 4.1

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 12 of 237

Main ShellDesign tasks are in general:

Additional results such as beam section forces are also available.

1.2 Program limitations

1.3 License and Support

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 13 of 237

2.1 Input files

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 14 of 237

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 15 of 237

Figure 2-1: Execution of ShellDesign in Sesam Manager

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 16 of 237

2.3.1 Syntax highlighting

A.2 Install and run Notepad++.

A.3 From the «Language» menu, choose «Define your language…».

Figure 2-3: Notepad++ «Define your language...» dialog

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 17 of 237

Figure 2-4: Notepad++ «Language» menu w/ShellDesign option

A.6 ShellDesign syntax highlighting should now be enabled. «SHELLDESIGN_usrlan.xml» is

2.3.2 Input statement suggestions and auto complete

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 18 of 237

The Sestra Print File will appear as .LIS.

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 19 of 237

1. Design based on User Input. See Section 3.1

Figure 3-1: Required input to design calculations in ShellDesign

The implemented design codes are:

• DNV-ST-C502 Offshore Concrete Structures [2]

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 20 of 237

Figure 3-2: User Input design - Design flow

3.2 Design based on the Conventional Design Method (CDM)

3.2.1 CDM - Method

ShellDesign reads FE results from:

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 21 of 237

FEM OLC File

Results in Plot File Results in

SHELLDESIGN USER MANUAL VERSION 7.0 – PAGE 22 of 237

Quasi static and time domain analysis