sofistik help.pdf

SOFiMSHCGeometric Modelling

Version 12.01

� SOFiSTiK AG, Oberschleissheim, 2011

SOFiMSHC Geometric Modelling

This manual is protected by copyright laws. No part of it may be translated,copied or reproduced, in any form or by any means, without written permissionfrom SOFiSTiK AG. SOFiSTiK reserves the right to modify or to release neweditions of this manual. The manual and the program have been thoroughly checked for errors.However, SOFiSTiK does not claim that either one is completely error free.Errors and omissions are corrected as soon as they are detected.The user of the program is solely responsible for the applications. We stronglyencourage the user to test the correctness of all calculations at least by randomsampling.

Geometric Modelling SOFiMSHC

i

1 General. 1−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Theoretical background 2−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.1. Coordinate systems 2−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2. Curves and alignment axes 2−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2.1. Alignment axes 2−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2.2. Freeform curves 2−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.3. Regions and geometric surfaces 2−5. . . . . . . . . . . . . . . . . . . . . . . . . .2.3.1. Rotational and sweep surfaces 2−6. . . . . . . . . . . . . . . . . . . . . . . . .2.4. Structural elements 2−6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.5. Mesh generation 2−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.6. Literature 2−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.7. Limitations 2−8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 General program control 3−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.1. Input language 3−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.2. Units 3−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.3. Remarks for the conversion from SOFiMSHB 3−1. . . . . . . . . . . . . . .3.4. Input records 3−2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.5. SYST − Global system definition 3−4. . . . . . . . . . . . . . . . . . . . . . . . . .3.6. CTRL − Control of analysis 3−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.6.1. Analysis and generation of structural model 3−8. . . . . . . . . . . . . . .3.6.2. Geometry healing 3−10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.6.3. Meshing control 3−11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.6.4. Element generation and boundary conditions 3−12. . . . . . . . . . . . .3.6.5. Mesh decomposition and band−width optimization 3−13. . . . . . . . .3.6.6. Warnings and error messages 3−14. . . . . . . . . . . . . . . . . . . . . . . . . .3.7. GRP − Group control 3−15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.7.1. Primary group number 3−15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.7.2. Secondary groups 3−16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.8. IMPO − Import of data 3−18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.9. EXPO − ANSI export of data 3−19. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.10. ECHO − Control of output 3−20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3.11. COOR − User defined coordinate system 3−21. . . . . . . . . . . . . . . . . .3.12. XSUB − Extraction of subsystems 3−24. . . . . . . . . . . . . . . . . . . . . . . .

4 Definition of geometric elements. 4−1. . . . . . . . . . . . . . . . . . . . . . .4.1. Input records 4−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.2. GAX − Geometric curve or axis 4−2. . . . . . . . . . . . . . . . . . . . . . . . . . .4.3. GAXA − Axis plan view 4−4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


ii

4.4. GAXH − Axis heights 4−7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.5. GAXB − Straights and circular arcs in 3D 4−8. . . . . . . . . . . . . . . . . .4.6. GAXC − 3D curve point data 4−10. . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.7. GAXN − Knot value of a NURBS−curve 4−12. . . . . . . . . . . . . . . . . . . .4.8. GAXP − Axis placements 4−13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.9. GAXS − Secondary axis 4−16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.10. GAXV − Variables along axis 4−17. . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.11. GAR − Geometric surface 4−19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.12. GARA − Plane, rotational and sweep surfaces 4−20. . . . . . . . . . . . . .4.13. GARC − Coons surface 4−22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4.14. GARS − Area by points 4−23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Definition of structural elements. 5−1. . . . . . . . . . . . . . . . . . . . . . .5.1. Input Records 5−1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.2. SPT − Structural point 5−3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.3. SPTP − Structural point properties 5−7. . . . . . . . . . . . . . . . . . . . . . . .5.4. SPTS − Spring element at point 5−14. . . . . . . . . . . . . . . . . . . . . . . . . .5.5. SPTH − Halfspace pile at point 5−18. . . . . . . . . . . . . . . . . . . . . . . . . . .5.6. SLN − Structural line 5−19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.7. SLNB − Straights and circular arcs 5−24. . . . . . . . . . . . . . . . . . . . . . . .5.8. SLNP − 3D curve point data 5−25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.9. SLNN − Knot value of a NURBS−curve 5−27. . . . . . . . . . . . . . . . . . . .5.10. SLNS − Supports and kinematic couplings on a SLN 5−28. . . . . . . .5.10.1. Supports and coupling conditions 5−29. . . . . . . . . . . . . . . . . . . . . . .5.10.2. Elastic beddings and spring elements 5−30. . . . . . . . . . . . . . . . . . . .5.10.3. Interface−elements 5−32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.11. SAR − Structural area 5−33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.12. SARB − Structural area boundaries and constraints 5−38. . . . . . . . .5.13. SARR − Rotational and sweep surfaces 5−40. . . . . . . . . . . . . . . . . . .5.14. SARP − 3D Surface data point 5−42. . . . . . . . . . . . . . . . . . . . . . . . . . .5.15. SARN − Knot value of a NURBS surface 5−44. . . . . . . . . . . . . . . . . . .5.16. SARC − Coons−Patch surfaces 5−45. . . . . . . . . . . . . . . . . . . . . . . . . .5.17. SVO − Structural volume 5−46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5.18. SVOS − Structrual volume faces 5−47. . . . . . . . . . . . . . . . . . . . . . . . . .5.19. GUID − Globally Unique Identifier 5−49. . . . . . . . . . . . . . . . . . . . . . . . .5.20. BBOX − Bounding box 5−50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


1−1Version 12.01

1 General.

SOFiMSHC is a tool for creating and processing geometric models and finite ele-ment structures. SOFiMSHC can be used as stand−alone program within Teddyand is integrated as geometry processing module in the SOFiSTiK programsSOFiPLUS, Extensions for Revit and Rhinoceros Interface.Basis and starting point of SOFiMSHC is an abstract structural model similar toa CAD model which includes all relevant geometric and structural information ne-cessary for describing a calculation model. After this model is read from databaseor entered by the user via CADINP, SOFiMSHC analyzes and processes it andcreates as result a finite element mesh consisting of beam, area and/or volumeelements. In addition to classical building structures, SOFiMSHC also providesa rich set of input facilities for the definition of alignment axes and bridge systems.

SOFiMSHC basically differentiates between geometric entities carrying geo-metry related data and structural elements containing all further informationneeded for definining a calculation model. As for the geometric entities followingtypes are supported:

Geometric axes:− straight lines− circles and circular arcs in space− alignment axes for road design defined separately in

plan view and elevation− polygonal lines− cubically interpolating splines− Hermite interpolation with defined tangents− arbitrary NURBS curves (Non Uniform Rational B−Splines)

Geometric surfaces:− flat surfaces− surfaces of revolution− sweep surfaces− bicubically interpolating surfaces− arbitrary NURBS surfaces

The basic geometric elements are usually defined independently from the overallstructural model and should be used in as comprehensive units as possible. Abridge with multiple spans, for example, can be defined with one single axis alongits whole length. The individual spans and all additional superstructures,


Version 12.011−2

however, are modeled with structural elements which inherit their geometry fromthe underlying axis definition. Once the geometry is changed the structural sys-tem will be automatically readjusted.

The static system itself with all mutual topological relationships comprises the fol-lowing set of basic structural elements:

Structural Points are defined at a specific position in space and may haveColumn Heads, Punching periphery and haunches assigned as structuralproperties.

Structural Lines connect two structural points and may have a geometriccurve assigned. Structural data includes supports and section definitions,for example.

Structural Regions are defined by a closed set of inner and outer bound-ary curves and may also have a geometric surface description assigned.Structural properties contain thickness, element formulation etc.

Structural Volumes are defined by a set of enclosing structural regionsand can be meshed either unstructured with tetrahedral elements or struc-tured by extrusion or rotation with hexahedral elements.

A number of possibilities are provided within the SOFiSTiK program environment,to access and define the input of SOFiMSHC:

• Definition using CADINP−ASCII−Files (Teddy + SOFiMSHC)

• Input of structural systems using SOFiPLUS (AutoCAD)

• Transfer of models from Autodesk Revit Structural (SOFiSTiK Extensionsfor Revit)

• Modeling in McNeel Rhinoceros (SOFiSTiK Rhinoceros Interface)

• Interface to the CDBASE for third party developers and for the import ofbuilding information models (e.g. IFC).

SOFiMSHC is both used as stand−alone batch program and as backend modulein the above mentioned CAD−programs. It contains interfaces to mesh−generat-ors from the University of Munich (DOMESH) and the University of Linz (NET-GEN) and to mesh−partitioning software (METIS).


1−3Version 12.01

This page intentionally left blank


2−1Version 12.01

2 Theoretical background

2.1. Coordinate systems

Global as well as local coordinate systems are described in SOFiMSHC as carte-sian right−handed system X−Y−Z. Rotations are applied in a mathematical posi-tive sense. Within record SYST a global gravity direction can be specified atparameter GDIR. This global gravity or ’downward’ direction affects the defaultorientation of loads, supports and other geometric attributes of structural itemswithin the model if not specified differently at the respective location.

Z

Y

XPhi

If the observer is looking from the birds eye view he will believe to see a right orleft handed 2D coordinate system depending on the orientation of the verticalaxis . We use the designation of the “first” and the “second” horizontal axis in thecounter clock wise orientation.

Each geometric or structural object in SOFiMSHC possesses a local orientationor a local coordinate system, which affects the direction of loads, cross−sectionsor support conditions:

• Points, for example, have a local coordinate system which defines primar-ily the local direction of supports and kinematic couplings. If no coordinatesystem is given explicitly the local z−direction defaults to the globally de-fined gravity direction or, if the point lies within a region or on a structuralline, to the local coordinate system defined there.

• For structural lines, up to three different local coordinate systems can beidentified. A first coordinate system is related to the underlying geometriccurve and is primarily used to define the orientation of circular arcs oralignment axes. On the structural line, an independant coordinate systemcan be defined which sets the orientation of cross−sections and beamelements. A third coordinate system may be specified in order to set thelocal direction of supports, springs or kinematic couplings connected to a


Version 12.012−2

line. If one of the three mentioned directions is not explicitly set by the user,it defaults to the previously defined system. If no coordinate system is de-fined at all, the global gravity direction is used.The local coordinate system of a structural line is normally specified by theuser by setting the direction of the local z−axis. As the local x−axis alwayspoints into the direction of the curve tangent, the local y−axis is definedautomatically.

• Geometric surfaces and structural regions have a local coordinate systemassigned which normally varies within the surface for curved shapes. Thez−axis of the coordinate system always remains perpendicular on thesurface. The coordinate system of a structural region defines, for example,the clock−order of outer boundary edges and the local orientation of thequadrilateral finite elements created on the surface.

• For volumes there might be a direction of orthotopic material properties,but there is no local coordinate system. However all surfaces describingthe volume will have a unique interior and exterior side. Thus a separatingsurface between two volumes will have a different orientation for the twocases.

2.2. Curves and alignment axes

Curves in SOFiMSHC are defined as parameter curves in three dimensionalspace. Parameter curves are basically defined by a local parameter s which runsalong the curve from its start to its endpoint. A ’curve function’ c(s) maps this localparameter s to global xyz−coordinates and therefore describes the curve in spacewhen s is changed from smin to smax:

s� c�(s)��

�

�

x(s)y(s)z(s)

��

�s� [smin,smax], (1)

Apart from its shape other parameters might also be specified along a given curveas a function of s, like for example the orientation, the size or the shape of varyingcross−sections. SOFiMSHC also allows to define so−called secondary lines,which are connected to a basis curve and whose distance is defined as a functionof s.


2−3Version 12.01

2.2.1. Alignment axesAs a special type of curve SOFiMSHC allows to define alignment axes asprimarily used in road and railway design. These curves typically consist of a se-quence of straights and circular arcs with transition elements in between. In orderto avoid sudden changes in curvature transition curves (or easement curves) areplaced between sections with different radii providing a gradual change of curva-ture from one section to another. Depending on the characteristics of the curva-ture gradient different types of transition elements can be identified:

• Clothoid: Curvature varies linearly with distance s along the track

�(s)� 1r(s)

� sR·L

� sA2

(2)

• Bloss−Curve: Curvature varies cubically with distance s

�(s)� 1r(s)

� 3·s2

R·L2 2·s3

R·L2(3)

• Sinusoidal transition curve:

�(s)� 1r(s)

�2�s sin(2�s

L)

2�LR(4)

• Cosinusoidal transition curve:

�(s)� 1r(s)

�1 cos(�s

L)

2R(5)

Above formulas apply for a transition curve of length L which starts fromcurvature=0 (straight axis) to a circular arc with radius R (curvature = 1/R). Fortransitions between sections with different radii (e.g. reversing clothoid, egg−shaped clothoid), they have to be modified accordingly. SOFiMSHC supports allvariants.

The definition of alignment axes in SOFiMSHC is carried out separately in planview and elevation. In plan view, sections consisting of straights, circular arcs andtransition curves are combined into a sequence defining a two−dimensional curvein x,y−coordinates. The elevation of the curve can be defined independently fromthe plan view by setting height values and elevation radii. Curvatures in the elev-ation are applied as parabolas.


Version 12.012−4

The following two pictures show an alignment axis in ground view and elevation.The axis consists in the ground view of a circular arc segment and a reversingclothoid with a start radius of RA = −100m and an end radius RE = +50m. In theelevation view the curve is rounded off parabolically with a radius of 100m.

2.2.2. Freeform curvesFor defining freeform curves SOFiMSHC provides an implementaton of NURBSbased on the openNURBS library. NURBS (Non−Uniform Rational B−Splines)comprise a special class of curves widely used in computer aided design or com-puter graphics for modelling curves and surfaces of arbitrary shapes. Mathemat-ically, they consist of piecewise rational polynomials of a given order which areconnected together under consideration of certain continuity conditions (e.g. tan-gentially continuous, curvature continuous). Due to their construction using ra-tional polynomials, NURBS are also capable of representing circles, ellipses orhyperbolas mathematically exact. A definition of NURBS−curves basicallyinvolves the following set of properties and elements:


2−5Version 12.01

• DegreeThe degree decribes the highest polynomial exponent of the NURBS basisfunctions. Degree 1 is called linear, degree 2 quadratic, 3 cubic etc. A cubicdegree is generally sufficient, but curves with degrees up to 32 may be de-fined and used.

• Control pointsControl points are the basic construction points of a NURBS curve orsurface. With exception of the first and the last point they are notnecessarily located directly on the curve but will stay close to it. SinceNURBS curves are constructed using piecewise polynomials, the positionof a single control point only changes the shape of its adjacent basispolynoms. This so−called ’local property’ of Nurbs − in contrast to purepolynomial curves − allows to modify a curve locally without affecting thewhole shape of the curve. In addition to its xyz−coordinates a control pointsmay also have a weight assigned. By changing the control−point weightsto values <> 1.0 the basis functions convert to rational polynoms whichoffers the possibility to model also circular arcs, hyperbolas or ellipses withNURBS.

• KnotsBasically, a single knot−value defines the location on a curve where twoNurbs basis functions are connected. For a given NURBS curve with Ncontrol points they are usually stored internally as monotone list of size (de-gree+N−1). The knot−vector may be defined by the user in order to set thelocal curve parametrisation explicitly. In general cases however there is noneed to define the knots by the user as SOFiMSHC creates an appropriatedistribution automatically. Knots can also be defined repeatedly at thesame location. This knot multiplicity changes the default transitioncondition at the interface between two basis functions such that also kinksand even jumps could be modeled within one single curve.

2.3. Regions and geometric surfaces

SOFiMSHC supports different types of geometric surfaces which can be refer-enced in order to describe the shape of a structural region which is to be meshed.If no geometry is defined explicitly, SOFiMSHC tries to create the shape of asurface from its boundary description. This works, of course, for all plane surfacesand normally also for curved shapes with a less complex boundary description(e.g. four boundary edges in a rectangular like pattern). For complex shapes


Version 12.012−6

however, it is more reasonable to specify the geometric shape of a regionexplicitly.

2.3.1. Rotational and sweep surfaces

The general idea of these type of surfaces is that a surface is defined by movingan arbitrary curve in space. In case of a surface of revolution a curve c(v) is rotatedaround a straight axis. The parametric description of the surface s(u,v) is givenby

s(u,v)�M(v)·c(u) (6)

where the matrix M(v) defines rotation around an arbitrary axis in space. Theparameter v denotes the rotation angle in radians.A sweep surface is defined by moving a curve c(u) along a traction curve t(v). Thegeneral form of a sweep surface s(u,v) is given by

s(u,v)� t(v)�M(v)·c(u). (7)

The curve c(u) may also be rotated by M(v) within the local coordinate system ofthe traction curve after moving it along t. In most cases however, c(v) is only trans-lated along t(v) without rotation. The rotation matrix M defaults to the unity−matrixthen.

2.4. Structural elements

As previously mentioned SOFiMSHC basically distinguishes between geometricentities and structural objects. Geometric elements primarily define the shapeand the position of objects in space. Structural objects are referencing the shapeof the geometry elements and furthermore contain all relevant structuralinformation together with necessary mutual topological relationships. Thestructural model within SOFiMSHC corresponds to a classical B−Rep (boundaryrepresentation) data model which can be found in a similar form in other commonCAD−systems. B−rep models describe objects in space by describing theboundary of the objects. Structural lines, for example, are bounded by theirendpoints and structural regions are bounded by a closed sequence of structuraledges. Structural regions may also have internal boundaries forming openingsinside the region.


2−7Version 12.01

2.5. Mesh generationThe 2D−mesh generation is based on the work by Rank et al. for unstructuredmesh generation for pure quadrilateral meshes. [1]. The first step is to generatea triangular mesh which is then divided into a quadrilateral mesh. This is the rea-son why along all edges the number of sections will be even.

However there are specific macros for supports like columns modifying the basicgenerated mesh in a post processing step.

The 3D−mesh generation is either done as a structured mapped mesh generationbased on the surfaces generated before, or a unstructured mesh generation forpure Tetrahedron meshes. This is adopted from a mesh generator developed atthe University of Linz [2]. As the quality of Tetrahedron is significantly less thanthat of Hexahedron we have to generate a more dense element mesh. Bothmethods may be mixed within one system.

2.6. Literature[1] E. Rank, M. Rücker, M. Schweingruber (1994)

Automatische Generierung von Finite−Element−NetzenBauingenieur Heft 10, 1994

[2] Joachim Schöberl (1997)NETGEN − An advancing front 2D/3D−mesh generator based on ab-stract rules. Comput.Visual.Sci, 1:41−52, 1997.Software available under the Lesser−Gnu−Public−Licence (LGPL)

[3] Karypis,G. , Kumar,V. (1997)A Fast and High Quality Multilevel Scheme for Partitioning IrregularGraphs. http://www.cs.umn.edu/~karypis

[4] Farin, G. (1996)Curves and Surfaces for Computer−Aided Geometric DesignAcademic Press, San Diego

[5] Rank, E., Halfmann, A., Rücker, M., Katz, C., Gebhard, S. (2000)Integrierte Modellierungs− und Berechnungssoftware für denkonstruktiven Ingenieurbau: Systemarchitektur und NetzgenerierungBauingenieur 75, pp 60−66, Springer Verlag Berlin

[6] Piegl,L., Tiller,W. (1997)The NURBS Book, Monographs in Visual Communication Springer, Berlin


Version 12.012−8

2.7. Limitations

The following limits can not be exceeded in principle:

Number of nodes : 9 999 999Largest node number : 9 999 999Largest element number: 9 999 999

Structural points SPT 99 999Structural lines SLN 99 999Structural regions SAR 99 999Structural volumes SVO 99 999

Basically, the numbers of structural elements should not be selected with aunreasonably high value. The program needs to allocate unnecessary amountsof memory, which might increase the overall running time of the program.

Attention should be paid to the fact that only numbers below 1 Mio can be enteredand accessed within CADINP. This means that even though element numbersabove 1 Mio can be created in SOFiMSHC, these elements cannot be accessedfrom CADINP in order to set additional properties or apply loads etc. Thus, thegroup divisor setting the base number of the elements created within a groupshould be set to a reasonably small value.


3−1Version 12.01

3 General program control

3.1. Input language

The input in SOFiMSHC is generally carried out in CADINP language. More in-formation on this can be found in the general SOFiSTiK manual ’FEA /STRUCTURAL Installation and Basics’.

3.2. Units

SOFiSTiK programs offer the possibility to carry out all input and output of datain engineering units. A number of unit sets are provided for this purpose, whichare preset according to the design code used in the given project. This default canadditionally be changed for each program run separately using the keywordPAGE. More information about unit sets can be found in the general SOFiSTiKmanual, section ’Units’.

The description of the input values in this manual will always contain the unit, inwhich a given record is expected to be given. It shows also, if the input record fol-lows a predefined unit set.

Three categories of units are distinguished:m Fixed unit. Input is always required in the specified unit.[mm] Explicit unit. Input defaults to the specified unit. Alternatively, an

explicit assignment of a related unit is possible (eg. 2.5[m] ).[mm]1011 Implicit unit. Implicit units are categorised semantically and

denoted by a corresponding identity number (shown in green).Valid categories referring to the unit ’length’ are, for example,geodetic elevation, section length and thickness. The defaultunit for each category is defined by the currently active (designcode specific) unit set. This input default can be overridden asdescribed above. The specified unit in square bracketscorresponds to the default for unit set 5 (Eurocodes, NORM UNIT 5).

3.3. Remarks for the conversion from SOFiMSHB

As of version 2012, the previous mesh generator SOFiMSHB will be entirely re-placed by SOFiMSHC. Following remarks may help to convert old data sets:


Version 12.013−2

• Compared to SOFiMSHB, SOFiMSHC provides considerable more ca-pabilities for modeling structural systems. Especially due to the fact, thatstructural elements will be intersected and joined automatically inSOFiMSHC, there is no need to model adjacencies between elementsexplicitly any more. Structural elements can be defined in independentunits, which simplifies modification and extension of given data setsconsiderably. In general it is therefor recommended to revise old data setsand to adapt them to the new concept of SOFiMSHC.

• The syntax of the input records for structural elements in SOFiMSHC issimilar to those of SOFiMSHB. In order to convert a given input to aSOFiMSHC data set, it is therefore often sufficient to replace the record na-mes in the text file as follows:

GPT −> SPTGLN −> SLNGAR −> SAR (analogue GARB −> SARB)GVO −> SVO (analogue GVOS −> SVOS)

In the case that couplings and elastic beddings have been defined theymust be revised manually however, since their definition has beenchanged and enhanced within SOFiMSHC.

• The finite element model created with SOFiMSHB can basically also be ex-ported into a SOFiMSHA data set, which can be read in with the most cur-rent version in any case. In the case that none of the above approacheshas been successful, at least this might be a way to reuse already existingdatabases.

3.4. Input records

Record Items

SYST

GRP

CTRL

TYPE GDIV GDIR FIX XREF YREF ZREF T11 T12

T13 T21 T22 T23 T31 T32 T33

NO REF BASE TITL

OPT VAL V2 V3 V4

IMPO

EXPO

ECHO

OPT FROM PASS

OPT VAL TO PASS

OPT VAL


3−3Version 12.01

Record Items

COOR TYPE ID IDP S X Y Z T11 T12

T13 T21 T22 T23

XSUB TYP FIXA FIXL FIXM CD

Records HEAD, END and PAGE are described in the general manual SOFiSTiK:’Basics’.


Version 12.013−4

See also: SPT SPTP SLN SLNP SLNS SAR SARB SVO SVOS

3.5. SYST − Global system definitionÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SYST

Item Description Unit Default

TYPE SPAC 3D spatial structures

SOFiSTiK YX−plane accord. DIN 1080:FRAM Plane framePAIN Plane strain planar systemPESS Plane stress planar systemAXIA Axial symmetric system

(X is rotation axis)GIRD Plane girder or plate bendingPGIR Prestressed plate system

International XY−planeWFRA Plane frameWPAI Plane strain planar systemWPES Plane stress planar systemWAXI Axial symmetric system

(X is rotation axis)SLAB Plane girder or plate bendingPSLA Prestressed plate system

INIT Keep existing system typeREST Keep structural system

LIT GIRD


3−5Version 12.01

Item DefaultUnitDescription

GDIVGDIR

FIX

Group divisiorDirection of gravity load

XX, YY, ZZ, NEGX, NEGY or NEGZGlobal default constraints

−LIT

LIT

0*

−

XREFYREFZREFT11T21T31...T33

Origin of coordinate system in WCS

Transformation matrix WCS −> UCSDefault: T11 T12 T13 1.0 0.0 0.0

T21 T22 T23 = 0.0 1.0 0.0T31 T32 T33 0.0 0.0 1.0

mmm−

0.00.00.01.00.00.0

1.0

This record defines the type of the analytical model used for the given system.With the exception of TYPE REST, all structural elements will be deleted and thesystem will be reinitialized. An input of SYST REST keeps the system type alongwith all structural elements of a previous SOFiMSHC−run. Existing finiteelements will be deleted in any case.

The user coordinate system (UCS) in SOFiSTiK is always defined as a right−handed coordinate system, which can be linked to a global project coordinate sys-tem using a reference point and a transformation matrix. Since SOFiSTiK worksin the mks−system, the transformation matrix can be employed for connecting amm− based CAD−systems, for example.

For planar systems there are different conventions about the orientation of theglobal X,Y and Z axis. German Design Codes (e.g. DIN 1080) usually request thatthe global Z axis has to be aligned downwards into gravity direction (i.e. GDIRPOSZ). On the other hand, in an international setting often classical coordinatesystems are used with the Z axis pointing upwards (i.e. GDIR NEGZ). You mayselect your convention freely. Similar applies for planar 2D systems. Systems oftype FRAM, PAIN, PESS, AXIA, GRID or PGIR are systems where the globalZ−axis is directed into viewing direction whereas for WFRA, WPAI, WPES, WAXI,SLAB or PSLA the z−axis will be aligned towards the observer.

In the case of planar systems like FRAM/GIRD only half of the global unknownsare activated during analysis such that either out−of−plane or in−plane−deforma-tions and stress−resultants will be suppressed. Therefore, beams with principal


Version 12.013−6

axes different to the axes of the global coordinate system can be analyzed onlyin three dimensions.

The group divisor GDIV sets the mode how element numbers are assigned togroups. Further information can be found in the description of record GRP. Thedefault of 0 deactivates all group selection possibilities.

The global gravity direction sets the default direction of, for example, loads,boundary conditions or sections. It will be also used to set the default viewing di-rection of graphical programs.


3−7Version 12.01

See also: SPT SPTP SLN SLNP SLNS SAR SARB SARS SVO SVOS

3.6. CTRL − Control of analysisÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

CTRL


OPT A literal from the following list:

TOPO Topological decompositionONOFFDELGAXPSARBXFLG

TOLG Intersection toleranceNODE Start index of automatically

assigned numbersDELN Deletion of unused elements

LIT

LIT/−−

−−−−

[m]1001/−−

−

!

ON0

−+3+8+1

−0.011000

1

HEAL Geometry healingJOINDELO

LIT[m]1001

[m2]1002

!1.01.0

MESH Start of mesh generationHMIN Mesh sizeFINE Refinement at nodesEFAC Refinement at short edgesPROG Progression factor

−[m]1001

[m]1001/−−−

01.0

HMIN1.41.5

LOCA Local coordinate systemsTOLN geom. tolerance detection of

identical FE−nodesPSUP Point support modellingLSUP Line support modelling

−−

−−

11.e−6

01

OPTI Renumbering optimisationSUB No of subdomainsPART Controls mesh−partitioning

−−−

49−−


Version 12.013−8


WARN Suppress warning message − −

VALV2V3V4

Value of controlSecond value if neededThird value if neededFourth value if needed

−−−−

−−−−

This record is used to set global program control options. They can be classifiedas follows:

3.6.1. Analysis and generation of structural modelIn a first processing step, SOFiMSHC reads in the model entered by the user orgiven by CAD and intersects all elements with each other in order to obtain a me-chanically consistent structural system. The general behaviour during this pro-cess can be controlled using the following options.

TOPO ON V2Stores the input model entered by the user at the reference key givenat parameter V2 and activates the analysis and intersection of thestructural system.

TOPO OFFDeactivates the import and analysis of the structural system entirely,even if meshing of the structure has been activated (CTRL MESH ac-tivates CTRL TOPO ON automatically). This setting is usually onlyneeded for debugging purposes. The model must have been alreadyimported and analyzed in a previous run.

TOPO DEL V2Deletes the structural elements stored at the given reference key. Un-der normal circumstances, the database will be properly initializedand structural elements deleted, when setting the system type in-ternally (see SYST). Hence this option is usually only necessary inorder to analyze failed program runs.

TOPO GAXP V2Controls the automatic generation of structural elements betweenplacements on a geometric axis. Following options are possible (bit−mask):

+1: Generate structural points at placements+2: Generate structural lines beween placements


3−9Version 12.01

TOPO SARB V2Controls the definition and processing of boundary edges of structuralregions. Following options available (bit−mask):

+1: Boundary edges are always given in sorted order. Usually the case when importing from CAD and can be set to avoid unnecessary and extensive tests

In some cases, especially when importing data from external CADsystems, the type of the boundary edges is not clearly specified. Fol-lowing bitmask allows to control edges, which are internal to a regionand which has not been explicitly defined as opening (SARB IN) orconstraining edges (SARB CONS): +4: edges will be classified as boundary of an opening +8: edges will be classified as edges of a separate internal region +12: edges will be classified as constraining edges

TOPO XFLG V2This parameter controls the structural element intersection processon a global level. Following options (bit−mask) are available: +1: Structural points, which have been defined explicitly by the user (i.e. both have been assigned a number) will not be merged, even if they are located at the same position in space

In addition to that, the intersection of elements can also be controlledfor each structural element individually. See parameter XFLG in re-cords SPT, SLN and SAR, respectively.

TOLG This parameter sets the tolerance used during intersection of structu-ral elements. Elements (structural points, lines and areas) with adistance below the given tolerance will be merged. The tolerance canbe given in absolute or relative lengths:TOLG>0: absolute length in mTOLG<0: relative factor which will be scaled by characteristic lengthsof the model. Default setting is TOLG = −0.01


Version 12.013−10

NODE This parameter sets the start index for the numbers of automaticallycreated structural elements and FE−nodes. During analysis of the in-put model, new structural elements can be created, which will be assi-gned a number automatically. Especially when working with multipleSOFiMSHC input blocks within one project, it is recommended to setthis parameter to a higher value in order to separate automatically as-signed from explicitly defined numbers.

DELN Deletion of unused structural points and lines.Basically, SOFiMSHC deletes structural points and lines which arenot connected with the model and which have no stiffness properties: 0: Unused structural points and lines will not be deleted 1: Unused structural points and lines will be deleted (default)

3.6.2. Geometry healingModels from external CAD−systems or files often exhibit geometric inconsisten-cies resulting in failed meshing runs or poor element quality. SOFiMSHC providesa number of options for correction of geometry:

HEAL JOIN V2[m] V3[deg]In some cases basically connected curve or line sequences will beexported from external systems fragmented into multiple short struc-tural lines. A large number of such short structural lines might incre-ase the number of elements in the resulting finite element mesh unne-cessarily. This options allows to join adjacent structural lines of similartype to single edges.Two neighboring lines will be connected, if the following requirementsare met:− The length of the adjacent lines lies below the given parameter V2− The angle between the two lines is lower than V3− There is no other edge connected (no Y−joint)− Boundary and cross−section properties do not change.

HEAL DELO V2This options deletes openings with a surface area below the given va-lue V2.


3−11Version 12.01

3.6.3. Meshing controlMESH This parameter activates the mesh generation for the defined model.

Following options exist:0 deactivate meshing1 meshing of beam structures2 meshing of beam and shell structures3 meshing of beam, shell and/or volumes

In addition to the basic options 1−3 one may add the following values:+ 16 keep explicit old elements+ 32 triangular elements only+ 64 quadrilateral elements only+ 96 mixed element shapes allowed+ 128 disable dupl. run with background mesh+ 256 post−processing only (partitioning, optim.)

A CTRL MESH automatically activates the topological analysis andintersection of structural elements (STEU TOPO 0)

HMIN Parameter HMIN controls globally the element size of the resultingfinite element mesh. It defines the maximum allowed length of a beamand/or the edge of a shell or volume element. Please note, that themesh density defines only an upper bound for the element size. Localgeometric features or other constraints might require a smallerelement size.In addition to the global setting, the mesh size can be overwritten indi-vidually for single structural objects (structural points, lines, regions).

EFAC This parameter controls the mesh density in the vicinity of short struc-tural edges. In the neighborhood of short structural edges, whoselength are below the global element size HMIN, the mesh density isreduced locally in order to avoid distorted quad elements with highlydifferent edge lengths. The parameter describes the factor

“Local mesh size” / “Length of short edge”

Default setting is a factor of EFAC=1.40. For models containing manysmall edges, however, this setting might result in meshes with manylocal refinements, which increase the total number of elementsconsiderably. In order to avoid the local refinements, this factor


Version 12.013−12

should be increased with the disadvantage, that the element qualitymight be reduced. On the other hand, if a model contains relativelylong and small structural areas, whose width lies below the globalmesh density, it is recommended to deactivate this parameter entirely(EFAC = 0). This avoids the reduction of the mesh density to the endsof the areas which results in a more regular mesh.

PROG This parameter defines the rate, how the mesh density is increasedfrom a local refinement to the global part. It describes basically themaximum allowed ratio of the edge size between two adjacent quadelements. Standard setting is a progression factor of PROG = 1.5.

3.6.4. Element generation and boundary conditions

LOCA Controls the definition of the local coordinate−system of beam ele-ments.

0 = local z−axis points into gravity direction resp. the local y−axis intothe first global horizontal axis if the former is not possible (i.e. beamaxis parallel to gravity). User defined orientations are applied to thelocal y−axis.

1 = local z−axis points into gravity direction resp. into the first globalhorizontal axis if the former is not possible (i.e. beam axis parallel togravity). User defined orientations are applied to the local z−axis.

2 = local z−axis points into global Z resp. into global X if the formeris not possible (i.e. beam axis parallel to global Z). User defined ori-entations are applied to the local z−axis. (Default in Industry Founda-tion Classes, IFC)

3 = local z−axis points into global Z resp. into global Y if the formeris not possible. User defined orientations are applied to the localy−axis (GENF).

TOLN This parameter controls the detection of double finite element nodes.FE−nodes whose distance lies below the given tolerance are in-tersected and replaced. The parameter is given as relative factorwhich will be scaled internally by model dimensions.


3−13Version 12.01

PSUP controls the mesh generation for Point−Support (Bitpattern)−1= no special action 0= generate 4 rectangular quad elements (default) 1= increase thickness of elements at support 2= cinematic constraints of mid points 4= cinematic constraints of corner points 8= additional centre node for constraints16= deactivate the correction of minimum mesh size

LSUP controls the generation of boundary elements (= supporting lines) onstructural lines: 0 = create boundary elements if the line has an elastic support

or contains only a group nr > 0 without a section nr. 1 = create boundary elements also for structural lines with rigid

support in gravity direction (default setting) 2 = create boundary elements if any type of support is given. 3 = create boundary elements for all edges. 4−15: reserved for internal tests. +16 = create elastic springs instead of boundary elements.

3.6.5. Mesh decomposition and band−width optimizationOPTI SOFiMSHC optimizes the internal numbering of the created FE−

nodes in order to allow a efficient storage and solution of the resultingfinite element equation system. This can be controled using the fol-lowing options (bit−mask): 0 = no reordering 1 = fast global reordering 2 = best global reordering 3 = best local and global reordering +16 use Metis−random Matching (RM)

+32 use Heavy−Edge Matching (HEM)+48 use Sorted HEM+49 use for Sparse−Solver (default)

The type of optimisation should be adapted to the equation solver tobe used. An improper setting may have adverse effects.

CTRL SOLV 1 options 1 to 3CTRL SOLV 2 option 1CTRL SOLV 3 options >16 (recomm. 49)CTRL SOLV 4 options >16 (recomm. 49)


Version 12.013−14

Option 2 should not be used for systems which decompose into sev-eral independant subsystems.

SUB By setting the parameter SUB the mesh partitioning tool metis is re-quested to decompose the finite element mesh into the given numbersubdomains.

PART Bitpattern to control partitioning 0 = use PMETIS or KMETIS (SUB>8) 1 = use KMETIS for mesh partioning 2 = use PMETIS for mesh partioning

+16 = use Random Matching (RM)+32 = use Heavy−Edge Matching (HEM)+48 = use Sorted HEM (Default)

256 = use reordered nodal−Bisection257 = use group definitions

3.6.6. Warnings and error messagesWARN The given warning will be supressed.


3−15Version 12.01

See also: SYST

3.7. GRP − Group controlÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GRP


NO

BASETITL

Group number

Base number for this groupTitle of the group

−/LIT

−Lit32

!

*−

Element groups are an important aid for the definition of construction stages orthe assignment of loads, for example. Structural lines, areas and volumes definedin SOFiMSC can be assigned to different groups. Thereby it must be distinguis-hed between primary and secondary groups:

3.7.1. Primary group numberThe primary group number is uniquely defined for each element. Each group isassociated with a range of element numbers which easily allows to reconstructthe group id from the element id. SOFiMSHC provides different methods for theassigment of element numbers to a group. The kind of assignment is specifiedby the group divisor GDIV in the main system record SYST.

• GDIV > 0The group number of a single element is defined by the integer division ofthe element number by the group divisor.

Example: Group number Group divisor Element numbers0 1000 0 − 9991 1000 1000 − 19992 1000 2000 − 29992 5 10 − 14


Version 12.013−16

• GDIV=0All groups must be assigned an individual base number in increasing order.An element number within one of the intervals defines the membership tothe respective group.Example: Group Base Element number

0 1 1−999991 100000 100000−1999992 200000 200000−2499993 250000 250000−2599994 260000 from 260000

• GDIV<0The base values of all groups will be defined automatically after all ele-ments have been generated. It is thus not any longer necessary to definebase values individually. The value at GDIV<0 defines the lowest commonmultiple from which the element numbers of the next higher group will beassigned to. The current limit for elements within a group is set to 1 Million.

For all cases, the maximum group number is 999. The base number and designa-tion is identical for all elements within a group. Large element numbers will besplitted into its group and element part in print outputs in order to support betterreadability. It is therefor also recommended to use base numbers which are a mul-tiple of 100, 1000 or 10 000.

3.7.2. Secondary groups

In addition to their primary group number, elements can be assigned to any num-ber of so called secondary groups. Secondary groups are labeled using a textstring of maximum four characters (e.g. ’GR1’). The assignment of elements tosecondary groups is done separately after definition of the structural system.Subsequently to the definition of the secondary group using this record any num-ber of selection records can be given. Following type of selections are possible:

SLN NO selection of a structural lineSAR NO selection of a structural areaGUID ID selection using the Globally Unique Identifier of a structural

element (usually defined in a CAD−system)BBOX selection using a rectangular bounding box.


3−17Version 12.01

Example:GRP NO ’GR1’SLN NO 1,2,3SAR NO 5

defines a secondary group labeled ’GR1’, which contains all beam and areaelements created on the structural lines 1, 2 and 3 and structural area 5.

Apart from this selection mechanism, elements can also be assigned to a secon-dary group using attribute regions. For more information please see at the de-scription of attribute regions at record SAR.


Version 12.013−18

3.8. IMPO − Import of data

ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖ

IMPO


OPT Special options0 no special options1 convert xyz to yzx system2 convert xyz to zxy system4 Set origin pointer to elementno8 Set origin pointer to elementno

without group number16 do not extrude support conditions256 Use Group instead of geometry

numbers for selections

− 0

FROMPASS

Name of a databasePassword of database

Lit96Lit16

*−

With the record IMPO you may select for the 3D−extrusions the meshes to beused for the extrusion from a different database. This record may be defined onlyonce and is then valid for all extrusions.


3−19Version 12.01

3.9. EXPO − ANSI export of data

ÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖÖ

EXPO


OPT

VAL

Data to be exportedGAX Geometric axisGAR Geometric surfaceRAW Basic structural model

ID of axis, surface (optional)

LIT

Lit4

RAW

−

TOPASS

Name of a file to write toPassword of database

Lit96Lit16

*−

Using record EXPO geometric or structural elements within the database can beexported into an input file for SOFiMSHC. This can be useful when analyzing thedata after an error occured or to make further use of the data in different settings.

If an Identifier is given additionally at GAX or GAR, only the selected geometricaxis or surface is exported to the file, otherwise all elements of the given type areexported. When using option RAW, an additional literal ’FULL’ may be addedwhich allows to extend the export also to internally used datatypes. In this casefor example, globally uniqe identifier (GUID) of the structural elements, which willbe used for idenfication of structural objects in different CAD−systems, will beexported to the input file.

If no file name is specified the data will be exported to a file namedproject_MEX.dat.

The units of the values will be set to the current setting of UNIE from record PAGE.The language of the new file will be the same as the current CADINP input file.


Version 12.013−20

See also:

3.10. ECHO − Control of outputÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

ECHO


OPT A literal from the following list:

MAT Material dataSECT Section for beamsGEOM Geometric itemsNODE Generated nodesQUAD Generated quadrilateralsBRIC Generated volume elementsBEAM Generated beam elementsBOUN Generated elastic supportsSYST System summarySTAT Analysis statistics

FULL all the above options

LIT FULL

VAL Value of output optionNO no outputYES regular outputFULL extensive outputEXTR extreme output

LIT FULL

The name (ECHO) of this record must be repeated every time the command isbeing used, otherwise it may be confused with other records with the same name.


3−21Version 12.01

See also: GAXP SPT SLN SAR

3.11. COOR − User defined coordinatesystem

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

COOR


TYPE

IDIDP

Type / reference of coordinate systemWRLD: world coordinate systemSPT: reference to structural pointAXIS: reference to axisGAXP: reference to placementCYLI: cylindrical coordinate systemSPHE: spherical coordinate system

Number / ID of reference itemID of placement (Type GAXP)

LIT

−/Lit8Lit4

WRLD

−−

S

XYZ

T1XT1YT1Z

T2XT2YT2Z

Parameter on axis (Typ AXIS, GAXP)

Coordinate of origin(Type WRLD, CYLI, SPHE)

Direction first axis

Direction second axis

−

[m]1001

[m]1001

[m]1001

−−−

−−−

−

0.00.00.0

1.00.00.0

0.01.00.0

This record sets a new reference coordinate system for position and direction in-put in SOFiMSHC. After setting the coordinate system, all succeding input of aposition or a direction in any structural or geometrical record will be interpretedaccording to the given coordinate system. The coordinate system can bechanged within a data record as often as desired. Setting COOR WRLD resetsthe coordinate system to the default, an euclidian coordinate system with originat (0,0,0).

Different types are provided to set the coordinate system:


Version 12.013−22

• WRLD: world coordinate systemThis type defines an euclidian (orthogonal) coordinate system with origingiven at X,Y,Z. The orientation of the coordinate system can be set usingthe paramters T11 to T23. They define the first local direction T1(T11,T12,T13) and the second local direction T2 (T21,T22,T23) . The thirddirection is derived from the cross product of the first and second axis. Inthe case that the second direction is not orthogonal to the first, it will be or-thogonalized.

• SPT: Reference to structural pointBy setting a structural point number at ID, the coordinate system will bemoved to the local coordinate system of an already defined structural point.

• AXIS: Reference to structural line/axis at station SThe coordinate system will be moved to the respective station S of an axisor a structural line and rotated according to the local coordinate system ofthe axis. The axis or structural line resp. is given at ID. It is also possibleto reference secondary axes (e.g. ID ’A1.B’).

• GAXP: Reference to placementThe coordinate system is moved to the location of a placement, which hasbeen defined using GAXP at an axis. The second and third direction of thecoordinate system (local y and local z) will be aligned according to the cut−plane of the placement (local z usually points into gravity direction). Theaxis is given at parameter ID. The placement can be identified by its pa-rameter position at S or its identifier given at IDP.

• CYLI: Cylindrical coordinate systemBy indicating an origin at X,Y,Z and two direction vectors at T1(T11,T12,T13) and T2 (T21,T22,T23), a cylindrical coordinate system canbe defined.All succeding input of a position (X,Y,Z) or a direction (DX,DY,DZ) will beinterpreted according to the following scheme:

X: Radius (distance) from rotational axisY: Azimut angle in rotational planeZ: Height along rotational axis

• SHPE: Spherical coordinate systemBy indicating an origing at X,Y,Z and two direction vectors at T1(T11,T12,T13) and T2 (T21,T22,T23), a spherical coordinate system canbe defined.


3−23Version 12.01

All succeding input of a position (X,Y,Z) or a direction (DX,DY,DZ) will beinterpreted according to the following scheme:

X: Radius (distance) from originY: Azimut angle ’phi’ in equatorial planeZ: Inclination from equatorial plane


Version 12.013−24

See also: GUID BBOX

3.12. XSUB − Extraction of subsystemsÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

XSUB


TYPE

FIXAFIXLFIXM

CDB

Systemtype of SubmodelSPAC spatial systemSLAB 2D plate/girder system

Type or factor of axial stiffnesType or factor of lateral stiffnessType or factor of rotational stiffness

Name of File to be created

Lit4

−/Lit−/Lit−/Lit

LIT

SPAC

FIX1.01.0

This records allows to extract a partial system from a general structural model fora detailed analysis. The extracted model will be stored in a new database asplanar slab or again as new spacial system, which can be then meshed and calcu-lated in a separate independent project.

In the case, that the partial model will be extracted as plate system (TYPE SLAB)all selected structural elements will be projected onto the xy−plane at coordinatez=0.0.

All structural elements connected to the partial model which will be cut during theextraction, like adjacent columns or walls, will be replaced by linear elastic springelements or fixed supports approximating the stiffness at the connection. Thegeneration of these boundary conditions can be controlled using the parametersFIXA to FIXM. The three parameters can be distinguished between axial, lateraland rotational stiffness components.

• FIXV: Control of axial stiffnessThe bedding component in axial direction of connected elements will becalculated as follows:

Connected Structural line ca = E*A/lStructural area: ca = E*T/h

’A’ denotes the cross section area and ’l’ the length of the connected struc-tural line (e.g. column). For adjacent structural areas the linear elastic line


3−25Version 12.01

bedding replacing the area will be calculated from the plate thickness andthe average height.

• FIXH: Control of lateral stiffnessThe stiffness in transversal direction will be calculated under the assump-tion, that the connected building element has hinged support at the bottom:

Structural line: cl = 3 * E Iy / l3 (bzw. 3 * E Iz / l3)Structural area: cl = 3 * E Iy / h3

For an adjacent structural line two spring elements will be created for thestiffness in the direction of the local y− and z−axis of the cross section. Fora connected structural region, the supported line will be fixed in longitudinaldirection.

• FIXM: Control of rotational stiffnessFor the computation of the rotational stiffness, it is again assumed, that theconnected building element has hinged support at the bottom:

Structural line: cr = 3 * E Iy / l2 (bzw. 3 * E Iz / l2)Structural area: cr = 3 * E Iy / h2

In all three cases, a numerical value > 0.0 or one of the two literals FIX or FREEcan be given at FIXA to FIXM. In the case, that a numerical value is given, it willbe interpreted as factor multiplying the default stiffness values calculated as givenabove. The literal ’FIX’ creates a fixed support and the literal ’FREE’ releases therespective degrees of freedom entirely.

The elements of the partial system are selected by entering subsequent recordsdirectly after XSUB:

• SLN: Selection of a structural line with number NO

• SAR: Selection of a structural region with number NO

• GUID: Selection using a Globally Unique Identifier (GUID)A GUID uniquely identifies a structural element and will be usually setwhen exporting the model from a CAD system (e.g. SOFiPLUS, Exten-sions for Revit).

• BBOX: Selection using a rectangular bounding boxThis option is especially suitable for selecting all structural elements on aspecified floor level (e.g. BBOX z1 9.5 z2 10.5).


Version 12.013−26

The selection records given above can be defined in any number and any order.


4−1Version 12.01

4 Definition of geometric elements.

This chapter describes the definition of general geometrical elements like geome-tric axes or surfaces.

4.1. Input records

Record Items

GAX

GAXA

GAXH

GAXB

GAXC

GAXN

GAXP

GAXS

GAXV

NO TYPE ID2 ID3 ID4 ID5 REF SUR1 SUR2

TYPC DEG TITL

S X Y SX SY L R

RA RE LA LE TYPS

S H R

R XM YM ZM NX NY NZ X1 Y1

Z1 X2 Y2 Z2 X3 Y3 Z3

X Y Z W NX NY NZ ALFX ALFY

ALFZ

S MUL DIV

ID IDS S TYPE GPT GRP NCS Y Z

ALF ALFX ALFY ALFZ INCR INCL

ID IDS GPT GRP Y Z TITL

ID NAME S V DV TYPE

GAR

GARA

GARC

GARS

NO TYPE DEGU DEGV M N TITL

NO TYPE GIDI GID2 X Y Z NX NY

NZ SMIN SMAX TMIN TMAX M N TITL

NU0 NU1 NV0 NV1 XUV1 YUV1 ZUV1 XUV4 YUV4

ZUV4

M N X Y Z W T


Version 12.014−2

See also: GAXA GAXH GAXB GAXC GAXN GAXP GAXS GAXV

4.2. GAX − Geometric curve or axisÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAX


IDTYPE

Axis identifierType of axis

DEL delete this entryNONE no specific typeAXIS system axis (e.g. A−A)BEAM axis of beam sequenceLANE traffic laneTEND tendon axis

Lit4LIT

!LANE

ID2ID3ID4ID5

Reserved for export of additional dataReserved for export of additional dataReserved for export of additional dataReserved for export of additional data

−−−−

−−−1

REFSUR1SUR2

TYPCDEGR

Reference to a master axisNumber of a geometric surfaceNumber of a second geometric surface

Type of curve to be generatedDegree of spline curve (see GAXC)

Lit4Lit4Lit4

LIT−

−−−

**

TITL Designation of axis Lit32 −

This record defines alignment axes for road design or arbitrary geometric curveswhich are generally idependent from structural elements. In SOFiMSHC,geometry axes represent mainly general data structures allowing to define fullyparametrc input data sets. One important application area, for example, is bridgedesign, where all elements of a bridge can be defined relatively to this central axis.Once the geometry of the axis is changed, all dependent structures will beadapted automatically. In addtition, arbitrary variable distributions can be definedfor a geometry axis, which can be used, for example, to describe varying sections,additional load lines or secondary girders.

As axis identifier at ID only literals consisting of maximum four characters are allo-wed, for example GAX ID ’AX1’.


4−3Version 12.01

For defining the geometry SOFiMSHC provides a number of possibilities(parameter TYPC). The geometry of an axis is defined by subsequent records offollowing types:

• AXIS (GAXA / GAXH) Alignment axes in plan view andelevation

• ARC (GAXB) Straight lines and circular arcs in 3D

• POLY (GAXC) Polygonal line

• SPLI (GAXC) Cubic B−Spline Interpolation

• HINT (GAXC) Hermite−Interpolation

• NURB (GAXC / GAXN) Arbitrary Freeform Curves(B−splines, NURBS)

In addition to its geometric shape the following records allow to define additionaldependant parameters and properties:

• GAXS Secondary axes

• GAXP Placements: special positions alongan axis

• GAXV Definition of variables along an axis

Freeform curves of type GAXC can also be defined relatively to an other axis.Ifa previously defined curve is given at record REF, all following coordinates areinterpreted relatively to the curve. This allows to define offset curves or to createan identical copy of an axis.

It is also possible to project curves onto a surface or to create a curve byintersecting two arbitrary surfaces:

• If a single surface is given at SUR1, the curve will be projected onto thegiven surface.

• In the case that two surfaces are defined at SUR1 and SUR2, thegenerated curve is the intersection of the two given surfaces.


Version 12.014−4

See also: GAX GAXH GAXP GAXS GAXV

4.3. GAXA − Axis plan viewÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAXA


SXYSXSYLRRARELA

LE

TYPS

Station valueCoordinates of startpoint / tangential intersectionDirection of tangent

Length of sectionRadiusRadius of the axis at startRadius of the axis at endLength of first transition element or<0 for Clothoidal parameter (R*L=A2)Length of second transition element or<0 for Clothoidal parameter (R*L=A2)Type of transition curve

−mm−−mmmmm

m

LIT

*******RR*

LA

CLOT

Record GAXA defines sections of a setting out line in plan view for a preceedingaxis GAX. SOFiMSHC provides two different possibilities of definition:

Length based definition:

Using this mode, an axis always starts with a startpoint (station + coordinate) anda tangential direction, e.g.

GAXA S 250.0 X 0 0 0 SX 1 0 0.

Subsequently, single segments are defined with their length and possible startand end radius:


4−5Version 12.01

GAXA L 50.0 RA 0.0 RE 200.0GAXA L 50.0 R 200.0GAXA L 50.0 RA 200.0 RE 0.0GAXA L 50.0

For segments with different radius between start and end, a transition curve is in-serted. A radius with positive value cause a curvature to the right−hand side,whilst a negative value a curvature to the left−hand side. Using the input above,for example, a sequence consisting of a transition element, a circular arc, a transi-tion element and a straight segment at the end will be created.

Tangentially based definition

Pi−1

Pi

PC

RRA

RE

R

In this kind of input, the user defines the intersections of the curve tangents to-gether with a curvature radius and different length parameters, for example:

GAXA X 0.0 Y 0.0GAXA X 30.0 Y 10.0 R 40.0 LA 10.0 LE 10.0.GAXA X 60.0 Y 0.0

Using this parameters SOFiMSHC inserts a curve sequence such, that its endpoints fits tangentially to the predefined polygon. For the parameter following pos-sibilities exist:

• The minimum radius at R and the total length of the curve sequence is gi-ven at L. In this case, a curve sequence is inserted under consideration ofthe symmetry condition A1=A2. This is called a “symmetric standard se-quence”.

• The minimum Radius R and the length of the two transition segments LAand LE are given. This case defines a so called “asymmetric standard se-quence”. The length of the circular segment is calculated automatically.The user may also define a start radius RA and an end radius RE. In this


Version 12.014−6

case, the curve sequence does not any longer fit curvature continuouslyto the tangents.

• If no radius is given at all, a polygonal axis with kinks is created.

In the case that the parameters of the transition elements define a shorter lengththan needed, a straight segment will be inserted before the standard curve se-quence and the position of the tangent points will be adjusted accordingly.

Instead of a Clothoid, also a cubic parabola (TYPS CUBI) (not recommended) ora Bloss Curve (TYPS BLOS) may be used as transition element. And finally,SOFiMSHC also allows to use sinusoidal (TYPS SIN) and cosinusoidal (TYPSCOS) transition elements.


4−7Version 12.01

See also: GAX GAXA GAXP GAXS GAXV

4.4. GAXH − Axis heightsÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAXH


SHR

Station valueHeightRadius of elevation

−mm

***

GAXH defines the elevation of an alignment axis defined previously at GAX. Ac-cording to the convention used in road design positive height values will be placedin a direction opposite to the globally defined gravity direction (POSZ, NEGZ).Curvature radii will be applied as quadratic parabolas.

R

P2

P1

P3

P4


Version 12.014−8

See also: GAX GAXA GAXH GAXP GAXS GAXV

4.5. GAXB − Straights and circular arcsin 3D

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAXB


RXMYMZMNXNYNZ

RadiusCoordinates of center

Direction of normal to circle plane

[m]1001

[m]1001

[m]1001

[m]1001

−−−

−−−−−−−

X1Y1Z1X2Y2Z2X3Y3Z3

Startpoint of circular arc / straight

Endpoint of circular arc / straight

Third point on circular arc

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

−−−−−−−−−

S1S2

Parameter at start (optional)Parameter at end (optional)

−−

0.0−

Records of type GAXB can be used to define straight lines, circles and cicular arcsin space. Records of this type always refer to the most recently defined curve atGAX. Multiple segments are allowed to be entered in order to define polycurves.For the definition of a single segment following possibilities exist:

• A straight line is defined by its start− and endpoint at (x1,y1,z1) and(x2,y2,z2).

• A full circle can be defined by its center (xm,ym,zm), the radius and the nor-mal on the circular plane (nx,ny,nz).

• A circular arc can be defined by its start− and endpoint at (x1,y1,z1) und(x2,y2,z2), a radius and the normal or by entering the start−, the endpointand the center.


4−9Version 12.01

• In addition, circular arcs can also be defined by entering three points on thearc. (x1,y1,z1) und (x2,y2,z2) describe the start− and the endpoint, (x3,y3,z3)a third point on the arc.

When multiple segments are defined, the transition between two segmentsshould be modeled with continuous tangents. Kinks are possible but should beavoided as they can lead to incorrect or erroneous meshes. In order to definekinks it is better to define two curves with a structural point in between.

Using the parameters S1 and S2 the chainage (or parametrisation) of the curvecan be set explicitly. If nothing is given at S1 and/or S2 the parametrisation is de-fined according to the true (arc) length of the curve.


Version 12.014−10

See also: GAX GAXN GAXP GAXS GAXV

4.6. GAXC − 3D curve point data


GAXC


XYZ

WS

3D coordinates

Weight of control point (NURBS)Station on point (for interpolation)

[m]1001

[m]1001

[m]1001

−−

0.00.00.0

1.0−

DXDYDZ

NXNYNZ

Tangential direction (Type HINT)

Direction of local z−axis (not available)

−−−

−−−

−−−

−−−

The geometry of arbitrary freeform curves can be defined with this record by ente-ring characteristic data points. Each record GAXC defines a single coordinate in3D. The points always refer to the directly preceding geometry axis. The type andthe degree of the curve is specified by the parameters TYPC and DEG within themain record GAX:

• POLY: Interpolation as polygonal sequenceThe given points will be connected to a polygonal line.

• SPLI: Spline interpolationThe given datapoints will be interpolated using a cubic B−Spline. The inter-polation is carried out curvature continuous at the definition points (C2−continuity).The chainage (parametrisation) of the curve can be set explicitly at eachdatapoint using the parameter S. If no parameter values are given,SOFiMSHC assigns a parametrisation automatically. The end chainagecorresponds to the geometric length of the axis in this case.


4−11Version 12.01

• HINT: Hermite interpolationThe given datapoints will be interpolated using piecewise cubic B−Splinesegments. The interpolation is carried out tangentially continuous at thedefinition points (C1−continuity).Using the parameters DX,DY,DZ, the tangential direction at certain pointscan be defined explicitly by the user. Similar to the spline interpolation, theparametrisation (chainage) along the curve can be set using the parameterS.

• NURB: NURBS−curveA NURBS (Non Uniform Rational B−Spline) curve can be defined by ente-ring the euclidian coordinates of the control−points at X,Y,Z. If weights <>1.0 are given, the input results in a true ’rational’ NURBS curve, which, forexample, allows to describe also circle and ellipses. The degree of theNURBS curve can be set in record SLNN, when defining the knot vector.

It is also possible to create curves relatively to an existing axis. If a reference axisREF is given in the main record GAX, the X−values are then interpreted as stationvalue S on the reference axis and the values Y and Z as distances relatively tothe local coordinate system of the referenced axis. The thus defined points arethen interpolated by a cubic B−spline (TYPC SPLI). Contrary to secondary axesat GAXS, the reference is resolved explicitly, i.e. a new independent geometry iscalculated based on the definition of the data points.

At NX,NY,NZ a user defined orientation of the local z−axis can be set for eachpoint on the curve independantly. This allows to define, for example, arbitrarily ori-ented cross−sections along a curve or an axis. If no directions are given at all, thelocal z−axis is oriented towards the globally defined gravity direction.


Version 12.014−12

See also: GAX GAXA GAXH GAXC GAXP GAXS GAXV

4.7. GAXN − Knot value of aNURBS−curve


GAXN


SMULDEGR

Knot valueMultiplicitydegree of Nurbs

−−−

!11

Records of type GAXN are used to define the knot vector of NURBS−curves orto explicitly set the parametrization of interpolation curves. For each knot valueof a NURBS or parameter value a single record GAXN is to be entered whichrefers to the previously defined geometry axis at GAX. Multiple knot−values (e.g.at the ends of a curve) can be entered in a single record using multiplicities > 1.Within the first record the polynomial degree of a NURBS−curve can be set usingparameter DEGR.

When NURBS−curves are defined in SOFiMSHC knot vectors must always begiven with multiple knots at the ends (“clamped ends”) with a multiplicity equal tothe degree of the curve. In the case that no knot−vector is given by the user at all,a uniform distribution is assumed internally.


4−13Version 12.01

See also: GAX GAXS GAXV

4.8. GAXP − Axis placementsÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAXP


IDIDS

STYPE

Ident of primary axisSelection of secondary axes

0 = primary, A−Z for secondary,’*’ = all, ’+’ = only secondary axes

Station valueType of placement as combination of

’S’ support’J’ construction joint’A’ startface’E’ endface’H’ horizontal connection

Lit4LIT

−/LitLit8

−*

!−

SPT

GRPNCS

IDP

Number of structural point to be created atthe placementGroup number of the following sectionCross−section number of the subsequentsection or number before and behind theplacement given as Literal ’ncs1.ncs2’Identificator of placement

−

−−/Lit

Lit4

−

00

−

YZALFALFXALFYALFZINCRINCL

TITL

additional explicit transverse offsetadditional explicit transverse offsetAlignment about the global Z directionSkew about the local x−axisSkew about transverse y−axisSkew about vertical z−axisCross fall to the right (+y)Cross fall to the left (−y)

Title of placement

mm

degdegdegdeg−−

Lit32

0.00.0−

0.00.00.00.0

−INCR

−

GAXP is used to define important sections and points, so called placements,along a geometry axis GAX at a specific station S. A placement can be definedexclusively for the main axis or for one of the secondary lines, but can also be as-signed to all or all secondary lines simultaneously. A combination of literals (e.g.


Version 12.014−14

’SJ’) can be set at TYP for classification of the placement. In order to avoid ambi-guous input it is recommended to enclose the literals in apostrophes.

Based on the placement definitions SOFiMSHC can create a structural systemconsisting of beam elements along the axis. For each placement a structural pointwill be created on the axis whose node number can be set at SPT. In betweenstructural lines will be created, which get the number of their preceding point assi-gned. The user may specify a group or section number for a specific placementon the axis which are then used for all subsequent beam elements created unlessone of the number is changed. The generation of the structural elements basicallystarts at the first placement which has a cross−section number assigned andends at the end of the axis or if a placement is of type ’E = endface’.

In order to facilitate the organization of point and group numbers the user maydefine offset numbers at secondary axes GAXS which are then used to set therespective group and points numbers of the placements on secondary lines. If nopoint number is given at a specific placement, SOFiMSHC assignes a numberautomatically starting from SPT=1000 in intervals of 100 along the axis. In orderto prevent unintended interference of user defined and automatic numbers, it isrecommended to set the start index of automatically assigned number inSOFiMSHC at parameter CTRL NODE from 1000 to a sufficiently higher value.

A placement basically defines an infinite plane at a given station S perpendicularto the axis tangent. Structural points and other placement properties on second-ary axes will then be created at the intersection of this plane with the axis. Thisinfinite plane can be further rotated about the three local axis coordinates by set-ting ALFZ, ALFY and ALFX or may be aligned within the global X−Y coordinateplane by setting an angle at ALF = {1−360 deg}.

S2

S1S3

S4

GAXPGAXP

GAXPGAXP

GAXSALF

ALFZ

Secondary axis relative to axis

When placements of type support, start or endface (Type ’S’, ’A’ and ’E’) aredefined, an internal variable array S_XI() is automatically set up which providesthe curve parameter S with respect to span lengths between supports. For ex-


4−15Version 12.01

ample, S_XI(0) provides the S−parameter of the start face, S_XI(1) the locationof the first support, S_XI(1.5) the mid of the first span and so on.

Anstelle des Stationswertes S kann auch der Name einer Variablen als Literaleingegeben werden. In diesem Falle werden für jede Stützstelle der Variablenautomatisch Placements vom angegeben Typ erzeugt.

Instead of the station value S the user may also enter the name of a variable. Inthis case placements of the given type will be created for each base−point of thevariable.

Further we have two values for the cross fall. The sign of the inclination is definedthat an increase of height in the direction outward is positive,

INCR�� z� �y

�;� INCL�� z� �y

Y

Z

−INCR

−INCL

Inclination

For using the inclination two variables #INCR and #INCL may be used (e.g. fora direction of an edge within a section). However, this variable contains not thetangent value, but the clockwise angle in radians about the X−axis defined by theinclination. The value of 0 is the direction of the Y−axis to the right.


Version 12.014−16

See also: GAX GAXP GAXV

4.9. GAXS − Secondary axisÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAXS


IDIDS

Ident of Primary axisIdent of secondary axis (A to Z)

Lit4LIT

*0

SPTGRPYZTITL

offset for structural point numbersoffset for group numbers of GAXPoffset in transverse directionoffset in vertical directionDesignation of continuous beam

−−

m/Lit16m/Lit16Lit32

10

0.00.0−

GAXS defines a secondary axis relatively to a primary axis. The distance may bedefined either by a constant value in local y− and z−direction or dependend ona axis variable specified with GAXV.

It is further possible to specify an offset for point and group numbers used inGAXP placements.


4−17Version 12.01

See also: GAX GAXP GAXS

4.10. GAXV − Variables along axisÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAXV


ID

NAME

S

V

DV

TYPE

Id of axis

Name of variable

Value / formula for station

Value / formula for Variable

Value / formula for derivative of Variable

Properties of data pointPOLY Value only D− Inclination beforeD+ Inclination behindD* Inclination before and behindSPLI Intermediate spline pointFUNC funktion

Lit4

Lit16

Lit20

Lit40

Lit40

LIT

*

!

0.0

0.0

0.0

POLY

In SOFiMSHC an arbitrary number of additional variables can be defined alonga geometry axis, which can be used, for example, to define varying cross sectionsor to describe the shape of a secondary axis. A variable distribution can be eitherdefined by a number of base points and tangent directions which are interpolatedor directly by entering a formula expression at V.

Following example shows the definition of a quadratic parabola by three basepoints. The point in the middle is assigned a horizontal tangent and the type ’D*’,which ensures that both sections on the left and the right hand side of the pointare connected horizontally:

GAXV AX1 NAME VAR2 S 0.0 V +3.0GAXV AX1 NAME VAR2 S 25.0 V −7.0 DV 0.0 TYPE D*GAXV AX1 NAME VAR2 S 50.0 V +3.0

The same result could also be obtained by entering one single formula expres-sion:


Version 12.014−18

LET#S_ACT 0GAXV AX1 VAR2 S 0 V ’=#S_ACT*(#S_ACT−50)/62.5+3’ TYPE FUNC

It is important to note, that the formula expression, which is to be evaluated dy-namically, has to be specified within apostrophes and with a leading ’=’. The ex-pression is valid from the start−parameter given at S (here: S=0.0) until the nextbase point of the variable or, if no additional record GAXV is given, until the endof the axis. The control variable must always be named by #S_ACT and must alsobe defined prior to its first usage.


4−19Version 12.01

See also: GARA GARC GARS

4.11. GAR − Geometric surfaceÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GAR


NOTYPE

Area identifierType of area

DEL deletes given recordRuled surfaces

PLAN planar surfaceROTA surface of revolutionSWEE sweep surface

Coons Patches:BLIN bilinear Coons PatchCOON bicubic Coons Patch

Freeform−surface:SPLI bicubic interpolation of pointsNURB NURB control points

Lit4LIT

!*

DEGUDEGV

Degree of Nurb in u directionDegree of Nurb in v direction

−−

**

TITL Designation Lit32 −

This record GAR defines a raw geometric surface without any structural informa-tion. This surface can then be referenced as ’background geometry’ by a structu-ral area SAR or can be used to create an intersection curve with another surface,for example.

The type of the geometry to be created can be set at parameter TYPE. Thegeometry itself is then defined using one of the following records:

• GARA: Definition of rotational and sweep−surfaces (default: ROTA)

• GARC: Definition of so−called Coons Surfaces (default: BLIN)

• GARS: Definition of a freeform surface using interpolation points orNURBS control points (default: SPLI)


Version 12.014−20

See also: GAR GAX

4.12. GARA − Plane, rotational andsweep surfaces


GARA


GID1GID2

Ident of first generating axisIdent of second generating axis

Lit4Lit4

−−

XYZNXNYNZ

UMINUMAXVMINVMAX

Reference point

Direction vector

Start parameter in meridian direc. (GID1)End parameter in meridian directionStart angle of rotationEnd angle of rotation

[m]1001

[m]1001

[m]1001

−−−

−−−−

0.00.00.0***

0.*0.*

TITL Designation Lit32 −

Using this record GARA planar, rotational or sweep−surfaces can be defined:

PLAN: Planar Surface

A plane is defined by a point in space (X,Y,Z) and a normal vector (NX,NY,NZ).In order to avoid numerical problems, the dimensions of the plane should be re-stricted to the requred extensions using the parameters UMIN to VMAX. If no si-zes are specified, a default size of −100 to +100m is set in both directions.

ROTA: Surface of revolution

A geometric curve GID1 is rotated about a straight axis in space. The rotation axisis defined by a point at X,Y,Z and a directionvector at NX,NY,NZ.The parameters UMIN and UMAX define the extends of the surface in meridiandirection along the generating curve GID1. If nothing is given, the whole curveGID1 is taken.The extend of the rotation angle in degree is defined using the paramters VMINand VMAX. If nothing is given, the parameters default to an angle from 0 to 180degree.


4−21Version 12.01

Important: In order to avoid ambiguity in numerical operations, surfaces of revolu-tion should never be defined as closed surface with a rotation angle from eg. 0to 360 degree. In these cases it is recommended to create two halfshells withangles from 0 to 180 degree and 0 to −180 degree respectively.

SWEE: Sweep−Surface

A curve GID1 is swept along a so called trajectory curve GID2. Instead of the tra-jectory curve, a direction vector can be given at NX,NY,NZ along which the gener-ating curve GID1 is moved.The parameters UMIN and UMAX define the extend of the surface along the gen-erating axis GID1. If nothing is given here, the whole curve is used.The parameters VMIN and VMAX define the range on the trajectory axes or thelength on the directon vector respectively.


Version 12.014−22

See also: GAR

4.13. GARC − Coons surfaceÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GARC


NU0NU1NV0NV1XUV1YUV1ZUV1 ...XUV4YUV4ZUV4

Axis for Coons Patch bei u=0.0Axis for Coons Patch bei u=1.0Axis for Coons Patch bei v=0.0Axis for Coons Patch bei v=1.0Twist (d2x/du/dv) at corner 1

Twist (d2x/du/dv) at corner 4

lit4lit4lit4lit4***

***

!!!−

0.00.00.0

0.00.00.0

GARC defines an area by four boundary curves, where an interpolation betweenopposite curves will take place. This may yield a C0−continuity with a bilinearBLIN or a C1−continuity with a bicubic blending function COON. For the latter weneed not only properly defined local y−coordinate directions of the curves, butalso the twist values at the corners of the patch. As the twist values are not deriv-able from the curves itself, the user may specify them explicitly. If not defined, thearea will become flat at the corners. The curves may be longer than the patch re-gion as long as the intersections may be calculated properly.

u=0.0

u=1.0

v=1.0

v=0.0NU0

NU1NV1

NV0


4−23Version 12.01

See also: GAR

4.14. GARS − Area by pointsÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GARS


MNXYZW

Raster (1−max) in local u directionRaster (1−max) in local v directionPoint coordinates

Weight for NURBS

−−mmm−

**

0.00.00.01.0

This record defines points on the surface or NURBS control points of a generalfreeform surface. The points must be given in a regular a m times n grid.

Knots of a general NURBS−surface are also defined with this record in that waythat only M or N is defined, then we have:Definition of number M, value X and multiplicity W for the u direction, definitionof number N, value Y and multiplicity W for the v direction. Missing values will beinterpolated.


Version 12.014−24

This page intentionally left blank


5−1Version 12.01

5 Definition of structural elements.

This chapter describes the definition of structural elements. Structural elementsdefine the calculation system and contain a geometrical description as well asstructural information like cross−sections, material or support conditions whichare needed to set up the calculation model. SOFiMSHC supports structuralpoints, structural lines, structural areas and structural volumes. The structuralmodel can then be meshed to create a finite element model consisting of beam,shell and/or volume elements.

5.1. Input Records

Record Items

SPT

SPTP

SPTS

SPTH

NO X Y Z REF NREF FIX BX BY

T NX NY NZ SX SY SZ XFLG TITL

TYPE X Y REF VAL VALQ VALM GRP MNO

NO REF TYPE CP CQ CM DX DY DZ

GRP MNO AR

PRE GAP CRAC YIEL MUE COH DIL

NCS L PSKN LSKN MXSK MXPF

SLN

SLNB

SLNP

SLNN

SLNS

NO NPA NPE REF FIX SDIV GRP NCS NP

KR DRX DRY DRZ DROT EXA EYA EZA EXE

EYE EZE FIXA FIXE FIMA FIME XFLG TITL

X1 Y1 Z1 X2 Y2 Z2 R

NX NY NZ XM YM ZM X3 Y3 Z3

X Y Z W NX NY NZ

S MUL DIV DEG

GRP FIX REFT REF CA CL CD CXX CYY

CZZ DXX DYY DZZ BFIX FCTA FCTE


Version 12.015−2

Record Items

SAR

SARB

SARR

SARP

SARN

SARC

NO FIX GRP MNO MRF REF NX NY NZ

NRA QREF KR DRX DRY DRZ DROT T TX

TY TXY TT CB CT XFLG H1 H2 H3

CHK4 CHK5 CHK6 CHK7 TITL

TYPE NL NP NA NE T MNO FIX DFIX

CA CL CD

TYPE GID1 GID2 X Y Z NX NY NZ

UMIN UMAX VMIN VMAX

TYPE M N X Y Z W T

S T DEGS DEGT

TYPE NU0 NU1 NV0 NV1

SVO

SVOS

NO FIX MNO MRF TYPE TITL

NAR ACT NO T FAC0 FAC1 TFAC TFA1 TREF

PHI0 PHI DPHI REF DX DY DZ XX YY

ZZ NARA NARE MNO


5−3Version 12.01

See also: SPTP

5.2. SPT − Structural pointÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SPT


NOXYZREF

NREF

FIXBXBYT

NXNYNZ

SXSYSZ

XFLG

TITL

Point numberPoint coordinates

Relative to / projection onPT, PCYL, PPOLAX, AXYZ, AXZX, AXXYAR, ARYZ, ARZX, ARXY

Identifier of projection target

Support conditionWidth of support / mesh in local xWidth of support / mesh in local yPlate thickness if lying inside a SAR

z−axis of the local coordinate system

x−axis of the local coordinate system

Prevent automatic superposition

Title of point

−[m]1001

[m]1001

[m]1001

LIT

−/Lit4

Lit16[m]1001

[m]1001

[mm]1010

−−−

−−−

LIT

Lit32

−0.00.00.0−

−

−−−−

***

***

−

−

A structural point in SOFiMSHC is defined by its coordinates and a localcoordinate system with local x−, y− and z−axis. If not otherwise specified, thecoordinate system of the point aligned with its z−axis in gravity direction. In thecase that no point number is given, a new point with a new number will be createdonly if there is no other point at the given XYZ−position. Otherwise, the givenproperties will be merged with the existing point. One may also change thedefinition of an already existing point by entering a negative number at NO. The


Version 12.015−4

definition of a structural point may be enhanced by immediate consecutiveproperty records of type SPTP and SPTS.

Structural points can be projected onto an existing line/axis or a structural regionby specifying one of the literals AX or AR at REF and the axis or region id at NREF.Specialized options (e.g. AXXY, ARXY) allow to restrict the projection to theglobal YZ, ZX or XY−plane. For example, using REF AXXY GAX1 a structuralpoint can be projected within plan view onto the the geometric axis ’GAX1’.

In addition to projection, structural points can also be created directly on the refe-renced line/axis or surface by specifying the local parameters at SX or SX andSY respectively. If also SY and SZ are given for a structural line, the point can beplaced relatively to the line at SX with the given distance in Y− and Z−coordinates.In all cases the local coordinate system of the structural point is set according tothe coordinate system of the line or the structural region.

Coordinates of a structural point can also be defined relatively to another pointat NREF. The relative distance can be given in euclidian, cylindrical or sphericalcoordinates. Therefor, one of the following types can be set at REF:

PT euclidian (rectangular) coordinate−systemX,Y,Z relative to the reference point

PCYL cylindrical coordinate systemX = radius, Y = rotation angle (deg) , Z = height

PPOL polar coordinate systemX = radius, Y = azimut (deg), Z = polar angle (deg)

Example: SPT 5 REF PT 101 X 10.0 creates a new point with number 5 at ax−distance of 10.0m relatively to point 101.

The coordinates at XYZ are always defined relatively in the local coordinatesystem of the reference point. The new point will also get the coordinate systemof the reference point. This option is especially useful to define single structuralpoints relatively to another. Considerable more possibilities are provided by thespecial record COOR, which allows to define a user coordinate system for allgeometry input. There also cylindrical and spherical coordinate systems can bedefined.

Support conditions can be defined at parameter FIX by combining one of thefollowing standard literals (e.g. FIX PXPY):


5−5Version 12.01

PX Clamped support of displacement in xPY Clamped support of displacement in yPZ Clamped support of displacement in zMX Clamped support of rotation about xMY Clamped support of rotation about yMZ Clamped support of rotation about zMB Clamped support of warping

XP = PY + PZYP = PX + PZZP = PX + PYPP = PX + PY + PZ

XM = MY + MZYM = MX + MZZM = MX + MYMM = MX + MY + MZ + MBF = PP + MM

A preceding ”L” switches to local directions for the following Literals, a ”G”restores the global direction reference. If nothing is given, the support will bealigned according to global coordinate directions. If the literal at FIX contains thecharacter sequence ”−>”, the following number refers to the number of a coupledpoint. In this case, the referenced node will be connected with the respectivekinematic constraints. For example, a definition of PXPY−>4 sets thedisplacements in X and Y direction of the current node to those of node number4. Coupling of kinematic constraints can also be defined using additional pointproperty records SPTP. In the respective section, the reader will also find a list ofall possible coupling constraints as well as their kinematic dependencies.

Option XFLG allows to prevent the automatic superposition of the given structuralpoint with other structural elements. Following options are provided, which canalso be combined:

• ’P’ The given structural point will not be replaced by other structuralpoints.

• ’L’ The structural point will not subdivide other structural lines.

• ’A’ The structural point will not be embedded within a structural regionas constraining point.


Version 12.015−6

If this option is set, it overwrites the default setting where two points will not bereplaced if both have been created explicitly (with a positive number). The optionXFLG also applies to implicit points which had not been assigned a number.


5−7Version 12.01

See also: SPT

5.3. SPTP − Structural point propertiesÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SPTP


TYPE Type of propertySUPP Periphery of support

(column head)VOUT Periphery of haunchesPNCH Periphery of punchingKPPX, KPPY etc. coupling condition

(see explanation)

LIT !

XYREF

Local dimensionsonly SUPP/VOUT/PNCH

Reference to section number for SUPP/VOUT/PNCHcoupled strutural point

[m]1001

[m]1001

−

0.00.0−

VAL Property value (e.g. Plate thickness) 0.0

GRP Group number − 0

This record defines extended geometric properties or kinematic constraints orcoupling conditions for a structural point. Geometric properties may be definedas a centred rectangle or as a general polygonal section by referencing a crosssection in the database. A haunched region will be accounted for by a varyingthickness for the generated mesh in the vicinity of the column head. In generalthere are multiple records of type SPTP are allowed for a single structural point.

For defining kinematic coupling conditions between structural points at parameterTYPE a number of special literals are provided which allow to fix one or multipledegrees of freedom:

KPX0 Coupling of x−displacement only (ux = uxo)KPY0 Coupling of y−displacement only (uy = uyo)KPZ0 Coupling of z−displacement only (uz = uzo)

KMX Coupling of rotation about the x−axis (ϕx = ϕxo)KMY Coupling of rotation about the y−axis (ϕy = ϕyo)KMZ Coupling of rotation about the z−axis (ϕz = ϕzo)


Version 12.015−8

The three conditions KPX0, KPY0 and KPZ0 however, do not satisfy mechanicalequilibrium conditions as they do not consider the distance between the connec-ted structural points. For this reason, additional literals are provided which ac-count for the real distance between the points and which should be preferablyused in most cases:

KPPX Connection of x displacement only (see formula 1)KPPY Connection of y displacement only (see formula 2)KPPZ Connection of z displacement only (see formula 3)

Couplings can also be defined in radial and tangential direction. Radial refers tothe distance between the first and the connected point and tangential to all direc-tions perpendicular:

KPR Coupling of displacements in radial direction (see formula 18)KPT Coupling of displacements in tangential directions (see formula 19)KMR Coupling of rotations about the radial direction (see formula 18)KMT Coupling of rotations about all tangential directions (see formula 19)

A number of additional literals are provided which allow to define special bound-ary conditions or to define a combination of the above mentioned relations:

KP = KPPX + KPPY + KPPZ describes mechanically a rigid connection with hinged conditions at the reference node

KF = KP + KMX + KMY + KMZ describes mechanically a rigid connection with clamped support at the reference node

KL = KP + KMTKQ = KP + KMR

KPEX Rotation about x−axis only (see formula 7 to 9)KPEY Rotation about y−axis only (see formula 10 to 12)KPEZ Rotation about z−axis only (see formula 13 to 15)

KFEX Rotation about x−axis only (see formula 7 to 9)KFEY Rotation about y−axis only (see formula 10 to 12)KFEZ Rotation about z−axis only (see formula 13 to 15)


5−9Version 12.01

SYM Symmetry conditions about the mid−perpendicularANTI Anti−symmetry conditions about the mid−perpendicularCYCL Cyclic symmetry conditions

INTE Interpolation of displacements onlyINTF Interpolation of all deformationsINTS Special form of the interpolation for mindlin plates

The mathematical formulas mentioned previously which are used for the calcula-tion of the coupled displacement conditions are listed at the end of this section.

With the exception of KPX, KPY and KPZ all coupling conditions satisfy the mech-anical equilibrium conditions by taking the real distances between the two con-nected points into account. Mechanically they act like infinitely stiff structuralmembers and remain numerically stable when solving the finite element system.Their primary application area is the formulation of boundary conditions for platesand shells and the modelling of stiff structural parts. As the kinematic constraintsdescribe linear relationships, they are not capable to account for geometricallynon−linear effects from second or third order theory.

List of kinematic displacement relations of couplings conditions

KPPX: ux = uxo + ϕyo ⋅ (z − zo) − ϕzo ⋅ (y − yo) (1)

KPPY: uy = uyo + ϕzo ⋅ (x − xo) − ϕxo ⋅ (z − zo) (2)

KPPZ: uz = uzo + ϕxo ⋅ (y − yo) − ϕyo ⋅ (x − xo) (3)

KP: KPPX + KPPY + KPPZ

KF additionally: ϕx = ϕxo (4)ϕy = ϕyo (5)ϕz = ϕzo (6)

KPEX: uy = uyo − ϕxo ⋅ (z − zo) (7)uz = uzo + ϕxo ⋅ (y − yo) (8)

KFEX additionally: ϕx = ϕxo (9)

KPEY: ux = uxo + ϕyo ⋅ (z − zo) (10)uz = uzo − ϕyo ⋅ (x − xo) (11)


Version 12.015−10

KFEY additionally: ϕy = ϕyo (12)

KPEZ: ux = uxo − ϕzo ⋅ (y − yo) (13)uy = uyo + ϕzo ⋅ (x − xo) (14)

KFEZ additionally: ϕz = ϕzo (15)

The conditions for fixed supports PR and PT and for coupling conditions KPR andKPT in radial and transversal directions respectively as well as their counterpartsfor moments are not explicitly but implicitly defined. The programs themselvescreate an appropriate explicit form.

PR: ut ⋅ n = 0ux ⋅ dx + uy ⋅ dy + uz ⋅ dz = 0 (16)

PT: u ⋅ n = 0

uxdx

��uy

dy�� uz

dz(17)

KPR: (u−uo)t ⋅ n = 0(ux−uxo)⋅dx + (uy−uyo)⋅dy + (uz−uzo)⋅dz = 0 (18)

KPT: (u−uo) ⋅ n = 0

(uxuxo)dx

��uyuyo

dy��

(uzuzo)dz

(19)

The symmetry and anti−symmetry conditions are given in the following equationsin vectorial form. A presentation by their components is not included here:

SYM: ut ⋅ n = − uto ⋅ n

ANTI: ut ⋅ n = uto ⋅ n

In case of mesh refinement or in cases of stiff cross−girders there may arise aneed for nodes that lie between two others and depend on them. This kind of de-pendency can be described by means of interpolating couplings INT?. The follow-ing picture shows a mesh with a so−called ’hanging’ node which displacementscan be calculated by interpolating the displacements of the two adjacent nodes:


5−11Version 12.01

INTE−couplings

The INTE−coupling is a constraint with special attributes. Herein, opposite tonode to node couplings, one node (the middle node) is dependent on two othernodes. The displacements and rotations of the middle node are interpolated fromthe corresponding values of the adjacent nodes.

u0 = u1 · DD + u2 · (1−DD)

When the deflections of the outer nodes are somehow prescribed, e.g. fixed orprovided with a certain stiffness, the deflection of the middle node is prescribedin the same way too. The coupling is rigid only when both nodes can not displacerelatively to each other. A rigid body with three nodes must be described bymeans of two KP/KF couplings; the INTE−coupling can not be used in that case.

There are several variants of interpolation used by INTE−couplings, which are de-scribed in the following.

INTE Displacements: linearly interpolatedRotations: not definedApplication: mesh refinements TALPA

INTFDisplacements: linearly interpolated as in TYPE PRotations: “torsion” linearly interpolated, other rotations com−

puted from displacement differences divided by therespective node distances

Application: connection of beam elements onto disksstiff cross−girders between two supports

In the general three−dimensional case, if one draws the lines connecting the twonodes in the initial undeformed as well as in their deformed state, two rotationalcomponents are defined exactly by the secant angles of those. The third yet un-determined rotational component has the direction of the connecting line (tor-


Version 12.015−12

sion), and it is normally interpolated. The general expression is very complicated;however, INTE−couplings parallel to the axes of coordinates can be expressedby much simpler expressions, e.g.,

X = 0.Y = dZ = 0.

results in:

ϕx = � uz / d

ϕy = ϕy−m

ϕz = − � ux / d

INTSDisplacements: quadratically interpolatedRotations: linearly interpolatedApplication: mesh refinements of plates and shells

In mesh refinements of plates and shells there is a problem in coupling the transla-tional and rotational degrees of freedom. Very poor elements function with a plaininterpolation. Due to the peculiarities exhibited by the formulation of the SEPP/ASE−elements, even in its simplest form, the INTE−conditions must be accord-ingly complicated. In case of regular elements by Kirchhoff’s theory for example,a cubic interpolation of the displacements and two of the rotations must be em-ployed. Mindlin elements also work with the so−called Kirchhoff constraints. Inprinciple of course, translations and rotations are interpolated independently ofone another, yet proper additional conditions are used to make sure that the shearforce corresponds to the derivative of the moment.

A quadratic distribution of the bending deflection along with a linear distributionof the rotations can be accomplished through the introduction of an additionaltranslational degree of freedom at the middle of an element’s side. This additionaldegree of freedom can be later eliminated. This method is also employed by V−couplings. Although the formulation is consistent and leads to considerably betterresults than the older methods, it is not recommended unlimitedly. In particular,it should not be used with non−conforming elements.

The application of INTE in the direct vicinity of singularities is generally not recom-mended.


5−13Version 12.01

ÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏÏ

The support of the slab may be done by different approaches, which can be selec-ted with the number of additional asterixes “*” at FIX and the CTRL option PSUP.

no Use the value of CTRL PSUP* increase thickness for centre (CTRL PSUP 1)

= monolithic support** do not increase thickness for centre (CTRL PSUP 0)

= hinged or elastic support*** add kinematic constraints

(only for special purpose, CTRL PSUP 2 / 4)

The generation of such a mesh macro is currently only possible for supportswithin the slab and only if the central point is not to close to any other structuraledge. If this is not the case, the point will become only a single node in the gener-ated FE−mesh. This behaviour may also be enforced with definition of CTRLPSUP −1.


Version 12.015−14

See also: SPT

5.4. SPTS − Spring element at pointÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SPTS


NOREF

TYPE

Spring numbernumber of 2nd reference point

Type / direction of springCX, CY, CZ local X, Y, ZCXX, CYY, CZZ global X, Y, Z

C explicit direction (DX, DY, DZ)or direction to reference point

−_

LIT

−−

C

CPCQCM

stiffness in axial directiontransversal stiffnessrotational stiffness

[kN/m3]1097

[kN/m3]1097

[kNm/rad]1098

0.0.0.

DXDYDZ

GRPMNOAR

X−component of explicit directionY−component of explicit directionZ−component of explicit direction

group numbernumber of stress−strain curve / materialreference area

−−−

−−

[m2]1002

−−−

−−−

PREGAPCRACYIELMUECOHDIL

prestress forcespring gap (slip)spring failure loadspring yield loadfriction coefficient for lateral springcohesion value for lateral springdilatation value for lateral spring

[kN]1028

[m]1001

[kN/m3]1097

[kN/m3]1097

−[kN/m3]1097

−−−−−−−

This record defines beddings or spring elements on a structural point. For a givenstructural point SPT multiple subsequent records of type SPTS can be enteredallowing to create an arbitrary number of springs, which, for example, can be as-signed to different groups. Spring elements can be defined as beddings to a fixedsupport or relatively to another structural point.


5−15Version 12.01

The stiffness of a spring element can be basically defined with three parameters:CA to CM. The first parameter CA describes an axial stiffness along the principaldirection of the spring. The second parameter CQ describes a stiffness compon-ent acting in the whole plane perpendicular to the axial direction. Mechanically,this stiffness corresponds to two identical axial springs lying orthogonal to eachother within the plane. Since the direction of these springs inside the plane canbe chosen arbitrarily, this component is also denoted as isotropic lateral springstiffness. The third parameter CM describes the rotational stiffness about the prin-cipal spring axis.

The axial and lateral spring stiffness as well as the nonlinear parameters CRAC,YIEL and COH are given as bedding stiffness per area (e.g. kN/m/m2). These stiff-ness values will be scaled by the given reference area AR, resulting in a springelement with point support stiffness (kN/m). If nothing is given for AR the stiffnessvalues will be directly taken as point stiffness value.

A spring can have a number and can be assigned to a group. If the identifier ofa second structural point is given at REF the spring is created between the givenand the referenced structural point.

The direction of the spring can be defined as follows:

• Along the local coordinate system of the structural point

Each structural point contains a local coordinate system, which can be setexplicitly at the structural point record SPT. By setting CX, CY, or CZ atparameter TYPE, the spring can be aligned to one of this local coordinatedirections.

• Along one of the global X,Y,Z − coordinate axes

If CXX, CYY or CZZ is given at TYPE, the spring is oriented, indepenentlyof the structural point, toward one of the global X, Y, or Z− coordinate axes,respectively.

• Along an explicitly given direction vector at DX, DY, DZ

A spring can also be aligned arbitrarily by setting a direction at DX, DY, DZ.


Version 12.015−16

• Distance between point and reference point

For a spring, connecting the point with a reference point, the direction tothe reference point is taken as axial direction in the case, that no differentsettings have been given.

In the case that no direction is given at all, the spring is aligned with the localz−axis of the structural point.

Different stiffness values in lateral direction cannot be defined within one singlerecord of type SPTP. However, multiple records can be given in order to createsprings aligned perpendicular to each other. Using value lists, CADINP allows tohandle this case efficiently. For example: SLNS TYPE CX,CY,CZ CP 1000.0,2000.0, 3000.0 creates three orthogonal springs having each different stiffnessvalues of 1000.0, 2000.0 and 3000.0, respectively.

Using the parameter PRE, prestress can be activated within the spring. In its initialposition at rest, the spring already exerts a force or a moment (if only CM is given)into or about its direction. Prestress for the lateral component CQ cannot bedefined.

At the parameters GAP, CRAC, YIEL, MUE, COH, DIL values like crack−, yieldload or friction coefficients can be given in order to activate non−linear effects:

Prestress:The failure and yield loads are shifted by the amount of the prestress.

Gap:The spring transmits forces along its axis only after its deformation has ex-ceeded the gap.

Failure load:Upon reaching the failure load the spring fails in both the axial and the lat-eral direction. The failure load is always a tensile force or a positive mo-ment.

Yield load:Upon reaching the yield load, the deformation component of the spring in-creases in its direction, without a corresponding increase of the springforce.


5−17Version 12.01

Friction coefficient:If a friction coefficient and/or a cohesion are input, the lateral spring can notsustain forces greater than:

Friction_coeff. · Compressive_force + Cohesion

For large tension forces or a failed axial spring (CRAC) the lateral forceacts only if 0.0 has been input for both the friction coefficient and the cohe-sion.

General non−linear effects can be defined by referencing an arbitrary stress−strain curve or a non−linear material at MNO. The number at MNO then refer-ences a work law or material which has been defined prior in AQUA. In the casethat a material is being referenced, an influence area should be given at AR whichscales the material bedding values accordingly in order to create the spring con-stants:

CP := Cb⋅AR [kN/m = kN/m2⋅m2/m]CQ := Cq⋅AR

In the case that a dilatation value (DIL) is defined, a displacement in the lateraldirection will generate a component in the axial direction.


Version 12.015−18

See also: SPT

5.5. SPTH − Halfspace pile at pointÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SPTH


NCSL

Cross−section numberLength of pile in gravity direction

−[m]1001

00.0

PSKN

LSKNMXSKMXPF

percentage of total pile load transfered byskin frictionpercentage of inactive skin lengthmaximum load transferable by skin frictionmaximum load transferable in pile foot

−−

[kN]1151

[kN]1151

50

−−

This records defines properties of a halfspace−pile connected to the previouslygiven structural point. Information about the parameters can be found in the ma-nual of HASE in record PILE.


5−19Version 12.01

See also: SLNB SLNP SLNS SPT

5.6. SLN − Structural lineÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SLN


NONPANPEREFFIXSDIV

Line numberPoint at start of linePoint at end of lineReference to a geometry at GAXBoundary conditions along the lineMesh density for a subdivision

−−−

−/LITLit16

[m]1001

−−−−−−

GRPSTYPSNONPKRDRXDRYDRZDROTEXAEYAEZAEXEEYEEZEFIXAFIXEFIMAFIME

XFLG

Group numberElement type, subdivisionNumber of cross sectionNumber of bore / bedding profileDirection identifier orexplicit direction vector of the localbeam coordinate system

Additional rotation about beam axisEccentricity in global coordinatesat start

Eccentricity in global coordinatesat end

Hinge conditions at startHinge conditions at endHinge conditions at all interior startsHinge conditions at all interior ends

Prevent automatic intersection

−LIT

−/Lit12

LIT−−−

deg[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

−/Lit16−/Lit16−/Lit16−/Lit16

LIT

−−−−−0.0.0.0.0.0.0.0.0.0.−−−−

−

TITL Title of Line Lit32 −

This record defines a structural line. Start and end points of the line may be spe-cified explicitly by referencing structural points which have been previouslydefined at SPT or implicitly using subsequent geometry records of type SLNB / SLNP . In the latter case, it will be checked if a structural point already exists at


Version 12.015−20

the respective end coordinate of the line and creates one if not. If no number isgiven for the structural line at NR, a new number will be assigned automatically.

By entering a negative number at NO the properties of a previously defined struc-trual line can be changed. For example: SLN −10 SNO 1 changes the cross−sec-tion number of line no 10. All other properties of the line remain unchanged. If anadditional property record of type SLNS is given when a line is being changed,it will be added to all previously defined property records of the line.

The geometry of a line can be described by adding subsequent records of typeSLNB or SLNP. SLNB allows to define straight lines and circular arcs whereasSLNP is used to create freeform curves. A third possibility is to set the geometryby referencing a previously defined axis GAX at REF. If no geometry is definedat all, a straight line between start− and endpoint is assumed.

All beam elements which will be created along the structural line have a local co-ordinate system assigned whose local x−axis is always aligned parallel to thestructural line. For curved edges this coordinate system may vary along the line.This local beam−coordinate system determines the orientation of cross sectionsand, if not otherwise specified at record SLNS, the direction of local supports andkinematic couplings. The orientation of the local z−axis perpendicular to the linecan be specified using special literals at KR or directly by entering direction vectorat DRX,DRY,DRZ. Following possibilities exist:

• Explicit direction vector at DRX,DRY,DRZ

The entries DRX,DRY,DRZ define a direction vector according to which thelocal z−axis of the beam coordinate system is aligned. The local x−axis (=tangent) of the coordinate system remains always parallel to the structuralline.Which of the two local directions y or z is aligned is basically determinedby the global variable CTRL LOCA. If nothing is given, the local z−axis isused.

• Predefined directions using a literal at KR

Instead of an explicit direction, the user may also enter one of the literalsPOSX, POSY, POSZ, NEGX, NEGY or NEGZ at KR in order to align thelocal x−axis with one of the given global directions.Moreover, the local x−axis may also be aligned within one of the global co-ordinate planes by entering:


5−21Version 12.01

KR = XY, YX: align x within global XY−plane in X− resp. Y−directionKR = YZ, ZY: align x within global YZ−plane in Y− resp. Z−directionKR = ZX, XZ: align x within global ZX−plane in Z− resp. X−direction

• Align to other structural element KR {PT,LN,AR} NO

Using this option, the local z− (or y−) axis of the beam elements along thestructural line can be aligned towards another structural element. Fol-lowing possibilities exist:

KR PT: align towards a structural pointKR LN: align towards a structrual lineKR AR: align towards a structural area

The direction of each beam element is determined individually by calcu-lating the projection onto the referenced structural item. If no projectionexist, i.e. the distance is zero, the coordinate system of the referenced itemis taken directly.

• additional rotation about beam axis at DROT

By indicating an angle for DROT the local coordinate system will be addi-tionally rotated about the beam axis. The angle is to be given in degrees.

In order to define boundary or coupling conditions at FIX the same literals can beused as for the definition of boundary conditions on structural points at SPT. Ifthe Literal at FIX contains the character string ”−>”, the following number istreated as the number of a reference line. Referenced lines will get the same num-ber of subdivided elements whereas the pairwise corresponding nodes will beconnected with kinematic constraints. An input PZ−>4, for example, sets all nodaldisplacements in z−direction to those of reference line nr 4. For the definition ofmore advanced coupling and interface conditions a special record SLNS isprovided, which may be used better.

SDIV defines the maximum edge−length of beam or plane elements to be createdalong the structural line. If no mesh size is given at SDIV, the size of possibly con-nected structural regions or the global setting at CTRL HMIN is taken.

A set of literals at parameter STYP allows to control the generation of beam ele-ments and the intersection behaviour of the structural line:


Version 12.015−22

• Type of beam elements to be generated:

’B’ = beam with reference axis (section at origin)’N’ = centric beam (section at barycenter)’T’ = truss element’C’ = cable element

• Kind of subdivision applied:

’E’ = sudivide structural line in beam elements (Default)’X’ = subdivide in elements without connecting the elements with a surrounding FE−mesh’Y’ = create one single element with beam sections’Z’ = create one single element without beam sections

If the type of beam element is set to ’truss−element’ (STYP ’T’) SOFiMSHC auto-matically activates option ’Z’ = ’create one element without sections’. In case ofcable elements (STYP ’C’) the intersection with other structural elements is pre-vented by default (see option XFLG) in addition. In both cases these default set-tings can be overwritten by the user if any other option is given at STYP.

Beams with linearly varying sections can be defined by entering two section num-bers separated by a dot at NCS (i.e. ’1.2’ ). The sections at internal element nodeshave to be created by running AQUA afterwards with option INTE 0.

Hinge conditions at the structural line can be specified for the start and the endpoint individually using FIXA and FIXE. In addition to that, the options FIMA, FIMEallow to define hinge conditions at nodes created in the internal of the structuralline (e.g. hinged chain). Following literals are possible:

N,VY,VZ normal−, transversal forcesMT,MY,MZ momentsMB warpingPP = NVYVZMM = MTMYMZMB

The literals always define the hinge condition which is to be released. They canalso be arbitrarily combined (e.g. MYMZ), in order to release multiple degrees offreedom. If a number is given at FIXA to FIME non−linear force−work laws canbe referenced (see AQUA: record SFLA).


5−23Version 12.01

Option XFLG allows to prevent the automatic intersection of the given structuralline with other structural elements. As an example, it might be possible to definetwo parallel structural lines at the same position without having SOFiMSHC to re-place one of the lines during the automatic intersection process. In detail, the fol-lowing options, which can also be combined, are provided at XFLG:

• ’P’ The given structural line will no longer be subdivided by structuralpoints.

• ’L’ The structural line will no longer be subdivided nor replaced by otherstructural lines.

• ’A’ The structural line will no longer be subdivided by crossing structuralareas and will also not be embedded within a structural region asconstraining line.

Please note that the above mentioned options only apply to the internal of thestructural line. They will not apply to the endpoints. In the case that the user alsowants to prevent intersection at the endpoints, he has to create the endpoints withthe respective settings explicitly.


Version 12.015−24

See also: SLN SPT

5.7. SLNB − Straights and circular arcsÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SLNB


X1Y1Z1X2Y2Z2RNXNYNZXMYMZMX3Y3Z3

Coordinates of startpoint

Coordinates of endpoint

RadiusNormal direction of circle plane

Coordinates of center

Third point on arc

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

−−−

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

0.00.00.00.00.00.0−−−−−−−−−−

Records of type SLNB can be used to define straight lines, circles and cicular arcsin space. Records of this type always refer to the most recently defined structuralline at SLN. Multiple segments are allowed to be entered in order to definepolycurves. For the definition of a single segment following possibilities exist:

• A straight line is defined by its start− and endpoint at (x1,y1,z1) and(x2,y2,z2).

• A full circle can be defined by its center (xm,ym,zm), the radius and the nor-mal on the circular plane (nx,ny,nz).

• A circular arc can be defined by its start− and endpoint at (x1,y1,z1) und(x2,y2,z2), a radius and the normal or by entering the start−, the endpointand the center.

• In addition, circular arcs can also be defined by entering three points on thearc. (x1,y1,z1) und (x2,y2,z2) describe the start− and the endpoint, (x3,y3,z3)a third point on the arc.


5−25Version 12.01

See also: SLN SPT

5.8. SLNP − 3D curve point dataÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SLNP


XYZ

WS

DXDYDZ

NXNYNZ

TYPE

3D coordinates

Weight of control point (NURBS)Station on point (for interpolation)

Tangential direction (Type HINT)

Direction of local z−axis

Type of curve

[m]1001

[m]1001

[m]1001

−−

−−−

−−−

0.00.00.0

1.0−

−−−

−−−

Structural lines with arbitrary freeform geometry can be defined with SLNP usingcharacteristic data points. Each record SLNP defines one coordinate in 3D. Theyalways refer to the previously defined structural line at SLN. Following types ofcurves are supported:

• POLY: Interpolation as polygonal sequenceThe given points will be interpolated as polygonal sequence.

• SPLI: Spline interpolationThe given datapoints will be interpolated using a cubic B−Spline. The inter-polation is carried out curvature continuous at the definition points (C2−continuity).The parametrisation (chainage) of the curve can be set explicitly at eachdatapoint using the parameter S. If no parameter values are given,SOFiMSHC assigns a parametrisation automatically. For this, specialtechniques are applied which minimize possible oszillations between un-equally distributed definition points.


Version 12.015−26

• HINT: Hermite interpolationThe given datapoints will be interpolated using piecewise cubic B−Splinesegments. The interpolation is carried out tangentially continuous at thedefinition points (C1−continuity).Using the parameters DX,DY,DZ, the tangential direction at certain pointscan be defined explicitly by the user. Similar to the spline interpolation, theparametrisation (chainage) along the curve can be set using the parameterS.

• NURB: NURBS−curveA NURBS (Non Uniform Rational B−Spline) curve can be defined by ente-ring the euclidian coordinates of the control−points at X,Y,Z. If weights <>1.0 are given, the input results in a true ’rational’ NURBS curve, which, forexample, allows to describe also circle and ellipses. The degree of theNURBS curve can be set in record SLNN, when defining the knot vector.


5−27Version 12.01

See also: SLN SLNP

5.9. SLNN − Knot value of aNURBS−curve

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SLNN


SMULDEGR

Knot valueMultiplicitydegree of Nurbs

−−−

!1*

Records of type SLNN are used to define the knot vector of NURBS−curves orto explicitly set the parametrization of interpolation curves. For each knot valueof a NURBS or parameter value a single record SLNN is to be entered whichrefers to the previously defined structural line at SLN. Multiple knot−values (e.g.at the ends of a curve) can be entered in a single record using multiplicities > 1.Within the first record the polynomial degree of a NURBS−curve can be set usingparameter DEGR.

When NURBS−curves are defined in SOFiMSHC knot vectors must always begiven with multiple knots at the ends (“clamped ends”) with a multiplicity equal tothe degree of the curve. In the case that no knot−vector is given by the user, auniform distribution is assumed internally.

When defining interpolation curves, the local parameter values at each inter-polation point can also be set explicitly using this record. This can be, for example,necessary when one wants to keep the parametrization between different curvesconsistent. In general cases however, it is better to not set these values alwayssince SOFiMSHC optimizes the parametrization by default such that ozillationsbetween the different interpolation points are minimized.


Version 12.015−28

See also: SLN SLNP

5.10. SLNS − Supports and kinematiccouplings on a SLN


SLNS


GRPFIXREFT

REFMNO

CACLCD

KRDRXDRYDRZDROTD

BFIXFCTAFCTE

Group number of the supportBoundary / coupling conditionsType of support / bedding

>FIX absolute>SPT relative to a point>SLN relative to a line+SAR, −SAR, *SAR:

interface element

Number of referenced element Material number

AUTO detect automatically

Axial beddingLateral (transversal) beddingTorsional bedding

Direction specifierExplicit direction of support/bedding

Rotation about beam axisDistance to interface element(REFT SAR)Width of supportFactor for beddings at startFactor for beddings at end

−Lit28LIT

−−/LIT

[kN/m3]1097

[kN/m3]1097

[kN/rad]1099

−/Lit4−−−

deg[m]1001

[m]1001

−

*−

>FIX

−−

0.0.0.

−0.0.0.0.0.

1.01.01.0

This record defines boundary conditions, elastic supports, kinematic couplings orspecial interface elements for the most recently defined structural line at SLN. Fora given structural line, multiple records of type SLNS can be given, e.g. in orderto define elastic boundary conditions and fixed supports along the line in parallel.


5−29Version 12.01

5.10.1. Supports and coupling conditionsSupports or coupling conditions along the structural line can be defined at para-meter FIX where the following set of literals is possible:

PX Clamped support of displacement in xPY Clamped support of displacement in yPZ Clamped support of displacement in zMX Clamped support of rotation about xMY Clamped support of rotation about yMZ Clamped support of rotation about zMB Clamped support of warping

XP = PY + PZYP = PX + PZZP = PX + PYPP = PX + PY + PZ

XM = MY + MZYM = MX + MZZM = MX + MYMM = MX + MY + MZ + MBF = PP + MM

The above given literals can be combined in order to fix multiple degrees of free-dom (e.g. FIX PPMX). Local directions can be fixed by preceding a ’L’ (e.g.LPXPY). Additional information about setting support conditions can be found atrecord SPTP of the structural point. It is also possible to define multiple recordsof type SLNS for a single structural line. If there are multiple support and/or coup-ling conditions given, they will be superimposed accordingly.

Local support conditions (e.g. LPZ) are primarily aligned according to the localcoordinate system of the beam elements created along the structural line. Thislocal orientation, however can also be set separately for this record using theparameters KR to DROT. The possibilities therefore are described in detail at re-cord SLN.

In case that a number is given at REF a kinematic coupling is created to the refe-renced element. All coupled degrees of freedom of the structural line are set equalto those of the reference element. A coupling condition can be defined to a struc-tural point (REFT >SPT) or a structural line (REFT >SLN). In the latter case, both


Version 12.015−30

the given and the referenced line will be subdivided equally and the respectivenodes will be connected with the given condition. Kinematic couplings of warpingtorsion (MB) between two structural lines are not allowed.

Couplings between structural lines always satisfy the mechanical equilibriumconditions by taking the real distances between the referenced nodes into ac-count. The displacement conditions are thus calculated by:

PX: ux = uxo + ϕyo ⋅ (z − zo) − ϕzo ⋅ (y − yo)

PY: uy = uyo + ϕzo ⋅ (x − xo) − ϕxo ⋅ (z − zo)

PZ: uz = uzo + ϕxo ⋅ (y − yo) − ϕyo ⋅ (x − xo)

Above literals correspond to the literals KPPX, KPPY, KPPZ for coupling dis-placement conditions between two structural points. Mechanically, a coupling ofall displacements (FIX PP) acts like an infinitely stiff member with a rotationalhinge in the coupled nodes. If also the rotations are fixed (FIX FF = PP + MM),it acts like a rigid connection with clamped support at both ends.

5.10.2. Elastic beddings and spring elementsInstead of coupling or support conditions the given record also allows to createboundary elements with elastic bedding or spring elements along the given struc-tural line by setting one of the parameters at CA to CD or a material number atMNO. In contrast to individual spring elements, a boundary element defines acontinuous bedding along the line which interpolates the displacements betweenthe finite element nodes. If only linear parameters are given, SOFiMSHC gener-ates basically boundary elements. In case of non−linear parameters (usuallygiven by the material) or in case of coupled structural lines, spring elements willbe created along the structural line. The generation of beddings and spring ele-ments can be further controlled by setting the global parameter STEU LSUP.

Basically, a spring or a boundary element can be assigned three parameters:axial (CA), lateral (CL) and/or rotational (CD) stiffness. These three parametersalways refer to an explicit bedding or spring direction. An axial bedding acts radialinto this direction, a lateral (or transversal) bedding in a plane perpendicular to itand a rotational bedding parameter creates a rotational stiffness around this dir-ection. The bedding direction can be set by the user by specifying the parametersKR to DROT. If no direction is given, the spring or boundary elements will bealigned parallel to the structural line. SOFiMSHC provides following possibilitiesfor setting directions of spring and boundary elements:


5−31Version 12.01

• Locally aligned KR LOCX, LOCY, LOCZ (only spring elements)

Spring elements can be aligned according to one of the local coordinatedirections of the structural line. Default setting is KR LOCX. In this case,the spring direction will be set parallel to the axis of the structural line.LOCY and LOCZ respectively allows to align the direction with one of thelocal coordinate axes perpendicular to the line. The local directions LOCYand LOCZ primarily refer to the local coordinate system (y− or z−axis) ofthe beam elements created along the structural line. If no beam coordinatesystem is given (e.g. line is boundary of a structural region), the directionsrefer to the coordinate system of the structural line itself.

• Additional rotation about line axis DROT (only spring elements)

In the case that an angle is given at DROT, the direction of spring elementswill be additionally rotated about the axis of the structural line.

• Oriented globally KR POSX

By setting one of the literals POSX, POSY, POSZ or NEGX, NEGY, NEGZat KR, the direction of spring or boundary elements can be set accordingto one of the global coordinate axes X, Y or Z..

• Explicit direction vector at DRX, DRY, DRZ

A vector given at DRX, DRY, DRZ allows to align spring and boundary ele-ments with an arbitrary global direction.

Similar to coupling conditions, also linear or non−linear bedding conditions canbe defined between two structural lines, if the numer of a referenced line is givenat parameter REF. In this case, the given and the referenced line will be sub-divided with the same number of nodes and spring elements created in between.If no direction is given at KR to DROT, the direction of the spring elements is setto the direction between the referenced nodes.

In the case that a material number is given at MNO, the spring constants will becalculated from the corresponding linear or non−linear elasticity properties of thematerial. BFIX can be set to adapt the material parameters to the width of the sup-port. A negative value at the bedding parameters CA to CD allows to further scalethe values calculated from the material. If the literal AUTO is set, SOFiMSHCautomatically determines the material number from the adjacent structural area.


Version 12.015−32

5.10.3. Interface−elementsThe options {+−*} SAR at REFT allow to create coupled interface elements alongthe given structural line automatically. Depending on the sub−type at SAR,SOFiMSHC creates and sets of interface edges to one or both sides of the lineand disconnects connected structural regions accordingly. The direction at DRX,DRY, DRZ or, if not given, the local z−axis of the structural line defines to whichside connected lines and regions will be disconnected. Thereby three possibilitiesexist:

+SAR: a single interface edge is created in positive z−direction−SAR: a single interface edge is created in negative z−direction*SAR: two interface edges are created in both directions.

If a distance is given at D a gap is created between the given and the interfaceline.

SOFiMSHC creates spring elements between the coupled interface edges andassigns the linear bedding parameters given at CA to CD or possibly non−linearparameters if given at the material. The direction of the spring elements is alwaysaligned perpendicular to the coupled lines.


5−33Version 12.01

See also: SARB SPT SLN

5.11. SAR − Structural areaÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SAR


NO

FIXGRPMNOMRFREFNXNYNZ

Area number/ Type identifierPROP attribute regionVOID opening

Boundary condition within the areaGroup number of elements in areaMaterial number of QUADs in areaMaterial number of reinforcementGeometric reference on area SARVector defining the upward direction ofthe area

−/LIT

LIT8−−−

LIT4−−−

0

*000−***

NRA

QREF

KRDRXDRYDRZDROT

Formulation of elements (Bitmask) 0 geometry only +1 plate action +2 membrane action +4 in−plane bending

Reference for elementsCENT centeredABOV in negative z directionBELO in positive z direction

Direction identifier orexplicit direction vector of the localelement coordinate system

see remarksRotation angle

−

LIT

LIT/−−−−

[deg]

0/7

CENT

*−−−

0.0


Version 12.015−34


TTXTYTXYTTCB

CT

Constant thickness overrideOrthotropic thicknessOthotropic thicknessOrthotropic thickness crossOrthotropic thickness torsionFactor (negative) or bedding modulus fornormal subgrade beddingFactor (negative) or bedding modulus fortransverse subgrade bedding

[mm]1010

[mm]1010

[mm]1010

[mm]1010

[mm]1010

[kN/m3]1097

[kN/m3]1097

*TTTT−1

−1

MCTL

H1H2H3

XFLG

TITL

Meshing control+1 create regular mesh

if possibleMesh density:− for the whole region− at points inside the regionMinimum thickness of elements withinthe structured boundary layer mesh de-fined with DFIX (−> SARB)

Disable automatic intersection

Title of region

[m]1001

[m]1001

[m]1001

LIT

Lit32

0

−−−

−

−

The given record defines a structural area, a two−dimensional arbitrarily shapedregion which can be meshed with triangular or quadrilateral elements. If no identi-fier NO is given, SOFiMSHC assigns one automatically. A negative identifierchanges the existing definition of a previously defined record.

Two special literals (PROP, VOID) indicate that the record defines an attribute re-gion or an opening instead of a regular area. These special type of regions canbe placed arbitrarily within the model on top of other surfaces in order to changeselected properties locally or to create openings. They will not be meshed forthemself. SOFiMSHC intersects these regions geometrically with other structuralregions and changes the given properties in the intersected part or cuts out anopening respectively.

In addition to changing the properties the elements within an attribute region canalso be assigned to a secondary group (see record GRP). For this the secondarygroup identifier, given as text string of at most four characters, has to be set at


5−35Version 12.01

parameter GRP. In this case, all elements remain in the primary group defined forthe original structural area and will be additionally assigned to the secondarygroup of the attribute region.

The shape of a structural region is defined by its boundary and possibly a geomet-ric surface description. A valid region requires at least one closed loop of outerboundary curves which are defined by following SARB records. Inner boundariesmay be added to create openings. For more complex geometric shapes an addi-tional surface definition is needed in order to describe the geometry inside theouter boundary. This geometry can be either defined by referencing a GAR recordat REF or by adding succeding SARP records describing points on the surface.In most cases however, an explicit geometry is not necessary as SOFiMSHC de-termines it automatically on basis of the boundary description.

The orientation of a structural region is basically defined by specifying a normaldirection at NX,NY,NZ. This direction defines the local z−axis of all plane ele-ments created on the structural region, which are oriented to the opposite side ofthe normal. It can be entered only approximately by the user, only specifying theside as SOFiMSHC calculates its exact direction according to the given geometryafterwards.

The orientation of the elements within the structural region can be specified bydifferent methods. By default, the local x−axis of the plane−elements will bealigned:

• Explicit direction vector at DRX,DRY,DRZ

A direction vector at DRX, DRY, DRZ defines a direction to which the localx−axis of all plane elements created on the structural region will be aligned.This direction must not be defined perpendicular to the surface, as no uniqedirection can be determined in this case then.By setting one of the literals RADI or TANG at KR it can be further specifiedwhich of the two local coordinate axes x or y is to be aligned.

• Predefined directions using a literal at KR

Instead of an explicit direction, the user may also enter one of the literalsPOSX, POSY, POSZ, NEGX, NEGY or NEGZ at KR in order to align thelocal x−axis with one of the given global directions.Moreover, the local x−axis may also be aligned within one of the global co-ordinate planes by entering:


Version 12.015−36

KR = XY, YX: align x within global XY−plane in X− resp. Y−directionKR = YZ, ZY: align x within global YZ−plane in Y− resp. Z−directionKR = ZX, XZ: align x within global ZX−plane in Z− resp. X−direction

• Align to other structural element KR {PT,LN,AR} NO

Using this option, the local z− (or y−) axis of the area elements on the struc-tural region can be aligned towards another structural element. Followingpossibilities exist:

KR PT: align towards a structural pointKR LN: align towards a structrual lineKR AR: align towards a structural area

The direction of each area element is determined individually by calcu-lating the projection onto the referenced structural item. If no projectionexist, i.e. the distance is zero, the coordinate system of the referenced itemis taken directly.

• additional rotation about beam axis at DROT

By setting an angle for DROT the local coordinate system of each planeelement will be additionally rotated about its local z−axis.

The thickness of the elements in a structural region can be defined by setting theparameter T. If no thickness is given, it will be set to a constant value of 1.0 m. Inaddition to a constant distribution of the thickness, SOFiMSHC also allows todefine varying thicknesses within a region. Therefor two possibilities exist:

• Thickness at boundary edges in record SARB:By setting the thickness value at the outer boundary edges of a region, avarying thickness can be defined.

• Thickness at structural points within the region:For this, structural points with thickness properties (SPT ... T) can bedefined within or on the boundary of the region in order to describe a vari-able thickness distribution. Since one of these points may be shared bymultiple structural regions, the region thickness value at SAR must be setexplicitly to T=0.0 in order to activate this setting. Only structural points withno additional geometric information like column sizes etc. will be con-sidered in calculating the thickness distribution.


5−37Version 12.01

In both cases a least square method is applied, which interpolates the thicknessvalues at the support points or lines. In most cases this interpolation reduces toa planar distribution of the thickness values across the region, but may also behigher polynomial in the case that a higher number of support points is given.

Different stiffnesses in different local directions can be defined by setting ortho-troptic thickness values (TX, TY, TXY, TT). An average thickness T should begiven which will is used for calculating masses etc.

Meshing of the region can be controlled using a general parameter and differentdensity values. By setting MCTL to 1 SOFiMSHC tries to create a regular meshon structural regions with 4 boundary edges. The structured mesh is created aslong as the ratio of edges and angles corresponds approximately to a rectangularshape. H1 changes the density of the mesh within the region to a value differentto the global setting in CTRL HMIN. The value given at H1 defines the maximumlength of an element edge. Additionally, H2 can be set to create refinementsaround structural points inside the region.

Option XFLG allows to prevent the automatic intersection of the given structuralregion with other structural elements. The following options are provided, whichcan also be combined:

• ’P’ Structural points will no longer be automatically added asconstraining points to the region.

• ’L’ Other structural lines will no longer be automatically added asconstraining lines to the region.

• ’A’ The structural region will not be intersected with other structural re-gions. I.e. no intersection lines will be created automatically. Two structuralregions can be placed parallel on top of each other without warning.

Please note that the above mentioned options only apply to the internal of thestructural region. They will not apply to edges and points on the boundary. In thecase that the user also wants to prevent intersection on the boundary, he has tocreate the lines and points with the respective settings explicitly.

Independantly from the settings in XFLG it will always be possible to add singlestructural points and lines as constraining points and lines explicitly to the regionusing the command SARB CONS. Contrary to the default behaviour ofSOFiMSHC, this allows to add only a selection of structural elements asconstraints to a region.


Version 12.015−38

See also: SAR SLN

5.12. SARB − Structural areaboundaries and constraints


SARB


TYPE Type of boundaryOUT outer boundaryIN inner boundaryCONS inner constraint

LIT OUT

NLNP

NANE

T

Number of a geometric lineNumber of a geometric point

number of start pointnumber of end point

Thickness of the area in this boundary

−−

−−

[mm]1010

00

**

*

MNOFIXDFIXCACLCD

Material number of the boundaryHinge condition of boundaryDistance to boundaryAxial beddingLateral beddingTorsional bedding

−LITm

[kN/m2]1096

[kN/m2]1096

[kNm/m]1099

0−0000

This record describes one single edge of an outer or inner boundary of a preced-ing structural region defined at SAR. A valid structural region requires at least oneclosed loop of outer boundary edges but may also have a number of inner bound-aries to describe openings or constraining edges. The edge can be given as refer-ence to a structural line SLN or can be established directly by adding subsequentSLNB or SLNP records.

In the case, that no outer boundary is explicitly given for a structural area,SOFiMSHC creates the edges on the boundary automatically on basis of the un-derlying geometric surface definition, if one exist. This option is especially helpfulwhen defining rotational (SARR) and freeformsurfaces (SARP).

The edges of the boundaries can be entered in any sequence and orientation.SOFiMSHC sorts and connects the edges, provided that common end pointsexist and a closed sequence of edges can be found.


5−39Version 12.01

Additional point or line constraints in the interior of the domain may be defined forsupports, columns or other selected points using TYPE CONS. As SOFiMSHChowever, automatically incorporates points and lines lying inside a region as con-straint, there is usually no need for this option. Only in cases, where the automaticdetection fails, it can be useful to add points or lines as constraints explicitly.

For boundary edges and constraining points a thickness may be set at T in orderto define a varying thickness distribution over the structural region. The thicknessis approximated between the given points and lines using a least squaresmethod. Depending on the number of definition points linear and higher polyno-mial distributions of the thickness are possible. If the thickness is given at bound-ary edges, the general thickness of the region at SAR must be set explicitly to ’0’.

Hinge− and bedding conditions can be defined for outer and inner edges. Hingeconditions are defined at FIX, where the literals PX, PY, PZ, MX, MY, MZ whichcan also be combined are possible and which defines the respective local degreeof freedom to be released. In order to define bedding conditions on the boundary,linear bedding constants can be given at CA, CL and CD for axial, transversal androtational bedding or a material at MAT which allows to define also non−linearconditions. When boundary conditions are defined, additional edges will be cre-ated in the interior of the region and connected with the respective boundary. Ifa distance is given at DFIX, these internal edges will be additionally set off witha small gap to the interior of the region.


Version 12.015−40

See also: SAR

5.13. SARR − Rotational and sweepsurfaces


SARR


Type

GID1GID2

XYZNXNYNZ

UMINUMAXVMINVMAX

Type of Structural surface geometryROTA Surface of revolutionSWEE Sweep−surface

First generating curveSecond generating curve

Reference point

Direction vector

Start parameter in u−directionEnd parameter in u−directionStart parameter in v−directionEnd parameter in v−direction

Lit4

−/Lit4−/Lit4

[m]1001

[m]1001

[m]1001

−−−

−−

−/[deg]−/[deg]

ROTA

*−

0.00.00.0***

**0.*

The given record SARR defines the geometry of rotational or sweep−surfaces.The record is a property record and refers to the directly preceding definition ofa structural area SAR. Only one record SARR is allowed or each structural area.

The following types of geometry can be described with this record:

ROTA: Surface of revolution

A given structural line or geometric curve GID1 is rotated about a straightaxis in space. The rotation axis is defined by a point at X,Y,Z and a direc-tionvector at NX,NY,NZ.The parameters UMIN and UMAX define the extends of the surface in me-ridian direction along the generating curve GID1. If nothing is given, thewhole curve GID1 is taken.The extend of the rotation angle in degree is defined using the paramters


5−41Version 12.01

VMIN and VMAX. If nothing is given, the parameters default to an anglefrom 0 to 180 degree.

Important: In order to avoid ambiguity in numerical operations, surfaces ofrevolution should never be defined as closed surface with a rotation anglefrom eg. 0 to 360 degree. In these cases it is recommended to create twohalfshells with angles from 0 to 180 degree and 0 to −180 degree respec-tively.

SWEE: Sweep−Surface

A structural line or geometric curve GID1 is swept along a so called traject-ory curve GID2. Instead of the trajectory curve, a direction vector can begiven at NX,NY,NZ along which the generating curve GID1 is moved.The parameters UMIN and UMAX define the extend of the surface alongthe trajectory curve GID2 or the direction vector, respectively. If nothing isgiven here, the whole curve or the length of the direction vector is used.The parameters VMIN and VMAX define the extend of the surface alongthe generating curve GID1.

In general cases, there is no need to define the boundary edges of the structuralarea explicitly, when rotational or sweep surfaces are defined with this record.SOFiMSHC creates the edges automatically at the boundary of the geometry sur-face. Only in cases if openings or constraining edges should be defined or theboundary of the structural area does not coincide with the extends of the geome-tric surface, the boundary edges have to be defined explicitly using records oftype SARB.


Version 12.015−42

See also: SAR, SARN

5.14. SARP − 3D Surface data pointÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SARP


TYPEMNXYZWT

Type of data pointPosition in u−direction {1,...}Position in v−direction {1,...}X−coordinateY−coordinateZ−coordinateWeight of control−point (TYPE NURB)Thickness of plate at point (currently notsupported)

Lit−−

[m]1001

[m]1001

[m]1001

−[mm]1010

−!!0.0.0.1.0−

With records of type SARP an arbitrary freeform surface geometry can be definedfor a preceding structural region at SAR. A single record SARP describes onepoint on the surface. The points will be usually given in a m x n−grid like pattern.

Depending on the parameter TYPE, following types of surface geometries can bedefined:

SPLI: Bicubic interpolation

The given data points will be interpolated by a bicubic spline surface. Thepoints must be given in a m x n−grid like pattern.

NURB: Nurbs surface

The given data points correspond to the control points of a NURBS sur-face. The points must be given in a m x n−grid like pattern. In order to de-scribe non−rational NURBS−surfaces (e.g. rotational or spherical sur-faces), each point can also be assigned a weight W<>1.0. Additionalinformation about the definition of NURBS curves and surfaces can befound in chapter 2 of this manual.

In general cases, there is no need to define the boundary edges of the structuralarea explicitly, when a freeform surface geometry is defined with this record.SOFiMSHC creates the edges automatically at the boundary of the geometry sur-face. Only in cases if openings or constraining edges should be defined or theboundary of the structural area does not coincide with the extends of the geome-


5−43Version 12.01

tric surface, the boundary edges have to be defined explicitly using records oftype SARB.


Version 12.015−44

See also: SAR SARP

5.15. SARN − Knot value of a NURBSsurface


SARN


STDEGSDEGT

Knot value in S−directionKnot value in T−directionDegree of surface in S−directionDegree of surface in T−direction

−−−−

0.0.33

SLNN defines knot values of an arbitrary NURBS surface. A NURBS freeformsurface contains two so−called knot vectors for each parameter direction. Thisrecord defines one single entry of these lists either for the S−direction or the T−dir-ection of the parameter plane. The knot−values of a direction must be given inascending order.

A detailed description of knot−vectors of freeform curves and surfaces can befound in chapter 2 of this manual.


5−45Version 12.01

See also: SAR

5.16. SARC − Coons−Patch surfacesÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SARC


TYPE Type of surface interpolation Lit BLIN

SOFiMSHC allows to create curved structural areas only by definition of an outerboundary. In these cases − if the user has not explicitly defined the geometry ofthe area (SARR, SARP) − the surface geometry is interpolated from the pairwiseopposite boundary curves (Coons−Patch or Gordon−Surfaces). With this recordthe type of this interpolation can be set:

• BLIN: bilinear interpolationThe surface geometry is defined by linear interpolation of oppositeboundary curves

• BCUB: bicubic interpolationA bicubic interpolation also considers the inclinations of the boundary cu-ves. This allows to define surfaces with smooth transitions betweenadjacent structural areas.

SOFiMSHC automatically performs a linear interpolation of the boundary edges,if the edges are not lying within a plane and no surface geometry has been setexplicitly. Thus, this record must only be given if a cubic interpolation is desired.

In order to perform a Coons−Patch interpolation, at least three closed boundaryedges must be given. If more than four edges are given, they will be joined con-veniently.


Version 12.015−46

See also: SVOS

5.17. SVO − Structural volumeÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SVO


NO

FIX

GRPMNOMRFTYPE

TITL

Volume numberDEL delete all volumes

Boundary condition within the volume

Group number of volume elementsMaterial number of volume elementsMaterial number of reinforcementType of Volume

BRIC Solid Continua ElementsBMAT Springelements from beddingMAT Springelements from material

Title of volume

−

LIT

−−−

LIT

LIT32

1

*

000

BRIC

−

This defines a volume. You may change an existing definition if you enter a nega-tive value for NO. The geometry of the volume itself is defined via surfaces se-lected via SVOS.

SVO can also define an elastic support or interface between two structural areas.This is accomplished by defining at TYPE a literal BMAT or MAT. In this casespring elements in the direction of extrusion will be generated instead of the stan-dard 8 node solids. The mechanical properties of which are calculated from theadjacent QUAD−areas and either from the bedding constants defined for materialMNO or the values of the elasticity and shear modulus and tensile and compres-sive strength defined with Material MNO and the real distance of the nodes alongthe extrusion direction. A definition of MRF allows the selection of an explicitforce−displacement curve for non−linear analysis.


5−47Version 12.01

See also: SVO SPT SAR SARB CTRL

5.18. SVOS − Structrual volume facesÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

SVOS


NAR

ACT

NO

Number of the surface SAR

Action of surfaceSURF general surfaceQGRP surface from QUAD elementsEXTR extrusion of surfaceROTA rotation of surfaceMESH mesh size for tetrahedron

generationBGRP Extrusion of beams

Number of a geometric line or axis orsubdivision of a boundary layer

−

LIT

−/LIT

!

SURF

(!)

T Boundary layer thickness (SURF/QGRP)or extra thickness value for ROTAor explicit stepping for EXTRor value for mesh density for MESH

* 0.0

FAC0FAC1TFACTFA1TREFPHI0PHIDPHI

Start scale factor for EXTREnd scale factor for EXTRScale factor for variable thicknessEnd scale factor for variable thicknessReference value for variable thicknessRotational start angle for EXTR/ROTARotational end angle for EXTR/ROTAIncrement of rotational angle for ROTA

−−−−*

degdegdeg

1.01.00.0

TFAK*0

0/36015


Version 12.015−48


REFDXDYDZXXYYZZ

Reference SPT on surfaceExplicit extrusion / rotational axisif NO is not defined

This definition is equivalent to an axisstarting from point (xx,yy,zz) zu(xx+dx,yy+dy,zz+dz)

−******

*0.00.00.00.00.00.0

NARANAREMNO

Start surface numberEnd surface numberMaterialnumber of boundary layer

−−−

−−

(SVO)

There are different possibilities to define a volume:

• Tetrahedral unstructured mesh of an arbitrary volume defined by the com-plete set of all surfaces. Any surface may have a boundary layer of moder-ate thickness T (must be smaller than mehs size in corners) which is sub-divided in NR elements and may have assigned a different materialnumner MNO.

• Hexahedral structured mesh by extrusion of surfaces along a line or axiswith number NO or an explicit value, applying a linear variant scaling androtation along. A linear variation of a scaling and a rotation about the ex-truded line and a variable thickness can be applied in this case. The meshsize along the extrusion is given either through the available mesh parti-tioning or through the explicit default of an increment T.

• Hexahedral structured mesh by rotation of the surface about an axis in aspecific angle area.

When extruding a structural region into a hexahedral element mesh, the structurallines bounding the region will also be extruded to new structural regions with thesame number on the outer sides of the volume. Attention should be paid, thatthese line numbers do not correspond to any other number of a structural regiondefined before.

For Tetraeder−Volume−Generations it is possible to specify at SVOS the item Tas thickness of a boundary layer, created by a parallel offset of the surface. WithNO a subdivision of the boundary layer may be defined, with MNO the boundarylayer will get this material number instead that of the volume.


5−49Version 12.01

See also: SPT, SLN, SAR, SVO

5.19. GUID − Globally Unique IdentifierÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

GUID


ID 128 bit code given as hexadecimal string Lit !

This record allows to assign a Globally Unique Identifier to a structural element.A Globally Unique Identifier (GUID) is a worldwide unique reference numberusually stored as 128−bit integer, which is primarily used for the unique identifica-tion of objects, when data is exchanged between different computer systems. Itmust be given at parameter ID as hexadecimal string, like for example:

GUID ID ’3F5A9ECC−145B−4093−9D16−E6F48732F569’.

The GUID is a property record and must be given directly after the definition ofthe structural element at SPT, SLN, SAR or SVO. GUIDs will be assigned to allstructural elements exported from SOFiPLUS or Autodesk Revit Structural.When describing the model using the CADINP language in text mode, it is usuallynot necessary to set a GUID.


Version 12.015−50

See also: XSUB GRP

5.20. BBOX − Bounding boxÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

BBOX


XMINYMINZMIN

XMAXYMAXZMAX

Minimum coordinates

Maximum coordinates

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

[m]1001

1.e101.e101.e10

1.e101.e101.e10

This record defines as rectangular bounding box for the selection of structuralelements. The record can be used for selecting the elements of a subsystem (seeXSUB) or as secondary group (see GRP).

sofistik help.pdf

Documents

geometric surfaces

spt structural point

d surface data point

d curve point data

sar structural area

generation of structural

gar geometric surface

sln structural line