Multi-Step Nonlinear

User’s Guide
Simcenter 3D 2312 Series
Unpublished work. © 2023 Siemens

This Documentation contains trade secrets or otherwise confidential information owned by Siemens Industry Software Inc. or
its affiliates (collectively, “Siemens”), or its licensors. Access to and use of this Documentation is strictly limited as set forth in
Customer’s applicable agreement(s) with Siemens. This Documentation may not be copied, distributed, or otherwise disclosed
by Customer without the express written permission of Siemens, and may not be used in any way not expressly authorized by
Siemens.

This Documentation is for information and instruction purposes. Siemens reserves the right to make changes in specifications
and other information contained in this Documentation without prior notice, and the reader should, in all cases, consult
Siemens to determine whether any changes have been made.
No representation or other affirmation of fact contained in this Documentation shall be deemed to be a warranty or give rise to
any liability of Siemens whatsoever.
If you have a signed license agreement with Siemens for the product with which this Documentation will be used, your use of
this Documentation is subject to the scope of license and the software protection and security provisions of that agreement.
If you do not have such a signed license agreement, your use is subject to the Siemens Universal Customer Agreement, which
may be viewed at https://www.sw.siemens.com/en-US/sw-terms/base/uca/, as supplemented by the product specific terms
which may be viewed at https://www.sw.siemens.com/en-US/sw-terms/supplements/.
SIEMENS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENTATION INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT OF
INTELLECTUAL PROPERTY. SIEMENS SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL OR
PUNITIVE DAMAGES, LOST DATA OR PROFITS, EVEN IF SUCH DAMAGES WERE FORESEEABLE, ARISING OUT OF OR RELATED
TO THIS DOCUMENTATION OR THE INFORMATION CONTAINED IN IT, EVEN IF SIEMENS HAS BEEN ADVISED OF THE POSSIBILITY
OF SUCH DAMAGES.

TRADEMARKS: The trademarks, logos, and service marks (collectively, "Marks") used herein are the property of Siemens or other
parties. No one is permitted to use these Marks without the prior written consent of Siemens or the owner of the Marks,
as applicable. The use herein of third party Marks is not an attempt to indicate Siemens as a source of a product, but is
intended to indicate a product from, or associated with, a particular third party. A list of Siemens’ Marks may be viewed at:
www.plm.automation.siemens.com/global/en/legal/trademarks.html. The registered trademark Linux® is used pursuant to a
sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the mark on a world-wide basis.

About Siemens Digital Industries Software

Siemens Digital Industries Software is a global leader in the growing field of product lifecycle management (PLM),
manufacturing operations management (MOM), and electronic design automation (EDA) software, hardware, and services.
Siemens works with more than 100,000 customers, leading the digitalization of their planning and manufacturing processes. At
Siemens Digital Industries Software, we blur the boundaries between industry domains by integrating the virtual and physical,
hardware and software, design and manufacturing worlds. With the rapid pace of innovation, digitalization is no longer
tomorrow’s idea. We take what the future promises tomorrow and make it real for our customers today. Where today meets
tomorrow. Our culture encourages creativity, welcomes fresh thinking and focuses on growth, so our people, our business, and
our customers can achieve their full potential.

Support Center: support.sw.siemens.com

Send Feedback on Documentation: support.sw.siemens.com/doc_feedback_form

 Contents

Introduction
SOL 401 nonlinear capabilities ──────────────────── 1-1
SOL 402 nonlinear capabilities ──────────────────── 1-2
Program architecture ───────────────────────── 1-4
Nonlinear characteristics and general recommendations ──────── 1-6

User Interface
Supported inputs ────────────────────────── 2-1
System Cells ─────────────────────────────── 2-2
Case control section ─────────────────────────── 2-5
Bulk data section ───────────────────────────── 2-6
Parameters ─────────────────────────────── 2-9
Nonlinear Effects in SOL 401 ───────────────────── 2-10
Nonlinear Effects in SOL 402 ───────────────────── 2-15
Nonlinear Parameters in SOL 401: NLCNTL entry ──────────── 2-17
Nonlinear Parameters in SOL 402: NLCNTL2 entry ─────────── 2-18
Solver Support ─────────────────────────── 2-21
Parallel support ─────────────────────────── 2-23
Memory assignment ──────────────────────── 2-27
SOL 402 - Intentional job termination ───────────────── 2-30
SOL 401 - Subroutine to monitor solution progress ─────────── 2-31

Subcase Types
Subcase analysis type ──────────────────────── 3-1
Dependent and independent subcases ───────────────── 3-2
SOL 401 - Subcase sequencing ──────────────────── 3-4
Static subcase ─────────────────────────── 3-12
Preload subcase ────────────────────────── 3-13
Normal modes subcase ─────────────────────── 3-14
Transient dynamic subcase ───────────────────── 3-15
Modal frequency response subcase (SOL 401) ───────────── 3-26
Cyclic modes subcase ──────────────────────── 3-39
Fourier harmonic solution ────────────────────── 3-45
Nonlinear buckling (SOL 401) ──────────────────── 3-48
Linearized buckling (SOL 402) ──────────────────── 3-60

Element support
Element Overview ────────────────────────── 4-1
Elements in nonlinear analysis ──────────────────── 4-3
Shell elements ──────────────────────────── 4-5

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3
© 2023 Siemens
 SOL 401- Tension-only shell element ───────────────── 4-12
SOL 401 - Shear panel element ──────────────────── 4-16
Bar and beam elements ─────────────────────── 4-19
Spring and damper elements ──────────────────── 4-22
SOL 401 - Rod element ─────────────────────── 4-26
Fixed rotational degrees-of-freedom (SOL 401) ──────────── 4-27
Rigid elements ─────────────────────────── 4-28
Generalized plane strain (SOL 401) ────────────────── 4-34
Element addition and removal ──────────────────── 4-37
Improved architecture for small strain problems (SOL 401) ───────
4-44
Error estimator for mesh refinement (SOL 401) ──────────── 4-47
Progressive failure analysis in solid composites ────────────
4-49
SOL 401 - Material and load scaling for 2D/3D models ─────────
4-65
SOL 402 - 2D Fourier axisymmetric and 2D/3D coupling ─────────
4-69
Chocking elements (SOL 401) ──────────────────── 4-76
Cohesive elements ───────────────────────── 4-80
Crack simulation (SOL 401) ───────────────────── 4-83
Stress output coordinate system ─────────────────── 4-86
Direct matrix input on grid points (DMIG) ─────────────── 4-87
SOL 402 - External superelements ────────────────── 4-89
Kinematic joints (SOL 402) ────────────────────── 4-94
Formulation of isoparametric elements ──────────────── 4-97
Isoparametric coordinates ──────────────────────── 4-98
Shape functions ──────────────────────────── 4-103
Example element matrix ──────────────────────── 4-105
Volume integration of element matrices ───────────────── 4-107
Element loads and equilibrium ───────────────────── 4-109
Element coordinates ────────────────────────── 4-111
Stress data recovery ────────────────────────── 4-113

Material support
Material overview ────────────────────────── 5-1
Plasticity analysis ────────────────────────── 5-3
Overview of Plasticity ──────────────────────── 5-9
Strain rate-dependent plasticity ─────────────────── 5-14
SOLs 401 and 402 - Stress-strain measures ────────────── 5-16
Cast iron plasticity SOLs 401 and 402 ───────────────── 5-20
Nonlinear elastic material (SOL 401) ───────────────── 5-23
Creep analysis ─────────────────────────── 5-28
User defined materials ─────────────────────── 5-47
User defined creep models (SOL 401 and 402) ───────────── 5-70
Disable plasticity and creep ───────────────────── 5-80
Hyperelastic materials (SOL 402) ─────────────────── 5-81
Gasket material (SOL 402) ────────────────────── 5-86
Ply failure theories (SOL 402) ──────────────────── 5-90

4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contents

Boundary conditions
Constraints ───────────────────────────── 6-1
Multipoint constraint ───────────────────────── 6-2
Enforced displacements ─────────────────────── 6-3
Cyclic symmetric boundary condition ───────────────── 6-4
SOL 402 - Redundant constraints ─────────────────── 6-10

Loads
Loads overview ─────────────────────────── 7-1
Mechanical loads (SOL 401) ────────────────────── 7-2
Mechanical loads (SOL 402) ────────────────────── 7-6
Thermal loads ─────────────────────────── 7-10
Mapping times in universal files ────────────────────── 7-18
Solution time steps (SOL 401) ──────────────────── 7-22
Solution time steps (SOL 402) ──────────────────── 7-25
Bolt preload (SOL 401) ──────────────────────── 7-27
ETYPE=1 Bolt (SOL 401) ───────────────────────── 7-30
ETYPE=2 Bolt (SOL 401) ───────────────────────── 7-34
Bolt preload output (SOL 401) ────────────────────── 7-38
Bolt preload (SOL 402) ──────────────────────── 7-40
Fluid penetrating pressure load ─────────────────── 7-48
Initial stress-strain (SOL 401) ───────────────────── 7-53
Distributed force to a surface or edge (SOL 401) ──────────── 7-59
SOL 401 - Interpolating rotational inertia loads ──────────── 7-65
SOL 402 - Interpolating rotational inertia loads ──────────── 7-69

Contact conditions (SOL 401)

Contact Overview ────────────────────────── 8-1
Contact Subcase Control ─────────────────────── 8-2
Contact Definition ────────────────────────── 8-3
Contact Control Parameters ────────────────────── 8-8
Contact kinematics ────────────────────────── 8-9
Contact Penalty Factors ─────────────────────── 8-25
SOL 401 - Contact and glue characteristic length ──────────── 8-27
SOL 401 - Tangential contact stiffness in sequentially dependent modal subcases
──────────────────────────────── 8-28
Contact Sliding and Geometry Update ──────────────── 8-30
Contact and rigid body motion ──────────────────── 8-32
Contact Gaps, Penetrations, and Offsets ──────────────── 8-35
Ramping contact changes ────────────────────── 8-40
Contact Surface and Edge Refinement ──────────────── 8-41
SOL 401 - Contact convergence ──────────────────── 8-43
SOL 401 - Contact message output ────────────────── 8-48
Contact Output ─────────────────────────── 8-52
References ───────────────────────────── 8-53

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5
© 2023 Siemens
 Contact conditions (SOL 402)
Contact overview ────────────────────────── 9-1
Contact subcase control ─────────────────────── 9-2
Contact definition ────────────────────────── 9-3
Contact control parameters ────────────────────── 9-7
Contact element ─────────────────────────── 9-8
Contact and rigid body motion ──────────────────── 9-12
SOL 402 - Contact damping ───────────────────── 9-14
Contact offsets, initial penetrations, adjustment ──────────── 9-17
SOL 402 - Tangential contact stiffness in modal subcases ──────── 9-20
Contact convergence ──────────────────────── 9-21
Contact output ─────────────────────────── 9-25
SOL 402 - Contact status output ─────────────────── 9-26
SOL 402 - Virtual thread contact ─────────────────── 9-29
Recommendations for contact definitions ─────────────── 9-32

Glue conditions
Overview of Gluing Elements ──────────────────── 10-1
Glue Regions ──────────────────────────── 10-6
Defining and Selecting Glue Pairs ────────────────── 10-7
Glue Control Parameters ────────────────────── 10-10
SOL 401 - Contact and glue characteristic length ─────────── 10-16
SOL 401 - Glue preview ─────────────────────── 10-17

Output
Requesting output ───────────────────────── 11-1
Gauss point output ───────────────────────── 11-4
SOL 402 - Iterations per subcase summary ────────────── 11-15
SOL 402 - Plot output request ──────────────────── 11-17
SOL 401 - Iteration related output data ──────────────── 11-19
SOL 401 - Solution accuracy indicator ──────────────── 11-23
SOL 401 - Residual output ───────────────────── 11-25
Types of strain output ─────────────────────── 11-26
SOL 401 - Grid point force output ────────────────── 11-28
SOL 402 - Modal participation factors and effective mass ─────── 11-30

Restart solution
SOL 401 Restart ─────────────────────────── 12-1
SOL 402 Restart ─────────────────────────── 12-6

Considerations for nonlinear analysis

Discrete system for a nonlinear continuum model ─────────── 13-1
Finite element formulation for equilibrium equations ───────── 13-3
Coordinate transformations ───────────────────── 13-8

6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contents

Displacement sets and reduction of system equations ───────── 13-12

Nonlinear solution procedure ──────────────────── 13-17

Geometric nonlinearity
Overview and user interface ───────────────────── 14-1
Updated element coordinates ──────────────────── 14-8
Concept of convective coordinates ──────────────────── 14-9
Updated coordinates and net deformation ──────────────── 14-10
Provisions for global operation ────────────────────── 14-14
Follower forces ────────────────────────── 14-16
Basic definition ──────────────────────────── 14-17
Implementation ──────────────────────────── 14-18

Solution methods
SOL 401 Singularities ──────────────────────── 15-1
SOL 402 Singularities ──────────────────────── 15-4
Solution Algorithm ───────────────────────── 15-6
Adaptive Solution Strategies ───────────────────── 15-8
Newton’s method of iteration ──────────────────── 15-9
SOL 401 - Newton-Raphson iteration strategy ──────────── 15-13
Stiffness update improvement with large strain (SOL 401) ─────── 15-15
Stiffness update strategies ───────────────────── 15-16
Update principles ─────────────────────────── 15-17
Divergence criteria ─────────────────────────── 15-19
Convergence criteria ──────────────────────── 15-22
Rudimentary considerations ─────────────────────── 15-23
Convergence conditions ──────────────────────── 15-24
SOL 401 - Error functions and weighted normalization ─────────── 15-25
SOL 402 - Error functions and weighted normalization ─────────── 15-28
Implementation ──────────────────────────── 15-32

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7
© 2023 Siemens
8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 1. Introduction
1.1 SOL 401 nonlinear capabilities
SOL 401 is a multi-step, structural solution that supports a combination of subcase types (linear,
dynamic, preload, modal, Fourier, cyclic).

SOL 401 supports large strains and large displacements, large rotations, and nonlinear materials.

SOL 401 is supported as a standalone solver, it can be used in Simcenter 3D Pre/Post, and is supported in
Simcenter Femap’s Analysis Set Manager. SOL 401 is also the structural solution used by the Simcenter
3D Multiphysics environment within the Pre/Post application. The Multiphysics environment supports all
combinations of structural-to-thermal and thermal-to-structural coupling with the Simcenter 3D Thermal
solution.

Primary operations for nonlinear elements are updating element coordinates and applied loads for
large displacements. The geometric nonlinearity becomes discernible when the structure is subjected
to large displacement and rotation. Geometric nonlinear effects are prominent in two different aspects:
geometric stiffening due to initial displacements and stresses, and follower forces due to a change in
loads as a function of displacements.

Material nonlinearity is an inherent property of any engineering material. SOL 401 supports plasticity,
strain rate-dependent plasticity, nonlinear elasticity, creep, and viscoelasticity. In addition, user defined
materials are available.

The primary solution operations are time increments, iterations with convergence tests for acceptable
equilibrium error, and stiffness matrix updates. The iterative process is based on variations of Newton's
method. The stiffness matrix updates are performed to improve the computational efficiency, but may be
overridden at your discretion.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 1-1
© 2023 Siemens
 1. Introduction

1.2 SOL 402 nonlinear capabilities

SOL 402 is a multi-step, structural solution that supports a combination of subcase types (static
linear, static nonlinear, nonlinear dynamic, preload, modal, Fourier, buckling and complex eigenvalues
extraction) and large rotation kinematics. SOL 402 is supported as a standalone solver, it can be used in
Simcenter 3D Pre/Post, and is also supported in Simcenter Femap’s Analysis Set Manager.

SOL 402 supports large strains and large displacements, large rotations, and nonlinear materials.

An example application for SOL 402 in the automotive industry is analyzing tires or engine mounts
(hyperelastic materials). In the aerospace industry, an example application is analyzing vibration
dampers between a rocket body and its boosters or composite panels.

Geometric nonlinear effects

SOL 402 supports large displacements (PARAM,LGDISP) and large strains (PARAM,LGSTRN).

The material and geometric nonlinearity parameters are global for all subcases. If material nonlinearity is
turned on, plasticity and creep can be turned off at the subcase level.

Materials support

Material nonlinearity is an inherent property of any engineering material. SOL 402 supports plasticity,
hyperelasticity (MATHE, MATHM, MATHEV, and MATHP bulk entries), creep (MATCRP and CREEP bulk
entries), and strain-rate dependent laws (MATSR bulk entry).

You can also set gasket behaviors (MATG bulk entry) or define your own nonlinear material (UMAT bulk
entry).

Kinematic joints support

SOL 402 supports nonlinear kinematic joints and flexible sliders. Kinematic joints allow structural
analyses of an assembly containing moving parts.

With flexible sliders, you drive the displacement of parts along a line of beams that models a track. You
can also add a nonlinear frictional behavior.

For more information, see Kinematic joints (SOL 402).

Solution nonlinear control parameters

On the NLCNTL2 bulk entry, you can define all the solution nonlinear parameters at the subcase level.
For instance:

1-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 nonlinear capabilities

• You can choose between fixed time steps or automatic time stepping. You can also control the time
step size (minimum, maximum, increase ratio), the integration scheme, and the integration error.

You can also control the convergence of the solution.

• You can set options to control plasticity and creep conditions.

Restart of solutions

In SOL 402, on the NLCNTLG bulk entry, you can define restart conditions.

• You can make an internal restart.

Internal restarts start a specified subcase with the computation state (displacements, velocities,
stresses, state variables, and so on) of a preload, static, or dynamic subcase during the same solve.
For example, you might want to start several non-sequentially dependent (NSD) subcases with the
results of a bolt preload subcase.

You can use the RSUB=n parameter of the NLCNTL2 bulk entry to make an internal restart.

• You can make an external restart.

External restarts start a new nonlinear solve with results from a previous solve. For example, you can
start a new solution using the computed pre-stress of your model. Or, you can start a new solution
from the last converged step within a static or dynamic subcase.

For more information, see SOL 402 Restart.

Failure theories

With the MATDMG bulk entry, you can model progressive ply failure in composite laminates. For more
information, see Progressive failure analysis in solid composites.

Nonlinearities in contact conditions

Nonlinearities are taken into account in contact conditions: small or large sliding behaviors can be
modeled in the contact, and you can define regularization models to control how the contact conditions
are updated.

You can add time, velocity, or temperature dependent friction behaviors.

In dynamic analysis (ANALYSIS=DYNAMICS), you can add a contact tangential viscous pressure.

Nonlinearities in glue conditions

In SOL 402, glue conditions are weld-like connections and no nonlinear effect can change this behavior.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 1-3
© 2023 Siemens
 1. Introduction

1.3 Program architecture

The software has a modular structure to separate functional capabilities which are organized under an
efficient executive system. The program is divided into a series of independent subprograms, called
functional modules. A functional module is capable of performing a pre-defined subset of operations. It
is the Executive System that identifies every module to execute by MPL (Module Properties List).

The Executive System processes the input data by IFP (Input File Processor) and the general initialization,
which are known as Preface,operations. It then establishes and controls the sequence of module
executions in the OSCAR (Operation Sequence Control Array) based on the user-specified DMAP (Direct
Matrix Abstraction Program) or solution sequence. The Executive System allocates system files to the
data blocks in the FIAT (File Allocation Table) and maintains a parameter table for module interface.
The Executive System is also responsible for the database management and all the input and output
operations by GINO (General Input/Output Routines).

The functional module consists of a number of subroutines. Modules communicate with each other only
through secondary storage files, called data blocks (matrix or table). Each module performs a certain
function with input data blocks and produces output data blocks. A module may communicate with
the Executive System and with other modules through parameters, which may be input and/or output
variables of the module. Modules utilize main memory dynamically. If the size of the main memory
is insufficient to complete an operation, the module uses scratch files, which reside in the secondary
storage as an extension of the main memory. This is known as a spill operation.

DMAP is a kind of macro program using a data block oriented language. The solution sequence is a
collection of module statements written in the DMAP language tailored to process a sequential series of
operations, resulting in a specific type of structural analysis. A typical solution sequence consists of three
phases of functional operations: formation, assembly, and reduction of matrices; solution of equations;
and data recovery.

The nonlinear solution sequences have built-in loops in the second phase for subcase changes, load
increments, and stiffness matrix updates. Nested in this DMAP loop, nonlinear solution processes
comprise a number of internal iteration loops. Confining the discussion to SOL 401, the hierarchy of
the nonlinear looping is shown in the table below. Central to the nonlinear processes is module NLTRD3.
The module is self-contained to perform iterations for converged solutions.

Table 1-1. Hierarchy of Nonlinear Looping

Name or Loop Type

1 Subcases (boundaries, temperatures, loads, outputs) DMAP Control
2 Time Steps (NLTRD3) Module Control
3 Stiffness Matrix Updates The actual stiffness update is under
DMAP control, but the request for
a stiffness update in the middle of
a solution is under Module control.
Decomposition is under module
control.

1-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Program architecture

4 Iterations (Vector Arithmetic) Module Control

5 Elements (NLEMG) Subroutine Control
6 Volume Integration (Gauss Points) Subroutine Control

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 1-5
© 2023 Siemens
 1. Introduction

1.4 Nonlinear characteristics and general recommendations

The modeling guidelines for nonlinear analysis and linear analysis are summarized as follows:

• The analyst should have some insight into the behavior of the structure to be modeled; otherwise, a
simple model should be the starting point.

• The size of the model should be determined based on the purpose of the analysis, the trade-offs
between accuracy and efficiency, and the scheduled deadline.

• Prior contemplation of the geometric modeling will increase efficiency in the long run. Factors to be
considered include selection of coordinate systems, symmetric considerations for simplification, and
systematic numbering of nodal points and elements for easy classification of locality.

• Discretization should be based on the anticipated stress gradient, i.e., a finer mesh in the area of
stress concentrations.

• Element types and the mesh size should be judiciously chosen. For example, avoid highly distorted
and/or stretched elements (with high aspect ratio).

• The model should be verified prior to the analysis by some visual means, such as plots and graphic
displays.

Nonlinear analysis requires better insight into structural behavior. First of all, the type of nonlinearities
involved must be determined. The geometric nonlinearity is characterized by large displacements and
large rotations. Intuitively, geometric nonlinear effects should be significant if the deformed shape of
the structure appears distinctive from the original geometry without amplifying the displacements.
There is no distinct limit for large displacements because geometric nonlinear effects are related to the
dimensions of the structure and the boundary conditions.

Additional recommendations are important for nonlinear analysis:

• PARAM,LGDISP,1 must be defined to turn on geometric nonlinearity.

• Material nonlinear effects can also be included. See Plasticity analysis, Hyperelastic materials,
Creep analysis, Gasket material, and Progressive failure analysis in solid composites.

• The nonlinear region usually requires a finer mesh. Use a finer mesh if severe element distortions or
stress concentrations are anticipated.

• The subcase structure should be utilized properly to divide the load or time history for conveniences in
data recovery, and database storage control, not to mention changing constraints and loading paths.

• Many options are available in solution methods to be specified on the NLCNTL and the TSTEP1 bulk
entries. The defaults should be used on all options before gaining experience.

1-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 2. User Interface
2.1 Supported inputs
The input data structure includes an optional header, executive control section, case control section, and
the bulk data section. In general, features and principles for the user interface are consistent with other
solution sequences. Any exceptions for SOL 401 or SOL 402 are explained in this guide.

Mechanical design is dictated by the strength, dynamic, and stability characteristics of the structure.
The software provides the analysis capabilities of these characteristics with solution sequences, each
of which is designed for specific applications. The type of desired analysis is specified in the executive
control section by using a solution sequence identification.

• SOLs 401 and 402 are designed for nonlinear analyses with large displacements and large strains.

The basic input data required for a finite element analysis may be classified as follows:

• Geometric data

• Element data

• Material data

• Boundary conditions and constraints

• Loads and enforced motions

• Solution methods

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-1
© 2023 Siemens
 2. User Interface

2.1.1 System Cells

SOL 402 supports the following NASTRAN System Cells.

System Cell (Name) Function and Reference

57 (HICORE) Working memory
81 Specifies the amount of open core memory to which certain numerical
modules will be restricted.
107 (PARALLEL) Parallel processing deselection (deactivation) for matrix operations.
See Keywords in the Simcenter Nastran Installation and Operations
Guide.
0: Deactivate parallel processing
N: Number of processors
143 (LOCBULK) LOCBULK=1 or 2 specifies that Bulk Data is being obtained with the
DBLOCATE FMS statement. NASTRAN LOCBULK=2 is specified when no
bulk entries, except for PARAM entries, are to be deleted or added. All
PARAM entries must be respecified. All other entries will be ignored
and, if present, may increase CPU times in XSORT and IFP. With
LOCBULK=2, the XSORT and IFP modules will not reprocess the Bulk
Data Section stored in the SEMAP run. Also, GP1, TASNP2, SEP1 and
SEP1X modules will be skipped. 0 is the default, which assumes the
RESTART FMS statement.
144 RESTART FMS statement existence flag. Set to 1 if RESTART statement
is present.
370 (QRMETH) Selects the formulation used by the QUADR/TRIAR elements.
0: Selects the QUADR/TRIAR membrane formulation with active out of
plane rotational DOF (default)
1: Selects the older, limited QUADR/TRIAR formulation. Complex
stresses and strains are not computed
3: Converts QUADR/TRIAR into QUAD4/TRIA3 formulation
5: Converts QUAD4/TRIA3 into the newer QUADR/TRIAR formulation
400 Reserved
401 Reserved
413 OP2 file format (32-bit or 64-bit).
0: let the software chooses the format (Default).
1: 32-bit format.
442 Controls if Solution Monitor files are generated for Simcenter 3D and
FEMAP. It is only valid on the platforms supported by Simcenter 3D
and FEMAP.

2-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 System Cells

0: Do not generate (default)

1: Generate files and delete after solution completes
-1: Generate files and keep after solution completes
2: reserved
525 Enables integer inputs to be 11 characters.
587 Determines the sectional properties for the axisymmetric elements
CTRAX3, CQUADX4, CTRAX6, and CQUADX8.
0 (default): Stiffness, mass, and loads are based on a 2*PI section
(beginning with NX Nastran 10).
1: Stiffness, mass, and loads are computed on a per radian basis
(behavior prior to NX Nastran 10), except for heat transfer solutions
with CTRAX3, CQUADX4, CTRAX6, and CQUADX8, which remain on a
2*PI basis.
592 Reserved. Used when sys442=2.
593 Reserved. Used when sys442=2.
674 Controls the export of decks.
0: The deck contains one SPC (or SPC1) companion card for every
imposed displacement SPCD (default for all Nastran solutions except
SOL 402).
1: The deck does not contain any companion card. The computation
will then be more efficient. However, if you manually set the system
cell to 1 on a deck that contains companion cards (for example, one
that was generated in Simcenter 3D using SOL 401, but then later
converted to SOL 402), any imposed displacements on a DOF that is
fixed with SPC/SPC1 will be ignored (default for SOL 402).
675 Verbosity level for SOL 402.
0 (default) = minimum verbosity.
1 = Low verbosity. List the output of the pre-processing (Bacon)
and post-processing (Fac) steps of SOL402 solver. This is done
automatically in case of warning or errors during those steps.
2 = High verbosity. In addition to sys675=1, list the content of the
model read during the pre-processing step.
3 = High verbosity. In addition to sys675=2, call the DMAP module
TABPRT to print the content of all the output datablocks (except
rotation matrices TRMBU and TRMBD).
4 = High verbosity. In addition to sys675=3, call the DMAP module
TABPRT to print the content of all the output datablocks (very large
output, not recommended).

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-3
© 2023 Siemens
 2. User Interface

683 Temporarily turns off printing USER INFORMATION MESSAGE 4114

(OUTPX2) during writing the datablock in the scratch OP2 file.
Automatically turned on when needed.
699 Specifies the number of displacement curves that appear in a report.
(Default = 3)
The list of nodes that will be considered for displaying the curves is
defined with the SETMC Case Control entry.
If more than 2 curves are requested, only the curves for the minimum,
maximum, and average values of all the selected nodes will be
displayed.
701 Checks for the existence of NLCNTLG,RSTGEN to request restart
information generation.
709 Checks for the existence of NLCNTLG,RSTFROM to request restart
information generation.
710 Checks for the existence of NLCNTLG,EXEFORM to request restart
information generation.

2-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Case control section

2.1.2 Case control section

The primary purpose of the case control is to define subcases. The subcase structure provides a means
of changing loads, boundary conditions, and solution methods by making selections from the bulk data.
Loads and solution methods may change from subcase to subcase. Constraints can be changed from
subcase to subcase. As a result, the subcase structure determines a sequence of loading and constraint
paths. The subcase structure also allows you to select and change output requests. Any commands
defined above the subcase specifications are applicable to all the subcases. Commands defined in a
subcase supersede any made above the subcases.

See the Case Control Applicability Tables in the Simcenter Nastran Quick Reference Guide for the
supported commands in SOLs 401 and 402.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-5
© 2023 Siemens
 2. User Interface

2.1.3 Bulk data section

The following tables list the bulk entries supported by SOLs 401 and 402.

Table 2-2. Summary of bulk entries supported by SOL 401

ACCEL CPLSTN8 INITADD PCOMPS

ACCEL1 CPLSTS3 INITS PELAS
BCPROP CPLSTS4 INITSO PELAST
BCPROPS CPLSTS6 MAT1 PGPLSN
BCRPARA CPLSTS8 MAT2 PLOAD
BCTPARM CPYRAM MAT8 PLOAD1
BCTSET CQUAD4 MAT9 PLOAD2
BEDGE CQUAD8 MAT11 PLOAD4
BGADD CQUADR MATCID PLOADE1
BGPARM CQUADX4 MATCRP PLOADFP
BGSET CQUADX8 MATCZ PLOADX1
BOLT CRAKTP MATDMG PLOTEL
BOLTFOR CROD MATFT PMASS
BOLTFRC CSHEAR MATS1 PPLANE
BOLTLD CTETRA MATSR PROD
BOLTSEQ CTRAX3 MATT1 PSHEAR
BSURF CTRAX6 MATT2 PSHELL
BSURFS CTRIA3 MATT8 PSHLPNL
CBAR CTRIA6 MATT9 PSOLCZ
CBEAM CTRIAR MATT11 PSOLID
CBUSH CVISC MOMENT RBAR
CBUSH1D CYCADD MOMENT1 RBE2
CCHOCK3 CYCAXIS MOMENT2 RBE3
CCHOCK4 CYCSET MPC RFORCE
CCHOCK6 DAMPTAB MPCADD RFORCE1
CCHOCK8 DAREA MPLAS SLOAD
CDAMPi DLOAD MVPLAS SNORM
CELAS1 DMIG MUCRP SPC
CELAS2 DTEMP MUMAT SPC1
CHEXA DTEMPEX NLARCL SPCADD
CHEXCZ ECHOOFF NLCNTL SPCD
CMASS1 ECHOON NSM SPOINT
CMASS2 EIGRL NSM1 TABLED1
CMASS3 ELAR NSMADD TABLED2
CMASS4 ELAR2 NSML TABLED3
CONM1 ELARADD NSML1 TABLED4
CONM2 ENDDATA PARAM TABLEM1
CORD1C FORCDST PBAR TABLEM2
CORD1R FORCE PBARL TABLEM3
CORD1S FORCE1 PBEAM TABLEM4
CORD2C FORCE2 PBEAML TABLEM5
CORD2R GRAV PBUSH TEMP
CORD2S GRDSET PBUSH1D TEMPD

2-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bulk data section

CORD3G GRID PBUSHT TEMPEX

CPENTA GROUP PCHOCK TLOAD1
CPENTCZ IMPERF PCOMP TLOAD3
CPLSTN3 IMPRADD PCOMPG TSTEP1
CPLSTN6 INCLUDE PCOMPG1 VCEV

Table 2-3. Summary of bulk entries supported by SOL 402

BCPROP CPLSTS4 MAT2 PGAP

BCPROPS CPLSTS6 MAT3 PJOINT
BCRPARA CPLSTS8 MAT8 PLOAD
BCTADD CPYRAM MAT9 PLOAD1
BCTPAR2 CQUAD MATCID PLOAD2
BCTSET CQUAD4 MATCRP PLOAD4
BEDGE CQUAD8 MATCZ PLOADE1
BGADD CQUADR MATDMG PLOADFP
BGPARM CQUADX4 MATFT PLOADX1
BGSET CQUADX8 MATG PLPLANE
BOLFRC CREEP MATHE PLSOLID
BOLT CROD MATHEM PMASS
BOLTFOR CTETRA MATHEV PPLANE
BOLTLD CTRAX3 MATHP PROD
BSURF CTRAX6 MATS1 PSHELL
BSURFS CTRIA3 MATSR PSHL3D
BVTADD CTRIA6 MATT1 PSOLCZ
BVTPAR CTRIAR MATT11 PSOLID
BVTSET CYCADD MATT2 RBAR
CBAR CYCAXIS MATT3 RBE2
CBEAM CYCSET MATT8 RBE3
CBUSH DESC MATT9 RFORCE
CBUSH1D DLOAD MATTC RFORCE1
CDAMP1 DMIG MOMENT SEBULK
CDAMP2 DRIVER MOMENT1 SECONCT
CELAS1 DTEMP MOMENT2 SELOAD
CELAS2 ECHOOFF MPC SELOC
CGAP ECHOON MPCADD SPC
CHEXA EIGB MPLAS SPC1
CHEXZ EIGC MUCRP SPCADD
CJOINT EIGR MUMAT SPCD
CMASS1 EIGRL MVPLAS TABLED1
CMASS2 ENDDATA NLCNTL2 TABLED2
CONM1 FLXADD NLCNTLG TABLED3
CONM2 FLXSLI OUTMGT TABLED4
CONROD FMH3D PBAR TABLEM1
CORD1C FORCE PBARL TABLEM2
CORD1R FORCE1 PBEAM TABLEM3
CORD1S FORCE2 PBEAML TABLEM4
CORD2C FOU3 PBUSH TABLEM5
CORD2R GRAV PBUSH1D TABLES1

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-7
© 2023 Siemens
 2. User Interface

CORD2S GRID PBUSHT TABLEST

CPENTA GROUP PCOMP TEMP
CPENTCZ INCLUDE PCOMPG TEMPD
CPLSTN3 JCON PCOMPG1 TIC
CPLSTN4 JCONADD PCOMPS TLOAD1
CPLSTN6 LOAD PDAMP TSTEP
CPLSTN8 MAT1 PELAS TSTEP1
CPLSTS3 MAT11 PELAST

2-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Parameters

2.1.4 Parameters

Parameters are used in the solution sequences for input of scalar values and for requesting special
features. All parameters values can be specified in the Bulk Data using the PARAM bulk entry. A subset of
these parameters can optionally be defined in the case control using the PARAM command.

See the Parameter Applicability Tables in the Simcenter Nastran Quick Reference Guide for the
parameters supported by SOLs 401 and 402. Parameters with a "B" in the table can only be specified in
the Bulk Data. Parameters with an "E" in the table can be specified in either the Bulk Data or in the Case
Control.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-9
© 2023 Siemens
 2. User Interface

2.2 Nonlinear Effects in SOL 401

Large displacement

The parameter LGDISP turns the nonlinear large displacement capability on/off for the static, dynamic,
and preload subcases. If you define the parameter LGDISP for SOL 401, you must include it in the bulk
data portion of your input file. The single PARAM,LGDISP setting applies to all subcases.

• PARAM,LGDISP,-1 (default) - Large displacement effects are turned off for STATIC, PRELOAD, and
DYNAMICS subcases.

For the MODES, CYCMODES, and FOURIER subcases, second-order effects are ignored.

• PARAM,LGDISP,1 - Large displacement effects are turned on for STATIC, PRELOAD, and DYNAMICS
subcases.

When large displacement effects are turned on, you can use the SPINK, STRESSK, and FOLLOWK
parameters on the NLCNTL bulk entry to turn on or off the second-order effects for the STATIC,
DYNAMICS, and PRELOAD subcases, as well as for the MODES, CYCMODES, and FOURIER subcases.

PARAM,LGDISP,1 turns on large displacement effects, but small strains are assumed.

Material nonlinear effects can also be included. See Support for plasticity analysis and Support for
creep analysis.

Large strain

The parameter LGSTRN turns on/off large strains, displacements, and rotations.

• PARAM,LGSTRN,0 (default) - Small strains are assumed.

• PARAM,LGSTRN,1 - Large strains are requested. When you request large strain effects, large
displacement effects are also automatically included (LGDISP=1).

The following elements are supported in a SOL 401 large strain analysis:

• The 3D solid elements CHEXA, CPENTA, CTETRA, CPYRAM. Solid composites are not supported.

• The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8, and the plane stress elements
CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8. When large strain is requested, the mean dilatational
formulation option for nearly incompressible materials is not supported, therefore the FOROPT
field on the PPLANE bulk entry is ignored.

In addition, when you include the plane stress elements in a large strain analysis, their cross-section
thickness can change as a function of the normal total strain ε33:

2-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear Effects in SOL 401

Then,

where t is the current thickness and t0 is the initial thickness.

• The axisymmetric elements CQUADX4, CQUADX8, CTRAX3 and CTRAX6.

• The spring elements CELAS1, CELAS2, CBUSH, and CBUSH1D are supported as small strain element
types in a large strain analysis.

• The mass elements CMASSi, CONM1, CONM2.

• The rigid elements RBE2, RBE3, RBAR.

Including an element not listed above will cause a fatal error.

Large strain is not supported when element add/removal is requested.

Large strain is supported when running SOL 401 in the Simcenter 3D Multiphysics environment.

Material support for large strain

• The same material types which are supported with small strain are also supported with large strain,
except for the MUMAT. The supported materials are the MAT1, MATT1, MAT9, MATT9, MAT11,
MATT11, MATS1, MATCRP, MPLAS, and MUCRP.

• Large strain analysis always uses the {log(True)strain, Cauchy stress} strain-stress measures in the
material law.

• When you define a plastic material for a large strain analysis, the STRMEAS field is available on the
MATS1 bulk entry to define the stress and strain measure of the input data.

• When "ENG", "UNDEF", or blank is defined in the STRMEAS field, the stress-strain data is defined
in engineering measures. When large strain (PARAM,LGSTRN,1) is requested, the software will
convert the data to true measures. Otherwise, the data is not converted and the software uses the
engineering format.

For more information, see SOLs 401 and 402 - Stress-strain measures.

• When "TRUE" is defined in the STRMEAS field, the stress-strain data is defined in true (Cauchy)
measures. In this case, when large strain (PARAM,LGSTRN,1) is requested, the software does no
conversion of the data.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-11
© 2023 Siemens
 2. User Interface

• If you define engineering stress-strain data for a large strain analysis, you can use the STRCONV
parameter on the NLCNTLG bulk entry to select the method in which the software uses to convert the
strain-stress data from engineering to Cauchy. STRCONV=0 (default) selects the exact conversion and
STRCONV=1 selects the standard conversion. See the NLCNTLG bulk entry in the Simcenter Nastran
Quick Reference Guide for information on these choices.

• The STFOPTN parameter on the NLCNTL bulk entry selects the material stiffness matrix option.

• When small strain analysis is requested (PARAM,LGSTRN,0), the default is STFOPTN=3, which means
that the elastic stiffness matrix is used to start each subcase, the elastic stiffness matrix is used if
a stiffness update is requested prior to the beginning of a new time step, and the tangent stiffness
matrix is used at any intermediate stiffness update.

• When large strain analysis is requested (PARAM,LGSTRN,1), the default is STFOPTN=2, which means
that the tangent material stiffness matrix is always used.

Load information for large strain

• When you request large strains, large displacement effects are also automatically included
(LGDISP=1). As a result, follower forces such as the pressure loads (PLOAD4, PLOAD, PLOADX1) will
rotate with the applied surface of solid elements and be integrated over the surface in the current
configuration.

• You can define a preload subcase in a large strain analysis. You can include a bolt preload using the
ETYPE=2 option on the BOLT bulk entry.

• Initial stress-strain conditions are not supported in a large strain analysis.

Output information for large strain

• The stress-strain output measure is {log(True)strain, Cauchy stress} when large strain is requested.

• The system cell 627 and CORDM<0 on the PSOLID bulk entry are ignored in a large strain analysis.
As a result, stress and strain results are always output in the body-fixed material coordinate system,
which are the updated material coordinates when large rotation occurs.

Additional element information for large strain

• The integration scheme of large strain elements may be different than the small strain elements. See
the PSOLID bulk entry for the details.

• In large strain analysis, your mesh quality should be as good as possible. If the computed Jacobian
determinant of an element in the current configuration is not positive, which means the mesh is too
distorted, a time step bisection will occur.

• For the first-order solid elements (4-node axisymmetric element and 8-node HEXA element), the
actual volume changes at the Gauss points are replaced by the average volume change of the

2-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear Effects in SOL 401

element. This is known as the selectively reduced-integration technique, because the order of
integration is reduced in selected terms, or as the B-Bar technique, because the strain-displacement
relation (B-matrix) is modified. This technique helps to prevent mesh locking, and provides accurate
solutions in incompressible or nearly incompressible cases.

The modified rate of the deformation tensor is

where

is the identity tensor,

f=1/2 for axisymmetric elements,

f=1/3 for CHEXA element, and

For axisymmetric elements, the out-of-plane strain increment is calculated by averaging over the
current element volume:

• For plane strain and plane stress elements, the mean dilatational formulation option for nearly
incompressible materials is not supported, therefore the FOROPT field on the PPLANE bulk entry is
ignored.

In addition, when you include the plane stress elements in a large strain analysis, their cross-section
thickness can change as a function of the normal total strain ε33:

Then,

where t is the current thickness and t0 is the initial thickness.

SOL 401 large strain formulation

• SOL 401 uses the updated Lagrangian Jaumann formulation (ULJ) for large strain analysis. The current
configuration of the body is used during the analysis. The stress-strain measures are respectively
Cauchy or “true” stress and “integrated” total strain (similar as true strain). This total strain is

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-13
© 2023 Siemens
 2. User Interface

constructed by integrating the Jaumann strain rate approximately over the increment by the central
difference algorithm. When the strain components are referred to a fixed coordinate basis, the strain
at the start of the increment must also be rotated to account for the rigid body rotation that occurs in
the increment. More precisely, the Jaumann strain rate is defined by

where,

, and

L is the velocity gradient tensor.

Then the Jaumann strain can be updated by the incremental method from iteration n to n+1:

where,

ΔR is the increment in rotation defined by the Hughes-Winget (1980) method as

and ΔW is the central difference integration of the rate of spin tensor W:

The subscript n+1/2 means that the strain increment and spin tensor increment are both defined in
the midpoint configuration.

The Jaumann strain can be regarded as an approximation of the left Hencky strain. It is used for stress
updates by the material constitutive relation.

• The time step size affects the Jaumann strain, so that finite time step sizes lead to an error in the
calculation of the Jaumann strain. For a uniaxial deformation, the Jaumann strain approaches the
logarithmic strain as the step size is reduced. For a rigid-body rotation, the Jaumann strain also
rotates, with the rotation of the Jaumann strain approaching the expected rotation as the step size is
reduced.

• The Jaumann strain method is the most frequently used strain rate. However, it is deficient with large
shear strain problems because it produces an artificial oscillation for a simple shear problem. It can
also be shown that the Jaumann strain is path-dependent in general, so that a deformation history
in which the final deformations equal the initial deformations can produce (nonphysical) non-zero
Jaumann strains, even in the limit of infinitesimally small time steps.

2-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear Effects in SOL 402

2.3 Nonlinear Effects in SOL 402

Large displacement

The parameter LGDISP turns the nonlinear large displacement capability on/off. If you define the
parameter LGDISP for SOL 402, you must include it in the bulk data portion of your input file. The
single PARAM,LGDISP setting is global and applies to all subcases.

• PARAM,LGDISP,-1 (default) - Large displacement effects are turned off for STATIC, PRELOAD, and
DYNAMICS subcases.

For the MODES, CYCMODES, and FOURIER subcases, second-order effects are ignored.

As a consequence, BUCKLING subcases are not allowed.

Small strains are assumed and follow the Engineering strain law.

• PARAM,LGDISP,1 - Large displacement effects are turned on for STATIC, PRELOAD, and DYNAMICS
subcases.

For the MODES, CYCMODES, and FOURIER subcases, second-order effects are taken into account. In
particular the stress stiffening effect of the previous static subcase.

For the BUCKLING subcases, nonlinear effects are split in two terms: a dead load part and a varying
part. The varying part is related to the loads variation from its latest static equilibrium.

Large strain

The parameter LGSTRN turns on/off large strains, displacements, and rotations.

• PARAM,LGSTRN,0 (default) — Small strains are assumed.

• PARAM,LGSTRN,1 — Large strains, displacements, and rotations are assumed (that is, LGDISP is
automatically set to 1).

In particular, nonlinear material laws will switch to a Cauchy stress and Logarithmic strain. All TABLES1
stress/strain hardening curves should also use the same convention.

Note:
Large strain formulation is applicable to all elements. If MATNL is set to -1 (default, which turns
off material nonlinearity), the software issues a fatal message asking you to either turn on
material nonlinearities (MATNL = 1) or to set the LGSTRN parameter to 0 to run the computation
with linear materials and linear elements. Otherwise, the results may not be what you expect.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-15
© 2023 Siemens
 2. User Interface

Note:
In SOL 402, LGDISP and LGSTRN both turn on large strains for all element types. The only
difference between LGDISP and LGSTRN is that:

• if LGDISP=1, the {Biot (engineering) strain, Biot stress} stress-strain measure is used by default.

• if you explicitly turn on large strains (LGSTRN=1), then the {log (True) strain, Cauchy stress}
stress-strain measure is used.

For more information, see SOLs 401 and 402 - Stress-strain measures.

2-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear Parameters in SOL 401: NLCNTL entry

2.4 Nonlinear Parameters in SOL 401: NLCNTL entry

The NLCNTL bulk entry can be used to define strategies for the incremental and iterative solution
processes. It is difficult to choose the optimal combination of all the options for a specific problem.
However, based on a considerable number of numerical experiments, the default option was intended
to provide the best workable method for a general class of problems. You should start with the default
settings.

The NLCNTL bulk entry defines the parameters for SOL 401 control. The NLCNTL=n case control
command selects the NLCNTL bulk entry, and can be defined in a subcase or globally. You can define the
parameters on the NLCNTL bulk entry using the following format.

1 2 3 4 5 6 7 8 9 10
NLCNTL ID Param1 Value1 Param2 Value2 Param3 Value3
Param4 Value4 Param5 Value5 -etc-

For example,

NLCNTL 1 EPSU 1E-3 EPSP 1E-3 EPSW 1E-7 +

+ CONV PW KSTEP 5 MAXITER 25

See the NLCNTL bulk entry in the Simcenter Nastran Quick Reference Guide for the list of parameters
and descriptions.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-17
© 2023 Siemens
 2. User Interface

2.5 Nonlinear Parameters in SOL 402: NLCNTL2 entry

The NLNTL2 bulk entry defines all the solution control parameters for SOL 402. The parameters can vary
from one subcase to another.

The NLCNTL=n case control command selects the NLCNTL2 bulk entry, and can be defined in a subcase
or globally.

It is difficult to choose the optimal combination of all the NLCNTL2 bulk entry options for a specific
problem. However, the defaults were intended to provide the best workable method for a general class
of problems. Therefore, if you have little insight or experience in a specific application, you should start
with the default values.

Analysis control

The NLCNTL2 bulk entry helps you to control the analysis itself. For instance, you can:

• Control the maximum displacement and/or rotation that you allowed in your model.

• Decide whether time-unassigned loads or temperatures are ramped or stepped.

• Take inertia into account in nonlinear dynamic subcases.

Plasticity and creep control options

In SOL 402, when the MATNL parameter is set to 1 (PARAM,MATNL,1) to turn creep and/or plasticity
effects on, you can turn these effects off at the subcase level with the CREEP and PLASTICTY parameters
of the NLCNTL2 bulk entry. For more information, see Disable plasticity and creep.

Time integration

On the NLCNTL2 bulk entry, you select the one of the following integration schemes:

• Newmark implicit predictor-corrector scheme

• Hilber-Hughes-Taylor (HHT) implicit predictor-corrector scheme

• Generalized midpoint method

• Generalized-α method

It is difficult to recommend the optimal integration scheme because the number of nonlinear problems
is so large. However, studies show some behaviors that you can use as quick guidelines:

2-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear Parameters in SOL 402: NLCNTL2 entry

• The Generalized-α schema (θ=0.55) that is enabled by default is unconditionally stable. This method
remains stable even for large time steps and without loss of accuracy.

• The Newmark schema (β=1/4, γ=1/2) has no numerical damping. It converges reasonably when the
time step is small enough. Newmark is unstable if γ < 1/2.

• The Hilber-Hughes-Taylor (α=0.05) shows moderate numerical damping and damps the high
frequencies, but without any loss of accuracy.

• The Generalized midpoint schema (θ=0.55) or the Newmark one (Newmark (β=0.5625, γ=1)) shows
strong numerical damping characteristics, but damps both the lower and higher frequencies. In
general, this is an unwanted characteristic for an integration scheme except possibly for special
applications.

The Generalized midpoint schema, with θ=0.50, shows no numerical damping.

Equilibrium iteration and convergence

On the NLCNTL2 bulk entry, you can control the equilibrium iterations and the convergence of the solve:

• You can specify the maximum number of iterations that the automatic time stepping method has to
perform to complete a time step.

• You can specify force, displacement, and energy reference levels and tolerances used in the Newton-
Raphson schema to stop the iteration process.

• While the Newton method is effective in most problems, in some specific problems, you can cope with
difficulties in convergence due to the Newton method step length.

On the NLCNTL2 bulk entry, you can then activate the line search algorithm that will control the
length of the Newton method step by minimizing the energy error or the force residue.

Note:
As the computing cost for each line search is comparable to that of an iteration, the permanent
activation of the line search can be counterproductive.

Automatic time stepping

On the NLCNTL2 bulk entry, you can:

• Choose between fixed time steps or automatic time stepping. You can also control the time step size
(minimum, maximum, increase ratio).

• Control the negative or zero pivots rejection.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-19
© 2023 Siemens
 2. User Interface

• Control the viscous material integration.

Internal restart options

Internal restarts start a specified subcase with the computation state (displacements, velocities, stresses,
state variables, and so on) of a preload, static, or dynamic subcase during the same solve. For example,
you might want to start several non-sequentially dependent (NSD) subcases with the results of a bolt
preload subcase. Similarly, you can start other NSD subcases with the results of a dynamics subcase.

You can use the RSUB parameter to select the subcase you want to restart from.

Note:
This restart should not be confused with the external restart that starts a new run from a
computation state loaded from a previous solve. For more information on this restart, see SOL
402 Restart.

Contact options

On the NLCNTL2 bulk entry, you can define specific parameters for contact conditions, such as the
characteristic length of the contact or the relaxation factor.

Format

1 2 3 4 5 6 7 8 9 10
NLCNTL2 ID PARAM1 VALUE1 PARAM2 VALUE2 PARAM3 VALUE3
PARAM4 VALUE4 PARAM5 VALUE5 -etc-

Example

SUBCASE 1
LABEL = Subcase - Nonlinear Dynamics 1
NLCNTL = 101
TSTEP = 101
ANALYSIS = DYNAMICS
SEQDEP = YES
....
NLCNTL2 101 AUTOTIM ON DTMAX0.010000 TETA0.600000 +
+ TINTMTH MGENALP

For more information, see the NLCNTL2 bulk entry in the Simcenter Nastran Quick Reference Guide.

2-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Solver Support

2.6 Solver Support

Solver support for SOL 401

You can select a different solver type for symmetric and unsymmetric problems:

• The symmetric solver choices are the sparse direct solver (default), the element iterative solver, the
PARDISO solver, and the MUMPS solver. You use the SOLVER parameter on the NLCNTL bulk entry to
select the symmetric solver.

• The unsymmetric solver choices are the sparse direct solver, the PARDISO solver (default), and the
MUMPS solver. You use the USOLVER parameter on the NLCNTL bulk entry to select the unsymmetric
solver.

You can request a different solver from one subcase to the next, but with the following exceptions.

• The dynamics subcase doesn’t support the element iterative solver. If the element iterative solver is
requested for a dynamics subcase, it will revert to the sparse solver.

• The normal modes, cyclic modes, and Fourier modes subcases always use the sparse solver, and
ignore the solver selection.

By default, the software automatically selects either the symmetric or unsymmetric solver at each
iteration depending if unsymmetric terms actually exist and how significant those terms are. Contact
friction and damping defined for dynamics can create unsymmetric terms. Solving with unsymmetric
matrices is more costly. You can eliminate the unsymmetric terms and solve with a symmetric solver
when the unsymmetric terms are not significant to the result and/or convergence.

You use the FSYMTOL, KSYM and KSYMTOL parameters on the NLCNTL bulk entry to control if the
unsymmetric terms are included.

Additional information:

• The sparse direct solver is a robust and reliable option, well-suited to sparse models where accuracy is
desired.

• The element iterative solver performs well with solid element-dominated models. It may be a faster
choice if lower accuracy is acceptable. You can optionally define the SMETHOD case control command
and the ITER bulk entry to alter any of the default options available on the ITER entry.

• For problems involving contact and 3D solid elements, the element iterative solver is generally faster
as compared to the sparse direct solver.

• The PARDISO solver is a hybrid direct-iterative solver, potentially faster with larger numbers of cores
than the sparse solver but with slightly lower accuracy. See Memory assignment.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-21
© 2023 Siemens
 2. User Interface

Solver support for SOL 402

You select the solver with the RESO parameter on the NLCNTLG bulk entry, and the software uses your
selection for either symmetric and unsymmetric problems. The solver choices are the MUMPS solver,
sparse direct solver, and the skyline solver. MUMPS is used by default for all run types (sequential, SMP,
and DMP). SOL 402 does not support the element iterative solver.

For the statics, dynamics, and preload subcases, you can use the INLY parameter on the NLCNTLG bulk
entry to request the symmetric or the unsymmetric version of the solver you selected with the RESO
parameter. The software uses the symmetric version by default.

The buckling, normal modes, cyclic normal modes, and Fourier normal modes subcases always use the
symmetric solver.

You can consider requesting the unsymmetric version when matrices are actually unsymmetric. For
example, contact friction can produce an unsymmetric stiffness. When INLY=0, matrices are forced to be
symmetric. When INLY=1, the full matrices are used regardless if unsymmetry exists or not.

2-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Parallel support

2.7 Parallel support

Parallel support for SOL 401

SOL 401 supports distributed-memory parallel processing (DMP) and shared-memory parallel processing
(SMP).

• You can request shared-memory parallel processing using the PARALLEL or SMP nastran keyword.
This keyword sets the number of MKL threads.

You can run Shared Memory Parallel (SMP) on a single machine with multiple processors and cores.
SMP does not require a special license. If you are licensed to run a solution with the serial option (that
is, no parallel options), then you can run the same solution with SMP.

SMP occurs for lower level operations such as matrix decomposition and matrix multiplication. Each
SMP thread shares common memory and I/O. You request SMP by defining the number of threads
with the parallel (or smp) keyword.

We recommend that you always run with SMP if your hardware has multiple physical processors. If
your hardware has the same or more physical processors than the number of threads you request with
the parallel keyword, you will not see slower performance running with SMP. In general, you should
see improved performance with SMP as compared to a serial run.

Note that if you request more threads than your physical number of processors, the run will continue
but with virtual threads. Running with virtual threads can reduce the performance.

• You can request distributed-memory parallel processing using the DMP nastran keyword and nrec for
RDMODES. This keyword sets the number of CPUs to use.

No license is required when DMP≤4. When DMP>4, you do need a DMP license.

You can run DMP on a single machine with multiple processors, or multiple machines each with one
or more processors communicating over a network.

The .f06 file will include a message similar to the following indicating the number of processors used
by the solution:

NUMBER OF PROCESSORS USED.....(NPROC) = n

The DMP methods divide the FE model into geometric and frequency parts to be solved
simultaneously. Each process works on its own partition of the geometry or frequency range, it uses
its own memory, and does I/O independently. You request DMP by defining the number of processes
with the following keywords:

DMP may be combined with SMP, so that each DMP process uses multiple SMP threads.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-23
© 2023 Siemens
 2. User Interface

See "Chapter 6, Methods for Multi-step Nonlinear Solution" in the Simcenter Nastran Parallel
Processing Guide.

Parallel support for SOL 402

SOL 402 supports distributed-memory parallel processing (DMP) and shared-memory parallel processing
(SMP).

• You can request shared-memory parallel processing using the PARALLEL or SMP nastran keyword.
This keyword sets the number of MKL threads.

SMP does not require a special license. If you are licensed to run a solution with the serial option (that
is, no parallel options), then you can run the same solution with SMP.

• You can request distributed-memory parallel processing using the MPI402 nastran keyword. This
keyword sets the number of CPUs to use.

No license is required when MPI402≤4. When MPI402>4, you do need a DMP license.

The .f06 file will include a message similar to the following indicating the number of processors used
by the solution:

NUMBER OF PROCESSORS USED.....(NPROC) = n

The DMP keyword provides no function in SOL 402.

• See "Chapter 6, Methods for Multi-step Nonlinear Solution" in the Simcenter Nastran Parallel
Processing Guide.

Combining DMP and SMP processes in SOL 402

When combining DMP and SMP, each DMP process will spawn the number of threads as specified by the
PARALLEL (or SMP) keyword.

Each DMP process will allocate its own memory, whereas the threads are sharing the same memory
without any significant increase.

The total amount of memory specified by the memory keyword will, by default, be divided by two times
the number of DMP processes because for each DMP process, the main executable and the MUMPS
solver used to solve the system of equations in parallel will both allocate the same amount of memory.
In case the computation runs on multiple hosts, the memory will be divided by two times the maximum
number of DMP processes on any given host.

In case the default memory allocation for the main executable and MUMPS is not satisfactory,
particularly if MUMPS does not have enough memory to work in-core but needs to work out-of-core,
the amount of memory received by the MUMPS solver can be adjusted by setting the mumpsmem=n
keyword, where n is an integer between 1 and 99 (default = 50).

2-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Parallel support

MUMPS prints in the .f06 file an estimate of the memory needed at the start of the run for both
in-core and out-of-core solutions. If possible, you should adjust the mumpsmem keyword so that the
memory shown in the ( ZONE OR MUMPS_MAX_MEM ) row is greater than the memory in the IN CORE
FACTORIZATION row, with a margin of safety. The following .f06 file examples demonstrate the in-core
and out-of-core listings:

In-core example:

Out-of-core example:

At the end of the .f06 file, the maximum amount of memory that was actually used by any DMP process
is also listed:

For best performance, you should:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-25
© 2023 Siemens
 2. User Interface

• Increase the total memory allocated by Nastran up to the machine’s memory if possible, unless you
want to keep some available for other tasks.

• Choose the highest number of DMP processes that can fit in the total memory allocated by the
solution.

• Ensure that each DMP process has enough memory for the given problem. If not, an error message
will appear in the .f06 file that will give the amount of memory needed.

If the memory cannot be increased, the number of DMP processes must be decreased.

• Make sure that the number of DMP processes multiplied by the number of threads is at most equal to
the number of cores on the machine.

This is the case if all DMP processes are located on the same machine. If they are spread over a cluster
of machines, then you should ensure that the number of DMP processes on each single machine
multiplied by the number of threads is at most equal to the number of cores on that machine.

2-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Memory assignment

2.8 Memory assignment

SOL 401 - Memory assignment

The MUMPS and Sparse solver both use the memory you request with the memory keyword. The state
variables and solution vectors are written to the scratch file during the solution, so that storage does not
compete with the solver for in core memory.

For the MUMPS and Sparse solvers, by default, SOL 401 allocates the memory you request with
the memory keyword as described in Managing Memory in the Simcenter Nastran Installaton and
Operations Guide.

If you are running SOL 401 with DMP, see section "2.4.4 - Memory assignment" in the Simcenter Nastran
Parallel Processing Guide for information on memory allocation.

For the Paradiso solver, SOL 401 allocates a percentage of its open core memory to the solver. By
default, 75% of Simcenter Nastran open core memory is allocated to the Paradiso solver. You can use the
system cell 734 to change this percentage. For example, the system cell setting SYSTEM(734)=80 will
request 80% of the available Simcenter Nastran open core memory.

You can revert to the behavior before Simcenter Nastran 2020.1 by defining SYSTEM(735)=1. That is,
when SYSTEM(735)=1 is defined, the Paradiso solver will use the available in-core memory that is not
allocated to any application, including Simcenter Nastran.

SOL 402 - Memory assignment

For larger problems, the computation part of SOL 402 will need much more memory than what is
required for input data processing.

By default, the software allocates half of the total memory you specify with the memory keyword to the
main executable and the other half to the MUMPS solver.

You can adjust the percentage of memory allocated to MUMPS with the mumpsmem=n keyword, where
n is an integer between 1 and 99 (default = 50). This is particularly useful if MUMPS does not have
enough memory to work in-core.

Before Simcenter Nastran starts MUMPS, it prints the following message to the .f06 file showing the
percentage of memory allocated:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-27
© 2023 Siemens
 2. User Interface

After MUMPS starts, the software prints the MUMPS memory estimation to the .f06 file. The following
examples demonstrate this output for both in-core and out-of-core solutions. If possible, adjust the
mumpsmem keyword so that the memory shown in the (ZONE OF MUMPS_MAX_MEM) row is greater
than the memory in the IN CORE FACTORIZATION row, with a margin of safety.

SOL 402 - In-core example:

SOL 402 - Out-of-core example:

You can optionally use the environment variable NXNS_MEMORY to specify in MB the memory used for
the computation. NXNS_MEMORY overrides the memory requested with the memory keyword.

Environment Variable Description

NXNS_MEMORY Specifies memory in MB for the solution only.

2-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Memory assignment

Note:
When defining NXNS_MEMORY, include the numerical value in MB, but do not include the "MB"
text describer.
For example:

• Valid definition:
NXNS_MEMORY=4000

• Invalid definition:
XNS_MEMORY=4000MB

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-29
© 2023 Siemens
 2. User Interface

2.9 SOL 402 - Intentional job termination

A SOL 402 job may be terminated at any equilibrium iteration (or time step) by modifying the RUN
file NAME_PID_me.run, where NAME is the input file name and PID is a unique number defined by the
software.

To dynamically update any numerical parameter for the next time step, the software reads the content
of this file at the end of every computation time step, up to the EXIT line. In particular, moving the line
containing ISTO before the EXIT line and setting this parameter to 999 will stop the computation. When
you do this instead of killing the job, you ensure that all results are saved and all files are properly closed.

2-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Subroutine to monitor solution progress

2.10 SOL 401 - Subroutine to monitor solution progress

The external subroutine NUSOL is available for SOL 401, which you can use to monitor the status of each
solution/time point. Simcenter Nastran sends the subroutine some basic solution/time point information
and status at the start and end of each solution/time point and subcase. You can use the information
provided to the subroutine, for example, to make a decision at each solution/time point whether to
continue or stop the solution.

The source code for the subroutine is available for you to customize. A compiled version of the
subroutine is available for you to use with SOL 401. You can activate the subroutine with the system cell
setting SYSTEM(736)=2. When the subroutine is activated, you will see that the same data sent to the
subroutine is also in the .f06 file. Each set of data will begin with the variable IRET. For example:

^^^

^^^**********************************************************************
***************************
^^^* STATICS
SOLUTION *
^^^* SUBCASE ID :
25 *
^^^* SEQDEP :
NO *
^^^* SUBCASE START TIME :
0.000000E+00 *
^^^* SUBCASE END TIME :
1.000000E+00 *

^^^**********************************************************************
***************************
^^^
^^^
TEST FOR NUSOL, IRET 1
TEST FOR NUSOL, SUBCASE_ID 25
TEST FOR NUSOL, ANALYSIS_TYPE 1
TEST FOR NUSOL, DTIME_BEGIN 0.200000000000000
^^^

• IRET has the following meanings:

=1 Beginning of the current subcase.

=2 Beginning of the current time step.

=3 End of the current time step.

=-3 End of the current time step with error (no convergence)

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-31
© 2023 Siemens
 2. User Interface

=4 End of the current subcase

=5 End of the analysis.

• ANALYSIS_TYPE has the following meanings:

=1 Statics

=2 Dynamics

=3 Modal

=4 Preload

=5 Cycmodes

=6 Fourier

Demonstration models

Demonstration models are available in the Simcenter Nastran installation as shown below. Note that all
the models are integrated into a single library.

• On Windows:
Compiled Fortran code: installation_location\scnas\em64tntl\libusol_usolf.dll
Compiled C code: installation_location\scnas\em64tntl\libusol_usolc.dll

• On Linux:
Compiled Fortran code: installation_location\scnas\x86_64linuxl\libusol_usolf.so
Compiled C code: installation_location\scnas\x86_64linuxl\libusol_usolc.so

NUSOL interface

Simcenter Nastran will call the NUSOL subroutine, which serves as the entry point to the user defined
solution/time information. You must create a shared library (DLL/SO file) from this routine, which will
then be used by Simcenter Nastran.

The arguments of NUSOL are detailed below. Simcenter Nastran expects that the real, integer and
character values passed from the argument list are of precision REAL*8, INTEGER*8 and CHARACTER
(LEN=8).

SUBROUTINE NUSOL(SUBCASE_ID, ANALYSIS_TYPE, DTIME_BEGIN,

$ DSTEP_BEGIN, DTIME_END, DSTEP_END, TIME_END,
$ STEP_END, IRET )

SUBCASE_ID......RETURN VALUE FOR SUBCASE ID (Output, Integer)

ANALYSIS_TYPE...RETURN VALUE FOR ANALYSIS TYPE (Output, Integer)

2-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Subroutine to monitor solution progress

ANALYSIS = STAT ANALYSIS_TYPE=1 STATICS

ANALYSIS = DYNA ANALYSIS_TYPE=2 DYNAMICS
ANALYSIS = MODE ANALYSIS_TYPE=3 Normal Modes
ANALYSIS = PREL ANALYSIS_TYPE=4 Bolt Preload
ANALYSIS = CYCM ANALYSIS_TYPE=5 Cyclic Modes
ANALYSIS = FOUR ANALYSIS_TYPE=6 Fourier Modes

DTIME_BEGIN.....RETURN VALUE FOR TIME INCREMENT AT THE BEGINNING OF EACH

TIME STEP
FOR STATICS/DYNAMICS SUBCASES (Output, Real)
DSTEP_BEGIN.....RETURN VALUE FOR STEP INCREMENT AT THE BEGINNING OF EACH
LOAD STEP
FOR PRELOAD SUBCASE (Output, Real)

DTIME_END.......RETURN VALUE FOR TIME INCREMENT AT THE END OF EACH TIME

STEP (Output, Real)
DSTEP_END.......RETURN VALUE FOR LOAD INCREMENT AT THE END OF EACH LOAD
STEP (Output, Real)

TIME_END........RETURN VALUE FOR TIME AT THE END OF EACH SUBCASE

(Output, Real)
STEP_END........RETURN VALUE FOR LOAD AT THE END OF EACH SUBCASE
(Output, Real)

IRET............IDENTIFICATION OF LOCATION FOR CALLING NUSOL (Output,

Integer)
IRET=1 -> CALL NUSOL AT BEGINNING OF CURRENT SUBCASE.
IRET=2 -> CALL NUSOL AT BEGINNING OF CURRENT TIME STEP.
IRET=3 -> CALL NUSOL AT END OF CURRENT TIME STEP
CONVERGED.
IRET=-3 -> CALL NUSOL AT END OF CURRENT TIME STEP WITH
ERROR.
IRET=4 -> CALL NUSOL AT END OF CURRENT SUBCASE.
IRET=5 -> CALL NUSOL AT END OF THE ANALYSIS.

Build instructions

You can develop the external routine using FORTRAN or C, and compile for Windows or Linux operating
systems.

Before you use NUSOL, you must build your own shared library to create a *.dll file on Windows or an .so
file on Linux. Simcenter Nastran will link to this shared library for data exchange. You will need to have
the Fortran or C compiler to compile the corresponding source code.

Source code examples are included with the Simcenter Nastran installation at the following locations.

• Source code written in C can be found at:

installation_location\scnas\usol\usolc\

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 2-33
© 2023 Siemens
 2. User Interface

• Source code written in FORTRAN can be found at:

installation_location\scnas\usol\usolf\

Once your makefile is correctly defined and your compiler is configured, a shared library of libusol.dll/
libusol.so can be built. The table below lists the build commands and shared libraries for Windows and
Linux.

Platform Build Command Shared Library

Windows nmake libusol.dll libusol.dll
Linux make libusol.so libusol.so

Specifying the user library location

There are four ways, in the following order of precedence from high to low, in which you can point
Simcenter Nastran to the location of your user-defined library.

1. You can define the keyword usollib on the command line when running your job. For example,

nastran.exe usollib=D:/workdir/libusol.dll input_file.dat

2. You can define the keyword usollib in your RC file. For example,

usollib=D:/workdir/libusol.dll

3. You can define the environment variable NXN_USOL_LIB. For example,

set NXN_USOL_LIB=D:/workdir/libusol.dll

4. You can replace the following files with your compiled routine:

• On Windows:
installation_location\scnas\em64tntl\libusol.dll

• On Linux:
installation_location\scnas\x86_64linuxl\libusol.so

2-34 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 3. Subcase Types
3.1 Subcase analysis type

The ANALYSIS case control command defines the subcase analysis type. SOL 401 and SOL 402 allow any
combination of the subcase types. See SOL 401 - Subcase sequencing.

• Nonlinear static subcase: You include ANALYSIS=STATICS in a subcase.

• Nonlinear dynamic subcase (includes damping and inertia effects): You include ANALYSIS=DYNAMICS
in a subcase.

• Preload subcase: You include ANALYSIS=PRELOAD in a subcase.

• Modal subcase: You include ANALYSIS=MODES in a subcase.

• Cyclic Normal Modes: You include ANALYSIS=CYCMODES in a subcase.

• Fourier Normal Modes: You include ANALYSIS=FOURIER in a subcase.

• Modal frequency response (SOL 401 only): You include ANALYSIS=MFREQ in a subcase.

The ANALYSIS case control command does not have a default in SOL 401 or SOL 402. You must define it
in every subcase, and it cannot be defined globally.

Additional subcase types

SOL 401 supports the modal frequency response subcase. You include ANALYSIS=MFREQ in a subcase.

SOL 401 also supports the nonlinear buckling subcase. Nonlinear buckling in SOL 401 is defined with the
ANALYSIS=STATIC subcase type. See Nonlinear buckling (SOL 401).

SOL 402 also supports the following subcase types.

• Buckling modes subcase (incremental stability). You include ANALYSIS=BUCKLING in a subcase.

ANALYSIS=BUCKLING must follow a ANALYSIS=STATICS.

For more information, see Linearized buckling (SOL 402).

• Complex modes subcase. You include ANALYSIS=CEIG in a subcase.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-1
© 2023 Siemens
 3. Subcase Types

3.2 Dependent and independent subcases

Sequentially dependent subcase in SOL 401

You can use the SEQDEP case control command to define any subcase type as sequentially dependent
(SD), or non-sequentially dependent (NSD).

Using the SEQDEP command in SOL 401

• SEQDEP=YES (default) – the subcase is an SD subcase.

An SD subcase uses the final computation state from the previous static, dynamic, or preload
subcase for its starting state (for example, stress, strain, and displacements). That is, it is sequentially
dependent on these subcase types.

SOL 401 uses time as the variable to increment temperatures and loads. An SD static, dynamic, or
preload subcase uses the end time from the previous static, dynamic, or preload subcase for its start
time. See Defining Solution Time Steps (SOL 401) and SOL 401 - Subcase sequencing.

• SEQDEP=NO – the subcase is a NSD subcase.

The NSD subcase does not use any computation state from any previous subcase, regardless of the
parameter settings on the NLCNTL bulk entry. An NSD subcase allows you to reset the problem back to
the initial state.

In addition, the start time for a static, dynamic, or preload NSD subcase is reset to 0.0. See Defining
Solution Time Steps (SOL 401).

For example, you can define a sequence of SD static subcases to increment loads, then define an NSD
static subcase to start a new load sequence, which is then followed by more SD static subcases to
sequence the new load scenario.

Sequentially dependent subcase in SOL 402

You can use the SEQDEP case control command to define any subcase type as sequentially dependent
(SD), or non-sequentially dependent (NSD).

SOL 402 uses time as the variable to increment loads. Both SD and NSD subcases in SOL 402 use the
final time from the previous subcase for their start time.

Using the SEQDEP command in SOL 402

• SEQDEP=YES (default) - the subcase is an SD subcase.

An SD subcase uses the final computation state from the previous subcase for its starting state (for
example, stress, strain, and displacements).

3-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Dependent and independent subcases

An SD subcase ignores the RSUB parameter on the NLCNTL2 bulk entry.

• SEQDEP=NO - the subcase is an NSD subcase.

By default, an NSD subcase does not use a previous computation state for its starting state. However,
an NSD subcase can optionally reload the computation state from the end of any previous subcase
using the RSUB=n parameter of the NLCNTL2 bulk entry, where n can be -1, 0, or >0:
-1 Same behavior as SEQDEP=YES.
0 Subcase does not use a computation state from a previous subcase for its starting
state (default for SEQDEP=NO).
>0 Restart from the end of subcase n, where n references a previous subcase number.

For more information on defining times steps in SOL 402, see Solution time steps (SOL 402).

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-3
© 2023 Siemens
 3. Subcase Types

3.3 SOL 401 - Subcase sequencing

By default, a subcase's initial condition is the end state of the previous static, dynamic, or preload
subcase. That is, it is sequentially dependent on these subcase types. See Dependent and independent
subcases.

Sequentially dependent subcases allow you to:

• Apply or remove mechanical loads, thermal loads, bolt preloads, contact/glue conditions, and
elements in a specific sequence in the statics, dynamics, and preload subcases. This sequence can
replicate a real sequence of events, for example, allowing contact conditions to become established,
applying a bolt tightening sequence, applying thermal loads from a braking scenario, and then
applying mechanical loads.

Solutions that include nonlinear conditions are path dependent. That is, the order of the loads
and constraint conditions change the outcome. The available nonlinear conditions include large
displacements, large strain, nonlinear materials, and contact conditions.

Large displacements and large strain must remain on or off for the entire solution. You must define
the parameter settings to turn on or off large displacements (LGDISP) or large strain (LGSTRN) in the
bulk data section of the input file. These settings apply to all static, preload, and dynamic subcase for
the entire solution.

You can turn on and off the creep and plastic material nonlinear effects in a subcase using the CREEP
parameter and the PLASTIC parameter, respectively. You define these parameters on the NLCNTL bulk
entry. Note that you must also define the MATNL parameter to +1 in the bulk data section of the input
file to turn material nonlinear effects on.

You can apply, modify, or remove contact conditions in a subcase by including (or not including) a
unique BCTSET=n case control command in the subcase.

• Change subcase type. See Subcase analysis type.

For example, you can sequence loads in statics, dynamics, and preload subcase types to prestress
the structure. You can include a normal modes, cyclic modes, or a Fourier modes subcase type after
the load application, and the software will solve for the modes while the structure is in a prestressed
state. The effects of stress stiffening, follower stiffness, and spin softening are included in the modes
subcase types by default.

• Change the constraint conditions. You can select new SPC=n and MPC=n sets in each subcase. Be
aware that new constraint conditions can change the problem and compromise equilibrium. If a
change in constraints is drastic and abrupt, the problem may not converge.

• Help convergence by limiting the load increments and resulting changes to the problem in a single
subcase. You can reduce the problem in each subcase by spreading the changes across multiple
subcases. Examples include adding or removing loads, contact, and elements. For example, it can be
helpful to activate contact conditions in a subcase while other loads are held constant. For this case,

3-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Subcase sequencing

you can use a preload subcase type to resolve the contact interference condition before continuing to
a static or dynamic subcase for mechanical and thermal load applications.

• Help convergence by setting specific nonlinear control parameter and contact control parameter
settings at the subcase level. For example, you might only need the contact stabilization damping
(CTDAMP) in a subcase in which contact conditions are becoming established.

• Change the frequency of output and to turn on or off specific types of output. You control the
frequency of output using the NOUT field on the TSTEP1 entry selected for each subcase. For example,
you might request output for only the final time step in some subcases, and then request output for
all time steps in the final subcase. You can also turn off the request of output in a subcase that was
previously requested in the global case. For example, if DISPLACEMENT=ALL is requested in the global
case, you can include DISPLACEMENT=NONE to override the global setting.

The table lists the subcase types for load application, and the subcase types for modal analysis.

Subcases for load application Subcases for modal analysis

Static Normal Modes
Transient Dynamics Cyclic Modes
Preload (Constant time nonlinear Fourier
static)

You can sequence loads and constraints in the Subcases for load application:

• The static subcase solves for static equilibrium, and time is used for sequencing loads. Displacements
represent the degrees-of-freedom in a static subcase. Dynamic effects are not included, but the
time-assigned loads that you request with the DLOAD=n command have consistent inputs for the
static and dynamic subcases. The software resolves inertia forces such as gravity, rotational velocity,
and rotational acceleration to static loads. See Loads.

A constant-time subcase has the same start and end time. A static subcase can have a constant time
only if it is defined with an end time equal to 0.0. See Defining Solution Time Steps (SOL 401).

The static subcase can be combined with the DYNAMICS, PRELOAD, MODES, CYCMODES, and FOURIER
subcase types.

• The dynamic subcase solves for dynamic equilibrium in the actual time domain. This subcase
includes dynamic effects such as inertial forces, damping, and momentum. Displacement, velocity,
and acceleration represent the degrees-of-freedom in a dynamic subcase.

For details on sequencing dynamic subcases, see "Subcase sequencing" in Transient dynamic
subcase.

• The preload subcase solves for static equilibrium, but with time held constant. You can include a
preload subcase anywhere in a sequence. The preload subcase allows you to preload a bolt, add or
modify a contact condition, add or modify a thermal load, or add a new element to the problem. New

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-5
© 2023 Siemens
 3. Subcase Types

service loads defined with the LOAD=n or DLOAD=n are ignored in a preload subcase. However, when
you apply these loads in a previous static or dynamic subcase, the software holds them constant for
the preload subcase.

Because the preload subcase allows new thermal load sets and contact sets, to retain these sets
through a preload subcase, you must define them either globally or in the preload subcase.

When you define a bolt preload load set using the BOLTLD=n command, it needs only to be defined in
the preload subcase. The software retains the bolt preload status in the consecutive static or dynamic
subcases. You should not redefine the BOLTLD=n command in these subcases.

You must define contact conditions and thermal loads in every consecutive subcase in which you
would like to include them. For example, if you define a contact set with the BCTSET=5 command in
a preload subcase, and you want to include this definition in all consecutive static subcases, you must
include the BCTSET=5 command in these subcases. If you want to include the same contact set in
every subcase, you can define the contact set globally.

Although a preload subcase has a constant time, you still must reference a TSTEP1 bulk entry in the
preload subcase with an end time (Tend1) that is the same as the start time for that subcase. You
should define the number of increments (INC) on the TSTEP1 entry, and the software increments bolt
preload, contact, or a thermal load defined for that subcase.

You can combine the preload subcase with the STATICS, DYNAMICS, MODES, CYCMODES, and
FOURIER subcase types.

When you include the subcases for modal analysis in a sequence of subcases for load application, the
modal analysis uses the final stiffness state of the previous static, dynamics, or preload subcase.

Note that a sequentially dependent (SEQDEP=YES) modes subcase (ANALYSIS=MODES, CYCMODES, or

FOURIER) cannot follow a dynamic subcase (ANALYSIS=DYNAMICS). Doing so will result in a fatal error.

Global versus Subcase Behavior

The case control commands that are listed prior to the first subcase in the input file are defined globally.
The case control commands defined globally are inherited by all the applicable subcases. However, if a
subcase contains a case control command of the same name as one that is included in the global case,
the subcase specification of the case control command takes precedence. In other words, the two case
control specifications are not additive.

For example, suppose that LOAD=5 is defined globally, and LOAD=7 is defined in a static subcase. For
that static subcase, the software uses the LOAD=7 definition and ignores the LOAD=5 definition. Another
static subcase that does not have a LOAD=n command will use the global LOAD=5 definition. If the
input file also includes modes subcase types (MODES, CYCMODES, and FOURIER), because the LOAD=n
command is not applicable to these subcases, they will ignore it.

Time-unassigned mechanical load sets that you define using the LOAD=n command, and time-assigned
mechanical load sets that you define using the DLOAD=n command are distinct load types. The software

3-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Subcase sequencing

applies both time-unassigned and time-assigned load sets in the statics and dynamics subcase types
when both are defined.

Time-unassigned thermal load sets that you define using TEMP(LOAD) command and time-assigned
thermal load sets that you define using DTEMP command are also distinct load types. If you specify both
DTEMP and TEMP(LOAD), only the last one defined is applied. For example, if you define the TEMP(LOAD)
command globally, and you define the DTEMP command in a subcase, the DTEMP command is used for
that subcase.

Load and contact increments

Nonlinear solutions converge better when the changes to the problem occur in controlled increments.
Examples of changes includes loads, deformations, and contact.

The following explains how the software increments these changes.

• Mechanical load increments

Time-unassigned mechanical loads that you request using the LOAD=n case control command are
ramped by the number of increments (Ninc) on the TSTEP1 entry defined for the subcase, by default.

If a previous static or dynamic subcase included a LOAD=n definition, the current subcase begins with
the final LOAD=n definition from the previous subcase and ends with the LOAD=n definition defined in
the current subcase. The software ramps the time-unassigned load from the load's beginning value to
its final value by the number of increments (Ninc).

Time-assigned mechanical loads that you request using the DLOAD=n case control command are
incremented according to the load definition with the TLOADi and TABLEDi bulk entries, and the
TSTEP1 bulk entry defined for the subcase. Time-assigned mechanical loads do not consider a
DLOAD=n defined in a previous subcase.

See Mechanical Loads (SOL 401).

• Thermal load increments

Time-unassigned thermal loads that you request using the TEMP(LOAD)=n case control command are
ramped by the number of increments in a subcase, by default.

Time-assigned thermal loads that you request using the DTEMP=n case control command are
incremented according to the load definition with the DTEMP or DTEMPEX bulk entries, and the
TSTEP1 bulk entry defined for the subcase. See Thermal Loads.

• Bolt preload increments

You must define bolt preloads in a preload subcase type that has a constant time. The incrementing of
bolt preloads depends on whether you have defined a bolt sequence with the BOLTSEQ bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-7
© 2023 Siemens
 3. Subcase Types

When you do not define a BOLTSEQ bulk entry, all bolt preloads, temperature loads, and contact initial
interference are incremented by the number of increments defined with the Ninc field on the TSTEP1
defined in the preload subcase.

When you define a BOLTSEQ, you use the number of increments (Ninc) on the BOLTSEQ entry to
increment the bolt preloads. The software ignores the number of increments (Ninc) on the TSTEP1
entry for this case. The temperature loads and contact initial interference are incremented at the
same time as the first bolt listed on the BOLTSEQ entry using the Ninc value defined for that bolt. The
software holds the temperature loads and contact conditions constant when incrementing the other
bolts in the sequence.

• Contact increments

The TZPENE parameter on the BCTPARM bulk entry is available to ramp the removal of initial contact
interference for time-assigned subcases. For example, this capability may be useful if you have
modeled interfering contact surfaces to represent a press fit condition.

Use the TZPENE parameter to define the end time when initial contact interference will be eliminated.

For example, if a subcase start time is 5.0, end time is 10.0, and TZPENE=7.2, the initial contact
interference will be eliminated starting from the beginning of the subcase at time=5.0 until time=7.2.

The IPENRAMP parameter on the BCTPARM bulk entry is available to request for the software to ramp
or not ramp the removal of initial contact interference for a constant time subcase. For example,
a preload subcase is a constant time subcase. You define the number of increments (INC) on the
TSTEP1 entry referenced in the subcase, and the software will ramp the contact interference by those
increments.

Restarts

A restart solution is a method of continuing from a previous run without having to start from the
beginning. For example, an initial run could create a pre-stressed condition as a result of a preload
subcase to allow contact conditions to become established, followed by another preload subcase for the
application of bolt preloads. You can then use the restart file created from the initial run in repeated
restart solutions. The restart solution begins at the state from the initial run and can continue with a
sequence of more subcases for mechanical and thermal load application.

See SOL 401 Restart.

Input example

The following case control example includes a sequence of sequentially dependent subcase types.
Because subcases are sequentially dependent by default, you do not need to define the SEQDEP case
control command.

3-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Subcase sequencing

Type Input syntax Description

$ EXECUTIVE CONTROL
SOL 401
CEND
$ CASE CONTROL
Global TEMP(INIT)=1 Case control commands defined here apply to all subcases
commands DLOAD=300 unless you redefine the command in a subcase.
DTEMP=502
TEMP(INIT)=1 defines a global initial temperature set. When
SPC=100
you have thermal loads, the initial temperature set must be
BCTSET=7
the same for all subcases.
The DLOAD=300 defines a global time-assigned load set.
The DTEMP=502 defines a global time-assigned thermal load
set.
The BCTSET=7 defines a global contact set.
The SPC=100 defines a global constraint set.
DISPLACEMENT=ALL These commands are global output requests. You can request
SPCFORCES=ALL additional output or redefine any of these commands in the
STRESS=ALL subcases.
Subcase $ Preload Subcase This preload subcase establishes the contact set (eliminates
commands SUBCASE 1 initial interference conditions) requested with the global
ANALYSIS=PRELOAD BCTSET=7 command.
TSTEP=100
Although a preload subcase has a constant time, you still
must include a TSTEP command to select a TSTEP1 bulk entry
that is defined with a constant time. This is still the start of
the solution time stepping, so the end time is equal to 0.0.
The software ramps the contact interference by the number
of increments (INC field) defined on the TSTEP1 entry.
The thermal loads at time=0.0 that you define using
the global time-assigned thermal load set DTEMP=502 are
applied if they are non-zero.
Because new service loads are never applied in a preload
subcase, the global time-assigned mechanical load set
DLOAD=300 is ignored. You could define a constant time
static subcase with an end time=0.0 to apply service loads at
time=0.0.
$ Preload Subcase This preload subcase applies the bolt preloads that you
SUBCASE 2 requested using the BOLTLD=7 command. If the BOLTLD=7
ANALYSIS=PRELOAD command selects the BOLTLD bulk entry (and not the
BOLTLD=7 BOLTSEQ bulk entry), the software ramps the bolt preload
TSTEP=101 by the number of increments (INC field) on the TSTEP1 entry.
This is still the start of the solution time stepping, so the end
time defined on the TSTEP1 entry is equal to 0.0.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-9
© 2023 Siemens
 3. Subcase Types

Type Input syntax Description

The globally defined thermal load set DTEMP=502 remains
applied at its time=0.0 status.
The globally defined service load set DLOAD=300 is ignored
by the preload subcase.
The globally defined contact set (BCTSET=7) is still active,
and will continue to iterate if the bolt preload changes the
contact condition.
$ Statics Subcase This static subcase begins to increment time.
SUBCASE 3
The TSTEP=102 command selects a TSTEP1 bulk entry with
ANALYSIS=STATICS
an end time=20.0 and number of increments=10.
TSTEP=102
For each time increment (2.0, 4.0, 6.0, etc), the software
now begins to update the global time-assigned mechanical
load (DLOAD=300) and global time-assigned thermal load
(DTEMP=502).
The globally defined contact set (BCTSET=7) is still active,
and continues to iterate as the loading changes the contact
condition.
The bolt preload defined in SUBCASE 2 is maintained.
$ Preload Subcase This preload subcase introduces the new contact set
SUBCASE 4 BCTSET=8, which is needed to increase the contact region
ANALYSIS=PRELOAD definition, and to introduce new contact control parameters
BCTSET=8 defined on the BCTPARM bulk entry.
TSTEP=103
Because the preload subcase is a constant time subcase, the
TSTEP=103 command selects a TSTEP1 bulk entry with an
end time=20.0, which is the end time from the previous
subcase. The software ramps the contact interference by the
number of increments (INC field) on the TSTEP1 entry.
The globally defined thermal load set DTEMP=502 remains
applied at its time=20.0 status.
The globally defined service load set DLOAD=300 remains
applied at its time=20.0 status.
The bolt preload defined in SUBCASE 2 is maintained.
$ Statics Subcase This static subcase introduces the new time-unassigned load
SUBCASE 5 set defined with the LOAD=402 command. The software
ANALYSIS=STATICS ramps this loading by the number of increments (Ninc) on
BCTSET=8 the TSTEP1.
LOAD=402
The TSTEP=104 command selects a TSTEP1 bulk entry with
TSTEP=104
an end time=40.0 and number of increments=10. The start
time for this subcase is 20.0 (the end time from the previous
subcase).

3-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Subcase sequencing

Type Input syntax Description

To retain its definition, you must redefine the contact
set BCTSET=8 introduced in SUBCASE 4 in this subcase.
Otherwise, the global contact set would be reapplied.
For each time increment (22.0, 24.0, 26.0, etc), the
software again updates the global time-assigned mechanical
load (DLOAD=300) and global time-assigned thermal load
(DTEMP=502).
The bolt preload defined in SUBCASE 2 is maintained.
$ Normal Modes A normal modes solution is requested at the current state of
Subcase the nonlinear problem.
SUBCASE 6
The METHOD=103 command selects the EIGRL bulk entry
ANALYSIS=MODES
requesting the number of modes.
METHOD=103
NLCNTL=30 The NLCNTL=30 command selects a NLCNTL bulk entry with
the parameter setting KMODTN=5. This setting requests the
software to replace the final contact stiffness with a tied-
contact stiffness.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-11
© 2023 Siemens
 3. Subcase Types

3.4 Static subcase

Solutions 401 and 402 support a static subcase type to request a statics analysis. You designate the
static subcase by including the ANALYSIS=STATICS case control command in the subcase.

In a static subcase, the software solves for static equilibrium, and time is used for sequencing loads.
Displacements represent the degrees-of-freedom in a static subcase. Dynamic effects are not included,
but the time-assigned loads that you request with the DLOAD=n command have consistent inputs for the
static and dynamic subcases. The software resolves inertia forces such as gravity, rotational velocity, and
rotational acceleration to static loads.

The static subcase can be combined with the DYNAMICS, PRELOAD, MODES, CYCMODES, and FOURIER
subcase types. See SOL 401 - Subcase sequencing.

You can apply or remove mechanical loads, thermal loads, bolt preloads, contact/glue conditions, and
elements in a specific sequence in the statics, dynamics, and preload subcases. This sequence can
replicate a real sequence of events, for example, allowing contact conditions to become established,
applying a bolt tightening sequence, applying thermal loads from a braking scenario, and then applying
mechanical loads.

By default, a static subcase's initial condition is the end state of the previous static, dynamic, or preload
subcase. That is, it is sequentially dependent on these subcase types. See Dependent and independent
subcases.

The available nonlinear conditions in the static subcase includes large displacements, large strain,
nonlinear materials, and contact conditions.

Large displacements and large strain must remain on or off for the entire solution. You must define the
parameter settings to turn on or off large displacements (LGDISP) or large strain (LGSTRN) in the bulk
data section of the input file. These settings apply to all static, preload, and dynamic subcase for the
entire solution.

You can turn on and off the creep and plastic material nonlinear effects in a subcase using the CREEP
parameter and the PLASTIC parameter, respectively. You define these parameters on the NLCNTL bulk
entry. Note that you must also define the MATNL parameter to +1 in the bulk data section of the input
file to turn material nonlinear effects on.

You can apply, modify, or remove contact conditions in a subcase by including (or not including) a
unique BCTSET=n case control command in the subcase.

A constant-time static subcase has the same start and end time. A static subcase can have a constant
time only if it is defined with an end time equal to 0.0. See Solution Time Steps (SOL 401) and Solution
Time Steps (SOL 402).

3-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Preload subcase

3.5 Preload subcase

Solutions 401 and 402 support a preload subcase type to request a statics analysis but with time held
constant. You designate the static subcase by including the ANALYSIS=PRELOAD case control command
in the subcase.

You can include a preload subcase anywhere in a sequence of STATICS, DYNAMICS, MODES, CYCMODES,
and FOURIER subcase types. See SOL 401 - Subcase sequencing.

The preload subcase allows you to preload a bolt, add or modify a contact condition, add or modify
a thermal load, or add a new element to the problem. New service loads defined with the LOAD=n or
DLOAD=n are ignored in a preload subcase. However, when you apply these loads in a previous static or
dynamic subcase, the software holds them constant for the preload subcase.

Because the preload subcase allows new thermal load sets and contact sets, to retain these sets through
a preload subcase, you must define them either globally or in the preload subcase.

When you define a bolt preload load set using the BOLTLD=n command, it needs only to be defined in
the preload subcase. The software retains the bolt preload status in the consecutive static or dynamic
subcases. You should not redefine the BOLTLD=n command in these subcases. See Bolt preload (SOL
401) and Bolt preload (SOL 402).

You must define contact conditions and thermal loads in every consecutive subcase in which you would
like to include them. For example, if you define a contact set with the BCTSET=5 command in a preload
subcase, and you want to include this definition in all consecutive static subcases, you must include the
BCTSET=5 command in these subcases. If you want to include the same contact set in every subcase,
you can define the contact set globally.

Although a preload subcase has a constant time, you still must reference a TSTEP1 bulk entry in the
preload subcase with an end time (Tend1) that is the same as the start time for that subcase. You should
define the number of increments (INC) on the TSTEP1 entry, and the software increments bolt preload,
contact, or a thermal load defined for that subcase.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-13
© 2023 Siemens
 3. Subcase Types

3.6 Normal modes subcase

Solutions 401 and 402 support the normal modes subcase type to request for the software to compute
the natural frequencies and mode shapes of your structure. You designate the normal modes subcase by
including the ANALYSIS=MODES case control command in the subcase.

When you include the subcases for modal analysis (which includes the cyclic and Fourier subcase types)
in a sequence of subcases for load application, the modal analysis uses the final stiffness state of the
previous static, dynamics, or preload subcase. The previous static, dynamics, or preload subcases can
include the nonlinear conditions such as large displacements, large strain, nonlinear materials, and
contact.

For example, you can sequence loads in statics, dynamics, and preload subcase types to prestress the
structure. You can include a normal modes, cyclic modes, or a Fourier modes subcase type after the load
application, and the software will solve for the modes while the structure is in a prestressed state. The
effects of stress stiffening, follower stiffness, and spin softening are included in the modes subcase types
by default. See SOL 401 - Subcase sequencing.

The normal modes subcase should include the METHOD case control command which selects the EIGRL
bulk entry. The EIGRL entry defines the data needed to perform the real eigenvalue analysis with the
Lanczos method. For example, you can define the number of modes, the frequency range, and the
eigenvector normalization method.

If you have included contact conditions in your previous static, dynamics, or preload subcase, the final
contact stiffness is applied in the modal subcase. You can use the KMODTN parameter on the NLCNTL
bulk entry for SOL 401 or on the NLCNTL2 bulk entry for SOL 402 to adjust the contact stiffness applied
in the modal subcase.

Note that a sequentially dependent (SEQDEP=YES) modes subcase (ANALYSIS=MODES, CYCMODES, or

FOURIER) cannot follow a dynamic subcase (ANALYSIS=DYNAMICS). Doing so will result in a fatal error.

3-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Transient dynamic subcase

3.7 Transient dynamic subcase

Solutions 401 and 402 support a transient dynamic subcase type to request a direct transient response
analysis. You designate the transient dynamic subcase by including the ANALYSIS=DYNAMICS case
control setting in the subcase.

A transient response analysis computes the behavior of a structure subjected to a time-varying

excitation. The equation of motion for the dynamic subcase includes the stiffness, damping, and mass
terms with the option to output displacement, velocity, and acceleration at each degree-of-freedom.

Similar to the other subcase types, the transient dynamic subcase can optionally include geometry
nonlinear effects when PARAM,LGDISP,1 is defined, and it can include the material nonlinear effects
when plasticity, creep, and viscoelasticity are defined. A linear dynamic analysis occurs when no
nonlinear conditions are present.

You use the same inputs to define time assigned and time unassigned mechanical and thermal loads
for dynamic and static subcases. The difference is that for the dynamic subcase, the software uses time
explicitly.

Mass inputs

In the equation of motion for dynamic and modal subcases, the mass matrix is used in the inertia force
term . For the dynamic and static subcases, mass is also used to compute grid point forces from
the body loads such as gravity, angular velocity, and angular acceleration.

You can use the following inputs to define the mass properties:

• The mass matrix is automatically computed when mass density (ρ) is specified on the MATi entries
associated with the finite elements.

• Nonstructural mass per unit length can be defined on the PBAR and PBEAM entries. In addition,
nonstructural mass per unit area can be defined on the PSHELL entries.

• The CONM1 entry allows you to input a fully coupled 6x6 mass matrix. You can also define half of the
terms on the CONM1 entry for a symmetric matrix.

• The CONM2 entry defines concentrated mass and inertia terms at a grid point.

• The CMASSi bulk entries can be used to define mass at a single degree-of-freedom (DOF) when only
one DOF is referenced, or it can be used to define coupling between two DOF.

The following parameters are related to the specification of mass properties.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-15
© 2023 Siemens
 3. Subcase Types

• PARAM,COUPMASS,1 – Requests that the coupled mass option be used rather than the lumped mass
option for the elements that support the coupled mass option. By default, with the lumped mass
option, the mass of an element is divided and distributed to the grid points. With the coupled mass
option, the distributed mass is replaced by a non-diagonal mass matrix that couples the connected
grid points. The coupled mass option is sometimes more accurate, but it uses more computation time.

Note that COUPMASS controls the type of mass matrix used for the inertia term in the dynamic
equation of motion. Although, SOL 401 always computes body forces using the consistent mass
matrix independent of the PARAM,COUPMASS specification.

• PARAM,WTMASS,value – Specifies a factor by which to multiply the mass of the structure to obtain
dimensionally correct mass. For example, if the ft-lb-sec system is used, and the mass input unit is
pounds, then value = 1/32.174 = .031081. This factor operates on all mass terms.

Damping

All damping definitions for the transient subcase are applied to the viscous damping force term
in the equation of motion, where is the velocity, and is the total viscous damping matrix. The
total viscous damping is the sum of three types of optional damping inputs:

where,

• is viscous damping explicitly defined with the CDAMPi, CVISC, CBUSH, or CBUSH1D bulk entries.

• is damping proportional to the mass and stiffness matrices. The parameter ALPHA1 defines
damping proportional to the mass matrix, and the parameter ALPHA2 defines damping that is
proportional to the stiffness matrix. The proportional damping is computed as

• is structural damping, which is converted to viscous damping. For both SOLs 401 and 402, the GE
field on the MATi entry defines the structural damping for the elements that reference the material
entry. For SOL 401 only, the parameter G defines a global structural damping, which is applied to the
entire stiffness matrix.

For SOL 401, G and GE are converted to viscous damping using the parameters W3 and W4 as follows.

Where:

G is the overall structural damping coefficient (PARAM,G).

3-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Transient dynamic subcase

W3 is a frequency in radians per unit time (PARAM,W3) for the conversion of the overall structural
damping into viscous damping.

[K] is the global stiffness matrix.

GE is the element structural damping coefficient defined using the GE field on the material entries.

W4 is a frequency in radians per unit time (PARAM,W4) for the conversion of element structural
damping into viscous damping.

[KE] is an element stiffness matrix.

For SOL 402, the parameters G, W3, and W4 are unsupported inputs, and W4 is internally set to 1.0.
As a result, for SOL 402, GE is converted to viscous damping as follows.

Note that GE and G by themselves are dimensionless multipliers of the stiffness. Although, the viscous
damping explicitly defined with the CDAMPi, CVISC, CBUSH, or CBUSH1D bulk entries have damping
units.

Loads and constraints

The dynamic subcase supports the same loads and constraints as the static subcase. Specifically, both
subcases support the definition of the LOAD and the DLOAD case control commands, which reference
time-unassigned and time-assigned loads, respectively. When the time unassigned loads are defined, the
parameter LVAR on the NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk entries is available to optionally
ramp the loads by the number of increments defined on the TSTEP1 bulk entry.

Time unassigned and time assigned temperature loads are also supported for both the dynamic and
static subcases. The time unassigned temperature load is requested with the TEMP(LOAD) case control
command, and the time assigned temperature load is requested with the DTEMP case control command.
When the time unassigned temperature loads are defined, the parameter TVAR on the NLCNTL (SOL 401)
or NLCNTL2 (SOL 402) bulk entries is available to optionally ramp the temperature loads by the number
of increments defined on the TSTEP1 bulk entry.

You use the same inputs to define time assigned and time unassigned loads for dynamic and static
subcases. The difference is that for the dynamic subcase, the software uses time explicitly.

Note that a time unassigned load selected with the LOAD command is not specifically defined with a
time function. Although, when you apply a time unassigned load and choose the ramp option, it is
incremented similar to a time assigned load. For example, if you select a gravity load defined with the
GRAV bulk entry with the LOAD command and the ramp option is requested, the software will increment
the gravity from 0.0 at the start of the subcase, and then increases to its full value by the end of the
subcase. Since this is not likely your desired load application of gravity, you can either turn the ramping
off with the LVAR parameter, or you can reference your gravity load as time-assigned with the DLOAD
command, and define a constant scale factor for all time steps.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-17
© 2023 Siemens
 3. Subcase Types

See Loads in the Multi-Step Nonlinear User’s Guide.

Initial conditions

You can request initial displacement and velocity conditions for a dynamic subcase with the IC=n case
control command. The integer n on the IC case control references a TIC bulk entry. Only the PHYSICAL
option (default) on the IC command is available, which is the option for defining initial conditions on
grid points.

The IC command can be defined either in a dynamic subcase, or if all subcases include
ANALYSIS=DYNAMICS, you can define the IC command above the subcase level (globally). For either
definition, the software will only apply an initial condition to a dynamic subcase that is either the first
subcase, or if it is not the first, it must be non-sequentially dependent (SEQDEP=NO). The software
ignores an initial condition when a dynamic subcase does not satisfy these rules, and instead starts
from the state of displacement, velocity, and acceleration from the previous preload, static, or dynamic
subcase.

Subcase sequencing

The dynamic subcase can be combined with the other subcase types (STATICS, PRELOAD, MODES,
CYCMODES, FOURIER). Below are some example scenarios and exceptions.

Note that if you are incrementing time across sequentially dependent static and dynamic subcases, your
time steps must continue from one subcase to next.

• A non-sequentially dependent (SEQDEP=NO) dynamic subcase can follow any subcase. The non-
sequentially dependent dynamic subcase begins from time=0.0, and includes any initial velocity or
acceleration conditions you have defined for the subcase.

Example:

SUBCASE 1
ANALYSIS=STATICS
NLARCL=1
....
SUBCASE 2
ANALYSIS=DYNAMICS
SEQDEP=NO
....

• For SOL 401, a sequentially dependent (SEQDEP=YES) dynamic subcase can be defined before or after
the STATICS, DYNAMICS, and PRELOAD subcase types, except for a static subcase which requests a
nonlinear buckling analysis with the NLARCL=ID case control command. The sequentially dependent
dynamic subcase will start from the last converged configuration and state variables from the end of
the prior static, preload, or dynamic subcase.

Example:

3-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Transient dynamic subcase

SUBCASE 1
ANALYSIS=PRELOAD
....
SUBCASE 2
ANALYSIS=STATICS
SEQDEP=YES
....
SUBCASE 3
ANALYSIS=DYNAMICS
SEQDEP=YES
....
SUBCASE 4
ANALYSIS=STATICS
SEQDEP=YES
....
SUBCASE 5
ANALYSIS=PRELOAD
SEQDEP=YES
....
SUBCASE 6
ANALYSIS=DYNAMICS
SEQDEP=YES
....

• For SOL 401, a sequentially dependent modes subcase (ANALYSIS=MODES, CYCMODES, or FOURIER)
cannot be defined immedately after a dynamic subcase (ANALYSIS=DYNAMICS). Doing so will result in
a fatal error.

• For SOL 402, a sequentially dependent (SEQDEP=YES) dynamic subcase can be defined before or after
the STATICS, DYNAMICS, PRELOAD, MODES, CYCMODES, and FOURIER subcase types.

The sequentially dependent dynamic subcase will start from the last converged configuration and
state variables from the end of the prior static, preload, or dynamic subcase.

Example:

SUBCASE 1
ANALYSIS=PRELOAD
....
SUBCASE 2
ANALYSIS=STATICS
SEQDEP=YES
....
SUBCASE 3
ANALYSIS=DYNAMICS
SEQDEP=YES
....
SUBCASE 4

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-19
© 2023 Siemens
 3. Subcase Types

ANALYSIS=STATICS
SEQDEP=YES
....
SUBCASE 5
ANALYSIS=PRELOAD
SEQDEP=YES
....
SUBCASE 6
ANALYSIS=DYNAMICS
SEQDEP=YES
....

• Any non-sequentially dependent (SEQDEP=NO) subcase type can follow a dynamic subcase.

Example:

SUBCASE 1
ANALYSIS=DYNAMICS
....
SUBCASE 2
ANALYSIS=STATICS
SEQDEP=NO
....
SUBCASE 3
ANALYSIS=DYNAMICS
SEQDEP=YES
....
SUBCASE 4
ANALYSIS=DYNAMICS
SEQDEP=NO
....

• The cyclic symmetry boundary condition is supported by the dynamic subcase. The cyclic symmetry
definition with the CYCSET case control command must be defined above the subcases (globally) and
applies to all subcases. For the static and dynamic subcase types, the solution is performed for the 0th
harmonic only.

Example:

CYCSET=100
....
SUBCASE 1
ANALYSIS=STATICS
....
SUBCASE 2
ANALYSIS=DYNAMICS
SEQDEP=YES/NO
....

3-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Transient dynamic subcase

Output summary

The dynamic subcase supports the same output requests as the static subcase. In addition, you can also
request velocity and acceleration for the dynamic subcase. All output for SOLs 401 and 402 is in SORT1
format, including the dynamic subcase. SORT2 output is not supported.

Time integration methods

Two types of analysis can be performed with the dynamic subcase:

• When the dynamic analysis includes the stiffness, damping, and inertia terms, the general equation of
motion is as follows.

• You can optionally turn the inertial effects off for a dynamic subcase by setting the parameter
INERTIA=NO on the NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk entries. The general equation
of motion for this analysis is as follows.

At each time step, a set of linear or nonlinear equations is solved. A full or modified Newton-Raphson
strategy can be used.

The TINTMTH parameter is available on the NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk entries to
select the time integration method. In addition, the parameters BETA, GAMA, ALFA, TETA, and RHOINF
are available for SOLs 401 and 402 to define constant terms referenced in the following integration
method descriptions.

• Newmark Method (SOLs 401 and 402)

Velocity is obtained from acceleration using a generalized single step integration operator as

Equation 3-1.

A similar integration operator is used to obtain displacement as

β and γ correspond to the parameters BETA and GAMA on the NLCNTL (SOL 401) or NLCNTL2 (SOL
402) bulk entries.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-21
© 2023 Siemens
 3. Subcase Types

• β= 1/4 and γ= 1/2 correspond to the assumption of average constant acceleration over the time
step. This set of values provides the Newmark unconditional scheme with maximum accuracy.

• β= 1/6 and γ= 1/2 correspond to the assumption of linear acceleration over the time step.

Using a central difference operator for integrating velocity implies , so that we have

Equation 3-2.

From Equation 3-2, accelerations in terms of current displacements and state at t are derived as:

Equation 3-3.

Then using Equation 3-1 and the chain rule, fc can be derived as . Likewise velocities in
terms of current displacements and state at t are obtained as:

Equation 3-4.

Note that the terms within square brackets in Equations 3-3 and 3-4 only depend on displacements,
velocities and accelerations at t, and terms that contribute to the integration operator. Therefore, the
former quantities should be stored as state variables (at nodes).

Finally the corresponding residual is computed as:

The residual and Jacobian for the Newmark operator are summarized in the following figure.

3-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Transient dynamic subcase

Figure 3-1. Newmark operator

• Hilber-Hughes-Taylor (HHT) Method (SOLs 401 and 402)

The HHT integrator generalizes the Newmark operator, and in doing so, introduces a small amount of
numerical damping by weighting the residual between previous and current time step. This is done by
modifying the (residual) equilibrium equations as

where α corresponds to the parameter ALFA parameter on the NLCNTL (SOL 401) or NLCNTL2 (SOL
402) bulk entries.

Note that we can simply retain the definitions and most expressions from the Newmark operator, and
summarize the HHT operator in the following figure.

Figure 3-2. HHT operator

This procedure includes numerical damping in the high frequency spectrum. This numerical damping
has a stabilizing effect on the time integration procedure while guaranteeing very good accuracy
of integration of the low frequency range (including rigid body motion in particular). The particular
value α= 0 generates zero numerical damping (and corresponds to the classical Newmark scheme
with β= 1/4 and γ = 1/2) while α= 1/3 generates maximum damping. It is generally recommended to
use an intermediate value (α= 0.05 or α= 0.1).

• Generalized Alpha Method (SOL 401 only)

The Generalized Alpha Method modifies the Hilber-Hughes-Taylor method by rewriting the equilibrium
expression at time tn+1, then applying the time integration described with Newmark's method:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-23
© 2023 Siemens
 3. Subcase Types

where θ corresponds to the TETA parameter on the NLCNTL bulk entry.

The Newmark parameters are obtained by:

This procedure allows to introduce some numerical damping in the high frequency spectrum of the
system under consideration. This numerical damping has a stabilizing effect on the time integration
procedure while guaranteeing very good accuracy of integration of the low frequency range
(including rigid body motion in particular). To obtain maximum damping in the high frequencies
and minimum damping in the low frequencies α and θ have to satisfy the following relationship:

and θ has to satisfy .

• Generalized Midpoint Method (SOL 402 only)

This method is different from the other methods because the equilibrium equations are solved at a
time that is intermediate between time tn and time tn+1:

where θ corresponds to the TETA parameter on the NLCNTL2 bulk entry.

It consists of calculating the displacements, velocities, and accelerations at time tn+θ in terms of the
same quantities at time tn from the following expression:

Substituting the expression for the acceleration (constant per time step) into the equilibrium
equations, yields:

Using the expression for qn+1 and qn+θ = (1-θ)qn + θqn+1, we obtain:

Using now the Newton Raphson method to iteratively correct the above equation, yields:

with the residual.

3-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Transient dynamic subcase

The value of θ must be between 1/2 and 1 for this method to be unconditionally stable.

• Modified Generalized Alpha Method (SOLs 401 and 402)

The Modified Generalized Alpha Method is obtained using a vector a of acceleration-like variables in
the Newmark integration formula.

Those additional variables are related to the accelerations by the following equation:

where,

are optimal algorithmic parameters for second-order ODEs.

This procedure allows to introduce some numerical damping in the high frequency spectrum of the
system under consideration. This numerical damping has a stabilizing effect on the time integration
procedure while guaranteeing very good accuracy of integration of the low frequency range
(including rigid body motion in particular). Compare to Hilber-Hughes-Taylor method and Generalized
Alpha Method, this scheme enforces exactly equilibrium at every time step, which guaranties second-
order accuracy also for the accelerations and less sensitivity to variable time steps

Damping is controlled by the spectral radius at infinity ρ∞: an undamped scheme is characterized by
ρ∞= 1, while ρ∞= 0 provides asymptotic annihilation of the high frequency response.

The RHOINF parameter on the NLCNTL bulk entry (SOL 401) and NLCNTL2 bulk entry (SOL 402) is
available to define ρ∞.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-25
© 2023 Siemens
 3. Subcase Types

3.8 Modal frequency response subcase (SOL 401)

Frequency response analysis is used to compute the dynamic structural response to a steady-state
harmonic excitation. Examples of harmonic excitation include rotating machinery and unbalanced tires.

In frequency response analysis, the excitation is defined in the frequency domain. Excitations can be in
the form of applied forces and enforced motions (displacements, velocities, or accelerations).

You designate a modal frequency response subcase by including the ANALYSIS=MFREQ case control
setting. You must define the frequency response subcases immediately after a normal modes subcase
(ANALYSIS=MODES). Multiple frequency response subcases are supported, for example, to compute
the response from various dynamic load scenarios, forcing frequency sets, and damping values. The
frequency response subcases use the normal modes of the structure to uncouple the equations of
motion and reduce the problem size.

Note that the modal frequency response subcase cannot follow a cyclic modes subcase
(ANALYSIS=CYCMODES), although, a cyclic boundary condition is supported.

You can include a sequence of preload and statics subcases before the normal modes and frequency
response subcases. The normal modes and frequency response subcases use the nonlinear base state
computed by the preload and static subcase sequence.

For example, in the figure below, two static subcases sequence time-assigned loads and temperatures.
The normal modes subcase 3 uses the nonlinear base state at the end of statics subcase 2. The
frequency response subcase 4 also depends on the same nonlinear base state because it uses the
modes, modal stiffness, and modal mass computed in subcase 3.

3-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Modal frequency response subcase (SOL 401)

The nonlinear base state includes the deformed configuration and the total tangential stiffness at the
end of the previous statics or preload subcase. The total tangential stiffness is the sum of the following:

where,

Nonlinear material stiffness resulting from plasticity and creep.

Stress stiffening computed when large displacements are requested. You can use the
parameter STRESSK on the NLCNTL bulk entry to turn off stress stiffening.
Stiffness computed from follower loads when large displacements are requested.
Follower loads occur when applied loads are dependent on large displacements, for
example, a pressure load on a rotating surface. You can use the parameter FOLLOWK
on the NLCNTL bulk entry to turn off follower stiffness.
Final contact normal and tangential stiffness. Contact edges and faces will appear
glued in the normal modes and frequency response subcases. You can use the
parameter KMODTN on the NLCNTL bulk entry to change the tangential contact
stiffness for the normal modes subcase.
Glue normal and tangential stiffness.

Spin-softening stiffness computed from a rotational load causing significant radial

deformation. Computed when large displacements are requested. You can use the
parameter SPINK on the NLCNTL bulk entry to turn off spin softening stiffness.

You can also run a modal frequency response analysis without statics and preload subcases. You define
the first subcase as normal modes, followed with the frequency response subcases. As a result, there is
no nonlinear base state for this definition.

Modal frequency response computation

You can assume in the following equations when a nonlinear stiffness is computed in a
preload or static subcase and applied to the normal modes and frequency response subcases.

The general equation of motion for a damped system subjected to a harmonic excitation is:

Equation 3-5.

To understand modal frequency response analysis, we will ignore the viscous damping and the
structural (hysteretic) damping terms in physical coordinates, and will add them later in modal
coordinates. Equation 3-5 simplifies to:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-27
© 2023 Siemens
 3. Subcase Types

Equation 3-6.

Assume a harmonic solution of the form:

Equation 3-7.

where is a complex displacement vector.

In Equation 3-6, we ignore the forcing term and substitute Equation 3-7 and its second time derivative.
Solving the resulting equation yields the natural frequencies and mode shapes for the system.

We use the mode shapes, , to transform the response from physical coordinates, , to modal
coordinates, :

Equation 3-8.

Substituting Equation 3-8 and its second time derivative into Equation 3-6 and simplifying yields the
equation of motion in terms of the modal coordinates:

Equation 3-9.

The equations forming Equation 3-9 are coupled. To uncouple the equations, we premultiply Equation
3-9 by the transpose of the eigenvector matrix, :

Equation 3-10.

Doing so diagonalizes the mass and stiffness matrices. The transformed mass and stiffness matrices and
forcing vector are referred to as:

3-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Modal frequency response subcase (SOL 401)

Modal (generalized) mass matrix.

Modal (generalized) stiffness matrix.

Modal force vector.

In the uncoupled form, the equation of motion in terms of the modal coordinates can be written as a set
of single degree-of-freedom systems:

Equation 3-11.

where:

Modal mass for the ith mode.

Modal stiffness for the ith mode.
Modal force for the ith mode.

When you define proportional damping, modal damping, and structural damping, the equation
of motion includes the complex damping force , and the complex stiffness force
, where is the sum of proportional and modal damping, and is the structural
damping stiffness. See Damping definition.

The equation of motion in modal coordinates with the damping forces can be written as:

Equation 3-12.

The equation of motion remains uncoupled when damping is defined.

From Equation 3-12, the individual modal responses, , are calculated for a specific forcing
frequency, . The physical response at the specified forcing frequency is then recovered from:

Equation 3-13.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-29
© 2023 Siemens
 3. Subcase Types

These responses are in complex form (magnitude/phase or real/imaginary) and are used to compute any
other output you requested, for example, stress and strain.

Mass definition

In the normal modes and modal frequency response subcases, mass is used by the inertia force term in
the equation of motion. For the static subcases, mass is used to compute grid point forces from the body
loads such as gravity, angular velocity, and angular acceleration.

You can use the following inputs to define the mass properties:

• The mass matrix is automatically computed when mass density (ρ) is specified on the MATi entries
associated with the finite elements.

• Nonstructural mass per unit length can be defined on the PBAR and PBEAM entries. In addition,
nonstructural mass per unit area can be defined on the PSHELL entries.

• The CONM1 entry allows you to input a fully coupled 6x6 mass matrix. You can also define half of the
terms on the CONM1 entry for a symmetric matrix.

• The CONM2 entry defines concentrated mass and inertia terms at a grid point.

• The CMASSi bulk entries can be used to define mass at a single degree of freedom (DOF) when only
one DOF is referenced, or it can be used to define coupling between two DOF.

The following parameters are related to the specification of mass properties.

• PARAM,COUPMASS,1 – Requests that the coupled mass option be used rather than the lumped mass
option for the elements that support the coupled mass option. By default, with the lumped mass
option, the mass of an element is divided and distributed to the grid points. With the coupled mass
option, the distributed mass is replaced by a non-diagonal mass matrix that couples the connected
grid points. The coupled mass option is sometimes more accurate, but it uses more computation time.

Note that COUPMASS controls the type of mass matrix used for the inertia term for the normal modes
subcase, which can affect the resulting mode shapes and frequencies, modal stiffness, and modal
mass used by the modal frequency response subcase. For either COUPMASS setting, the equation of
motion remains uncoupled for the modal frequency response subcase.

For the statics subcase, SOL 401 always computes body forces using the consistent mass matrix
independent of the PARAM,COUPMASS specification.

• PARAM,WTMASS,value – Specifies a factor by which to multiply the mass of the structure to obtain
dimensionally correct mass. For example, if the ft-lb-sec system is used, and the mass input unit is
pounds, then value = 1/32.174 = .031081. This factor operates on all mass terms.

Damping definition

3-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Modal frequency response subcase (SOL 401)

The modal frequency response subcase supports proportional viscous damping, modal viscous damping,
and structural damping. Viscous damping defined with the CDAMPi, CVISC, CBUSH, or CBUSH1D bulk
entries is not supported.

You select the damping definition with the DAMPING=n case control command, which can select the
DAMPTAB bulk entry and the DAMPING bulk entry. You can define both the DAMPTAB entry and the
DAMPING entry, and they can share the same SID.

• To define damping as frequency-dependent, you must define the DAMPTAB bulk entry. The DAMPTAB
bulk entry allows you to reference:

- The TABLEDi entry defining solution frequencies versus structural damping coefficients.

- The TABLEDi entry defining solution frequencies versus ALPHA1 and ALPHA2 proportional damping
values.

- The TABDMP1 entry defining natural frequencies versus modal damping values (critical damping
ratios only).

• To define your structural damping and proportional viscous damping as a constant, you can use the
DAMPING bulk entry, or you can define the parameter values G, ALPHA1, and ALPHA2. The parameter
definition does not require the DAMPING=n case control command.

• You can define damping as a combination of the three options (DAMPTAB bulk entry, DAMPING
bulk entry, and parameters) and the software uses the following precedence to select one of the
proportional viscous damping definitions, one of the modal viscous damping definitions, and one of
the structural damping definitions. For example, the software can use the parameter definition for the
structural damping and use the DAMPTAB definition for the modal damping.

1. DAMPTAB entry.

2. DAMPING entry.

3. Parameters.

The software computes the damping as follows.

• Viscous proportional damping:

You can define , which the software uses to compute a viscous damping proportional to
the mass of each mode , and , which the software uses to compute a viscous damping
proportional to the stiffness of each mode . The subscript indicates that ALPHA1 and ALPHA2 can
be defined dependent on the solution frequency.

The proportional damping is computed as:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-31
© 2023 Siemens
 3. Subcase Types

When you define frequency-dependent proportional damping, you define data tables representing the
solution frequencies versus ALPHA1 or ALPHA2. The software uses the actual solution frequencies you
define on the FREQi entries to interpolate the data in the table. As a result, a unique ALPHA1 and
ALPHA2 value is used at each solution frequency.

• Viscous modal damping:

You define viscous modal damping with a data table containing angular natural frequencies versus
critical damping ratios. The software uses the actual natural frequencies computed in the normal
modes subcase to interpolate the data in the table. As a result, each mode has a unique, interpolated
critical damping ratio, which is applied consistently for all solution frequencies.

The software uses the interpolated critical damping ratio to compute the modal damping for each
mode:

where the critical damping for each mode is computed as

and is the angular natural frequency for the mode.

The total viscous damping for each mode is the sum of the proportional and modal damping:

• Structural damping:

You can define the global structural damping coefficient , which the software uses to compute the
structural damping for each mode:

where is the modal stiffness for the ith mode.

The subscript on the damping coefficient indicates that it can be defined dependent on the solution
frequency.

When you define frequency-dependent structural damping, you define data tables representing the
solution frequencies versus the structural damping. The software uses the actual solution frequencies
you define on the FREQi entries to interpolate the data in the table. As a result, a unique structural
damping value is used at each solution frequency.

Frequency-dependent loads

3-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Modal frequency response subcase (SOL 401)

You define frequency-dependent dynamic loads for the modal frequency response subcase. The
software applies the load definition at each solution frequency you define with the FREQi bulk entries.
See Solution frequencies.

• Frequency-dependent loads are selected with the DLOAD=n case control command, where n is a
single load set defined by the RLOAD1 and RLOAD2 bulk entries, or a DLOAD bulk entry if you want to
combine multiple RLOADi entries into a single load set.

• Frequency-dependent load definition in the Bulk Data:

• The RLOAD1 entry defines a frequency-dependent dynamic load of the form:

You can define C(f) and D(f) as frequency-dependent on a TABLEDi bulk entry, or as a constant
directly on the RLOAD1 entry. The software interpolates frequency-dependent values.

• The RLOAD2 entry defines a frequency-dependent dynamic load of the form:

You can define B(f) and ϕ(f) as frequency-dependent on a TABLEDi bulk entry, or as a constant
directly on the RLOAD2 entry. The software interpolates frequency-dependent values.

• You can define a time delay, τ, and a phase angle, θ, on the RLOADi entries. If the values vary across
the degree of freedom referenced by the EXCITEID, you define the DELAY and DPHASE bulk entries.
If the values are constant for all degrees of freedom referenced by the EXCITEID, you can define the
values directly on the RLOADi entry.

• Defining the EXCITEID and TYPE fields on the RLOADi entries:

■ The EXCITEID field on the RLOADi entry selects either a static load ID, or an enforced
displacement defined with the SPCD entry. The supported static load inputs are the DAREA,
FORCE, FORCE1, FORCE2, GRAV, MOMENT, MOMENT1, MOMENT2, PLOAD, PLOAD1, PLOAD2,
PLOAD4, PLOADE1, PLOADX1, RFORCE, RFORCE1, and SLOAD bulk entries. The FORCDST bulk
entry cannot be selected by the EXCITEID.

■ You should enter 0 in the TYPE field on the RLOADi entry when a static load is referenced in the
EXCITEID field.

You should enter 1, 2, or 3 in the TYPE field on the RLOADi entry when a displacement, velocity,
or acceleration, respectively, is defined with an SPCD entry referenced in the EXCITEID field.

• TABLEDi (i=1,2,3,4) - Tables that defines the load variation with frequency.

• DLOAD - Combines multiple RLOADi entries into a single load set.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-33
© 2023 Siemens
 3. Subcase Types

• The figure below demonstrates how the DLOAD, RLOADi, FORCE (for example), and TABLEDi bulk
entries relate to one another.

• Load input example 1:

When there is more than one frequency-dependent load set, the DLOAD bulk entry is required:

$
$ DLOAD COMBINES MULTIPLE RLOAD1 (102 AND 125)
DLOAD 17 1. 1. 102 1. 105
$
$ FREQUENCY-DEPENDENT FORCE, EXCITEID=125, TYPE=0 (DEFAULT)
RLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
$
$ TABLED=13 DEFINING D(F) VERSUS FREQUENCY
TABLED2 13
0. +
+ 0. 1. 1000. 10. 10000. 0. ENDT$
$ FREQUENCY-DEPENDENT FORCE EXCITEID=3, TYPE=0 (DEFAULT)
RLOAD1 105 3 12
$
FORCE 3 73 0 2. 8. 0. 0.
$
$ TABLED=12 DEFINING D(F) VERSUS FREQUENCY
TABLED2 12
0. +
+ 0. 1. 1000. 10. 10000. 0. ENDT

• Load input example 2:

3-34 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Modal frequency response subcase (SOL 401)

When there is only one frequency-dependent load set, the DLOAD entry is not necessary:

$
$
$ FREQUENCY-DEPENDENT FORCE, EXCITEID=125, TYPE=0 (DEFAULT)
RLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
PLOAD 125 100.0 21 30 18 10
PLOAD 125 100.0 10 18 22 25
$
$ TABLED=13 DEFINING D(F) VERSUS FREQUENCY
TABLED2 13
0. +
+ 0. 1. 1000. 10. 10000. 0. ENDT
$

Solution frequencies

You define the solution frequencies with the FREQ, FREQ1, and FREQ2 bulk entries. The FREQUENCY
case control command selects the FREQi bulk entries. All FREQi entries with the same ID are applied in
the analysis. As a result, you can use a combination of FREQ, FREQ1, and FREQ2 entries to define your
solution frequencies.

Bulk Entry Description

FREQ Defines discrete excitation frequencies.
FREQ1 Defines a starting frequency Fstart, a frequency increment Δf, and the number of
frequency increments.
FREQ2 Defines a starting frequency Fstart, and ending frequency Fend, and the number of
logarithmic intervals.

Output summary

The modal frequency response subcase supports the same output requests as the static subcase. You
can also request velocity, acceleration, and modal displacements with the VELOCITY, ACCELERATION,
and SDISPLACEMENT case control commands, respectively. One exception is that stress output is not
available for beam, shell and composite elements.

All output for SOL 401 is in SORT1 format, including the modal frequency response subcase. SORT2
output is not supported.

The software always uses the modal displacement method of results recovery for the modal frequency
response subcase. With this recovery method, the software computes the total physical displacements
for each solution frequency from the modal displacements. Then it computes all other output you
requested, for example, stress and strain, using the physical displacements.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-35
© 2023 Siemens
 3. Subcase Types

Case control example

The following case control input example demonstrates the input requirements for the normal modes
and the modal frequency response subcases.

Type Input syntax Description

$ EXECUTIVE CONTROL
SOL 401
CEND
$ CASE CONTROL
Global TEMP(INIT)=1 The SPC=100 defines a global constraint set for all subcases,
commands DLOAD=300 including the normal modes and frequency response
DTEMP=502 subcases.
SPC=100
The software only applies these global commands to the
BCTSET=7
static and preload subcases:
TEMP(INIT)=1 defines a global initial temperature set. When
you have thermal loads, the initial temperature set must be
the same for all applicable subcases.
The DLOAD=300 defines a global time-assigned load set.
The DTEMP=502 defines a global time-assigned thermal load
set.
The BCTSET=7 defines a global contact set.
DISPLACEMENT=ALL These global output requests are applicable to all subcases,
STRESS=ALL including the normal modes and frequency response
subcases.
Preload and $ Preload Subcase This preload subcase establishes the contact set (eliminates
static SUBCASE 1 initial interference conditions) requested with the global
subcase ANALYSIS=PRELOAD BCTSET=7 command.
commands TSTEP=100
Although a preload subcase has a constant time, you still
must include a TSTEP command to select a TSTEP1 bulk entry
that is defined with a constant time. This is still the start of
the solution time stepping, so the end time is equal to 0.0.
The software ramps the contact interference by the number
of increments (INC field) defined on the TSTEP1 entry.
The thermal loads at time=0.0 that you define using
the global time-assigned thermal load set DTEMP=502 are
applied if they are non-zero.
Because new service loads are never applied in a preload
subcase, the global time-assigned mechanical load set
DLOAD=300 is ignored. You could define a constant time
static subcase with an end time=0.0 to apply service loads at
time=0.0.

3-36 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Modal frequency response subcase (SOL 401)

Type Input syntax Description

$ Statics Subcase This static subcase begins to increment time.
SUBCASE 2
The TSTEP=102 command selects a TSTEP1 bulk entry with
ANALYSIS=STATICS
an end time=20.0 and number of increments=10.
TSTEP=102
For each time increment (2.0, 4.0, 6.0, etc), the software
now begins to update the global time-assigned mechanical
load (DLOAD=300) and global time-assigned thermal load
(DTEMP=502).
The globally defined contact set (BCTSET=7) is still active
and continues to iterate as the loading changes the contact
condition.
The bolt preload defined in SUBCASE 2 is maintained.
Normal $ Normal Modes A normal modes solution is requested at the current state of
modes Subcase the nonlinear problem.
subcase SUBCASE 3
The METHOD=103 command selects the EIGRL bulk entry
commands ANALYSIS=MODES
requesting the number of modes.
METHOD=103
NLCNTL=30 The NLCNTL=30 command selects a NLCNTL bulk entry with
the parameter setting KMODTN=5. This setting requests the
software to replace the final contact stiffness with a tied-
contact stiffness.
The globally defined constraint set (SPC=100) is still active
and applied in this subcase.
The globally defined output requests are still active and
applied in this subcase.
The globally defined time-assigned load set DLOAD=300,
time-assigned thermal load set DTEMP=502, and contact
set BCTSET=7 are all ignored in this subcase. Also, the bolt
preload defined in SUBCASE 2 is ignored. Although, all of
the definitions applied in the previous static and preload
subcases determine the final deformed state of the model,
and the final state of the nonlinear stiffness used in this
normal modes subcase.
Frequency $ Frequency Response A frequency response solution is requested that uses the
response Subcase normal modes computed in subcase 3.
subcase SUBCASE 4
The DLOAD=120 command will select an RLOADi bulk entry
commands ANALYSIS=MFREQ
that defines a frequency-dependent loadset.
DLOAD=120
FREQ=130 The FREQ=130 command will select an FREQi bulk entry that
defines the solution frequencies for the analysis.
The globally defined constraint set (SPC=100) is still active
and applied in this subcase.
The globally defined output requests are still active and
applied in this subcase. You can optionally add additional

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-37
© 2023 Siemens
 3. Subcase Types

Type Input syntax Description

output or change the globally defined output in this or in any
subcase.
The globally defined time-assigned load set DLOAD=300,
time-assigned thermal load set DTEMP=502, and contact
set BCTSET=7 are all ignored in this subcase. Also, the bolt
preload defined in SUBCASE 2 is ignored. Although, all of
the definitions applied in the previous static and preload
subcases determine the final deformed state of the model,
and the final state of the nonlinear stiffness used in this
normal modes subcase.

3-38 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cyclic modes subcase

3.9 Cyclic modes subcase

The cyclic solution method takes advantage of cyclic symmetry to reduce the time needed to create
and solve a full 360 degree model. To use this method, you create a 3D-solid element model that
represents a fundamental segment. The fundamental segment represents a structure that is made up of
N repetitions, where each repetition can be obtained by rotating the fundamental segment an angle that
is an integer multiple of 2π/N.

An important feature of this cyclic solution method is the automatic coupling of the translational DOF
on the symmetry faces. The CYCSET case control command, which selects the CYCSET bulk entry, or
multiple CYCSET entries with the CYCADD bulk entry, defines the coupling. The coupling definition is
required and must be defined globally. As a result, the MPC equations created by the software are
applied in every subcase.

See Cyclic symmetric boundary condition for the automatic coupling details.

CYCMODES subcase

A cyclic modes subcase is available and designated with ANALYSIS=CYCMODES in the subcase. The cyclic
modes formulation includes the harmonic index, k, which represents an additional dimension of the
vector space that is not present in an "ordinary" modal analysis. For cyclic models with an even number
of sectors (N is even), the allowable set of harmonics is 0,1, ...., N/2. For cyclic models with an odd
number of sectors (N is odd), the allowable set of harmonics is 0,1,…, (N-1)/2.

You request the harmonic index values in which you want modes to be computed with the HARMONICS
case control command, and a cyclic modal solution occurs for each harmonic index independently. For
example, if you request 10 modes on the EIGRL bulk entry, and you request a modal solution for the 0th,
the 1st, and the 2nd harmonic, a discrete cyclic modal solution occurs for each of these harmonics.

When computing the cyclic modes, the software uses a duplicate sector method. For harmonics k=0
and k=N/2, there are distinct eigenvalues, and only one eigenvector component associated with each
eigenvalue. For all other harmonics (0 < k < N/2), each eigenvalue is repeated, and the displacement
vector for each corresponding eigenvalue has two components; the cosine component and the sine
component .

Static, preload, dynamic, and modal (non-cyclic modes) subcases

The static, preload, dynamic, and modal (non-cyclic modes) subcases can also be included in the input.
These subcases use the MPC equations automatically created by the software, but they are not cyclic.
That is, the displacements only represent the 0th harmonic, n=1 fundamental sector.

Any of the subcase types can be defined as sequentially dependent. In SOL 401, you can define the
parameters STRESSK, SPINK, and FOLLOWK on the NLCNTL bulk entry to request stress stiffening, spin
softening, and follower stiffness, respectively.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-39
© 2023 Siemens
 3. Subcase Types

Note that a sequentially dependent (SEQDEP=YES) modes subcase (ANALYSIS=MODES, CYCMODES, or

FOURIER) cannot follow a dynamic subcase (ANALYSIS=DYNAMICS). Doing so will result in a fatal error.

Cyclic modes subcase input summary

• In SOL 401, the automatic coupling definition is required. See Cyclic symmetric boundary condition.

• The ANALYSIS=CYCMODES case control command is defined in the specific subcases in which you are
requesting the cyclic modes solution method.

• The HARMONICS case control command requests the specific harmonics in which modes are
computed. "ALL" requests all possible harmonics. If you define the SID of a SET bulk entry, the SET
entry lists the harmonic numbers to be computed, including "0" to request the zeroth harmonic.

The maximum harmonic for a model is related to the total number of segments which would
theoretically exist to represent the full model.

• For an even total number of segments:

Maximum harmonic = Total number of segments/2.

For example, if a 30 degree segment is modeled, the total number of segments to create a full
model is 360/30 = 12. Since 12 is even, the maximum harmonic = 12/2=6.

• For an odd total number of segments:

Maximum harmonic = (Total number of segments-1)/2.

For example, if a 40 degree segment is modeled, the total number of segments is 360/40 = 9. Since
9 is odd, the maximum harmonic = (9-1)/2 = 4.

• As a result of the inherent symmetry in the cyclic modal solution, mode pairs exist for harmonic
numbers 1 through N/2 -1. The software automatically outputs the mode pairs for these subcase
types for the modes requested with the EIGRL entry. For example, if you request 10 modes on the
EIGRL entry:

For harmonic index 0 and N/2, 10 modes are computed.

For harmonic numbers 1 through N/2 -1, 20 modes are computed (10 distinct modes).

This behavior is consistent for modes requested with the OMODES case control command. See the
remarks on the OMODES command for details.

• The HOUTPUT case control command optionally requests the harmonics to output modes. "ALL"
requests output for every harmonic requested on the HARMONICS command. You can define an
integer to select the SID of a SET bulk entry, which lists the harmonic numbers to be output. These IDs

3-40 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cyclic modes subcase

are a subset of the IDs requested on the HARMONICS command. The C, S, C*, and S* describers on
the HOUTPUT command are not supported by SOL 401 nor SOL 402.

• For SOL 401, an output coordinate system exception exists for the cyclic modes subcase. For the solid
elements that represent a cyclic symmetry fundamental segment, stress and strain are output in the
cylindrical coordinate system selected on the CYCAXIS bulk entry. This exception only applies to the
stress and strain output from the cyclic modes subcase. Stress and strain output for a cyclic symmetry
fundamental segment from all other subcase types is in the material coordinate system.

• The METHOD case control command selects the EIGRL bulk entry which then defines the eigenvalue
solution options. For example, the lower and upper frequency ranges and the number of modes.
Since a single EIGRL entry is selected in a subcase, the same EIGRL options are used when the
software computes the modes for each harmonic.

• For SOL 402, when you combine Fourier axisymmetric elements and cyclic symmetry in a cyclic
subcase, you use the FHAR case control command to request the harmonic numbers for the Fourier
elements, and the HARMONICS case control command to request the harmonic numbers for the cyclic
symmetry. When the 0th harmonic is requested for the cyclic symmetry (HARMONIC=0), the 0th
harmonic is computed for the Fourier elements by default, even if you do not request it with the
FHAR command. You can omit the 0th harmonic with the FHAC command. See SOL 402 - 2D Fourier
axisymmetric and 2D/3D coupling.

Post-processing the results

Simcenter Nastran outputs results for the fundamental sector. Due to the symmetric nature of the
problem and the orthogonal nature of the modes, the results for the entire structure (360 degree
model) can be inferred from the results of the fundamental sector.

• For the 0th harmonic:

Where,

n = sector for which results are to be inferred.

= Results corresponding to the fundamental sector at harmonic 0.

results for sector n at harmonic 0.

• For harmonic k (0 < k < N/2),

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-41
© 2023 Siemens
 3. Subcase Types

Where,

N = Total number of sectors.

n = Sector for which results are to be inferred.

k = Harmonic index

= Cosine cyclic component for the k harmonic of the mode being computed for the fundamental
sector.

= Sine cyclic component for the k harmonic of the mode being computed for the fundamental
sector.

R = any output quantity of interest. For example, displacement or stress.

• For harmonic N/2:

Where,

n = Sector for which results are to be inferred.

= results corresponding to the fundamental sector at harmonic N/2.

= results for sector n at harmonic N/2.

Cyclic clocking and normalization for the CYCMODES subcase

As a result of the inherent symmetry with the cyclic modal solution, modes occur in pairs for harmonics
1 through N/2-1, where N is the total number of sectors.

Once Simcenter Nastran computes the normal modes, it uses the initially computed global displacement
vectors to do the following:

• The software clocks the eigenvector solution to the fundamental sector. This clocking ensures that, for
the first mode in a mode pair, the maximum nodal displacement occurs on the fundamental sector.

• If you have selected either the AFNORM or DISP normalization options, the software renormalizes
using the maximum displacement relative to all sectors.

The clocking and normalization procedure is as follows.

3-42 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cyclic modes subcase

The displacement result for a single mode and harmonic is represented by the equation:

The global displacement vectors and in a single mode are orthogonal to each other. In addition,
from one mode in a pair is related to from the same pair.

For a traveling wave with equal amplitude in any mode pair, every grid point traverses an ellipse in three
dimensional space. The maximum resultant displacement is the major axis of the ellipse. For a grid point
i, the maximum resultant displacement is computed as follows.

is the cyclic cosine displacement vector (three components) at a specific grid point.

is the cyclic sine displacement vector (three components) at a specific grid point.

The software computes the following using the cyclic cosine and sine vectors:

The resultant displacement at each grid point i is computed as:

The software determines the grid point with the maximum resultant displacement. For this grid point ii,
the phase angle is computed as:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-43
© 2023 Siemens
 3. Subcase Types

This phase angle will be used to clock the displacements to the fundamental sector.

The maximum displacement found at grid point ii is used to compute the normalization factor:

• For AF normalization, the factor is computed as:

where,

ω is the frequency for the mode, and

AFNORM is the parameter setting PARAM, AFNORM which defaults to 1.0.

For the modes considered as rigid body modes, the software sets ω = 1 when computing the AF
normalization factor. The software considers a mode to be a rigid body mode if its frequency is below
the value of the parameter AFZERO (default=1.0 Hz).

• For unit (MAX) normalization, the factor is computed as:

• For mass (MASS) normalization, the factor f=1.0 is used since the eigenvector was already mass
normalized when the modes were computed initially.

The cyclic cosine and sine components are then clocked based on the computed values of .

The cyclic components for each mode are then reset to these values:

3-44 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Fourier harmonic solution

3.10 Fourier harmonic solution

A Fourier normal modes subcase is available in SOL 401 and SOL 402 for models that include
axisymmetric elements. The subcase is designated with the ANALYSIS=FOURIER and HARMONICS=N case
control commands in the subcase.

The conventional axisymmetric element includes radial and axial degrees-of-freedom with no variation
in theta.

In the Fourier normal modes subcase, the axisymmetric element has radial, axial and theta degrees-of-
freedom. In addition, the degrees-of-freedom are represented with harmonic terms of a Fourier series of
the form:

where,

c=cos(kθ) and s=sin(kθ),

k is the harmonic number,

are symmetric displacements, and

are antisymmetric displacements.

Both symmetric and antisymmetric displacements are computed by Simcenter Nastran for a particular
harmonic k.

With the Fourier normal modes subcase, you request which harmonic numbers a modal solution should
occur, and the harmonic terms for modal output. For each harmonic number in which you request
modes and output, the software can compute the symmetric and antisymmetric displacements, stress,
strain, SPC force and grid point forces. You can use the typical case control commands to request the
output. You can then optionally use the Simcenter post processor to display the physical results on either
a 3D segment, or on a full 360 degree model display.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-45
© 2023 Siemens
 3. Subcase Types

The modal solution for each harmonic term is discrete, and independent of other harmonic terms. For
example, if you request 10 modes on the EIGRL bulk entry, and you request a modal solution for the 0th,
the 1st, and the 2nd harmonic term, a discrete modal solution will occur for each of these harmonics.
You will have 10 modes for the 0th, 10 modes for the 1st, and 10 modes for the 2nd term, and there is
no coupling of the mode results between the different harmonics.

Static and modal (non-Fourier normal modes) subcases can also be included in the input, and are
designated with the case control commands ANALYSIS=STATICS or ANALYSIS=MODAL. Although, the
conventional axisymmetric element formulation is used in the static and modal subcases.

The Fourier normal modes subcase can optionally be sequentially dependent on a static subcase.

Note that a sequentially dependent (SEQDEP=YES) modes subcase (ANALYSIS=MODES, CYCMODES, or

FOURIER) cannot follow a dynamic subcase (ANALYSIS=DYNAMICS). Doing so will result in a fatal error.

In SOL 401, you can optionally define the parameters STRESSK, SPINK, and FOLLOWK on the NLCNTL
bulk entry to request the additional stiffness terms computed in the previous static subcase.

In addition to axisymmetric elements, the plane stress and the chocking elements can also be included
with the Fourier normal modes subcase. In the Fourier normal modes subcase, Gauss locations on the
chocking element use the axisymmetric Fourier formulation if the location is considered chocked. That
is, it includes stiffness in the radial, axial and theta degrees-of-freedom, and all degrees-of-freedom
are represented using harmonic terms of a Fourier series. To be considered chocked, the loads in a
previous static subcase should result in the chocked condition, and the consecutive Fourier normal
modes subcase should be defined as sequentially dependent. By default, all Gauss locations on the
chocking elements are considered unchocked in a Fourier normal modes subcase, and use the plane
stress element formulation.

For grid points which are defined on the rotation axis, in addition to any conditions that you defined,
Simcenter Nastran automatically applies the following SPC and MPC conditions during the solution.

• For the harmonic number k=0, Simcenter Nastran fixes the radial (Ur) and azimuth (Uθ) degrees-of-
freedom.

• For the harmonic number k=1, Simcenter Nastran fixes the axial degree-of-freedom, and it creates the
MPC condition Ur = Uθ for the cosine terms, and the MPC condition Ur = -Uθ for the sine terms.

• For the harmonic numbers k>1, Simcenter Nastran fixes all translational degrees-of-freedom.

Note:
By default, only the MPC conditions automatically created by the software for harmonic number
k=1 are permitted. If you define additional MPC conditions, or include RBE2, RBE3, RBAR elements
in your model, and you have requested harmonic numbers k>0 in a Fourier modes subcase, the
solution will end with a fatal error.
You can define SYSTEM(809)=1, and the solution will continue with a warning message.

3-46 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Fourier harmonic solution

Note:
When axisymmetric elements are defined on the XZ-plane of the basic coordinate system, the
X-axis of the basic system is the radial direction, the Z-axis of the basic system is the axial
direction, and the Y-axis of the basic system is the azimuth direction. The grid points defining
these elements must have X ≥ 0.
When axisymmetric elements are defined on the XY-plane of the basic coordinate system, the
Y-axis of the basic system is the radial direction, the X-axis of the basic system is the axial
direction, and the Z-axis of the basic system is the azimuth direction. The grid points defining
these elements must have Y ≥ 0.

Fourier normal modes subcase input summary

• The ANALYSIS=FOURIER case control command should be defined in the subcase in which you are
requesting the Fourier normal modes subcase in SOL 401.

• The HARMONICS case control command requests the specific harmonics in which modes will be
computed. The SET entry then lists the harmonic numbers to be computed, including "0" to request
the zeroth harmonic. Since there is an infinite number of harmonics in the Fourier normal modes
analysis, the describer "ALL" is not supported in the ANALYSIS= FOURIER subcase.

• The HOUTPUT case control command optionally requests the harmonics to output modes. "ALL"
requests output for every harmonic requested on the HARMONICS command. An integer can be
defined to select the SID of a SET bulk entry listing the harmonic numbers to be output. These IDs
typically represent a subset of the IDs requested on the HARMONICS command. The C, S, C*, and S*
describers on the HOUTPUT command are not supported by SOL 401.

• The METHOD case control command selects the EIGRL bulk entry, which then defines the eigenvalue
solution options. For example, the lower and upper frequency ranges and the number of modes.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-47
© 2023 Siemens
 3. Subcase Types

3.11 Nonlinear buckling (SOL 401)

A nonlinear buckling analysis is used to accurately determine what the critical buckling load is and how a
structure behaves after it has buckled. You can request a nonlinear buckling analysis in a SOL 401 statics
subcase. You can choose from one of the following three arc-length methods:

• Riks arc-length method

• Modified Riks arc-length method

• Crisfield arc-length method

To request the nonlinear buckling analysis, your statics subcase should include the standard
ANALYSIS=STATICS command along with the NLARCL=ID case control command. The ID on the NLARCL
command selects the NLARCL bulk entry which defines the nonlinear buckling parameters.

The NLARCL command in the subcase is the trigger which the software uses to start the nonlinear
buckling analysis. The referenced NLARCL bulk entry is also required, even when the default values are
used.

The nonlinear buckling statics subcase must be either the first subcase, or the last in a sequence of static
subcases. A nonlinear buckling statics subcase can only be followed by a modal subcase.

• If the nonlinear buckling statics subcase is the first subcase, all of the loads defined in the current
subcase are incrementally applied by the software during the arc-length solution.

• If the nonlinear buckling statics subcase is the last subcase and it is sequentially dependent, the loads
applied in the previous subcase are held constant in the current subcase. The difference between
the load defined in the nonlinear buckling statics subcase and the load from the previous subcase
is computed. This load difference is incrementally applied by the software during the arc-length
solution.

You select loads in a nonlinear buckling statics subcase with either the LOAD=n or DLOAD=n case control
commands. Although, you cannot increment loads in a nonlinear buckling statics subcase with a TSTEP1
bulk entry since the software increments the loads for you. If you define a TSTEP1 entry in a nonlinear
buckling statics subcase, you must define it with a constant time. That is, it must have an end time
(Tend) which is the same as the start time for that subcase. In addition, the output frequency option
Nout on the TSTEP1 entry is ignored in a nonlinear buckling statics subcase. The output frequency is
instead controlled by the NOUTAL parameter on the NLARCL bulk entry.

If you want to define a specific load sequence up to the point of buckling, you can do this with static
subcases without buckling defined before your nonlinear buckling statics subcase. In these previous
static subcases, you can increment loads with the TSTEP1 bulk entry.

The NLARCL bulk entry has the following solution parameters:

3-48 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear buckling (SOL 401)

TYPE = RIKS selects the Riks arc-length method

= MRIKS selects the modified Riks arc-length method (Default)
= CRIS selects the Crisfield arc-length method
MINALR Minimum allowable arc-length adjustment ratio between increments for the adaptive
arc-length method. (0.0<Real≤1.0; Default=0.25)
MAXALR Maximum allowable arc-length adjustment ratio between increments for the adaptive
arc-length method. (Real>=1.0, Default=4.0)
MAXR Defines the overall upper and lower bounds on the load increment /arc-length in the
subcase.
SCALE Scale factor for controlling loading contribution in the arc-length constraint. (Real>0.0;
Default = 0.0)
DESITER Desired number of iterations for convergence to be used for the adaptive arc-length
adjustment. (Integer>0, Default=12)
MXINC Maximum number of controlled load increments done in the arc-length subcase
(Integer>0; default=20)
LDFACIN Initial load factor. This load factor will be used to compute initial arc-length (REAL>0,
DEFAULT=1.0).
NOUTAL Skip factor for output of the incremental results. Output always occurs at the final
increment. For example, if you define NOUTAL=2, output occurs at every other
converged solution increment and for the final increment. If you define NOUTAL=0,
output only occurs at the final increment. (Integer≥0; Default=1)
MXLDFAC Maximum value of load-factor at which solution will be terminated. (Real, Default =
1.0)

Initial Imperfections

You define the X,Y,Z location of a grid point on the GRID entry. An option is available to adjust this
location with a +/- delta X,Y,Z position. For example, if a grid point is defined on the GRID entry at 1.0,
1.0, 0.0, and a delta of .2, 0.0, 0.0 is defined, the modeled location for this grid point becomes 1.2,
1.0, 0.0. This location adjustment is useful in the nonlinear buckling analysis to define an imperfection.
For example, an imperfection on the side of a cylinder which is under axial compression will impose a
deliberate location for buckling.

The grid point imperfections are selected with the IMPERF case control command which selects the
IMPERF or IMPRADD bulk entries. The IMPRADD entry allows you to combine multiple IMPERF entries,
and scale the referenced imperfection sets either independently or collectively.

The IMPERF case control command must be defined globally (above the subcases). As a result, the
updated location of the referenced grid points applies to all subcases.

Restrictions

• The software issues a fatal error if LGDISP=-1 and an arc-length solution is requested.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-49
© 2023 Siemens
 3. Subcase Types

• The software issues a fatal error if an arc-length solution is requested in the context of a Simcenter 3D
Multiphysics solution.

• The software issues a fatal error if a sequentially dependent STATICS or PRELOAD subcase follows an
arc-length subcase.

• The software issues a fatal error if a sequentially dependent arc-length subcase follows another
sequentially dependent arc-length subcase.

• An enforced displacement defined with the SPCD bulk entry is held constant in a nonlinear buckling
solution.

Arc-length theory

The concept of the arc-length method is to modulate the applied loads in order to produce solutions
with displacement increments of manageable size of a given load step. In order to modulate the applied
load, an additional variable, the load factor, and a constraint equation are introduced. There are various
approaches to providing a constraint equation.

Consider a residual load {R}.

Equation 3-14.

where F represents the internal forces, and the total external load P is expressed as:

Equation 3-15.

where P0 denotes the applied load at the end of the preceding subcase, ΔP represents the load
increment in the current subcase, and μ is the load factor varying from 0 to 1, but not limited to
this range, within the subcase. Linearizing {R} about (u,μ), R(u,μ) can be expressed as:

3-50 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear buckling (SOL 401)

Equation 3-16.

Based on the above equations, the equilibrium condition at (u+Δu, μ+Δμ) dictates that

Equation 3-17.

where, is the follower matrix, is the stiffness matrix , and .

The iteration equation can be derived by rearranging Equation 3-17:

Equation 3-18.

where the follower matrix is omitted. The iterative process can be established by decomposing the
equation above into two parts:

Equation 3-19.

Then the trial solution is obtained by

Equation 3-20.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-51
© 2023 Siemens
 3. Subcase Types

with

Equation 3-21.

where Δμ can be obtained from the constraint equation.

Riks Method and Its Variations

The displacement increment is limited by a constraint equation:

Equation 3-22.

where w is a scaling factor you specify with the SCALE parameter on the NLARCL bulk entry, and Δl is
defined by

Equation 3-23.

You define the initial value of Δμ with the LDFACIN parameter on the NLARCL bulk entry. The constraint
of Equation 3-22 has a disparity in the dimension by mixing the displacements with the load factor. For
this reason, the scaling factor (w) is introduced so that you can scale μ to the appropriate dimension or
delete the Δμ term. The default value of w is zero as demonstrated in Figure 3-6. The iteration follows
the path on the plane normal to the initial tangent as shown in Figure 3-3. Therefore the subsequent
iterations (i > 1) must satisfy

Equation 3-24.

3-52 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear buckling (SOL 401)

Recalling that the first iteration should result in

Equation 3-25.

Equation 3-24 may be reduced to

Equation 3-26.

from which the load factors for the subsequent iterations are determined by

Equation 3-27.

and

Equation 3-28.

Notice that the normal plane does not change during the iteration by Riks method. In addition, {ΔuP}
remains constant if the iteration process is the modified Newton's method.

Alternatively, the normal plane may be updated at every iteration. If the normal plane is to be normal
to the cumulative incremental displacements for the preceding iterations as shown in Figure 3-4, the
orthogonality condition in Equation 3-24 should be modified to:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-53
© 2023 Siemens
 3. Subcase Types

Equation 3-29.

The increment in the load factor for i > 1 is obtained by solving Equation 3-29,

Equation 3-30.

This variation of Riks method has an advantage over the Crisfield method as it avoids the solution of a
quadratic equation.

Crisfield Method

Instead of iterating on the normal plane, the solution is sought on the surface defined by Equation 3-22
with an arc-length of Δl as depicted in Figure 3-5,

Equation 3-31.

This constraint can be interpreted as keeping the incremental displacement constant, if w=0, as shown
in Figure 3-6. Substituting Equation 3-21 into the preceding equation, we obtain a quadratic equation in
terms of Δμ:

Equation 3-32.

where

3-54 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear buckling (SOL 401)

Equation 3-33.

Since the Crisfield method leads to a quadratic equation, the selection of the proper root of this equation
becomes the most critical process for the success of this method. There are two roots to Equation 3-32,

Equation 3-34.

The root is chosen so that the angle between two vectors {ui-1 - uo} and {ui - uo} is less than 90 degrees,

Equation 3-35.

There are cases where no roots can be found. Such is the case when the trial solution is far from the true
solution and stays outside the region covered by the arc-length. In this case, the trial solution vector is
scaled so that the direction vector intersects with the surface defined by Equation 3-31.

The wrong choice of the root could cause an unintentional loading path reversal, by which the
solution returns to the previous state. Such cases can be detected by checking the orthogonality of
the incremental displacements of the two successive solutions. If this case is detected, the root is chosen
so that the angle between {ui - uo} and {ui - uo} is an acute angle.

Adaptive Arc-Length Method

It is difficult to estimate a proper arc-length for multi-degree-of-freedom problems. The initial arc-length
for the Crisfield method can be determined by

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-55
© 2023 Siemens
 3. Subcase Types

Equation 3-36.

with

Δμ1 = μ1 = LDFACIN parameter on the NLARCL bulk entry.

You can define the maximum number of increments in the subcase with the MXINC parameter on the
NLARCL bulk entry.

The arc-length should be continuously updated at every increment using the information gathered
during the preceding increment. One method is to reduce the arc-length if it requires an excessive
number of iterations to attain a converged solution,

Equation 3-37.

where Id is the desired number of iterations for convergence and defined with the DESITER parameter on
the NLARCL bulk entry, and Imax is the number of iterations required for convergence from the preceding
step.

The adaptive process should be based on the arc-length ratio,

Equation 3-38.

Combining two criteria, the new arc-length ratio is adapted to the nonlinearity by

3-56 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear buckling (SOL 401)

Equation 3-39.

In order to maintain the stability for the adaptive process, ALRATIO should also be bounded,

MINALR < ALRATIO < MAXALR

You can define the parameters MINALR and MAXALR on the NLARCL bulk entry, which have the defaults
of 0.25 and 4, respectively. If the adjusted ALRATIO falls outside the bounds, ALRATIO is reset to the
limit. Then the arc-length is updated at the beginning of the next step based on ALRATIO as follows:

Δlnew = ALRATIO * Δlold

In the unstable regime where the stiffness is negative, the load factor decreases with a forward step.
When this happens, the sign of Δμ1 should be reversed. This possibility should be examined at the
beginning of each increment. The sign can be determined by the sign of a dot product,

Equation 3-40.

An adaptive bisection algorithm is also incorporated to cope with divergent cases. If the iterative process
using the arc-length method tends to diverge, the arc-length is bisected. The bisection is combined in
concert with the stiffness matrix update strategy. The bisection procedure continues until the iterative
process is stabilized and a converged solution is found. However, the number of contiguous bisections is
limited by the parameter MAXBIS on the NLCNTL bulk entry. The variable arc-length at every increment
invokes the recovery from the bisection process once the difficulties in convergence are overcome.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-57
© 2023 Siemens
 3. Subcase Types

Figure 3-3. Riks Method

Figure 3-4. Modified Riks Method

3-58 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear buckling (SOL 401)

Figure 3-5. Crisfield Method - Arc-length in terms of Combined Variables

Figure 3-6. Crisfield Method - Arc-length in terms of Displacements

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-59
© 2023 Siemens
 3. Subcase Types

3.12 Linearized buckling (SOL 402)

The non-linear behavior of a slender structure can be complex: you can encounter limit points where the
load vs displacement curves reach a maximum or a bifurcation point where the structure buckles from
one mode shape to another mode (orthogonal to the primary one).

To better understand the behavior, you can calculate critical loads and buckling modes by solving the
stability eigenvalue problem.

Stability eigenvalue problem

In the neighborhood of an equilibrium point, the tangent stiffness matrix can be developed in function
of the load factor:

KT = K*T + Δλ * K'T + Δλ2 * K''T.

For structural elements, if a total Lagrangian formulation and Green strains are used, and if the material
is elastic, this development is correct. Otherwise, it is only an approximation.

A linearization of this stiffness matrix is performed and the following eigenvalue problem is solved:

(K*T + Δλ * K'T)q = 0.

In order to compute the 1st derivative K'T, the following procedure is used:

1. The solver computes a variation of displacements from the variation of the external forces by
solving the equation:

K*T * Δq = ΔF.

2. Then, the solver computes the tangent stiffness matrix at two different points:

K1T = KT (q + Δq).

K2T = KT (q + 2Δq).

3. The 1st derivative K'T is then solved as a combination of the 3 matrices:

K'T = 0.5 * (4K1T - K2T - 3K*T).

For structural elements in total Lagrangian formulation with elastic material, this method gives the true
geometric stiffness: the critical buckling load will not depend on the size of Δλ.

In case of non-linear material (plastic or other), the tangent constitutive law is kept constant in the 3
computations of the stiffness matrix.

3-60 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Linearized buckling (SOL 402)

Workflow

1. After at least one ANALYSIS=STATICS subcase n, you define a ANALYSIS=BUCKLING subcase n+1.

Note:
ANALYSIS=BUCKLING must follow a ANALYSIS=STATICS, not a ANALYSIS=DYNAMICS.

2. The buckling subcase uses the last equilibrium state of the previous subcase n to compute tangent
stiffness matrix K*T.

3. The variation of the load (ΔF) is computed according to the loading time dependent function and
for a variation of time of 1 sec after the final time of subcase n.

4. The loads in the model that do not vary in between the time interval [tn, tn + 1 sec] are considered
as dead loads: they are applied on the structure but are not involved in the buckling process (Fn).

The loads in the model that vary in between the time interval [tn, tn + 1 sec] are considered as
working loads: these are the loads that are involved in the buckling process (ΔF).

5. If λ is the buckling factor given by modal analysis, the critical loading is:

Fcrit = Fn + λΔF.

Note:
You can repeat the sequence of STATICS subcase followed by BUCKLING subcase several times.

Result analysis and assumptions

• If contact conditions are defined, the contact configuration is supposed to be constant during the
modal analysis. Closed contact will be kept closed and open contact will be kept open. As far as a
buckling mode amplitude is unknown, penetration could be observed in post processing.

• If some enforced displacements (SPCD) exist, they are considered fixed in the buckling mode analysis.

• The buckling factor λ gives you the proportion of load variation that must be applied to make tangent
matrix singular.

The behavior is supposed to be locally linear, displacements and stress are supposed to be
proportional to a constant variation: q(λ) = qn + λΔq and σ(λ) = σn + λΔσ.

• If λ is > 0: the maximum load or the bifurcation point is not yet reached. In case of bifurcation,
the post buckling behavior will probably looks like the buckling mode. It can eventually be used to
introduce an imperfection in the structure.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-61
© 2023 Siemens
 3. Subcase Types

• If λ is < 0: the maximum load or the bifurcation point has already be reached. The non-linear
computation has probably shown negative pivots and the equilibrium can be unstable. In this case,
you can use RJPN parameter of the NLCNTL2 bulk entry to reject unstable time step.

Example

Case Control

NASTRAN SYSTEM(674)=1
$
SOL 402
CEND
$*
$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$*
$* CASE CONTROL
$*
$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$*
TITLE = Buckling analyses of a compressed plate
SUBTITLE = Several load levels
ECHO = UNSORT
SPC = 1
DLOAD = 2
METHOD = 10
DISPLACEMENT(PRINT) = ALL
STRESS(PRINT) = ALL
$
SUBCASE 1
ANALYSIS = STATICS
LABEL = First Loading [0-1]
TSTEP = 101
$
SUBCASE 2
ANALYSIS = BUCKLING
LABEL = Buckling analysis with unitary load
METHOD = 20
SEQDEP = YES
EKE(PRINT,THRESH=0.3) = ALL
$
SUBCASE 3
ANALYSIS = STATICS
LABEL = Loading up to 100. [1-100]
TSTEP = 102
$
SUBCASE 4
ANALYSIS = BUCKLING
LABEL = Buckling analysis at 100 load

3-62 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Linearized buckling (SOL 402)

METHOD = 40
SEQDEP = YES
EKE(PRINT,THRESH=0.3) = ALL
$
SUBCASE 5
ANALYSIS = STATICS
LABEL = Loading up to 250. [100-250]
TSTEP = 103

Time steps definition

TSTEP1 101 0.01 1 END

TSTEP1 102 1.0 1 END
TSTEP1 103 2.5 1 END

Eigenvalues selection

$------1-------2-------3-------4-------5-------6-------7-------8-------9-
-----10
$EIGRL SID V1 V2 ND MSGLVL MAXSET SHFSCL NORM
EIGRL 20 0. 500. 50 MAX
EIGRL 40 5 1

Loads

$
$ Loading
$
$------1-------2-------3-------4-------5-------6-------7-------8-------9-
-----10
DLOAD 2 1. 1. 3
TLOAD1 3 33 0 load 4
TABLED2 4 0.
+ 0. 0. 0.01 0. 10. 10. ENDT

In this example, the first buckling uses the loads time definition "buckling" interval of [0.01, 1.01], and
the second buckling uses the interval of [1.0, 2.0].

The loads are well defined in these intervals.

Output in the .f06 results file

THERE ARE 8 EIGENVALUES BETWEEN 0.000E+00 AND 5.000E+02

RESULTS AT ITERATION 10, NUMBER OF VECTORS : 30
EIGENVALUE BUCKLING FACTOR

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 3-63
© 2023 Siemens
 3. Subcase Types

1 -4.072133E-03 4.428440E+00
2 -4.770635E-03 4.038430E+01
3 -7.414269E-03 1.151249E+02
.....

3-64 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 4. Element support
4.1 Element Overview
The following summarizes all of the elements and materials supported in SOLs 401 and 402.

• The 3D solid elements CTETRA, CHEXA, CPENTA and CPYRAM are supported for linear, geometric
nonlinear, and material nonlinear analysis. The PSOLID or the PCOMPS bulk entries define the solid
element properties for both SOLs 401 and 402, or with the PLSOLID when a hyperelastic material is
defined for SOL 402 only. The PCOMPS defines a layered solid composite property.

• The axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6, the plane strain elements
CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8, and the plane stress elements CPLSTS3, CPLSTS4, CPLSTS6,
CPLSTS8 are supported for linear, geometric nonlinear, and material nonlinear analysis.

The properties for the axisymmetric elements are defined with the PSOLID bulk entry.

The properties for the plane strain and plane stress elements are defined with the PPLANE bulk entry
for both SOLs 401 and 402, or with the PLPLANE when a hyperelastic material is defined for SOL 402
only.

The grid points on these elements must all lie in either the XZ plane, or all in the XY plane of the basic
coordinate system. The software automatically determines the orientation.

When axisymmetric elements are defined on the XZ plane, X is the radial direction, and Z is the axial
direction. The grid points defining these elements must have X ≥ 0.

When axisymmetric elements are defined on the XY plane, Y is the radial direction, and X is the axial
direction. The grid points defining these elements must have Y ≥ 0.

• In SOL 401, a special, generalized plane strain formulation is available using the CPLSTN3, CPLSTN4,
CPLSTN6, and CPLSTN8 element types. The generalized plane strain elements must reference a
PGPLSN bulk entry. See Generalized plane strain analysis.

• In SOL 401, the chocking element is available. A chocking element is a special type of axisymmetric
element used to model regions in an axisymmetric analysis that can carry a compressive hoop stress,
but cannot carry a tensile hoop stress. See Chocking elements.

• The cohesive element is available to model adhesively bonded interfaces. Cohesive elements can
account for compliance in the connection and damage in the material. See Cohesive elements.

• The bar and beam elements defined with the CBAR and CBEAM entries are available. They support
large displacements and rotations when large displacements are requested with PARAM,LGDISP,1 in
SOL 401 or PARAM,LGSTRN,1 in SOL 402. See Bar and beam elements.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-1
© 2023 Siemens
 4. Element support

In SOL 402, nonlinear behaviors of bar and beam elements are only available for thin sections.

• The shell elements CTRIAR, CQUADR, CTRIA6, and CQUAD8 entries are supported. CQUAD4 and
CTRIA3 elements are also supported as inputs and the software will treat them as CQUADR and CTRIAR
elements. See Shell elements.

• A tension-only shell element is supported by SOL 401. The CQUADR or CQUAD4 bulk entries define
the connectivity, and the properties are defined with the PSHLPNL bulk entry. The tension-only shell
element initially behaves in shell element status. The software converts the element to shear panel
status using the conversion threshold defined in the SC and SDIR fields on the PSHLPNL entry. See SOL
401- Tension-only shell element.

• A shear panel element is supported by SOL 401. The CSHEAR bulk entry defines the connectivity, and
the properties are defined with the PSHEAR bulk entry. See SOL 401- Shear panel element.

• The spring elements CELAS1, CELAS2, CBUSH1D, and CBUSH are supported. See Spring and damper
elements.

• A rod element is supported by SOL 401. The CROD bulk entry defines the connectivity, and the
properties are defined with the PROD bulk entry. See SOL 401 - Rod element.

• The RBE2 and RBAR rigid elements are supported with optional large displacement effects and thermal
expansion. The RBE3 rigid element is also supported, but in SOL 401, it does not support large
displacement effects or thermal expansion. In SOL 402, it supports large displacements, rotations, and
thermal expansion. See Rigid element support.

• The mass elements CMASSi and CONMi are supported.

• You can model progressive ply failure in solid composites. See Progressive failure analysis in solid
composites.

• You can request stress norm, stress error norm, strain energy norm, and strain energy error norm
output. The output is computed and stored on an individual element basis. The Pre/Post application
uses the output for adaptive meshing. See Error estimator for mesh refinement.

• In SOL 401, you can compute and output the j-integral in a crack simulation. The j-integral output can
be requested and used by third-party software like Zencrack to perform a fracture mechanics analysis.
The CHEXA bulk entry allows for a collapsed element definition. See Crack simulation.

• In SOL 402, you can define kinematic joints. See Kinematics joints.

4-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Elements in nonlinear analysis

4.2 Elements in nonlinear analysis

In nonlinear finite element analysis, lower-order elements are often preferred over higher-order ones
because of their robustness and reasonable accuracy at reduced costs. The software supports linear
elements, rather than quadratic or cubic elements, to process nonlinearity. When using lower-order
elements, quadrilateral and hexahedral elements are generally preferred over triangular, pentahedral
or tetrahedral elements. Triangular and tetrahedral elements can exhibit excessively stiff behavior, and
caution is needed when using these elements.

Caution is also needed when different element types are combined in a model, and if these elements
are incompatible. In such cases, some provision (e.g., appropriate constraints) may be necessary at the
interface boundary. Modeling the joints (such as bolted, riveted, or welded) is particularly difficult. For
lack of better information, the joints are usually modeled as rigid or free in certain degrees-of-freedom.
If improved accuracy is required at such joints, the characteristics of the joint (stiffness and/or damping)
may have to be identified from experiments or the local analysis of a detailed model at the joint.
Modeling of the boundary conditions at the supports poses similar difficulties. Ideal boundaries are
represented as free, clamped, pinned, roller or ball joints. The reality tends to be in smeared condition.

Turning on nonlinearities in SOL 401

Large displacement - SOL 401

The parameter LGDISP turns the nonlinear large displacement capability on/off for the static, dynamic,
and preload subcases. If you define the parameter LGDISP for SOL 401, you must include it in the bulk
data portion of your input file. The single PARAM,LGDISP setting applies to all subcases.

• PARAM,LGDISP,-1 (default) - Large displacement effects are turned off for STATIC, PRELOAD, and
DYNAMICS subcases.

For the MODES, CYCMODES, and FOURIER subcases, second-order effects are ignored.

• PARAM,LGDISP,1 - Large displacement effects are turned on for STATIC, PRELOAD, and DYNAMICS
subcases.

When large displacement effects are turned on, you can use the SPINK, STRESSK, and FOLLOWK
parameters on the NLCNTL bulk entry to turn on or off the second-order effects for the STATIC,
DYNAMICS, and PRELOAD subcases, as well as for the MODES, CYCMODES, and FOURIER subcases.

PARAM,LGDISP,1 turns on large displacement effects, but small strains are assumed.

Large strain - SOL 401

The parameter LGSTRN turns on/off large strains, displacements, and rotations. See Nonlinear Effects in
SOL 401 for details on large strain.

• PARAM,LGSTRN,0 (default) - Small strains are assumed.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-3
© 2023 Siemens
 4. Element support

• PARAM,LGSTRN,1 - Large strains are requested. When you request large strain effects, large
displacement effects are also automatically included (LGDISP=1).

Turning on nonlinearities in SOL 402

LGDISP parameter

Elements become actively nonlinear if the parameter LGDISP is turned on. You must include this
parameter in the bulk data portion of your input file. The single PARAM,LGDISP setting is global and
applies to all subcases.

• PARAM,LGDISP,-1 (default) - Large displacement effects are turned off for ANALYSIS=STATIC,
ANALYSIS=PRELOAD, or ANALYSIS=DYNAMICS subcases.

For further ANALYSIS=MODES, ANALYSIS=CYCMODES, or ANALYSIS=FOURIER subcases, second-order

effects are ignored, in particular the stress stiffening effect of the previous static subcase.

As a consequence, further ANALYSIS=BUCKLING subcases are not allowed.

Small strains are assumed and follow the Engineering strain law.

• PARAM,LGDISP,1 - Large displacement effects are turned on for ANALYSIS=STATIC,

ANALYSIS=PRELOAD, or ANALYSIS=DYNAMICS subcases.

For further ANALYSIS=MODES, ANALYSIS=CYCMODES, or ANALYSIS=FOURIER subcases, second-order

effects are taken into account, in particular the stress stiffening effect of the previous static subcase.

For further ANALYSIS=BUCKLING subcases, nonlinear effects are split in two terms: a dead load part
and a varying part. The varying part is related to the loads variation from its latest static equilibrium.

Small strains are assumed and follow the Piola-Kirchoff strain law.

LGSTRN parameter

The parameter LGSTRN turns on/off large strains, displacements, and rotations.

• PARAM,LGSTRN,0 (default) - Small strains are assumed.

• PARAM,LGSTRN,1 - Large strains, displacements, and rotations are assumed (that is, LGDISP is
automatically set to 1). Large strain formulation is applicable to all elements.

In particular, nonlinear material laws will switch to a Cauchy stress and Logarithmic strain. All TABLES1
stress/strain hardening curves should also use the same convention.

4-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Shell elements

4.3 Shell elements

SOLs 401 and 402 support shell elements defined with the CTRIAR, CQUADR, CTRIA6, and CQUAD8
entries. CQUAD4 and CTRIA3 elements are also supported as inputs, and the software will treat them as
CQUADR and CTRIAR elements.

The shell elements are supported in the subcase types STATIC, PRELOAD, and MODAL. They are not
supported in the BUCKLING, CYCLIC and FOURIER subcase types.

The PSHELL property entry is supported. In addition, the PCOMPG1 property entry is available to define a
composite property which allows for a different failure theory for each layer.

The PCOMP and PCOMPG property entries are supported in SOL 401 to assist you in adapting laminate
models that were created for non-SOL 401 solution sequences to SOL 401. For more information, see
PCOMP and PCOMPG properties.

For SOL 401, you can optionally specify that shell elements that reference PCOMPG1, PCOMPG, and
PCOMP property entries use a transverse shear stress formulation that produces results that are
independent of the choice of material coordinate system. For more information, see Formulation
options for laminate shell elements.

The shell element using the PSHELL bulk entry supports geometry nonlinear conditions (large
displacement, large rotation, and contact) and material nonlinear (plasticity and creep). When you use
a nonlinear plastic or creep material, the NLAYERS parameter is supported to define the number of
integration points through the thickness. The NLAYERS parameter supports 3, 5, 7, and 9 points through
the thickness.

A composite shell element using the PCOMPG1 property bulk entry supports the geometry nonlinear
conditions, but does not support material nonlinear.

The ZOFF field on the element entry is supported to offset the element reference plane.

CQUAD8 and CTRIA6 elements

• The CQUAD8 and CTRIA6 element formulations that the software uses for SOL 401 and 402, are
different from the CQUAD8 and CTRIA6 element formulations that the software uses in the other
solution sequences. You can use the SOL 401 and 402 formulations to model the following mono-
layer and laminate plane stress behaviors:

• Membrane stiffness (SOL 402 only)

• Membrane and bending stiffness (SOL 401 only)

• Membrane, bending, and transverse shear stiffness

• Membrane, bending, transverse shear, and coupled membrane-bending stiffness

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-5
© 2023 Siemens
 4. Element support

The SOL 401 and 402 formulations do not support the following behaviors which are supported in
other solution sequences:

• Plane strain.

• Bending stiffness only.

• Bending and transverse shear stiffness only.

The SOL 401 and 402 formulations have several advantages over the formulations used in the other
solution sequences.

• They allow for higher aspect ratio of length to thickness before shear locking occurs.

• The CQUAD8 formulation is a heterosis formulation.

• The formulations use the K6ROT parameter to suppress grid point singularities by adding stiffness to
the out-of-plane rotational DOF.

• When viewed normal to the reference plane of the element, the X- and Y-axes of the material
coordinate system are consistent across the element. In the element formulations that are used
in other solution sequences, the X- and Y-axes of the material coordinate system vary across the
element.

• The CQUAD8 heterosis formulation uses eight-noded serendipity shape functions for the translational
DOF, and nine-noded Lagrange shape functions for the rotational DOF. The enriched shape functions
lead to better results although at some computational cost.

Because a ninth grid point is required for Lagrange shape functions and only eight actual grid points
exist, the software creates internal DOF at the centroid of the element. The internal DOF functions as
the ninth grid point for the element. After calculating the element matrices, the software condenses
the internal DOF prior to assembly into the global matrices.

By default, four Gauss points (2 x 2 integration) are used to integrate the membrane and transverse
shear stiffness, and nine Gauss points (3 x 3 integration) are used to integrate the bending and
coupled membrane-bending stiffness.

• The CTRIA6 formulation uses six-noded serendipity shape functions for the translational and
rotational DOF.

By default, three Gauss points are used to integrate the membrane, bending, transverse shear, and
coupled membrane-bending stiffness.

• When the software computes the element stiffness matrix for SOL 401 and 402 formulations, it adds
rotational stiffness directly into the element stiffness matrix for the out-of-plane rotational DOF. The
rotational stiffness that the software adds is given by the following equation:

4-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Shell elements

where K6ROT is the value of the K6ROT parameter, and D44 and D55 are entries in the constitutive
relation of the shell element. For example, the constitutive relation for a shell element whose
geometry and material properties are symmetric about its midplane has the following form:

where:
Nx, Ny, Nxy In-plane forces
Mx, My, Mxy In-plane moments
εxo, εyo, γxyo Midplane strains
κx, κy, κxy Midplane curvatures

PSHELL property

• The MID1, MID2, and MID3 are all required. MID1 and MID2 must be explicitly defined, and the MID3
field defaults to the MID2 value.

• MID4 is optional. If MID4 is defined, MID1 and MID2 must be defined. MID4 is applied with respect
to the element plane regardless if ZOFF is defined or not. A ZOFF definition on the element entry
produces a coupling independent of the MID4. As a result, defining both MID4 and ZOFF together
will create two independent sources of coupling. If you define both MID4 and ZOFF, the MID4 should
represent an additional coupling which is unique to the ZOFF coupling.

• When plastic or creep nonlinear materials are defined, the MID1, MID2, and MID3 must all be the
same, and MID4 must be undefined.

• 12I/T**3 and TS/T are only taken into account for elastic materials.

PCOMPG1 property

• The PCOMPG1 property entry is available to define a composite property which allows for a specific
material and failure theory for each ply.

• You select the material for each ply using the MIDi field on the PCOMPG1 entry. The MIDi field can
select a MAT1, MAT2, MAT8, MAT9, or MAT11 bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-7
© 2023 Siemens
 4. Element support

If you select a MAT1, MAT9, or MAT11 entry for a ply material, you can use the MATFT bulk entry to
define the failure theory allowable stress and strain values for shell and solid composites. The ID of the
MATFT entry must be the same as the ID of the MAT1, MAT9, or MAT11 entry. You can define multiple
failure theory allowables on the same MATFT, and the software applies the specific failure theory you
select for the ply in the FTi field on the PCOMPG1 entry.

The MATFT entry is required to define the allowable stress and strain values with the MAT9 and MAT11
material entries.

For the MAT1 entry, if you use FT=HILL, HOFF, or TSAI, you can optionally specify the allowable stress
on the MAT1 entry directly instead of the MATFT. If the allowables are defined on both the MAT1 and
MATFT entries, the software applies the values on the MATFT.

The MATFT entry is not supported with the MAT2 or MAT8 entry. You must define the allowable stress
on the MAT2 entry, and the allowable stress or strain on the MAT8 entry.

For shell composites, only FT = HILL, HOFF, TSAI, and STRN are supported (FT = STRS and TS are not
supported). In addition, the transverse material properties are ignored by shell elements.

FT = HILL or HOFF: Zt, Zc, S13, and S23 are ignored.

FT = TSAI: Zt, Zc, S13, S23, F13, and F23 are ignored.

FT = STRN: Zet, Zec, Se13, and Se23 are ignored.

• When a composite property is used, the software does not create a smeared, homogeneous shell
representation using classical lamination theory. Instead, an integration scheme similar to what is
used for solid composites is used.

• Failure index and strength ratio output are supported for all failure indices.

• In SOL 402, Z0 is added to the offset introduced on the element bulk entry (ZOFFS). If element forces
are required, bending moments are given with respect to the updated neutral plane.

PCOMP and PCOMPG properties

• PCOMP and PCOMPG property entries are supported in SOL 401 to assist you in adapting laminate
models that were created for non-SOL 401 solution sequences to SOL 401.

During the SOL 401 solve, when the software encounters a PCOMP or PCOMPG bulk entry in the input
file, it internally converts it into a PCOMPG1 bulk entry. Because the PCOMPG1 bulk entry does not
have a LAM field, the software ignores the LAM field specification on the PCOMP or PCOMPG bulk
entry when it performs the conversion and instead assumes the LAM field default of "Blank".

Formulation options for laminate shell elements

4-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Shell elements

• In SOL 401, you can optionally use laminate shell elements whose transverse shear stress formulation
produces results that are independent of the choice of material coordinate system. The optional
formulation is independent of the material coordinate system because it accounts for all three
moments, Mx, My, and Mxy in Figure 1, whereas the default formulation ignores Mxy. Thus, depending
on the stress state and the choice of material coordinate system, the default formulation may lead to
less accurate results.

To use the formulation that accounts for all three moments, specify SYSTEM(715) = 1.

Figure 4-1. Moments acting on a laminate shell element in the XY-plane

Material support

• The MAT1 and MATT1 bulk entries define isotropic materials for any shell and composite property.

• The MAT2 and MATT2 bulk entries define anisotropic materials for any shell and composite property.

• The MAT8 and MATT8 bulk entries define orthotropic materials for any shell and composite property.

• The MAT9 and MATT9 bulk entries define anisotropic materials for any shell and composite property.

• The MAT11 and MATT11 bulk entries define orthotropic materials for any shell and composite
property.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-9
© 2023 Siemens
 4. Element support

• The nonlinear plastic and creep material are only supported for the PSHELL.

• User defined materials defined with the UMAT external program are only supported for the PSHELL
property.

• The TABLEM5 bulk entry defines tabular functions for progressive ply failure with the UD damage
model.

• SOL 402 adds support for MATSR strain rate dependence.

Material coordinate system

The material coordinate system is used to define the orientation of material properties when orthotropic
or anisotropic materials are selected. In addition, stress and strain results are always output in the
material coordinate system. The material coordinates are updated when large rotation occurs.

The X-axis of the element material coordinate system for the shell element is determined as follows:

• Option 1: If a material coordinate system is not selected on the element entry, the X-axis of the
material coordinate system is, by default, aligned with the element edge defined by grid points G1
and G2. The X-axis can optionally be rotated by defining THETA on the element entry.

• Option 2: A material coordinate system can be selected with the MCID field on the element entry. The
X-axis of the selected material coordinate system is projected onto the plane of the shell to define the
shell material X-axis.

In addition, if a composite property is used for the element with the PCOMPG1 entry, a unique THETA
value can be defined for each ply. The THETA on the ply rotates the material x-axis for each ply relative to
the element material x-axis as described above.

The material Z-axis is the positive out-of-plane shell normal defined by the right-hand-rule and the grid
point connection order. The material Y-axis is determined by the cross product of the material X-axis and
Z-axis.

Supported Loads

• Pressure loads are supported with the PLOAD, PLOAD2, or PLOAD4 bulk entries.

• General loads are supported with the FORCE, FORCE1, FORCE2, MOMENT, MOMENT1, MOMENT2,
DAREA, and SLOAD.

• Body loads are supported with the GRAV, RFORCE, and RFORCE1. The RFORCE2 is not supported.

In SOL 401, body loads are also supported with the ACCELi.

• Temperature loads with variation through the element thickness are not supported using the TEMPP1
bulk entry.

4-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Shell elements

Shell element output summary

• Engineering stress and strain are always output.

• Stress and strain results are always output in the material coordinate system. The material coordinates
are updated when large rotation occurs and large displacements effects are requested with
PARAM,LGDISP,1.

• Shell elements using a PSHELL support stress/strain results at grid or Gauss points. Stress and strain is
computed at the top and bottom of the element. The STRCUR describer, which requests output at the
middle plane, is not supported.

• Composite shell elements using the PCOMPG1 entry only support stress/strain results at grid points.

• The CENTER, CUBIC, or SGAGE options on the STRESS and STRAIN case control commands are not
supported.

• The OMID parameter which is used in other solutions to output stress and strain in the element
coordinate system is not supported.

• The Z1 and Z2 fields on the PSHELL bulk entry, which define fiber distances for stress calculations for
other solution types, are not supported by SOLs 401 and 402.

• For composite shell elements, FI and SR is supported for all failure indices.

• The FORCE case control command can be used to request shell element resultants in material
coordinates.

• Grid point forces are supported.

• Shell elements support surface-to-surface contact and surface-to-surface glue. Edge-to-edge and
surface-to-edge glue is not supported for shells in SOL 401. Both glue and contact results are support
for the shell elements.

Additional information

• The SNORM parameter and bulk entry are only supported by the CTRIAR and CQUADR elements.

• The K6ROT parameter and bulk entry are only supported by the CTRIA6 and CQUAD8 elements.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-11
© 2023 Siemens
 4. Element support

4.4 SOL 401- Tension-only shell element

A tension-only shell element is available for SOL 401. You define the connectivity of the tension-only
shell element with the CQUADR or CQUAD4 bulk entries, and you define the properties with the
PSHLPNL bulk entry.

The tension-only shell element initially behaves in shell element status. The software converts the
element to shear panel status according to the following conversion threshold you define in the SC and
SDIR fields on the PSHLPNL entry.

SDIR character input Criteria to convert the element to shear panel status
"PSMIN" Minimum principal stress < SC.
"ESYSX" σxx in the element coordinate system < SC.
"ESYSY" σyy in the element coordinate system < SC.
"MSYSX" σxx in the material coordinate system < SC.
"MSYSY" σyy in the material coordinate system < SC.

When the tension-only shell element is in shell element status, it is consistent with the shell element
used in SOL 401. When it is in shear panel status, it is consistent with the CSHEAR element used in the
linear solutions, such as SOL 101.

When the conversion from shell to shear panel occurs, the software does a stiffness update regardless
of the KUPDATE setting on the NLCNTL bulk entry. Once the software converts the element from shell
to shear panel, the software will not revert the element back to shell status, unless you start a new
sequentially independent subcase. Then the element begins again in shell element status.

The conversion threshold can be satisfied at an iteration before a time step has converged, and the
conversion from shell to shear panel will occur during the iterations at the current time step.

By default, the shell to shear panel conversion behavior is on. You can define parameter setting
PARAM,TENSOQD,1 to turn the conversion behavior off, and the element remains as a shell element.
In this situation, the element can behave nonlinearly (material and geometric).

When the conversion behavior is on, the tension-only shell element does not consider any material or
geometric nonlinear conditions. Although, the software will compute the nonlinearities for any other
element types that you include with the tension-only shell element.

When the element is converted to shear panel status, it no longer includes any rotational stiffness. Any
loads or constraints defined to the rotational DOF on the tension-only shell are no longer applied when
the element is in shear panel status.

When the element is in shear panel status, it resists the action of tangential forces applied to its edges,
and the action of normal forces if the effective extensional stiffness is defined. The element formulation
is defined with the effective extensional area which is equivalent to rods on the perimeter of the

4-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401- Tension-only shell element

element. You define the effective extensional stiffness with the F1, F2, F3, and F4 fields on the PSHLPNL
entry, which the software uses to compute the effective extensional areas Ai:

where T is the element thickness, Ap is the panel surface area defined by half the vector cross product
area of the diagonals, and L12, L34, L23, and L41 are the lengths of sides 1-2, 3-4, 2-3, and 4-1,
respectively.

Figure 4-2. Extensional Area for Shear Panel

You can use the ESHLPNL command to output the status (shell or shear panel behavior) and, if
applicable, the conversion time for each tension-only shell element at each time point. The conversion
time is the time point during the solution when the tension-only shell element status changes from shell
to shear panel.

• For CQUAD4 or CQUADR elements that reference PSHLPNL bulk entries, in the ESHLPNL command
output, STATUS = 0 denotes that the element behaves as a shell element up to that time point.
For such a case, NONE is listed as the corresponding conversion time. STATUS = 1 denotes that the
element behaves as a shell element up to the corresponding conversion time and then behaves as
a shear panel for the remainder of the solution unless you start a new sequentially independent
subcase.

• For CSHEAR elements that reference PSHEAR bulk entries, because they behave as a shear panel
throughout the solution, in the ESHLPNL command output, STATUS =1 and the corresponding
conversion time is 0.0.

An example of ESHLPNL command output in an .f06 file is as follows:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-13
© 2023 Siemens
 4. Element support

In this example:

• Elements 3, 4, and 5 behave as shell elements through the time point for the output of 0.5.

• Elements 6, 7, and 8 converted to behave as shear panels at the previous time point of 0.25.

• Element 9 converted to behave as a shear panel at the time point for the output of 0.5.

• Because elements 41 and 42 have STATUS =1 and a corresponding conversion time of 0.0, they are
CSHEAR elements that reference PSHEAR bulk entries. The other elements are CQUAD4 or CQUADR
elements that reference PSHLPNL bulk entries.

Conversion criteria computation

By default, the software converts an element when the average value from all of its Gauss points
satisfies the criteria.

You can define the parameter setting PARAM,TOQDGAUS,0, and the software will convert an element
when the value at any of its Gauss points satisfied the criteria.

For more information, see TOQDGAUS in the Simcenter Nastran Quick Reference Guide.

Element results output

When the tension-only shell element is in shell status, the results output format is same as regular shell
element.

When the tension-only shell element is in shear panel status, the following output are available
according to the case control request:

• The components of force at the corners of the element.

• The shear flows (force per unit length) along each element edge.

• The average shear stress and the average shear strain.

The positive directions for these quantities are identified in the following figure.

4-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401- Tension-only shell element

Figure 4-3. Shear Panel Corner Forces and Shear Flows

Extensional force output

The shear panel element and the tension-only shell element in shear panel status both compute
extensional forces when the effectiveness factors (F1, F2, F3, F4) are defined on the property entries
(PSHEAR and PSHLPNL bulk entries). The software does not include the resulting extensional force with
the actual element output.

You can define CBAR, CBEAM, or CROD elements on the perimeter of the shear panel and the tension-
only shell elements, and define the parameter setting PARAM,ADTOQDLD,YES, and the software will add
the extensional force computed for the shear panel and the tension-only shell elements to the axial
force computed for the line elements. The total axial force on the CBAR, CBEAM, or CROD elements will
include their own axial force contribution, plus the extensional force computed for all shear panel and
the tension-only shell elements that share the same edge.

By default, ADTOQDLD is set to NO, and the extensional force is not output. The output for the CBAR,
CBEAM, or CROD elements will only include their own axial force contribution.

Note that the stiffness you define for the extensional edges and the stiffness you define for the CBAR,
CBEAM, or CROD elements are independent of each other. You can increase or decrease the stiffness for
any of these elements independently, which then contributes to the global stiffness.

For more information, see ADTOQDLD in the Simcenter Nastran Quick Reference Guide.

For more information, see SOL 401 - Shear panel element in this guide.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-15
© 2023 Siemens
 4. Element support

4.5 SOL 401 - Shear panel element

The shear panel element is available for SOL 401. You define a shear panel element with the CSHEAR
bulk entry and its properties with the PSHEAR bulk entry.

A shear panel is a two-dimensional structural element with four grid points that supports shear stress
in its interior, and the action of normal forces when the effectiveness factors are defined on the PSHEAR
bulk entry. It is used in situations where the bending stiffness and axial membrane stiffness of the plate
are negligible.

An application of the shear panel element is in the analysis of thin reinforced plates and shells, such as
thin aircraft skin panels. For these applications, the shear panel element carries the in-plane shear, and
reinforcing rods carry the normal forces. This is particularly true when the actual panel is buckled or if it
is curved.

The shear panel element does not consider any material or geometric nonlinear conditions. However,
the software will compute the nonlinearities for any other element types that you include with the shear
panel element.

The shear panel element does not include rotational stiffness. Any loads or constraints defined on the
rotational DOF on the shear panel element are ignored.

You can define the effective extensional stiffness with the F1, F2, F3, and F4 fields on the PSHEAR entry,
which the software uses to compute the effective extensional areas Ai:

where T is the element thickness, Ap is an area defined by half of the magnitude of the vector cross
product of the diagonals, and L12, L34, L23, and L41 are the lengths of sides 1-2, 3-4, 2-3, and 4-1,
respectively.

For more information, see CSHEAR and PSHEAR in the Simcenter Nastran Quick Reference Guide.

4-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Shear panel element

Figure 4-4. Extensional Area for Shear Panel

Element results output

The following output are available according to the case control request:

• The components of force at the corners of the element.

• The shear flows (force per unit length) along each element edge.

• The average shear stress and the average shear strain.

The positive directions for these quantities are identified in the following figure.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-17
© 2023 Siemens
 4. Element support

Figure 4-5. Shear Panel Corner Forces and Shear Flows

Extensional force output

The shear panel element and the tension-only shell element in shear panel status both compute
extensional forces when the effectiveness factors (F1, F2, F3, F4) are defined on the property entries
(PSHEAR and PSHLPNL bulk entries). The software does not include the resulting extensional force with
the actual element output.

You can define CBAR, CBEAM, or CROD elements on the perimeter of the shear panel and the tension-
only shell elements, and define the new parameter setting PARAM,ADTOQDLD,YES, and the software will
add the extensional force computed for the shear panel and the tension-only shell elements to the axial
force computed for the line elements. The total axial force on the CBAR, CBEAM, or CROD elements will
include their own axial force contribution, plus the extensional force computed for all shear panel and
the tension-only shell elements that share the same edge.

By default, ADTOQDLD is set to NO, and the extensional force is not output. The output for the CBAR,
CBEAM, or CROD elements will only include their own axial force contribution.

Note that the stiffness you define for the extensional edges, and the stiffness you define for the CBAR,
CBEAM, or CROD elements are independent of each other. You can increase or decrease the stiffness for
any of these elements independently, which then contributes to the global stiffness.

For more information, see ADTOQDLD in the Simcenter Nastran Quick Reference Guide.

For more information, see SOL 401- Tension-only shell element in this guide.

4-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bar and beam elements

4.6 Bar and beam elements

SOL 401 and SOL 402 supports bar and beam elements defined with the CBAR and CBEAM entries.
The bar and beam elements support large displacements and rotations when large displacements are
requested with PARAM,LGDISP,1.

In SOL 402, CBAR defines the same element as CBEAM.

Physical properties

• The PBAR and PBARL entries define the physical properties for the BAR element.

• The PBEAM and PBEAML entries define the physical properties for the BEAM element.

• The intermediate stations defined with the X/XB field are permitted on the PBEAM and PBEAML entries
if, for example, the beam cross section properties change in the middle. Although, output requests
are only supported at the ends A and B. The software ignores output requests at the intermediate
locations (0 < X/XB < 1.0).

PBEAML section properties for SOL 402

• SOL 402 only supports different cross sections at ends A and B without any intermediate sections. A
linear variation is assumed between the two ends.

• Beam sections of the following types are not supported: T1, T2, CHAN2, CROSS, H, BOX1, HEXA, HAT,
and HAT1. In that case, the software will automatically create the equivalent PBEAM bulk entry and
stress-recovery will not be performed. For beam sections of the following types: T1, T2, CHAN2, and
H, equivalent profiles exist in other axes (T, CHAN, CHAN1, I or I1).

• For beam sections of the following types: I, I1, CHAN, CHAN1, L, Z, T, BOX, and TUBE, the stress
recovery locations are located at the mid-thickness instead of the outer skin. Therefore, small
deviations can be observed compared to other Simcenter Nastran solutions, such as SOL 401.

Materials

• MAT1 and MATT1 are supported.

• In SOL 401, MAT1 and MATS1 are supported to define a plastic material. For the nonlinear material
behavior to be included in the solution, you must reference the nonlinear materials from the PBARL
and PBEAML property entries that define one of the following cross section types: TUBE, L (PBEAML
only), I, CHAN, T, BOX, BAR, I1, CHAN1, Z, and ROD.

SOL 401 supports the cross section types on the PBARL and PBEAML that are not listed above and the
PBAR and PBEAM entries if you reference a linear material entry. If you reference a nonlinear material
for these properties or cross section types, the solution ends with a fatal error.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-19
© 2023 Siemens
 4. Element support

You can optionally define a different cross section at ends A and B, and the software will compute
a linear variation. Cross section definitions at intermediate stations are ignored when a nonlinear
material is applied.

The CBAR and CBEAM elements in SOL 401 do not use a plastic hinge approach, which is used by
the CBEAM elements in SOL106. As a result, they are not limited to elastic-perfectly plastic materials
(H=0.0) defined with the MATS1 bulk entry. For the CBAR and CBEAM elements in SOL 401, you can
use the same plastic materials on the MATS1 entry which are supported for solid and shell elements,
such as H≠0.0 or stress-strain data.

• In SOL 401, MAT1 and MATCRP are supported to define a creep material. For the nonlinear material
behavior to be included in the solution, you must reference the nonlinear materials from the PBARL
and PBEAML property entries that define one of the following cross section types: TUBE, L (PBEAML
only), I, CHAN, T, BOX, BAR, I1, CHAN1, Z, and ROD.

The cross section types on the PBARL and PBEAML that are not listed above and the PBAR and PBEAM
entries are supported by SOL 401 if you reference a linear material entry. If you reference a nonlinear
material for these properties or cross section types, the solution will end with a fatal error.

You can optionally define a different cross section at ends A and B, and the software will compute
a linear variation. Cross section definitions at intermediate stations are ignored when a nonlinear
material is applied.

• In SOL 402, for nonlinear material, MATS1 can be used in PBARL and PBEAML property entities with
profiles BAR, BOX, CHAN, CHAN1, I, I1, L, T, TUBE, and Z. If a plastic material is used (MATS1 bulk entry
with TYPE=PLASTIC), the behavior is not limited to elastic-perfectly plastic. The material behavior is
calculated by numerical integration in the central section of the element. It is constant for the whole
element. To have a behavior close to a plastic hinge, you have to use a finer mesh.

Supported loads

• The PLOAD1 bulk entry is supported to apply distributed loads.

• Bar and beam elements also support the general loads that SOLs 401 and 402 support. For example
the elements support forces using the FORCE, FORCE1, and body loads defined with the GRAV and
RFORCEi bulk entries.

SOL 401 also supports DAREA bulk entries and ACCELi body loads bulk entries.

Bar and beam element output summary

• Element results include stress, element force, total strain, elastic strain, and thermal strain.

• Stress and force output requests are only supported at the ends A and B. The software ignores output
requests at the intermediate locations (0 < X/XB < 1.0).

• Stress, strain, and force results are always output in the element coordinate system.

4-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bar and beam elements

• The stress and strain output is similar to the existing format for other solutions, except that SOL 401
and 402 do not compute the minimum and maximum values (S-MIN and S-MAX) and the margin of
safety values (M.S. -T, and M.S. -C).

• The reported stresses SXC, SXD, SXE, and SXF are a combination of the normal and bending stress
reported in the element axial direction at the cross section locations C, D, E, and F.

• The element force output includes the bending moment and shear force in planes 1 and 2, axial force,
total torque, and warping torque.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-21
© 2023 Siemens
 4. Element support

4.7 Spring and damper elements

Spring elements

You can use the CELAS1, CELAS2, CBUSH1D, and CBUSH elements in SOL 401 and SOL 402 to define
spring stiffness.

CELAS1- Scalar Spring Connection

• A single CELAS1 element connects two degrees-of-freedom at two different grid points. It behaves as
a simple extension/compression or rotational spring, carrying either force or moment loads.

• If you define the CELAS1 element between non-coincident grid points, the CELAS1 element does
not account for the distance between the connecting grid points when transferring loads. This is
important when you expect your spring stiffness to carry transverse loads. The CELAS1 element is safe
to use when connecting coincident grid points. The CBUSH element is recommend when connecting
non-coincident grid points.

• With the CELAS1 element, you can define either a constant or a nonlinear stiffness.

• You define the constant stiffness in the Ki field on the PELAS entry. The constant spring stiffness
definition is independent of the displacement.

• You define the nonlinear spring when the CELAS1 references both the PELAS and PELAST bulk
entries. The TKNID field on the PELAST entry selects a TABLEDi entry, which defines the force versus
displacement data.

• In SOL 401, the CELAS1 element does not support large displacement effects when PARAM,LGDISP,1
is defined. You can include the CELAS1 element in a solution with PARAM,LGDISP,1 defined, but it
should not be located in a region of the model where large rotations occur. If you define the CELAS1
as a nonlinear spring, the software uses the nonlinear spring definition whether large displacements
are turned on or off.

SOL 402 does not have this limitation.

• You can request force and stress output for the CELAS1 element.

• In SOL 402, G1 and G2 must be grid points, not scalar points.

CELAS2- Scalar Spring Connection

• A single CELAS2 element connects two degrees-of-freedom at two different grid points. It behaves as
a simple extension/compression or rotational springs, carrying either force or moment loads.

• If you define the CELAS2 element between non-coincident grid points, the CELAS2 element does
not account for the distance between the connecting grid points when transferring loads. This is

4-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Spring and damper elements

important when you expect your spring stiffness to carry transverse loads. The CELAS2 element is safe
to use when connecting coincident grid points. The CBUSH element is recommend when connecting
non-coincident grid points.

• The CELAS2 element only supports a constant spring stiffness which is independent of the
displacement. This stiffness is defined in the Ki field on the CELAS2 entry. No property entry is used
with the CELAS2 element.

• In SOL 401, the CELAS2 element does not support large displacement effects when PARAM,LGDISP,1
is defined. You can include the CELAS2 element in a solution with PARAM,LGDISP,1 defined, but it
should not be located in a region of the model where large rotations occur.

SOL 402 does not have this limitation.

• You can request force and stress output for the CELAS2 element.

• In SOL 402, G1 and G2 must be grid points, not scalar points.

CBUSH1D- Rod Type Spring Connection

• The CBUSH1D element is a one dimensional axial spring.

• The CBUSH1D element stiffness and forces are only axial. It can be used to define an axial spring
between coincident or non-coincident grid points. When the grid points are coincident, the x-axis of
the coordinate system selected with the CID field on the CBUSH1D entry becomes the axial direction.
When the grid points are non-coincident, the line from grid point A to grid point B is the element axis.

• In SOL 401, the CBUSH1D element connecting non-coincident grid points is the only spring that
supports large displacement effects when PARAM,LGDISP,1 is defined.

SOL 402 does not have this limitation because in SOL 402 all springs non-coincident grid points
support large displacement effects.

• A CBUSH1D element connecting coincident grid points does not support large displacement effects
when PARAM,LGDISP,1 is defined. In this case, the CBUSH1D element axis remains fixed.

• The CBUSH1D element supports either a constant or a nonlinear stiffness option.

The constant spring stiffness definition is independent of the displacement and is defined with the K
field on the on the PBUSH1D entry.

The nonlinear spring definition is a force versus displacement table. The nonlinear spring data is used
when large displacements are turned on or off with the parameter LGDISP.

The nonlinear spring is defined by the following fields in the continuation row on the PBUSH1D entry:

• “SPRING” should be defined in the field 2 of the continuation row.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-23
© 2023 Siemens
 4. Element support

• "TABLE" should be defined in field 3 of the continuation row.

• The ID of a TABLEDi entry should be defined in field 4 of the continuation row.

• The TABLEDi entry defines the force versus displacement relationship.

• You can request force and stress output for the CBUSH1D element.

CBUSH- Defines a generalized spring.

• A unique feature of the CBUSH element relative to the other spring elements is that it accounts for the
distance between the connecting grid points when transferring loads. As a result, it is a safe choice for
connecting either coincident or non-coincident grid points.

• The CBUSH entry supports either a constant, or a nonlinear stiffness option:

• The constant spring stiffness definition is independent of the displacement. This stiffness is defined
in a “K” row on the PBUSH entry, following by a stiffness value for each of the six degree-of-
freedom.

• The nonlinear spring definition is a force versus displacement table. The nonlinear spring is defined
when the CBUSH entry references both the PBUSH and PBUSHT bulk entries. The TKNIDi fields on
the PBUSHT select the force versus displacement tables. The software uses the nonlinear spring
when large displacements are turned on or off with the parameter LGDISP.

• In SOL 401, the CBUSH element does not support large displacement effects when PARAM,LGDISP,1 is
defined. You can include the CBUSH element in a solution with PARAM,LGDISP,1 defined, but it should
not be located in a region of the model where large rotations occur.

SOL 402 does not have this limitation.

• You can request force, stress, and strain output for the CBUSH element.

• The system cell 665 is available to globally turn off the computation of the CBUSH coupling moments
when the connecting grid points are not coincident. The system cell applies to all solutions except for
SOL 402.

SYSTEM(665) = 0 (default) The coupling moments are computed.

SYSTEM(665) = 1 The coupling moments are not computed.

Damper elements

CDAMP1 and CDAMP2- Scalar Damper Connections

4-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Spring and damper elements

• A single CDAMP1/CDAMP2 element connects two different degrees-of-freedom at two different grid
points. It behaves as a simple extension/compression or rotational damper, carrying either force or
moment loads in function of the relative speed between the two degrees-o- freedom.

• Both CDAMP1 and CDAMP2 elements must be defined between non-coincident grid points and the
initial position has no consequence on the damping force.

• With the CDAMP1 element, you can define a constant value of viscous damping using the PDAMP bulk
entry.

With the CDAMP2 element, you can define a constant value of viscous damping directly in the
CDAMP2 bulk entry. You do not need a reference to a material or property entry.

• In SOL 402, the G1 and G2 grid points must be grid points not scalar points.

You can request force and stress output for the CDAMP1 or CDAMP2 element. The value of the
generalized force is defined by the equation:

where:

• C is the viscous damping defined in the PDAMP bulk entry for the CDAMP1 element, or directly defined
in the CDAMP2 bulk entry for the CDAMP2 element

• are the speeds of the DOF G1 and G2 in component C1 and C2

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-25
© 2023 Siemens
 4. Element support

4.8 SOL 401 - Rod element

The rod element is available for SOL 401. You define the rod element connectivity with the CROD bulk
entry and its properties with the PROD bulk entry.

The CROD element is a straight cylindrical element with constant axial and torsional stiffness along its
length. You define the cross section area (A), the torsional constant (J), and reference a MAT1 material
entry on the PROD entry.

The CROD supports large displacements and rotations when large displacements are requested with
PARAM,LGDISP,1. It does not support material nonlinear conditions.

The x -axis of the element coordinate system is defined by a line connecting end a to end b, as shown in
the figure below. You can request axial force and torque output with the FORCE case control command.
The positive directions for the forces are indicated in the figure.

Figure 4-6. Rod Element Coordinate System and Element Forces

You can also request axial and torsional stress output with the STRESS case control command. The
positive stress directions are the same as those indicated for the force vectors in the figure above.

For more information, see CROD and PROD in the Simcenter Nastran Quick Reference Guide.

4-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Fixed rotational degrees-of-freedom (SOL 401)

4.9 Fixed rotational degrees-of-freedom (SOL 401)

The 3D solid, axisymmetric, plane stress, and plane strain elements have rotational degrees of freedom,
but when the elements are either not connected, or connected only to each other, the rotational degrees
of freedom have no stiffness. Rotational degrees of freedom without stiffness do not affect the solution.

To improve performance, for the following elements, the software applies a fixed constraint to the
rotational degrees of freedom on the grid points that are not connected to elements with rotational
stiffness. The performance improvement is not available when the iterative solver is requested with
SOLVER=ELEMITER on the NLCNTL bulk entry.

• 3D solid elements CHEXA, CTETRA, CPENTA, and CPYRAM

• Axisymmetric elements CTRAX3, CTRAX4, CQUADX6, and CQUADX8

• Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, and CPLSTS8

• Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, and CPLSTN8

Examples of elements that have rotational stiffness include the CBAR, CBEAM, CBUSH, CBUSH1D,
CELAS1, CELAS2, CONM1, CONM2, CTRIA3, CQUAD4, CTRIA6, CQUAD8, CROD, CSHEAR, MPC, RBAR,
RBE2, and RBE3.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-27
© 2023 Siemens
 4. Element support

4.10 Rigid elements

SOLs 401 and 402 support the RBE2, RBAR, and RBE3 elements. In the modal subcases in which
ANALYSIS=MODAL, CYCMODES, or FOURIER, the software represents the rigid elements with MPC
equations. In the static, transient dynamics, and preload subcases in which ANALYSIS=STATICS,
DYNAMICS, or PRELOAD, the software always represents RBE3 elements with MPC equations.

SOL 401 - RBE2 and RBAR in static, dynamics, and preload subcases

In SOL 401 subcases where ANALYSIS=STATICS, DYNAMICS, or PRELOAD, the RIGID case control
command controls whether the RBE2 and RBAR elements include large displacement effects and thermal
expansion.

When RIGID=STIFF or RIGID=AUTO (default) and large displacements are requested with
PARAM,LGDISP,1, the RBE2 and RBAR elements use a stiff element method to compute the large
displacement effects. With the stiff element method, the software internally replaces the RBE2 and RBAR
elements with either a stiff beam element or a stiff spring element. The stiff element then accounts for
large displacements and rotations, including thermal expansion.

An alternate nonlinear multipoint constraint (MPC) method is available. When you include the
RIGID=NONLIN option and large displacements are requested with PARAM,LGDISP,1, the RBE2 and RBAR
elements will use a nonlinear MPC method to compute the large displacement effects. The software
recomputes the MPC relationships when the rigid elements rotate. The RIGID=NONLIN option couples all
six DOF.

With the nonlinear MPC method, the software adds the dependent DOF to the multipoint constraint
set (m-set), thus eliminating this DOF from the analysis set (a-set). As a result, if your model includes
many RBE2 and RBAR elements, the nonlinear MPC method can be more efficient than the stiff element
method.

The RIGID=NONLIN option does not support thermal expansion of the RBE2 and RBAR elements, so you
must use the stiff element method if thermal expansion is required. The stiff element method is still used
by default when large displacements are requested with PARAM,LGDISP,1. If you are running a small
displacement analysis with PARAM,LGDISP,-1 (default), and you require thermal expansion, you must
explicitly define RIGID=STIFF.

When the RIGID=NONLIN option is selected, the coefficients for the constraint equation can vary at each
iteration based on the change in the rotations for the independent grid. As a result, the multipoint
constraint equations and the multipoint constraint transformations are recomputed. For models which
include many nonlinear rigid elements with many iterations, this will increase the solution time.

See SOL 401 - Nonlinear MPC mathematical description below.

Input summary for SOL 401

4-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Rigid elements

• When RIGID=AUTO (default) and PARAM,LGDISP,-1 (default), the software automatically applies the
RIGID=LINEAR option. Specifically, the RBE2 and RBAR elements do not include large displacement
effects or thermal expansion.

• When RIGID=AUTO (default) and PARAM,LGDISP,1, the software automatically applies the behavior
consistent with RIGID=STIFF and PARAM,LGDISP,1. Specifically, the RBE2 and RBAR elements use a stiff
element method to compute large displacement effects, and they include thermal expansion.

• When RIGID=STIFF and PARAM,LGDISP,-1 (default), the RBE2 and RBAR elements do not include large
displacement effects, but they do include thermal expansion.

• When RIGID=STIFF and PARAM,LGDISP,1, the RBE2 and RBAR elements use a stiff element method to
compute large displacement effects, and they include thermal expansion.

• When RIGID=NONLIN and PARAM,LGDISP,-1 (default), the RBE2 and RBAR elements do not include
large displacement effects or thermal expansion. The behavior is the same as RIGID=LINEAR.

• When RIGID=NONLIN and PARAM,LGDISP,1, the RBE2 and RBAR elements use a nonlinear MPC method
to compute large displacement effects, but they do not include thermal expansion.

• When RIGID=LINEAR, the RBE2 and RBAR elements do not include large displacement effects or
thermal expansion. This behavior is independent of the PARAM,LGDISP setting.

• The following occurs when thermal expansion is requested with the RIGID=STIFF option.

For the RBAR element, the software computes an average TEMP(LOAD) and TEMP(INIT) for the
element from the grid point values.

For the RBE2 element, the software computes an average TEMP(LOAD) and TEMP(INIT) for each leg of
the element using the values on the independent/dependent grid pairs such that each leg can have a
different thermal strain if the temperatures vary at the grids.

The rigid element thermal strains are calculated from

εthermal = α(AVGTEMP(LOAD) – AVGTEMP(INIT))

If TEMP(LOAD) or TEMP(INIT) are not defined, they are assumed to be zero.

• MPCFORCE and GPFORCE output are supported with all of the rigid elements. Since the software
internally replaces an RBAR or RBE2 with a stiff beam or spring element when RIGID=STIFF, these
elements are no longer represented as MPC equations. As a result, MPCFORCE output is not applicable
to these elements. GPFORCE and FORCE output is applicable.

• When RIGID=STIFF and you combine static, transient dynamics, and preload subcases in which RBE2
and RBAR elements include large displacement effects and modal subcases in your input file, the RBE2
and RBAR elements are treated as stiff beams in a static, transient dynamics, and preload subcase, but
are still treated as MPC equations in a modal subcase. If your rigid elements experience large rotations

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-29
© 2023 Siemens
 4. Element support

in a static, transient dynamics, and preload subcases, a sequentially dependent modal subcase will
use the deformed state from the previous statics subcase, but the MPC equations are still relative to
the unchanging global coordinate system.

With the RIGID=STIFF option, to compute large displacement effects and thermal expansion, the
software internally replaces the RBE2 and RBAR elements with either a stiff beam element, or a stiff
spring element. A coincident grid tolerance is used to determine if a beam or a spring is used. For the
RBAR, if the distance between the connecting grids is less than the tolerance, the stiff spring formulation
is used. For the RBE2, if the distance between the grid defined in the GN field on the RBE2 entry, and
any of the grids defined in the GM fields on the RBE2 entry, is less than the tolerance, the stiff spring
formulation is used. You can optionally define the coincident grid tolerance explicitly with the parameter
RGLCRIT. By default, it is automatically computed by the software:

Coincident Grid Tolerance = 1E-6 * LMODEL (units=length)

where LMODEL is the largest dimension of the model determined by the software.

You can optionally define the beam stiffness and area explicitly using the parameters RGBEAME and
RGBEAMA, respectively. By default, they are automatically computed by:

Beam Stiffness = 1e+2 * EMAX (units=force/length^2)

Beam Area = (LMODEL * 1e-2)^2 (units=length^2)

where EMAX is the largest Young’s modulus in the model. If no material is specified in the model, EMAX
is set to 1.0E12.

You can optionally define the spring stiffness explicitly using the parameter RGSPRGK. By default, it is
automatically computed by:

Spring Stiffness = EMAX * LMODEL (units = force/length)

See the RIGID case control command.

SOL 401 - Nonlinear MPC mathematical description

Nonlinear MPCs are an alternate method of enforcing rigid constraints in a nonlinear analysis. You can
request the nonlinear MPCs with RIGID=NONLIN or RIGID=AUTO for RBAR or RBE2 elements. The desired
effect of this methodology is to ensure that the length of the segment connecting the independent node
to the dependent node remains constant.

Let and be the respective coordinates of the independent and dependent nodes in the
reference configuration.

4-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Rigid elements

and is the length of this vector.

After deformation , the new position of the independent node will be:

The rotations associated with the independent node can be represented by and the corresponding
rotation matrix by .

The current position of the independent node can then be obtained by:

In index notation, this can be written as:

To obtain :

The finite rotation vector associated with the independent node can be represented by:

Let represent the largest absolute component of the rotation vector, that is,
.

The rotation magnitude can then be defined as:

And the rotation axis can be defined as:

The skew symmetric matrix associated with the rotation vector is then given by:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-31
© 2023 Siemens
 4. Element support

The rotation matrix is then the exponential of this skew symmetric matrix:

Constraints:

Restating the equation for translations of the dependent node in terms of translations and rotations of
the independent node:

The coefficients for the translations of the independent grid in the constraint equation then are:

The result of this equation is an identity matrix as expected.

The coefficients for rotations of the independent node that affect the translations of the dependent node
are:

Since, the constraint coefficients depend on the rotation matrix, they can potentially change in each
iteration. The enforcement of this constraint in each iteration by updating the constraint matrix is the
main difference between RIGID=LINEAR and RIGID=NONLIN.

SOL 402 - RBE1, RBE2, and RBAR element options

• RBE2 and RBE3 elements support large displacements (PARAM,LGDISP,1) and large strains
(PARAM,LGSTRN,1).

• The RIGID case control command is ignored and does not affect the behavior of the spring.

4-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Rigid elements

• The TEMP(LOAD) and TEMP(INIT) value used on RBAR elements is an average calculated from the grid
point values. On RBE2 elements, an average TEMP(LOAD) and TEMP(INIT) is calculated for each leg of
the element using the values on the independent/dependent grid pairs such that each leg can have a
different thermal strain if the temperatures vary at the grids.

The rigid element thermal strains are calculated from:

εthermal = α(AVGTEMP(LOAD) – AVGTEMP(INIT))

If TEMP(LOAD) or TEMP(INIT) are not defined, they are assumed to be zero.

• All rigid elements support MPCFORCE and GPFORCE output.

• GPFORCE output correctly accounts for large displacements.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-33
© 2023 Siemens
 4. Element support

4.11 Generalized plane strain (SOL 401)

A special plane strain formulation called generalized plane strain is available as an optional extension
to the standard plane strain formulation. Both formulations use the CPLSTN3, CPLSTN4, CPLSTN6, and
CPLSTN8 plane strain element types. To invoke the generalized plane strain option, the plane strain
elements need to reference a PGPLSN property bulk entry. The generalized plane strain option is only
supported in SOL 401, and is only applicable to small strain, small deflection structural analyses. These
structural analyses include linear static, creep, and plasticity analyses, and combination creep and
plasticity analysis.

Analysis with the generalized plane strain formulation is highly specialized and typically used to evaluate
the behavior of gas turbine compressor and turbine blades. For such an analysis, you mesh the cross
section of the blade with CPLSTN3, CPLSTN4, CPLSTN6, or CPLSTN8 elements. All of the elements in the
mesh should reference a single PGPLSN property bulk entry.

With the PGPLSN bulk entry, you can specify the following data:

• The material bulk entry that is referenced by the PGPLSN bulk entry. MAT1 and MAT3 material bulk
entries can be referenced.

• The control grid point. The control grid point is the location where out-of-plane loads or enforced
displacements are applied to the set of elements that reference the PGPLSN bulk entry.

• The element thickness in the undeformed state.

• Optional user-defined additive normal stiffness and rotational stiffness values.

• You can specify time-varying added normal and rotational stiffness terms. To do so, in an added
stiffness field on the PGPLSN entry, enter the identification number of a TABLEDi bulk entry. On the
TABLEDi entry,you will list tabular data to define how the added stiffness term varies with time.

For the generalized plane strain analysis, Simcenter Nastran calculates the standard in-plane plane
strain stiffness, but also calculates three net out-of-plane stiffness values relative to the displacement
coordinate system of the control grid point. Consequently, how you specify the displacement coordinate
system for the control grid point is very important. You should specify the displacement coordinate
system of the control grid point such that one axis is normal to the cross section and the other two axes
are parallel to the principal axes of the cross section. By so doing, the three net out-of-plane stiffness
values that Simcenter Nastran calculates represent the normal stiffness of the cross section, and the two
bending stiffness for symmetrical bending of the cross section.

Because the CPLSTN3, CPLSTN4, CPLSTN6, and CPLSTN8 plane strain elements can only be defined in
the XY- or XZ-planes of the basic coordinate system, the direction normal to the cross section is always
in the Z- or Y-direction, respectively of the basic coordinate system. Simcenter Nastran checks that one
of the axes of the displacement coordinate system of the control grid point coincides with the correct
normal direction and issues an error if one does not.

4-34 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Generalized plane strain (SOL 401)

Simcenter Nastran does not check the other two coordinate directions of the displacement coordinate
system for the control grid point. It is your responsibility to assure that these directions are parallel to the
principal axes of the cross section.

If you specify additive stiffness, the normal stiffness is added to the normal stiffness that Simcenter
Nastran calculates for the cross section. The additive rotational stiffness values are added to the bending
stiffness values as follows:

• If the model lies in the XY-plane of the basic coordinate system, the KR1 value on the PGPLSN bulk
entry is added to the bending stiffness about the X-axis of the displacement coordinate system of the
control grid point. the KR2 value on the PGPLSN bulk entry is added to the bending stiffness about the
Y-axis of the displacement coordinate system of the control grid point.

• If the model lies in the XZ-plane of the basic coordinate system, the KR1 value on the PGPLSN bulk
entry is added to the bending stiffness about the X-axis of the displacement coordinate system of the
control grid point. the KR2 value on the PGPLSN bulk entry is added to the bending stiffness about the
Z-axis of the displacement coordinate system of the control grid point.

You can apply loads to the control grid point and to the generalized plane strain element mesh. At the
control grid point, you can account for the centrifugal force that is attributable to the portion of the
blade from the cross section you are modeling to the blade tip. To allow you to define a mechanically
equivalent loading at the control grid point, you can specify not only a force that acts normal to the cross
section, but also the bending moments that act on the cross section about axes parallel to the principal
axes of the cross section.

To the generalized plane strain mesh, apply surface tractions, body forces, and in-plane enforced
displacements that you want to include in the analysis. For example, you can apply aerodynamic forces
to the grid points that lie on the periphery of the mesh.

From the net out-of-plane stiffness values and the loads that are applied to the control grid point,
Simcenter Nastran calculates the thickness change over the cross section. Similar to planes remaining
plane in pure bending of beams, Simcenter Nastran enforces that the surface defined by the thickness
change is planar. From the thickness change over the cross section, Simcenter Nastran calculates the
out-of-plane strain of the elements at the grid locations. During the solution of the finite element model,
Simcenter Nastran uses the out-of-plane strain and any surface tractions, body forces, and in-plane
enforced displacements that you specified.

If an enforced displacement and enforced rotations are applied at the control grid point, the thickness
change of the cross section is directly specified. From the thickness change, Simcenter Nastran calculates
the out-of-plane strain directly and the solution of the finite element model is as before.

Note the generalized plane strain element is not supported by glue or contact regions.

The following constitutive models are available with generalized plane strain elements:

• To model plasticity of an isotropic material, use the MAT1 and MATS1 bulk entries in combination.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-35
© 2023 Siemens
 4. Element support

• To model plasticity of an isotropic material with temperature-dependent properties, use some

combination of the MAT1, MATS1, MATT1, TABLEST, and TABLES1 bulk entries.

• To model plasticity of an orthotropic material, use the MAT3 and MATS1 bulk entries in combination.
The elastic portion of the response is orthotropic, and the plastic portion of the response is isotropic.

• To model plasticity of an orthotropic material with temperature-dependent properties, use some

combination of the MAT3, MATS1, MATT3, TABLEST, and TABLES1 bulk entries. The elastic portion of
the response is orthotropic, and the plastic portion of the response is isotropic.

• To model creep of an isotropic material, use the MAT1 and MATCRP bulk entries in combination.

• To model creep of an isotropic material with temperature-dependent properties, use the MAT1,
MATT1, and MATCRP bulk entries in combination.

• To model creep of an orthotropic material, use the MAT3 and MATCRP bulk entries in combination.

• To model creep of an orthotropic material with temperature-dependent properties, use the MAT3,
MATT3, MATCRP, and TABLEM1 bulk entries in combination. The elastic portion of the response is
orthotropic, and the creep portion of the response is isotropic.

For additional information, see the PGPLSN bulk entry in the Simcenter Nastran Quick Reference Guide.

4-36 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Element addition and removal

4.12 Element addition and removal

SOL 401 supports the following element addition and removal capabilities:

• The software can add or remove elements during a solution at pre-defined time points. For example,
you can represent a material removal process while the model is in a loaded state.

• The software can remove elements based on a state of strain at the element integration points. This
is useful to represent a rupture condition. You can define the removal strain state using an inelastic
strain (plasticity and creep), or using the total mechanical strain (elastic+inelastic mechanical strain).

The software adds or removes the associated element mass, damping, and stiffness from the solution.

The ELAR case control command is available to select the element add/removal set defined with the
ELAR, ELAR2, and ELARADD bulk entries. See Input summary below for the statics, dynamics, and
preload subcase specific details.

You define the add and removal of elements with the ELAR and ELAR2 bulk entries. The ELAR entry
references a group of elements, which is useful when you have a large number of elements to add or
remove. The ELAR2 entry lists elements directly for add or removal, so it is useful when you have fewer
elements. See the ELAR and ELAR2 entries for details.

The ELARADD bulk entry is also available to combine multiple ELAR and ELAR2 bulk entries into a single
add/removal set.

Input summary

• The TYPE field on the ELAR and ELAR2 entries defines the addition/removal criteria type:

TYPE = TIME: Element addition or removal based on time.

TYPE = RINELE: Element removal based on inelastic strain.

TYPE = RMECHE: Element removal based on mechanical strain.

• For static and dynamic subcases:

• The static and dynamic subcases support element addition and removal by time, and element
removal by strain.

• Element addition or removal is not supported in a statics subcase in which nonlinear buckling is
requested with the NLARCL=ID case control command.

• The ELAR case control command can be defined above the subcase level (global) or in a subcase.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-37
© 2023 Siemens
 4. Element support

An ELAR command in a statics or dynamic subcase and a definition at the global level are
equivalent. That is, if you define the ELAR command in a subcase, the software internally converts
it to a global definition. As a result, the element addition or removal will occur in the static or
dynamic subcase where the requested time or strain occurs, and not necessarily the subcase in
which the ELAR command was defined.

If you define multiple ELAR definitions globally and/or in subcases, the software combines and
applies all ELAR sets (global + subcase definitions) as a global set.

• For TYPE = TIME, the AC and RC fields on the ELAR and ELAR2 entries define the addition time and
removal time, respectively.

If the time defined for AC or RC is in the time range for a subcase, but not precisely a solution time
defined by the TSTEP1 bulk entry, a new solution time will be created for the element addition or
removal.

If AC or RC are not in the time range of one of the subcases, the software will not add or remove
the associated elements.

• For TYPE = TIME, by default, elements are added with strain. That is, the initial geometry at
time=0.0 is the undeformed reference state for the elements added with strain.

You can optionally add elements as strain free by defining YES in the STNFREE field on the ELAR and
ELAR2 entries. See Strain free addition details.

• For TYPE = RINELE, you enter the effective inelastic strain in which the element will be removed in
the RC field. The strain value you define includes strain contributions from both plasticity and creep
materials if both are defined on an element. Plastic and creep strain output can be requested with
the PLSTRN and CRSTRN case control commands, respectively.

• For TYPE = RMECHE, you enter the effective mechanical strain in the RC field in which the
element will be removed. The strain value you define includes the elastic and inelastic strains.
Elastic strain output can be requested with the ELSTRN case control command. For example, if an
element has both plastic and creep strain, the effective mechanical strain would be the sum of
the effective elastic, effective plastic, and effective creep strains. If the material is a user defined
material (UMAT), the effective mechanical strain is the equivalent mechanical strain computed from
mechanical strain components.

• The addition delta time (AD field on the ELAR and ELAR2 entries) and removal delta time (RD
field on the ELAR and ELAR2 entries) are time intervals used to add or remove the element mass,
damping, and stiffness. The delta time options slow the transition of adding or removing elements
which helps to prevent convergence problems.

If the delta time is greater than the time remaining in the subcase, it will be adjusted to equal the
remaining time in the subcase.

4-38 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Element addition and removal

If you define -1 in the AD or RD fields, the software will ramp the element addition or removal over
the remaining subcase time.

When the AD and RD fields are undefined, an element addition or removal occurs instantly.

• For preload subcases:

• The ELAR case control command must be defined in the preload subcase.

• Only element addition using TYPE=TIME is supported. The fields AC, AD, and STNFREE are ignored.
The software internally assigns AC to be the subcase time (time is constant for a preload subase),
AD=0.0, and STNFREE=YES.

Since element removal is not allowed in the preload subcase, an error is reported if RC or RD
are defined. An element added in a preload subcase can be removed in a later static or dynamic
subcase.

• A preload subcase can include an element addition set (ELAR command) or a bolt preload set
(BOLDLD command), but it cannot include both.

• Elements included in a bolt definition cannot be added or removed in any subcase (static, dynamic,
preload).

• A preload subcase in general (with and without the ELAR command) can include a new thermal
load set (TEMPERATURE command) and/or a new contact set (BCSET command). No other new
load sets are allowed in a preload subcase. Load sets defined globally or in previous subcases are
maintained in the preload subcase.

Additional information

• Element addition and removal can not occur in a modal, cyclic, or Fourier subcase. Although, the
add/remove status is retained for these subcases if they are sequentially dependent. For example, if an
element is added in a static subcase and the next subcase is a sequentially dependent modal subcase,
the added element will be active in the modal subcase.

• For TYPE=TIME, the following elements are supported:

The 3D solids elements CTETRA, CHEXA, CPENTA, CPYRAM with properties defined with the PSOLID or
PCOMPS entry.

The axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6.

The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8 including when defined as a
generalized plane strain element.

The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-39
© 2023 Siemens
 4. Element support

The chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8.

The bar and beam elements CBAR, CBEAM.

The shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, CTRIA3 with properties defined with
the PSHELL, PCOMP, or PCOMPG entries.

The spring elements CELAS1, CELAS2.

The bushing elements CBUSH1D, CBUSH.

The rigid elements RBE2 & RBAR can be added and removed for TYPE=TIME when large displacements
are requested (PARAM,LGDISP,1). The rigid elements are represented as stiff elements (RIGID=STIFF
or RIGID=AUTO, which is the default for large displacements). The software always adds the rigid
elements as strain free (it internally forces STNFREE=YES and AD=0.0 for the rigid elements).

• For TYPE=RINELE, the following elements are supported:

The 3D solids elements CTETRA, CHEXA, CPENTA, CPYRAM defined with the PSOLID entry.

The axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6.

The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8 including when defined as a
generalized plane strain element.

The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

The chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8.

The shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, CTRIA3 with properties defined with
the PSHELL entry.

• For TYPE=RMECHE, the following elements are supported:

The 3D solids elements CTETRA, CHEXA, CPENTA, CPYRAM defined with the PSOLID or PCOMPS entry.

The axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6.

The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8 including when defined as a
generalized plane strain element.

The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

The chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8.

4-40 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Element addition and removal

The shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, CTRIA3 with properties defined with
the PSHELL, PCOMP, or PCOMPG entries.

• The elements CMASSi, CONMi, and cohesive elements are not supported for adding and removing.

• The software automatically adds or removes from the solution any loads, boundary conditions, or
unconnected grid points that are referenced by elements which are added or removed.

Exceptions:

- Contact and glue conditions are not supported on elements being added or removed.

- MPCs or rigid elements cannot be defined on the same grid points of elements being added or
removed.

- A distributed load defined with the FORCDST bulk entry is not supported with the element addition
or removal.

• When you reference elements by an element addition/removal set to be added at a solution time
point, the software considers those elements as inactive at the start of the solution. The software
considers all other elements as active at the start of the solution.

Relative to a sequence of sequentially dependent (SD) subcases, elements can only be added one
time, and elements can only be removed one time. As a result, elements that are removed cannot be
added again.

For example, you can remove an element which was active at the start of the solution, or you can
remove an element which became active at a solution time point during the solution.

• You can only define one removal criteria for an element. For example, for the same element, you
cannot define both a removal based on a strain state and a removal based on time.

• If you include a non-sequentially dependent (NSD) subcase, the state of the solution is reset back to
the initial state, including the element add and remove status and the solution time which is reset
back to 0.0. When you define an NSD subcase, you are restarting the solution.

Strain free addition details

• For TYPE=TIME, you can add an element in a strain free state by defining YES in the STNFREE field on
the ELAR and ELAR2 entries. The grid point locations and the resulting element geometry at the add
time becomes the initial undeformed reference state for the added strain free elements. Deformation
after the add time will then begin to strain these elements. The STNFREE field default is NO, and
elements are added with strain. That is, the initial geometry at time=0.0 is the undeformed reference
state for the elements added with strain.

• The strain free addition is supported only with TYPE=TIME.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-41
© 2023 Siemens
 4. Element support

• Strain free elements are added at the time you define in the AC field. The delta time (AD field) is
always 0.0 for the strain free addition. As a result, the strain free elements are added immediately at
time=AC. If you define the delta time (AD≠0.0), the software will force it to 0.0 and issue a warning.

• The following elements can be added with strain (STNFREE=NO) or strain free (STNFREE=YES):

The 3D solid elements CTETRA, CHEXA, CPENTA, CPYRAM with properties defined with the PSOLID or
PCOMPS entry.

The axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6.

The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8 including when defined as a
generalized plane strain element.

The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

The chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8.

The bar and beam elements CBAR, CBEAM.

The shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, CTRIA3 with properties defined with
the PSHELL, PCOMP, or PCOMPG entries.

The spring elements CELAS1, CELAS2.

The bushing elements CBUSH1D, CBUSH.

• The rigid elements RBE2 & RBAR can be added and removed for TYPE=TIME when large displacements
are requested (PARAM,LGDISP,1). The rigid elements are represented as stiff elements (RIGID=STIFF
or RIGID=AUTO, which is the default for large displacements). The software always adds the rigid
elements as strain free (it internally forces STNFREE=YES and AD=0.0 for the rigid elements).

• You can remove elements that are added as strain free.

• At time=AC, the strain free elements are under an annealed condition: zero stress, strain, plastic
strain, etc. They exert zero forces on the rest of the model, which allows adding to be done
immediately at AC, without an adverse effect on the solution.

• At time=AC, the strain free elements have zero thermal strain. The software considers the
temperatures at time=AC as the new initial temperatures when computing thermal strain on these
elements at times>AC.

• The strain free element additions are supported with large displacement effects on or off.

When large displacement effects are on (PARAM,LGDISP,1), the software computes the strain as

4-42 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Element addition and removal

ε = ΔLAC/LAC,

where the displacement ΔLAC is computed relative to the add time (ΔLAC=0.0 at time=AC), and the
length LAC is computed using the updated geometry at time=AC.

When large displacement effects are off (PARAM,LGDISP,-1), the software computes the strain as

ε = ΔLAC/L0,

where the displacement ΔLAC is computed relative to the add time (ΔLAC=0.0 at time=AC), and the
length L0 is computed using the original geometry at time=0.0.

• At time=AC, the software considers the strain free element normals as the new initial element normal.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-43
© 2023 Siemens
 4. Element support

4.13 Improved architecture for small strain problems (SOL 401)

An element architecture is available for SOL 401 with small strains that improves performance for the
following elements:

● The 3D solid elements CHEXA, CTETRA, CPENTA, and CPYRAM referencing a PSOLID property.
● The axisymmetric elements CTRAX3, CTRAX4, CQUADX6, and CQUADX8.
● The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, and CPLSTS8.
● The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, and CPLSTN8.

When you run your analysis with large strains turned off (PARAM,LGSTRN,0), the improved approach is
used by default. You can switch the improved architecture off by defining SYSTEM(746)=0.

The following are not supported with the improved architecture. As a result, the software automatically
switches the improved architecture off if any of these are present.

● Dynamic subcase.
● Collapsed CHEXA element used in the crack simulation.
● J-integral output for a crack simulation.
● User defined materials requested with the MUMAT bulk entry.
● Adaptive meshing output requested with the ADAPTERR case control command.
● Element addition and removal requested with the ELAR case control command.
● MAT3 material entry defined in the model.oxy _newline.

Restarts:

You can use the improved architecture with a restart, although you must use the same architecture in
both the initial run and in the restart runs. For example, if your initial run includes only static subcases,
but the restart run includes a dynamic subcase, you will need to define SYSTEM(746)=0 for both runs
because the improved architecture is not supported with a dynamic subcase.

Element output:

When you use the improved architecture in a small strain analysis with nonlinear materials, you can use
the RESXTRP parameter on the NLCNTLG bulk entry to control how the software calculates the grid point
stresses for the elements that support the improved architecture.

When you specify RESXTRP = ON (the default), the software does the following:

1. Calculates the strain at the Gauss points.

2. Using the material law (constitutive relation), calculates the stress at the Gauss points from the
strain at the Gauss points.

3. Using the shape functions, extrapolates the stress and strain at the Gauss points to the
corresponding grid points.

4-44 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Improved architecture for small strain problems (SOL 401)

When you specify RESXTRP = OFF, the software does the following:

1. Calculates the strain at the Gauss points.

2. Using the shape functions, extrapolates the strain at the Gauss points to the corresponding grid
points.

3. Using the material law (constitutive relation), calculates the stress at the grid points from the strain
at the grid points.

When your model is dominated by the elements that support the improved architecture, specifying
RESXTRP=ON (the default) reduces the total data I/O.

Both RESXTRP settings produce identical grid point total strains, but the grid point stresses can differ as
illustrated in the following example.

Note:
The following example is simplified and provided for conceptual purposes only. The actual
extrapolation of Gauss point results to grid point results involves matrix algebra where the results
at multiple Gauss points are used to calculate the result at a single grid point.

Suppose that for a uniaxial stress state, the material behavior is elastic-perfectly plastic and the Gauss
point strain lies in the elastic portion of the stress-strain curve. For RESXTRP = ON, the software
calculates the Gauss point stress to be:

where E is the elastic modulus.

The shape functions act as weighting factors that are applied to the Gauss point results when the
software extrapolates the Gauss point results to the grid points. Thus, the grid point results are:

where N is the weighting that the shape functions apply to the Gauss point results when the software
extrapolates the Gauss point results to the grid points.

For RESXTRP = OFF, the software calculates the grid point strain to be:

which is identical to the grid point strain that the software calculates when RESXTRP = ON.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-45
© 2023 Siemens
 4. Element support

Depending on the value of N, the grid point strain could lie in the elastic or perfectly plastic region of the
stress-strain curve. If the grid point strain lies in the elastic region, the software calculates the grid point
stress to be:

which is identical to the grid point stress that the software calculates when RESXTRP = ON.

However, if the value of N is such that the grid point strain lies in the perfectly plastic region, the
software calculates the grid point stress to be:

where σy is the yield stress for the material.

Thus, in this example, except for the special case where:

the grid point stress results differ from those calculated when RESXTRP = ON.

This conclusion can be extended to actual elements because, as demonstrated in the example, the
RESXTRP = OFF option guarantees that the grid point stress and strain lie on the stress-strain curve,
whereas the RESXTRP = ON option does not.

Note:
If your model has linear materials only (PARAM,MATNL,-1 or no nonlinear material bulk entries),
SOL 401 always calculates the grid point stresses from the grid point strains.

4-46 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Error estimator for mesh refinement (SOL 401)

4.14 Error estimator for mesh refinement (SOL 401)

You can request stress norm, stress error norm, strain energy norm, and strain energy error norm output
when using SOL 401. The output is computed and stored on an individual element basis. Pre/Post uses
the output for adaptive meshing.

The output is supported for the following element types:

Solid elements CHEXA, CPENTA, CPYRAM, CTETRA (excludes CHEXA and

CPENTA elements referencing PCOMPS bulk entries)
Axisymmetric CQUADX4, CQUADX8, CTRAX3, CTRAX6
elements
Plane strain CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8 (includes elements
elements referencing PGPLSN bulk entries)
Plane stress CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8
elements

• The stress norm is calculated from:

• The stress error norm is calculated from:

• The strain energy norm is calculated from:

• The strain energy error norm is calculated from:

where

Ω is the element volume,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-47
© 2023 Siemens
 4. Element support

σunaveraged is the unaveraged stress vector,

σaveraged is an averaged stress vector computed at a grid point using the stress vectors from elements
connected to the grid point,

D matrix is the constitutive relation.

When computing σaveraged, stress values are not averaged across different element families, material
properties, material coordinate systems, orientation angles in 2D solid elements, and thicknesses in
plane stress elements.

You use the STRESS, STNERGY and STEP describers on the ADAPTERR case control command to request
the output.

• The ADAPTERR case control command must be defined above the subcases (globally).

• The STRESS describer requests the stress norm and the stress error norm.

• The STNERGY describer requests the strain energy norm and strain energy error norm.

• You can specify both the STRESS and STNERGY describers to request stress norm, stress error normal,
strain energy norm and strain energy error norm output.

• The software always outputs the maximum value on each element, for each output type requested,
by comparing the values from all solution steps. In addition, if you specify the STEP describer, the
software will output what you have requested at the output increment steps defined with the TSTEP1
entries.

For additional information, see the ADAPTERR case control command.

4-48 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

4.15 Progressive failure analysis in solid composites

You can model progressive ply failure in composite laminates that are meshed with composite solid
elements. Simcenter Nastran supports a unidirectional fiber reinforced ply damage model (UD) and an
enhanced unidirectional fiber reinforced ply damage model (EUD).

The UD model is based on a model developed by Ladeveze and Le Dantec (Damage modeling of the
elementary ply for laminated composites, Composites Science and Technology 43, 1992) in which
damage is linked to the transverse normal stress and in-plane shear stress.

The EUD model is obtained by further splitting damage variables in UD into two parts: diffuse damage
related parts, and crack density dependent parts. The EUD model damage depends on the transverse
cracking of the ply.

Both of the models can account for:

• Damage in fiber direction 11, damage in shear direction 12, damage in transverse direction 22.

• Damage linked to the stresses in the out-of-plane direction.

• Damage mechanisms: fiber breaking, diffuse damage (fiber-matrix debonding), transverse cracking in
matrix.

• Damage linked to time delay effects.

• Coupling with plasticity.

• Stress/strain-dependent elastic modulus.

The procedure for estimating ply damage is iterative. Using the material properties in the undamaged
state, Simcenter Nastran makes an initial calculation of the stress state. Simcenter Nastran uses this
stress state in the unidirectional ply model to calculate an initial estimate of ply damage. Based on these
damage values, Simcenter Nastran calculates the material properties in the damaged state. With these
values for the material properties, Simcenter Nastran solves the model to obtain the updated stress
state. Simcenter Nastran uses the updated stress state in the ply model to calculate a second estimate of
the ply damage, and continues iterating until the ply damage values converge.

The converged damage values are termed the static damage. If you optionally include time delay effects,
the final damage values for the time step are the static damage values adjusted for the time delay.

To use the progressive ply failure capability, model the laminate with CHEXA and CPENTA solid elements
that reference PCOMPS bulk entries. In the MIDi fields of the PCOMPS bulk entries, enter the MID of
MAT11 bulk entries to define the linear elastic properties of the plies in the undamaged state. To
define the material properties and parameters that are related to progressive ply failure model, include
MATDMG bulk entries that have the same MID as the MAT11 bulk entries. To obtain ply failure results
output, include a PFRESULTS case control command.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-49
© 2023 Siemens
 4. Element support

You can use the CHEXCZ and CPENTCZ cohesive elements to model the interface between the different
plies. In this case, you model the plies with composite solid elements with a cohesive element defined
between the plies.

Additional details for the UD and EUD models:

• The UD and EUD models are both supported by composite solid elements.

• The UD and EUD models only support orthotropic materials. The material ID defined for a composite
ply on the PCOMPS entry references a MAT11 and a MATDMG. You enter PFA in the FTi field on the
PCOMPS entry.

• The UD and EUD models both require that you specify PARAM,MATNL,1 to activate the damage
property. By default, PARAM,MATNL,-1, and PFA behavior is turned off.

• The UD and EUD models both support geometry nonlinear.

• You can include both the UD and EUD models on different plies on the same composite defined with
the PCOMPS entry.

• The PFRESULTS case control command includes the CRKDSTY describer to request the crack density
output. The ODAMGPFR datablock stores the crack density output.

When you include the CRKDSTY describer on the PFRESULTS command, the EUD model outputs the
transverse crack density output. It is a scalar value reported at the mid ply location for each ply at the
element corners. The crack density is dimensionless.

• Both the UD and EUD models allow you to include coupling with plasticity. If you have included
the coupling with plasticity, you can define the PLSTRN case control command in a subcase to
request plastic strain output at grid points. The plastic strain at the Gauss points is not computed for
composite solids.

• You can define six damage variables for the EUD method; d11, d22, d33, d12, d23, d13, which
correspond to the variables df, d', d', d, d23, d in the constitutive model, respectively. You can include
the DAMAGE describer on the PFRESULTS command to request the damage output. The damage
values are reported at the mid ply location (per ply at the element corners). For both the UD and EUD
models, damage values are computed relative to the ply coordinate system and are scalar quantities.

• For both the UD and EUD models, when you include the STATUS describer on the PFRESULTS
command, a damage status is computed as an element result. The integer meaning of each damage
status (0, 1, 2, or 3) is documented on the PFRESULTS command.

• For both the UD and EUD models, within a single ply, if the worst damage value is greater than 0.0
on a Gauss point, the software considers the ply as damaged. If the worst damage value on all Gauss
points reaches the maximum allowed damage value specified in the DMAX field on the MATDMG
entry, the ply has completely failed. The DMAX default is 0.999.

4-50 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

• For both the UD and EUD models, the dissipated energy requested with the ENERGY describer on the
PFRESULTS case control command represents the energy dissipated due to damage and plasticity in
the material. The output is a single scalar value per element.

• For both the UD and EUD models, stress and strain can be requested for specific elements, by ply and
in the ply coordinate system. The plastic strain is only output at the middle location of each ply.

• The shear damage (d12) for the UD ply failure model supports a nonlinear function of thermodynamic
force Y. You can specify the nonlinear function with the TABLEM5 bulk entry, which is referenced by
the TID field on the MATDMG bulk entry. The TABLEM5 specifies the function d12=f(sqrt(Y)), where
d12 is the y data, and sqrt(Y) is the x data.

Unidirectional (UD) ply model

You can select the UD model by entering UD in the PPFMOD field on the MATDMG entry. The
unidirectional ply model uses the following equation for the strain energy density at a point in a ply. This
equation accounts for damage to the ply and is used to formulate expressions for element stiffness and
thermodynamic force.

Equation 4-1.

where:

• The 1-direction is the fiber direction.

• The 2-direction is the in-plane transverse direction.

• The 3-direction is the out-of-plane transverse direction.

• d11, d22, and d12 are the damage variables.

• EI0, Gij0, and νij0 are the elastic modulus, shear modulus, and Poisson’s ratio, respectively for the
undamaged material.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-51
© 2023 Siemens
 4. Element support

• λ is a parameter whose value is either zero or one that controls whether or not damage is linked to
out-of-plane stresses.

Note:
‹x›+ means use the value for x when x > 0, and use x = 0 when x ≤ 0. Similarly, ‹x›- means use the
value for x when x < 0, and use x = 0 when x ≥ 0.

The unidirectional ply model uses thermodynamic forces to predict ply damage. Thermodynamic forces
are derived from the strain energy density as indicated in the following equation.

Equation 4-2.

The criteria that the unidirectional ply model uses to predict ply damage are indicated in the following
equation.

4-52 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

Equation 4-3.

where:

• dijs are the static damage values.

• Y11lim+ and Y11lim- are energy threshold values in tension and compression, respectively.

• Y120 is the energy threshold for shear damage d12.

• Y12C is the critical value of energy for shear damage d12.

• b3 is the coupling coefficient between damage variables.

In Equation 4-3, Ymax is defined from Equation 4-4.

Equation 4-4.

where t is the time at the end of the current time step.

In Equation 4-4, Y(t) is referred to as the equivalent thermodynamic force, and it is given by Equation
4-5.

Equation 4-5.

where b2 is also a coupling coefficient.

In Equation 4-3, Y12F and Y22F are referred to as the thermodynamic forces in fragile behavior. They are
defined by Equation 4-6.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-53
© 2023 Siemens
 4. Element support

Equation 4-6.

where η is the transition thickness of the ply, h is the thickness of the ply, and Y12S and Y22S are the
transverse fissuration thresholds.

Note:
sup (supremum) evaluates to the least upper bound of the arguments.

UD model - Time delay effects

The unidirectional ply model can optionally include time delay effects. Time delay effects smooth the
occurrence of damage. Equation 4-7 shows how the rate of damage accumulation is calculated.

Equation 4-7.

where τc is a time constant, ac is a parameter for delay, and dmax is the maximum allowable value of
damage.

dijS are the static damage values calculated from Equation 4-3.

UD model - Nonlinear function of shear damage versus thermodynamic force

The shear damage (d12) for the UD ply failure model supports a nonlinear function of thermodynamic
force Y.

4-54 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

Equation 4-8.

You can specify the nonlinear function with the TABLEM5 bulk entry, which is referenced by the TID field
on the MATDMG bulk entry. The TABLEM5 specifies the function d12=f(sqrt(Y)), where d12 is the y data,
and sqrt(Y) is the x data.

UD model - Coupling with plasticity

The unidirectional ply model includes coupling with plasticity. The plasticity calculations use the
effective stress definitions in Equation 4-9.

Equation 4-9.

The software uses the effective stresses in Equation 4-10 to predict when yielding occurs.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-55
© 2023 Siemens
 4. Element support

Equation 4-10.

where:

• a is the coupling coefficient.

• p is the cumulative plastic strain.

• R0 is the initial plasticity threshold.

• R(p) is the yield function.

The form of the yield function that the software uses is given by Equation 4-11.

Equation 4-11.

where K and γ are experimentally-tested material constants.

The software calculates the rate of plastic strain accumulation from Equation 4-12.

4-56 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

Equation 4-12.

where:

Equation 4-13.

UD model - Nonlinear traction and compression

The unidirectional ply model can optionally include a nonlinear elastic modulus in the fiber direction as
indicated in Equation 4-14.

Equation 4-14.

where ζ+ and ζ- are nonlinearity coefficients in tension and compression, respectively. You can control if
the nonlinearity coefficients are applied to the strain or the stress using the PLYUNI field on the MATDMG
bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-57
© 2023 Siemens
 4. Element support

UD model - Specifying material properties and parameters

The following table shows where you specify the various material properties and parameters used in the
UD model.

Material property or parameter Bulk entry (field name)

Ei0, 0,
Gij νij 0 MAT11
λ MATDMG (PE field)
Y11lim+ MATDMG (Y11LIMT field)
Y11 lim- MATDMG (Y11LIMC field)
Y120 MATDMG (Y012 field)
Y12C MATDMG (YC12 field)
b2 MATDMG (B2 field)
b3 MATDMG (B3 field)
η MATDMG (HBAR field)
h PCOMPS (TRi field)
Y12S MATDMG (YS12 field)
Y22S MATDMG (YS22 field)
τc MATDMG (TAU field)
ac MATDMG (ADEL field)
dmax MATDMG (DMAX field)
a MATDMG (A field)
R0 MATDMG (LITK field)
K MATDMG (BIGK field)
γ MATDMG (EXPN field)
ζ+ MATDMG (KSIT field)
ζ- MATDMG (KSIC field)
Controls if nonlinearity coefficients are applied MATDMG (PLYUNI field)
to strain or stress.
d12=f(sqrt(Y)) (optional) TABLEM5 is referenced by the TID field on MATDMG

Enhanced unidirectional (EUD) ply model

You can select the EUD model by entering EUD in the PPFMOD field on the MATDMG entry. Relative
to the UD model, the EUD model allows for additional damage caused by fiber-matrix debonding and
transverse cracking. The MATDMG bulk entry includes an input format specifically for the EUD definition.

EUD model - Elastic strain and thermodynamic forces

4-58 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

The constitutive model for the EUD model is:

with,

and,

where,

df is the damage variable linked to fibers direction,

d, d', and d23 are the three damage variables linked to diffuse damage, with,

are the three damage variables linked to transverse cracking,

the superscript 0 is related to the undamaged material, and

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-59
© 2023 Siemens
 4. Element support

[x+] is 1 when x is positive, and 0 otherwise.

EUD model - Thermodynamic forces

Thermodynamic forces are obtained by taking the derivative of the potential with respect to the damage
variables, taking the mean value over the ply thickness:

where,

is the mean value of x over the ply thickness,

is x when x is positive, and 0 otherwise,

h is the ply thickness, and

hc is a critical thickness defining the threshold between thin and thick ply behavior.

For external plies, min(h,hc) should be replaced by min(2h,hc).

EUD model - Evolution laws of the damage variable linked to fibers

First, a "static" damage w is computed. Its evolution is a function of the thermodynamic forces described
above:

4-60 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

where,

are the breaking thresholds in traction and compression,

Yc is a critical thermodynamic force,

k is a coupling coefficient.

If a delay effect is considered, the damage becomes,

where,

τc and ac,

dmax is the maximum fibers damage.

In option, w can be limited to dmax before taking into account the time delay effect.

EUD model - Evolution laws of damage variables linked to diffuse damage

First, a "static" damage w is computed. Its evolution is a function of the thermodynamic forces described
above,

Y0 is a fiber/matrix debonding threshold,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-61
© 2023 Siemens
 4. Element support

YC is a critical thermodynamic force,

b2 is a coupling coefficient.

If a delay effect is considered, the damages become,

where,

τc and ac are parameters of the delay law,

b3 is a coupling coefficient between the damage variables,

ds is the maximum diffuse damage.

In option, w can be limited to ds before taking into account the time delay effect.

Diffuse damages are not influenced by the damage linked to the fibers.

EUD model - Evolution laws of damage variables linked to transverse cracking

We have , where ρ is the crack density.

The rupture envelope is written,

where,

τc and ac are parameters of the delay law,

b3 is a coupling coefficient between the damage variables,

ρs is the maximum crack damage.

EUD model and plasticity

4-62 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Progressive failure analysis in solid composites

We define the effective stresses,

A yield criteria is defined as a function of the effective stresses,

where,

R(p)=Kpɣ is the yield function,

p is the accumulated plastic strain,

R0 is the initial plasticity threshold,

a is a coupling coefficient,

K and ɣ are material parameters given by experimental testing.

The plastic strain velocities are given by,

EUD model - Specifying material properties and parameters

The following table shows where you specify the various material properties and parameters used in the
EUD model.

Material property or parameter Bulk entry (field name)

Ei0, Gij0, νij0 MAT11
b2 MATDMG (B2 field)
b3 MATDMG (B3 field)
h PCOMPS (TRi field)
τc MATDMG (TAU field)
ac MATDMG (ADEL field)
dmax MATDMG (DMAX field)

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-63
© 2023 Siemens
 4. Element support

Material property or parameter Bulk entry (field name)

a MATDMG (A field)
R0 MATDMG (LITK field)
Κ MATDMG (BIGK field)
Y MATDMG (EXPN field)
ζ+ MATDMG (KSIT field)
ζ- MATDMG (KSIC field)
YdfT MATDMG (Y11LIMT field)
YdfC MATDMG (Y11LIMC field)
Y0 MATDMG (Y012 field)
Yc MATDMG (YC12 field)
K MATDMG (K field)
ds MATDMG (DS field)
GIC MATDMG (GIC field)
GII C MATDMG (GIIC field)
GIIIC MATDMG (GIIIC field)
ρs MATDMG (RO1 field)
min(h,hc) MATDMG (HBAR field)
ɑ MATDMG (ALPHA field)
Controls if delay effect is used MATDMG (USER field)
before applying the maximum
damage.

4-64 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Material and load scaling for 2D/3D models

4.16 SOL 401 - Material and load scaling for 2D/3D models
Analysis of rotating machinery such as turbine engines is typically modeled in 2D with a mix of
axisymmetric and plane stress elements. For regions in which more detail is required, a sector of 3D
solid elements can be used that includes cyclic symmetry boundary conditions. These 3D cyclic sectors
do not interact with each other and are typically connected to the axisymmetric mesh via MPCs.

SOL 401 supports the combination of 2D axisymmetric elements and 3D cyclic sectors in the statics,
dynamics, and preload subcases, but not in the cyclic modes or Fourier modes subcases.

Note that if your model includes a combination of 2D axisymmetric elements and 3D cyclic sectors, and
you have included either the cyclic modes or Fourier modes subcases, the solution will end with a fatal
error.

The model below includes both 2D elements, and a sector of 3D solid elements.

The axisymmetric element formulation represents the mass and stiffness of a fully revolved (2π)
geometry, but the cyclic sector only represents a 1/N section of the geometry. As a result, the mass,
stiffness, and loading are not consistent between these two portions of the model.

When the software determines that a combination of 2D axisymmetric elements and 3D cyclic sectors
exists, it automatically scales the appropriate material properties and loads on the cyclic sectors.

To request the automatic scaling, you list the elements in a 3D cyclic sector on a GROUP bulk entry. Then
you enter the GROUP identification number in the GROUPID field on the CYCSET bulk entry.

The automatic scaling is supported in the statics, dynamics, and preload subcases.

Currently, you can include the 3D solid elements CHEXA, CTETRA, CPENTA, CPYRAM, and the mass
element CONMi in the GROUP for the automatic scaling.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-65
© 2023 Siemens
 4. Element support

For the elements that you list in the GROUP, the software scales their material properties, and the
forces and moments applied to those elements by the value of NSEG, which is the number of cyclic
sectors defined on the CYCSET entry. The software scales the following loads: FORCE, FORCE1, FORCE2,
MOMENT, MOMENT1, MOMENT2, PLOAD, PLOAD4, FORCDST, PLOADFP, and BOLTFRC.

Note the following rules for loads defined with the PLOADFP and BOLTFRC entries. The software will
issue a fatal error if these are violated.

● For the fluid penetration pressure load defined with the PLOADFP entry, all of the elements in a region
must either be in a cyclic sector or not in a cyclic sector. The software scales the pressure applied to
these elements when they are all in a cyclic sector.
● Similarily, for bolt preloads of ETYPE= 2 and 3, all of the elements representing the bolts referenced
by a BOLTFRC entry must be in a cyclic sector or not in a cyclic sector. The software scales the preload
force when all of the elements are in a cyclic sector.

If you are modeling multiple cyclic sectors (stages), each with a different total number of sectors (NSEG),
you must define a separate CYCSET entry for each stage. You use the STAGE field on each CYCSET entry
to define a unique identification number for each stage. You use the CYCADD bulk entry to combine the
multiple CYCSET entries into a single cyclic symmetry set.

The model below includes multiple stages, each with a different total number of sectors.

You can disable the automatic scaling by defining the parameter setting CY3DSCL=0 on the NLCNTLG
bulk entry. By default, CY3DSCL=1 and the automatic scaling occurs.

The following information message is printed to the .f06 file for each CYCSET ID when the automatic
scaling occurs:

4-66 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Material and load scaling for 2D/3D models

If you requested the Grid Point Weight Generator output (PARAM, GRDPNT), the initial Grid Point Weight
Generator table contains the unscaled mass. When cyclic scaling occurs, a second Grid Point Weight
Generator table using the scaled sector mass is printed:

Additional information:

• All cyclic sectors having the same CYCSET STAGE ID must also have the same NSEG value.

• There should be no interaction (connections, MPCs, contact, glue, etc.) between cyclic sectors with
different STAGE IDs.

• There is no connectivity check for elements in the GROUP referenced on the CYCSET entry. Properties
for all elements in the group will be scaled.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-67
© 2023 Siemens
 4. Element support

• The CYCSET entry also defines the automatic cyclic symmetry coupling boundary conditions. See
Cyclic symmetric boundary condition.

4-68 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - 2D Fourier axisymmetric and 2D/3D coupling

4.17 SOL 402 - 2D Fourier axisymmetric and 2D/3D coupling

Fourier axisymmetric element

Fourier axisymmetric elements are available with SOL 402 to improve accuracy and to allow for non-
axisymmetric loading. The degrees-of-freedom (DOF) for the Fourier elements is represented as a
series, where each term in the series represents additional harmonic behavior. The r, z, and θ DOF
are represented by the following.

The software solves the displacement results of each requested harmonic number i. The 0th harmonic
represents the behavior of a pure axisymmetric element. Each harmonic > 0 then adds additional
behavior.

The following 2D to 3D coupling options can result in non-axisymmetric loading.

• You can use the FOU3 coupling element to connect a node with six DOF to a node used by the Fourier
axisymmetric element. See FOU3 coupling element.

• You can use the 2D-3D coupling to connect a Fourier axisymmetric mesh edge to a 3D solid element
mesh face. The 3D solid element mesh can represent a cyclic symmetry portion of the structure, or a
full 360-degree representation. See 2D-3D coupling.

You model the Fourier elements using the existing axisymmetric elements CQUADX4, CQUADX8,
CTRAX3 and CTRAX6. The grid points on these elements must all lie in either the XZ plane, or all in
the XY plane of the basic coordinate system. The software automatically determines the orientation.

You can directly connect plane stress elements to the Fourier axisymmetric elements for use in a statics
subcase, but this connection is currently not supported in the modes subcase types (ANALYSIS=MODES,
FOURIER, or CYCLIC).

You use the FHAR case control command to request the harmonic numbers for the Fourier elements.
The FHAR references the ID of a SET case control command in which the SET command lists the
harmonic numbers.

When the FHAR command is defined, the software automatically considers all axisymmetric elements
as Fourier elements. The FHAR command must be defined above the subcases (globally). As a result, it
applies to all subcases. The FHAR command is supported in the "nonlinear subcases" (statics, preload,
and dynamics subcases), and in the "modes subcases" (normal modes, cyclic modes, and complex
modes subcases).

You use the FHAC case control command in specific subcases to remove a subset of the harmonic
numbers requested with the FHAR command. Two FHAC sets are supported; one for the nonlinear

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-69
© 2023 Siemens
 4. Element support

subcases (statics, preload, and dynamics subcases), and a second for the modes subcases (normal
modes, cyclic modes, and complex modes subcases).

Every nonlinear subcase must request the same harmonic numbers. Similarly, every modes subcase
must request the same harmonic numbers. As a result, the FHAC command for "nonlinear subcases"
must be included in every statics, preload, and dynamics subcase, and, the FHAC command for modes
subcases must be included in every normal modes, cyclic modes, and complex modes subcase.

The following case control example demonstrates the FHAR and FHAC requests.

....
CEND
$ CASE CONTROL
FHAR=5 (Global definition requesting harmonics 1-10)
SET 5 = 1 THRU 10
SET 7 = 4,5
SET 8 = 9,10
SUBCASE 1
ANALYSIS=PRELOAD
FHAC=7 (Harmonics 4 and 5 removed for nonlinear subcases)
SUBCASE 2
ANALYSIS=STATICS
FHAC=7 (Harmonics 4 and 5 removed for nonlinear subcases)
SUBCASE 3
ANALYSIS=MODES
FHAC=8 (Harmonics 9 and 10 removed for modes subcases)
SUBCASE 4
ANALYSIS=CEID (complex modes)
FHAC=8 (Harmonics 9 and 10 removed for modes subcases)
....

Note: When your model includes a bolt preload and/or a contact condition on axisymmetric elements,
only the 0th harmonic is supported with the FHAR command. If you request harmonics higher than 0,
the solution will end with a fatal error.

Coupling and negative harmonics

You use the parameter FHMETH on the NLCNTLG bulk entry to select whether the harmonics are coupled
or uncoupled, and whether the negative harmonics are computed. The table below summarizes the
FHMETH options.

FHMETH option Description

FHMETH = 1 The zero, positive, and negative harmonics are computed and are fully coupled.
FHMETH = 2 The zero, positive, and negative harmonics are computed and are uncoupled.
FHMETH = 3 The zero, positive, and negative harmonics are computed, and positive and
negative pairs are coupled.

4-70 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - 2D Fourier axisymmetric and 2D/3D coupling

FHMETH option Description

FHMETH = 11 The zero and positive harmonics are computed and are coupled.
FHMETH = 12 The zero and positive harmonics are computed and are uncoupled.
FHMETH = 13 Same as FHMETH=12.

When nonlinear conditions are present (material nonlinear, large displacements, large strain, contact),
coupled harmonics become more important to achieve convergence. Some nonlinear problems can still
converge with the uncoupled option, but an increase in iterations may be required. The results of a
converged coupled analysis or a converged uncoupled analysis will be the same.

Options 1 and 2 are the more common choices. The fully coupled option is much more computational
than the uncoupled option. For linear problems, the harmonics are uncoupled, and you can reliably use
the uncoupled option to improve the performance.

If you understand your loading and the resulting deformation, you can consider removing the negative
harmonics to reduce the model size with the options 11, 12, and 13. These options can also be used in a
normal modes subcase to avoid the duplicate modes.

Note that you only request the positive harmonics with the FHAR and FHAC commands, and the
software automatically computes the negative harmonics based on the FHMETH option. For example,
if harmonics FHAR=0, 1, 2 are requested, for FHMETH=1, 2, or 3, the harmonics -2, -1, 0, 1, 2 are
computed, and for FHMETH=11, 12, or 13, the harmonics 0, 1, 2 are computed.

Cyclic symmetry subcase

When you combine Fourier axisymmetric elements in a cyclic symmetry subcase, you use the
HARMONICS case control command to request the harmonics for the 3D-solid element cyclic symmetry
portion of the model, and the FHAR and FHAC commands to request the harmonic numbers for the
Fourier elements. See "Cyclic symmetric" in the Multi-Step Nonlinear User’s Guide.

The existing Fourier subcase with axisymmetric elements and the Fourier axisymmetric elements used in
a modal subcase are mathematically the same analysis, and will give similar results.

When the 0th harmonic is not requested for the cyclic symmetry (HARMONIC≠0), the 0th harmonic
is not computed for the Fourier elements by default. You must explicitly request it with the FHAR
command for it to be computed. When the 0th harmonic is requested for the cyclic symmetry
(HARMONIC=0), the 0th harmonic is computed for the Fourier elements by default, even if you do
not request it with the FHAR command. You can omit the 0th harmonic with the FHAC command.

For the statics, dynamics, preload, and modes subcases, the 0th harmonic is still computed for the
Fourier elements by default, even if you do not request it with the FHAR command. You can omit the 0th
harmonic with the FHAC command.

FOU3 coupling element

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-71
© 2023 Siemens
 4. Element support

You can use the FOU3 bulk entry to connect a grid point with six DOF (GA) to a grid point used
in the connectivity of a Fourier axisymmetric element (GB). You can include the grid point GA in
the connectivity of other elements, or you can use GA to apply forces or moments by leaving it
unconnected. The FOU3 element is a special type of MPC condition that distributes the forces and
moments between the 3D portion to the Fourier elements with harmonic dependent DOF.

You can include the grid point GA in the connectivity of other elements, or you can use GA to apply
forces or moments by leaving it unconnected. The FOU3 element is a special type of MPC condition
that distributes the forces and moments between the 3D portion to the Fourier elements with harmonic
dependent DOF.

You use the FOU3 bulk entry to define the element. The FOU3 entry includes the identification number,
grid point in 3D (GA), Fourier element grid point (GB), and the OPT field. The OPT field defines the DOF
to couple.

OPT field on the FOU3 entry (Integer="1", "2", or "5"; No default)

• OPT=1: With this option, GA and GB must be coincident, and the translational DOF are coupled
(R,θ,Z).

• OPT=2: With this option, GA must be on the symmetry axis, and GA and GB must have the same
axial coordinate. A rigid connection is created between the translational DOF on the 3D node and the
Fourier node. This option links the 3D node at r=0.0, to a rigid disk, where the radius of the disk is
determined by the coordinate of the Fourier node.

• OPT=5: With this option, GA must be on the symmetry axis, and GA and GB must have the same
axial coordinate. All six DOF of the 3D grid point are coupled (translational and rotational DOF). This
option links the 3D node at r=0.0, to the mean displacement of a disk, where the radius of the disk is
determined by the coordinate of the Fourier node. The Fourier disk is not rigid and is free to deform.

2D-3D coupling

You can request the 2D-3D coupling to connect a Fourier axisymmetric mesh edge to a 3D solid element
mesh face. The 3D solid element mesh can represent a cyclic symmetry portion of the structure, or a full
360-degree representation.

You request the coupling with the FMH3D bulk entry. You create an element edge region on the Fourier
mesh and a face region on the 3D mesh, and then reference the regions in the GREDGE and GRFACE
fields, respectively. Simcenter Nastran creates virtual grid points during the solution along a face that is
parallel to the 3D face region. The virtual grid points are copies of the grid points in the 2D edge region.
It glues the virtual grid points to the grid points on the 3D face and connects the virtual grid points to
the grid points on the 2D edge using constraint conditions similar to the FOU3 elements.

By default, the number and location of the virtual grid points are controlled by the software, but you can
optionally control the number of virtual grid points and their location with the following fields on the
FMH3D entry.

4-72 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - 2D Fourier axisymmetric and 2D/3D coupling

Field name Field description

ANGLEI Angle in the circumferential direction beginning at the 2D edge region, and
ending at a location near the beginning edge of the 3D solid face region.
See the image above. You must define both ANGLEI and ANGLED, or neither.
(Real>0.0; Default=Auto computed by software.)
ANGLED Angle in the circumferential direction beginning at the location determined
by ANGLEI, then measured to a location near the ending edge of the 3D
solid face region. See the image above. You must define both ANGLEI and
ANGLED, or neither. (Real>0.0; Default=Auto computed by software.)
N or DIST For the grid points referenced by the 2D region, N is the number of evenly
distributed copies of virtual grid points in the arc defined by ANGLED. N and
DIST cannot both be defined. A fatal error will occur if both are defined.
(Integer>0; Default=blank which selects the fully automatic coupling unless
DIST is defined). See Coupling options below.
For the grid points referenced by the 2D region, DIST is the distance between
the copies of virtual grid points in the arc defined by ANGLED. The software
uses DIST to compute a number of grid points N such that ALPHAD*RADIUS /
(N+1) < DIST. N and DIST cannot both be defined. A fatal error will occur if
both are defined. (Real>0.0; Default=blank which selects the fully automatic
coupling unless N is defined). See Coupling options below.
SDISN Normal search distance. The normal distance from a virtual node to the solid
element face must be less than SDISN for the software to create a glue
condition at that location. (Real>0.0; Default = 0.001*DIAG, where DIAG is
the software computed diagonal of the mesh region selected in the GRFACE
field.)
SDIST Tangential search distance. For virtual grid points that are beyond the
projected area of the 3D solid face region, the tangential distance from
a virtual node to the solid element face must be less than SDIST for the
software to create a glue condition at that location. (Real>0.0; Default =
0.001*DIAG, where DIAG is the software computed diagonal of the mesh
region selected in the GRFACE field.)

Coupling methods

• Fully automatic method

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-73
© 2023 Siemens
 4. Element support

You can select the fully automatic method by leaving the N, DIST, ANGLEI, and ANGLED fields blank.
The software will automatically determine the number and location of the virtual grid points and
ignores the SDISN and SDIST fields.

The software automatically does the following when you use the fully automatic method:

• Positions the virtual grid points in optimum locations.

• Accounts for skew angles (when the 2D axisymmetric edge is not parallel with the 3D mesh edges).
• Avoids coupling redundancies on the same 3D face.
• Avoids coupling redundancies with the dependent degrees-of-freedom on a cyclic symmetry
boundary condition.
• Accounts for different mesh sizes on the 3D face and the 2D axisymmetric mesh.
• Accounts for elements that include midside grid points (higher order elements).

• Manual method

You can select the manual method by defining either the N or the DIST field. You can optionally define
the ANGLEI, ANGLED, SDISN and SDIST fields when using the manual method, or leave them blank
and the software will use their default values.

The software does the following when you use the manual method:

• To prevent over-constraining of the elements due to the creation of too many virtual grid points, the
software associates each virtual grid point with the closest possible 3D grid point.

• The software avoids coupling redundancies, particularly, the dependent degrees-of-freedom on a

cyclic symmetry boundary condition.

Contact and bolt preload on 2D and 3D elements

Contact and bolt preload are supported in models that include only 2D elements, only 3D elements, or a
combination of 2D and 3D elements.

• Contact regions can be defined on 2D element edges and on 3D element faces.

The 2D elements include the axisymmetric, plane stress, and plane strain elements. The 3D elements
include the CHEXA, CPENTA, CPYRAM, and CTETRA elements.

• A bolt can be modeled with 2D or 3D elements.

The 2D elements include the axisymmetric and plane stress elements. The 3D elements include the
CHEXA, CPENTA, and CTETRA elements.

For example, in a multistage turbine engine model, the blades can be meshed with 3D solid or
plane stress elements, and the disks can be meshed with 2D axisymmetric elements. You can define
an axisymmetric bolt parallel with the axisymmetric axis of rotation to compress all of the engine
stages together. The bolt preload defined on the bolt results in the compressive axial loading. You can

4-74 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - 2D Fourier axisymmetric and 2D/3D coupling

also define edge-to-edge contact conditions between the different engine stages modeled with the
axisymmetric elements.

Note:
When your model includes a bolt preload and/or a contact condition on axisymmetric elements,
only the 0th harmonic is supported with the FHAR command. If you request harmonics higher
than 0, the solution will end with a fatal error.

When applying the preload, the software cuts the bolt perpendicular to its axis. It evenly distributes
the opposing axial bolt force to each side of the cut, and then it solves a solution to determine
the axial displacement of each side of the cut. The software then maintains the grid pairs in their
relative deformed state in the subsequent subcases. Axial force is the only bolt force component for a
axisymmetric bolt.

To maintain the grid pairs in their relative deformed state at the cut, the software applies an average
axial displacement condition on each side of the cut. When post processing results computed from a
modes subcase, the bolt axis may appear unconnected at the cut. This is normal and is a result of the
average displacement condition enforced at the cut.

Fourier element output

The Fourier axisymmetric element DOF output is dependent on a summation of the harmonics at
specific values of theta. You can use the FHPOST and FHPNST parameters to request the theta locations
for output. In addition, if you include other 3D elements in the model, the FHPOST parameter also
controls if output occurs for this portion of the model.

• FHPOST=1 Requests 3D harmonic results for the Fourier axisymmetric elements at incremental angle
locations around the complete 360-degree circumference. You use the FHPNST parameter to define
the angle increments per 90 degrees. In addition, 2D results on the modeled axisymmetric geometry
and 3D results on the modeled solid element geometry are also output.

• FHPOST=4 Requests 2D results on the modeled axisymmetric geometry.

• FHPOST=5 (Default) Requests 2D results on the modeled axisymmetric geometry and 3D results on
the modeled solid element geometry.

General 2D and 3D output

Fourier element output is written to *.des and *.fac Samcef output files, and not to the .op2 file.
Results on the axisymmetric plane include "2D" in their file name, and results for solid elements and
the 360 degree Fourier axisymmetric element results include "3D" in their file name. In addition, results
from statics, dynamics, and preload subcases include "_me." in their filename, and results from modes,
complex modes, and cyclic modes subcases include "_dy." in their filename. You can import these results
files into Simcenter 3D post processing to view the output.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-75
© 2023 Siemens
 4. Element support

4.18 Chocking elements (SOL 401)

Chocking element is a special type of axisymmetric element that is used to model regions in an
axisymmetric analysis that can carry a compressive hoop stress, but cannot carry a tensile hoop stress.
You use chocking elements to model regions where the axisymmetric geometry is violated by regularly-
spaced features like holes or keyways.

Chocking elements behave like axisymmetric elements when a compressive hoop stress is present, and
behave like plane stress elements otherwise.

An example is the shrouding around the periphery of turbine blades in an aircraft engine.

A generic turbine assembly is shown in the figure. You can see that the shroud is constructed from
discrete segments that are attached to each turbine blade. A small gap exists between each segment. If
the combination of mechanical and thermal loads is such that these gaps close, the shroud can sustain
a compressive hoop stress. To account for this behavior in an axisymmetric model, you can mesh the
shroud cross section with chocking elements.

Tip:
As a rule, only use chocking elements in combination with axisymmetric elements. A mesh
comprised solely of chocking elements may lead to singularities, convergence issues, and
erroneous results.

Gap status

An expression for the gap size at the end of a time step for each Gauss point is obtained as follows:

1. In the deformed configuration, the circumferential distance occupied by the chocking element is
given by

2πr – Ng

4-76 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Chocking elements (SOL 401)

where N is the number of gaps, g is the gap size at the end of the iteration and r is the radius at the
end of the iteration.

2. Because εθ is the hoop strain in engineering measure, and engineering strains are based on
undeformed lengths, the circumferential distance occupied by the chocking element in the
deformed configuration is also given by

(1 + εθ) (2πr0 – Ng0)

where r0 is the initial radius and g0 is the initial gap size.

3. Equating the above terms for the circumferential distance occupied by the chocking element in the
deformed configuration and solving for the gap size at the end of the iteration yields

g = (1 / N) [2πr – (1 + εθ) (2πr0 – Ng0)]

Using the expression above for the gap size, the software calculates the gap status at each Gauss point.

Chocked status

At any Gauss point location where g ≤ 0, the location is considered chocked, and the contribution to
the elemental stiffness matrix from that Gauss point is based on the axisymmetric formulation of the
chocking element.

Unchocked status

At any Gauss point location where g > 0, the location is considered unchocked, and the contribution
to the elemental stiffness matrix from that Gauss point is based on the axisymmetric formulation of
the chocking element with the Eθ, νθr, and νθz elastic constants reduced by a factor of 1 x 106. Doing
so causes the element stiffness to be essentially identical to a plane stress formulation with σθ as the
out-of-plane normal stress.

Large displacement on (LGDISP=1)

When large displacements are enabled, the software computes an updated gap status at the end of each
time step. The resulting stiffness can then change from one time step to the next based on the changing
gap status and the deformed state of the model.

For applications of chocking elements like the turbine shroud, the mesh of chocking elements is
connected to axisymmetric elements. Because the stiffness in the radial direction for such a model is
relatively large, even when a positive gap exists, the incremental radial displacements that the software
calculates during the iterative solution are relatively small and the solution is able to converge.

However, if the model is extremely compliant in the radial direction, the radial coordinates that the
software calculates to reformulate the stiffness may be negative, which is physically impossible. When
the software detects a negative radial coordinate, it does not reformulate the stiffness matrix and it uses
the initial circumferential distance for the deformed configuration at the next iteration.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-77
© 2023 Siemens
 4. Element support

To enable large displacements, specify PARAM,LGDISP,1.

Large displacement off (LGDISP=-1)

When large displacements are not enabled, you can use the parameter CHOCK on the NLCNTLG bulk
entry to control the frequency of gap status updates.

When CHOCK=NO, a solution occurs for the first time step to determine the gap status at each Gauss
point. The software uses this chocked or unchocked status to recompute the stiffness. The resulting
stiffness is then used for the rest of the solution, and the gap status is not reevaluated.

When CHOCK=YES (default), the software computes an updated gap status at the end of every time
step. The software uses this updated chocked or unchocked status to recompute the stiffness. The
resulting stiffness can change from one time step to the next based on the changing gap status, but not
on the deformed state of the model.

The CHOCK=YES option allows you to update the stiffness based on the chocking status, but without the
computation expense of running a large displacement analysis. This option is only appropriate when the
changing geometry and stiffness updates that occur with LGDISP=1 are not significant.

PARAM,LGDISP,-1 is the default value for the LGDISP parameter.

Note:
The axisymmetric formulation of chocking elements sustains tensile, as well as compressive hoop
stress. Because the gap distance does not update when using the CHOCK=NO option, overly stiff
results can occur for loadings that tend to increase the gap distance.

Surface tractions on chocking elements

Use the PLOADX1 bulk entry to apply surface tractions to the edges of chocking elements. When the
software calculates the equivalent grid point forces from the surface traction data on a PLOADX1 bulk
entry, it accounts for the presence of gaps.

For example, suppose you use a PLOADX1 bulk entry to apply a pressure along the edge of a chocking
element. If the edge is directed in the axial direction, the total force applied to the chocking element
over 2π radians is:

p (2πr – Ng) L

where p is the pressure, r is the radial coordinate of the edge, N is the number of gaps, g is the gap size,
and L is the length of the edge.

Chocking element types

Four elements support the chocking capability. They are:

4-78 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Chocking elements (SOL 401)

• CCHOCK3 – A triangular chocking element

• CCHOCK4 – A quadrilateral chocking element

• CCHOCK6 – A triangular chocking element with midside nodes

• CCHOCK8 – A quadrilateral chocking element with midside nodes

All four chocking elements must reference the PCHOCK property bulk entry. On the PCHOCK bulk entry,
you specify the material property for the chocking element and the number of gaps. You can specify
the initial gap thickness on either the PCHOCK bulk entry or on the chocking element bulk entries that
reference the PCHOCK bulk entry. If the initial gap thickness is specified on both, the specification on the
chocking element bulk entry takes precedence. If the gap is of uniform thickness, use the GAPT field on
the PCHOCK bulk entry to specify the gap thickness. If the gap thickness varies through the cross section,
use the GAPi fields on the chocking element bulk entries, or use a combination of GAPT specifications
and GAPi overrides, to specify the gap thickness.

To request gap results output, use the CKGAP case control command.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-79
© 2023 Siemens
 4. Element support

4.19 Cohesive elements

In SOLs 401 and 402, you can use cohesive elements to model adhesively bonded interfaces. The
advantages of cohesive elements over traditional glue connections in Simcenter Nastran are that with
cohesive elements, you can account for:

• Compliance in the connection.

• Damage in the material.

You can define cohesive elements with the CHEXCZ and CPENTCZ elements. You can define these
elements as occupying a solid volume or a planar area. To define the element geometry such that it
occupies a planar area, define coincident grid points on each edge that connects the top and bottom
faces.

For example, to define the CPENTCZ element as a planar area, G1, G10, and G4 must have the same
coordinates. G1 is also included in the connectivity of an element that is part of the mesh on one side
of the interface and G4 is also included in the connectivity of an element that is part of the mesh on the
other side of the interface. Mid-side grid points on edges that connect the top and bottom faces like G10
are exclusive to the cohesive element mesh.

CHEXCZ and CPENTCZ elements must reference a PSOLCZ property. With the PSOLCZ bulk entry, you
reference the corresponding MAT1, MAT11, or MATCZ bulk entry, the material coordinate system, and,
under certain circumstances, the thickness of the element.

There are three stiffness values associated with cohesive elements: K01 and K02 are the transverse shear
stiffness; K03S is the out-of-plane normal stiffness. You specify these stiffness values as follows:

• If the PSOLCZ bulk entry references a MAT1 bulk entry, Simcenter Nastran calculates the stiffness of
the cohesive elements to be K01 = G / THICK, K02 = G / THICK, and K03S = E / THICK, where THICK is
the value you specify in the THICK field of the PSOLCZ bulk entry.

• If the PSOLCZ bulk entry references a MAT11 bulk entry, Simcenter Nastran calculates the stiffness of
the cohesive elements to be K01 = G13 / THICK, K02 = G23 / THICK, and K03S = E3 / THICK, where
THICK is the value you specify in the THICK field of the PSOLCZ bulk entry.

• If the PSOLCZ bulk entry references a MATCZ bulk entry, you specify the stiffness directly in the K01,
K02, and K03S fields of the MATCZ bulk entry. For this case, the THICK field of the PSOLCZ bulk entry is
ignored.

In all three cases, Simcenter Nastran does not use the physical thickness of cohesive elements as defined
by the geometric coordinates of the grids to determine the stiffness of the cohesive element.

For SOL 401, you must define PARAM,MATNL,1 to activate damage estimation. SOL 402 does not have
this requirement.

4-80 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cohesive elements

You use the MATCZ bulk entry when you want to obtain material damage estimates. On the MATCZ bulk
entry, specify the damage estimation model. You can choose from the following options:

• In the polynomial model (the default), the Mode I, Mode II, and Mode III damage variables are taken
to be equal, and the damage is modeled as a function of thermodynamic force. An evolution equation
is used to estimate the damage.

• In the bi-triangular model, for Mode I, Mode II, and Mode III, the relationship between stress and
displacement is modeled as bilinear. δ

• In the exponential model, for Mode I, Mode II, and Mode III, the relationship between stress and
displacement is modeled as exponential.

Simcenter Nastran also does not use the physical thickness of cohesive elements as defined by the
geometric coordinates of the grids in damage calculations.

The double cantilever beam (DCB) test is a common method to determine the fracture properties. For
example, data from the DCB test is used to represent the first mode of the bi-triangular model. The
model represents a bilinear relationship between stress and displacement as shown below.

where,

Y0 is the area under the first (gray) triangle, and defines the Y0S field on MATCZ,

G is the total area under both triangles (gray+blue), and defines the GIC field (mode 1) on MATCZ,

Ki is the slope from 0.0 to σmax, and defines the K03S field on MATCZ.

Results for cohesive elements are calculated at the corner grid points. The results include:

• Damage values

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-81
© 2023 Siemens
 4. Element support

• Surface tractions

• Relative displacements

To request result output for cohesive elements, use the CZRESULTS case control command. With the
CZRESULTS case control command, you can request the damage for all three modes, components of the
surface tractions, and components of the relative displacements. Relative displacement is defined as the
displacement of the top surface of the cohesive element relative to the bottom surface of the cohesive
element.

Traction and relative displacement are both output into three components. The components are output
in the material coordinate system relative to the deformed state. Tractions have units of force per unit
area. Relative deformation has units of length.

4-82 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Crack simulation (SOL 401)

4.20 Crack simulation (SOL 401)

You can compute and output the j-integral for a given crack geometry. This capability is only supported
for SOL 401. The j-integral output can be used by third-party software like Zencrack to perform a fracture
mechanics analysis.

• You can use the JINTEG case control command to control the computation and output of the
j-integral. With the JINTEG case control command, you can direct the j-integral output to either .op2
or .f06 files.

For additional information, see the JINTEG case control command.

• The creation of the CRAKTP bulk entry. You can use the CRAKTP bulk entry to specify information
related to the crack tip.

For additional information, see the CRAKTP bulk entry in the Simcenter Nastran Quick Reference
Guide.

• The creation of the VCEV bulk entry. You can use the VCEV bulk entry to define virtual crack tip
extension vectors.

For additional information, see the VCEV bulk entry in the Simcenter Nastran Quick Reference Guide.

• The modification of the CHEXA bulk entry to allow for collapsed CHEXA element definition. Note that
the collapsed CHEXA element is not supported in a glue or contact region.

• The creation of the COLPHEXA parameter. You can allow collapsed CHEXA elements to bypass input
file checks with the COLPHEXA parameter. To do so, specify PARAM,COLPHEXA,YES in the bulk section
of the input file.

Collapsed CHEXA elements

Any face of a CHEXA element can be collapsed to an edge. The edge of the collapsed face represents the
crack front.

Figure 4-7 shows the connectivity for a standard CHEXA element.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-83
© 2023 Siemens
 4. Element support

Figure 4-7. Standard CHEXA Element

Figure 4-8 shows the CHEXA element of Figure 4-7 with the G2–G14–G6–G18–G7–G15–G3–G10 face
collapsed so that the G2–G14–G6 edge and the G3–G15–G7 edge become the crack front. Alternately,
the G2–G14–G6–G18–G7–G15–G3–G10 face could be collapsed so that the G2–G10–G3 edge and the
G6–G18–G7 edge would become the crack front.

Figure 4-8. Collapsed CHEXA Element

Two options are available for specifying a CHEXA element with a collapsed face:

• In Format 1, 15 unique grid IDs are specified in the 20 grid ID fields of the CHEXA bulk entry.
Format 1 is typically used for elastic material models. With Format 1, mid-side grids can move to the
quarter-span locations closest to the crack front.

4-84 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Crack simulation (SOL 401)

For the collapsed CHEXA element shown in Figure 4-8, the Format 1 specification is as follows:

1 2 3 4 5 6 7 8 9 10
CHEXA EID PID G1 G2 G2 G4 G5 G6
G6 G8 G9 G2 G11 G12 G13 G14
G14 G16 G17 G6 G19 G20

where the same grid ID is entered in the G2, G3, and G10 fields, another grid ID is entered in both the
G14 and G15 fields, and another grid ID is entered in the G6, G7, and G18 fields.

• In Format 2, 20 unique grid IDs are specified in the 20 grid ID fields of the CHEXA bulk entry. However,
eight of the grid IDs do not have unique coordinates. Format 2 is typically used for elasto-plastic
material models. With Format 2, mid-side grids remain at the mid-span locations.

For the collapsed CHEXA element shown in Figure 4-8, the Format 2 specification is as follows:

1 2 3 4 5 6 7 8 9 10
CHEXA EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13 G14
G15 G16 G17 G18 G19 G20

where the grids entered in the G2, G3, and G10 fields would share the same coordinates, the grids
entered in the G14 and G15 fields would share the same coordinates, and the grids entered in the
G6, G7, and G18 fields would share the same coordinates. Unlike Format 1 where grids in the CHEXA
element connectivity are merged, Format 2 does not merge coincident grids in the CHEXA element
connectivity. Thus, these grids can move independently of one another.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-85
© 2023 Siemens
 4. Element support

4.21 Stress output coordinate system

SOLs 401 and 402 output stress and strain in the body-fixed material coordinate system for the following
elements, where the body-fixed material coordinate system is the material coordinate system relative to
the deformed state.

• 3D solids elements CTETRA, CHEXA, CPENTA and CPYRAM

• Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8

• Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8

• Shell elements CTRIAR, CQUADR, CTRIA6, and CQUAD8 along with the CQUAD4 and CTRIA3 which are
automatically converted to CQUADR and CTRIAR elements.

The transformation matrix from the initial or the body-fixed material coordinate system to the basic
coordinate system is written to the TRMBU or TRMBD datablocks, respectively, for post processors.

3D solid, plane strain, and plane stress elements output options (SOL 401 only)

In SOL 401, the SYSTEM(627)=0 setting is available to optionally write the stress and strain output for
the 3D solid, plane strain, and plane stress elements to the basic coordinate system.

• SYSTEM(627)=0 - SOL 401 outputs stress and strain on the 3D solid, plane strain, and plane stress
elements in the basic coordinate system.

• SYSTEM(627)=1 (Default) - SOL 401 outputs stress and strain on the 3D solid, plane strain, and plane
stress elements in the body-fixed material coordinate system.

The system cell 627 does not apply to the shell, beam, spring, or cohesive elements.

Shell, beam, spring, or cohesive elements output options

• For the shell elements CTRIAR, CQUADR, CTRIA6, and CQUAD8 along with the CQUAD4 and CTRIA3
elements that are automatically converted to CQUADR and CTRIAR elements, the stress, strain, and
element force (shell resultants) are always output in the body-fixed material coordinate system.

• For the CBAR and CBEAM elements, the stress, strain, and element force (beam resultants) are always
output in the body-fixed element coordinate system, where the body-fixed element coordinate system
is the element coordinate system relative to the deformed state.

• Cohesive elements, the relative displacements, and tractions are always output in the body-fixed
material coordinate system.

4-86 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Direct matrix input on grid points (DMIG)

4.22 Direct matrix input on grid points (DMIG)

SOL 401 DMIG Support

SOL 401 supports the direct matrix input of stiffness, damping, and mass on grid points. You define the
matrix with the DMIG bulk entry. The DMIG entry should be referenced in the case control above the
subcase level (globally) by the following commands:

• K2GG command if the DMIG matrix represents stiffness.

• B2GG command if the DMIG matrix represents damping.

• M2GG command if the DMIG matrix represents mass.

The software uses the matrices defined with the DMIG entry to augment the stiffness, damping, and
mass matrices computed from the finite elements. For example, body forces defined with the RFORCEi
and GRAV entries will automatically consider the new total mass, which includes the DMIG mass.

Additional information:

● The matrices defined on the DMIG entry for SOL 401 must be symmetric.

● You can define the parameters CM2, CK2, and CB2 to scale the linear DMIG matrices defining mass,
stiffness, and damping. The parameters CM1, CK1, and CB1 are not supported.

● When you include DMIG matrices in restart solutions, for both the initial and restart solution, you
must reference the DMIG entries from the global case control using the appropriate K2GG, M2GG, and
B2GG command.

SOL 402 DMIG Support

SOL 402 supports the direct matrix input of mass on grid points. You define the matrix with the DMIG
bulk entry. The DMIG entry should be referenced in the case control above the subcase level (globally)
by the M2GG command.

The software uses the matrices defined with the DMIG entry to augment the mass matrices computed
from the finite elements. For example, body forces defined with the RFORCEi and GRAV entries will
automatically consider the new total mass which includes the DMIG mass.

Additional information:

● The matrices defined on the DMIG entry for SOL 402 must be symmetric.

● The parameters CM2, CK2, CB2, CM1, CK1, and CB1 are not supported.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-87
© 2023 Siemens
 4. Element support

● For restart solutions, if you included the DMIG matrices in the initial solution, you should not include
them in the restart solution.

4-88 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - External superelements

4.23 SOL 402 - External superelements

An external superelement is a reduced boundary representation of a component model stored in an
external file. You create each external superelement in a specific component solution. The reduced
boundary representation for an external superelement includes the boundary matrices such as stiffness
and mass written in terms of the boundary degrees-of-freedom (DOF).

After you create one or more external superelements with component solutions, you can then combine
them at the boundary DOF with your residual structure for an assembly solution using SOL 402.

External superelement component solution

You can create superelements using either a SOL 101 static reduction or a SOL 103 modal reduction
(component mode synthesis). The following are the input file requirements for the component solution.

• You define the EXTSEOUT case control command above the subcase level to request the creation of
the superelement.

You must include the DMIGOP2 describer to request that that the superelement matrices be exported
to an .op2 file.

You can optionally define the ASMBULK describer to request for the software to write an *.asm file
which includes boundary connection data. This data will help you define your assembly solution input
file as described in the Superelement assembly solution instructions below.

SOL 402 does not currently recover results on the omitted DOF in the assembly solution, so you do
not need to request the geometry with the GEOM describer.

EXTSEOUT(ASMBULK,DMIGOP2=20)

• If you are creating the superelement with a SOL 101 statics reduction, you select the superelement
boundary DOF with the ASET bulk entry.

ASET 1005 123456

• If you are creating the superelement with a SOL 103 modal reduction, you select the superelement
fixed boundary locations with the BNDFIX bulk entry and the free boundary locations with the
BNDFREE bulk entry. Fixed boundary DOF are constrained when computing the component modes,
and free boundary DOF are free. Fixed boundary are generally used at the superelement connection
locations and free boundary can be used, for example, where you plan to apply a load or perhaps to
recover results in the assembly solution at a DOF that must be unconstrained.

BNDFIX 1005 123456

BNDFREE 1007 123456

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-89
© 2023 Siemens
 4. Element support

• The displacement coordinate system of the boundary grid points must use the default basic
coordinate system, and not a local system. This is the case for superelements created with both
SOL 101 and SOL 103. The displacement coordinate system is defined with the CD field on the GRID
bulk entry.

• If you are creating the superelement with a SOL 103 modal reduction, you must specify the real
eigenvalue extraction options with an EIGR or EIGRL bulk entry.

You also must define SPOINT and QSET/QSET1 bulk entries to create a DOF set for the software to
retain the reduced component modes. The number of SPOINTs must be greater than the number of
modes you request for the solution on the EIGRL bulk entry.

EIGRL 100 20 0 7
SPOINT 100001 THRU 100500
QSET1 0 100001 THRU 100500

• In the file management section, you must specify an ASSIGN statement for the external
superelement .op2 file that will be created from the component solution.

$* FILE MANAGEMENT
ASSIGN OUTPUT2='inner_panel_sim1-inner_panel_superelement_0.op2' ,
STATUS=UNKNOWN UNIT=20

• You can define loads in your component solution and the software writes them to the external
superelement. You can then select the individual loads in the assembly solution. For SOL 402, this
only applies to the ramped loads selected with the LOAD=n case control command, and not to the
time assigned loads selected with the DLOAD=n case control command.

Component solution SOL 103 input example:

$* FILE MANAGEMENT
ASSIGN OUTPUT2='inner_panel_sim1-inner_panel_superelement_0.op2' ,
STATUS=UNKNOWN UNIT=20
$* EXECUTIVE CONTROL
SOL 103
CEND
$* CASE CONTROL
EXTSEOUT(DMIGOP2=20)
METHOD = 100
$* BULK DATA
BEGIN BULK
EIGRL 100 20 0 7 MASS
SPOINT 100001 THRU 100500
QSET1 0 100001 THRU 100500
.....
PARAM POST -2
$* GRID CARDS
$*

4-90 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - External superelements

GRID* 1001 16.1333330000E+029.5000000000E+01+

* 1.5000000000E+01 1
.....
$* ELEMENT CARDS
CQUAD4 1014 1 1118 1164 1128 1144 0.0000
.....
$* Superelement boundary constraints
BNDFIX 1005 123456
BNDFIX 1014 123456
BNDFIX 1046 123456
BNDFIX 1155 123456
BNDFIX 2001 123456
BNDFIX 2002 123456
BNDFIX 3001 123456
BNDFIX 3002 123456
....
ENDDATA

Superelement assembly solution

For the assembly solution, you need the external superelement .op2 files to be created in the
component solutions, and a new SOL 402 assembly solution input file which includes the following:

• In the file management section, specify an ASSIGN statement for each external superelement that you
want to include in the assembly solution.

$* Superelement ID: 23
ASSIGN INPUTT2='inner_panel_superelement_0.op2' ,
UNIT=201
$* Superelement ID: 24
ASSIGN INPUTT2='outer_panel_superelement_0.op2' ,
UNIT=202

• You include the portions of your model that have not been reduced to a superelement. This portion is
considered the residual structure.

• If the ASMBULK describer was specified in the component solution, you can use the bulk entries in the
*.asm file to help you define the following in the bulk data of your assembly solution input file.

• The SEBULK bulk entry defines the external superelement ID and the unit number used in the
ASSIGN statement.

$* Superelement ID: 23 Orientation and Connection to Residual

Structure
SEBULK 23 EXTOP2 MANUAL 201

• The grid point IDs selected for the boundary DOF must be defined in the assembly solution input
file, because they are used to connect the superelements.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-91
© 2023 Siemens
 4. Element support

• The SECONCT bulk entry defines the grid point connections between two superelements. The
residual structure uses an ID of "0" as shown in the SECONT example below.

SECONCT 23 0
NO +
+ 1005 26051 1014 26060 1046 26092 1155
26201+
+ 2001 27047 2002 27048 3001 28047 3002
28048

• The SELOC bulk entry is needed when you are relocating (or reorienting) the superelement.
You define three non-colinear boundary grid points belonging to the superelement, and three
belonging to the residual.

SELOC 23 1005 1014 2001 26051 26060 27047

• If you defined loads in your component solution, for the assembly solution, you can define the
SELOAD bulk entry to select the loads included with the external superelement. The input format
for the SELOAD entry is:

1 2 3 4 5 6 7 8 9 10
SELOAD LIDS0 SEID LIDSE

where LIDS0 is the new load ID defined in the assembly solution input file, SEID is the external
superelement ID, and LIDSE is the original load ID defined in the component solution. LIDS0 should
match the value of n on a LOAD=n case control command defined in the assembly solution input
file.

• Your assembly solution cannot include a Fourier subcase.

• You can include a superelement in an assembly model that has cyclic symmetry, but the superelement
must represent a full 360 degrees and not a cyclic component. The rest of the model can include
cyclic symmetry.

• The SEDAMP and SEUNIT bulk entries are not supported in SOL402.

Assembly solution input example:

$* FILE MANAGEMENT
$* Superelement ID: 23
ASSIGN INPUTT2='inner_panel_superelement_0.op2' ,
UNIT=201
$* Superelement ID: 24
ASSIGN INPUTT2='outer_panel_superelement_0.op2' ,
UNIT=202
$* EXECUTIVE CONTROL
SOL 402

4-92 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - External superelements

CEND
$* CASE CONTROL
SPC = 1
DISPLACEMENT(PLOT,REAL) = ALL
STRESS(PLOT,REAL,VONMISES,CENTER) = ALL
SUBCASE 1
LOAD = 101
NLCNTL = 101
TSTEP = 101
ANALYSIS = STATICS
.....
$* BULK DATA
BEGIN BULK
PARAM LGSTRN 1
PARAM MATNL 1
PARAM POST -2
.....
$* GRID POINTS
GRID* 49060 24-3.500000000E+012.1500000000E+02+
* 0.0000000000E+00 24
.....
$* ELEMENTS
CBAR 1 25023 29053 29203 0.0000-1.00000 0.0000
RBE2 25037 25038 123456 25039
.....
$* Superelement ID: 23 Orientation and Connection to Residual Structure
SEBULK 23 EXTOP2 MANUAL 201
SELOC 23 1005 1014 2001 26051 26060 27047
SECONCT 23 0 NO +
+ 1005 26051 1014 26060 1046 26092 1155 26201+
+ 2001 27047 2002 27048 3001 28047 3002 28048
$* Superelement ID: 24 Orientation and Connection to Residual Structure
SEBULK 24 EXTOP2 MANUAL 202
SELOC 24 1005 1014 2001 29053 29062 30049
SECONCT 24 0 NO +
+ 1005 29053 1014 29062 1046 29094 1155 29203+
+ 2001 30049 2002 30050 3001 31049 3002 31050
.....
ENDDATA

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-93
© 2023 Siemens
 4. Element support

4.24 Kinematic joints (SOL 402)

Solution 402 supports kinematic joints and flexible sliders. Kinematic joints allow structural analyses of
an assembly containing moving parts.

This capability lets you solve models such as aerostructures, helicopters, deployable structures in space,
gas turbines, and machine tools.

You can also use flexible slider joints to drive displacement of parts along beams, such as a model of a
track.

Kinematic joints

A kinematic joint connects two nodes. For some of the joints, you can define a third node for additional
spring or damper properties, or for driver loads.

(1) Horizontal sliders; (2) Vertical sliders; (3) Rotating

cylinder for swivel arm; (4) Rotating cylinder for mill head

In the CJOINT bulk entry, you define the joint connectivity: a joint connects two nodes, N1 and N2.

4-94 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Kinematic joints (SOL 402)

In the PJOINT bulk entry, you define the joint type. Depending on the joint type, you can model different
behaviors for the kinematic of the joint and you can constrain some DOFs:

Slider joints

Joint type Description

INLINE This joint constrains the 2nd node to slide along the straight line that joins
both nodes, and allows the relative rotations between the nodes.
SLIDER This joint constrains the 2nd node to slide along the straight line that joins
both nodes, but fixes the relative rotation between the nodes.
CYLDR This joint constrains the 2nd node to slide along the straight line that joins
both nodes and allows a relative rotation between the nodes along that axis.
SLIUNV This joint constrains the 2nd node to slide along the straight line that joins
both nodes. A universal joint relation is introduced between the rotations of
the two nodes.
SCREW This joint acts as the CYLDR joint, but the relative rotation around and
translation along the straight line that joins both nodes are related by the
pitch property of the screw.

Kinematic joints with coincident nodes

All the joints in the following table have two coincident nodes.

Joint type Description

REVOLUTE The joint constrains the nodes to rotate relative to each other along an axis
that the you define.
SPHERE This joint allows the relative rotation between the two nodes, but fixes their
relative translation.
FIXED This joint introduces rigid links between the two nodes. The links can be
released per DOF at a given time.
UNIVSL This joint acts as two combined REVOLUTE joints and designs a cardan shaft.
CONVEL A constant velocity joint is similar to a universal joint, except that a constant
velocity joint ensures a constant velocity through the joint's spin axis.

Options

Optionally, in the PJOINT bulk entry, you define the stiffness of the joint and add friction to the behavior
of the joint, while in the PJOINT2 bulk entry, you add a spring and/or damper behavior.

With the DRIVER bulk entry, you load the joint with a force or an imposed displacement for a
translational DOF. You load the joint with a torque or an imposed rotation for a rotational DOF

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-95
© 2023 Siemens
 4. Element support

In the JRESULTS case control command, you set output requests for the joint.

With the JCON bulk entry, you can define time constraints on a joint. At a given time, you can fix or
release the movement of the whole joint. For the FIXED joint, the links can be released per DOF at a
given time.

Flexible sliders

The FLXSLI bulk entry lets you define flexible sliders. You set a list of nodes to follow a track made of
beams.

(1) nodes to be displaced along the beam elements, (2) beam

elements, (3) slider elements generated by the solver, (4) sensor node

You can define several slider types depending on how you want to control the relative rotations of the
nodes around the track.

You can also define friction and, with a driver, you can impose a force or displacement on the slider.

When you set a driver, you can also request to output the relative displacement along the curvilinear
abscissa of the track with the FLXRESULTS case control command.

4-96 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Formulation of isoparametric elements

4.25 Formulation of isoparametric elements

In the finite element method, parametric mapping is frequently used to map an irregular region into
a regular one. The coordinate system used in the parametric mapping is a natural coordinate system
suitable for the geometry. For instance, a natural coordinate system (ξ,η) is used for a quadrilateral
surface in which each corner node has an extremum value of +1 or -1 in ξ and η. Then, the geometry
of the internal points of the finite element can be described in terms of the nodal coordinates by the
parametric mapping. The mathematical expression for this parametric mapping or interpolation is called
a shape function. The displacement field inside the element should also be interpolated in terms of
nodal displacements. The mapping is isoparametric if the same shape function is used to interpolate the
displacement field as well as the geometry. The merit of isoparametric mapping is that the displacement
field is invariant to the orientation of the Cartesian coordinate system x and y.

Most of the elements are isoparametric elements, in which the shape functions are expressed in terms
of isoparametric coordinates. In what follows, derivations are shown for the isoparametric coordinates,
shape functions, element matrix describing the strain-displacement relations, volume integration for
stiffness and mass matrices by Gauss quadrature, and element loads are derived for a tetrahedron
element to illustrate element related operations.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-97
© 2023 Siemens
 4. Element support

4.25.1 Isoparametric coordinates

Cartesian coordinates are not convenient to describe the geometry or the displacement field of a
tetrahedron element. Let us introduce a set of volume coordinates (L1 L2 L3 L4), such that

as shown in the figure Volume Coordinates for Tetrahedron. The relation between volume and
Cartesian coordinates can be established for a linear tetrahedron (without midside nodes) as follows:

x = L1x1 + L2x2 + L3x3 +L4x4

y = L1y1 + L2y2 + L3y3 +L4y4

z = L1z1 + L2z2 + L3z3 +L4z4

1 = L1 + L2 + L3 +L4

Equation 4-15.

It is obvious from Equation 4-15 that the shape functions are simply the volume coordinates, i.e.,

N1 = L1, N2 = L2, ..., etc.

Equation 4-16.

because x = Σ Nixi.

Shape functions for the quadratic tetrahedron can be derived using Lagrangian interpolation. These are

N1 = (2L1 – 1)L1, etc. for corner nodes

and N5 = 4L1, L2, etc. for midside nodes.

Equation 4-17.

4-98 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Isoparametric coordinates

Notice that these shape functions, Equations 4-16 and 4-17, satisfy element convergence criteria:
integrability (Cn-1 continuity for n-th derivative) and completeness (no straining by a rigid body mode,
constant strain condition, and continuous displacement field).

With the isoparametric element, the same shape functions are used to describe the displacement field as
well as the geometry, i.e.,

Equation 4-18.

The strains are calculated as

Equation 4-19.

where strain vector

Equation 4-20.

element matrix

Equation 4-21.

nodal displacement vector

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-99
© 2023 Siemens
 4. Element support

Equation 4-22.

with

Equation 4-23.

Equation 4-24.

Because the shape functions are defined in terms of local coordinates, a coordinate transformation is
required to obtain global derivatives. Volume coordinates involve four coordinates (one of which is
dependent), and the Jacobian matrix will become rectangular. To avoid this difficulty, let us introduce
local coordinates (ξ,η,ζ) as follows:

4-100 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Isoparametric coordinates

Equation 4-25.

Derivatives with respect to the local coordinates can be expressed in terms of global derivatives using
the chain rule, i.e.,

Equation 4-26.

where the Jacobian matrix is expressed in terms of shape functions as

Equation 4-27.

This Jacobian matrix must be inverted to obtain global derivatives, from which the element matrix is
formed. Notice that the determinant of the Jacobian matrix is called Jacobian which represents a volume
change, i.e.,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-101
© 2023 Siemens
 4. Element support

Equation 4-28.

4-102 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Shape functions

4.25.2 Shape functions

To make tetrahedron element compatible with other solid elements (HEXA and PENTA), deletion of any
or.all of.the midside nodes is permitted. The shape functions are modified with Kroneker deltas (δ5 - δ10)
where

δi = 0 if the midside node i is deleted

= 1 if the midside node i is not deleted

The goal is to construct functions which are unity at the associated node and zero at all other nodes,
regardless of any combination of deleted midside nodes, by the following scheme. At the corner nodes

At the midside nodes

Shape functions are identified as follows:

Derivatives of the shape functions with respect to the local coordinates are obtained as follows:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-103
© 2023 Siemens
 4. Element support

These shape functions and derivatives may be reduced to those for 4-noded and 10-noded tetrahedron
elements. It can be verified that, for any combination of deleted midside nodes, there exist a condition

which satisfies the constant strain requirement.

4-104 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Example element matrix

4.25.3 Example element matrix

To illustrate the computational procedure, an element matrix for a linear tetrahedron (4-noded) element
is explicitly derived here. The shape functions and the derivatives are tabulated below:

Node Ni δNi/δξ δNi/δη δNi/δς

1 ξ 1 0 0
2 η 0 1 0
3 ς 0 0 1
4 1 – ξ – η – ς –1 -1 –1

Then the Jacobian matrix may be found as

where (xij = xi - xj) is used for convenience. Upon inverting the Jacobian matrix, we have

where

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-105
© 2023 Siemens
 4. Element support

The global derivatives of the shape functions are

Hence the element matrix will be

Notice that the rank of [B] matrix is 6.

4-106 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Volume integration of element matrices

4.25.4 Volume integration of element matrices

By virtue of variational principles, the element stiffness matrix is derived as follows:

Equation 4-29.

where D is a (6x6) material tangential matrix.

While analytical integration is possible, there are some advantages in using numerical integration. The
Gaussian quadrature is used for the tetrahedron as usual. The minimum number of intergration points
required for non-singular stiffness matrix may be determined based on

Equation 4-30.

These numbers are found to be 1 and 4 for linear and quadratic tetrahedron, respectively. Using the
integration formulas shown in the figure Gaussian Quadrature for Tetrahedron, the element stiffness
matrices for linear and quadratic tetrahedron may be computed as

for 4–noded TETRA,

for 5–10 noded TETRA,

Equation 4-31.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-107
© 2023 Siemens
 4. Element support

where the scaling factor 1/6 is introduced to compensate IJI =6x (Volume). One-point scheme should be
used for 4-noded tetrahedron (all the midside nodes deleted) and four-point scheme otherwise.

It is difficult to determine lumped masses when some of the midside nodes are deleted. However, the
consistent mass matrix may be obtained using the same shape functions, i.e.,

Equation 4-32.

where [Ň] = [N1I N2I ..... N10I], with I being (3x3) identity matrix. Again the Gaussian quadrature 4-point
formula is used to find

Equation 4-33.

Notice that 4-point scheme is to be used even for 4-noded tetrahedron. For computational convenience,
the consistent mass may be converted to the lumped mass. One way to achieve this is to take the
diagonal terms and scale them so that the total mass is preserved.

4-108 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Element loads and equilibrium

4.25.5 Element loads and equilibrium

Nodal forces are computed from the element stresses using element matrix, i.e.,

Equation 4-34.

The Gaussian integration is performed as

for 4-noded tetrahedron and

for (5-10)-noded tetrahedron.

Equation 4-35.

Thermal load is like an initial strain. Therefore, nodal forces due to thermal load are obtained by

Equation 4-36.

where {εo}T = αΔT < 1 1 1 0 0 0 >. With anisotropic thermal properties, {εo}T becomes ΔT < α1, α2 ... α6 >
in general.

The pressure load applied to any surface of the tetrahedron may be distributed to the grid points using
the shape functions applicable to the 6-noded triangular element with removable midside nodes, i.e.,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-109
© 2023 Siemens
 4. Element support

Equation 4-37.

where {n} is a unit direction vector associated with a pressure (p) and

with I being (3 x 3) identity matrix. Shape functions (Ni’) are shown in the figure Shape Functions for
Pressure Load. Area integration should be performed using Gaussian quadrature formulas shown in the
figure Gaussian Quadrature for Pressure Load, i.e.,

Equation 4-38.

During the nonlinear iteration process, the equilibrium is not reached until convergence is achieved. The
equilibrium is sought in the global level when the residual load R approaches zero. The residual load
vector is defined as

Equation 4-39.

where {P} is the applied load vector including the thermal load and Σ implies assemblage in the global
coordinate system (coordinate transformation required).

4-110 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Element coordinates

4.25.6 Element coordinates

The element coordinate system for the tetrahedron element is defined with the initial element geometry
such that

• The origin is at the first grid point in the connectivity, G1.

• The x-axis is determined by connecting the origin G1 to node G2, i.e.,

Equation 4-40.

• The y-axis is determined by orthonormalization (Gram-Schmidt process) of the edge direction (V13)
with respect to x-axis,

Equation 4-41.

• The z-axis is orthogonal to x and y according to the right-hand rule, i.e.,

Then, the transformation from element coordinates to the basic coordinates is simply

Equation 4-42.

where

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-111
© 2023 Siemens
 4. Element support

Equation 4-43.

and < xe, ye, ze > Tbasic is the position vector of the element coordinate system with respect to the basic
coordinate system. Notice that [Tbe] is an orthogonal matrix, i.e.,

4-112 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Stress data recovery

4.25.7 Stress data recovery

In case of linear analysis, the stresses at the integration point are recovered as

Equation 4-44.

with

where {σ}, [B], {u} and {α} are defined in the element coordinate system, and the shape function
{Ni} interpolates Gauss point temperatures from the nodal temperatures. In case of nonlinear analysis,
stresses are computed again upon convergence, starting from the last converged state (last converged
solution of σ and u), i.e.,

Given {σold} and

Equation 4-45.

with

the nonlinear material routine computes updated stresses {σnew}, which are stored in ESTNL.

To output grid point stresses, the stresses, the integration points must be extrapolated to the nodal
points. A linear extrapolation can be applied using stresses at the element c.g. and the corner Gauss
point associated with a grid point. For a tetrahedron, referring to Figure 4-10,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-113
© 2023 Siemens
 4. Element support

Equation 4-46.

where

This yields

Equation 4-47.

In matrix form for all the grid points in the element

Equation 4-48.

where

This process must be operated on every component of stress vector. No extrapolation is required for
1-point integration.

4-114 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Stress data recovery

Figure 4-9. Volume Coordinates for Tetrahedron

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-115
© 2023 Siemens
 4. Element support

Figure 4-10. Gaussian Quadrature for Tetrahedron

4-116 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Stress data recovery

Figure 4-11. Shape Functions for Pressure Load

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 4-117
© 2023 Siemens
 4. Element support

Figure 4-12. Gaussian Quadrature for Pressure Load

4-118 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 5. Material support
5.1 Material overview
SOLs 401 and 402 - Material type support

• The MAT1 and MATT1 (temperature dependent) bulk entries define isotropic materials.

• The MAT2 and MATT2 (temperature dependent) bulk entries define anisotropic materials for shell
elements.

• The MAT3 and MATT3 (temperature dependent) bulk entries define orthotropic materials.

• The MAT8 and MATT8 (temperature dependent) bulk entries define orthotropic materials for shell
elements.

• The MAT9 and MATT9 (temperature dependent) bulk entries define anisotropic materials.

• The MAT11 and MATT11 (temperature dependent) bulk entries define orthotropic materials.

• The MATCZ bulk entry defines material properties for cohesive elements.

• The MATDMG bulk entry defines properties for progressive ply failure.

• The MATFT bulk entry defines the failure theory allowables for both shell and solid composites.

• The MATS1 or the MPLAS bulk entries define plastic material data.

• The MATCRP or the MVPLAS bulk entries define creep material data.

• SOL 401 supports a nonlinear elastic material for the 3D solid, plane stress, plane strain, generalized
plane strain, axisymmetric, chocking, and shell elements.

• Plastic and creep materials can optionally be assigned to the following elements: shell, 3D solid,
axisymmetric, plane stress, plane strain, CBAR, and CBEAM. You can enable one or both plasticity/
creep in all subcases or in specific subcases.

The MATCRP and CREEP bulk entries define creep materials and properties.

You can enable one or both plasticity/creep in all subcases or in specific subcases.

• The MUMAT bulk entry defines the material properties for the user defined material subroutine.

For more information, see User defined materials.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-1
© 2023 Siemens
 5. Material support

• The MATSR specifies strain-rate dependent properties for use with a MATS1 entry.

• Externally constructed, user-defined creep models.

SOL 402 only - Additional Material type support

• The MATHE and MATHOP bulk entries define hyperelastic materials.

• The MATHEM bulk entry adds the Mullins effects to the MATHE material.

• The MATHEV bulk entry adds viscoplastic effects to the MATHE material.

• The MATTC bulk entry specifies temperature-dependent creep coefficients on CREEP entry fields using
TABLEM1 entries.

For more information, see Hyperelastic materials (SOL 402).

5-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Plasticity analysis

5.2 Plasticity analysis

The constitutive plasticity model in SOLs 401 and 402 is a standard elastic-plastic model that allows for
bilinear and multilinear stress-strain curve representations. For multilinear representations, tabular data
is used to define the stress-strain curve. You can specify that the strain values in the tabular data are
either total strain or plastic strain. You can also define material properties as temperature-dependent. At
present, the von Mises yield criterion is the only yield criterion that is supported.

For bilinear stress-strain representations, you can select either isotropic, kinematic, or combined
hardening. For multilinear stress-strain representations, isotropic hardening is the only hardening rule
available.

You can selectively enable and disable plasticity effects in subcases. If plasticity-enabled subcases
are sequentially dependent, the plasticity state variables at the end of one subcase are used as the
plasticity state variables at the beginning of the next subcase. If a plasticity-disabled subcase is placed
between plasticity-enabled subcases, and the subcases are all sequentially dependent, the plasticity
state variables at the end of the preceding plasticity-enabled subcase are used as the plasticity state
variables at the beginning of the later plasticity-enabled subcase.

However, with the exception of special situations, we recommend you avoid placing a sequentially
dependent plasticity-disabled subcase after a plasticity-enabled subcase. Doing so eliminates the
possibility that the analysis does not account for changes to the plasticity state variables that might
result from the loading in the plasticity-disabled subcase.

Creep analysis is also supported in SOLs 401 and 402. You can enable one or both plasticity/creep in all
subcases, or you can enable one or both in specific subcases.

For more information about creep analysis, see Support for creep analysis.

User interface

• The MATNL parameter. With the MATNL parameter, you can globally switch the plasticity analysis
capability on or off.

• For SOL 401, the PLASTIC parameter is available on the NLCNTL bulk entry to optionally turn off the
plasticity capability in a subcase.

For SOL 402, you use the same parameter but on the NLCNTL2 bulk entry.

• The MPLAS or the MATS1 bulk entries allow you to define stress versus strain tabular data.

• When you define a plastic material for a large strain analysis on the MPLAS or MATS1 bulk entries, the
STRMEAS field is available to define the strain-stress measures of the input data. For more information,
see SOLs 401 and 402 - Stress-strain measures.

To activate plasticity analysis in SOLs 401 or 402, do the following:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-3
© 2023 Siemens
 5. Material support

1. Reference both the MATi and MPLAS bulk entries, or both the MAT1 and MATS1 bulk entries in the
regions where plasticity occurs. Note that the anisotropic materials MAT9 or MAT11 can optionally
be combined with the MPLAS. The MATS1 can only be combined with the isotropic material MAT1.

2. If you combine plasticity and creep materials, you should combine MPLAS with MVPLAS, or MATS1
with MATCRP.

3. Specify PARAM,MATNL,1.

4. Include a NLCNTL case control command that points to a NLCNTL/NLCNTL2 bulk entry.

5. On the NLCNTL/NLCNTL2 bulk entry, specify any applicable parameters.

If your input file contains subcases, and you want to include the effects of plasticity in specific subcases,
but not others, you have two options.

Option 1: Use a global NLCNTL case control command

1. Specify PARAM,MATNL,1.

2. Include a NLCNTL case control command above the subcases that points to a NLCNTL/NLCNTL2 bulk
entry.

3. On the NLCNTL/NLCNTL2 bulk entry, specify the applicable parameters.

4. In the subcases from which you want to disable the plasticity analysis capability, include a NLCNTL
case control command that points to a NLCNTL/NLCNTL2 bulk entry.

5. On the NLCNTL/NCLNTL2 bulk entry, specify the following:

• "PLASTIC" in a PARAMi field.

• "NO" in the corresponding VALUEi field.

Option 2: Include NLCNTL case control commands in every subcase

1. Specify PARAM,MATNL,1.

2. Include NLCNTL case control commands in each subcase. Multiple NLCNTL case control commands
can point to a single NLCNTL/NLCNTL2 bulk entry.

3. In subcases in which you want to enable the plasticity analysis capability, point the NLCNTL case
control command to a NLCNTL/NLCNTL2 bulk entry with the applicable parameters specified.

4. In subcases in which you want to disable the plasticity analysis capability, point the NLCNTL case
control command to a NLCNTL/NLCNTL2 bulk entry with the following specified:

5-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Plasticity analysis

• "PLASTIC" in a PARAMi field.

• "NO" in the corresponding VALUEi field.

If the properties on the MATi bulk entry are temperature-dependent, include a MATT1 bulk entry with
the same material identification number.

On the MPLAS or MATS1 bulk entry, you can specify if the tabular data used to describe the multilinear
stress-strain curve includes plastic strain or total strain. Total and plastic strains are related as follows:

where

For additional information, see the MPLAS and MATS1 bulk entries in the Simcenter Nastran Quick
Reference Guide.

Anisotropic Plasticity by Hill Yield Criterion

The Hill yield potential function is available on the MPLAS bulk entry for anisotropic plasticity. When you
select the Hill yield function, you define the following six stress ratios Rij relating a nominal yield stress
Y0 to the direction specific yield stress values Y0,ij. You can define the stress ratios as a constant for all
temperatures, or you can define them as temperature dependent.

The stress ratios are used to compute the following coefficients,

that are included in the following Hill yield potential function.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-5
© 2023 Siemens
 5. Material support

You can request for the software to apply the same Hill anisotropic stress to both plasticity and creep.
You must define the MPLAS and MVPLAS with the same ID, and the Hill stress ratios should be defined
only on the MPLAS bulk entry (not on MVPLAS). This definition ensures consistency for the combined
plasticity and creep with no differences in the yield and creep potentials.

Anisotropy definition by Lankford Strain Ratios

The Lankford Strain Ratios {r0; r45; r90} are a common measure of the plastic anisotropy of metal sheet.
The suffix 0, 45, 90 indicate the angle with respect to the lamination direction of the rolled metal sheet.
The following image illustrates their definition:

Starting with the Lankford strain ratios, it is possible to compute the specific parameters for a anisotropic
criterion. In the case of the Hill criterion, it is possible to find the Hill stress ratios:

For R23 and R13, there value is 1 because there is no relation available.

Those are the relations for the general anisotropy. Below are some other specific cases.

• Transverse anisotropy: There is no difference in the lamination plane between r0, and r90 (and also
r45 is the same). It is if only one strain ratio is available as the averaged value "r", then r= r0 = r90 =
r45. In this case the relations are:

5-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Plasticity analysis

• Planar anisotropy: There is a difference between r0 and r90, but r45 is equal to the mean value
between r0 and r90. It is if only r0 and r90 are available, then r45=0.5*(r0+r90).

The anisotropy is also measured by the following two parameters:

The normal strain ratio rN:

The plane strain ratio Δr:

We suggest the following reference for more information on defining anisotropy for metal forming
applications:

Hosford, W. F. and Caddell, R. M., Metal Forming: Mechanics and Metallurgy, Cambridge University
Press.

Plastic strain increment limit

When plastic deformation becomes significant, you may need to decrease the load increments to
capture the changing material behavior and to help convergence. The PLLIM parameter is available
on the NLCNTL bulk entry for SOL 401 and the NLCNTL2 bulk entry for SOL 402 to define the maximum
equivalent plastic strain increment allowed within a time step. When the plastic strain increment is
greater than PLLIM, the software will adjust the current time step increment.

See the remarks on the NLCNTL and NLCNTL2 bulk entries in the Quick Reference Guide for more
information.

For SOL 401, the software outputs the maximum effective creep and/or plastic strain increment to
the .f06 file at a converged time step. You can use the information to help reduce the strain increment,
for example, by reducing the time step size or by activating an adaptive time step method.

For the subcases that include active creep and/or plastic materials, the information is printed after the
message CONVERGENCE CHECK=YES when the strain increment is nonzero (>1.0E-14).

For example,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-7
© 2023 Siemens
 5. Material support

Hydrostatic pressure plasticity switch

You can request for the software to turn off plasticity at a Gauss point when the hydrostatic pressure
changes sign. Hydrostatic pressure is the portion of the total stress state that changes volume, and is
computed as:

P = -1/3 (σ11 + σ22 + σ33)

When the hydrostatic pressure changes sign at any Gauss point and the software turns plasticity off,
it will remain off at those Gauss point for the rest of the solution. The software will retain the plastic
strain that has occurred up to that time step, and continues the solution using elastic properties at those
locations.

You use the following parameters to request the hydrostatic pressure plasticity switch.

• You define the PLSHSOL parameter to "YES" on the NLCNTLG bulk entry to turn the switch on globally
(above the subcase level).

• In addition, in each preload, statics, or dynamics subcase you want the switch to be enabled, you
must also define the PLSHUT to "YES" on the NLCNTL bulk entry for SOL 401 or the NLCNTL2 bulk
entry for SOL 402.

5-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview of Plasticity

5.3 Overview of Plasticity

When you use the MATS1 bulk entry to define plasticity, the plasticity model includes a von Mises yield
function.

When you use the MPLAS bulk entry to define plasticity, the plasticity model includes the von Mises yield
function, the Hill yield function for anisotropic plasticity, and the cast iron yield type.

Both the MATS1 and the MPLAS entries include isotropic hardening, kinematic hardening, and combined
hardening.

The plasticity model must also be calibrated with uniaxial stress-strain data. The strain information
must be in the unitless form of length/length. Classical plasticity models include the following three
fundamental ingredients.

1. A yield function or yield criterion defines the limit of elastic behavior for a general state of stress.

The yield function may be thought of as a surface in a six dimensional stress space. It divides
the stress space into two regions. Points inside the yield surface are characterized by elastic
stress-strain behavior while stress states on the yield surface are at the limit of elastic behavior. The
yield function may be written as a function of stress and a hardening parameter k.

The von Mises yield function for an isotropic hardening material may be stated as:

J2 is the second invariant of the deviatoric stress tensor. The deviatoric stresses, sij, are given by:

where σm is the mean or average normal stress, and δij is the Kronecker delta.

Isotropic hardening assumes that the uniaxial yield stress, σy, is a function of plastic straining.

For kinematic or combined hardening, the von Mises yield function is

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-9
© 2023 Siemens
 5. Material support

J 2́ is the second invariant of the shift stress that is defined as the deviatoric stress minus the back
stress. The back stress may also be thought of as the position of the center of the yield surface in
the six-dimensional stress space. For initially isotropic materials, the back stress tensor components
are initially zero.

2. A flow rule determines the relative magnitudes of the components of the plastic strain increment
tensor.

The software uses an associated flow rule in which the plastic potential function, g, is the same as
the yield function, f, and the components of the plastic strain increment are given by:

In vector form, for the von Mises yield surface with kinematic hardening, the plastic flow vector is
given by:

For isotropic hardening, this equation reduces to the well-known Prandtl-Reuss equations.

3. A hardening rule defines the changes in the yield function as a result of plastic straining.

Also see the MPLAS bulk entry for information on the exponential saturation hardening rule, the
sublayer hardening rule, and the Chaboche hardening rule.

Isotropic Hardening

When you select isotropic hardening, the software uses a piece-wise linear stress-strain curve. The
isotropic hardening assumption isn't very realistic for most materials subjected to cyclic loading.
However, it is relatively simple and efficient.

5-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview of Plasticity

Isotropic hardening assumes that the yield surface expands uniformly as a result of plastic
straining. This assumption is achieved by making the yield stress a function of the integrated
effective plastic strain increments, which for a von Mises material is:

The slope of the stress plastic strain curve, Ep, is called the plastic modulus. It can be obtained from the
uniaxial stress-strain curve and is defined by:

For a von Mises material, the effective stress is given by:

Kinematic Hardening

When you select kinematic hardening, the software assumes a bilinear stress-strain curve. If the material
database contains a multilinear representation, only the yield point and the tangent modulus of the first
segment beyond the yield point are used to characterize the stress-strain behavior.

Kinematic hardening assumes that the yield surface translates in the stress space but doesn't change
size or shape. The yield stress, σy, doesn't change, but the back stress, αij, is a function of plastic
straining. The Ziegler-Prager kinematic hardening available with the MATS1 entry is a commonly used
model. This model assumes that the back stress increment is in the direction of the stress minus the back
stress.

The factor, dμ, depends on the plastic strain history.

Ziegler-Prager Combined Kinematic Isotropic Hardening

When you select combined kinematic isotropic hardening, the software assumes a bilinear stress-strain
curve. If the material database contains a multilinear representation, only the yield point and the
tangent modulus of the first segment beyond the yield point are used to characterize the stress-strain
behavior.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-11
© 2023 Siemens
 5. Material support

Combined hardening assumes that the yield surface both expands and translates in the stress space. The
plastic strain increment is composed of two components shown in the following equations:

where,

is associated with the isotropic expansion of the yield surface,

and is associated with the translation of the yield surface.

The reduced effective plastic strain associated with isotropic hardening is related to the effective plastic
strain by the following:

The back stress increment for Prager combined hardening is:

The back stress increment for Ziegler-Prager hardening is:

where M=0.5.

The software computes plastic strain increments using a backward Euler technique without sub-
incrementation. For the isotropic hardening model:

5-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview of Plasticity

where De is the elastic modulus matrix, εp is the plastic strain, is the effective plastic strain, and TYF
is the von Mises yield function.

The software will compute a consistent tangent modulus for use in generating the tangent stiffness
matrix. When this procedure is used with a full Newton-Raphson iteration, quadratic convergence can be
obtained. A detailed description of this procedure may be found in Crisfield, 1991.

References:

• Crisfield, M. A., Non-linear Finite Element Analysis of Solids and Structures (Chichester: John Wiley &
Sons, 1991).

• Chakrabarty, J., Theory Of Plasticity (New York: McGraw-Hill Book Company, 1987), 55-119.

• Chen, W. F. and Han, D. J., Plasticity for Structural Engineers, (New York: Springer-Verlag, 1988),
239-281.

• Lemaitre, J. and Chaboche, J. L., Mechanics of Solid Materials, (Cambridge: Cambridge University
Press, 1990), 161-240.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-13
© 2023 Siemens
 5. Material support

5.4 Strain rate-dependent plasticity

SOLs 401 and 402 support a strain rate-dependent plasticity material model. This material model
represents the hardening and the resulting increasing yield stress that occurs as the strain rate increases.

You have two options to define the strain rate-dependent plasticity. For either option described below,
in the regions of your model where you expect strain rate plasticity to occur, you will reference a MAT1
entry, a MATS1 entry, and a MATSR entry, all with the same ID.

You must also define the parameter setting PARAM,MATNL,1 to globally switch material nonlinear on.

• Option 1: Static stress scaling

This option scales the static stress found from an elastic-plastic material defined with the MATS1
entry. The elastic-plastic material definition can also reference temperature dependent stress-strain
data from the MATS1 entry.

You will define two constants on the MATSR bulk entry that are used in the plastic strain rate scaling
function below.

The software determines the current static yield stress σstat using the elastic-plastic material definition.
The static yield stress value is then scaled using the following strain-rate scaling function.

where is the current equivalent plastic strain rate, D is a constant defined with the TSRATE field
on the MATSR entry, and P is a constant defined with the BVALUE field on the MATSR entry.

Input example for option 1:

....
$ MAT1, MATS1, and MATSR all have the same ID
MAT1 1 2.08E+0880.0E+060.3 7.85E-061.72E-0520.0
....
$ MATSR defines the two constants for the scaling function
MATSR 1 4.0 6500.0
....
$ MATS1 and TABLES1 define the elastic-plastic material
MATS1 1 61 PLASTIC 0.0 1 1 3.50E+07
$ Stress-Strain data referenced from the MATS1 entry
TABLES1
61 +
+ 0.0 0.0 1.2E-02 2.5E+06 2.0E-02 3.0E+061.0
64.25E+6+
+ ENDT
....

5-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Strain rate-dependent plasticity

• Option 2: Strain rate-dependent tables

From the TID field on the MATSR bulk entry, you reference a TABLEST entry, which then references
multiple TABLES1 entries defining stress-strain tables for multiple plastic strain rates. In this case, the
software does not use the stress-strain data referenced by the TID or H fields on the MATS1 entry. You
cannot define a temperature dependency with this option. The MATS1 entry is still needed to define
the type of nonlinearity (TYPE field), the hardening rule (HR field), and the initial yield point (LIMIT1
field).

Because plastic strain rate data is often provided at logarithmic intervals, the software internally
computes the natural logarithm of both the current plastic strain rate value and the plastic strain
rates you enter on the TABLEST entry. Because log(0.0) cannot be computed, if you are including
stress-strain data for a plastic strain rate value of 0.0, you should enter a very small non-zero value
instead of 0.0. For example, .0001.

The following input file example includes stress-strain tables for the plastic strain rates 0.0, 200.0, and
400.0. The strain rate units are 1/second. Note that 0.0001 has been entered instead of the 0.0 plastic
strain rate for the reason described above.

...
MAT1 2 7.0+4 0.3 0.0
MATS1 2 PLSTRN 0.0 1 1 3.5E+7
$ TID field on the MATSR entry references the TABLEST entry.
MATSR 2 2
$ TABLEST references stress-strain tables for the plastic strain rates.
TABLEST 2
1 +
+ 0.0001 22 200.0 23 400.0 24 ENDT
....
TABLES1
22 +
+ 0.0 400.0 0.2 1400.0 ENDT
TABLES1
23 +
+ 0.0 567.52 0.2 1986.3 ENDT
TABLES1
24 +
+ 0.0 599.20 0.2 2097.2 ENDT
....

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-15
© 2023 Siemens
 5. Material support

5.5 SOLs 401 and 402 - Stress-strain measures

The abbreviations ENG, TRUE, and PK2 are used below to indicate the following strain-stress measures:
ENG = {Biot (engineering) strain, Biot stress}
TRUE = {True {log(True)strain, Cauchy stress}
PK2 = {Piola Kirchhoff Stress, Green strain}

SOL 401 and 402 stress-strain input measure

When you define a plastic material for a large strain analysis on the MPLAS or MATS1 bulk entries, the
STRMEAS field is available to define the strain-stress measures of the input data.

• When "ENG", "UNDEF", or blank is defined in the STRMEAS field, the software assumes the input data
is defined using ENG measure. When large strain (PARAM,LGSTRN,1) is requested, the software will
convert the data to TRUE measure. Otherwise, the data is not converted and the software uses ENG
measure.

• When "TRUE" is defined in the STRMEAS field, the software assumes the input data is defined using
TRUE measure. In this case, the software does no conversion of the data.

SOL 401 stress-strain measures and results output

• For a small strain analysis (PARAM,LGSTRN,0), the software uses ENG measure.

• For a large strain analysis (PARAM,LGSTRN,1), the software uses TRUE measure.

• PK2 measure is used for shell elements, although SOL 401 does not support shell elements with
large strain (PARAM,LGSTRN,1). As a result, for small strains (< 2%) on shell elements, the difference
between the various measures is not significant.

SOL 402 stress-strain measures and results output

• ENG measure is used for all elements when small displacements (PARAM,LGDISP,-1) and small strains
(PARAM,LGSTRN,0) are requested. This occurs for elements using linear or nonlinear materials.

• TRUE measure is used for elements using a nonlinear material and large strains (PARAM,LGSTRN,1) is
requested.

• PK2 measure is used for these cases:

● Large displacements (PARAM,LGDISP,1) and small strains (PARAM,LGSTRN,0) are requested. This
occurs for elements using linear or nonlinear materials.

● For elements using a linear material and large strains (PARAM,LGSTRN,1) is requested.

5-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOLs 401 and 402 - Stress-strain measures

● Shell and beam elements using a linear material and either large displacements (PARAM,LGDISP,1)
or large strains (PARAM,LGSTRN,1) is requested.

Additional information for SOL 402 measures

• When you use hyperelastic materials, it is recommended that you request large displacements
(PARAM,LGDISP,1) and small strains (PARAM,LGSTRN,0) because the material formulation is based
on these assumptions.

• Nonlinear materials are not supported for beam, bar, or rod elements that use a cross section that is
not a standard shape.

• Stress is not output for rod elements that use a linear elastic material.

• The measure is reported in the material section of the .f06 file:

1.3. CHECK OF MATERIALS

=======================

1.3.1. MATERIAL "MAT1_1"

------------------------

LINEAR ELASTIC BEHAVIOR

ELASTIC PROPERTIES
....
....
STRESS MEASURE : 2nd PIOLA KIRCHHOFF
STRAIN MEASURE : GREEN

SOLs 401 and 402- Stress-strain conversion

When you define a plastic material for a large strain analysis on the MPLAS or MATS1 bulk entries, if
you define ENG (for engineering measure) in the STRMEAS field, and you have requested large strain
(PARAM,LGSTRN,1), the software converts the data from engineering to true measure. The software
converts all data points, including the yield point. As a result, the elastic modulus is also converted to
true measure. The true measure modulus is used to calculate the plastic strain and validate the input
data.

If the true modulus is not equal to the value of E that you define in the MAT1 entry, the software still
uses E without conversion to calculate the linear elastic tangential matrix.

The software conversion procedure is as follows.

1. Convert stress-strain data to true measure.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-17
© 2023 Siemens
 5. Material support

You use the STRCONV parameter to request either the exact or the standard conversion methods.
When the exact method is requested (STRCONV=0), the true stress and strain are computed with:

where,

and are the true stress and strain,

and are the nominal (engineering) stress and strain defined on the TABLES1 bulk entry,

and is the lateral nominal strain computed by;

where,

is the lateral elastic nominal strain,

is the lateral plastic nominal strain,

is the elastic nominal strain,

and is the plastic nominal strain.

If plastic strain is defined in the TABLES1 entry, the nominal modulus EN on the MAT1 entry is used
to compute the elastic nominal strain ( ). If total strain is defined on the TABLES1 entry, the
slope of the line joining the first and the second point is used to compute the nominal modulus EN
which is then used to compute the elastic nominal strain.

The standard method is used by default (STRCONV=1). With the standard method, we assume
small strains and a Poisson's ratio of 0.5 for the plastic portion, and the true stress and strain are
computed with:

2. Compute the modulus in true measure.

The software computes a modulus using stress-strain in true measure. Before Simcenter Nastran
2022.1, the nominal modulus EN was used.

3. Compute the plastic strain.

5-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOLs 401 and 402 - Stress-strain measures

The software uses the modulus in true measure to compute the plastic strain. Before Simcenter
Nastran 2022.1, the nominal modulus EN was used.

The elastic strain in true measure is computed with:

The plastic strain in true measure is computed by subtracting the elastic strain from the total strain:

4. Validate that the non-elastic slopes are smaller than the elastic slope.

The software uses the modulus in true measure to validate the stress-strain data. Before Simcenter
Nastran 2022.1, the nominal modulus EN was used.

This validation is equivalent to a plastic strain that is monotonically increasing:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-19
© 2023 Siemens
 5. Material support

5.6 Cast iron plasticity SOLs 401 and 402

SOLs 401 and 402 support the gray cast iron plasticity material model. Gray cast iron has the following
characteristics.

• In tension, it is brittle as a result of the graphite flakes in the microstructure that act as stress
concentrators resulting in reduced yield strength.

In compression, the effect of the graphite flakes is less significant, and the ductile response is the
same as most steels. The compressive yield stress can be three (or more) times larger than the tensile
yield stress.

• The elastic properties are the same under tension and compression, and are defined on a MAT1 entry.

• In tension, it has an inelastic (plastic) volume change. As a result, you must define a plastic Poisson's
ratio in tension, which is the absolute value of the ratio of the transverse to the longitudinal plastic
strain under uniaxial tension.

In compression, the software assumes no inelastic volume change (incompressible, Poisson's ratio =
0.5).

• It has different hardening and flow behavior in tension and compression.

In tension, the software uses a pressure-dependent yield surface with a non-associated flow rule.

In compression, the software uses the von Mises yield condition with an associated flow rule.

Input summary

The MPLAS bulk entry is available to define the plastic material data.

You must also define the parameter setting PARAM,MATNL,1 to globally switch material nonlinear on.

You define the elastic material data on the MAT1 entry, which has the same ID as the MPLAS entry.

The MPLAS format includes specific rows to define yield function data and hardening rule data.

MPLAS format for gray cast iron

1 2 3 4 5 6 7 8 9 10
MPLAS MID Name/Descriptor
"YIELD" GCIRON

5-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cast iron plasticity SOLs 401 and 402

1 2 3 4 5 6 7 8 9 10
"ISOH" "TABULAR" TID Tension "T" "PLS" "TRUE" NUPL
TID "C" "PLS" "TRUE"
Compression

• Because there is different behavior in tension and compression for the gray cast iron material, you
must define an isotropic hardening data row for both tension data and compression. Field 5 in these
rows designates the data row as tension ("T") or compression ("C").

• The stress-strain data referenced from field 4 must be true (Cauchy) measures. The Xi, Yi data
defined on the TABLES1 entry must be stress-plastic strain, with the data beginning at the yield point
(X1=plastic strain at the yield point=0.0, Y1=yield stress).

• You must define the plastic Poisson's ratio in field 9 (NUPL) on the tension data row.

• For all fields with character inputs, the text shown in quotes are the only supported values. You must
define this text. See the MPLAS bulk entry in the Quick Reference Guide for the definition of these
fields.

• The second hardening row must have fields 2 and 3 blank, as shown in the format above.

Equations for gray cast iron material

• Yield surfaces

Tension:

Compression:

where,

the quantity results from the combination of q and r, and is defined as the angle of the tension
yield surface in the meridional plane for the stress state,

q, p, and r are stress invariants:

is the von Mises equivalent stress,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-21
© 2023 Siemens
 5. Material support

is the equivalent pressure stress,

is the third invariant of the deviatoric stress tensor,

is the identity tensor

is the stress deviator,

is the Cauchy stress.

• Flow rule

where in tension,

and in compression,

where,

• Hardening rules

Tension:

Compression:

• Constitutive model

5-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear elastic material (SOL 401)

5.7 Nonlinear elastic material (SOL 401)

SOL 401 supports a nonlinear elastic material for the 3D solid, plane stress, plane strain, generalized
plane strain, axisymmetric, chocking, and shell elements. You will define a nonlinear elastic uniaxial
stress-strain curve. The software will load and unload along this curve such that no permanent strains
are introduced.

Figure 5-1. Nonlinear Elastic Material

The material can accommodate bilateral properties (uniaxial tension-compression) accurately for the
multiaxial deformation provided the strain remains in the small range (less than 2%). If your application
requires large strain, you should use SOL 402 with a hyperelastic material.

You define the nonlinear elastic material with MAT1 and MATS1 bulk entries, all with the same ID.
You can also optionally define the MATT1, if, for example, you want Poisson's ratio to be temperature
dependent. On the MATS1 entry, you should include "NELAST" in the TYPE field to designate the
nonlinear elastic material. You will define the stress-strain data on the TABLES1 bulk entry, and
optionally the TABLEST entry, if the stress-strain data is temperature dependent.

If you define your stress-strain curve only in tension (quadrant 1), the behavior in compression (quadrant
3) will be the mirror image of the behavior in tension. In this case, you should define the first data point
at the origin.

You can also define unique stress-strain data in tension and compression. In this case, your data must
begin with the most negative value in quadrant 3; it must include the origin, and then proceed positive
ending with the most positive value in quadrant 1.

You must also define the parameter setting PARAM,MATNL,1 to globally switch material nonlinear on.

Theoretical

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-23
© 2023 Siemens
 5. Material support

The nonlinear elastic material satisfies the equivalence of the deformation work per unit volume for
simple tension, to the strain energy per unit volume (conservation of energy). In addition, the work
done for deformation is defined by the stress-strain curve in simple tension. That is,

Equation 5-1.

The effective strain is defined by

Equation 5-2.

From the total differential of equation 5-1, the following is obtained.

Equation 5-3.

Substituting equation 5-3 into equation 5-1, stresses can be expressed in terms of total strains.

Equation 5-4.

The tangential matrix can be obtained by differentiating equation 5-4.

Solution Algorithm

You specify the nonlinear stress-strain curve, , on the TABLES1 entry along with the MAT1 and
MATS1 entries. The software uses the following data for the computations.

Input data:

Output data:

5-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear elastic material (SOL 401)

A new strain state is computed by:

The effective strain is computed based on by

where

The effective strain is then:

The effective stress is determined from the stress-strain curve and .

The new stress state is determined by:

The tangential matrix is determined by:

where is the slope at . That is,

where is the k-th data point in the TABLES1 entry and k is determined such that
. Note that k=1 for and for .

Adaptation of the uniaxial compression stress-strain curve

For uniaxial loading, the magnitude of the strain for this single direction becomes the effective strain.
That is,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-25
© 2023 Siemens
 5. Material support

for uniaxial tension in x.

for uniaxial compression in x.

We need to find the effective stress corresponding to . The two known data points are the effective
stress for uniaxial tension , and the effective stress for uniaxial compression . Some method of
interpolation or extrapolation is required to predict the effective stress for the general stress state using
two known data points.

The first stress invariant is used for interpolation and extrapolation. That is,

Considering that the pure shear is midway between simple tension and simple compression, the first
stress invariant is used. Hydrostatic tension and compression cases will impose lower and upper bounds
for extrapolation. That is,

for uniaxial tension and compression.

for pure shear.

for hydrostatic pressure.

The instantaneous modulus should be interpolated or extrapolated in the same manner.

Computational procedure for bilateral stress-strain relations

The new stress state is proportional in magnitude to the effective stress , which is determined as
follows.

1. Compute the effective stress based on . That is,

2. Compute the first invariant of :

3. Determine the ratio by normalizing by . That is,

5-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear elastic material (SOL 401)

where signifies the relative distance from the midpoint of and at . It is implausible to
process a large value of , such is the case with a hydrostatic load. Therefore, will be confined to a
range, . The value will be reset to the limit if lies outside the range.

4. Look up the stress-strain curve defined on the TABLES1 entry and determine and . That is,

5. Determine based on , and . That is,

For the tangent matrix, the instantaneous modulus should be determined using the same ratio
as follows:

1. Compute the instantaneous slope at for tension. That is,

for .

where is the i-th data point on the TABLES1 entry.

2. Compute the instantaneous slope at for compression. That is,

for .

3. Determine based on , , and . That is,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-27
© 2023 Siemens
 5. Material support

5.8 Creep analysis

Material creep is a permanent deformation that results from the prolonged application of a constant
stress below the yield stress. For metals, material creep generally occurs at temperatures greater than
1/3*melting temperature.

The following summarizes the creep material process with Simcenter Nastran.

1. Creep Law

You should obtain uniaxial creep data for your specific material from a stress-relaxation test.
Each test determines the deformation (strain) over time as a result of a constant tensile load
at a constant temperature. You will need data from multiple tests to represent the loads and
temperatures for your application.

The strain rate data for material creep is divided into the following three stages.

• In the primary stage, the strain rate varies with time.

• In the secondary stage, the strain rate becomes relatively constant.

5-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

• In the tertiary stage, material damage begins until rupture occurs.

You can model the primary and secondary stages in SOLs 401 and 402, but not the tertiary stage.

You will select a creep law which mathematically represents your uniaxial creep data in a specific
stage of creep. A creep law defines the effective creep strain rate as a function of effective creep
strain ( ), effective stress ( ), and/or the temperature (T).

Simcenter Nastran has multiple creep laws for you to select with either the MVPLAS bulk entry, or
the MATCRP bulk entry.

See Creep laws.

If your law is not available on the MVPLAS or MATCRP entries, you can use a user defined creep law.
See User defined creep models (SOL 401 and 402).

2. Creep criteria, flow rule, and effective strain increment

a. The creep criteria function defines the relation between the effective stress and the stress
tensor .

b. The creep flow rule defines the relation between the creep strain rate tensor and the stress
tensor .

where the flow function g is equal to the criterion function f defined above in "a",

and is the effective creep strain rate computed using the creep law.

c. The criteria function and the flow rule are combined to compute the effective creep strain
increment .

See Creep criteria, flow rule, and strain increment computation.

3. Viscous Integration Scheme

To evaluate each increment of creep strain, the software performs a numerical integration based
on the generalized trapezoidal rule as follows:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-29
© 2023 Siemens
 5. Material support

where is the creep strain rate tensor computed with the flow rule, Δtn = tn – tn-1 is the duration
of the sub interval, and β is the integration factor you specify with the parameter CRINFAC on the
NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk entries.

See Viscous Integration Scheme.

4. Creep Time Step Control

Creep adaptive time stepping is available when the time steps you request with the TSTEP1 bulk
entry are either too coarse to produce accurate creep results, or too fine to produce creep results
efficiently.

See Creep time step overview.

See SOLs 401 and 402 - CRLIMR creep time stepping method.

See SOL 401 - TSCCR creep time stepping method.

See SOL 402 - TSCVSC creep time stepping method.

For SOL 401, the software outputs the maximum effective creep and/or plastic strain increment
to the .f06 file at a converged time step. You can use the information to help reduce the strain
increment, for example, by reducing the time step size or by activating an adaptive time step
method.

For the subcases that include active creep and/or plastic materials, the information is printed after
the message CONVERGENCE CHECK=YES when the strain increment is nonzero (>1.0E-14).

For example,

5. User Interface and Temperature Conversion

See User interface for a summary of all creep user interface options.

5-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

See Converting temperature units for creep materials for information on converting the
temperature units of your temperature dependent creep material data.

Creep laws

The creep law defines the effective creep strain rate as a function of effective creep strain, effective
stress, and temperature. The following table summarizes the available creep laws in Simcenter Nastran.

Law Effective creep strain rate* Creep stage Bulk Entries

Norton-Bailey time Primary MVPLAS, MATCRP
hardening
Norton-Bailey Primary MVPLAS, MATCRP
strain hardening

Generalized strain Primary MVPLAS, MATCRP

hardening
Generalized Norton Secondary MVPLAS, MATCRP

Generalized Secondary MVPLAS, MATCRP

Garofalo
User MUCRP or MVPLAS+MUCRP

* For the Norton-Bailey law, you can define A, B, D as temperature dependent. For the generalized creep
laws, you can define C1, C2, and C3 as temperature dependent, and/or you can define C4 to include the
temperature dependent term .

• Norton-Bailey creep law

The Norton-Bailey creep law is selected by entering "301" in the TYPE field on the MATCRP entry.
In the Norton-Bailey law, temperature is not accounted for explicitly. To account for temperature-
dependence, you can define the coefficients as tabular functions of temperature.

With the Norton-Bailey law, you can select either time or strain hardening using the HARD field on the
MATCRP bulk entry.

When HARD=TIME, the Norton-Bailey law has the When HARD=STRAIN (default), the Norton-Bailey
form: law has the form:

The time hardening rule uses time as a material The strain hardening rule assumes that the
state variable. It assumes that the material state is material state is determined by the accumulated
determined by the length of time the material has effective creep strain. When stress or temperature
been creeping. changes, the shift from one creep curve to
another is based on the accumulated effective
When stress or temperature changes, the shift
creep strain. This shift is illustrated in the
from one creep curve to another is based on the
following figure.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-31
© 2023 Siemens
 5. Material support

accumulated creep time. This shift is illustrated in The strain hardening rule is generally considered
the following figure. to be superior to the time hardening rule. Under
conditions of constant stress and temperature,
The time hardening rule is usually not very
the time hardening and strain hardening
realistic when very large changes in temperature
assumptions produce identical results.
or stress occur over the interval of interest.

Figure 5-3. Norton-Bailey strain hardening

Figure 5-2. Norton-Bailey time hardening

• Generalized strain hardening creep law

The strain hardening creep law is selected by entering "STRNHARD" in the L-TYPE field on the MVPLAS
entry, or the TYPE field on the MATCRP entry.

The C1, C2, C3, and C4 coefficients are used to define the strain hardening creep law as follows:

where εcr is the effective creep strain, σ is the effective stress, and T is the temperature.

A fatal error occurs if any of the C1, C2, or C3 fields are left blank. If C4 is left blank, the temperature
term is ignored.

• Generalized Norton Creep Law

The Norton creep law is selected by entering "NORTON" in the L-TYPE field on the MVPLAS entry, or
the TYPE field on the MATCRP entry.

The C1, C2, and C4 coefficients are used to define the Norton creep law as follows:

5-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

A fatal error occurs if either of the C1 or C2 fields are left blank. If C4 is left blank, the temperature
term is ignored.

• Generalized Garofalo Creep Law

The generalized Garofalo creep law is selected by entering "GENGAROF" in the L-TYPE field on the
MVPLAS entry, or the TYPE field on the MATCRP entry.

The C1, C2, C3, and C4 coefficients are used to define the generalized Garofalo creep law as follows:

A fatal error occurs if any of the C1, C2, or C3 fields are left blank.

If C4 is left blank, the temperature term is ignored.

• User Creep Law

You can define a creep law by developing and compiling an external user subroutine NUCREEP. The
external routine can optionally include multiple creep laws.

Source code examples are included with the Simcenter Nastran installation for you to begin your own
external material development. Ready-to-run demo cases are also included to demonstrate the input
file requirements and the general workflow.

The MUCRP bulk entry is available to define the creep coefficients in the Simcenter Nastran input file.
Simcenter Nastran passes this data to the NUCREEP routine. The MUCRP entry in your input file is the
trigger Simcenter Nastran uses to call the external routine.

You can define the MUCRP entry independently, or you can define the MVPLAS with a row that
includes "LAW" and LTYPE=USER that references the MUCRP entry. Only the combined MVPLAS and
MUCRP entries can be used to define anisotropic creep.

See User defined creep laws.

Creep criteria, flow rule, and strain increment computation

The form of the effective stress, the flow rule, and the effective strain increment computation depend if
you use the Von Mises or the Hill criteria.

The Von Mises criteria (isotropic creep) is always used when you define your material with the MATCRP
entry, and it is default criteria when you define your material with the MVPLAS.

You can select the Hill criteria (Anisotropic creep) with the ANISO field when you define your creep
material with the MVPLAS entry. You can use the "HILL" option with only creep, or the "MPLAS" option
when both plasticity and creep use the same Hill anisotropic stress function.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-33
© 2023 Siemens
 5. Material support

The following summarizes the creep criteria, the flow rule, and the effective strain increment
computation for the Von Mises and the Hill criteria.

• Creep criteria: Determines how the effective stress is computed from the stress tensor .

The general creep criteria function is:

The Von Mises criteria effective stress is:

The Hill criteria effective stress is:

Where F, G, H, L, M and N are functions of the Hill Stress Ratios.

When i=j

and when i≠j,

• Flow rule: Computes the creep strain rate tensor from the stress tensor .

The general form of the creep flow rule is:

where the flow function g is equal to the criteria function f.

5-34 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

The Von Mises criteria flow rule is:

where is the effective creep strain rate computed using the creep law, is the effective stress,
and Sij are the components of the deviatoric stress tensor.

• Effective creep strain increment: The criteria function and the flow rule are combined to compute
the effective creep strain increment .

Note that represents the components of the deviatoric creep strain increment. For both the Von
Mises and the Hill criteria, the total creep strain tensor and the deviatoric creep strain tensor are the
same since, for these criteria, the creep strain does not change the volume.

The Von Mises effective creep strain increment is:

The Hill effective creep strain increment is:

See the Hill criteria effective stress above for the definition of F, G, H, L, M and N.

Viscous Integration Scheme

You can request the implicit or the explicit creep integration method. The most important consideration
when choosing the integration method is whether the solution will converge and complete. The second
consideration is performance.

For improved performance, we recommend the explicit method when the creep material is the only
nonlinear condition in your model. Otherwise, the implicit method is recommended. The methods are
described as follows.

Implicit creep integration method

The implicit method performs a numerical integration based on the generalized trapezoidal rule:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-35
© 2023 Siemens
 5. Material support

where:
Δt is the current time step,
is the creep strain rate at the previous solution time t
is the creep strain rate at the current time t+Δt
β is the integration factor you specify with the parameter CRINFAC on the NLCNTL (SOL 401) or NLCNTL2
(SOL 402) bulk entries. When you define CRINFAC>0.0, the implicit method is used.

The implicit method is always stable; it can use larger time steps, but it often needs to iterate at each
time step to converge. For this reason, the implicit method is not as efficient. When additional nonlinear
conditions are requested (for example, plasticity or large displacement), the implicit method is either
necessary or it has no disadvantage in performance compared with the explicit method.

We recommend one of the following two CRINFAC settings for the implicit method because each
provides predictable stability and accuracy.

• CRINFAC=1.0: This choice is fully implicit, is highly stable, and has an accuracy of the 1st order.

• CRINFAC=0.5: This choice selects the trapezoidal rule, is stable (but less stable than fully implicit), and
has an accuracy of the 2nd order (more accurate than fully implicit). This option typically converges
faster than CRINFAC=1.0.

CRINFAC=0.5 is recommended for simple models where high stability is not required. It can result in a
faster solution with less time steps and iterations.

Explicit creep integration method

You request the explicit method by defining CRINFAC=0.0 (β=0.0); the generalized trapezoidal rule
reduces to the forward Euler method:

The explicit method is conditionally stable and requires more time steps than the implicit method for
stability and accuracy. Because the explicit method does not perform material iterations, and does not
need to update the stiffness, it is efficient to use for the specific models that it can successfully be used.

Note that the explicit method will produce a fatal error if both creep and plastic materials are defined.
You must turn off creep and/or plastic material computations in a subcase by defining the parameter
settings CREEP=NO and/or PLASTIC=NO on the NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk entries.

When you request the explicit method, we recommend you request the following stiffness update
options using the KUPDATE parameter on the NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk entries.

5-36 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

• When you request the explicit method and creep is the only nonlinear condition, and you have
no temperature-dependent materials, request no stiffness updates. We recommend you define the
KUPDATE=-1 option (no stiffness updates) for either SOL 401 or 402. For SOL 401 only, you can
optionally use the default KUPDATE=0 (automatic update strategy) to achieve no stiffness updates for
this case.

Note that no other nonlinearities means no large displacement or strain (PARAM,LGDISP,-1 and
PARAM,LGSTRN,0), no other nonlinear materials except creep, and no large sliding contact (DISP=1
setting on the BCTPARM bulk entry for SOL 401 or BCTPAR2 bulk entry for SOL 402).

• When you request the explicit method and creep is the only nonlinear condition, and you do have
temperature-dependent materials (TEMP(LOAD) case control and MATTi bulk entries), we recommend
the KUPDATE=-3 option. With this option, the stiffness is updated only at the first iteration of each new
time step.

External user creep materials (NUCREEP) - Integration recommendations

• When defining an external creep material, we recommend that you define the derivatives in the
NUCREEP arguments D_EFF_CR_SN(2) and D_EFF_CR_SN(5) as none zero.

Creep time step overview

The solution times you specify on the TSTEP1 bulk entry may result in time steps that are either too
coarse to produce accurate creep results, or too fine to produce creep results efficiently. Creep adaptive
time stepping is available to help avoid these problems. The software applies the creep time stepping
methods after the global equilibrium iterations and the contact iterations have converged.

• For SOL 401, you have three time stepping choices.

• The CRLIMR adaptive time stepping method (used by default).

See SOLs 401 and 402 - CRLIMR creep time stepping method.

• The TSCCR adaptive time stepping method.

See SOL 401 - TSCCR creep time stepping method.

• No adaptive time stepping method. For this case, the time steps you define on the TSTEP1 bulk
entry, the time steps resulting from the DTINIT, DTSBCDT, DTMIN, DTMAX parameters, and any
other time step bisections not specific to the creep material are used.

For SOL 401, you use the CRLIMR or the TSCCR parameter on the the NLCNTL bulk entry to select the
creep adaptive time stepping method. Their settings determine if the CRLIMR method is used, if the
TSCCR method is used, or if no creep time stepping method is used.

• By default if you do not define either the CRLIMR or the TSCCR parameter, the software uses the
CRLIMR method with CRLIMR=1.0.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-37
© 2023 Siemens
 5. Material support

• When you explicitly define both the CRLIMR and the TSCCR parameters:

If you define CRLIMR > 0.0 and any TSCCR setting, the software uses the CRLIMR method and
ignores the TSCCR setting.

If you define CRLIMR = 0.0 and TSCCR ≠ -1, the software uses the TSCCR method.

If you define CRLIMR = 0.0 and TSCCR = -1, the software does not use a creep time stepping
method.

• When you explicitly define only the CRLIMR parameter:

If you define CRLIMR > 0.0, the software uses the CRLIMR method.

If you define CRLIMR = 0.0, the software uses the TSCCR method with the TSCCR = 12 default.

• When you explicitly define only the TSCCR parameter:

If you define TSCCR ≠ -1, the software uses the TSCCR method.

If you define TSCCR = -1, the software uses the CRLIMR method using the CRLIMR = 1.0 default.

• By default, SOL 402 does not use adaptive creep time stepping.

• To request the CRLIMR method for SOL 402, define CRLIMR > 0.0 on the NLCNTL2 bulk entry.

• To request the viscous time stepping method for SOL 402, define TSCVSC=ON on the NLCNTL2 bulk
entry.

See SOL 402 - TSCVSC creep time stepping method.

SOLs 401 and 402 - CRLIMR creep time stepping method

The software uses the value defined with the CRLIMR parameter (Real ≥ 0.0) to adjust the integration
error as described below.

During the creep analysis, the software computes the integration error e as the ratio of the difference in
creep strain increment to the elastic strain.

When using the CRLIMR time stepping method (CRLIMR>0.0), the software requires that e must be less
than 0.1. That is, the difference in the creep strain increment must be less than 10% of the elastic strain.

5-38 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

The software uses the value of CRLIMR to compute r below, which is used to increase or decrease the
acceptable error.

The software also computes enu, which is the difference in the creep strain increment.

The CRLIMR time stepping method uses the values r, enu, and the parameters CRICOFF, EQMFMX,
EQMFMIN, DTMIN, DTMAX you define on the NLCNTL and NLCNTL2 bulk entries, to determine a value of
HRAT, which is used to compute the following.

The CRLIMR time stepping method is as follows:

• If enu<CRICOFF (default=1.0E-6), then HRAT=EQMFMX. This is the case when the error is very small.
The value of r is not used for this case.

• If r≤1, then the error is accepted, the time step moves forward, and HRAT=min[max[0.9/r;1.0] ;
EQMFMX].

• If r>1, then the error is rejected, the current time step is restarted, and HRAT=min[0.9/r ; EQMFMIN].

The value of Δtnext determined from the time stepping method is checked for the time step limits:

• If Δtnext<DTMIN, the analysis ends.

• Otherwise, Δtnext_actual=min[Δtnext,DTMAX]

We recommended a value of CRLIMR=1.0 when using the CRLIMR time stepping method.

SOL 401 - TSCCR creep time stepping method

For SOL 401, you use the CRLIMR and TSCCR parameters on the NLCNTL bulk entry to request the creep
time stepping method. By default if you do not define either parameter, the software uses the CRLIMR
method with CRLIMR=1.0. See Creep time step control.

You can request the TSCCR method using one of the following:

• If you explicitly define CRLIMR = 0.0 and TSCCR ≠ -1, the software uses the TSCCR method.

• If you explicitly define CRLIMR = 0.0 but do not define TSCCR, the software uses the TSCCR method
with the TSCCR=12 default.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-39
© 2023 Siemens
 5. Material support

• If you explicitly define TSCCR ≠ -1 but do not define CRLIMR, the software uses the TSCCR method.

You can tweak the TSCCR time stepping method with the following parameters on the NLCNTL bulk
entry:

Paramet
er Description
CRCERAT Ratio of maximum creep increment to elastic strain that is used to adaptively specify the next
time step.
CRCINC Maximum creep increment that is used to adaptively specify the next time step.
CRICOFF Creep strain increment below which the next time step is the product of the current time
step and the maximum time step multiplying factor.
CRINFAC Numerical integration parameter.
DTINIT Initial time step for adaptive time stepping, or the constant time step if adaptive time
stepping is overridden.
CRMFMN Minimum time step multiplying factor.
CRMFMX Maximum time step multiplying factor.
DTSBCDT Controls whether the first time step in a sequential subcase uses the initial time step or the
time step calculated at the end of the previous subcase.
CRTEABS Maximum absolute truncation error that is used to adaptively specify the next time step.
CRTECO Effective creep strain below which CRTEABS is used, and above which CRTEREL is used.
CRTEREL Maximum relative truncation error that is used to adaptively specify the next time step.
TSCCR Requests the TSCCR creep time stepping method.
DTMIN Minimum time step.
DTMAX Maximum time step.

The value you assign to the TSCCR parameter selects a specific time stepping option. See the TSCCR
parameter on the NLCNTL bulk entry for the list of these settings.

The TSCCR adaptive time stepping options include the following:

• The next time step is based on the maximum creep strain increment criterion. You specify the
maximum creep strain increment with the CRCINC parameter.

See Maximum creep strain increment criterion for TSCCR method.

• The next time step is based on the ratio of maximum creep increment to elastic strain criterion. You
specify the ratio of maximum creep increment to elastic strain with the CRCERAT parameter.

See Ratio of maximum creep increment to elastic strain criterion for TSCCR method.

5-40 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

• The next time step is based on the maximum truncation error criterion. For this option, you have three
sub-options.

See Maximum truncation error criterion for TSCCR method.

• Use the maximum absolute truncation error. You specify the maximum absolute truncation error
with the CRTEABS parameter.

• Use the maximum relative truncation error. You specify the maximum relative truncation error with
the CRTEREL parameter.

• Use the maximum absolute truncation error if the creep strain is less than the value specified by
the CRTECO parameter, and use the maximum relative truncation error if the creep strain is greater
than the value specified by the CRTECO parameter.

• The next time step is the shortest time step calculated by any combination of the maximum creep
strain increment, ratio of maximum creep increment to elastic strain, and maximum truncation error
criteria.

When the creep simulation begins, the value of the DTINIT parameter is always used as the first
time step. If you define TSCCR=0, the value of the DTINIT parameter is used as a constant time step
throughout the simulation.

When TSCCR>0, after each time step the software compares the calculated creep strain increment to the
value of the CRICOFF parameter. If the creep strain increment is greater than the value of the CRICOFF
parameter, the software uses the TSCCR adaptive time stepping to calculate the next time step. If the
creep strain increment is less than the value of the CRICOFF parameter, the software uses the product of
the current time step and the value of the CRMFMX parameter as the next time step.

If the software uses the TSCCR adaptive time stepping to calculate the next time step, the next time
step is compared to the product of the current time step and the value for the CRMFMN parameter. If
the next time step is smaller than the product of the current time step and the value for the CRMFMN
parameter, the software halves the current time step, recalculates the current creep strain increment,
and reenters the algorithm at the point the creep strain increment is compared to the value of the
CRICOFF parameter. If the next time step is larger than the product of the current time step and the
value of the CRMFMN parameter, the software keeps the next time step.

The next time step is then compared against the values of the DTMAX and DTMIN parameters. First, the
software checks to see if the value of the DTMAX parameter is 0.0. If so, the software accepts the value
for the next time step and uses it to compute the next creep strain increment. If the value of the DTMAX
parameter is not set to 0.0, the next time step is compared to the value of the DTMAX parameter. If
the next time step is larger than the value of the DTMAX parameter, the software uses the value of the
DTMAX parameter as the next time step and uses it to compute the next creep strain increment. If the
next time step is smaller than the value of the DTMAX parameter, the next time step is compared to the
value of the DTMIN parameter. If the next time step is smaller than the value for the DTMIN parameter,
the software halves the current time step, recalculates the current creep strain increment, and reenters
the algorithm at the point the creep strain increment is compared to the CRICOFF parameter. If the next

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-41
© 2023 Siemens
 5. Material support

time step is larger than the value of the DTMIN parameter, the software accepts the value for the next
time step and uses it to compute the next creep strain increment.

The TSCCR adaptive time stepping is summarized by the following flowchart.

Figure 5-4. Flowchart of TSCCR creep time stepping method

Regardless of whether you are using the adaptive time stepping or a constant time step, the solution
times you specify with the TENDi and NINCi fields on TSTEP1 bulk entries are always honored. At all

5-42 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

times during the creep simulation, if the next time step would result in skipping over a TSTEP1-defined
solution time, the software truncates the next time step so that a solve occurs at that solution time.

As a best practice, consider using the TSTEP1 bulk entry to specify only the times you want the results
output, and let the adaptive time stepping algorithm determine all the other solution times.

Maximum creep strain increment criterion for TSCCR method

With the maximum creep strain increment criterion, Simcenter Nastran calculates the next time step by
scaling the current time step as follows:

Equation 5-5.

where CRCINC is the value of the CRCINC parameter and Δεec is the current effective creep strain
increment.

Ratio of maximum creep increment to elastic strain criterion for TSCCR method

With the ratio of maximum creep increment to elastic strain criterion, Simcenter Nastran calculates the
next time step by scaling the current time as follows:

Equation 5-6.

where CRCERAT is the value of the CRCERAT parameter, Δεec is the current effective creep strain
increment, and εeE is the current total effective elastic strain.

Maximum truncation error criterion for TSCCR method

With the maximum truncation error criterion, Simcenter Nastran also calculates the next time step by
scaling the current time step. The value of the CRTECO parameter on the NLCNTL bulk entry determines
whether the maximum absolute truncation error or the maximum relative truncation error is used to
adaptively specify the next time step.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-43
© 2023 Siemens
 5. Material support

• If the effective creep strain is less than the value of the CRTECO parameter, the maximum absolute
truncation error is used. The maximum absolute truncation error is specified with the CRTEABS
parameter on the NLCNTL bulk entry.

• If the effective creep strain is greater than the value of the CRTECO parameter, the maximum
relative truncation error is used. The maximum relative truncation error is specified with the CRTEREL
parameter on the NLCNTL bulk entry.

The next time step is calculated by scaling the current time. When the maximum absolute truncation
error is applied, the software computes the next time step as:

When the maximum relative truncation error is applied, the software computes the next time step as:

where e is the calculated truncation error, and is the current effective creep strain increment. There
are two approaches to calculate the truncation error e corresponding to the two different scenarios:

1. At the first time step or if β=0 or β=1, the two point rule truncation error is used.

2. From the second time step and 0 < β< 1, the three point rule truncation error is used.

SOL 402 - TSCVSC creep time stepping method

The software considers the TSCVSC creep time stepping method after the general solution equilibrium
criteria force (PRCR), energy (PRCE), or displacements (PRCQ) are satisfied. You request and control the
viscous integration error criteria with the following three parameters on the NLCNTL2 bulk entry:

• You define TSCVSC=ON to activate the TSCVSC viscous time stepping method. The default is
TSCVSC=OFF.

• You use the parameter VSCOTE (default=0.1) to define the viscous integration error threshold.

• You use the parameter VSCOSN (default=1) to define the viscous material minimum normalization
stress σref.

The method computes a viscous integration error elocal using:

5-44 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Creep analysis

If the ratio (elocal / VSCOTE) < 1, the time step is accepted. Otherwise, it is rejected.

The time step size is a function of this ratio and the min/max equilibrium time multiplying factors
(EQMFMIN and EQMFMX).

User interface

• You define a creep material with the MATi and MVPLAS bulk entries, or with the MAT1 and MATCRP
bulk entries. The material entries must be referenced by an element property. For example, from a
PSHELL or a PSOLID entry.

All elements support a creep material except for rigid elements.

• If the properties on the MATi bulk entry are temperature-dependent, include a MATTi bulk entry with
the same material identification number.

• You can specify the coefficients for the creep laws as either constant or as a function of temperature.
To specify a coefficient as temperature-dependent, enter the identification number of a TABLEM1 bulk
entry in the corresponding L-PARi fields on the MVPLAS bulk entry, or the A, B, or D fields on the
MATCRP bulk entry. On the TABLEM1 bulk entry, enter tabular data that describes how the coefficient
varies with temperature.

• You must globally switch the creep analysis capability on with the parameter setting PARAM,MATNL,1.

• You can selectively disable creep effects in specific subcases with the CREEP parameter on the NLCNTL
bulk entry for SOL 401 or on the NLCNTL2 bulk entry for SOL 402.

The total accumulated creep strain at the end of a subcase is used as the initial creep strain for the
next creep-enabled subcase in a sequence of subcases.

• You can use the parameter TABS to convert the temperature units for creep materials. For more
information, see Converting temperature units for creep materials.

• For SOL 401, additional creep control parameters are available on the NLCNTL bulk entry. For SOL
402, creep control parameters are available on the NLCNTL2 bulk entry. These parameters allow you
to control time stepping and adjust the creep integration factor β with the parameter CRINFAC. See
Viscous Integration Scheme.

• Creep adaptive time stepping is available when the time steps you request with the TSTEP1 bulk entry
are either too coarse to produce accurate creep results, or too fine to produce creep results efficiently.
See Creep time step overview.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-45
© 2023 Siemens
 5. Material support

• The software always applies the following parameters on the NLCNTL for SOL 401 or NLCNTL2 bulk
entry for SOL 402, even when creep adaptive time stepping is not requested:

Paramet
er Description
DTINIT Initial time step in a subcase.
DTSBCDT For SOL 401 only, option to use DTINIT or not in a new subcase in a sequence. A subcase
with a zero start time always uses DTINIT.
0 (Default): Use the time step prediction at the end of the previous subcase. If the
predicted time step is zero, use DTINIT.
1: Use DTINIT.
DTMIN Minimum time increment.
DTMAX Maximum time increment.

Converting temperature units for creep materials

Temperature dependent creep material data is typically relative to the absolute temperature units
Rankine or Kelvin. You can optionally use the parameter TABS with SOLs 401 and 402 to request
that the software first convert the units of your temperature inputs before applying them to the strain
hardening, Norton, or generalized Garofalo creep laws defined on the MVPLAS or the MATCRP entry. You
can request a conversion from Fahrenheit to Rankine, or from Celsius to Kelvin.

For example, if you enter your temperature values on the TEMP and TEMPD bulk entries in Celsius, you
can define PARAM,TABS,273.16 to request for the software to convert these temperatures to Kelvin
before applying them to the creep material.

TABS only converts the temperature units before applying them to creep materials. All other
temperature-dependent material definitions use the temperatures as they are defined. For example,
the temperature values you enter on the TABLEM1 entry (referenced from the MATTi entry), or on the
TABLEST (referenced from the MATS1 entry), must be consistent with the temperatures you define on
the TEMP or TEMPD bulk entries.

In the creep equations, TABS is added to the temperature value, and to the coefficient C4. When TABS >
0.0, the exponent in the creep equations has the form:

When the parameter TABS=0.0, the exponent in the creep equations has the form:

You must define C4 if you want a temperature dependent creep material. C4 has no default, and if left
blank, the software will ignore the temperature term in the creep laws.

5-46 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

5.9 User defined materials

SOLs 401 and 402 support externally computed, user defined material models. You can define a material
model by developing and compiling an external routine. The external routine can optionally include
multiple material models.

Source code examples are included with the Simcenter Nastran installation for you to begin your
own external material development. A Ready-to-run routine and test cases are also included to
demonstrate the input file requirements and the general workflow.

You can develop an external material routine using FORTRAN or C, and compile for Windows or Linux
operating systems.

Simcenter Nastran Inputs

The MUMAT bulk entry is available to define the material data in the Simcenter Nastran input file.
Simcenter Nastran passes this data to the external routine. The MUMAT entry in your input file is the
trigger Simcenter Nastran uses to call the external routine.

You must also define the parameter setting PARAM,MATNL,1 to globally switch material nonlinear on.

An exception for SOL 401 is when MUMAT is used to define Hooke’s matrix for the initial elastic stiffness
(IOPER=3 in the NXUMAT arguments). For that linear material definition, SOL 401 uses the MUMAT
definition regardless of the PARAM, MATNL setting.

For SOL 401, all element types that support material nonlinearity can be used with a user defined
material except for composite elements. The composite elements include the solid elements CHEXA and
CPENTA that reference the PCOMPS bulk entry, and the shell elements CTRIAR, CQUADR, CTRIA6, and
CQUAD8 that reference the PCOMP, PCOMPG, or PCOMPG1 bulk entries.

For SOL 402, all element types that support material nonlinearity can be used with a user defined
material, including the composite elements. Note that, SOL 402 does not support generalized plane
strain elements and chocking elements.

The elements referencing the MUMAT entry material ID will use an associated material law defined in
the user defined material routine NXUMAT. See NXUMAT interface for the NXUMAT API description.
The elements referencing the MUMAT entry must also reference MAT1, MAT2, MAT8, MAT9, MAT11,
and MATCZ entries. Simcenter Nastran uses the MATi properties to compute the initial elastic stiffness.
Temperature dependent materials are also supported and are used by Simcenter Nastran when
computing the initial elastic stiffness. The initial elastic stiffness computed by Simcenter Nastran and
the data defined on the MATi, MATTI, and TABLEMi entries are all passed from Simcenter Nastran to the
external routine.

All of the data defined on the MUMAT bulk entry is also passed to the NXUMAT routine. You can include
a variety data types on the MUMAT entry. For example, real, integer, tables and table of tables can all be
included.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-47
© 2023 Siemens
 5. Material support

The following data is supported on the MUMAT entry:

• MODNAME1 and MODNAME2 fields - Optional character fields.

• MATNAME field - Can be used to request a specific material model.

• NUMSTAT field - Defines the total number of state variables, if they exist.

The following tabular data is supported on the MUMAT entry:

Note: When you reference TABLES1, TABLEM1, TABLEST entries on the MUMAT entry, Simcenter Nastran
does no interpolation or extrapolation of the data before passing it to the external routine.

• TABLES1 - This is a collection of real data pairs. You reference the ID of TABLES1 entries defined in
your Simcenter Nastran input file.

• TABLEM1 - This is a collection of real data pairs. You reference the ID of TABLEM1 entries defined in
your Simcenter Nastran input file.

• TABLEST - This is a collection real data values versus table ID’s. The table ID's reference other tables
with a collection of real data pairs. You reference the ID of TABLEST entries defined in your Simcenter
Nastran input file.

Simcenter Nastran also optionally stores, retrieves, and outputs state variable data computed by the
external routine. For example, stress, creep strain and plastic strain at each solution increment can be
stored as state variables. You define the number of state variables in the NUMSTAT field on the MUMAT
entry, and Simcenter Nastran will initialize the appropriate storage. The flow of state variable data is as
follows:

• Your external routine provides Simcenter Nastran with updated state variables at the end of a time
step.

• Simcenter Nastran stores the variables in the database.

• Simcenter Nastran provides the data back to the external routine at the beginning of the consecutive
time step.

You can request Simcenter Nastran to output the state variables using the STATVAR case control
command. Regardless of what the data is originally, for example, vector or tensor components,
Simcenter Nastran outputs all of the state variable data as scalar values. The GRID/GAUSS output option
is also available on the STATVAR command.

Note: SOL 402 can output a maximum of 64 state variables. If the number of state variables for output is
larger than 64, the software will output the first 64 variables, and report a warning.

You can pass parameters defined in the Simcenter Nastran input file to the external routine. This
includes parameters defined with the PARAM case control, the PARAM bulk entry, and the PLASTIC,

5-48 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

CREEP, and the MATNL parameter settings defined on the NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk
entry. You can use these settings in your external routine, for example, to turn on/off specific material
computations in a subcase.

NXUMAT interface

The subroutine NXUMAT directs Simcenter Nastran to a specific material model. A shared library (DLL/SO
file) is built from this routine and used by Simcenter Nastran to model the material behavior. The
building process of the shared library is described in Compiling instructions.

The arguments of NXUMAT are detailed below. Simcenter Nastran expects that the real, integer and
character values passed from the argument list are of precision REAL*8, INTEGER*8 and CHARACTER
(LEN=8).

SUBROUTINE NXUMAT(IOPER, MODNAME1, MODNAME2, MATID, HOOK, TANSTIFF,

MATIR, MATIN, NMATI, MUDATAR, MUDATAI, NMUDATA ,
DFGRDT0, DFGRDT1, EPSTOTT1, EPSMT1, EPSTHT1, EPSDELM,
DELTAT, TIMET1, TEMPT0, TEMPT1, NB, INTVALS,
REALVALS, XYZT1, ROT, NXPARAM, STATEVAR, NSVAR,
SIGMA, EPSPL, EPSCR, DTRATIO, VOID1, VOID2, VOID3,
IRET)

FUNCTION : USER MATERIAL DEFINITION

THIS ROUTINE IS DIVIDED IN THREE STEPS (IOPER)

IF (IOPER.EQ.0) THEN
NXUMAT DLL VERSION NUMBER
ELSEIF (IOPER.EQ.1) THEN
INITIALIZATION OF STATEVAR
ELSE
COMPUTATION OF MATERIAL LAW
ENDIF
END

Each of the arguments of the NXUMAT routine is described below.

IOPER (Input)

IOPER defines the operational step for which NXUMAT has been called for. The IOPER subroutines
(0, 1, 2, and 3) are independent of one another. You can include or not include any of the IOPER
subroutines in your MUMAT.

IOPER = 0: this is used to facilitate versioning for the NXUMAT library. This number is read from
the argument STATEVAR(1).

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-49
© 2023 Siemens
 5. Material support

For SOL 401, the following is printed to the .f06 file in the user information message 23209 along
with the value in STATEVAR(1):

*** USER INFORMATION MESSAGE 23209 (IFPDRV)

VERSION 1.00 OF NXUMAT DLL LOADED.

For SOL 402, the following is printed in the material section (1.3.1) of the .f06 file:

1.3.1. MATERIAL "MUMAT_1"

-------------------------
NASTRAN MATERIAL
Initializing user DLL MUMAT
Successfully loaded user DLL version 7.0000

IOPER=1: For SOL 401, this is used to initialize state variables. This subroutine can be used to
assign initial values to the STAEVAR array, which will be stored by Simcenter Nastran and returned
in the computational step.

SOL 402 automatically initializes the variables to 0. As a result, you cannot initialize your own state
variable values.

IOPER=2: This subroutine is considered the computational step.

For a nonlinear material, it is common to include a IOPER=2 subroutine and not include a
IOPER=3 subroutine. The IOPER=2 subroutine can compute the stress, plastic/creep strains, all state
variables, and the tangent Hooke’s matrix. In this case, Nastran retains the original Hook’s matrix
computed using the MATi / MATTi definition.

IOPER=3: This subroutine is used to compute and return the Hooke’s matrix (SOL 401 only).

For a linear elastic material, it is common to include a IOPER=3 subroutine and not include a
IOPER=2 subroutine. The Hooke’s matrix computed by NXUMAT is output and given to Nastran.
Nastran replaces the original matrix, which was computed using the MATi / MATTi definition with
the updated NXUMAT version.

Note:
IOPER = 3 is not used in SOL 402.

MODNAME1 (Input)

MODNAME1 contains the eight-character name from the MUMAT entry.

MODNAME2 (Input)

MODNAME2 contains the eight-character name from the MUMAT entry.

5-50 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

MATID (Input)

MATID is the material ID given in the MUMAT entry.

HOOK(NB,NB) (Input)

HOOK is an NBxNB-size matrix containing Hooke’s matrix. This is pre-computed by Simcenter

Nastran based on the MATi entries associated with the MUMAT entry.

TANSTIFF(NB,NB) (Input/Output)

TANSTIFF contains the tangent stiffness matrix computed at the previous time step when entering
NXUMAT and should be updated with the tangent stiffness matrix for the current time step upon
convergence.

MATIR(NMATI) (Input)

MATIR contains the real data from the associated MATi entries. Its format is explained in MATIN/
MATIR array format.

MATIN(NMATI) (Input)

MATIN contains the integer data from the associated MATi entries. Its format is explained in MATIN/
MATIR array format.

NMATI (Input)

NMATI is the size of the MATIR/MATIN array.

MUDATAR (NMUDATA) (Input)

MUDATAR contains the real data from the MUMAT entries. Its format is explained in MUDATAI/
MUDATAR array format.

MUDATAI (NMUDATA) (Input)

MUDATAI contains the integer data from the MUMAT entry. Its format is explained in MUDATAI/
MUDATAR array format.

NMUDATA (Input)

NMUDATA is the size of the MUDATAR/MUDATAI array.

DFGRDT0(3,3) (Input)

Deformation gradient at the previous time step. This is currently undefined.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-51
© 2023 Siemens
 5. Material support

DFGRDT1(3,3) (Input)

Deformation gradient at the previous time step. This is currently undefined.

EPSTOTT1(NB) (Input)

Total strain tensor (including mechanical and thermal strain).

EPSMT1(NB) (Input)

Mechanical strain.

EPSTHT1(NB) (Input)

Thermal strain.

EPSDELM(NB) (Input)

Mechanical strain increment.

DELTAT (Input)

Time step.

TIMET1 (Input)

Current time.

TEMPT0 (Input)

Temperature at the previous time step.

TEMPT1 (Input)

Temperature at the current time step.

NB (Input)

Number of tensor components.

Note:
For SOL 402, NB=6 contains all element types, including axisymmetric, plane strain, and shell
elements.

5-52 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

INTVALS(*) (Input)

The INTVALS array contains various integer data, including the following:

INTVALS(1) contains the element ID.

INTVALS(2) contains the Gauss ID.

INTVALS(3) contains the current time step number.

INTVALS(4) contains the iteration number for the current time step.

INTVALS(5) contains the subcase ID.

INTVALS(6) contains the material type such as plane strain.

INTVALS(7) contains a standard tangential matrix at the point of convergence, which is used
at the beginning of the next step for plasticity models. (SOL 401)

Note:
For SOL 402, the INTVAL(7) convergence flag does not apply because the UMAT routine is not
called after convergence.

REALVALS(*) (Input)

The REALVALS array contains various real data, including the following:

REALVALS(1) contains the element thickness for shell elements.

XYZT1(3) (Input)

XYZT1 contains the updated coordinates of the current Gauss point.

Note:
Not available for SOL 401. For SOL 402, the initial Gauss point coordinates for solid, plane
strain, and axisymmetric elements are provided.

ROT(3,3) (Input)

ROT contains the rotational matrix between the structural and material coordinate systems.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-53
© 2023 Siemens
 5. Material support

Note:
Not available for SOL 401. For SOL 402, the initial rotational matrix for only solid, plane
strain, and axisymmetric elements is provided.

NXPARAM(*) (Input)

NXPARAM contains the list of PARAM entry values that are in the input test case. You can pass
parameters defined in the Simcenter Nastran input file to the external routine. This includes
parameters defined with the PARAM case control, the PARAM bulk entry, and the PLASTIC, CREEP,
and MATNL parameter settings defined on the NLCNTL (SOL 401) or NLCNTL2 (SOL 402) bulk entry.
You can use these settings in your external routine, for example, to turn on/off specific material
computations in a subcase. Refer to the included utility routine PARAMQRY to understand how to
use this functionality.

Note:
For SOL 402, this is restricted to LGDISP, LGSTRN, K6ROT, SNORM, W3/4, ALPHA1/2, G,
MATNL, NLAYERS, NOFISR, SRCOMPS, MAXRATIO, and AFNORM.

STATEVAR(NSVAR) (Input/Output)

STATEVAR contains the state variables that you specified. It contains the previous time step state
variables as input and must be updated with current state variables upon convergence.

NSVAR (Input)

NSVAR is the number of state variables.

Note:
The UMAT developer must perform error checking with this argument if the value specified
on the MUMAT card is not consistent with the expected state variable vector length.

SIGMA(NB) (Input/Output)

SIGMA contains the stress tensor from the previous time step and must be updated with the
current time step value upon convergence.

EPSPL(NB) (Input/Output)

EPSPL contains the plastic strain tensor from the previous time step and must be updated with
current time step value upon convergence. This strain tensor is stored inside Simcenter Nastran and
is output when requested.

5-54 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

EPSCR(NB) (Input/Output)

EPSCR contains the creep strain tensor from the previous time step and must be updated with
current time step value upon convergence. This strain tensor is stored inside Simcenter Nastran and
is output when requested.

DTRATIO (Output)

DTRATIO is the next time step to the current time step ratio. It can be specified by the user from
inside NXUMAT to control the time stepping scheme. If the output of this variable is 0, it is ignored.
When DTRATIO < 0 we terminate the time step and start a new one with reduced time step.

Note:
For SOLs 401 and 402, if the material has no viscous effect, the output is 0, and this is
ignored.

VOID1, VOID2, VOID3

These are empty slots for future use.

IRET (Output)

IRET is the return code. Any returned value other than 0 (>0) will stop the solution and issue a fatal
message with the return code.

The user data specified on the MUMAT entry and corresponding MATi entry is passed to the NXUMAT
routine via the arrays MUDATAI/MUDATAR and MATIN/MATIR respectively. This section describes the
layout of the input data arrays supplied to the NXUMAT subroutine.

Each entry (that is, the MUMAT entry and the MATi* entry) is stored in two arrays each. One array has
the integer data and the other has the real data. Some cross-referencing between the two arrays must
be done to extract the desired data. The format of these arrays is described in the following sections.
These arrays are declared as INTEGER*8 for the integers and REAL*8 for the real portion.

MATIN/MATIR array format

MATi data along with corresponding MATTi entries are sent to the NXUMAT routine through two arrays:
MATIN and MATIR. Both MATIN and MATIR represent the MATi entry data in the format laid out in the
following table. The integer data of the MATi and MATTi entries exist in MATIN and the real data exist in
the MATIR array.

The first word in the array is the total number of words in the array. The second word is the offset to the
mapping array. The mapping array has information on the location of each table of data. The third word
identifies the type of the array: 1 corresponds to the MATIN array and 2 corresponds to the MUDATAI

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-55
© 2023 Siemens
 5. Material support

array. The fourth word is the material ID, and the fifth word contains the type of the MATi entry. Based
on the type of MATi entry for which this array contains data, the next ‘N’ words from the sixth word
contain the bulk entry data (N=11, 20, and 15 for the MATi entry respectively). After that, in the next
word (if any), corresponding MATTi entries are present, including its ID. If no MATTi entries are present,
this word is zero. If the MATTi entry is present, after the ID the MATTi entries are laid out next. If MATTi
entries are present, that means TABLEM1 data is present. This is laid out next in the array. Each table
has a fixed format as shown in the following table and is ended by a -1. Multiple tables can exist. The
mapping array is laid out in the end.

Word Description
1 Total length of data used in this array (LENGTH).
2 Offset to the mapping array (array index).
3 The ID code for a MATIN array is always 1.
The ID code is used by the interpolation routines to identify the data structure.
4 Material ID used to setup the array.
5 MAT table type:
1: The record contains MAT1 data.
9: The record contains MAT9 data.
11: The record contains MAT11 data.
6 Number of entries in the record (N):
If the MAT table type is 1, N = 11.
If the MAT table type is 9, N = 30.
If the MAT table type is 11, N = 15.
7 through N+6 MAT* constants (real).
N+8 MATT* ID (0 if no MATT* entry).
N+9 through 2N+8 MATT* entries (integers).
N+6 through TABLEM1 data tables (CODEX/CODEY: 0=Linear, 1=Log):
LENGTH
1. Table identification number (if 0, no table).

2. NUMPAIR: Number of X-Y Pairs.

3. CODEX: Type of interpolation for the x-axis (integer).

4. CODEY: Type of interpolation for the y-axis (integer).

5. EXTRAP: Extrapolation option.

6. X tabular value (real).

7. Y tabular value (real).

5-56 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

Word Description
- Words 6 through 7 repeated NUMPAIR.
(-1) end of TABLEM1 tables.
Mapping

1. Table ID.

2. Array index pointing to the table data.

For example, consider a MAT9 entry as show below along with a MATT9 entry and corresponding
TABLEM1 entries.

MAT9 1 1.+7 2.5+6 1.+6 0. 0. 0. 1.+7+

+ 1.+6 0. 0. 0. 3.+7 0. 0. 0.+
+ 3.75+6 0. 0. 1.75+6 0. 1.75+6 0.1 1.-5+
+ 1.-5 1.-5 1.-5 1.-5 1.-5 0.
MATT9 1 1 1+
+ 3 +
+ 1 2+
+ 2 2 2 2 2
TABLEM1 2 LINEAR LINEAR +
+ 50. 1.-5 200. 1.-5 ENDT
TABLEM1 1 LINEAR LINEAR +
+ 50. 1e+7 200. 7e+6 ENDT
TABLEM1 3 LINEAR LINEAR +
50. 3e+7 200. 1e+7 ENDT

Using the information above, these entries are formatted into the array shown below.

Integer
Description MATIN Data MATIR Real Data
1 Length MATIN(1) 104 MATIR(1) 0.000000000000000D+000
2 Offset MATIN(2) 99 MATIR(2) 0.000000000000000D+000
3 MAT* Identifier MATIN(3) 1 MATIR(3) 0.000000000000000D+000
4 MID MATIN(4) 1 MATIR(4) 0.000000000000000D+000
5 MAT* type MATIN(5) 9 MATIR(5) 0.000000000000000D+000
6 No. of MAT9 data Entries MATIN(6) 30 MATIR(6) 0.000000000000000D+000
7 MAT9 data (refer to MATIN(7) 0 MATIR(7) 10000000
MATIR)

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-57
© 2023 Siemens
 5. Material support

Integer
Description MATIN Data MATIR Real Data
8 MAT9 data (refer to MATIN(8) 0 MATIR(8) 2500000
MATIR)
9 MAT9 data (refer to MATIN(9) 0 MATIR(9) 1000000
MATIR)
10 MAT9 data (refer to MATIN(10) 0 MATIR(10) 0.000000000000000D+000
MATIR)
11 MAT9 data (refer to MATIN(11) 0 MATIR(11) 0.000000000000000D+000
MATIR)
12 MAT9 data (refer to MATIN(12) 0 MATIR(12) 0.000000000000000D+000
MATIR)
13 MAT9 data (refer to MATIN(13) 0 MATIR(13) 10000000
MATIR)
14 MAT9 data (refer to MATIN(14) 0 MATIR(14) 1000000
MATIR)
15 MAT9 data (refer to MATIN(15) 0 MATIR(15) 0.000000000000000D+000
MATIR)
16 MAT9 data (refer to MATIN(16) 0 MATIR(16) 0.000000000000000D+000
MATIR)
17 MAT9 data (refer to MATIN(17) 0 MATIR(17) 0.000000000000000D+000
MATIR)
18 MAT9 data (refer to MATIN(18) 0 MATIR(18) 30000000
MATIR)
19 MAT9 data (refer to MATIN(19) 0 MATIR(19) 0.000000000000000D+000
MATIR)
20 MAT9 data (refer to MATIN(20) 0 MATIR(20) 0.000000000000000D+000
MATIR)
21 MAT9 data (refer to MATIN(21) 0 MATIR(21) 0.000000000000000D+000
MATIR)
22 MAT9 data (refer to MATIN(22) 0 MATIR(22) 3750000
MATIR)
23 MAT9 data (refer to MATIN(23) 0 MATIR(23) 0.000000000000000D+000
MATIR)
24 MAT9 data (refer to MATIN(24) 0 MATIR(24) 0.000000000000000D+000
MATIR)
25 MAT9 data (refer to MATIN(25) 0 MATIR(25) 1750000
MATIR)
26 MAT9 data (refer to MATIN(26) 0 MATIR(26) 0.000000000000000D+000
MATIR)
27 MAT9 data (refer to MATIN(27) 0 MATIR(27) 1750000
MATIR)

5-58 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

Integer
Description MATIN Data MATIR Real Data
28 MAT9 data (refer to MATIN(28) 0 MATIR(28) 0.1
MATIR)
29 MAT9 data (refer to MATIN(29) 0 MATIR(29) 1.000000000000000D-005
MATIR)
30 MAT9 data (refer to MATIN(30) 0 MATIR(30) 1.000000000000000D-005
MATIR)
31 MAT9 data (refer to MATIN(31) 0 MATIR(31) 1.000000000000000D-005
MATIR)
32 MAT9 data (refer to MATIN(32) 0 MATIR(32) 1.000000000000000D-005
MATIR)
33 MAT9 data (refer to MATIN(33) 0 MATIR(33) 1.000000000000000D-005
MATIR)
34 MAT9 data (refer to MATIN(34) 0 MATIR(34) 1.000000000000000D-005
MATIR)
35 MAT9 data (refer to MATIN(35) 0 MATIR(35) 0.000000000000000D+000
MATIR)
36 MAT9 data (refer to MATIN(36) 0 MATIR(36) 0.000000000000000D+000
MATIR)
37 MATT9 ID MATIN(37) 1 MATIR(37) 0.000000000000000D+000
38 MATT9 entries MATIN(38) 1 MATIR(38) 0.000000000000000D+000
39 MATT9 entries MATIN(39) 0 MATIR(39) 0.000000000000000D+000
40 MATT9 entries MATIN(40) 0 MATIR(40) 0.000000000000000D+000
41 MATT9 entries MATIN(41) 0 MATIR(41) 0.000000000000000D+000
42 MATT9 entries MATIN(42) 0 MATIR(42) 0.000000000000000D+000
43 MATT9 entries MATIN(43) 0 MATIR(43) 0.000000000000000D+000
44 MATT9 entries MATIN(44) 1 MATIR(44) 0.000000000000000D+000
45 MATT9 entries MATIN(45) 0 MATIR(45) 0.000000000000000D+000
46 MATT9 entries MATIN(46) 0 MATIR(46) 0.000000000000000D+000
47 MATT9 entries MATIN(47) 0 MATIR(47) 0.000000000000000D+000
48 MATT9 entries MATIN(48) 0 MATIR(48) 0.000000000000000D+000
49 MATT9 entries MATIN(49) 3 MATIR(49) 0.000000000000000D+000
50 MATT9 entries MATIN(50) 0 MATIR(50) 0.000000000000000D+000
51 MATT9 entries MATIN(51) 0 MATIR(51) 0.000000000000000D+000
52 MATT9 entries MATIN(52) 0 MATIR(52) 0.000000000000000D+000
53 MATT9 entries MATIN(53) 1 MATIR(53) 0.000000000000000D+000
54 MATT9 entries MATIN(54) 0 MATIR(54) 0.000000000000000D+000
55 MATT9 entries MATIN(55) 0 MATIR(55) 0.000000000000000D+000
56 MATT9 entries MATIN(56) 0 MATIR(56) 0.000000000000000D+000

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-59
© 2023 Siemens
 5. Material support

Integer
Description MATIN Data MATIR Real Data
57 MATT9 entries MATIN(57) 0 MATIR(57) 0.000000000000000D+000
58 MATT9 entries MATIN(58) 0 MATIR(58) 0.000000000000000D+000
59 MATT9 entries MATIN(59) 0 MATIR(59) 0.000000000000000D+000
60 MATT9 entries MATIN(60) 2 MATIR(60) 0.000000000000000D+000
61 MATT9 entries MATIN(61) 2 MATIR(61) 0.000000000000000D+000
62 MATT9 entries MATIN(62) 2 MATIR(62) 0.000000000000000D+000
63 MATT9 entries MATIN(63) 2 MATIR(63) 0.000000000000000D+000
64 MATT9 entries MATIN(64) 2 MATIR(64) 0.000000000000000D+000
65 MATT9 entries MATIN(65) 2 MATIR(65) 0.000000000000000D+000
66 MATT9 entries MATIN(66) 0 MATIR(66) 0.000000000000000D+000
67 MATT9 entries MATIN(67) 0 MATIR(67) 0.000000000000000D+000
68 MATT9 entries MATIN(68) 0 MATIR(68) 0.000000000000000D+000
69 TABLEM1 ID MATIN(69) 1 MATIR(69) 0.000000000000000D+000
70 No. of XY data MATIN(70) 2 MATIR(70) 0.000000000000000D+000
71 CODEX MATIN(71) 0 MATIR(71) 0.000000000000000D+000
72 CODEY MATIN(72) 0 MATIR(72) 0.000000000000000D+000
73 EXTRAPOLATION option MATIN(73) 0 MATIR(73) 0.000000000000000D+000
74 X(1) MATIN(74) 0 MATIR(74) 50
75 Y(1) MATIN(75) 0 MATIR(75) 10000000
76 X(2) MATIN(76) 0 MATIR(76) 200
77 Y(2) MATIN(77) 0 MATIR(77) 7000000
78 TABLEM1 End MATIN(78) -1 MATIR(78) 0.000000000000000D+000
79 TABLEM1 ID MATIN(79) 3 MATIR(79) 0.000000000000000D+000
80 No. of XY data MATIN(80) 2 MATIR(80) 0.000000000000000D+000
81 CODEX MATIN(81) 0 MATIR(81) 0.000000000000000D+000
82 CODEY MATIN(82) 0 MATIR(82) 0.000000000000000D+000
83 EXTRAPOLATION option MATIN(83) 0 MATIR(83) 0.000000000000000D+000
84 X(1) MATIN(84) 0 MATIR(84) 50
85 Y(1) MATIN(85) 0 MATIR(85) 30000000
86 X(2) MATIN(86) 0 MATIR(86) 200
87 Y(2) MATIN(87) 0 MATIR(87) 10000000
88 TABLEM1 End MATIN(88) -1 MATIR(88) 0.000000000000000D+000
89 TABLEM1 ID MATIN(89) 2 MATIR(89) 0.000000000000000D+000
90 No. of XY data MATIN(90) 2 MATIR(90) 0.000000000000000D+000
91 CODEX MATIN(91) 0 MATIR(91) 0.000000000000000D+000
92 CODEY MATIN(92) 0 MATIR(92) 0.000000000000000D+000

5-60 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

Integer
Description MATIN Data MATIR Real Data
93 EXTRAPOLATION option MATIN(93) 0 MATIR(93) 0.000000000000000D+000
94 X(1) MATIN(94) 0 MATIR(94) 50
95 Y(1) MATIN(95) 0 MATIR(95) 1.000000000000000D-005
96 X(2) MATIN(96) 0 MATIR(96) 200
97 Y(2) MATIN(97) 0 MATIR(97) 1.000000000000000D-005
98 TABLEM1 End MATIN(98) -1 MATIR(98) 0.000000000000000D+000
99 Mapping array starts. MATIN(99) 1 MATIR(99) 0.000000000000000D+000
Table ID, offset given
below
100 Index to Table ID above MATIN(100) 69 MATIR(100) 0.000000000000000D+000
101 Table ID MATIN(101) 3 MATIR(101) 0.000000000000000D+000
102 Index to Table ID above MATIN(102) 79 MATIR(102) 0.000000000000000D+000
103 Table ID MATIN(103) 2 MATIR(103) 0.000000000000000D+000
104 Index to Table ID above MATIN(104) 89 MATIR(104) 0.000000000000000D+000

MUDATAI/MUDATAR array format

The data defined on the MUMAT bulk entry is passed to the NXUMAT routine via the MUDATAI and
MUDATAR arrays. Both MUDATAI and MUDATAR represent the MUMAT entry data in the format laid out in
the following table. The integer data of MUMAT exist in MUDATAI and the real data exist in the MUDATAR
array.

The first word in the array is the total number words in the array. The second word is the offset to
the mapping array. The mapping array has information of the location of each table of data. The third
word identifies the type of array: 1 corresponds to the MATIN array and 2 corresponds to the MUDATAI
array. The next six words are the data present on the first line of the MUMAT entry. After this, the next
word contains a code that identifies the type of data that is to follow (1 for real, 2 for integer, 3 for
TABLES1, 4 for TABLEST, 5 for TABLEM1, and 6 for a mapping array). After the code, the next word is the
size of the array for this ‘code data’ followed by the data. Note that multiple types of data can exist, so
expect multiple codes followed by their corresponding data.

After this, the table data is laid out for each TABLES1, TABLEST, and TABLEM1 on the MUMAT entry. The
format is shown in the following table.

Word Description
1 Total length of data used in this array (LENGTH).
2 Offset to the mapping array (array index).
3 The ID code for a MUDATAI array is 2 for MUMAT.
The ID code is used by the interpolation routines to identify the data structure.
4-10 First line of the MUMAT Bulk Data Entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-61
© 2023 Siemens
 5. Material support

Word Description
11 Code descriptor:
0: End of Data, or no data if the first word is 0.
1: REAL Data.
2: INTEGER Data.
3: TABLES1 Data.
4: TABLEST Data.
5: TABLEM1 Data.
6: Mapping.
Code = 1 REAL data

Size of array

2-n) Real data

Code = 2 INTEGER data

Size of array

2-n) Integer data

Code = 3 TABLES1 data

Size of array

2-n) Table IDs

Code = 4 TABLEST data

Size of array

2-n) Table IDs

Code = 5 TABLEM1 data

Size of array

2-n) Table IDs

Code = 6 Mapping

1. Size of the mapping array.

2. Table ID.

3. Table Type (code 3, 4, 5)

5-62 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

Word Description
4. Array Index pointing to the table data
TABLES1 data 1. Table identification number (if 0, no table) (integer).

2. NUMPAIR: Number of X-Y pairs.

3. X tabular value (real).

4. Y tabular value (real).

Words 3 and 4 repeated NUMPAIR.

TABLEST data 1. Table identification number (if 0, no table) (integer).

2. NUMPAIR: Number of X-Y pairs.

3. EXTRAP: Extrapolation option (0=no extrapolation, 1=extrapolation).

4. X tabular value (real).

5. TID: Table ID (integer).

Words 4 and 5 repeated NUMPAIR.

TABLEM1 data (CODEX/CODEY: 0=Linear, 1=Log)

1. Table identification number (if 0, no table) (integer).

2. NUMPAIR: Number of X-Y pairs.

3. CODEX: Type of interpolation for the X-axis (integer).

4. CODEY: Type of interpolation for the Y-axis (integer).

5. EXTRAP: Extrapolation option (0=no extrapolation, 1=extrapolation).

6. X tabular value (real).

7. Y tabular value (real).

Words 6 and 7 repeated NUMPAIR.

For example, consider the MUMAT entry below along with a TABLES1 entry.

MUMAT 1 NLPLAST
$

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-63
© 2023 Siemens
 5. Material support

+ INTEGER 1 1 2 0
$ YF HR METHOD NLTYPE
$ 2 3 4 5 6 7 8 9 10
+ REAL 0.0 9.+2
$ H/EP LIMIT1 E NU RHO A TREF
+ TABLES1 80
TABLES1 80 +
+ 0.0 0.0 7.5-4 9.+2 17.5-4 1.5+327 2.0+3 +
.5-4
+ ENDT

Using the information above, these entries are formatted into the array shown below.

Integer
Description MATIN Data MATIR Real Data
1 Length of the MUDATAI(1) 38 MUDATAR(1) 0.000000000000000D+000
array
2 Offset MUDATAI(2) 24 MUDATAR(2) 0.000000000000000D+000
3 MUMAT MUDATAI(3) 2 MUDATAR(3) 0.000000000000000D+000
identifier
4 MUMAT data MUDATAI(4) 1 MUDATAR(4) 0.000000000000000D+000
5 MUMAT data MUDATAI(5) 2.31E+18 MUDATAR(5) 0.000000000000000D+000
6 MUMAT data MUDATAI(6) 2.31E+18 MUDATAR(6) 0.000000000000000D+000
7 MUMAT data MUDATAI(7) 0 MUDATAR(7) 0.000000000000000D+000
8 MUMAT data MUDATAI(8) 0 MUDATAR(8) 0.000000000000000D+000
9 MUMAT data MUDATAI(9) 7 MUDATAR(9) 0.000000000000000D+000
10 MUMAT data MUDATAI(10) 2.31E+18 MUDATAR(10) 0.000000000000000D+000
11 Code descriptor MUDATAI(11) 1 MUDATAR(11) 0.000000000000000D+000
1 = Real data
12 Size of real data MUDATAI(12) 2 MUDATAR(12) 0.000000000000000D+000
13 Value(1) in MUDATAI(13) 0 MUDATAR(13) 0.000000000000000D+000
MUDATAR array
14 Value(2) in MUDATAI(14) 0 MUDATAR(14) 900
MUDATAR array
15 Code descriptor MUDATAI(15) 2 MUDATAR(15) 0.000000000000000D+000
2 = Integer
data
16 Size of Integer MUDATAI(16) 4 MUDATAR(16) 0.000000000000000D+000
data
17 Value(1) MUDATAI(17) 1 MUDATAR(17) 0.000000000000000D+000

5-64 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

Integer
Description MATIN Data MATIR Real Data
18 Value(2) MUDATAI(18) 1 MUDATAR(18) 0.000000000000000D+000
19 Value(3) MUDATAI(19) 2 MUDATAR(19) 0.000000000000000D+000
20 Value(4) MUDATAI(20) 0 MUDATAR(20) 0.000000000000000D+000
21 Code descriptor MUDATAI(21) 3 MUDATAR(21) 0.000000000000000D+000
3 = Tables1
data
22 Number of MUDATAI(22) 1 MUDATAR(22) 0.000000000000000D+000
Tables1
Table IDs
23 Tables1 ID MUDATAI(23) 80 MUDATAR(23) 0.000000000000000D+000
24 Code descriptor MUDATAI(24) 6 MUDATAR(24) 0.000000000000000D+000
6 = Mapping
data
25 Size of MUDATAI(25) 3 MUDATAR(25) 0.000000000000000D+000
Mapping data
26 Table ID MUDATAI(26) 80 MUDATAR(26) 0.000000000000000D+000
27 Table Type MUDATAI(27) 3 MUDATAR(27) 0.000000000000000D+000
3 = Tables1
28 Index to MUDATAI(28) 29 MUDATAR(28) 0.000000000000000D+000
Tables1 data
29 Tables1 ID MUDATAI(29) 80 MUDATAR(29) 0.000000000000000D+000
30 No. of XY pairs MUDATAI(30) 4 MUDATAR(30) 0.000000000000000D+000
31 X(1) MUDATAI(31) 0 MUDATAR(31) 0.000000000000000D+000
32 Y(1) MUDATAI(32) 0 MUDATAR(32) 0.000000000000000D+000
33 X(2) MUDATAI(33) 0 MUDATAR(33) 7.500000000000000D-004
34 Y(2) MUDATAI(34) 0 MUDATAR(34) 900
35 X(3) MUDATAI(35) 0 MUDATAR(35) 1.750000000000000D-003
36 Y(3) MUDATAI(36) 0 MUDATAR(36) 1500
37 X(4) MUDATAI(37) 0 MUDATAR(37) 2.750000000000000D-003
38 Y(4) MUDATAI(38) 0 MUDATAR(38) 2000

Source code examples

Source code examples are included with the Simcenter Nastran installation at the following locations.

• Source code written in C can be found at:

installation_location\scnas\nxumat\democ\

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-65
© 2023 Siemens
 5. Material support

• Source code written in FORTRAN can be found at:

installation_location\scnas\nxumat\demof\

Compiling instructions

The source code examples are located with the installation at the following locations.

• The FORTRAN source code and compile procedures are located at:
installation_location\scnas\nxumat\demof

• The C source code and compile procedures are located at:

installation_location\scnas\nxumat\democ

You can use any compiler as long as you adhere to the standard NXUMAT description in the provided
source code, and the compiled .dll or .so file uses one of the following handles as entry points:
NXUMAT, NXUMAT_, nxumat or nxumat_.

Template make files are provided in the democ and demof folders for both Windows and Linux operating
systems.

If you run nmake libumat.dll in the demof or democ folders on a Windows machine, a Windows
shared library (libnxumat.dll) will be produced from the FORTRAN or C code, respectively.

If you run make libumat.so in the demof or democ folders on a Linux machine, a Linux shared library
(libnxumat.so) will be produced from the FORTRAN or C code, respectively.

This assumes that you have an Intel Fortran or C compiler, and the nmake or make utility on Windows or
Linux, respectively. You will need to point to proper compilers and linkers in the makefiles to successfully
compile.

Ready-to-run routine and test cases

Compiled example routines and Simcenter Nastran input files are included with the Simcenter Nastran
installation to demonstrate the input file requirements and the general workflow.

• On Windows:
Compiled Fortran code: installation_location\scnas\em64tntl\libnxumat_demof.dll
Compiled C code: installation_location\scnas\em64tntl\libnxumat_democ.dll

• On Linux:
Compiled Fortran code: installation_location\scnas\x86_64linuxl\libnxumat_demof.so
Compiled C code: installation_location\scnas\x86_64linuxl\libnxumat_democ.so

Before using the compiled examples, you will need to follow the instructions in Specifying the user
library location to point Simcenter Nastran to a compiled example library. You can point Simcenter
Nastran to either the Fortran or the C compiled example.

5-66 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

Nine material models are included in the compiled example. You can select a specific model in your
Simcenter Nastran input file with the MODNAME1 field on the MUMAT bulk entry.

The following table summarizes the nine material models, the MODNAME1 input definition you use to
select a specific material model, and a ready-to-run Simcenter Nastran input file nxumatex*.dat for each
material model.

You can find the ready-to-run input files at:

installation_location\scnas\nxumat\demodat\

MODNAME1 Input File Description

EISO nxumatex1.dat Isotropic, temperature independent
EORTHO nxumatex2.dat Orthotropic, temperature independent
EANISO nxumatex3.dat Anisotropic, temperature independent
ETISO nxumatex4.dat Isotropic, temperature dependent
ETORTHO nxumatex5.dat Orthotropic, temperature dependent
ETANISO nxumatex6.dat Anisotropic, temperature dependent
NLPLAST nxumatex7.dat Plasticity, temperature dependent
NLCREEP nxumatex8.dat Creep, temperature dependent
PLASCR nxumatex9.dat Plasticity and creep combined, temperature dependent
CZDAMG nxumatex10.dat Damage model for cohesive elements
EHOOK nxumatex11.dat Hooke's matrix of initial stiffness for solid elements
CZEHOOK nxumatex12.dat Hooke's matrix of initial stiffness for cohesive elements

UMAT time step adjustment (SOL 401)

When you include a UMAT material with SOL 401, the time-steps are determined by the following.

• The DTINIT parameter on the NLCNTL bulk entry defines the initial time step. The DTINIT parameter
default is the minimum of either 0.01 or the subcase duration*0.01.

• You can use the TSCUMAT parameter on the NLCNTL bulk entry to activate or deactivate the UMAT
time step adjustment. It is activated by default.

When the UMAT time step adjustment is activated (TSCUMAT=ON), at each time step, NXUMAT
computes and outputs the DTRATIO argument. Nastran uses the updated DTRATIO as follows:

• When DTRATIO = 0, Nastran sets TSCUMAT to OFF and no UMAT time step adjustment occurs for
that time step.

• When DTRATIO > 0, Nastran first checks if (UMFMIN < DTRATIO < UMFMX), where UMFMIN
(Default=0.2) and UMFMX (Default=5.0) are minimum and maximum limits defined on the NLCNTL
bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-67
© 2023 Siemens
 5. Material support

If DTRATIO < UMFMIN, Nastran assigns DTRATIO = UMFMIN.

If DTRATIO > UMFMX, Nastran assigns DTRATIO = UMFMX.

Nastran computes the next time step with Δt(n+1) = DTRATIO * Δt(n).

• When DTRATIO < 0, Nastran rejects the time step and computes a new current time step: Δt(new) =
Δt(n)/2

Specifying the user library location

There are four ways, in the following order of precedence from high to low, in which you can point
Simcenter Nastran to the location of your material library.

1. You can define the keyword umatlib on the command line when running your job. For example,

nastran.exe umatlib=D:/workdir/mymaterial.dll input_file.dat

2. You can define the keyword umatlib in your RC file. For example,

umatlib=D:/workdir/mymaterial.dll

3. You can define the environment variable NXN_LOCAL_LIB_NAME. For example,

set NXN_LOCAL_LIB_NAME=D:/workdir/mymaterial.dll

4. You can replace the following files with your compiled routine:

• On Windows:
installation_location\scnas\em64tntl\libnxumat.dll

• On Linux:
installation_location\scnas\x86_64linuxl\libnxumat.so

Debugging

You can debug a .dll file using Microsoft® Visual Studio on Windows as long as you build the .dll file
with the options required for debugging. The .dll file you use for debugging can be built with the
make_dll.bat or the nmake utility.
You can use the following procedure to debug.

1. Edit a local copy of the user routine and at the desired breakpoint, add a call to the
VxWaitDebugger() function (which is defined in vxbreak.c).

vxbreak.c and makefile.dbg are located:

5-68 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined materials

• For FORTRAN source code at installation_location\scnas\nxumat\demof.

• For C source code at installation_location\scnas\nxumat\democ.

2. Run nmake /f makefile.dbg libnxumat.dll to build your debug material library.

3. Run a job using the debug material library (*.dll) file.

The software pauses the execution.

4. Open Microsoft Visual Studio.

5. Click Debug→and then click Attach to Process.

6. From the Available processes list, select analysis.exe for SOL 401 or mecano.exe for SOL 402.

The debugger stops when it detects the VxWaitDebugger function.

7. Click Debug→and then click Step Over.

8. Repeat Step 7.

This exits this function, and you can return to the user routine for debugging.

Note:
If the run is terminated prematurely from within the debugger, you must delete the temporary files
in the work directory, for example, D:\workdir. Failure to do so will cause subsequent debugging
runs to fail.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-69
© 2023 Siemens
 5. Material support

5.10 User defined creep models (SOL 401 and 402)

SOLs 401 and 402 support externally constructed, user-defined creep models. You can define a creep
model by developing and compiling an external user subroutine NUCREEP. The external routine can
optionally include multiple creep models.

Source code examples are included with the Simcenter Nastran installation for you to begin your own
external material development. Ready-to-run demo cases are also included to demonstrate the input file
requirements and the general workflow.

You can develop an external material routine using FORTRAN or C, and compile for Windows or Linux
operating systems.

All elements support user defined creep materials.

∙ 3D solids elements CTETRA, CHEXA, CPENTA, CPYRAM.

∙ Axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6.

∙ Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8.

∙ Plane strain elements that reference the generalized plane strain property (PGPLSN).

∙ Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

∙ Chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8.

∙ Shell elements CTRIA6, CQUAD8, CTRIAR, CQUADR.

Simcenter Nastran Inputs

The MUCRP bulk entry is available to define the creep coefficients in the Simcenter Nastran input file.
Simcenter Nastran passes this data to the NUCREEP routine. The MUCRP entry in your input file is the
trigger Simcenter Nastran uses to call the external routine.

You must also define the parameter setting PARAM,MATNL,1 to globally switch material nonlinear on.

You can define the MUCRP entry independently, or you can define the MVPLAS with a row that includes
"LAW" and LTYPE=USER that references the MUCRP entry. Only the combined MVPLAS and MUCRP
entries can be used to define anisotropic creep.

The elements referencing the MUCRP entry material ID will use an associated material law defined
in the user defined material routine NUCREEP. The elements referencing the MUCRP entry must also
reference general material properties defined with a MAT1, MAT9, or MAT11 entry. The elements can
also reference a plastic material defined with the MPLAS or the MATS1 entry.

5-70 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined creep models (SOL 401 and 402)

All of the data defined on the MUCRP entry is also passed to the NUCREEP interface. You can include a
variety of data types on the MUCRP entry. For example, real, integer, tables and table of tables can all be
included.

The following tabular data is supported on the MUCRP entry:

• TABLES1 - This is a collection of real data pairs. You reference the ID of TABLES1 entries defined in
your Simcenter Nastran input file.

• TABLEM1 - This is a collection of real data pairs. You reference the ID of TABLEM1 entries defined in
your Simcenter Nastran input file.

• TABLEST - This is a collection of real data values versus table IDs. The table IDs reference other tables
with a collection of real data pairs. You reference the ID of TABLEST entries defined in your Simcenter
Nastran input file.

Simcenter Nastran also optionally stores, retrieves, and outputs state variable data computed by
the external routine. For example, stress, creep strain and the time increments for each solution
increment can be stored as state variables. You define the number of state variables in the NUMSTAT
field on the MUMAT entry, and Simcenter Nastran will initialize the appropriate storage.

You can request Nastran to output the state variables using the STATVAR case control command.
Regardless of what the data is originally, for example, vector or tensor components, Simcenter Nastran
outputs all the state variable data as scalar values. The GRID/GAUSS output option is also available on the
STATVAR command.

Note: SOL 402 can output a maximum of 64 state variables. If the number of state variables for output is
larger than 64, the software will output the first 64 variables, and report a warning.

Note: When you reference TABLES1, TABLEM1, TABLEST entries on the MUCRP entry, Simcenter Nastran
does no interpolation or extrapolation of the data before passing it to the external routine.

NUCREEP interface

Simcenter Nastran will call the NUCREEP subroutine, which serves as the entry point to the user defined
creep models. You must create a shared library (DLL/SO file) from this routine, which will then be used
by Simcenter Nastran.

The arguments of NUCREEP are detailed below. Simcenter Nastran expects that the real, integer and
character values passed from the argument list are of precision REAL*8, INTEGER*8 and CHARACTER
(LEN=8).

SUBROUTINE NUCREEP(
& D_EFF_CR_SN, D_EFF_SW_SN, STATEVAR , ENG_RATE,
& EFF_CR_SN , EFF_SW_SN , PRESS_EQV, STRESS_EQV,
& TEMPER_T1 , D_TEMPER ,
& TIME_T1 , D_TIME , MOD_NAME1, MOD_NAME2,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-71
© 2023 Siemens
 5. Material support

& INTG_MTHD , INCRM_END , COORD_XYZ, NUM_SV ,

& INT_VALS , REAL_VALS , MUDATAI , MUDATAR ,
& IOPER , IRET )

D_EFF_CR_SN(5): (Output, Array)

Increment of effective creep strain, and its derivatives (derivatives needed when INTG_MTHD=1)

D_EFF_CR_SN(1): increment of effective creep strain.

D_EFF_CR_SN(2):

D_EFF_CR_SN(3):

D_EFF_CR_SN(4):

D_EFF_CR_SN(5):

D_EFF_SW_SN(5): (Output, Array) **Currently not used**

Increment of effective swelling strain, and its derivatives

STATEVAR(NUM_SV): (Input/Output, Array)

An array of state variables that you specify. It contains the state variables from the previous time step
as input and can be updated with current state variables upon convergence. The length of the array is
NUM_SV which is defined on the MUCRP entry.

ENG_RATE: (Input/Output, Real) **Currently not used**

Magnitude of strain energy rate density

EFF_CR_SN(2): (Input, Array)

Effective creep strain

EFF_CR_SN(1): effective creep strain at start of the time increment

EFF_CR_SN(2): effective creep strain at end of the time increment

EFF_SW_SN(2): (Input, Array) **Currently not used**

Effective swelling strain

5-72 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined creep models (SOL 401 and 402)

PRESS_EQV: (Input, Real)

Pressure stress

STRESS_EQV: (Input, Real)

von Mises effective stress

TEMPER_T1: (Input, Real)

Temperature at the end of the time increment

D_TEMPER: (Input, Real)

Increment of temperature

TIME_T1: (Input, Real)

Step time at the end of the time increment

D_TIME: (Input, Real)

Time increment

MOD_NAME1: (Input, Character)

User specified model name, no more than 8 characters

MOD_NAME2: (Input, Character)

User specified model name, no more than 8 characters

INTG_MTHD: (Input, Integer)

Time integration method (0: EXPLICIT, 1: IMPLICIT)

INCRM_END: (Input, Integer)

Flag indicating whether it is the start or the end of the time increment (0: start of increment, 1: end of
increment)

COORD_XYZ(3): (Input, Array)

Coordinates of the point, 3 components represent X, Y, Z, respectively

NUM_SV: (Input, Integer)

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-73
© 2023 Siemens
 5. Material support

Number of user-defined state variables

INT_VALS(*): (Input, Array)

Solution values for information (integer)

INT_VALS(1): element ID

INT_VALS(2): Gauss/grid ID

INT_VALS(3): number of step

INT_VALS(4): internal iteration count

INT_VALS(5): subcase ID

INT_VALS(6): (not used)

INT_VALS(7): convergence flag

REAL_VALS(*): (Input, Array)

Solution values for information (real)

REAL_VALS(1): element thickness

REAL_VALS(2): integration weight

REAL_VALS(3): converter to absolute temperature

MUDATAI(*): (Input, Array)

Material parameters from MUCRP card (integer)

MUDATAR(*): (Input, Array)

Material parameters from MUCRP card (real)

IOPER: (Input, Integer)

Flag of solution process step (0: loading 1: initialization 2: computation)

Only IOPER=2 is activated in this release

IRET: (Output, Integer)

5-74 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined creep models (SOL 401 and 402)

Return value for error check (0: no error)

Build instructions

Before you use the user-defined creep models defined in NUCREEP, you must build your own shared
library to create a *.dll file on Windows or an .so file on Linux. Simcenter Nastran will link to this shared
library for data exchange. You will need to have the Fortran or C compiler to compile the corresponding
source code.

There are demo input files and user subroutines located in the installation folder of Simcenter Nastran.
The locations of these files are listed below in "Demo creep models and cases." Once your makefile is
correctly defined and your compiler is configured, a shared library of user defined creep models can be
built. The table below lists the build commands and shared libraries for Windows and Linux.

Platform Build Command Shared Library

Windows nmake libucreep.dll libucreep.dll
Linux make -f makefile.unix libucreep.so libucreep.so

Utilizing SMP for internal force calculation

You can use SMP for the internal force calculation with a user-defined creep material. You first must
build your user creep material library as multithread. To do this, the makefile you use when building the
library must include the compiler options for multithread. You can use the multithread library in a serial
run or in an SMP run.

For example, in the makefile for the demo user subroutines, with the Intel Fortran compiler, the options
"auto" and "threads" are included:

On Linux:

FFLAGS=-c -fPIC -auto -threads

On Windows:

FFLAGS=/c /auto /threads

• "auto" requests all local variables to be allocated to the run-time stack.

• "threads" requests the multithread library.

You should not include debug options like "debug" when building the multithread library because they
disable the optimization capability by default. If you do need the debugging option, you can build a
single-thread library, which can be used only in a serial run. Once you've completed your debugging, we
recommend you rebuild as a multithread library and continue using with SMP.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-75
© 2023 Siemens
 5. Material support

You request SMP by defining the number of threads with the parallel keyword. Each SMP thread shares
common memory and I/O.

You can run SMP on a single machine with multiple processors and cores. SMP does not require a special
license. If you are licensed to run a solution with the serial option (that is, no parallel options), you can
run the same solution with SMP.

We recommend that you always run with SMP if your hardware has multiple physical processors. If your
hardware has the same or more physical processors than the number of threads you request with the
parallel keyword, you will not see slower performance running with SMP. In general, you should see
improved performance with SMP as compared to a serial run.

Note that if you request more threads than your physical number of processors, the run will continue but
with virtual threads. Running with virtual threads can reduce the performance.

Specifying the user creep library location

There are four ways, in the following order of precedence from high to low, in which you can point
Simcenter Nastran to the location of your user-defined creep library.

1. You can define the keyword ucrplib on the command line when running your job. For example,

nastran.exe ucrplib=D:/workdir/libucreep.dll input_file.dat

2. You can define the keyword ucrplib in your RC file. For example,

ucrplib=D:/workdir/libucreep.dll

3. You can define the environment variable NXN_UCREEP_LIB. For example,

set NXN_UCREEP_LIB=D:/workdir/libucreep.dll

4. You can replace the following files with your compiled routine:

• On Windows:
installation_location\scnas\em64tntl\libucreep.dll

• On Linux:
installation_location\scnas\x86_64linuxl\libucreep.so

Example user creep subroutines description

The example code and input files included with the installation are to demonstrate how to build a
UCREEP material model. You can reuse the code to some extent to build your UCREEP material models,
but the code paths and data usage will need to be changed accordingly.

5-76 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined creep models (SOL 401 and 402)

The following summarizes the input data usage in the example subroutines.

• Integer input:

INTEGER INTEGER INTEGER INTEGER ...

1 2 3

INTEGER1: Hardening rule used by Norton-Bailey law only (Model Name = NLCREEP1). (0: strain
hardening, 1: time hardening)

INTEGERi (i > 1): Not used

• Real input:

REAL REAL1 REAL2 REAL3 ...

REALi: Creep constitutive model coefficients.

• TABLEM1 input:

TABLEM TIDM1 TIDM2 TIDM3 ...

1

TIDMi is the table ID of temperature dependent creep constitutive model coefficients.

TIDMi corresponds to REALi. See Remark below.

• TABLES1 and TABLEST are not used in the examples.

Remark:

A table ID=0 means no table is specified, and for TABLEM1, this means no temperature dependence. For
a table ID larger than 0, a valid table ID must be input, and the table ID must belong to an existing table
bulk entry.

MUCRP input example:

The following MUCRP input example references a user creep model named "NLCREEP1". There are
4 state variables defined in this material model. There are 3 creep model coefficients, C1=3.0E-17,
C2=5.0, C3=1.06. C1 and C3 have temperature dependence, corresponding to TABLEM1 101 and 102
respectively; C2 is constant. The first INTEGER 0 is defined for a certain material parameter.

1 2 3 4 5 6 7 8 9 10
MUCRP 1 NLCREEP 4 ... +
1

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-77
© 2023 Siemens
 5. Material support

+ INTEGER 0 +
+ REAL 3.0E-17 5.0 1.06 +
+ TABLEM1 101 0 103 +

Demo creep models and cases

There are ready-to-run, pre-compiled demonstration models. The table below summarizes these models.

Note that the input files for these examples are defined for SOL 401, although you can convert most of
them by replacing "SOL 401" with "SOL 402".

No. Model Name Input File Description Formulation

1 NLCREEP1 u401c01.dat Norton-Bailey,
with temperature
dependent material
parameters
2 STRNHD1 u401sth.dat Strain Hardening

3 NORTON1 u401c01nt.dat Norton

4 GENGRF1 u401c01ga.dat Generalized

Garofalo
5 GENBLK1 u401c01bb.dat Generalized
Blackburn

The compiled example libraries are available in the Simcenter Nastran installation folder as shown
below. Note that all of the models are integrated into a single library.

• On Windows:
Compiled Fortran code: installation_location\scnas\em64tntl\libucreep_ucrpf.dll
Compiled C code: installation_location\scnas\em64tntl\libucreep_ucrpc.dll

• On Linux:
Compiled Fortran code: installation_location\scnas\x86_64linuxl\libucreep_ucrpf.so
Compiled C code: installation_location\scnas\x86_64linuxl\libucreep_ucrpc.so

Note:
When you use the pre-compiled demonstration models, you can turn off the calculation of
derivatives in the user routines by defining "NODERIV" in the MODNAME2 field on the MUCRP bulk
entry. The value of the derivatives will be zero in the output for this case. For more details, please
refer to nucreep.F in installation_location/scnas/ucreep/ucrpf or ucreep.c in installation_location/
scnas/ucreep/ucrpc.

5-78 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 User defined creep models (SOL 401 and 402)

Debugging

You can debug a .dll file using Microsoft® Visual Studio on Windows as long as you build the .dll file
with the options required for debugging. The .dll file you use for debugging can be built with the
make_dll.bat or the nmake utility.
You can use the following procedure to debug.

1. Edit a local copy of the user routine and at the desired breakpoint, add a call to the
VxWaitDebugger() function (which is defined in vxbreak.c).

vxbreak.c and makefile.dbg are located:

• For FORTRAN source code at installation_location\scnas\ucreep\ucrpf.

• For C source code at installation_location\scnas\ucreep\ucrpc.

2. Run nmake /f makefile.dbg libucreep.dll to build your debug material library.

3. Run a job using the debug material library (*.dll) file.

The software pauses the execution.

4. Open Microsoft Visual Studio.

5. Click Debug→and then click Attach to Process.

6. From the Available processes list, select analysis.exe for SOL 401 or mecano.exe for SOL 402.

The debugger stops when it detects the VxWaitDebugger function.

7. Click Debug→and then click Step Over.

8. Repeat Step 7.

This exits this function, and you can return to the user routine for debugging.

Note:
If the run is terminated prematurely from within the debugger, you must delete the temporary files
in the work directory, for example, D:\workdir. Failure to do so will cause subsequent debugging
runs to fail.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-79
© 2023 Siemens
 5. Material support

5.11 Disable plasticity and creep

The MATNL parameter allows you to switch all creep and/or plasticity effects on/off for all related
elements.

Disable plasticity and creep in SOL 401

In SOL 401, when the MATNL parameter is set to 1 (PARAM,MATNL,1) to turn on creep and/or plasticity
effects, the MATOVR bulk entry lets you optionally disable the creep and plasticity effects for the
elements of a selected GROUP bulk entry.

• Use TYPE = "ELEM" to reference a GROUP bulk entry that includes a list of elements. The MATOVR
specification applies to the listed elements.

• Use TYPE = "PROP" to reference a GROUP bulk entry that includes a list of properties. The MATOVR
specification applies to all elements that reference the properties listed in the GROUP bulk entry.

For more information, see the MATOVR bulk entry in the Simcenter Nastran Quick Reference Guide.

Disable plasticity and creep in SOL 402

In SOL 402, when the MATNL parameter is set to 1 (PARAM,MATNL,1) to turn on creep and/or plasticity
effects, you can turn them off at the subcase level. Use CREEP,NO to exclude creep effects and/or
PLASTIC,NO to exclude plastic effects.

Note:
If PARAM,MATNL is set to -1 (all material nonlinearities disabled), you cannot use the CREEP,YES or
PLASTICITY,YES in a subcase to enable creep or plasticity effects in that subcase.

Note:
Creep and plasticity effects are enabled or disabled for all the elements that can support them. You
cannot enable or disable these effects for a specific group of elements.

For more information, see the NLCNTL2 bulk entry in the Simcenter Nastran Quick Reference Guide.

5-80 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Hyperelastic materials (SOL 402)

5.12 Hyperelastic materials (SOL 402)

Hyperelastic material overview

Hyperelastic models are popular for modeling the large strain nonlinear behavior of incompressible
materials, such as rubber.

These models do not provide any special insight into material behavior. They are based on the definition
of the strain energy density as a function of on strain invariants or stretch ratios. The input of the models
are coefficients that are mainly obtained by curve-fits of test data.

You can use the MATHE bulk entry to define the following hyperelastic materials: Mooney-Rivlin, Ogden,
and Hyperfoam. You can also add viscoelasticity effects to these materials with the MATHEV bulk entry
and add Mullins effects with the MATHEM bulk entry.

You can define hyperelastic material properties as temperature dependent on the MATHE bulk entry. For
the following properties, you can enter a real value if the property is not temperature dependent, or an
integer value that references the TABLEM1 bulk entry to define the temperature dependent property.

Property Description

K Specifies a bulk modulus for the Mooney-Rivlin or Ogden material models.

Texp Coefficient of thermal expansion for all material models.

Cij Material constants related to distortional deformation for the generalized Mooney-
Rivlin material model.

Muk Coefficients μk of the strain energy function for the Ogden or hyperfoam material
models.

ALPHAk Coefficients αk of the strain energy function for the Ogden or hyperfoam material
models.

BETAk Coefficients βk of the strain energy function for the hyperfoam material model.

Mooney-Rivlin materials: the MATHE bulk entry

Mooney-Rivlin material

The generalized Mooney-Rivlin strain energy function can be expressed as follows:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-81
© 2023 Siemens
 5. Material support

with

where:

• is the deviatoric stretch ratio defined as:

• K and J are the bulk modulus and volume ratio, respectively.

If you do not provide K, the software uses a default value of 1000(C10+C01).

SOL 402 requires the linearized Poisson coefficient to be positive. The linearized Poisson coefficient Nu is
computed based on the bulk modulus K and the two first material constants C10 and C01 using:

Ogden materials: the MATHE bulk entry

For the Ogden material model, the strain energy function is:

where:

• μk and αk are material constants.

• is the deviatoric stretch ratio defined as:

• K and J are the bulk modulus and volume ratio, respectively.

K is defined as:

5-82 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Hyperelastic materials (SOL 402)

Hyperfoam materials: MATHE bulk entry

For the hyperfoam material model, the strain energy function is:

where:

• μk, αk and βk are material constants.

• J is the volume ratio.

The hyperfoam material model in SOL 402 does not use the bulk modulus K.

For more information about these hyperelastic materials, see the MATHE bulk entry in the Simcenter
Nastran Quick Reference Guide.

Almost incompressible materials

For any of the hyperelastic material models, for almost incompressible materials, if you define your
material properties such that the computed linearized Poisson coefficient Nu exceeds .495, the solution
is likely to experience convergence problems. The software will report a warning message if Nu exceeds
.495. You can reduce Nu by reducing the bulk modulus.

Nu is computed with the bulk modulus (K) and the shear modulus (G) by

See the remarks on the MATHE bulk entry in the Simcenter Nastran Quick Reference Guide.

Mooney-Rivlin alternative: MATHP bulk entry

The MATHP bulk entry is an alternative to MATHE card to define a hyperelastic material based on Mooney
model.

It allows you to define the strain potential directly by providing the Mooney coefficients or by using the
experimental data provided in the TABi parameters of the MATHP bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-83
© 2023 Siemens
 5. Material support

If experimental data are provided, the Mooney coefficients are computed internally with a fitting
procedure.

The generalized Mooney-Rivlin strain energy function can be expressed as follows:

where:

• and are the first and second distortional strain invariants, respectively.

• J=det F is the determinant of the deformation gradient.

• 2D1=K and 2(A10 + A01)=G at small strains, in which K is the bulk modulus and G is the shear modulus.

The model reduces to a Mooney-Rivlin material if NA=3.

• T is the current temperature and T0 is the initial temperature.

In SOL 402, the degree of the Mooney-Rivlin strain potential is limited to 4 for the distortional part, and
to 1 for the volumetric part.

SOL 402 requires the linearized Poisson coefficient to be positive. The linearized Poisson coefficient Nu is
computed based on the volumetric coefficient D1 and the two first distortional constants A10 and A01.

For more information, see the MATHP bulk entry in the Simcenter Nastran Quick Reference Guide.

Adding viscoelasticity effects to hyperelastic materials: MATHEV bulk entry

The viscoelastic effect in the hyperelastic material is based on Prony series.

For more information, see the MATHEV bulk entry in the Simcenter Nastran Quick Reference Guide.

Adding Mullins effects to hyperelastic materials: MATHEM bulk entry

The Mullins effect in a hyperelastic material is based on the Ogden-Roxburgh model and takes damages
in elastomers into account.

5-84 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Hyperelastic materials (SOL 402)

When material is unloaded, the stress-strain curve is below the initial curve. When material is loaded
again, it follows the unloading path.

In this example:

1. The curve from 0, to A1, to A2, to A3 is the initial loading curve without taking into account Mullins
effect.

2. When the material is loaded up to A1 and then unloaded, it follows the path from A1, to B1, to 0.
When it is loaded again up to A2, it follows the path from 0, to B1, to A1, to A2.

3. If it is unloaded and the reloaded, it follows the path from A2, to B2, to 0, to B2, to A2, to A3.

4. And so on.

For more information, see the MATHEM bulk entry in the Simcenter Nastran Quick Reference Guide.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-85
© 2023 Siemens
 5. Material support

5.13 Gasket material (SOL 402)

Gaskets create a mechanical seal between surfaces under compression preventing fluid leakage. A seal
is created when the compressive load in the gasket thickness direction exceeds the gasket initial yield
stress. The seal is maintained as long as the compressive stress stays above the threshold value. If a
gasket leaks, it maintains its load-deflection characteristics. The gasket ruptures if the compressive stress
exceeds the ultimate stress.

You model a gasket with a single layer of elements in the thickness direction using CHEXA and CPENTA
elements. The CHEXA elements must be defined with 8 grid points and the CPENTA elements must be
defined with 6 grid points.

You must define the material X-axis in the gasket thickness direction. The software does not
automatically determine the gasket thickness direction. You define the material coordinates using the
CORDM field on the PSOLID bulk entry.

Note:
For the software to include the nonlinear elastic-plastic behavior, you must define the parameter
setting PARAM,MATNL,1 to globally switch material nonlinear on.

Material properties

Because the gasket material has different properties in different directions, it is orthotopic. Although, the
directional properties are independent of one another with no coupling.

• Properties in the thickness direction (material X-axis):

The compressive properties are nonlinear elastic and nonlinear plastic. You must define the
yield pressure, a loading curve, and one or more unloading curves. The leakage pressure is set
automatically to 1% of the yield pressure.

The tensile properties are linear elastic beginning at the 1st point of an unloading curve. You define
the tension Youngs modulus in the EPL field on the MATG entry.

5-86 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Gasket material (SOL 402)

• The in-plane membrane properties define the material behavior in the material Y and Z directions. You
define the membrane properties with a MAT1 bulk entry referenced by the IDMEM field on the MATG
entry.

• The transverse shear modulus is defined by the GPL field on the MATG entry.

To define the compressive properties in the thickness direction, you define the initial yield pressure with
the YPRESS field, and you select loading and unloading curves with the TABLD and TABLU fields on the
MATG entry. These curves define a pressure versus closure strain behavior. You must define the same
number of points on the unloading curves in order for the software to properly interpolate.

The closure strain is always defined as the change in gasket thickness divided by the original gasket
thickness and is positive in compression. The gasket pressure has units of stress, and it is also positive in
compression.

The following figures demonstrates the loading and unloading curves and inputs.

Figure 5-5. Pressure-Closure Curves without Initial Gap (GAP)

You can use the GAP field on the MATG entry to define an initial closure strain. The GAP value shifts the
pressure-strain curve to the right as demonstrated in the following figure.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-87
© 2023 Siemens
 5. Material support

Figure 5-6. Pressure-Closure Curves with Initial Gap (GAP)

You can define multiple gasket materials in the definition of a single gasket model. For example, you
might define one gasket material for a beaded area and a second gasket material for a non-beaded area.

The following figure demonstrates this type of model. The blue gasket is not beaded, and the red gasket
is beaded.

Output requests

You can request gasket results with the GKRESULTS case control command. The gasket results consist of
gasket pressure, gasket closure strain, gasket yield pressure, plastic gasket closure strain, and a gasket
status integer value. For example, in the following figure, 1 is the gasket pressure , 2 is the gasket
closure strain, 3 is the gasket yield pressure, and 4 is the plastic gasket closure strain.

5-88 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Gasket material (SOL 402)

Figure 5-7. Gasket results example

The gasket status integer value output has the following meanings.

Integer value Status Definition

1 Open The gasket pressure is less than the leakage pressure.
2 Closed The gasket pressure is higher than the leakage pressure but has not yet
caused plasticity.
3 Sealed There has been plastic gasket deformation and the current pressure is
above the gasket leakage pressure.
4 Leaked After plastic deformation, the gasket pressure has dropped below gasket
leakage pressure.
5 Crushed Gasket closure strain has exceeded the rupture value.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-89
© 2023 Siemens
 5. Material support

5.14 Ply failure theories (SOL 402)

Several failure theories are available in SOL 402 to assess the degradation of the material.

The available formulas are listed below.

You select the failure theory to apply with the FT parameter of the PCOMPS (composite solid) or PCOMP/
PCOMPG/PCOMPG1 (composite shells) bulk entries.

You define the failure criterion limits in the MATFT bulk entry.

Failure index and strength ratio

For composite materials, a failure criterion can be defined with a failure index (FI) or with a strength
ratio (SR).

For example, in an uni-axial tensile situation, the prediction of failures algorithm compares the applied
tensile stress σ and the material tensile strength X:

• The failure index FI is defined as σ / X. Failure occurs once the failure index has a value of 1 or above.

• To know the strength ratio SR by which the stress σ can be multiplied to produce failure (FI = 1):

1 = (SR * σ ) / X.

Then, SR = X / σ.

A simple relationship between the failure index and the strength ratio can be computed as:

SR = 1 / FI.

You control the computation of the ply strength ratios with the PARAM,SRCOMPS parameter:

• When PARAM,SRCOMPS,YES, ply strength ratios are output for composite elements that have the
failure indices requested.

• For shell composites, when PARAM,SRCOMPS,YES, the software computes both the failure index and
the strength ratio.

• For solid composites, when PARAM,SRCOMPS,YES, the software only computes the strength ratio,and
not the failure index.

5-90 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Ply failure theories (SOL 402)

Tsai-Hill theory

where X, Y, and Z are, either the tensile or compressive strength values, depending on the sign of the σ1,
σ2, and σ3 stress components.

The software automatically makes the choice:

• σ1 >=0, X = XT.

σ1 <0, X = XC.

(with T for traction and C for compression).

• σ2 >=0, Y = YT.

σ2 <0, Y = YC.

• σ3 >=0, Z = ZT.

σ3 <0, Z = ZC.

Note:
The shear strength values R, S, and T are always positive.

Hoffman theory

In the Hoffman criterion, the same formulation is used for volume, shell, and membrane elements.

The formula only takes the in-plane stress components into account, so it is independent of the out-of-
plane stress components.

where:

• σi are stresses and τij are shear stresses.

• XT and YT are the tensile strength values.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-91
© 2023 Siemens
 5. Material support

• XC and YC are the compressive strength values.

• The shear strength value R is always positive.

Tsai-Wu theory

In the Hoffman criterion, the same formulation is used for volume, shell, and membrane elements.

The formula only takes the transverse stress components into account in shells.

where:

• σi are stresses and τij are shear stresses.

• XT, YT, and ZT are the tensile strength values.

• XC, YC, and ZC are the compressive strength values.

• The shear strength values R, S, and T are always positive.

• The F12, F23, and F13 are interactions terms.

Maximum strain theory

In the maximum total strain theory, the software compares each of the total strain tensor components
independently with their maximum allowable value.

The total strains are used, including the mechanical strains and the thermal strains.

The six components that will be tested are:

5-92 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Ply failure theories (SOL 402)

where:

• εi are strains, ɣij are shear strains.

• DTij are the limits in traction, DCij the limits in compression, and DSTij the shear limits.

Maximum stress theory

In the maximum stress theory, the software compares each of the stress tensor components
independently with their maximum allowable value.

The six components that will be tested are:

where:

• σi are stresses and τij are shear stresses.

• XT, YT, and ZT are the tensile strength values.

• XC, YC, and ZC are the compressive strength values.

• R, S, and T are the shear strength values.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 5-93
© 2023 Siemens
 5. Material support

Maximum transverse shear theory

In the maximum transverse theory, the software compares each of the transverse shear stress
components independently with their maximum allowable value.

The two shear components that will be tested are:

∣τ23∣ < S

and

∣τ13∣ < T

where the shear strength values S and T are always positive.

Ply failure criteria theories

For information, see Ply failure criteria theories in the Samcef solver documentation.

5-94 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 6. Boundary conditions
6.1 Constraints
In the Case Control section, an SPC entry is used to select a single point constraint set (s-set) which will
be applied to the structural model. The specified set identification must be identical to the SID field of an
SPC, SPC1 or SPCADD bulk entry. Notice that SPCADD entries take precedence over SPC or SPC1 entries.
If both have the same SID, only the SPCADD entry will be used.

A significant application of SPC is the imposition of boundary conditions. The PS field in the GRID entry is
also able to specify single-point constraints associated with a grid point. Although, these constraints are
so-called permanent constraints which can not be changed during the analysis. An advantage of using
SPC to specify boundary conditions is that these boundary conditions can be changed from subcase to
subcase by selecting a different SPC set inside each subcase.

SPC input summary

• The SPC=n case control command selects either the SPC, SPC1, or SPCADD bulk entry.

The SPC condition can change between subcases.

The SPC entry can optionally be used to define a time-unassigned enforced displacement. It cannot
be defined as time-assigned. That is, it cannot be selected with the EXCITEID on the TLOAD1 entry.
For a time-assigned enforced displacement, you can use the SPCD entry. See Mechanical Loads for
information on the SPCD entry.

The SPCFORCES case control command is supported to request the SPC force output.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 6-1
© 2023 Siemens
 6. Boundary conditions

6.2 Multipoint constraint

While a single point constraint (SPC) is used to constrain the motion of a degree-of-freedom, a
multipoint constraint (MPC) is used to tie the motion of one degree-of-freedom to other degrees-of-
freedom. The MPC command in the Case Control section is used to select a multipoint constraint set in
the Bulk Data. The specified MPC set identification must appear at least in one MPC or MPCADD bulk
entry. Each MPC bulk entry may be used to define a constraint equation involving a group of degrees-of-
freedom in which the first degree-of-freedom is assumed to be the dependent degree-of-freedom and
included in the m-set. All the degree-of-freedom in m-set will be condensed out prior to the matrix
operations. Their response will be directly recovered from those of the independent degrees-of-freedom
according to the specified constraint equation.

The software allows you to change MPC conditions from subcase to subcase. However, you should avoid
changing MPC conditions between modes subcases because the software does not perform a set of
iterations to recompute the correct stiffness for the new MPC conditions. Thus, the modal results may
not be accurate for the new MPC conditions.

MPC input summary

• The MPC=n case control command selects either the MPC or MPCADD bulk entry.

• MPC conditions can change between subcases.

• MPC conditions do not update for large displacements (PARAM,LGDISP,1).

6-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Enforced displacements

6.3 Enforced displacements

Enforced displacements may be specified in the Bulk Data section using SPC or SPCD entries. An SPC
can be used to define time-unassigned enforced displacements. An SPCD can be used to define time-
assigned or time-unassigned enforced displacements. See Boundary conditions and Mechanical Loads
for input details.

Each SPC entry may define enforced displacements for up to two grid or scalar points. Several SPC
entries which reference the same SID may be used if enforced displacements for more than two grid or
scalar points are desired. The only disadvantage of this method is that the entire s-set must be redefined
if the enforced displacement conditions vary among subcases.

If a time-assigned or time-unassigned enforced displacement condition is defined with the SPCD entry, a
constraint must also be defined with the SPC entry on the same DOF referenced by the SPCD entry.

If multiple enforced displacement conditions are applied to the same DOF, the software uses the
following precedence.

• A time-assigned enforced displacement defined with the SPCD entry, which is referenced by the
EXCITEID on the TLOAD1 entry, will overwrite time-unassigned enforced displacements defined with
the SPCD or SPC entries.

• A time-unassigned enforced displacement defined with the SPCD entry, which is referenced by the
LOAD=n case control command, will overwrite a time-unassigned enforced displacement defined with
the SPC entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 6-3
© 2023 Siemens
 6. Boundary conditions

6.4 Cyclic symmetric boundary condition

The cyclic solution method takes advantage of cyclic symmetry to reduce the time needed to create
and solve a full 360 degree model. To use this method, you create a 3D-solid element model that
represents a fundamental segment. The fundamental segment represents a structure that is made up of
N repetitions, where each repetition can be obtained by rotating the fundamental segment an angle that
is an integer multiple of 2π/N.

An important feature is that the software will couple the translational DOF on the symmetry faces. The
CYCSET case control command, which selects the CYCSET bulk entry, or multiple CYCSET entries with the
CYCADD bulk entry, defines the coupling. The coupling definition must be defined globally. As a result,
the MPC equations created by the software are applied in every subcase.

To define the coupling, you select the cyclic source and target regions on the CYCSET bulk entry. A
very useful feature of the coupling definition is that the mesh on the source and target regions can be
dissimilar. In addition, features such as holes in one or both of the symmetry faces are also permitted.
The software internally computes the correct coupling conditions between the grids on the source and
target faces.

The CYCAXIS bulk entry is also required to define the default cylindrical coordinate system for the
coupling. The origin of this cylindrical system must be at the center of the revolution, and the Z-axis
must be consistent with the axial direction.

Coupling details

• The symmetry faces are grouped into source and target regions. To do the coupling, Simcenter
Nastran internally rotates the target region grids into the source region grids, it does a mesh
refinement on both the source and target, and then creates MPC equations using the target as the
dependent DOF and the source as the independent DOF. The MPC equations are created between any
source and target region grids within the user defined search distance (SDISTi) using a weighted area
method.

• The mesh on the source and target regions can be dissimilar. Features such as holes in one or both of
the symmetry faces are also permitted.

• It is recommended that the source and target faces have similar geometry. If the source and target
geometry is different, the software will still couple the appropriate source and target grids, although,
the solution accuracy will be compromised.

• You must define the coupling globally. The resulting MPC equations are included in all subcases.

Coupling input summary

• The CYCAXIS bulk entry is required to define the default cylindrical coordinate system for the coupling.
The origin of this cylindrical system must be at the center of the revolution, and the Z-axis must be
consistent with the axial direction.

6-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cyclic symmetric boundary condition

• The Z-axis of every cylindrical coordinate system referenced by the CYCSET entry must have the same
origin and direction as the z-axis of the default coordinate system selected with the CYCAXIS bulk
entry.

• The displacement coordinate system of grid points which are defined on the rotation axis must have
a Cartesian displacement coordinate system. For all other grid points, a cylindrical displacement
coordinate system is recommended. See Rules for source and target DOF.

• The CYCSET case control selects the CYCSET or CYCSADD bulk entries. The CYCSET case control must
be defined above the subcase level. As a result, the MPCs generated by the automatic coupling are
used in every subcase (cyclic modes, static, dynamics, preload, and normal modes).

• The BSURFS and BCPROPS bulk entries define the regions. These are existing inputs used to define glue
and contact regions.

• The CYCSET bulk entry pairs the source and target face regions.

• The source region selected in a pair must have a smaller positive theta location than the target
region.

• The software will use the number of segments (NSEG) field to compute the angle between the
source and target faces. For example, if a 30 degree segment is modeled, NSEG would be 12 =
(360/30).

• For SOL 401, if you are modeling multiple cyclic sectors (stages), each with a different number
of segments (NSEG), you must use the STAGE field to define a unique identification number (ID)
for each stage. All cyclic sectors having the same stage ID must also have the same NSEG value.
CYCSET bulk entries that do not identify a stage ID must all have the same NSEG value.

SOL 401 supports multiple stages and different sectors (NSEG) with the static, preload, dynamic
and modal subcases. The cyclic modes subcase does not support multiple stages, and requires that
all CYCSET entries have the same number of sectors (NSEG).

• The SDIST field is used to pair source and target grids when creating the MPC equations. From
each source grid, the search occurs in both the positive and negative theta DOF directions. If the
SDIST field is undefined, the software will automatically compute the search distance. The software
computed value is reported in the f06 file.

• For SOL 402, you can optionally select all of the elements included in the portion of your model
where you would like the cyclic coupling created. The software will automatically determine the
symmetry faces, and it will create the cyclic coupling. For example, if you are modeling stages of a
turbine engine, you would select all elements representing a single engine stage.

On the CYCSET entry, you use the STAGE field to define the stage number, and the GROUPID field
to select the GROUP bulk entry that lists all the elements in a stage. When you use these fields,
you leave the region selection fields SIDi and TIDi undefined because the software determines the
source and target element faces automatically.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 6-5
© 2023 Siemens
 6. Boundary conditions

• For SOL 401, the CYPARTOL field is available on the CYCSET bulk entry to adjust the parametric
coordinate tolerance.

To do the automatic coupling, the software first internally rotates the target region into the source
region by the segment angle. The software creates MPC equations between the source and target
region nodes if the following conditions are satisfied:

■ The distance from a rotated target node to the source faces in the theta direction must be
less than the specified search distance (SDISTi). For example, if you define NSEG=12, but your
segment angle is actually 31 degrees, there would still be a 1 degree separation between the
rotated target and the source. If the separation is larger than SDISTi, the software will not create
the coupling.

■ The software creates a parametric coordinate frame on each source element face where the
element corners are bounded by the coordinates -1.0 to +1.0. It projects each target node to a
source element to compute the parametric coordinates for the projected location. The software
includes a 0.005 tolerance, by default, in case the projected location is slightly outside of the
source element face. As a result, each projected target node must have a parametric coordinate
within -1.005 or +1.005, or the node is not coupled. The nodes that fail to project to an element
face will always be on the mesh boundary.

The software prints the following in the .f06 file showing the total number of target nodes and the
number of target nodes that were paired.

*** USER INFORMATION MESSAGE 23230 (WRTGEOM4CYC)

NUMBER OF NODES ON CYLIC TARGET FACE - 10130
NUMBER OF NODES ON CYCLIC TARGET FACE PAIRED WITH NODES ON CYCLIC
SOURCE FACE - 10128
NUMBER OF CYCLIC MPC CONDITIONS FORMED FOR STATICS/HARMONIC=0
SOLUTION - 30384

If you see a difference in the total number and the number paired in this output, you can consider
increasing the parametric tolerance in the CYPARTOL field.

• The CYCADD bulk entry can optionally be used to combine multiple CYCSET bulk entries.

• The CYCFORCES case control command optionally requests the MPC force output for the grids which
are included in the automatic coupling. It can be defined above the subcases (globally) or in a
subcase.

SOL 401 - Combination axisymmetric and 3D cyclic sector models

The axisymmetric element formulation represents the mass and stiffness of a fully revolved (2π)
geometry, but the cyclic sector only represents a 1/N section of the geometry. As a result, the mass,
stiffness, and loading are not consistent between these two portions of the model. When SOL 401
determines that a combination of axisymmetric elements and 3D cyclic sectors exists, it automatically
scales the appropriate material properties and loads on the cyclic sectors. See SOL 401 - Material and
load scaling for 2D/3D models.

6-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cyclic symmetric boundary condition

SOL 401 supports the combination of 2D axisymmetric elements and 3D cyclic sectors in the statics,
dynamics, and preload subcases, but not in the cyclic modes or Fourier modes subcases. If your model
includes a combination of 2D axisymmetric elements and 3D cyclic sectors, and you have included either
the cyclic modes or Fourier modes subcases, the solution will end with a fatal error.

SOL 402 - Fourier axisymmetric elements and 2D-3D coupling

SOL 402 supports Fourier axisymmetric elements, and an automatic 2D-3D coupling to connect a
Fourier axisymmetric mesh to a 3D solid element mesh. See SOL 402 - 2D Fourier axisymmetric and
2D/3D coupling.

Cyclic modes subcase

A cyclic modes subcase is available and designated with ANALYSIS=CYCMODES in the subcase. The cyclic
modes formulation includes the harmonic index, k, which represents an additional dimension of the
vector space that is not present in an "ordinary" modal analysis. See Cyclic modes subcase.

Note:
For SOL 401, an output coordinate system exception exists for the cyclic modes subcase. For
the solid elements that represent a cyclic symmetry fundamental segment, stress and strain are
output in the cylindrical coordinate system selected on the CYCAXIS bulk entry. This exception only
applies to the stress and strain output from the cyclic modes subcase. Stress and strain output for
a cyclic symmetry fundamental segment from all other subcase types is in the material coordinate
system.

SOLs 401 and 402 - Rules for source and target DOF

• If you define SPC conditions on target region DOF with the SPC, SPC1, or SPCD entries, the software
reports a warning message that it is ignoring the SPC conditions on the target region DOF, and the
solution continues.

• If you include a target region DOF on an RBE2, RBAR, or RBE3 element as a dependent DOF, the
software reports a warning message that it is ignoring the rigid connections on the target region DOF,
and the solution continues.

• For SOL 402, if you include a source region DOF on an MPC bulk entry as a dependent DOF, the
solution ends with a fatal error. SOL 401 allows this condition.

If you include a target region DOF on an MPC bulk entry as a dependent DOF, both SOLs 401 and 402
always end with a fatal error.

• Grid points which are defined on the Z-axis of the default cylindrical coordinate system must have a
Cartesian displacement coordinate system. For the grid points which are defined on the Z-axis and
are included in a source or target region, Simcenter Nastran automatically applies the following SPC
conditions during the solution. An exception is if you have already applied a boundary condition on
these grid points. In that case, the software will honor your conditions.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 6-7
© 2023 Siemens
 6. Boundary conditions

• In the cyclic modes subcase for the harmonic index k=0, and in the statics, preload, dynamics and
normal modes subcases, Simcenter Nastran fixes DOF 1, 2.

• In the cyclic modes subcase for the harmonic index k=1, Simcenter Nastran fixes DOF 3.

• In the cyclic modes subcase for all other harmonic index values, Simcenter Nastran fixes all six DOF.

SOL 401 - Subcase support of the cyclic symmetric boundary condition

For 3D cyclic sector only models (no 2D axisymmetric elements), the cyclic modes, static, preload,
dynamic, modal frequency response, and modal subcases are supported.

For the combined 2D axisymmetric and 3D cyclic sector models including the material and load scaling
for 2D/3D models, the static, preload, dynamic and modal subcases are supported. The cyclic modes
subcase is not supported for the combined model.

The static, preload, dynamic and modal subcases use the MPC equations automatically created by the
cyclic symmetric boundary condition, but the displacements are not cyclic. That is, the displacements
only represent the 0th harmonic, n=1 fundamental sector. Only the cyclic modes solution supports the
harmonic analysis.

Multiple cyclic sectors (stages) with a different number of sectors (NSEG) is only supported by the static,
preload, dynamic and modal subcases. The cyclic modes subcase does not support this.

The cyclic symmetry condition is not supported in the Fourier subcase.

SOL 402 - Subcase support of the cyclic symmetric boundary condition

For both the 3D cyclic sector only models (no 2D axisymmetric elements) and the combined
axisymmetric and 3D cyclic sector models, the cyclic, static, preload, dynamic and modal subcases are
supported.

The static, preload, dynamic and modal subcases use the MPC equations automatically created by the
cyclic symmetric boundary condition, but the displacements are not cyclic. That is, the displacements on
the 3D element grid points only represent the 0th harmonic, n=1 fundamental sector.

Multiple cyclic sectors (stages) with a different number of sectors (NSEG) is supported by the cyclic,
static, preload, dynamic and modal subcases.

SOL 402 - Cyclic symmetry regions and coincident grid points

If you define a single cyclic symmetry region that intersects a contact interface, any coincident grid
points at the contact interface can cause unpredictable cyclic symmetry coupling. As a result, the
software issues a fatal error if it finds any coincident grid points in a cyclic symmetry region. The
following image includes a contact interface , and an example cyclic symmetry definition that
would cause the fatal error. Notice that the cyclic symmetry region in this example spans both sides of
the contact definition.

6-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Cyclic symmetric boundary condition

To avoid the error, you should split your cyclic symmetry definition like the image below; one CYCSET
definition on one side of the contact interface , and another CYCSET definition on the other side of
the contact interface .

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 6-9
© 2023 Siemens
 6. Boundary conditions

6.5 SOL 402 - Redundant constraints

When grid points are included in a combination of any of these conditions: MPC, contact, glue, cyclic
symmetry conditions, their degree-of-freedom become over-constrained since they are dependent on
multiple conditions. This can occur, for example, on the edges between contact, glue, and cyclic
symmetry conditions.

By default, the software leaves one of the dependencies but zeros the others. Sometimes the issue is
revealed by zero pivot messages, but not always.

The software writes the pivot messages to the .f06 file as shown below.

Regardless of whether the software reports zero pivots, the issue is revealed in the redundant Lagrange
multiplier listing in the .f06 file as shown below.

Note that CONT in the above listing refers to a contact element, and MAPP refers to a node-to-face
glue element. A contact set (BCTSET) produces a CONT. A glue set (BGSET) and a cyclic symmetry set
(CYCSET) produce a MAPP. The contact and glue element numbers in the listing are internally generated
by the software.

If you encounter convergence problems as a result of the overly constrained DOF, you have the following
options. In general, if you receive messages regarding zero pivots, you should try to eliminate them.

6-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Redundant constraints

• If you receive zero pivot messages resulting from contact and cyclic symmetry, you can define a
normal contact stiffness with the NCMOD= -2.0 setting on the BCTPAR2 bulk entry. After you define
the normal stiffness, the related pivots should be eliminated.

• You can define the parameter setting NSTK=1 on the NLCNLG bulk entry and the software will replace
the redundant conditions with diagonal stiffness terms in the tangent matrix. The result is similar
to replacing the hard constraints with spring elements. The software no longer sees the multiple
conditions as a conflict and the Lagrange multipliers can remain without the need of setting them to
0.0.

• You can remove the element faces from the cyclic symmetry definition that have grid points in
common between the glue or contact set and the cyclic symmetry definitions.

The image below shows the element faces that must be removed from the cyclic symmetry definition
for this example.

In general, if your solution runs to completion and converges, you can ignore the redundant Lagrange
multiplier messages in the .f06 file.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 6-11
© 2023 Siemens
 6. Boundary conditions

6-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 7. Loads
7.1 Loads overview
The solution strategy in nonlinear is to apply the loads in an incremental fashion until the desired load
level is reached. The algorithms remember the loads from one subcase to the next.

The methods employed to define loads in SOL 401 and SOL 402 are similar to those used in a time
history solutions. A single degree-of-freedom or a set of GRID points may be loaded with force pattern
that varies with time. Functions may be tabular such as an earthquake or a booster liftoff, or they may be
simple analytic functions such as a sine wave. Simple static load sets may be used to create the dynamic
loads. They may be scaled and combined with other loads to simulate complex loading problems.

Time history loads define the loadings as functions of time and the location. They can be a load applied
at a particular degree-of-freedom, pressure over the surface area, or the body force simulating an
acceleration. The time history is provided by TLOADi bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-1
© 2023 Siemens
 7. Loads

7.2 Mechanical loads (SOL 401)

Mechanical loads can be defined in SOL 401 as time-assigned or time-unassigned. Time is used in a
statics subcase as the mechanism to increment loads. Time is used explicitly in a dynamics subcase.
Time-assigned and time-unassigned loads can be combined in the same statics or dynamics subcase.

• Load selection in Case Control:

• Time-unassigned loads are selected with the LOAD case control command,

LOAD=n

where n points to a DAREA, FORCDST, FORCE, FORCE1, FORCE2, GRAV, MOMENT, MOMENT1,
MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, PLOADE1, PLOADFP, PLOADX1, RFORCE, RFORCE1,
SLOAD, SPCD, or LOADSET entry.

The LVAR parameter on the NLCNTL bulk entry controls if time-unassigned mechanical loads are
ramped (default), or not ramped for each subcase. The ramping helps convergence by reducing the
load increments. You can optionally turn the ramping off by setting LVAR=STEP on the NLCNTL bulk
entry.

• Time-assigned loads are selected with the DLOAD case control command,

DLOAD=n

where n points to a load set defined by a TLOAD1 bulk entry, or a DLOAD bulk entry if you want to
combine multiple TLOAD1 entries into a single load set.

• Time-assigned load definition in Bulk Data:

• TLOAD1 or TLOAD3 - Defines time-assigned loads.

TLOAD1 is used to define most time-assigned loads. See Defining the TLOAD1 entry below. The
exception is the distributed force defined with the FORCDST bulk entry.

TLOAD3 is only used to select the FORCDST bulk entry to define a time-assigned distributed force.
See Distributed force to a surface or edge.

• TABLEDi (i=1,2,3,4) - Table that defines the load variation with time.

• DLOAD - Combines several TLOAD1 and TLOAD3 entries.

• Defining the TLOAD1 entry:

• The EXCITEID field on the TLOAD1 entry selects the static load set IDs.

7-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Mechanical loads (SOL 401)

• The supported static load inputs are the DAREA, FORCE, FORCE1, FORCE2, GRAV, MOMENT,
MOMENT1, MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, PLOADE1, PLOADX1, RFORCE, RFORCE1,
SLOAD, and SPCD bulk entries.

• The TYPE field on the TLOAD1 entry should be “0” for all load inputs selected by the EXCITEID field,
except for the SPCD entry. The SPCD entry requires “1” in the TYPE field.

• A real value is supported in the DELAY field on a TLOAD1 entry to optionally shift the time steps
used to compute the associated loads.

• A temperature load cannot be selected on the EXCITEID field. See Thermal Loads.

• The TID field selects a TABLEDi, which defines a load scaling versus time function.

• The figure below demonstrates how the DLOAD, TLOAD1, FORCE (for example), and TABLEDi bulk
entries relate to one another.

• Load Input Example 1:

When there is more than one time-assigned load set, the DLOAD bulk entry is required:

$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345
678
$
$ DLOAD COMBINES MULTIPLE TLOAD1 (102 AND 105)
DLOAD 17 1. 1. 102 1. 105
$
$ TIME-ASSIGNED FORCE, EXCITEID=125, TYPE=0 (DEFAULT), TIME FUNCTION TID=13
TLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
$
$ TIME FUNCTION 13 USED FOR FORCE LOAD
TABLED2 13
0. +

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-3
© 2023 Siemens
 7. Loads

+ 0. 0. 1. 100. 2. 0. ENDT
$
$ TIME-ASSIGNED FORCE EXCITEID=3, TYPE=0 (DEFAULT), TIME FUNCTION TID=12
TLOAD1 105 3 12
$
FORCE 3 73 0 2. 8. 0. 0.
$
$ TIME FUNCTION 12 USED FOR FORCE LOAD
TABLED2 12
0. +
+ 0. 0. 2. 1. ENDT

• Load Input Example 2:

When there is only one time-assigned load set, the DLOAD entry is not required:

$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345
678
$
$ TIME-ASSIGNED FORCE, EXCITEID=125, TYPE=0 (DEFAULT), TIME FUNCTION TID=13
TLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
PLOAD 125 100.0 21 30 18 10
PLOAD 125 100.0 10 18 22 25
$
$ TIME FUNCTION 13 USED FOR LOAD
TABLED2 13
0. +
+ 0. 0. 1. 100. 2. 0. ENDT
$

• Additional Information about mechanical loads:

• Enforced displacements may be specified using SPC or SPCD entries. See Enforced displacements.

• Loads in any subcase are total loads as opposed to incremental loads from the previous subcase. In
other words, the ending load from a previous subcase does not become the initial loading for the
consecutive subcase.

• If no load is applied in a subcase, the total load is zero.

• LOAD=n or DLOAD=n defined at the global level is used in all statics subcases unless a different
LOAD=n or DLOAD=n is defined in a subcase.

• If a time-assigned and time-unassigned enforced displacement condition is defined with the SPCD
entry, a constraint must also be defined with the SPC entry on the same DOF referenced by the
SPCD entry.

7-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Mechanical loads (SOL 401)

• The TSTEP1 bulk entry defines the time step intervals in which a solution will be generated and
output in a static subcase. If your time steps defined by the TSTEP1 entry exceed the time values
defined in your TABLEDi entry, by default, the software will extrapolate the data defined in the
TABLEDi entry. The software will issue a warning if extrapolation occurs. If you do not want the
software to extrapolate the data, you can enter “1” in the EXTRAP field on the TABLEDi entry.

• The LOADOFF parameter is available on the NLCNTL bulk entry to turn ON or OFF categories of
mechanical loads. The NLCNTL entry can be defined in the global subcase level and in individual
subcases.

The LOADOFF options are as follows.

LOADOFF value Result

LOADOFF=NONE No loads are turned off.
(Default)
LOADOFF=BODY Turns off body loads defined with the GRAV, RFORCE, RFORCE1, ACCEL,
and ACCEL1 bulk entries.
LOADOFF=BOUNDRY Turns off boundary loads defined with the PLOAD, PLOAD1, PLOAD2,
PLOAD4, PLOADE1, PLOADX1, FORCDST, FORCE, FORCE1, FORCE2,
MOMENT, MOMENT1, MOMENT2, and SLOAD bulk entries.
LOADOFF=BOTH Turns off both the BODY and BOUNDRY loads listed above.
When LOADOFF=BOTH is defined, the loads which remain on include
temperature loads, initial stress/strain, strains computed from a bolt
preload subcase, enforced displacements, and loads as a result of
contact conditions.

Note:
When running SOL 401 in a Simcenter thermal-structural multiphysics analysis, some
mechanical loads such as RFORCE1 are used by both the structural and thermal solutions. It's
important to understand that the LOADOFF parameter is only turning loads on or off for the
Simcenter Nastran structural solution, and not the thermal solution. In addition, the thermal
solution can compute pressure loads which are then applied in the structural solution. These
pressure loads are applied using the PLOADi entries, and as a result, they will be turned off
from the structural solution when LOADOFF=BOUNDRY is defined.

• When you define the RFORCE or RFORCE1 bulk entries as either time-assigned, or as time-
unassigned and ramped, the software uses time to scale the angular velocity and acceleration ,
which are used to compute the inertia force. You can use the RFVAR parameter to change how the
software interpolates the time variation. See SOL 401 - Interpolating rotational inertia loads.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-5
© 2023 Siemens
 7. Loads

7.3 Mechanical loads (SOL 402)

Mechanical loads can be defined in SOL 402 as time-assigned or time-unassigned. Time is used in a
statics subcase as the mechanism to increment loads. Time is used explicitly in a dynamics subcase.
Time-assigned and time-unassigned loads can be combined.

• Load selection in Case Control:

• Time-unassigned loads are selected with the LOAD case control command:

LOAD=n

where n points to FORCE, FORCE1, FORCE2, GRAV, MOMENT, MOMENT1, MOMENT2, PLOAD,
PLOAD1, PLOAD2, PLOAD4, PLOADE1, PLOADFP, PLOADX1, RFORCE, RFORCE1, or SPCD entry.

Beginning with Simcenter Nastran 2021.2, the time-unassigned loads are always ramped. Ramping
helps convergence by reducing the load increments. A fatal error occurs now if LVAR=STEP is
defined on the NLCNTL2 entry. You can use the system cell setting NASTRAN SYSTEM(767)= 0 to
turn off the fatal error and revert to the previous behavior.

• Time-assigned loads are selected with the DLOAD case control command:

DLOAD=n

where n points to a load set defined by a TLOAD1 bulk entry, or a DLOAD bulk entry if you want to
combine multiple TLOAD1 entries into a single load set.

Beginning with Simcenter Nastran 2021.2, you must define the time-assigned loads globally (above
all subcases). A fatal error now occurs if you define the DLOAD command in a subcase. You can
use the system cell setting NASTRAN SYSTEM(767)= 0 to turn off the fatal error and revert to the
previous behavior.

• Time-assigned load definition in Bulk Data:

• TLOAD1 - Defines time-assigned loads.

TLOAD1 is used to define most time-assigned loads. See Defining the TLOAD1 entry below.

• TABLEDi (i=1,2,3,4) - Table that defines the load variation with time.

• DLOAD - Combines several TLOAD1 entries.

• Defining the TLOAD1 entry:

• The EXCITEID field on the TLOAD1 entry selects the load set IDs.

7-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Mechanical loads (SOL 402)

• The supported static load inputs are the FORCE, FORCE1, FORCE2, GRAV, MOMENT, MOMENT1,
MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, PLOADE1, PLOADX1, RFORCE, RFORCE1, and SPCD
bulk entries.

• The TYPE field on the TLOAD1 entry should be “0” for all load inputs selected by the EXCITEID field,
except for the SPCD entry. The SPCD entry requires “1” in the TYPE field.

• The DELAY field on a TLOAD1 entry is ignored.

• A temperature load cannot be selected on the EXCITEID field. See Thermal Loads.

• The TID field selects a TABLEDi, which defines a load scaling versus time function.

• The figure below demonstrates how the DLOAD, TLOAD1, FORCE (for example), and TABLEDi bulk
entries relate to one another.

• Example 1 - Load Input

When there is more than one time-assigned load set, the DLOAD bulk entry is required:

$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345
678
$
$ DLOAD COMBINES MULTIPLE TLOAD1 (102 AND 105)
DLOAD 17 1. 1. 102 1. 105
$
$ TIME-ASSIGNED FORCE, EXCITEID=125, TYPE=0 (DEFAULT), TIME FUNCTION TID=13
TLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
$
$ TIME FUNCTION 13 USED FOR FORCE LOAD
TABLED2 13
0. +
+ 0. 0. 1. 100. 2. 0. ENDT

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-7
© 2023 Siemens
 7. Loads

$
$ TIME-ASSIGNED FORCE EXCITEID=3, TYPE=0 (DEFAULT), TIME FUNCTION TID=12
TLOAD1 105 3 1 12
$
FORCE 3 73 0 2. 8. 0. 0.
$
$ TIME FUNCTION 12 USED FOR FORCE LOAD
TABLED2 12
0. +
+ 0. 0. 2. 1. ENDT

• Example 2- Load Input

When there is only one time-assigned load set, the DLOAD entry is not required:

$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345
678
$
$ TIME-ASSIGNED FORCE, EXCITEID=125, TYPE=0 (DEFAULT), TIME FUNCTION TID=13
TLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
PLOAD 125 100.0 21 30 18 10
PLOAD 125 100.0 10 18 22 25
$
$ TIME FUNCTION 13 USED FOR LOAD
TABLED2 13
0. +
+ 0. 0. 1. 100. 2. 0. ENDT
$

• Additional Information about mechanical loads:

• You can specify the enforced displacements with SPC or SPCD entries. See Enforced
displacements.

• Loads in any subcase are total loads as opposed to incremental loads from the previous subcase. In
other words, the ending load from a previous subcase does not become the initial loading for the
consecutive subcase.

• If no load is applied in a subcase, the total load is zero.

• LOAD=n or DLOAD=n defined at the global level is used in all subcases.

Beginning with Simcenter Nastran 2021.2, you must define the time-assigned loads globally (above
all subcases). A fatal error now occurs if you define the DLOAD command in a subcase. You can
use the system cell setting NASTRAN SYSTEM(767)= 0 to turn off the fatal error and revert to the
previous behavior.

7-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Mechanical loads (SOL 402)

• SPCs are allowed to change between subcases, but the SPCD and MPC boundary conditions are not
allowed to change between subcases.

Unlike most other Simcenter Nastran solutions, SOL 402 does not require a SPC or SPC1 companion
card to fix the degrees-of-freedom that also have an imposed displacement. Any fixation has priority
higher than the imposed displacement: the displacement is then ignored and a warning message is
issued.

The absence of companion cards is automatically taken into account by Simcenter Nastran.
However, if you run an input file that was originally exported with companion cards (for example,
as exported by SOL 401), you need to set the SYSTEM CELL 357 to 0 so that Simcenter Nastran
correctly treats the companion cards.

• The TSTEP1 bulk entry defines the time step intervals in which a solution will be generated and
output in a subcase. If your time steps defined by the TSTEP1 entry exceed the time values defined
in your TABLEDi entry, by default, the software will extrapolate the data defined in the TABLEDi
entry. The software will issue a warning if extrapolation occurs. If you do not want the software to
extrapolate the data, you can enter “1” in the EXTRAP field on the TABLEDi entry.

• When RFORCE or RFORCE1 entries are referenced by the EXCITEID field on a TLOAD1 entry, the data
on the associated TABLEDi scale the angular velocity (ω) and acceleration (α), which are used to
compute an inertia force in the equation F = -[m] [ω x (ω x r)) + α x r]. Because ω is squared in the
force computation, the resulting scaling is not linearly related to the computed force (F).

• When you define the RFORCE or RFORCE1 bulk entries as time-unassigned and ramped, the
software ramps the angular velocity and acceleration , which are used to compute the inertia
force. You can use the RFVAR parameter to change how the software interpolates the time varying
scale factor . See SOL 402 - Interpolating rotational inertia loads.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-9
© 2023 Siemens
 7. Loads

7.4 Thermal loads

A thermal load requires a load temperature (Tload), an initial temperature (Tinit), and a reference
temperature (Tref).

Thermal strain is calculated by

ε = αload(Tload – Tref) – αinit(Tinit – Tref)

• Tload is the temperature load which induces a thermal strain.

• Tinit is the strain free temperature used in the analysis.

• Tref is the initial temperature used when computing the temperature dependent coefficient of thermal
expansion, and is defined on the MATi entry. See Computing the coefficient of thermal expansion.

• If either Tload or Tinit are defined, they both must be defined.

• If the coefficient of thermal expansion is defined as temperature dependent with the MATTi entries,
αload is evaluated at Tload, and αinit is evaluated at Tinit .

If the coefficient of thermal expansion is not defined as temperature dependent, αload and αinit are
assigned the single value defined on the MATi entry.

• You can use the MATCTE parameter to define a single coefficient of thermal expansion (αmatcte) that
overrides all values defined in the material definitions (MATi & MATTi bulk entries) and for the rigid
elements (RBEi and RBAR bulk entries). When MATCTE is defined, the thermal strain is calculated from:

ε = αmatcte(Tload – Tinit)

• Tinit is defined using the TEMP(INIT) case control command, and must be the same for all subcases.
Typically, the TEMP(INIT) command is defined globally, and selects one of the following.

• The TEMP(INIT) command can select the TEMP and TEMPD entries in the bulk data.

For example,

...
TEMP(INIT) = 100
...
BEGIN BULK
...
$ Initial temperatures defined in the bulk data
TEMP,100,5,232.0,6,354.4,...etc
...
$ TEMPD defines a temperature for grid points not included on a TEMP

7-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Thermal loads

entry
TEMPD,100,450.0
...

• The TEMP(INIT) command can select the TEMPEX and TEMPD bulk entries. The TEMPEX entry
references an external binary (BUN) or ASCII (UNV) universal file using the unit number defined
with an ASSIGN statement. The unit number must be unique to other universal files, and to other
reserved unit numbers. The universal file used to define Tinit must only include a single set of
temperature data.

If the universal file only defines temperatures for a portion of the model (subset), the TEMPD entry
must be included in the bulk data to define a temperature for the grid points not included in the
universal file.

For example,

...
ASSIGN BUN=‘temperature0.bun’ UNIT=21
...
TEMP(INIT) = 100
...
BEGIN BULK
...
$ Initial temperatures defined in the BUN file
TEMPEX,100,21
$ Temperature for grid points not in the BUN file
TEMPD,100,630.2
...

• For SOLs 402 and 414 only, the TEMP(INIT) command can select the TEMPRB bulk entry to define
the initial temperatures on the CBAR, CBEAM, CROD, and CONROD elements. You can use the Ta
and Tb fields on the TEMPRB entry to define a temperature at each end of the element. The TPij and
Tij fields are not supported.

The software computes the thermal strain for the element the same regardless of how you define
the temperatures on these elements. That is, it computes the average initial temperature,

Taverage_initial =(Tinitial end A + Tinitial end B)/2.

When computing thermal strain on the CBAR, CBEAM, CROD, and CONROD elements, the software
gives precedence to the temperatures defined with the TEMPRB entry over a temperature defined
on a grid point. For an element connected to a CBAR, CBEAM, CROD, and CONROD element, the
software does not apply the Ta or Tb temperature to the grid point when computing thermal strain
on the connected element, regardless if the shared grid point has a temperature defined or not.

For example,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-11
© 2023 Siemens
 7. Loads

TEMP(INIT) = 100
...
BEGIN BULK
...
$ Initial temperatures defined in the bulk data
TEMPRB,100,5,232.0,354.4
...
$ TEMPD defines a temperature for grid points not included on a TEMP
entry
TEMPD,100,450.0
...

• There are a variety of options to define Tload. These options can be defined globally and in a subcase.
Any subcase definition will override any global definition. For example, if you define a time-assigned
Tload globally using the DTEMP command, and you define a time-unassigned Tload in a subcase using
the TEMP(LOAD) command, the time-unassigned Tload is used for that subcase.

Note for SOL 402: Beginning with Simcenter Nastran 2021.2, you must define the time-assigned
temperature loads globally (above all subcases). SOL 402 now produces a fatal error if you define the
DTEMP command in a subcase. You can use the system cell setting NASTRAN SYSTEM(767)= 0 to turn
off the fatal error and revert to the previous behavior.

• You can define a time-unassigned Tload with all temperatures defined in the bulk data. The
TEMP(LOAD) case control command selects the TEMP and TEMPD entries in the bulk data.

For example,

...
SUBCASE 5
TEMP(LOAD) = 150
BEGIN BULK
...
$ time-unassigned grid point load temperatures for subcase 5
TEMP,150,74,232.0,23,354.4,...
$ TEMPD defines a temperature for grid points not included on a TEMP
entry
TEMPD,150,450.0
...

• For SOLs 402 and 414 only, you can define a time-unassigned Tloadwith the TEMPRB bulk entry to
define the load temperatures on the CBAR, CBEAM, CROD, and CONROD elements. You can use the
Ta and Tb fields on the TEMPRB entry to define a temperature at each end of the element. The TPij
and Tij fields are not supported.

The software computes the thermal strain for the element the same regardless of how you define
the temperatures on these elements. That is, it computes the average initial temperature,

7-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Thermal loads

Taverage_initial =(Tload end A + Tload end B)/2.

For example,

SUBCASE 5
TEMP(LOAD) = 150
BEGIN BULK
...
$ Initial temperatures defined in the bulk data
TEMPRB,150,5,232.0,354.4
...
$ TEMPD defines a temperature for grid points not included on a TEMP
entry
TEMPD,100,450.0
...

When computing thermal strain on the CBAR, CBEAM, CROD, and CONROD elements, the software
gives precedence to the temperatures defined with the TEMPRB entry over a temperature defined
on a grid point. For an element connected to a CBAR, CBEAM, CROD, and CONROD element, the
software does not apply the Ta or Tb temperature to the grid point when computing thermal strain
on the connected element, regardless if the shared grid point has a temperature defined or not.

• You can define a time-unassigned Tload with temperatures defined in an external binary (BUN) or
ASCII (UNV) universal file. The TEMP(LOAD) case control command selects the TEMPEX bulk entry
and optionally the TEMPD entry. The TEMPEX entry references the external universal file using
the unit number defined with an ASSIGN statement. The unit number must be unique to other
universal files, and to other reserved unit numbers. The universal file selected with the TEMPEX bulk
entry must only include a single set of temperature data.

If the universal file only defines temperatures for a portion of the model (subset), the TEMPD entry
must be included in the bulk data to define a temperature for the grid points not included in the
universal file.

TEMPEX example:

...
ASSIGN BUN=‘temperature1.bun’ UNIT=22
$...
SUBCASE 10
TEMP(LOAD) = 200
BEGIN BULK
...
$ Time-unassigned load temperatures for subcase 10
TEMPEX, 200, 22
$ Temperature for grid points not in the BUN file
TEMPD,200,630.2
...

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-13
© 2023 Siemens
 7. Loads

• You can define a time-assigned Tload with temperatures defined in the bulk data or in an external
binary (BUN) or ASCII (UNV) universal file. The DTEMP case control command selects the DTEMP
bulk entry, which defines a list of time points versus set IDs. The set IDs are either the IDs of TEMP
and TEMPD entries in the bulk data, or the IDs of TEMPEX and TEMPD entries in the bulk data. You
cannot combine TEMP and TEMPEX entries with the same set ID. You cannot define a TEMPD entry
that has the same ID as the DTEMP case control command.

Example with TEMP and TEMPD entries in the bulk data:

Note: This example assumes the TEMP entries for temperature sets
500 and 501 define temperatures for all grid points in the model,
but set 502 defines temperatures for a subset.
As a result, a TEMPD is only required for set 502.
...
DTEMP = 250
SUBCASE 1
...
BEGIN BULK
...
$ DTEMP is a list of time points versus set IDs
DTEMP,250,,,,,,,,+
+,.2,500,.4,501,.6,502
...
$ Load temperatures at t=.2
TEMP,500,5,232.0,6,354.4,7,284.2
$ Temperature for grid points not defined with TEMP entry 500.
TEMPD,500,630.2
...
$ Load temperatures at t=.4
TEMP,501,5,234.1,6,356.3,7,287.8
$ Temperature for grid points not defined with TEMP entry 501.
TEMPD,501,630.2
...
$ Load temperatures at t=.6
TEMP,502,5,237.3,6,358.4,7,292.4
$ Temperature for grid points not defined with TEMP entry 502.
TEMPD,502,630.2
...

Example with TEMPEX and TEMPD entries in the bulk data:

Note: This example assumes the BUN files for temperature sets
501 and 502 define temperatures for all grid points in the model,
but the BUN file for temperature set 502 only defines for a subset.
As a result, a TEMPD is only required for set 500.
...
ASSIGN BUN=‘temperature1.bun’ UNIT=22
ASSIGN BUN=‘temperature2.bun’ UNIT=23

7-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Thermal loads

ASSIGN BUN=‘temperature3.bun’ UNIT=24

...
DTEMP = 250
SUBCASE 1
...
BEGIN BULK
...
$ DTEMP is a list of time points versus set IDs
DTEMP,250,,,,,,,,+
+,.2,500,.4,501,.6,502
...
$ Load temperatures at t=.2
TEMPEX,500,22
$ Temperature for grid points not defined in BUN file
TEMPD,500,345.4
...
$ Load temperatures at t=.4
TEMPEX,501,23
...
$ Load temperatures at t=.6
TEMPEX,502,24
...
$ If the BUN file for t=.2 and t=.4 includes data for all grid
points,
the TEMPD is not needed

• You can define a time-assigned Tload with temperatures defined in a single, external binary (BUN) or
ASCII (UNV) universal file. The DTEMP case control command selects the DTEMPEX bulk entry and
optionally the TEMPD bulk entry. The DTEMPEX entry references the external universal file using the
unit number defined in the ASSIGN statement. The unit number must be unique to other universal
files, and to other reserved unit numbers. The single universal file selected with the DTEMPEX
bulk entry must include temperature data for multiple time points. The universal file can include
temperatures for grids which are not in the model.

If the universal file only defines temperatures for a portion of the model (subset), the TEMPD entry
must be included in the bulk data to define a temperature for the grid points not included in the
universal file.

Example with DTEMPEX and TEMPD entries in the bulk data:

...
ASSIGN BUN=‘temperature.bun’ UNIT=23
$...
DTEMP = 300
SUBCASE 1

BEGIN BULK

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-15
© 2023 Siemens
 7. Loads

...
$ Time-assigned load temperatures for subcase 20
DTEMPEX, 300, 23
...
$ Temperature for grid points not defined in BUN file
TEMPD,300,345.4
...

When you use DTEMPEX, you can optionally map the time values that the software reads from the
universal file and then writes to the database for the SOL 401 or 402 structural solution. You may
be able to use this capability to:

■ Conserve computational resources.

■ Circumvent the six significant digit limit inherent with universal files.

For more information, see Mapping times in universal files.

Additional information:

• The specification of TEMP(MATERIAL) or TEMP(BOTH) are unsupported and will cause a fatal error if
defined.

• The TVAR parameter on the NLCNTL bulk entry for SOL401 controls if time-unassigned temperature
loads selected with the TEMP(LOAD) case control command are ramped, or not ramped for each
subcase.

Beginning with Simcenter Nastran 2021.2, SOL 402 always ramps time-unassigned temperature
loads. SOL 402 will produce a fatal error now if TVAR=STEP is defined on the NLCNTL2 entry. You
can use the system cell setting NASTRAN SYSTEM(767)= 0 to turn off the fatal error and revert to the
previous behavior.

• When TVAR=RAMP, the software ramps the load temperatures from the final Tload defined for the
previous static subcase to the Tload defined for the current subcase. The software determines the
load temperature increments using the total number of time increments defined for that subcase. If
Tload is not defined in the previous subcase, the software ramps from Tinit to the current Tload.

• When TVAR=STEP (SOL 401 only), the load temperatures are not ramped.

The default is “RAMP” except when Tend1 = 0.0 is (preload subcase) defined on the TSTEP1 entry in
the first static subcase. “STEP” occurs in this case.

• For the time-assigned temperature data, the software will interpolate the grid point temperatures
when times are defined between the time points in the data. Although, if a solution time is outside
the data range, the software will use the data at the closest time point, and a warning will be written
to the f06 file.

7-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Thermal loads

• In SOL 401, you can turn off the thermal strain computation by defining the parameter setting
THRMST=NO (default=YES) on the NLCNTL bulk entry. This is useful for temperature dependent
material evaluation without thermal loading.

In SOL 402, thermal strain computations are always performed.

• When temperature dependent material properties are defined with the MATTi entries for a subcase,
the properties are evaluated at Tload selected with either the TEMP(LOAD) or DTEMP case control. Both
Tload and Tinit must be defined when temperature dependent properties are defined.

• In SOL 401, a modal subcase which is not sequentially dependent (SEQDEP=NO) can include
temperature dependent material properties defined with the MATTi entries. The properties are
evaluated at Tload selected with the TEMP(LOAD) case control. The DTEMP case control command is
not supported in a modal subcase. Both Tload and Tinit must be defined when temperature dependent
properties are defined.

• The OTEMP case control command can be included to request solution temperature output.

SOL 402 - Thermal load convergence option

When thermal loads produce unconstrained, free thermal deformation, little or no internal forces result.
This situation can lead to some early problems with the SOL 402 Newton-Raphson iteration strategy. As
a result, convergence can be slow or sometimes can fail.

You can use the ITHE parameter on the NLCNTL2 bulk entry to request how the software manages your
thermal loads. Your appropriate choice here can significantly improve the solution convergence. Either
option will produce the same results if the solution converges. Your choices are as follows.

• ITHE = -1 Free thermal expansion

You should use this option if your thermal loads produce unconstrained, free thermal deformation
resulting with little or no thermal stress.

• ITHE = 0 Constrained thermal expansion

You should use this option if your model is constrained such that your thermal loads produce little
free thermal deformation but significant thermal stress.

Computing the coefficient of thermal expansion

You use temperature versus strain (length) test data to compute the temperature dependent coefficient
of thermal expansion (α). This data begins with the test specimen of initial length L at a reference
temperature (Tref). The axial strain (Li) is then measured at consecutive temperatures Ti. To calculate αi:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-17
© 2023 Siemens
 7. Loads

7.4.1 Mapping times in universal files

For a SOL 401 or 402 structural solution, you can use the DTEMPEX bulk entry to read time versus nodal
temperature data from an external binary (.bun) or ASCII (.unv) universal file and store the data in the
Simcenter Nastran database. You can use a TABLED1 bulk entry to redefine the times in the universal file
so that the values that the software stores in the database are appropriate for the structural solution.

To define the mapping of times, you use the TID field on the DTEMPEX bulk entry to reference a TABLED1
bulk entry that contains the mapping of time from the universal file to the database for the structural
solution. On the TABLED1 bulk entry, you enter the times from the universal file as the independent
variables (xi values in the TABLED1 bulk entry) and you enter the corresponding times that Simcenter
Nastran stores in the database for the structural solution as the dependent variables (yi values in the
TABLED1 bulk entry).

Example: Shifting of time

In this example, suppose that you want to use data in a universal file whose times range from 60 to
240 seconds in a SOL 401 or 402 structural solution whose initial time is zero and final time is 180
seconds. Thus, you want to map the universal file temperatures to the structural solution as indicated in
the following table:

Time in universal file (sec) Time for structural solution (sec)

60 0
240 180

The following DTEMPEX and DTABLE1 bulk entries perform the desired mapping.

DTEMPEX,300,22,,120
TABLED1,120,,,,,,,,+TD1
+TD1,60.0,0.0,240.0,180.0,ENDT

For times in the universal file where a tabular data point does not exist in the TABLED1 bulk entry, the
software interpolates the tabular data to determine the value of time to store in the database for the
structural solution. In this example, because the interpolation method specified on the TABLED1 bulk
entry is linear, the time that the software stores in the database for the structural solution for a universal
file time of 120 seconds is:

Example: Scaling of time

In this example, suppose that you want to use data in a universal file whose times range from zero to
1000 seconds in a SOL 401 or 402 structural solution whose initial time is zero and final time is 50,000
seconds. Thus, you want to map the universal file temperatures to the structural solution as indicated in
the following table.

7-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Mapping times in universal files

Time in universal file (sec) Time for structural solution (sec)

0 0
1000 50,000

The following DTEMPEX and DTABLE1 bulk entries perform the desired mapping.

DTEMPEX,300,22,,120
TABLED1,120,,,,,,,,+TD1
+TD1,0.0,0.0,1000.0,50000.0,ENDT

For times in the universal file where a tabular data point does not exist in the TABLED1 bulk entry, the
software interpolates the tabular data to determine the value of time to store in the database for the
structural solution. In this example, because the interpolation method specified on the TABLED1 bulk
entry is linear, the time that the software stores in the database for the structural solution for a universal
file time of 200 seconds is:

Example: Combined shifting and scaling of time

In this example, suppose that you want to use data in a universal file in a SOL 401 or 402 structural
solution as indicated in the following figure:

Three distinct intervals exist:

• The thermal solution start up interval lasts for 5 minutes (300 seconds) and the times contained in
the universal file map to the structural solution without shifting or scaling.

• The thermal solution steady-state operation interval is modeled over 24 minutes (1440 seconds) and
the times contained in the universal file must be scaled to the 23 hours (82800 seconds) duration
structural solution.

• The thermal solution shut down interval lasts for 3 minutes (180 seconds) and the times contained in
the universal file must be shifted for the structural solution.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-19
© 2023 Siemens
 7. Loads

The following table shows the required mapping.

Time in universal file (sec) Time for structural solution (sec)

0 0
300 300
1740 83100
1920 83280

The following DTEMPEX and DTABLE1 bulk entries perform the desired mapping.

DTEMPEX,300,22,,120
TABLED1,120,,,,,,,,+TD1
+TD1,0.0,0.0,300.0,300.0,1740.0,83100.0,1920.0,83280.0,ENDT

For times in the universal file where a tabular data point does not exist in the TABLED1 bulk entry, the
software interpolates the tabular data to determine the value of time to store in the database for the
structural solution. For this example, because the interpolation method specified on the TABLED1 bulk
entry is linear, the time that the software stores in the database for the structural solution for a universal
file time of 17 minutes (1020 seconds) is:

Implications regarding universal file limitations

The previous example shows how the times in a thermal solution whose duration is shorter than the
SOL 401 or 402 structural solution can be mapped to appropriate times for the structural solution. When
possible, you can use this capability to conserve computational resources during the thermal solution.
However, you can also use this capability to avoid the limitation of six significant digits for the numerical
data in a universal file that results from the FORTRAN E13.5 formatting of the universal file.

For example, suppose in the previous example that the structural steady-state operation lasts for 23
years rather than 23 hours. Thus, the operating intervals are as follows:

• The structural solution start up interval lasts for 5 minutes (300 seconds).

• The structural solution steady-state operation interval lasts for 23 years (725,328,000 seconds).

• The structural solution shut down interval lasts for 3 minutes (180 seconds).

Suppose the time step is 1 second in both the thermal and structural solutions. The final time in the
structural solutions is 725,328,480 seconds (7.25328480E+08 seconds), which has nine significant
digits. The time at the previous time step is 725,328,479 seconds (7.25328479E+08 seconds), which
also has nine significant digits. Because the universal file is limited to six significant digits, both are
stored as 7.25328E+08 seconds in the universal file. Thus, if the duration of the thermal solution

7-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Mapping times in universal files

matched that of the structural solution, there is a loss of resolution in the time data that the thermal
solution writes to the universal file. By modeling the thermal solution over a shorter duration and then
using the DTEMPEX mapping capability to map the universal file times to times appropriate for the
structural solution, you can circumvent the six significant digit limitation of the universal file.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-21
© 2023 Siemens
 7. Loads

7.5 Solution time steps (SOL 401)

Mechanical and thermal loads can optionally be defined as a function of time in a static subcase. These
time-assigned loads only use time as the mechanism to increment the loads.

The TSTEP1 bulk entry defines the time step intervals in which a solution will be generated and output
in a static subcase. You include the TSTEP case control command in the static subcase to select a specific
TSTEP1 definition in the bulk data.

The TSTEP1 entry includes the end times (Tendi), the number of increments (Ninci), and the increment
for computing output (Nouti). The start time for a particular subcase depends if it is sequentially
dependent (SD) or not sequentially dependent (NSD).

1 2 3 4 5 6 7 8 9 10
TSTEP1 SID Tend1 Ninc1 Nout1
Tend2 Ninc2 Nout2
Tend3 Ninc3 Nout3
-etc-

TSTEP1 Input Example:

TSTEP1 1 10.0 5 2
50.0 4 3
100 2 ALL

In this example, assuming a start time=0.0 for the subcase, the resulting time steps are as follows. The
time steps in which output occurs are highlighted. Output always occurs at the end time.

The 1st row has an end time of 10.0, 5 increments, and output at every 2nd time step.

Time Step 1 Time Step 2 Time Step 3 Time Step 4 Time Step 5
2.0 4.0 6.0 8.0 10.0

The 2nd row has an end time of 50.0, 4 increments, and output frequency at every 3rd time step.

Time Step 1 Time Step 2 Time Step 3 Time Step 4

20.0 30.0 40.0 50.0

The 3rd row has an end time of 100.0, 2 increments, and output at all time steps.

Time Step 1 Time Step 2

75.0 100.0

7-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Solution time steps (SOL 401)

In the same example, assuming a start time=5.0 for the subcase, the resulting time steps for the first
row are as follows.

Time Step 1 Time Step 2 Time Step 3 Time Step 4 Time Step 5
6.0 7.0 8.0 9.0 10.0

The 2nd and 3rd row are the same:

Time Step 1 Time Step 2 Time Step 3 Time Step 4

20.0 30.0 40.0 50.0

Time Step 1 Time Step 2

75.0 100.0

Additional Information about TSTEP1:

• No output occurs when Nouti=0.

• Output always occurs at Tendi when Nouti≠0.

• Tendi must be increasing (Tendi < Tendi+1).

• When Tend1=0.0,

• No other times are allowed. This is the only time for the associated subcase.

• Ninci can be defined.

• Results will output at time = 0.0 if Nouti≠0.

• Nouti controls the frequency of results output. The table below summarizes the input options.

Nout Output frequency

YES Output occurs at all increments defined on TSTEP1.
END Output occurs at the end time.
ALL Output occurs at all increments on TSTEP1 and any software subincrements.
Note: When Nouti=ALL in the context of the Simcenter 3D Multiphysics
solution, the result output time steps will be a combination of the structural
output steps as well as the coupled time steps.
Integer = 0 No output occurs.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-23
© 2023 Siemens
 7. Loads

Integer > 0 Output is computed at every Nout increment specific with TSTEP1.
CPLD Output occurs only at coupling times. This option can only be defined by the
Simcenter 3D Multiphysics environment.

• For SOL 401, when a solution fails to complete because of a failed convergence or an error, the
software in addition to the results for the time steps that converged and for which you requested
output with Nouti, the software also outputs results for the last time step that converged before the
solution ended, even if you did not request output for that time step.

• The start time (Tstart) for a static subcase is determined as follows:

• If a static subcase definition in the case control includes SEQDEP=NO, that subcase is not
sequentially dependent (NSD). The start time for an NSD subcase is 0.0.

• For a sequentially dependent (SD) static subcase (default), the final Tendi from a previous SD or
NSD static subcase is the start time (Tstart) for the current SD subcase. If an SD subcase has no
previous SD or NSD static subcases, the start time is 0.0 for that SD subcase, and Tend1=0.0 is
permitted. Otherwise, Tend1 > Tstart for all other SD subcases.

• If a creep material is included, the software uses adaptive time stepping by default. The adaptive time
stepping can result in additional solution time steps which are not defined by the TSTEP1 entry. See
Creep analysis.

Similarly, when running SOL 401 in the context of the Simcenter 3D Multiphysics environment,
additional solution time steps beyond what is defined on the TSTEP1 entries are possible.

For both of these cases, the Nout field on the TSTEP1 bulk entry still determines the frequency of
results output.

7-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Solution time steps (SOL 402)

7.6 Solution time steps (SOL 402)

Mechanical and thermal loads can optionally be defined as a function of time. These time-assigned loads
only use time as the mechanism to increment the loads.

Both the TSTEP and TSTEP1 entries are supported in SOL 402, but it is recommended that you only use
the TSTEP1 entry. You cannot use both definitions in the same model.

When more than one subcase is specified in the case control, the TSTEP1 entry is required in all
ANALYSIS = STATIC, ANALYSIS = PRELOAD, and ANALYSIS = DYNAMICS subcases.

It is not used for modal subcases (MODES, CYCMODES, FOURIER, BUCKLING, and CEIG).

TSTEP1

The TSTEP1 entry includes the end times (Tendi), the number of increments (Ninci), and the increment
for computing output (Nouti).

The start time for a time-based subcase is always the end time from the previous time-based subcase,
regardless of the sequential dependency.

1 2 3 4 5 6 7 8 9 10
TSTEP1 SID Tend1 Ninc1 Nout1
Tend2 Ninc2 Nout2
Tend3 Ninc3 Nout3
-etc.-

Output always occurs at Tendi and every Nouti specified increment.

In ANALYSIS=PRELOAD, Tend is not used since it must be equal to Tstart.

The TSTEP1 entry must be selected with the TSTEP=SID case control command.

Nouti controls the frequency of results output. The table below summarizes the input options in SOL
402.

Nout Output frequency

YES Output occurs at all increments defined on TSTEP1.
END Output occurs at the end time.
ALL Output occurs at all increments on TSTEP1 and any software sub increments.
Integer = 0 Output occurs at the end time.
Integer > 0 Output is computed at every Nout increment specific with TSTEP1.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-25
© 2023 Siemens
 7. Loads

Even if NOUT=0, output always occurs at the very end of the subcase.

Automatic time stepping

Automatic time stepping strategy is turned on by default and can be controlled using the AUTOTIM,
DISLIM, DTINIT, DTMIN, DTMAX, EQMFMX, EQMFMIN, ITMA, and MAXBIS parameters of the NLCNTL2
bulk entry.

When automatic time stepping is activated, the software can reject a time step according to several
criteria. For example, either the maximum number of iterations (ITMA) or the maximum displacement
(DISLIM) may be violated. When the software rejects a time step, it reduces it using (Time Step x
EQMFMIN).

The MAXBIS parameter is available to request the maximum number of times the software can reduce a
time step consecutively. By default, MAXBIS=0 that requests no limit.

Time stepping is not allowed for an ANALYSIS=BUCKLING subcase because SOL 402 performs static
buckling.

7-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bolt preload (SOL 401)

7.7 Bolt preload (SOL 401)

The bolt preload capability allows you to model bolts with the 3D solid elements CHEXA, CPENTA, and
CTETRA, the 2D plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, and CPLSTS8, the axisymmetric
elements CTRAX3, CTRAX6, CQUADX4 and CQUADX8, and the 1D elements CBAR and CBEAM. A bolt
preload subcase is required, and it can include geometric and material nonlinear conditions.

The input requirements for bolt preloads in SOL 401 are as follows.

• A bolt preload subcase requires the ANALYSIS=PRELOAD and BOLTLD=n case control commands. The
BOLTLD case control command references a BOLTSEQ, BOLTFRC, or a BOLTLD bulk entry. Multiple
bolt preload subcases can be defined, and they can be defined as sequentially dependent or
nonsequentially dependent. As a result, you can define bolt preload subcases to apply or remove
bolt forces in any sequence. For example, you can apply a tightening sequence of many bolts before
and after service loads are applied.

Note that including BOLTLD=n in any subcase that is not a preload subcase will cause a fatal error.

• You use the BOLT bulk entry to select the elements that represent each bolt. The BOLT entry is
referenced by the BOLTFRC entry.

• You can use the BOLTLD bulk entry to combine and scale bolt preload sets defined with the BOLTFRC
bulk entry.

• You can use the BOLTSEQ bulk entry to define a sequence of preload steps in a single subcase. Each
step in a sequence in the sequence selects the ID of a BOLTLD and BOLTFRC bulk entry to select the
bolts and the preloads.

Note that the nonlinear MPC bolt method is not supported when you define the BOLTSEQ entry. When
you define the BOLTSEQ entry, the software automatically switches to the glue method.

• Bolt preloads must be defined in a preload subcase type which always has a constant time. The
incrementing of bolt preloads depends if you have defined a bolt sequence with the BOLTSEQ bulk
entry or not.

When no BOLTSEQ bulk entry is defined, any bolt preloads, temperature loads, and contact initial
interference are all incremented by the number of increments defined with the Ninc field on the
TSTEP1 defined in the preload subcase.

When a BOLTSEQ is defined, you use the number of increments (Ninc) on the BOLTSEQ entry to
increment the bolt preloads. The number of increments (Ninc) on the TSTEP1 entry is ignored for
this case. The temperature loads and contact initial interference are incremented at the same time
as the first bolt listed on the BOLTSEQ entry using the Ninc value defined for that bolt. The software
holds the temperature loads and contact conditions constant when incrementing the other bolts in
the sequence.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-27
© 2023 Siemens
 7. Loads

• You can use the BOLTRESULTS case control command to request the bolt force and the axial strain
output. See Bolt preload output.

Types of bolts

Bolts in SOL 401 can be defined with the ETYPE=1 or ETYPE=2 formats on the BOLT entry.

Note that all of the BOLT entries referenced in the same input file must be ETYPE=1 or ETYPE=2. A fatal
error will occur if BOLT entries with a combination of ETYPE=1 and ETYPE=2 are referenced.

• The ETYPE=1 format is used for bolts modeled with the CBAR and CBEAM elements. See ETYPE=1
Bolt.

• The ETYPE=2 format is used for bolts modeled with 3D solid elements, plane stress elements, or
axisymmetric elements. See ETYPE=2 Bolt.

Loads in a preload subcase

The bolt preload subcase includes the bolt preload forces and can optionally include a temperature load.
No service loads can be defined directly in a bolt preload subcase. A service load is any load selected
with the LOAD=n or DLOAD=n case control commands. Although service loads cannot be defined directly
in a bolt preload subcase, a sequentially dependent bolt preload subcase will maintain the service loads
used in a previous static subcase.

For example, if a dload=n is defined in the previous static subcase, then this definition is used in the
previous subcase and in the bolt preload subcase. If the previous subcase does not include a service
load, but a dload=n is defined globally, then this definition is used in the previous subcase and in the bolt
preload subcase.

The service loads can change the strain and the resulting axial bolt force by either compressing or
separating the bolted joint. The ability to include service loads in a bolt preload subcase is useful, for
example, if you define your bolt preloads in the first subcase, then you define your service loads in a
single or in consecutive subcases, then you reapply the bolt preloads.

Note that the maintaining of a service load from a previous static subcase is unique to the bolt preload
subcase. For example, if two consecutive sequentially dependent static subcases are defined and service
loads are defined in the first but not in the second, the software will remove the load in the second
subcase.

Constant time bolt preload subcase

A sequentially dependent bolt preload subcase must include a TSTEP1 bulk entry defined with a Tend1
which is the same as the start time for that subcase.

Although the bolt preload subcase does not use time to increment bolt preloads, this provides the ability
to continue a time sequence through an intermediate bolt preload subcase. A consecutive sequentially
dependent static subcase can then continue the time sequence to increment service loads.

7-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bolt preload (SOL 401)

A nonsequentially dependent bolt preload subcase still requires a TSTEP1 bulk entry defined with
Tend=0.0.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-29
© 2023 Siemens
 7. Loads

7.7.1 ETYPE=1 Bolt (SOL 401)

The ETYPE=1 format is used for bolts modeled with the CBAR and CBEAM elements. ETYPE=1 bolts use
the uniform strain method and only supported with the small strain analysis. With the uniform strain
method, the software iterates to determine the uniform axial strain which produces the axial bolt force
you request. The software then reapplies the computed strain for the consecutive subcases.

Defining the BOLT bulk entry for 1D elements (ETYPE=1)

The 1D bolt definition (ETYPE=1) for SOL 401 is consistent with the definition for linear solutions.

• You use the ETYPE=1 option on the BOLT bulk entry when defining the 1D bolt.

• If multiple CBAR or CBEAM elements are used to model a bolt, only one of the elements needs to be
listed on the BOLT entry. Although, if you are requesting results with the BOLTRESULTS case control
command and you would like these results stored for all of these CBAR or CBEAM elements, then you
should list all of the elements on the BOLT entry.

• The same case control commands and bulk entries supported by the 3D and 2D bolts are also
supported for the 1D bolts. This includes the BOLTLD and BOLTRESULTS case control commands and
the BOLT, BOLTLD, BOLTFRC, and BOLTSEQ bulk entries.

• You can use the LOAD, STRAIN, and DISP in the TYPE field on the BOLTFRC bulk entry to define a
preload as a force or a displacement, respectively.

• Sequential loading of 1D bolts is supported.

• You can define the BOLTRESULTS case control command to request the output of bolt axial force,
shear forces, bending moments and strains for the 1D bolts.

• SOL 401 requires that all of the BOLT bulk entries must have the same ETYPE. Specifically, they
must all be ETYPE=1 or ETYPE=2. A fatal error will occur if BOLT entries with different ETYPES are
referenced.

Bolt preload convergence for ETYPE=1

With bolts defined with ETYPE=1, you can adjust the bolt preload convergence tolerance with the
EPSBOLT parameter (default=1.0E-3), which is defined on the NLCNTL bulk entry. For each bolt preload
iteration, the software computes the difference between the current bolt preload and the user-defined
preload. If the difference is less than value of the EPSBOLT parameter, the bolt preload calculation is
considered converged. If the difference is greater than EPSBOLT, the preload strain is recomputed for the
next bolt preload iteration. The iterations continue until either convergence is satisfied, or the number
of iterations reaches the value of the ITRBOLT parameter (default=20). The ITRBOLT parameter is also
defined on the NLCNTL bulk entry.

The software issues a fatal error message if the bolt preload iterative solution fails to converge. The
convergence information related to bolt preload is listed in the f06 file.

7-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 ETYPE=1 Bolt (SOL 401)

Note: In solution 401, the software iterates until the resulting bolt force matches, within a tolerance,
the bolt preload you requested. The final bolt strain required to achieve the desired bolt force includes
the effects of any other defined loads (thermal loads, contact forces, and conditions from a previous
subcase). For example, if you compare the results from a solution with only bolt preloads defined with
the results from the same model with the addition of thermal loads and contact, the bolt force will be
the same, but the final bolt strain needed to achieve the bolt force will be different.

Zero bolt preload force considerations for ETYPE=1

The option to define a zero bolt preload force is available for bolts of all ETYPEs. The zero preload is
useful, for example, to predict the plastic axial bolt strain after applying a bolt preload, applying service
loads, then finally unloading the bolt to a zero axial force condition.

When you define a zero bolt preload force for ETYPE=1 bolts, the software iterates on the bolt strain
until the zero bolt force condition is satisfied. The software checks for convergence by checking if P/AE <
ZERBOLT, where

P is the resulting axial bolt force from an applied axial strain value,

A is the area of the bolt cross section,

E is the modulus of the material selected for the elements on the bolt, and

ZERBOLT is a parameter on the NLCNTL bulk entry and defaults to 1.0E-7.

Note that the software considers a bolt preload force to be zero when F/AE < ZERBOLT, where F is the
preload force you requested on the BOLTFRC entry. A preload of 0.0 always satisfies this, but it is also
possible for the preload to be nonzero, yet A and E are large enough for the software to determine that
the zero preload convergence checking should be used.

If the software determines that your requested preload is nonzero, it uses the EPSBOLT parameter to
determine convergence, and not ZERBOLT. See the remarks on the NLCNTL bulk entry.

Bolted joints with a modeled gap for ETYPE=1

With bolts defined with either ETYPE=1, the MISFBLT parameter is available on the NLCNTL bulk entry
to limit the bolt strain from one preload increment to the next. It is useful, for example, if you model a
bolted joint with a gap condition.

The bolt preload algorithm increments the bolt strain as the joint compresses. When a gap is present,
before the joint is compressed, the axial bolt force will be relatively low. As a result, the preload
algorithm will increase the strain increments. Once the gap is closed and the joint begins to compress,
the bolt and contact forces will change quickly, possibly causing the contact conditions to destabilized.
By limiting the bolt preload strain increments, you can reduce the chance of destabilization, and
ultimately help achieve convergence.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-31
© 2023 Siemens
 7. Loads

At the start of a bolt preload solution, the software uses your requested preload force and the bolt
geometry to estimate a bolt strain. The estimated strain (εes) is computed with the assumption that
everything is rigid except for the bolt. The software then computes the maximum allowable strain
increment using the MISFBLT parameter.

Δεmax = εes * MISFBLT

At each preload increment, the software compares Δεmax with the next computed preload increment
Δεi+1. The software uses the smaller of the two at each preload increment.

Bolt preload diagnostic messages in .f06 for ETYPE=1

With the ETYPE=1 uniform strain method, bolt preload diagnostic messages are written to the .f06 file.
The MSGLVLB parameter on the NLCNTL bulk entry controls the message level. The MSGLVLB options are
as follows:

MSGLVLB=0: Bolt summary messages are written to the .f06 file upon convergence.

MSGLVLB=1 (default): Bolt summary messages are written to the .f06 file at every bolt preload iteration.

MSGLVLB=2: Bolt summary messages and load/tolerance messages are written to the .f06 file at every
bolt preload iteration.

MSGLVLB=1 and 2 also require that the MSGLVL parameter, which is also defined on the NLCNTL bulk
entry, be set to 1 (default). When MSGLVL= 0 is defined, the software also forces MSGLVLB to 0, even
if you had defined MSGLVLB=1 or 2. The MSGLVLB 1 and 2 settings will also output a table of bolt
data showing the forces, moments and strains per bolt. This is only written after all bolt preloads have
converged.

The following examples demonstrate the MSGLVLB output options.

MSGLVLB = 0 – The following is output upon convergence.

----- BOLT COUNT ------ ----------- BOLT PRELOADING

STATUS-----------
ITERATION TOTAL PRELOADING WITHIN TOL ERROR TOL MAX ERROR
4 1 1 1 1.00E-03 8.80E-05

MSGLVLB = 1 (Default) – The following is output at every bolt iteration.

----- BOLT COUNT ------ ----------- BOLT PRELOADING

STATUS-----------
ITERATION TOTAL PRELOADING WITHIN TOL ERROR TOL MAX ERROR
1 1 1 0 1.00E-03 6.21E-01

MSGLVLB = 2 – The following is output at every bolt iteration.

7-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 ETYPE=1 Bolt (SOL 401)

----- BOLT COUNT ------ ----------- BOLT PRELOADING

STATUS-----------
ITERATION TOTAL PRELOADING WITHIN TOL ERROR TOL MAX ERROR
1 1 1 0 1.00E-03 6.21E-01
TARGET ACTUAL ERROR WITHIN
BOLT ID PRELOAD PRELOAD RATIO TOL
101 2.00E+08 7.58E+07 6.21E-01 -

MSGLVLB, 1 and 2 – The following is output upon convergence

-----BOLTS SUMMARY UPON CONVERGENCE-----

BOLT ID AREA PRELOAD AXIAL SHEAR1 SHEAR2 MOM1
MOM2 STRN
101 1.00E+02 2.00E+08 2.00E+08 -3.63E-07 1.10E-06 -2.79E+08 -2.79E+08
2.64E-02

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-33
© 2023 Siemens
 7. Loads

7.7.2 ETYPE=2 Bolt (SOL 401)

The ETYPE=2 format on the BOLT bulk entry is used for bolts modeled with 3D solid elements, plane
stress elements, or axisymmetric elements. ETYPE=2 bolts use the cut-plane method and are supported
with both small and large strain analysis. With the cut-plane method, the software splits the mesh at the
grid points specified on the BOLT definition by:

• Fitting a plane through the specified grid points.

• Creating a new, coincident grid point at each specified grid point location.

• Modifying the connectivity of elements that are both attached to the specified grid points and have
a centroid that is on the positive side of the computed plane so that the new, coincident grid points
replace the original specified grid points. Connectivity is unchanged for elements that are attached to
the specified grid points but have a centroid on the negative side of the computed plane.

The bolt shortening as a result of the preload is enforced by holding the grid point pairs at the cut in a
relative deformed state. The software uses a nonlinear MPC approach by default to maintain the relative
shortening. System cell 750 can be used to select the approach:

• SYSTEM(750)=2 (default): Selects the nonlinear MPC approach. See Nonlinear MPC preload
approach below.

• SYSTEM(750)=0 or 1: Selects the glue approach. See Glue approach and stiffness scaling options
below. Note that the displacement based preload (TYPE=DISP on BOLTFRC) is not supported with the
glue approach.

See system cell 750 for details.

Defining the ETYPE=2 BOLT

You list the grid point IDs connected to the element edges (2D bolt) or faces (3D bolt) where the
software will cut the bolt in the Gi fields on the BOLT entry.

You can define the bolt coordinate system with the CSID field and the bolt axial direction with the IDIR
field on the BOLT bulk entry.

If your bolt axis is parallel with one of the basic coordinate system axes, you can leave both the CSID
and IDIR fields blank, and the software will automatically determine the bolt axis. If your bolt axis is not
parallel with one of the basic axes, you must define the CSID and IDIR fields. If the CSID and IDIR fields
are blank and the bolt axis is not aligned with one of the three basic coordinate axes, the software will
end with a fatal error.

Defining the preload

7-34 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 ETYPE=2 Bolt (SOL 401)

You can define your preload on an associated BOLTFRC bulk entry as a displacement or a force. The
STRAIN preload option on the BOLTFRC bulk entry is not supported with the cut-plane method and will
cause a fatal error if defined.

When you apply the bolt preload as a displacement, the software treats this as incremental shortening.
That is, the specified shortening value is added to an existing bolt shortening (if a previous preload was
applied) and the net shortening is enforced.

A bolt preload force equal to 0.0 is supported. The zero preload is useful, for example, to predict the
residual axial bolt strain after applying a bolt preload, applying service loads, then finally unloading the
bolt to the zero axial force condition.

Bolt definition with axisymmetric elements

The axis of the axisymmetric bolt must be aligned with the axisymmetric axis of rotation defined by the
basic coordinate system. For example, if the axisymmetric elements are defined on the X-Z plane, the
axis of the bolt must be aligned with the Z-axis.

When you define a bolt with ETYPE=2, the software cuts the bolt perpendicular to the bolt axis. As
a result, when you define the axisymmetric bolt, you list the grid point IDs in the Gi fields on the
BOLT entry where you want the software to cut the bolt. Because the bolt axis is parallel with the
axisymmetric axis, you do not need to define the CSID or IDIR fields on the BOLT entry.

When you use the TYPE=LOAD option on the BOLTFRC entry, the load is the total force around the
circumference. The axisymmetric force output is also the total force around the circumference. The axial
force is the only bolt force component for the axisymmetric bolt.

Nonlinear MPC preload approach

The nonlinear MPC approach is based on the following assumptions:

1. The grid points defined on the bolt cut plane are nearly on the same plane and assumed to be
coplanar.
2. The bolt cut plane is nearly normal to the bolt axis direction.
3. After the bolt deforms, both sides of the cut plane remain a plane.
4. Any rotation of the two sides of the bolt cut plane due to deformation occurs about the centroid of
the two planes, and both sides of the cut plane should undergo identical rotation. A consequence of this
is that the displacement of the centroid of the cut planes due to rotation in the bolt axial direction is
0.0.
5. If you request a small displacement solution (LGDISP= -1), the MPC constraints created at the cut
plane are treated as linear constraints.

For all ETYPE=2 bolts, the software assigns the bolt coordinate system as the displacement coordinate
system to all of the bolt grid points on the cut planes (both the existing and the software-generated grid
points), and ignores any displacement coordinate systems you may have defined on the bolt grid points.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-35
© 2023 Siemens
 7. Loads

The bolt shortening (that is, the relative axial separation between the two sides of the cut plane) is
determined in the preload subcase and can only change when another preload subcase redefines the
shortening. The software maintains the bolt shortening in the other subcase types that follow a preload
subcase.

You can apply a bolt preload as a force or a displacement in the preload subcase. When the bolt preload
is applied as a force, the software computes the forces which will be applied to all the grid points on
the two sides of the cut-plane. The structure deforms under the application of the preload and the bolt
shortening is obtained after attaining equilibrium.

When you apply the bolt preload as a displacement, the software treats this as incremental shortening.
That is, the specified shortening value is added to an existing bolt shortening (if a previous preload was
applied) and the net shortening is enforced.

The MPC relationships created between the original and duplicate grid points at the bolt cut plane
enforce the following:

1. The original and duplicate grid points do not experience any relative in-plane separation.

2. The axial separation between the original and duplicate grid points equals the axial separation
between the centroids of the faces of the two sides of the bolt cut plane.

With small displacements (LGDISP=-1), the MPC conditions are created in the original bolt coordinate
system and remain unchanged through the solution.

With large displacements (LGDISP=+1) or large strain (LGSTRN=+1), the MPC conditions are relative to
the current bolt coordinate system. The software considers any rotation of the bolt coordinate system.

Glue approach and stiffness scaling options

When you define a bolt with ETYPE=2 and select the glue approach with SYSTEM(750)=0 or 1, the
software holds the grid pairs in their relative deformed state using a stiff glue condition. The software
computed glue stiffness is three orders of magnitude larger than your material stiffness. The software
applies the same glue stiffness to both the axial and tangential directions.

You can scale the axial bolt glue stiffness with the BLTGLSCL parameter and scale the tangential (two
coordinates normal to the axis) bolt glue stiffness with the BLTTNSCL parameter. Both parameters
default to 1.0, resulting in no scaling of the default stiffness. You decrease the stiffness by defining
values less than 1.0, or increase the stiffness by defining values greater than 1.0.

The default stiffness should work for most conditions. Although, if you experience conditioning and
convergence issues, you can consider reducing the bolt glue stiffness.

In addition, you can use the system cell definition SYSTEM(610)=1 to replace the tangential glue
stiffness with tangential MPC conditions. The axial stiffness remains as a glue condition. The MPCs are
generated based on the initial configuration and are not updated during the solution. As a result, these
MPC constraints are only valid when the rotations in the bolt are small.

7-36 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 ETYPE=2 Bolt (SOL 401)

By using the tangential MPC condition, you are coupling the grid point pairs such that they always move
together in the tangential direction. For example, if the default tangential stiffness is not large enough
and the bolt halves slide relative to each other, and you are confident that the bolt will not experience
large rotations, you can consider defining SYSTEM(610)=1.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-37
© 2023 Siemens
 7. Loads

7.7.3 Bolt preload output (SOL 401)

The BOLTRESULTS case control command is available to request the bolt force and the axial strain
output. The output includes the axial, bending moment, shear forces, and axial strain. It can be written
to the .f06, .op2, and .pch files. The data is written to the OBOLT1 data block in the .op2 file.

The bolt force output is a summation of the forces across the bolt cross section. The bolt force
computation for each force component is similar to cutting the bolt at a point along the axis, then
summing the forces on the faces of one side of the cut. Although the total force components are not
computed on a per element basis, the constant force values computed for the bolt are written to every
element defining the bolt. The result of this is that each bolt will display as a constant force inside a post
processor.

Bolt coordinates

The software uses the coordinate system you select with the CSID field on the BOLT bulk entry to
determine the bolt axis and the output coordinates. If you leave the CSID field blank, the software uses
the basic coordinate system. You can optionally define the IDIR field on the BOLT entry to select the
coordinate axis to use for the bolt axis.

The software computes a normal vector to the bolt cut you define in the Gi fields. That normal vector
must be parallel with one of the CSID coordinate axes or a fatal error occurs. If you receive the error, you
will need to reference a new local coordinate system in the CSID field that satisfies this requirement.

The requirement ensures a clearly defined coordinate system for computing and post processing bolt
results. Once the software determines the coordinate axis parallel with the bolt axis, the remaining two
coordinate axes become the output1 and output2 directions for shear and bending moment bolt results.
The following table shows the resulting coordinates for each bolt axis orientation.

Bolt axis coordinate Output1 coordinate Output2 coordinate

CSID x-axis (IDIR=1) CSID y-axis CSID z-axis
CSID y-axis (IDIR=2) CSID z-axis CSID x-axis
CSID z-axis (IDIR=3) CSID x-axis CSID y-axis

Bolt results output sign convention

You can request bolt preload results using the BOLTRESULTS case control command. For each output
component, the software computes a single scalar value, and outputs that value to every element in the
bolt definition. The sign given to the scalar value is determined by the following conventions.

The moment and shear forces described below are computed on the lower part of the bolt, that is the
part with the minimum axial coordinate. For example, if the bolt axis is parallel with the x-axis, and one
end of the bolt is at x= -15.0, and the other end is at x= -5.0, the end at x= -15.0 is the lower part.

• When you apply a positive preload force, the resulting axial bolt force output will also be a positive
value. A positive bolt preload force compresses an assembly.

7-38 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bolt preload output (SOL 401)

• The shear forces and bending moments are computed at the cut plane on the lower part of the bolt,
and the output is relative to the output1 and output2 coordinates listed in the table above.

In the following example, a service load Fx is applied that has produced shear forces and bending
moments on the bolt. Vt and Vb are the shear reaction forces at the top and bottom of the cut,
respectively. Mt and Mb are the moment reactions at the top and bottom of the cut, respectively.
The force and moment directions shown match what the grid point force output produces (GPFORCE
command).

The software computes the bolt results using the lower part of the bolt, so Vb and Mb are used. Since
the bolt axis is parallel with the z-axis (IDIR=3), as shown in the table above, the output1 coordinate
is the x-axis, and the output2 coordinate is the y-axis. The shear and moment bolt results for this
example are as follows.

• Shear force1 is a positive value in the x-direction.

• Shear force2 is zero since there is no load in the y-direction.

• Bending moment1 about the x-axis is zero since there are no loads in the y-direction or moments in
the x-direction.

• Bending moment2 about the y-axis is a positive value.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-39
© 2023 Siemens
 7. Loads

7.8 Bolt preload (SOL 402)

The bolt preload capability allows you to model bolts with either:

• 3D solid elements CHEXA, CPENTA, and CTETRA.

• 2D plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, and CPLSTS8.

• 2D axisymmetric elements CTRAX3, CTRAX6, CQUADX4 and CQUADX8.

• 1D elements CBAR and CBEAM.

A bolt preload subcase is required, and it can include geometric and material nonlinear conditions.

Input requirements

• A bolt preload subcase requires the ANALYSIS=PRELOAD, ANALYSIS=STATICS, or ANALYSIS=DYNAMICS.

It also requires a BOLTLD=n case control commands. The BOLTLD case control command references a
BOLTFRC or BOLTLD bulk entry.

Multiple bolt preload subcases can be defined. They can be defined as sequentially dependent or
non-sequentially dependent. As a result, you can define bolt preload subcases to apply or remove bolt
forces in any sequence. For example, you can apply a tightening sequence of many bolts before and
even after service loads are applied.

• You use the BOLT bulk entry to select the elements that represent each bolt.

Bolts can be defined with either the ETYPE=1, ETYPE=2, or ETYPE=3 formats on the BOLT bulk entry.
All three type request the cut plane method. For more information, see Cut plane method.

• You use the BOLTFRC bulk entry to define a preload enforced displacement (TYPE=DISP) or a preload
force (TYPE=LOAD). SOL 402 does not support a preload strain definition (TYPE=STRAIN).

• Beginning in Simcenter Nastran 2021.1, if you define a preload using the displacement option on a
bolt that has already received a prior preload, the software will add the new preload displacement
to the prior preload displacement. This occurs when the prior preload was defined with either the
TYPE=DISP or TYPE=FORCE options on the BOLTFRC entry.

For example, if a preload in subcase 1 uses the TYPE=FORCE option on a bolt, the software first
applies the preload force to compute the relative axial displacement D1 on each side of the bolt cut.
The software then maintains the grid pairs at the cut with the opposing axial deformation D1 in the
subsequent static, modal, and dynamic subcases 2, 3, and 4. Then in subcase 5, a new preload is
defined on the same bolt using the TYPE=DISP option with a preload value of D5 on the BOLTFRC

7-40 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bolt preload (SOL 402)

entry. The software now maintains the grid pairs at the cut with the new opposing axial deformation
D1+D5 in the subsequent subcases.

In pre-2021.1 releases, the software would maintain the grid pairs at the cut with the deformation
D5 in the subsequent subcases. You can revert to the pre-2021.1 behavior by defining the MODEVERS
parameter on the NLCNTLG bulk entry to a previous release. For example, MODEVERS=20201.

• You use the BOLTD bulk entry to combine and scale bolt preload sets that are defined with the
BOLTFRC bulk entry.

• You cannot define a sequence of several preload steps in the same subcase. You must define one
unique preload per subcase.

• If the bolt load is defined in an ANALYSIS=PRELOAD subcase, the bolt load will be linearly ramped
starting from the value 0.0 and ending with the bolt load defined for the subcase.

If the bolt load is defined in a subcase that does not include ANALYSIS=PRELOAD (for example, in a
subcase that includes ANALYSIS=STATICS), the bolt load will be applied as a function of time. The bolt
load for this case begins with the value from the end of the previous subcase, and ends with the bolt
load defined for the current subcase.

• When you define a bolt preload for SOL 402, at the beginning of the analysis (time=0.0), the software
cuts the bolt perpendicular to its axis resulting in a set of grids on each of the two cut faces.

Before Simcenter Nastran 2021.1, the grids on the cut faces remained free until the preload subcase.
As a result, for any subcases defined before the preload subcase, there was no load path through
the bolt, and the bolted interface was free to separate. You could avoid these issues by making the
preload subcase the first.

Beginning with Simcenter Nastran 2021.1, the software holds the grids on the cut faces together with
no relative axial deformation. This allows the bolts to participate in the problem before the preload
is applied. When the software does apply the preload, the relative axial deformation is updated
(increased or decreased) to satisfy your preload request.

Cut plane method

In SOL 402, the bolt is always cut. The preload is applied by a force or a relative displacement between
the two parts.

• With a bolt of ETYPE=1, the software cuts the bolt after the first element and add a sensor element
that will be loaded by the preload force or relative displacement.

• With a bolt of ETYPE=2, the cut is defined by a set a point. If all the points are coplanar, the
bolt direction is by default normal to this plane. The preload is applied by the means of a contact
condition.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-41
© 2023 Siemens
 7. Loads

• With a bolt of ETYPE=3, the cut is computed close to the bolt barycenter. If all the faces belonging to
the cut are coplanar, the bolt direction is by default normal to this plane and the preload is applied by
the means of a contact condition.

In all other cases, the bolt direction is by default the axis corresponding to the minimal inertia of the
bolt (or the maximal inertia if the bolt is very small).

Defining a BOLT bulk entry (ETYPE=1)

The bolt is exclusively made of CBAR or CBEAM elements that you reference in the EIDi fields.

Defining a BOLT bulk entry (ETYPE=2)

In that BOLT bulk entry, you define the cut in the bolt with a list of the grid points that are connected to
the element faces. You define the list of grid points in the Gi fields.

You optionally define the CSID and IDIR fields to specify the bolt direction. But you can leave both the
CSID and IDIR fields blank and let the software automatically compute the coordinate system and the
bolt axis.

If the Gi grid points are not coplanar, you must specify the bolt direction with the CSID and IDIR fields.

Defining a BOLT bulk entry (ETYPE=3)

In that BOLT bulk entry, you list all of the 2D or 3D element IDs that define the bolt.

If all the faces belonging to the cut are coplanar, the software computes by default the bolt direction
that is normal to this plane and the preload is applied by the means of a contact condition.

In all other cases, the bolt direction is by default the axis corresponding to the minimal inertia of the bolt
(or the maximal inertia if the bolt is very small).

However, you can specify that direction with the CSID and IDIR fields. In this case, a sensor element is
introduced in order to apply the preload.

You optionally define the GP field that defines grid point where the bolt cross sectional area is calculated.

Bolt preload on axisymmetric elements

You can define a bolt preload on the axisymmetric elements CTRAX3, CTRAX6, CQUADX4, and
CQUADX8. You use the ETYPE=2 option on the BOLT bulk entry to define the preload, which is the
same as you use to define a preload on 3D solid and plane stress elements.

The axis of the axisymmetric bolt must be aligned with the axisymmetric axis of rotation defined by the
basic coordinate system. For example, if the axisymmetric elements are defined on the X-Z plane, the
axis of the bolt must be aligned with the Z-axis.

7-42 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bolt preload (SOL 402)

When you define a bolt with ETYPE=2, the software cuts the bolt perpendicular to the bolt axis. As
a result, when you define the axisymmetric bolt, you list the grid point IDs in the Gi fields on the
BOLT entry where you want the software to cut the bolt. Because the bolt axis is parallel with the
axisymmetric axis, you do not need to define the CSID or IDIR fields on the BOLT entry.

You can apply the axisymmetric preload using the TYPE=LOAD, TYPE=STRAIN, or TYPE=DISP options on
the BOLTFRC bulk entry. When you use the TYPE=LOAD option on the BOLTFRC entry, the load is the
total force around the circumference. The axisymmetric force output is also the total force around the
circumference. The axial force is the only bolt force component for the axisymmetric bolt.

ETYPE=2 or 3 bolt connection options

When you define a bolt with ETYPE=2 or 3, the software cuts the bolt perpendicular to the bolt axis. It
evenly distributes the opposing axial bolt force to each side of the cut, and then it solves a solution to
determine the axial displacement of each side of the cut. The software then maintains the grid pairs in
their relative deformed state in the subsequent subcases.

You can specify how the software maintains the preload condition with the BOLTMETH parameter on the
NLCNTLG bulk entry.

• To maintain the preload condition on the two sides of the bolt cut using RBE3 elements and a sensor
element, you define BOLTMETH=SE3D. This is the default if you defined the bolt axis with the IDIR field
on the BOLT entry.

• To maintain the preload condition on the two sides of the bolt cut using a contact condition, you
define BOLTMETH=CONT. This is the default if you left the IDIR field undefined on the BOLT entry.

Bolt coordinates and output

The software uses the coordinate system you select with the CSID field on the BOLT bulk entry to
determine the bolt axis and the output coordinates. If you leave the CSID field blank, the software uses
the basic coordinate system. You can optionally define the IDIR field on the BOLT entry to select the
coordinate axis to use for the bolt axis.

The software computes a normal vector to the bolt cut you define in the Gi fields. That normal vector
must be parallel with one of the CSID coordinate axes or a fatal error occurs. If you receive the error, you
will need to reference a new local coordinate system in the CSID field that satisfies this requirement.

The requirement ensures a clearly defined coordinate system for computing and post processing bolt
results. Once the software determines the coordinate axis parallel with the bolt axis, the remaining two
coordinate axes become the output1 and output2 directions for shear and bending moment bolt results.
The following table shows the resulting coordinates for each bolt axis orientation.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-43
© 2023 Siemens
 7. Loads

Bolt axis coordinate Output1 coordinate Output2 coordinate

CSID X-axis (IDIR=1) CSID Y-axis CSID Z-axis
CSID Y-axis (IDIR=2) CSID Z-axis CSID X-axis
CSID Z-axis (IDIR=3) CSID X-axis CSID Y-axis

Bolt preload convergence

For all the three ETYPE of bolts, you can improve the bolt preload convergence tolerance with the
NLCNTL2 bulk entry. For example, you can release the convergence criterion (PRCR field) that has
relatively severe by default (1.0E-3) or you can switch to an energy criterion instead of the force criterion
(PRCR=1. 0 and PRCE=1.0E-4 for example).

You can also specify the number of increments during a static constant-time subcase using the Ninc1
parameter that is defined in the STEP1 bulk entry. This is useful to help convergence.

Zero bolt preload force

A zero bolt preload force can be used to disable a previous bolt preload.

Loads in a preload subcase

The bolt preload subcase includes the bolt preload forces and can optionally include a temperature load.
No service loads can be defined directly in a bolt preload subcase. A service load is any load selected
with the LOAD=n or DLOAD=n case control commands. Although service loads cannot be defined directly
in a bolt preload subcase, a sequentially dependent bolt preload subcase will maintain the service loads
used in a previous static subcase.

For example, if a DLOAD=n is defined in the previous static subcase, then this definition is used in the
previous subcase and in the bolt preload subcase. If the previous subcase does not include a service
load, but a DLOAD=n is defined globally, then this definition is used in the previous subcase and in the
bolt preload subcase.

The service loads can change the strain and the resulting axial bolt force by either compressing or
separating the bolted joint. The ability to include service loads in a bolt preload subcase is useful, for
example, if you define your bolt preloads in the first subcase, then you define your service loads in a
single or in consecutive subcases, then you reapply the bolt preloads.

Note that the maintaining of a service load from a previous static subcase is unique to the bolt preload
subcase. For example, if two consecutive sequentially dependent static subcases are defined and service
loads are defined in the first but not in the second, the software will remove the load in the second
subcase.

Constant time bolt preload subcase

A sequentially dependent bolt preload subcase must include a TSTEP1 bulk entry defined with a Tend1
that is the same as the start time for that subcase.

7-44 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bolt preload (SOL 402)

Although the bolt preload subcase does not use time to increment bolt preloads, including a TSTEP1
bulk entry provides the ability to continue a time sequence through an intermediate bolt preload
subcase. A consecutive sequentially dependent static subcase can then continue the time sequence to
increment service loads.

A non sequentially dependent bolt preload subcase still requires a TSTEP1 bulk entry defined with
Tend=0.0.

Bolt preload diagnostics in the .f06 log file

Depending on the bolt ETYPE, the following messages can help you to diagnose issues.

For ETYPE=1 bolts

Message label Explanation

%%%E01-OP2BO01: element is not a rod or a One element of the bolt is not a CBAR or
beam CBEAM.

For ETYPE=2 bolts

Message label Explanation

%%%E01-OP2BO02: the points are not coplanar: All the grid points defining the cut are not
Bolt direction is mandatory coplanar. The software cannot compute the bolt
direction. You must provide the bolt direction.
%%%E06-OP2BO03: not consistent bolt Although the direction of the bolt has been
definition. defined, the given grid points do not make a
cut that effectively cuts the bolt.

For ETYPE=3 bolts

Message label Explanation

%%%I01-OP2BO03: IDIR parameter null or blank The direction of the bolt is not defined.
The direction of the bolt axis is automatically Therefore, the software automatically computes
computed. it.
Bolt Axis: _ _ _
%%%W01-OP2BO03: no cutting plane found. All the faces belonging to the cutting plane
Check the bolt axis. do not cut the bolt and the bolt direction is
not provided. The software will automatically
compute the bolt axis, but it is recommended
that you check the computed direction.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-45
© 2023 Siemens
 7. Loads

Message label Explanation

%%%E06-OP2BO03: not consistent bolt The mesh of the bolt prevents the software
definition from finding a set of faces that cut the bolt.
%%%E08-OP2BO03: not possible to find the bolt The three bolt main inertia values are too close
direction. Please give the bolt direction. and the software cannot compute the bolt axis.
You must explicitly provide that direction.

Bolt preload results and sign convention

The BOLTRESULTS case control command requests the bolt force and the axial strain output. The output
is relative to the coordinate system used to define the bolt axis. The output includes the axial, bending
moment, shear forces, and axial strain. It can be written to the .f06 and .op2 files. The data is written to
the OBOLT1 data block in the .op2 file.

The bolt force output is a summation of the forces across the bolt cross section. The bolt force
computation for each force component is similar to cutting the bolt at a point along the axis, then
summing the forces on the faces of one side of the cut. For each output component, the software
computes a single scalar value. It outputs each scalar value to the elements on both sides of the cut face.
The sign of the force values is determined by the following conventions.

The moment and shear forces described below are computed on the lower part of the bolt, that is
relative to the IDIR axis. For example, if the bolt axis is along -Z, the lower side will be the one with the
largest coordinates.

• When you apply a positive preload force, the resulting axial bolt force output will also be a positive
value. A positive bolt preload force compresses an assembly.

• The shear forces and bending moments are computed at the cut plane on the lower part of the bolt,
and the output is relative to the output1 and output2 coordinates listed in the table above.

In the following example, a service load Fx is applied that has produced shear forces and bending
moments on the bolt. Vt and Vb are the shear reaction forces at the top and bottom of the cut,
respectively. Mt and Mb are the moment reactions at the top and bottom of the cut, respectively.
The force and moment directions shown match what the grid point force output produces (GPFORCE
command).

7-46 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Bolt preload (SOL 402)

The software computes the bolt results using the lower part of the bolt, so Vb and Mb are used.
Because the bolt axis is parallel with the Z-axis (IDIR=3), as shown in the table above, the output1
coordinate is the X-axis, and the output2 coordinate is the Y-axis. The shear and moment bolt results
for this example are as follows.

• Shear force1 is a positive value in the X-direction.

• Shear force2 is zero because there is no load in the Y-direction.

• Bending moment1 about the X-axis is zero because there are no loads in the Y-direction or
moments in the X-direction.

• Bending moment2 about the Y-axis is a positive value.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-47
© 2023 Siemens
 7. Loads

7.9 Fluid penetrating pressure load

Solutions 401 and 402 support a fluid pressure load that the software applies when both of the
following are satisfied.

• The element edges or faces you select to potentially receive the fluid pressure must have a contact
pressure lower than a critical contact pressure you define, or they should not be part of any contact
set.

• The fluid pressure application must have an open traceable path back to at least one starting grid
point. That is, at least one of the grid points connected to the element edge or face must either be a
starting grid point, or it must be connected to an element in which the fluid pressure is active.

You can use this load to represent, for example, a situation in which the contact pressures relax allowing
fluid pressure to enter. In addition, when sliding contact occurs, elements that are no longer in contact
can receive the fluid pressure, and elements that come into contact can have the pressure removed.

Fluid pressure moves into the interface as contact pressure relaxes

You define the fluid pressure load with the PLOADFP bulk entry. You can define the PLOADFP entry
as a time-unassigned load, which you select using the LOAD=n command in the case control, or as a
time-assigned load, which you select using the DLOAD=n command in the case control.

The LVAR parameter on the NLCNTL bulk entry is available to request whether time-unassigned loads are
ramped (default) by the number of increments (NINC) defined on the TSTEP1 bulk entry for the subcase.
The ramping helps convergence by reducing the load increments. You can optionally turn the ramping
off by setting LVAR=STEP on the NLCNTL bulk entry.

You can define multiple PLOADFP entries with the same ID. This allows you to define a PLOADFP for
multiple regions, and then reference all with a single load set ID. See "Loads" in the Multi-Step Nonlinear
User’s Guide for details.

The PLOADFP entry includes the following fields.

PLOADFP entry fields

PRESSURE Defines the normal pressure value as a force per unit area.

7-48 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Fluid penetrating pressure load

WETID Region ID of a BSURF, BSURFS, BEDGE, BCPROP, BCPROPS

containing element edges or faces that can potentially receive
the fluid pressure.
GRSTART ID of a GROUP bulk entry listing starting grid point IDs.
CPCRIT Critical contact pressure as a force per unit area.

You can use the fluid pressure load when large displacements are turned on with the parameter setting
LGDISP=1, although the load does not behave as a follower force. That is, the pressure direction remains
relative to the undeformed configuration, even if large rotations occur.

SOL 401 - Region definition

When SOL 401 determines whether an element edge or face receives the fluid pressure, it does not
matter whether the actual region is selected by a contact set. The software is considering only the
element edge or face itself, and whether that edge or face has a contact pressure that is lower than the
critical contact pressure.

This is helpful because, when you define your fluid pressure, you can select element edges or faces in a
potentially wetted region without concern for how you define your contact regions, and vice versa.

For example, you can create a region 1 of element edges or faces to potentially receive the fluid
pressure. Then you create a region 2 and a region 3 representing the source and target regions in your
contact pair. Some of the element edges or faces in region 1 might also be in regions 2 or 3, and others
might only exist in region 1.

The elements that only exist in region 1 are not included in a contact set, but they can still receive the
fluid pressure if they are in the traceable path back to your desired starting location.

The elements that exist in region 1 and in regions 2 or 3 are included in a contact set. They will receive
the fluid pressure only if their contact pressure is lower than the critical contact pressure, and they also
must be in the traceable path.

The following summarizes the 2D and 3D regions you can reference with the WETID field.

Bulk entries to define contact regions

BSURF Defines a region on shell element faces.
BCPROP (SOL 402 Defines a region on shell element faces by property ID.
only)
BSURFS Defines a region on 3D solid element faces.
BCPROPS (SOL Defines a region on 3D solid element faces by property ID.
402 only)
BEDGE Defines a region on 2D axisymmetric, chocking, plane strain
and plane stress element edges.

SOL 402 - Region definition

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-49
© 2023 Siemens
 7. Loads

If the element regions you reference with the PLOADFP entry are also included in contact regions, SOL
402 requires that the contact definition should be defined with only a single contact pair on a single
BCTSET bulk entry.

For example, in the image below, represents the fluid pressure regions referenced by the PLOADFP,
represents an incorrect contact definition in which two contact pairs are defined (four contact
regions), and represents the correct contact definition in which one contact pair is defined (two
contact regions).

The following summarizes the 2D and 3D regions you can reference with the WETID field.

Bulk entries to define contact regions

BSURF Defines a region on shell element faces.
BCPROP Defines a region on shell element faces by property ID.
BSURFS Defines a region on 3-D solid element faces.
BCPROPS Defines a region on 3-D solid element faces by property ID.
BEDGE Defines a region on 2-D axisymmetric, chocking, plane strain
and plane stress element edges.

Fluid pressure path

The fluid pressure path depends on the starting grid points you select in the GRSTART field.

• The software uses only corner grid points for the starting locations and ignores any midside grid
points you select in the GRSTART field.

• If you have not selected starting grid points in the GRSTART field, the software determines starting
grids automatically using the grid points on the free boundaries of your region. The following two
figures demonstrate the default start boundary for 2D and 3D regions.

7-50 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Fluid penetrating pressure load

2D region default starting boundary

3D region default start boundary

SOL 401 - Fluid pressure updates

For SOL 401, the parameter FPPUPDT is available on the NLCNTL bulk entry to control when the software
updates the fluid pressure load as a result of the changing contact status. By default, FPPUPDT=0, and
the fluid pressure application is updated only at the beginning of every time step using the final contact
status from the previous time step.

• FPPUPDT=0 (default)

The fluid pressure application is updated only at the beginning of every time step using the final
contact status from the previous time step. For the first time step in a solution when there is
no previous contact status, the software does not apply fluid pressure to any elements, including
elements that are not in a contact region.

You will need to include enough time steps for the coupled contact and fluid pressure to become
established and achieve a steady state. You should avoid a single time step solution. A warning
message will be printed in the .f06 file if you define only a single time step in the first subcase that
includes fluid pressures.

In addition, you can define a preload subcase before the subcase in which your fluid penetrating
pressures are applied to allow the contact conditions to become established. For this option, your
contact regions must be either initially interfering, or you are including bolt preloads in the preload
subcase to push the contact regions together.

• FPPUPDT=1

The fluid pressure is updated for every solution iteration that occurs in a single time step. This choice
will keep the fluid pressure current with the changing contact status. Defining FPPUPDT=1 is more
computational, and it can cause contact convergence issues if the fluid pressure and the contact
conditions are strongly coupled.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-51
© 2023 Siemens
 7. Loads

SOL 402 - topology-based option

When the mesh on the contact source and target does not match, the contact status and the resulting
fluid pressure area may not be exactly the same on the source and target. This difference in the fluid
pressure area is typically small, but when the pressure is large, this difference becomes more significant.

A topology-based option is available with SOL 402 to request for the software to apply the same fluid
pressure on the source and target. You select the topology option by defining "2" in the OPT field
on the PLOADFP entry. The topology option uses only the source side contact pressures to determine
the application of the fluid pressure. The locations receiving the fluid pressure on the source are then
projected and applied to the target side DOF as an equivalent load.

The software maps source faces to target face candidates at the start of the solution using the
undeformed geometry. Then it uses this initial set of face candidates at each iteration for the fluid
pressure projection. Because the set of face candidates is not updated again, the topology option should
not be used if significant sliding occurs between the source and target regions.

By default (OPT=1), and the source and target side contact pressures are both used to determine the
application of the fluid pressure.

Fluid pressure output

The existing OPRESS case control command has been updated with the FPP describer to request the
fluid pressure output for the 2D and 3D regions referenced by the PLOADFP entry. You can display the
OPRESS output in a post processor to visualize the edges or faces that receive and do not receive the
fluid pressure for each time step.

The figure below illustrates the fluid pressure output on a contact region. The red faces receive the
pressure and the blue faces do not.

You can also view the contact pressure results on the elements that are included in both contact and
fluid pressure. Note that when using FPPUPDT=0, the software uses the contact status from the previous
time step to update the fluid pressure. As a result, when comparing fluid pressure application with the
contact pressure, you will need to look at the contact pressure from the previous time step.

OPRESS command pressure output

7-52 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Initial stress-strain (SOL 401)

7.10 Initial stress-strain (SOL 401)

Defining an initial stress or strain condition

The option to define an initial stress or strain condition is available on all elements in SOL 401 except
for beam elements, shell elements, plane strain elements, generalized plane strain elements, solid
composite elements, and rigid elements.

An unbalanced initial stress-strain results in deformation when applied to an unconstrained body with
the possibility of residual stress.

Note that the definition of a Simcenter Nastran unbalanced initial stress-strain references the
unconstrained body, although, an initial stress-strain can be applied to constrained or unconstrained
models.

A balanced initial stress-strain results in a self-equilibrating stress state and no deformations. See
Balanced initial stress-strain section below.

You define the initial stress or strain with the INITS case control command, which selects the INITS bulk
entry. The INITS case control command must be defined globally, above the subcases. It is reapplied in
every static subcase.

The first row on the INITS bulk entry includes the following fields.

• The TYPE field defines the data type: TYPE=STRESS or TYPE=STRAIN

• The CSYS field selects the coordinate system for the stress or strain components. The default is the
basic coordinate system. CSYS = -1 can also be defined to select the material system.

• The LOC field defines the location:

LOC= GRID: Specifies that data is defined at grid points.

LOC= NOE: Specifies that data is defined on an element at grid locations. This can include corner
and/or midside grid locations.

You define the stress or strain data on the consecutive rows on the INITS entry. The software assumes
the data is either engineering stress or engineering strain. The format of these rows depends on the
data location defined in the LOC field, and the element type.

Format for the 3D solid elements CTETRA, CHEXA, CPENTA and CPYRAM:

Stress at grid points (TYPE=STRESS, LOC=GRID):

GRID ID Sxx Syy Szz Sxy Syz Szx
....

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-53
© 2023 Siemens
 7. Loads

Strain data at grid points (TYPE=STRAIN, LOC=GRID):

GRID ID Exx Eyy Ezz Exy Eyz Ezx
...

Stress data at the element corners (TYPE=STRESS, LOC=NOE):

ElemID GRIDID Sxx Syy Szz Sxy Syz Szx
...

Strain data at the element corners (TYPE= STRAIN, LOC=NOE):

ElemID GRIDID Exx Eyy Ezz Exy Eyz Ezx
...

For the plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8, the software uses both in-plane
and out-of-plane initial strain values. Although, only in-plane initial stress values are used. For example,
the following formats should be used when the plane stress elements are defined on the XY plane, and
the basic coordinate system (default) is used. For elements defined on the XZ plane, Sxx, Szz, Szx or
Exx, Eyy, Ezz, Ezx would be defined.

Stress data at grid points (TYPE=STRESS, LOC=GRID):

GRID ID Sxx Syy Sxy
...

Strain data at grid points (TYPE=STRAIN, LOC=GRID):

GRID ID Exx Eyy Ezz Exy
...

Stress data at the element corners (TYPE=STRESS, LOC=NOE):

ElemID GRIDID Sxx Syy Sxy
...

Strain data at the element corners (TYPE= STRAIN, LOC=NOE):

ElemID GRIDID Exx Eyy Ezz Exy
...

For the axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6, in-plane (radial and axial) and
out-of-plane (theta) initial stress or strain values are used by the software. For example, the following
formats should be used when the axisymmetric elements are defined on the XY plane, and the basic
coordinate system (default) is used. For elements defined on the XZ plane, Sxx, Szz, Szx or Exx, Ezz, Ezx
should be defined.

Stress data at grid points (TYPE=STRESS, LOC=GRID):

GRID ID Sxx Syy Szz Sxy
...

Strain data at grid points (TYPE= STRAIN, LOC=GRID):

GRID ID Exx Eyy Ezz Exy
...

7-54 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Initial stress-strain (SOL 401)

Stress data at the element corners (TYPE=STRESS, LOC=NOE):

ElemID GRIDID Sxx Syy Szz Sxy
...

Strain data at the element corners (TYPE= STRAIN, LOC=NOE):

ElemID GRIDID Exx Eyy Ezz Exy
...

For the plane stress and axisymmetric elements, if you select a coordinate system other than the basic
system in the CSYS field on the INITS entry, the software first transforms the data into the basic system,
and then uses the components consistent with the formats described above.

An option to output the initial strains using the OSTNINI case control command is available. You can
request the output at either the grid or corner Gauss locations on elements. The OSTNINI command
must be defined globally, and the output occurs once at the beginning of the solution. The strains are
output in the basic coordinate system.

Balanced initial stress-strain

A method is available that you can use to balance an unbalanced initial stress-strain. The method
removes the unbalanced part by removing the strains that produce a deformation. For example, because
approximate methods are used to measure residual stress, the application of the residual stress in your
finite element analysis as an initial condition may not result in a state of complete equilibrium, and
instead may result in both residual stress and deformation.

After you use the balancing method, your initial stress-strain will produce a self-equilibrating stress state
and no deformations.

The method requires that a part of your unbalanced initial stress-strain is actually balanced.

The balancing method requires that you first run a static offset-solution to obtain the total strain
output as a result of your unbalanced initial stress-strain with the model unconstrained. You only apply
the unbalanced initial stress-strain in the offset solution. No temperature loads, mechanical loads, or
enforced displacements are applied for this step.

Because there is no thermal strain {εth}, the total strain output {ε} from the offset-solution is computed
as:

{ε} = {εe} + {εin} - {ε0}

where,

{ε} = total strains you can request with the STRAIN case control command,

{εe} = elastic strains you can request with the ELSTRN case control command,

{εin}= inelastic strains you can request with the PLSTRN or CRSTRN case control commands,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-55
© 2023 Siemens
 7. Loads

{ε0} = initial strains you can request with the OSTNINI case control command.

The part of the unbalanced initial stress-strain {ε0} that yields a stress is included in the elastic strain {εe}
and possibly the inelastic strain {εin} if you have included any nonlinear materials. After removing {εe}
and {εin} from the unbalanced initial stress-strain {ε0}, the total strain {ε} output from the offset solution
includes only the part of the initial stress-strain that causes deformation.

You will use the total strain {ε} output from the offset-solution as an offset strain {εoff} in the consecutive
solution.

The total strain output is requested with the STRAIN=ALL case control command. If your model contains
multiple components, each with a unique balanced initial strain, you can run an offset-solution for each
component separately. The offset strains can be used in a consecutive assembly solution.

Note that, regardless of whether your initial stress-strain is applied to all locations on a component or
only to a portion, the offset strains are the total strains at all locations on that component.

To allow the static offset-solution to complete with the unconstrained condition, a matrix stabilization
option is available. Setting the parameter MSTAB to 1 on the NLCNTL bulk entry will turn on the option.
In addition, the MSFAC parameter is available to define a scale factor for matrix stabilization. Specifically,
when you define MSTAB=1, the software scales the diagonal terms by the factor (1+MSFAC).

Balanced solution

Once your offset strains are computed, you can run the consecutive balanced solution that includes
your initial stress-strain {ε0}, your offset strain {εoff}, and any other loads (temperature loads, mechanical
loads, enforced displacements).

You can optionally run a consecutive balanced solution as unconstrained with only your initial stress-
strain {ε0} and your offset strain {εoff} to verify that the strain offsets have removed all deformation,
leaving only the stress state. You can use the matrix stabilization option (MSTAB=1) in the verification
solution if you choose to keep your model unconstrained for this step. Finally, you can apply initial
stress-strain {ε0} and your offset strain {εoff} in a balanced component or assembly solution that includes
any load types and constraints.

During the balanced solution, the offset strains are included in the internal force calculation to
compensate for the deformations caused by your initial stress-strain. See Balanced stress-strain
computation for details.

Defining a balanced initial stress or strain condition

The INITS(OFFSET) case control command and INITSO bulk entry are available to input the offset strain.
Multiple INITSO bulk entries can be combined with the existing INITADD bulk entry.

You define the initial stress-strain with the INITS case control command, which selects the INITS bulk
entry. You can also define multiple INITS bulk entries, each with a unique ID, and then combine them
using the INITADD bulk entry. The INITADD entry is selected with the ID on the INITS case control. The

7-56 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Initial stress-strain (SOL 401)

INITS case control command must be defined globally, above the subcases. It is reapplied in every static
subcase.

The software does not need to associate a balanced initial stress-strain definition with an offset strain
definition in the balanced solution. As a result, the SID defined on the INITS(OFFSET) command that
selects your offset strains, and the SID defined on the INIT command that selects your unbalanced initial
stress-strain do not need to match.

Multiple initial stress-strain at the same location

You can define multiple unbalanced and balanced initial stress-strain at the same location. They can also
be defined using different coordinate systems. The software first converts all stress definitions to strain,
then it transforms all strain into the basic coordinate system, and finally it adds the strains defined at
common locations.

Balanced stress-strain computation

The reference (modeled) configuration of a component with balanced initial stress/strain includes initial
strains. Therefore, under the deformation field that results from combined initial strains and service
loads, the total strains measured from the reference configuration is given by:

{ε} = f({u}) + {εoff}

where,

f({u}) = [B]{u}

with [B] being the strain displacement matrix for small strain formulation.

The total strains are decomposed as:

{ε} = {εe} + {εth} + {εin} - {ε0}

where,

{ε} = total strains that you can request with the STRAIN case control command,

{εe} = elastic strains you can request with the ELSTRN case control command,

{εth} = thermal strains you can request with the THSTRN case control command,

{εin} = inelastic strains you can request with the PLSTRN and CRSTRN case control commands,

{ε0} = initial strains you can request with the OSTNINI case control command.

The elastic strains are obtained as,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-57
© 2023 Siemens
 7. Loads

{εe} = {ε} - {εth} - {εin} + {ε0}

In terms of balanced strain offsets, and assuming small strain formulation, the elastic strains are given by

{εe} = [B]{u} - {εth} - {εin} + ({ε0} + {εoff})

For components in the model without initial strains, {ε0} = {0} and {εoff} = {0}. For the components with
unbalanced initial strains, {εoff} = {0}.

Note that if you request the total strain output {ε} for the balanced solution with the STRAIN case control
command, the software will add the offset strain back to the total as if it were never removed for the
solution. As a result, the total strain computation when a balanced initial stress-strain is defined is the
same as when an unbalanced initial stress-strain is defined.

Converting an initial stress to an initial strain

If you define an initial stress {σ0}, the software converts this to a corresponding initial strain {ε0} by using
the elasticity matrix {D0} at the reference temperature Tref.

{ε0} = {D0}-1 {σ0}

Additional information:

• Initial stress and strain can be defined on a subset of the model. The software assumes a value of 0.0
at the locations where data is undefined. An exception is when data is undefined at a mid-side grid
point, and data is defined at both or either related corners. In this case, the software interpolates a
value for that mid-side grid point.

• The option to apply an initial stress or strain condition before applying other loads in an initial subcase
is available to help convergence. The first subcase should have Tend=0.0 on the TSTEP1 entry and no
load set selected. The number of increments can optionally be defined with NINC on the TSTEP1 entry
to increment the initial stress or strain. When NINC=1 (default), the initial stress or strain is applied
in a single step. When NINC>1, the initial stress or strain is ramped. A service load cannot be defined
when ramping initial stress or strain with NINC>1.

• The software converts an initial stress to an initial strain using the elastic modulus defined on
the MATi entries. If you define MATTi bulk entries to define the elastic modulus as temperature
dependent, the software uses the initial temperatures selected by the TEMPERATURE(INIT) case
control command to evaluate the temperature-dependent elastic modulus. Data on the MATS1 bulk
entry, if defined, is not used to convert stress to strain.

• You can define multiple INITS bulk entries, each with a unique ID, and then combine them using the
INITADD bulk entry. The INITADD entry is selected with the ID on the INITS case control. The INITS
entries selected by the INITADD entry must be all TYPE=STRESS or all TYPE=STRAIN. As a result, you
cannot mix initial stress and initial strain definitions in the same input file.

• If you define data on the same grid or element corner location, a fatal error occurs.

7-58 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Distributed force to a surface or edge (SOL 401)

7.11 Distributed force to a surface or edge (SOL 401)

You can request that the software use forces and moments that you define at a single point to
automatically compute and apply a traction to a surface or edge region. The software computed traction
has a specific form and is described in the Traction computation details section.

You use the FORCDST bulk entry to define the point location, an optional point location offset, the forces
and moments at the point, and to select the element or edge regions for the traction location. The
element and edge regions that receive the traction are defined as follows.

• You use the BSURF entry to create face regions on the shell elements CTRIA3, CTRIA6, CTRIAR,
CQUAD4, CQUAD8, and CQUADR.

• You use the BSURFS entry to create face regions on the solid elements CHEXA, CPENTA, CPYRAM, and
CTETRA.

• You use the BEDGE entry to create edge regions on the following elements:

Axisymmetric elements CTRAX3, CQUADX4, CTRAX6, CQUADX8.

Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

Chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8

You have the option on the FORCDST bulk entry to define the single point location for your forces and
moments at a grid point, at a coordinate system origin, or at the centroid of the surface or edge region
you have selected to receive the traction. The software automatically computes the centroid location of
the surface or edge region.

For a time-unassigned load, you reference the SID of the FORCDST bulk entry and any other mechanical
loads with the LOAD=n case control command either in a subcase or above the subcases (globally).

For example,

...
SUBCASE 5
LOAD = 150
BEGIN BULK
...
$ TIME-UNASSIGNED LOADS FOR SUBCASE 5
FORCDST,150,10,,CNTRD,,,,,+
+,1.0,23.4,428.6,84,2,49.7,7846.4,5876.5
...
RFORCE,150,5,,-6.4,0.0,0.0,1.0,2
...

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-59
© 2023 Siemens
 7. Loads

For a time-assigned load, you must select the FORCDST bulk entry with the EXCITEID on the TLOAD3
bulk entry. The TLOAD3 entry includes six TID fields that you can use to independently scale the three
force and the three moment components with time by referencing a unique TABLEDi entry for each. You
can also reference the same TABLEDi entry for any or all TID fields to define the same load variations.
The FORCDST entry is the only load you can select with the TLOAD3 entry. All other time-assigned
mechanical loads are selected by the EXCITEID of the TLOAD1 bulk entry, which scales all referenced
loads consistently with time. You can combine TLOAD1 and TLOAD3 entries into a single load set with
the DLOAD bulk entry.

For example,

...
SUBCASE 5
$DLOAD CASE CONTROL SELECTS THE DLOAD BULK ENTRY
DLOAD = 250
BEGIN BULK
...
$DLOAD BULK ENTRY COMBINES TLOAD3 (ID=302) and TLOAD1 (ID=305)
DLOAD,250,1.,1.,302,1.,305
...
$TIME-ASSIGNED FORCDST, EXCITEID=125, TIME FUNCTION FOR EACH COMPONENT
TLOAD3,302,125,,,,,,,+
+,,401,402,403,501,502,503
...
FORCDST,125,10,,CNTRD,,,,,+
+,1.0,23.4,428.6,84.2,49.7,78.4,56.5
...
$SOLID ELEMENT REGION TO RECEIVE TRACTION
BSURFS,10,,,,8,10,15,40,+
+,12,15,20,45,16,20,25,50,+
+,24,35,40,65,28,40,45,70,+
+,32,45,50,75,40,60,65,90
...
$TIME FUNCTIONS FOR EACH COMPONENT DEFINED ON FORCDST
TABLED2,401,0.,+
+,0.,0.,1.,100.,2.,0.,ENDT
TABLED2,402,0.,+
+,0.,0.,1.,120.,2.,0.,ENDT
TABLED2,403,0.,+
+,0.,0.,1.,140.,2.,0.,ENDT
TABLED2,501,0.,+
+,0.,0.,1.,80.,2.,0.,ENDT
TABLED2,502,0.,+
+,0.,0.,1.,90.,2.,0.,ENDT
TABLED2,503,0.,+
+,0.,0.,1.,100.,2.,0.,ENDT
...
$TIME-ASSIGNED RFORCE, EXCITEID=150, TIME FUNCTION TID=13
TLOAD1,305,125,13

7-60 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Distributed force to a surface or edge (SOL 401)

$TIME FUNCTION 13 USED FOR FORCE LOAD

TABLED2 13 0. + 0. 0. 1. 100. 2. 0. ENDT
RFORCE,150,5,,-6.4,0.0,0.0,1.0,2
...

The FORCDST bulk entry includes the optional point location offset. This offset is simply added to the
point location defined on the FORCDST bulk entry. The software does not scale the point location or the
offset with time. The TABLEDi entry you reference from a TID field only scales the associated force or
moment value. As a result, the location of the forces and moments remain constant for a solution.

The software always computes the traction based on the undeformed configuration. It does not take into
account large displacements or rotations when recomputing the traction at a time step.

Traction computation details

Figure 7-1 shows an example element patch to illustrate the procedure. You define the FORCDST bulk
entry to apply the forces and moments at point D or optionally at the centroid (C), and to select the
element patch where the software computes and applies the traction.

Figure 7-1. Element patch and load locations

The software computes the centroid (C) of the element patch. If you defined your forces and moments
at D, the software transfers them to an equivalent system at C using a rigid link transformation,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-61
© 2023 Siemens
 7. Loads

where is the vector from C to D.

If you define your forces and moments at the centroid location (C), the software skips the step of
transferring the forces and moments from location D to C.

A local coordinate system is computed on the patch using the eigenvectors of the inertia matrix. The
eigenvector associated with the largest eigenvalue is the x3 direction. This direction is perpendicular to a
flat surface or approximately perpendicular to a curved surface. The next two eigenvectors become the
x1 and x2 directions, respectively.

The software will compute the following traction on the patch:

where are the coordinates of the patch grid points relative to the local patch coordinates
.

The assumption is that the computed traction must satisfy the following requirements.

• The resultant force computed using the forces from all grid points on the patch must equal the force
resultant at C.

• The resultant moment computed using the moments from all grid points on the patch must equal the
moment resultant at C.

Rearranging the terms in the traction gives:

The traction vector is written as a superposition of six traction loads:

The six traction load cases are as follows (per unit surface area or per unit length).

is a uniformly distributed load of unit intensity in the direction.

is a linearly varying load in the direction.

7-62 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Distributed force to a surface or edge (SOL 401)

is a linearly varying load in the direction.

is a uniformly distributed load of unit intensity in the direction.

is a uniformly distributed load of unit intensity in the direction.

is a linearly varying load in the and directions.

The grid point force vector due to surface traction is given by integrating over the entire patch:

Substituting into the equation above gives:

Each term can be written as a grid point force vector:

The grid point force vector for the patch is a linear combination of the grid point force vectors from each
load case:

The original total load requirements are applied here. This results in a 6x6 system of equations that the
software uses to solve for C1, C2, …C6.

• The resultant force of all grid point forces on the patch must be the same as the forces at point C. The
resultant force is computed by:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-63
© 2023 Siemens
 7. Loads

• The resultant moment of all grid point forces on the patch must be the same as the moments at point
C. The resultant moment is computed by:

where is the grid point position with respect to the centroid (C).

There are now six equations to solve for the six unknowns C1, C2, ….,C6.

These equations are resolved into scalar equations.

The software uses the following 6x6 matrix to compute C1, C2, ….,C6.

For time-unassigned loads, this matrix is used once to compute C1, C2, ….,C6.

For time-assigned loads, this matrix is reused to recompute C1, C2, ….,C6 at each time step. The right-
hand side is updated with the updated force and moment values at each time step.

7-64 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Interpolating rotational inertia loads

7.12 SOL 401 - Interpolating rotational inertia loads

When you define the RFORCE or RFORCE1 bulk entries for SOL 401 as either time-assigned, or as
time-unassigned and ramped, the software uses time to scale the angular velocity and acceleration ,
which it uses to compute the inertia force.

You define the time variation either using a time-assigned load referenced by the DLOAD=n case
control command, or by a time-unassigned load referenced by the LOAD=n case control command,
which is ramped. You request this ramping using the LVAR parameter on the NLCNTL bulk entry.

The angular velocity is computed as:

where,

is the rotation vector defined on the RFORCEi entry,

and A is the scale factor of the angular velocity in revolutions per unit time defined on the RFORCEi
entry.

The associated force is computed as:

where,

m is the mass computed at each grid point Gi,

and ri is a position vector to grid point Gi and ra is the position vector to the grid point location G through
which the rotation vector acts. See the graphic on the RFORCEi entries for a definition of the position
vectors.

The RFVAR parameter is available on the NLCNTL bulk entry to change how the software interpolates the
time variation.

• When RFVAR=OMEGA (default), the software interpolates the time variation using .

As a result, if you define a linear time variation, the angular velocity will vary linearly. Because is
squared in the force computation, the force will not vary linearly.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-65
© 2023 Siemens
 7. Loads

• When RFVAR=FORCE, the software interpolates the time variation using . The software then
takes the square root of the interpolated value before applying it to the angular velocity.

As a result, if a linear time variation is defined, the force will vary linearly, but will not.

The RFVAR parameter setting changes the interpolation only for angular velocity, and not for angular
acceleration. Because the angular acceleration is not squared in the force computation, it varies linearly
with the force.

Note:
When you use RFVAR=FORCE with a time-assigned rotational load, for the start and end times
defined for a subcase on the TSTEP bulk entry, we recommend that you explicitly define an omega
value for those times on the TABLED1 entry referenced by the rotational load. If a start or end time
is not included on the TABLED1 entry, the software interpolates a value. Because RFVAR=FORCE
requests an interpolation using , the interpolated value may not be what you would have
explicitly defined for that time. The software issues a warning for this situation and continues the
solution using the interpolated value.
For example, a TABLED1 entry for a rotation load includes omega=10.0 at time=4.0, omega=20.0
at time=6.0, and no omega value at time=5.0. Because time=5.0 is defined as a subcase end time,
the software must interpolate a value for omega at time=5.0:
When RFVAR=FORCE, the interpolated value of omega is:

When RFVAR=OMEGA, the interpolated value of omega is:

RFVAR Example

Suppose you define solution times from 0.0 to 1.0 second in 5 increments, at time=0.0, f(t)=0.0, and at
time=1.0, f(t)=2.0.

Assume A=1.0, m is an identity matrix,

and , where is a unit vector.

The following table and plot shows the resulting values of and the resulting force magnitude for
this simplified input scenario.

7-66 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Interpolating rotational inertia loads

RFVAR=OMEGA RFVAR=FORCE

Time
0.0 0.0 0.0 0.0 0.0
0.2 0.4 0.16 0.894427 0.8
0.4 0.8 0.64 1.264911 1.6
0.6 1.2 1.44 1.5491933 2.4
0.8 1.6 2.56 1.788854 3.2
1.0 2.0 4.0 2.0 4.0

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-67
© 2023 Siemens
 7. Loads

7-68 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Interpolating rotational inertia loads

7.13 SOL 402 - Interpolating rotational inertia loads

You select a time-unassigned load with the LOAD=n case control command. Time-unassigned loads
are not explicitly defined with time varying scale factors, but they are ramped by the number of time
increments in a subcase. For example, if a subcase has 10 time steps, the software ramps the load in
1/10 increments at each time step.

When you define a time-unassigned rotational inertia load with the RFORCE or RFORCE1 bulk entry, the
software ramps the angular velocity and acceleration by the number of time increments defined in
the subcase.

The angular velocity is computed as:

where,

is the ramping load factor computed by the software for each time step,

is the rotation vector defined with the R1, R2, and R3 components on the RFORCEi entry,

and A is the scale factor of the angular velocity in revolutions per unit time defined on the RFORCEi
entry.

The inertia force as a result of the angular velocity is computed at each grid point using:

where,

m is the mass computed at the grid point,

and ri is a position vector to the grid point and ra is the position vector to the grid point location through
which the rotation vector acts. See the graphic in the remarks of the RFORCE or RFORCE1 entry for a
definition of the position vectors.

The RFVAR parameter is available on the NLCNTL2 bulk entry to change how the software interpolates
the ramping load factor .

• When RFVAR=OMEGA (default), the software interpolates the time variation using .

As a result, the angular velocity varies linearly. The force does not vary linearly because is squared in
the force computation.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-69
© 2023 Siemens
 7. Loads

• When RFVAR=FORCE, the software interpolates the time variation using . The software then
takes the square root of the interpolated value before applying it to the angular velocity.

As a result, the force varies linearly, but does not.

Note that the RFVAR parameter setting changes the interpolation only for angular velocity, and not for
angular acceleration. Because the angular acceleration is not squared in the force computation, it varies
linearly with the force.

For example, suppose you define solution times from 0.0 to 1.0 second in 5 increments, at time=0.0,
f(t)=0.0, and at time=1.0, f(t)=1.0.

Assume A=2.0, m is an identity matrix,

and , where is a unit vector.

The following table and plot shows the resulting values of and the resulting force magnitude for
this simplified input scenario.

RFVAR=OMEGA RFVAR=FORCE

Time
0.0 0.0 0.0 0.0 0.0
0.2 0.4 0.16 0.894427 0.8
0.4 0.8 0.64 1.264911 1.6
0.6 1.2 1.44 1.5491933 2.4
0.8 1.6 2.56 1.788854 3.2
1.0 2.0 4.0 2.0 4.0

7-70 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Interpolating rotational inertia loads

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 7-71
© 2023 Siemens
 7. Loads

7-72 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 8. Contact conditions (SOL 401)
8.1 Contact Overview
SOL 401 supports surface-surface and edge-edge contact. The algorithm supports large deformations
and finite sliding between contact pairs. For large deformation problems (LGDISP>-1), the contact
stiffness and contact forces are rotated with the geometry consistent with other element formulation in
SOL 401. The SOL 401 contact algorithm updates the geometry and pairing when there is finite sliding
between the contacting surfaces.

In addition, contact conditions are supported with the restart capability.

Contact is modeled using a contact set, contact regions, contact segments and contact pairs.

The table below lists the case control commands and bulk entries used to define contact.

Contact definition summary

Case control commands:

BCSET Selects a contact set.
BCRESULTS Selects contact results to output.
Bulk entries related to edge or surface definition:
BSURF Defines contact region on shell elements.
BCPROP Defines contact region on shell elements by property ID.
BSURFS Defines contact region on 3-D solid elements.
BCPROPS Defines contact region on 3-D solid elements by property ID.
BEDGE Defines contact region on 2-D axisymmetric, chocking, plane strain and
plane stress elements.
BCRPARA Defines parameters for contact region.
Bulk entries related to contact set definition:
BCTSET Defines the contact sets.
BCTADD Defines a union of contact sets.
BCTPARM Defines parameters for contact sets.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-1
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.2 Contact Subcase Control

The BCSET case control command selects the contact conditions defined in the bulk data. The BCSET
command can be defined in any static, dynamic, or bolt preload subcase type. For example, you can
remove or add contact regions and pairs, and change contact settings including parameters, from one
static or preload subcase to the next.

The modal, cyclic, and Fourier subcase types which are sequentially dependent (default) use the final
stiffness from a previous static or bolt preload subcase. The final stiffness from a static, dynamic, or
preload subcase includes the contact stiffness.

Note that if a subcase is sequentially dependent and it includes a new contact set, any contact tractions
from a previous subcase will be used as an initial condition for the current subcase. The previous
tractions define the initial condition for the newly formed contact elements.

8-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Definition

8.3 Contact Definition

Edge Contact Regions

An edge contact region is a collection of axisymmetric, chocking, plane strain, and plane stress element
free edges in a section of the model where you expect contact to occur. You create edge regions with
the BEDGE bulk entry.

• To define a contact edge using the BEDGE entry, you enter the element ID along with the corner GRID
IDs. You can define the edges on the BEDGE entry in any order.

Edge-to-edge contact can be defined on the edges of the following elements:

• Axisymmetric elements CTRAX3, CQUADX4, CTRAX6, CQUADX8.

• Chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8.

• Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

• Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8.

The axisymmetric, chocking, plane stress, and plane strain elements can be defined in either the XZ
plane or in the XY plane. Edge-to-edge contact is supported in either orientation. The generalized plane
strain element is not supported by glue or contact regions.

Surface Contact Regions

A surface contact region is a collection of element free faces in a section of the model where you expect
contact to occur. These regions can be created using the shell elements (BSURF and BCPROP) and using
solid element free faces (BSURFS and BCPROPS).

• The BSURF entry is defined by its own unique ID and is a list or range of shell element IDs to include in
the region.

• The BCPROP entry is defined by its own unique ID and is a list of shell element property IDs. Shell
elements which use any of these listed property IDs will be included in the region.

• The BSURFS entry is defined by its own unique ID and is a list of solid element IDs each followed by 3
grid points defining which face of the 3-D element to include in the contact region.

• The BCPROPS entry is defined by its own unique ID and is a list of solid element property IDs. The free
faces of the solid elements selected with a property ID are automatically determined by the software.

Surface-to-surface contact can be defined on the faces of the following elements.

• 3-D Solid elements CHEXA, CPENTA, CPYRAM, and CTETRA.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-3
© 2023 Siemens
 8. Contact conditions (SOL 401)

• Shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, and CTRIA3.

A contact surface can be defined with any face of a solid element. Although parabolic faces with omitted
midside grid points are permitted, their use could affect accuracy. All region IDs defined with the BSURF,
BCPROP, BSURFS, BCPROPS, and BEDGE entries must be unique.

Contact Region Parameters

The contact region parameter OFFSET can be defined using the BCRPARA bulk entry. The CRID field on
BCRPARA must match the ID used on one of the BSURF, BCPROP, BSURFS, BCPROPS, and BEDGE bulk
entries to be considered by the solution. The OFFSET parameter is supported with surface-to-surface and
edge-to-edge contact definitions.

Use the OFFSET field to account for a rigid layer between contact face or edge regions. For example, a
model which has two metal surfaces coming into contact, and one of these has a ceramic coating. If
the ceramic material stiffness is not significant enough to be included in the analysis, it may not have
been specifically modeled, but the thickness it adds to the face of the metal may be important when
considering the contact problem.

You can also use the OFFSET field to analyze an interference fit problem if unconnected elements are
modeled coincident. The offset value in this example can represent the theoretical interference.

• The option to increment contact offsets is available. For subcases which have a constant time*, the
software automatically increments the contact offset using the number of increments. The number
of increments is defined with either the Ninc field on the TSTEP1 entry, or with the Ninc field on the
BOLTSEQ entry.

8-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Definition

Note that the number of increments also increments loads and temperatures. The incrementing of the
contact offsets, loads, or temperatures helps the solution converge by reducing the changes which
occur in an increment.

*A constant time subcase has a TSTEP1 bulk entry defined with either Tend=0.0, or a Tend which is
the same as the start time for that subcase.

• When a sequentially dependent subcase is defined with SEQDEP=YES, the final contact offset from
a previous subcase, if it exists, is included at the start of the current subcase. The goal is to help
convergence when contact offsets change from one subcase to the next. In this case, the offset for the
current subcase is calculated as:

OFFSET = OC*LF+OP*(1 - LF)

Where:
OC = Contact offset for the current subcase,
OP = Contact offset from a previous subcase,
and LF = Load factor incremented in Ninc steps. The initial value is 1/Ninc and the final value is 1.0.

• General recommendations for offset definitions:

- A separate subcase is recommended to resolve the contact offset.

- When bolt preloads and contact offsets are defined together, be aware that both can result in axial
bolt strain. If you do not want the contact offset to result in an additional bolt strain, the contact offset
should be modeled with a slight gap.

• You can optionally change the contact offset definition from one subcase to the next by selecting
unique contact sets in each subcase which reference different BCRPARA bulk entries.

Contact Pairs

A contact pair combines two contact regions, source and target, in which contact will be analyzed
during the solution. Each contact pair can have its own unique friction value (if desired) and search
distance.

The BCTSET bulk entry is used to define both edge-to-edge and surface-to-surface contact pairs. The CID
field will need to match the value of ‘n' on the BCSET case control entry for the solution to recognize this
contact definition.

The SIDi and TIDi fields on the BCTSET bulk entry are used to define source and target regions
respectively for a pair. As many pairs as desired can be included on a single BCTSET entry. Each pair can
have a unique friction value (optional), a minimum search distance, and a maximum search distance.
You can define the optional Coefficient of Friction field (FRICi) for each contact pair. When contact is
detected, the solver uses this value to calculate any tangential contact forces.

The regions you select with SID and TID depend on the type of contact:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-5
© 2023 Siemens
 8. Contact conditions (SOL 401)

• For edge-to-edge contact pairs, SID and TID are contact regions defined with the BEDGE entry.

• For surface-to-surface contact pairs, SID and TID are contact regions defined with the BCPROP,
BCPROPS, BSURF, and BSURFS entries.

The minimum and maximum search distance fields (MINDi and MAXDi) define a range in which the
solver can initially determine if the distance between element edges or faces in a particular pair are
within the threshold for creating contact elements. These values are used to determine where contact
elements are created. The minimum distance can be negative if there is an interference condition
modeled as overlapping regions.

The contact condition can update when large sliding occurs when large displacement effects are turned
off (PARAM,LGDISP,-1) or on (PARAM,LGDISP,1).

Combining Contact Sets – BCTADD

You can optionally define multiple BCTSET/BCTPARM bulk entry sets, each set with unique contact set
IDs (CSID), and then combine them with a single BCTADD bulk entry. The multiple BCTSET/BCTPARM
bulk entry sets are created to adjust certain contact parameters locally. Contact parameters can also be
adjusted globally with a BCTPARM bulk entry having the same CSID as the BCSET case control command.

The following example demonstrates the inputs.

CASE CONTROL
$CSID on the BCSET case control matches CSID on BCTADD
BCSET = 108
...
BULK DATA
$Local Contact Set definitions
BCTSET 1 1 2 0.0 1.0
BCTSET 2 3 4 0.15 0.0 0.1
5 6 0.15 0.0 0.1
...
$Local Contact Parameters
BCTPARM 1 PENN 10 PENT 1
BCTPARM 2 PENN 1.0 PENT 0.1
...
$Local Contact Sets are combined with BCTADD
BCTADD 108 1 2
...
$Global Contact Parameters
BCTPARM 108 MAXS 30 NCHG 0.02

See the section Contact Control Parameters - BCTPARM for more information on contact parameters.

Contact with Composite Solid Faces

8-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Definition

Defining contact regions and pairs on composite solid faces which are perpendicular to the stack
direction (edge faces) may produce poor stress continuity. If the contact definition is between edge faces
belonging to different PCOMPS definitions, and if the number of plies on each PCOMPS definition is small
and the same, and the ply thicknesses are similar, the stress continuity should be fairly smooth. This also
applies to the results requested with the BCRESULTS case control command.

Additional Recommendations

When defining contact regions and pairs on geometry which are not tangent continuous, creating
single contact regions which cross corner transitions can result in non-uniform stress results around the
corners. It is recommended to break these areas into multiple regions and pairs as shown below.

When defining contact regions and pairs, it is recommended to not include the same element face in
multiple regions. In “A” below, an element is repeated in regions 2 and 3. In “B”, the same element only
exists in region 2. “B” is recommended. Repeating element faces multiple times in the same or different
regions can significantly increase memory requirements and degrade performance.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-7
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.4 Contact Control Parameters

The contact control parameters on the BCTPARM bulk entry can help you adjust the contact algorithm
when you are having problems getting a solution to converge and complete, or when the contact results
are not as expected. For many solutions, the default settings are appropriate, and the BCTPARM entry is
not required.

You can optionally define multiple BCTSET/BCTPARM bulk entry sets, each set with unique contact set
IDs (CSID), and then combine them with a single BCTADD bulk entry. The multiple BCTSET/BCTPARM
bulk entry sets are created to adjust certain contact parameters locally. Contact parameters can also be
adjusted globally with a BCTPARM bulk entry having the same CSID as the BCSET case control command.

Global and local contact parameters have the following definition and rules:

• Global Contact Parameters

The BCTPARM bulk entry, which uses the same CSID entered on the BCSET case control command,
defines global parameters.

Any of the parameters on the BCTPARM bulk entry can be defined globally. A parameter’s default value
is used if it is not defined globally or locally.

• Local Contact Parameters

The BCTPARM bulk entries associated to individual BCTSET bulk entries, which are then combined with
a BCTADD bulk entry, define local parameters.

See the Parameters for SOL 401 listed on the BCTPARM bulk entry in the Quick Reference Guide.

8-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

8.5 Contact kinematics

Consider the contact element between the points S and T in the figure below. S and T are the parametric
locations of a contact element on the source and target faces respectively.

S1, S2, S3, S4,...Sj are the grid points defining one solid element face which is included in the source
region.

T1, T2, T3, T4,...Tj are the grid points defining one solid element face which is include in the target
region.

Figure 8-1. Contact Source and Target Example

The global system of equations including contact at a given iteration i is:

Equation 8-1.

Where:

is the assembled contact stiffness,

is the assembled nodal contact forces,

NCE is the total number of contact elements created,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-9
© 2023 Siemens
 8. Contact conditions (SOL 401)

Kc is the contact stiffness from a single contact element,

and Fc are the contact forces from a single contact element,

The total traction for a contact element c at an iteration i can be split into normal and tangential
components as:

Equation 8-2.

where is the normal vector, and the tangential vector is .

Together , t1, and t2 form an ortho-normal basis.

Normal contact conditions

The normal contact conditions can be expressed as:

Equation 8-3.

Equation 8-4.

Equation 8-5.

8-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

Equation 8-3 imposes the condition that the penetration of the hitting surface into the target surface
can’t be greater than zero. Thus, surfaces can’t interpenetrate. The contact pressure, , is defined as
the negative of the normal component of the surface traction.

Equation 8-4 states that the contact pressure can’t be less than zero or tensile. Or normal tractions
between surfaces can’t be tensile.

Equation 8-5 imposes the condition that:

and

SOL401 uses a penalty method to enforce the contact constraints with the ability to augment the
tractions (Augmented Lagrangian formulation) to keep the penetrations to within a specified tolerance
(PTOL).

The pure penalty method can be activated by setting MAXS=1 on BCTPARM bulk data entry. Pure penalty
method is computationally in-expensive and in most cases produces acceptable solution. However, since
there is no check on penetration control this method can sometime cause large penetrations in the
model that could go undetected.

Augmented Lagrangian formulation is the default. With this method, first a converged solution is
obtained with a penalty method. If the convergence criteria have not been achieved, the tractions are
augmented and another series of iterations is performed until convergence is achieved. The tractions
could be augmented several times until either the desired level of penetration tolerance (PTOL) is
achieved when the convergence criteria is based on penetrations or alternately the tractions between
two augmentations are converged to a value below CTOL for convergence criteria based on augmented
tractions. MAXS (default=20) parameter specifies the maximum number of augmentations that are
performed for every time step. If the augmentation convergence is not achieved within MAXS number
of iterations the solution will proceed to the next step if the usual global convergence criteria have been
satisfied.

The normal traction is:

Equation 8-6.

is the normal traction from previous augmentation.

Note that =0 for the pure penalty method.

εn is the normal penalty stiffness (unit=force/length),

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-11
© 2023 Siemens
 8. Contact conditions (SOL 401)

is the contact element normal gap evaluated at iteration i,

K is the augmentation loop ID.

The relative displacement at a contact element location for iteration i is computed as:

Equation 8-7.

The contact element normal gap at iteration i is calculated as

Equation 8-8.

Equation 8-9.

Nj = Standard Source Face shape functions evaluated at the contact point

N'k = Standard Target Face shape functions evaluated at the contact point

Ns = Number of nodes on source face

Nt = Number of nodes on target face

Xs=X0s + Us

Xt=X0t + UT

8-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

X0s = Undeformed coordinates of the nodes on the source face

X0t = Undeformed coordinates of the nodes on the target face

Us = Nodal displacements on the source face

Ut = Nodal displacements on the target face.

Note that a positive value of indicates an overlap and a negative value indicates a separation
between the source and target faces at the contact element location.

Consequently a contact element is considered CLOSED if > 0 and OPEN if < 0.

The tangential traction is

Equation 8-10.

where,

λnt is the tangential traction from previous step.

εt is the tangential penalty factor (unit=force/length),

is the relative displacement increment in the tangential direction since last time step where j = 1,
2.

The relative displacement increment in the tangential direction is calculated as:

Equation 8-11.

where,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-13
© 2023 Siemens
 8. Contact conditions (SOL 401)

Equation 8-12.

(ΔUs) = Nodal displacement increment since last time step on the source side DOF.

(ΔUt)= Nodal displacement increment since last time step on the target side DOF.

A contact element can have the following states:

Inactive when < 0.

Active when > 0.

Coulomb Friction

If friction is present (μ > 0 where μ is the coulomb friction coefficient), an active contact element can
have either sticking or sliding state.

Similar to the normal contact conditions, the frictional contact conditions can be expressed as:

Equation 8-13.

Equation 8-14.

8-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

Equation 8-15.

Equation 8-16.

Equation 8-13 imposes the constraint that the magnitude of the in-plane friction traction, , cannot
exceed the coefficient of friction μ, times the normal contact traction. When the magnitude of friction
force reaches its maximum allowable value, the function Φ will be equal to zero.

Equation 8-14 relates the relative tangential displacement increment between the source and the target
surface, , to the magnitude of the relative slip increment, , which must be a non-negative
quantity.

Equation 8-16 implies that if ≥ 0 (there is slipping between the surfaces), then Φ= 0, and if =
0 (the surfaces are sticking), then Φ ≤ 0.

Therefore, for Coulomb friction:

• The maximum possible tangential traction equals the coefficient of friction times the normal traction
force.

• Contacting surfaces will "stick" if the tangential traction is less than the coefficient of friction times the
normal traction force.

• Contacting surfaces will "slide" in the direction of the tangential traction if the tangential traction
equals the coefficient of friction times the normal traction force.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-15
© 2023 Siemens
 8. Contact conditions (SOL 401)

Figure 8-2. Classical Coulomb Friction Model (FRICMOD=0)

Assume

A contact element state is Sticking if

Equation 8-17.

and Sliding if

Equation 8-18.

Bilinear Coulomb Friction (FRICMOD=1)

8-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

Figure 8-3. Bi-Linear Coulomb Friction Model

By default, SOL401 uses a bi-linear coulomb model specified by FRICMOD=1 on BCTPARM. This model
converges better than the classical model (FRICMOD=0) by providing a more distinct stick slip zone.
Here, the tangential penalty factor ɛT is adaptively computed based on the current contact pressure,
coefficient of friction and a critical slip value Scrit provided by the user. The default for Scrit is set at 0.5%
of the characteristic element length in the pair. A larger value of Scrit helps with easier convergence but
leads to more sliding, while a smaller value represents the exact coulomb behavior more closely but also
leads to slower convergence rates. The tangential stiffness is updated every iteration using:

Equation 8-19.

The incremental tangential relative displacement can be expressed as a sum of elastic and plastic parts.

Equation 8-20.

or

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-17
© 2023 Siemens
 8. Contact conditions (SOL 401)

Equation 8-21.

where is the elastic slip at the end of previous step.

The predictor slip is

Equation 8-22.

The trial tangential traction is evaluated from the predicted slip as:

Equation 8-23.

This predicted slip is elastic as long as the magnitude of the tangential traction is less than the critical
stress (i.e.) .

If the magnitude of the tangential traction exceeds the critical stress then slip must be taken into
account.

The magnitude of the plastic slip in this instance is given by where is the
magnitude of the predicted slip.

The incremental slip is computed as:

Equation 8-24.

8-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

When the slip output is requested, the total slip is computed as the algebraic sum of the incremental
slip (elastic and plastic) over time. The incremental slip is the difference in total slip between two output
intervals.

Additional friction models:

FRICMOD=2: Friction is computed using the following product which optionally depends on time,
velocity or temperature:

μ(t,T,v)= FPARA1 * CFVE(v) * CFTE(T) * CFNF(t)

FPARA1, CFNF, CFTE, and CFVE are all parameters defined on the BCTPARM entry. FRICi on the BCTSET
entry is ignored.

FPARA1 defines a constant friction value, and CFNF, CFTE, CFVE are integer inputs which reference
TABLEDi entries defining friction as a function of time, temperature, and velocity, respectively. If any of
CFNF, CFTE, or CFVE are undefined, their contribution is ignored.

FRICMOD=3: Two different friction coefficients are used depending on the sliding velocity.

This friction model uses the parameters VCRIT, FPARA1, and FPARA2 on the BCTPARM entry. FRICi on the
BCTSET entry is ignored.

VCRIT defines the critical sliding velocity, FPARA1 (1 in the image below) defines the friction coefficient
when the sliding velocity < VCRIT, and FPARA2 (2 in the image below) defines the friction coefficient
when the sliding velocity > VCRIT.

Figure 8-4. FRICMOD=3 Friction Model

FRICMOD=4: Friction coefficient varies linearly with the sliding velocity.

This friction model uses the parameters FPARA1, VCRIT, and FPARA2 on the BCTPARM entry. FRICi on the
BCTSET entry is ignored.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-19
© 2023 Siemens
 8. Contact conditions (SOL 401)

FPARA1 defines the friction coefficient at zero velocity, VCRIT defines the critical sliding velocity, and
FPARA2 defines the friction coefficient at the critical sliding velocity. The friction varies linearly between
FPARA1 (1 in the image below) and FPARA2 (2 in the image below), up to the critical sliding velocity
VCRIT after which it remains constant.

Figure 8-5. FRICMOD=4 Friction Model

Contact Force

The contact nodal force contribution due to all active contact elements at iteration i is computed as
follows:

Equation 8-25.

Equation 8-26.

Contact Stiffness

From the normal component of traction we have:

8-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

Equation 8-27.

For a sticking contact element with friction,

Equation 8-28.

For a slipping contact element,

Equation 8-29.

The contact stiffness contribution after ignoring the variation of friction coefficient with pressure and
sliding velocity is:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-21
© 2023 Siemens
 8. Contact conditions (SOL 401)

Equation 8-30.

Equation 8-31.

Equation 8-32.

The global contact stiffness is obtained by summing the stiffness contribution from all active contact
elements:

Equations 8-31 and 8-32 include non-symmetric stiffness terms. Using an un-symmetric solver will
significantly increase the memory requirements. The software automatically activates the un-symmetric
solver if the coefficient of friction is greater than FSYMTOL. The parameter FSYMTOL (specified on
NLCNTL) has a default value of 0.2.

Contact Iterations

8-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact kinematics

The contact problem is solved by a dual loop algorithm with the augmentation loop serving as
the outer loop and the regular NR iterations constituting the inner loop. In addition to the global
criteria to determine the inner iterations convergence, contact algorithm also checks for contact force
convergence. The inner loop is said to be converged if the change in contact force between two
consecutive iterations is < RCTOL. After the convergence of the inner loop (i.e.) NR iterations, the
tractions are augmented if needed and another round of inner iterations is done until either of the
following 2 criteria is met:

1. CNTCONV=1. In this case the outer loop convergence criteria are based on penetration tolerance.
The augmentations are performed until the max penetration in each contact pair is below the
tolerance PTOL.

2. CNTCONV=2. In this case the outer loop convergence criteria are based on contact traction
convergence ratio CTOL. The contact tractions are augmented until the augmented force ratio
FRAT change in the tractions between two consecutive augmentation loops is converged to a value
smaller than CTOL.

where c is a contact element, NCE is the total number of contact elements, λk is the contact
traction at a contact element, k is the augmentation loop number.

Contact Algorithm Flowchart

Steps 1 through 4 occur for each time step (n+1).

1. Loop over contact augmentations (K=1 to MAXS).

a. Initialize λkn .

b. Compute stiffness K and Kc.

2. Do Newton-Raphson iterations (i=1 to MAXITER).

a. Compute internal forces and where is the force contribution from contact.

b. Compute Residual

c. Solve (see equations 8-30 through 8-32 ).

d. Check for the solution convergence based on global criteria and RCTOL. The global solution
convergence criteria are defined by the CONV parameter on the NLCNTL bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-23
© 2023 Siemens
 8. Contact conditions (SOL 401)

A. If the solution convergence criteria are satisfied, go to step 3.

B. If the solution convergence criteria is not satisfied:

i. If (i < MAXITER) then do more iterations, go to 2a or if stiffness update is required,

go to step 1b.

ii. If (i = MAXITER) then convergence is not achieved and end problem. GO TO step 4.

3. Check outer loop convergence for contact based on either PTOL or CTOL.

a. If the contact outer loop is converged, end the problem. Go to step 4.

b. If the outer loop is not converged, increment the outer loop counter, augment the tractions,
and go to step 1b.

4. End Problem.

8-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Penalty Factors

8.6 Contact Penalty Factors

The normal penalty stiffness εn and the tangential penalty stiffness εT are computed for each contact
element as follows:

εn = Ac * E * PENN

εT = Ac * E * PENT

PENN and PENT are the normal and tangential penalty factors respectively. Ac is the area associated with
the contact element and E is the modulus of the softer region in the contact pair.

Note: If elements in your contact regions include material nonlinear, by default the initial contact
modulus E computed at the start of the solution is used throughout the solution. You can define
SYSTEM(740)=1 and the software will update the contact modulus if the underlying element undergoes
plastic deformations.

The normal penalty is computed by the contact algorithm or can be input by the user. The automatic
penalty factor calculation estimates geometry characteristics using element edge lengths in the vicinity
of the contact regions. The solver computes a characteristic length Lc for each contact pair and estimates
the normal penalty factor PENN as PENN = 1 / Lc. The default value of PENT is an order of magnitude
smaller than the PENN.

When the option to adaptively compute the tangential stiffness is selected, the tangential penalty factor
is adjusted based on current contact pressure, coefficient of friction and critical slip parameter.

PENT = μ * Tn / Scrit

The penalty factors influence the rate of convergence, and to a lesser extent, the accuracy of the
contact solution. The automatic penalty factor calculation works well for most instances, but manual
adjustments may be necessary, particularly if a contact problem fails to converge. When the problem
fails to converge or takes a lot of iterations to converge, reducing the default value of PENN by an order
or two of magnitude will generally help with convergence.

A large value of PENN will make the system of equations ill-stabled leading to convergence problems.
They could also produce spotty contact pressure results. In addition, a small value of PENN may cause
excessive penetrations which will require more traction augmentations. So the right choice of penalty
factors is the key to getting good quality contact stress results in a reasonable number of iterations.

The software provides an alternate way (PENTYP=2) to input PENN and PENT as spring rate per area.
That is, Force/(Length x Area). The contact element stiffness in this case is calculated as:

εn = Ac * PENN

εT = Ac * PENT

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-25
© 2023 Siemens
 8. Contact conditions (SOL 401)

The spring rate input is a more explicit way of entering contact stiffness since it is not dependent on the
modulus.

The auto-calculated values for PENN and PENT can be scaled using the AUTOSCAL and TANSCL
parameters respectively. The range for AUTOSCAL is usually 0.01 - 1.0 with the default being 1.0.
The default works well for bulk deformation dominant problems. For bending dominant or finite sliding
problems, a smaller range 0.01 - 0.1 is recommended.

8-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Contact and glue characteristic length

8.7 SOL 401 - Contact and glue characteristic length

The software computes a characteristic length for contact and glue pairs and uses the value for
the penalty stiffness calculation as well as penetration tolerance calculations. The software-computed
penalty stiffness is proportional to the inverse of the characteristic length.

By default, the characteristic length for shell element regions is computed using the element face
geometry. It is computed by averaging the square roots of the element face areas in the source and
target regions. This computation is appropriate for all shell element regions.

You can define SYSTEM(780)=0, and the characteristic length for shell element regions is computed
using the average thickness of the elements. This was the default computation before Simcenter
Nastran version 2206. This calculation is only appropriate when a meaningful thickness is defined for the
shell elements in the contact/glue regions. If you include very thin shell elements in your region, this
calculation can be inappropriate.

The SYSTEM(780) options are as follows.

SYSTEM(780) Characteristic length calculation

=1 (Default) The characteristic length is computed using the face geometry of all shell and solid
element faces in the regions. It is computed by averaging the square roots of the
element face areas in the source and target regions.
=0 Characteristic length is computed using the element thickness over all shell elements in
the regions.
• Case 1: When both the source and target are shell element regions.
Characteristic length= 0.5*(average_source_thickness + average_target_thickness)/2
• Case 2: When the source is a shell element region but the target is not.
Characteristic length= 0.5* average_source_thickness
• Case 3: When the target is a shell element region but the source is not.
Characteristic length= 0.5* average_target_thickness

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-27
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.8 SOL 401 - Tangential contact stiffness in sequentially

dependent modal subcases
When sequencing from a nonlinear subcase (PRELOAD, STATIC, DYNAMICS) that includes contact to
a modal subcase (MODES, CYCMODES, FOURIER), the parameter KMODTN on the NLCNTL bulk entry
allows you to select a different tangential contact stiffness for the modal subcase than was used in
the previous nonlinear subcase. It can be used, for example, when the nonlinear subcase required
frictionless contact, yet the modal subcase needs a tangential contact stiffness to prevent spurious rigid
body modes. KMODTN is only used in the modal subcases.

The KMODTN parameter settings allow you to independently control the tangential contact stiffness of
the contact pairs with friction (A), and without friction (B).

A: Contact pairs with friction are defined by INTRFC=1 and FRICMOD=0 or 1 on the BCTPARM bulk entry
with FRICi>0.0 on the BCTSET bulk entry.

B: Contact pairs without friction are defined either by INTRFC=4 on BCTPARM, or by INTRFC=1 and
FRICMOD=0 or 1 on the BCTPARM bulk entry with FRICi=0.0 on the BCTSET bulk entry.

KMODTN Friction
Setting status Tangential contact stiffness in modal subcase
The software applies a uniform tangential contact stiffness of (0.1 *
A
normal stiffness) in a modal subcase.
1
The software does not apply tangential contact stiffness in a modal
B
subcase.
The software applies the actual final tangential contact stiffness from the
A end of a nonlinear subcase in a modal subcase. The applied tangential
2 contact stiffness can be a mixture of sticking and sliding stiffness values.
The software does not apply tangential contact stiffness in a modal
B
subcase.
The software applies the actual final tangential contact stiffness from the
A end of a nonlinear subcase in a modal subcase. The applied tangential
3 contact stiffness can be a mixture of sticking and sliding stiffness values.
The software applies a uniform tangential contact stiffness of (0.1 *
B
normal stiffness) in a modal subcase.
A The software applies a uniform tangential contact stiffness of (0.1 *
4
B normal stiffness) in a modal subcase.
A The software replaces the final stiffness of any active contact element
B at the end of the nonlinear subcase with a no-separation, tied-contact
stiffness in both the normal and tangential directions, regardless of the
5
friction value. The tied-contact stiffness applied in the modal subcase is
similar in magnitude to the normal and tangential stiffness resulting from
a glue condition.

8-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Tangential contact stiffness in sequentially dependent modal subcases

In addition, you can define the KMODSCL parameter on the NLCNTL bulk entry to scale the software-
computed normal contact stiffness for the modal subcase. You can use the KMODSCL parameter with
any of the KMODTN parameter options (1-5).

By default, KMODSCL=1.0 and the normal contact stiffness used in the modal subcase is not scaled.

Note: In Simcenter Nastran 2020.1, system cells 733 and 752 were introduced to allow you to select
a different tangential contact stiffness for the modal subcase than was used in the previous nonlinear
subcase.

Beginning in 2021.1, you now use the KMODTN parameter on the NLCNTL bulk entry to request these
options. The system cells 733 and 752 are no longer supported.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-29
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.9 Contact Sliding and Geometry Update

The contact element locations on the element faces or edges are updated based on the value of the
DISP, GUPDATE, and GUPTOL parameters.

The DISP parameter on the BCTPARM bulk entry is available to select the sliding formulation. The
software only considers your GUPDATE and GUPTOL parameter settings when you use the DISP = 0
option.

DISP Behavior
0 (Default) Contact pairing is automatically determined by the software based on the
amount of relative sliding in the pair. The software considers your GUPDATE
and GUPTOL parameter settings (described below). If you have not explicitly
defined the GUPDATE and GUPTOL parameters, the default values are used.
1 Small sliding formulation. Contact pairing is not updated with sliding
displacements and is based on the initial geometry. The software internally
sets GUPDATE to 0 (no pairing update).
2 Large sliding formulation. Contact pairing is updated with sliding
displacements. The software internally sets GUPDATE to 4 (update every
iteration).

GUPDATE controls the frequency of the update and the GUPTOL determines whether a geometry update
is needed depending on the amount of relative sliding between the contact regions. The default for
GUPTOL is set at 25% of the characteristic element length in the pair. The default for GUDPATE is 2 for
large displacement analysis (LGDISP=1). By default, for a small displacement analysis (LGDISP=-1), the
contact pairing is updated at the start of each step.

If large enough sliding occurs within the defined tolerance, contact elements are recreated in the current
deformed configuration, and the relevant contact data like the contact stresses and slip for example, are
all mapped from the old to the new contact elements.

The following table summarizes the geometry update options for both small and large displacement
analysis.

GUPDATE Behavior
0 No update to contact element locations.
1 Contact elements are updated if the relative sliding exceeds threshold set by
parameter GUPTOL.
2 Contact elements are updated if the relative sliding exceeds threshold set by
parameter GUPTOL, and are updated at the start of each step. Default when
LGDISP=1.
3 Update occurs only at the start of each step. Default for LGDISP=-1.
4 Update occurs every iteration.

The following table illustrates the geometry update process.

8-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Sliding and Geometry Update

Initial configuration

Sliding occurs during a step.

The slide in this example is
greater than the value of
GUPTOL. This will result in
an updated configuration as
shown in the next step below.
Contact configuration is
updated after the magnitude
of the slide exceeds the value
defined on the parameter
GUPTOL.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-31
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.10 Contact and rigid body motion

Many static problems depend on contact to provide the boundary conditions necessary for a stable
problem. With these problem types, the stiffness matrix can be singular when the contact constraints are
inactive. You can use the following options to avoid singularities.

• Stiffness stabilization

To allow a solution to complete with an unconstrained condition, a matrix stabilization option is

available. Setting the parameter MSTAB to 1 on the NLCNTL bulk entry will turn on the option.

In addition, the MSFAC parameter is available to define a scale factor for matrix stabilization.
Specifically, when you define MSTAB=1, the software scales the diagonal terms by the factor
(1+MSFAC).

• Displacement scaling

Limiting the maximum incremental displacement per iteration is useful when a load is applied to
a body that is not initially in contact. A model can be unstable even when stiffness stabilization or
open stiffness is used resulting in excessive initial displacement. Setting the limiting displacement to
about the element size in this case would scale down the potentially huge displacement in the first
iteration so that the results remain close to the converged solution. The displacement scaling feature
can be thought of as a form of line search. This option is on by default and can be turned off by
setting DISCAL=0 on the BCTPARM bulk entry. You can also adjust the limiting factor with the DISTOL
parameter on the BCTPARM bulk entry.

• Contact stabilization damping

In order to stabilize rigid body motion caused before contact is engaged, a damping force can be
applied to keep the parts from flying off. The stabilization normal damping force is computed as
follows:

where is the normal damping coefficient, is the pseudo relative velocity of the contact
surfaces in the normal direction.

The normal damping coefficient is internally calculated by the solver. You can either scale or overwrite
the auto computed damping coefficient by entering the value as a function of contact pressure per
velocity.

The damping coefficient is calculated based on the contact stiffness, contact gap and current solution
time with respect to the subcase end time.

8-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact and rigid body motion

where CTDAMPN is the scale factor with a default value of 1.0,

Krep is a fraction of the closed contact stiffness,

Gapfac = 0 when gap > opntol or gap < 0.

The default value for OPNTOL is equal to 1.0 (times average element length).

where Curtim is the current solution time and Send is the subcase end time.

Thus by default the effects of the damping are ramped down to zero by the end of the first subcase.

Also, once the contact is established the damping effects vanish.

When CTDAMP=1 or 2, the damping is applied to a contact pair only when the entire pair is open.
Even if one contact element in the pair is active, the stabilization stiffness is not applied. However,
when CTDAMP=3, the stabilization stiffness is applied for any contact element that is open with a gap
smaller than OPNTOL.

Also, When CTDAMP > 1, the damping is not ramped down as a function of time and will be applied
always.

Similar to normal damping coefficient, tangential damping coefficient is also computed when there is
friction. The tangential damping coefficient is computed as:

CT = CTDAMPT * CN where CTDAMPT is the tangential scale factor with default = 0.001.

The tangential damping force is thus calculated as:

Where is the pseudo relative velocity in the tangential direction.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-33
© 2023 Siemens
 8. Contact conditions (SOL 401)

Note that you should specify either contact damping with the CTDAMP parameter, or the open
stiffness value with the OPNSTF parameter, but not both. If both are defined, then the open stiffness is
set to 0.0 and the damping is used.

8-34 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Gaps, Penetrations, and Offsets

8.11 Contact Gaps, Penetrations, and Offsets

Initial contact gap calculation

In the contact segment figure below, SS is a source segment (facet) with nodes S1-S4 and TS is a target
segment with nodes T1-T4.

S(ξ,η) is a Gauss point on a source segment and T(ξ*,η*) is the corresponding projection of S along the
normal evaluated at S(ξ,η).

is the normal at T(ξ*,η*).

XS and XT are the physical coordinates of S and T.

The initial physical gap is computed by:

where,

Stbf= 1.0, or if the source surface for shell elements is BOTTOM, then Stbf= -1.0.

Ttbf= 1.0, or if the target surface for shell elements is BOTTOM, then Ttbf= -1.0.

After the software computes the initial gap, it applies the following parameters in this order:

• ADJUST parameter on the BCTPARM entry.

• SHLTHK parameter on the BCTPARM entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-35
© 2023 Siemens
 8. Contact conditions (SOL 401)

• INIPENE parameter on the BCTPARM entry.

• OFFSET parameter on the BCTPARM and BCRPARA entries.
• ZOFFSET parameter on the BCTPARM entry.

ADJUST parameter on the BCTPARM entry

The ADJUST parameter requests that the software move the grid points when there are gaps. The
adjustment is applied at the start of the solution based on the initial geometry.

When you use the ADJUST parameter on the BCTPARM bulk entry, the software uses an adjustment
tolerance to move the source grid points onto the target faces when the absolute value of the initial
separation distance is within the adjustment tolerance.

Note: ADJUST works from the grid point locations and INIPENE works from the Gauss point locations. If
both are defined, ADJUST is first applied, then INIPENE.

• ADJUST = 0.0: Only the grid points that are initially overclosed are adjusted as long as the over-closure
is below the characteristic length (CLEN).

Initial physical gap is adjusted to 0.0 if -CLEN < gini< 0.0

• ADJUST > 0.0: The adjustment is applied to grid points that are initially open with a gap smaller than
the value of ADJUST * characteristic length.

Initial physical gap is adjusted to 0.0 if -CLEN < gini< ADJUST * CLEN

• ADJUST < 0.0: The software will adjust both the initially overclosed and the initially separated grid
points when either is smaller than the absolute value of ADJUST.

SHLTHK parameter on the BCTPARM entry

SHLTHK is the shell thickness offset flag. By default, the contact surface is assumed to be offset t/2 from
the nodes defining a shell element. If the FE mesh represents the outer surface, set this value to 1 so the
thickness offset will be ignored.

Let Sthk and Tthk be the half shell thicknesses at S and T (interpolated from nodal thicknesses Si and Ti,
respectively).

Initial penetration is computed as:

where,

8-36 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Gaps, Penetrations, and Offsets

INIPENE parameter on the BCTPARM entry

The INIPENE parameter requests that the software reset a gap or penetration to a new initial condition.
The INIPENE options are as follows.

• INIPENE = 0 (default): The software does not reset a gap or penetration.

• INIPENE = 1: Gaps are reset to a new initial condition.

When pini<0.0 and INIPENE=1; the initial penetration is reset to pini=0.0.

• INIPENE = 2: Penetrations are reset to a new initial condition in which there is no interference.

When pini>0.0 and INIPENE=2; the initial penetration is reset to pini=0.0.

• INIPENE = 3: Gaps and penetrations are both reset to a new initial condition in which there is no
interference. A constant gap can also be defined with the GAPVAL parameter on the BCTPARM entry.

When INIPENE=3; the initial penetration is reset to the following:

Contact surface offsets

An offset distance can be specified for a contact region on the BCRPARA entry, and for a contact pair on
the BCTPARM bulk entry. The OFFSET parameter on the BCTPARM bulk entry overwrites an offset defined
for a region on the BCRPARA entry.

In addition for shell element regions, the ZOFFSET parameter on the BCTPARM entry determines if
the shell element z-offset is included in the contact solution. By default, shell z-offsets are included.
ZOFFSET=1 will prevent them from being included.

Let Soff and Toff be the region offsets.

If OFFSET is defined as a parameter on BCTPARM then the region offsets defined on BCRPARA are
ignored. In this case, Soff=Toff=OFFSET/2

Let Szoff and Tzoff be Z-offsets on the source and target, respectively.

The net penetration is computed with:

Addition offset details:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-37
© 2023 Siemens
 8. Contact conditions (SOL 401)

• A separate subcase is recommended to resolve the contact offset prior to the application of service
loads. The offsets can be resolved incrementally based on the value of NINC parameter on the TSTEP1
bulk entry.

• When bolt preloads and contact offsets are defined together, be aware that both can result in axial
bolt strain.

• The option to increment contact offsets is available. For subcases that have a constant time*, the
software automatically increments the contact offset using the number of increments. The number
of increments is defined with either the Ninc field on the TSTEP1 entry, or with the Ninc field on the
BOLTSEQ entry.

Note that the number of increments also increments loads and temperatures. The incrementing of
the contact offsets, loads, or temperatures helps the solution converge by reducing the changes that
occur in an increment.

*A constant time subcase has a TSTEP1 bulk entry defined with either Tend=0.0, or a Tend, which is
the same as the start time for that subcase.

• When a sequentially dependent subcase is defined with SEQDEP=YES, the final contact offset from
a previous subcase, if it exists, is included at the start of the current subcase. The goal is to help
convergence when contact offsets change from one subcase to the next. In this case, the offset for the
current subcase is calculated as:

OFFSET = OC*LF+OP*(1 - LF)

Where:
OC = Contact offset for the current subcase,
OP = Contact offset from a previous subcase,
and LF = Load factor incremented in Ninc steps. The initial value is 1/Ninc and the final value is 1.0.

• You can optionally change the contact offset definition from one subcase to the next by selecting
unique contact sets in each subcase which reference different BCRPARA / BCTPARM bulk entries.

General notes

• The net penetration is computed at every gauss point generated on the source region and its
projection on the target region if it exists.
• The projection distance must lie within the search distance you specified on the BCTSET bulk entry.
• A source gauss point and its corresponding projection together constitute a contact element.
• For each contact node, the negative of pnet is reported from the closest contact element as separation
distance.

Interference example

Consider the following example.

8-38 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Gaps, Penetrations, and Offsets

The red area represents a 3D solid mesh and the green area represents a 2D shell element mesh. Contact
is defined between the shell mesh and the bottom of the solid mesh.

The gap (g) between the shell element face region (midplane where the grid points are modeled) and
the solid face region is 0.1.

The shell element thickness (t) is 0.4.

SOL 401 applies shell thickness first, then INIPENE settings, and finally offsets. For each of the following
cases, when ramping is requested with either the TZPENE or IPENRAMP parameters, the software will
ramp the initial penetration result shown.

1) The shell thickness is included, there are no INIPENE effects, and no offsets. The initial penetration =
(t/2 - g)=(0.2 - 0.1) = 0.1.

2) Same as 1 except INIPENE=3. The penetration of 0.1 would be reset to 0.0. The initial penetration =
0.0.

3) Same as 2 except an offset of 0.3 is defined on the solid contact region (BCRPARA bulk entry). The
penetration of 0.1 would be reset to 0.0, but because the offset is applied last, the initial penetration =
offset = 0.3.

4) Same as 3 except GAPVAL=0.1 is now defined. The penetration of 0.1 would be reset to 0.0,
then GAPVAL resets to an initial gap of 0.1, and finally, because the offset is applied last, the initial
penetration = (OFFSET-GAPVAL) = (0.3 - 0.1) = 0.2.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-39
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.12 Ramping contact changes

Contact conditions converge better when the changes to the contact problem occur in controlled
increments. As a result, you can request for the software to ramp the removal of penetrations.

Ramping the removal of penetrations in a time-assigned subcase

The TZPENE parameter on the BCTPARM bulk entry is available to ramp the removal of initial
penetrations for time-assigned subcases. For example, this capability may be useful if you have modeled
contact surfaces penetrating to represent a press fit condition.

TZPENE: End time when initial penetrations will be eliminated.

TZPENE=0.0 (Default): The initial penetrations are eliminated in the first subcase.

For example, if a subcase start time is 5.0, end time is 10.0, and TZPENE=7.2, the initial penetrations will
be eliminated starting from the beginning of the subcase (5.0) until time=7.2. Ramping the removal of
initial penetrations can help convergence.

Ramping the removal of penetrations in a constant-time subcase

The IPENRAMP parameter on the BCTPARM bulk entry is available to ramp the removal of initial
penetrations for a constant time subcase. For example, a preload subcase is a constant time subcase.

8-40 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact Surface and Edge Refinement

8.13 Contact Surface and Edge Refinement

The refinement of the source and target occurs by default. The contact search algorithm identifies for
each source segment a set of closest target segments that could potentially come into contact.

Each potential target segment is projected on to the source face or edge and a polygon clipping
algorithm computes an overlapping area. The overlapped area is divided into triangles creating a
“refined” source face/edge [3]. Integration points are created on each triangle based on gauss quadrature
rules and the value of the INTORD entry on the BCTPARM bulk entry.

The contact conditions are enforced at these integration points. The refinement process captures the
contact domain accurately and is an important piece in passing the constant stress patch test.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-41
© 2023 Siemens
 8. Contact conditions (SOL 401)

The refinement feature can optionally be turned off by setting REFINE=0 on the BCTPARM entry.

8-42 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Contact convergence

8.14 SOL 401 - Contact convergence

The contact algorithm includes an inner and an outer loop. The inner loop is represented by the
overall nonlinear problem using the Newton-Raphson iteration strategy. The outer loop is a contact
augmentation loop in which the software augments the contact tractions until the augmentation
penetration ratio check (PTOL) or the augmentation force ratio check (CTOL) is satisifed. The penetration
check (PTOL) is used by default. You can define CNTCONV=2 on the BCTPARM bulk entry, and the force
ratio check (CTOL) is used instead.

To satisfy the contact portion of the inner loop, the software computes either the global or the
pair based force ratio check (RCTOL). The global based check is used by default. You can define
SYSTEM(773)=1, and the pair based check is used instead.

The software does the contact damping tolerance check (DCTOL) when you have requested stabilization
damping with the CTDAMP parameter on the BCTPARM bulk entry. Stabilization damping is useful when
you are relying on the contact condition to prevent rigid body conditions, but the contact condition is
not fully active.

The Newton-Raphson iterations are used to solve the overall nonlinear problem with or without contact.
You can define convergence criteria for the overall problem with the CONV parameter on the NLCNTL
bulk entry.

The software prints all of the relevant information pertaining to each contact pair at the start of the
solution. You can use the MSGLVLC parameter on the NLCNTL bulk entry to control the output of contact
diagnostic messages to the *.f06 file.

See SOL 401 - Contact message output.

See SOL 401 - Iteration related output data.

Column Description
Augmentation If the contact penetrations exceed the penetration tolerance, an extra augmentation
penetration loop is performed. If the penetrations are below this tolerance, the augmentation loop
check (PTOL) is considered converged.
The penetration check is computed by:

1. The software computes a single averaged penetration value for each element face
or edge on the source region.

2. The maximum averaged penetration value from all of the element faces or edges
in a pair must be small than the penetration tolerance (PTOL).

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-43
© 2023 Siemens
 8. Contact conditions (SOL 401)

Column Description
You can adjust the penetration tolerance with the PTOL parameter on the BCTPARM
bulk entry.
Augmentation If you define CNTCONV=2 on the BCTPARM bulk entry, this check is used during the
force ratio augmentation loop instead of the penetration check.
check (CTOL)
The augmentation force ratio check indicates how the augmented contact traction is
changing relative to the previous augmentation loop. It is computed by:

where c is a contact element,

nce is the total number of contact elements,

is the augmented part of the total contact traction at a contact element,

and k is the augmentation loop number.
When FRAT < CTOL, the augmentation force ratio check is considered converged. You
define the parameter CTOL on the BCTPARM bulk entry.
Global force The global force ratio check indicates how the total contact traction is changing relative
ratio check to the previous iteration. It is computed by:
(RCTOL)

where c is a contact element,

nce is the total number of contact elements in all pairs,

is the total contact traction at a contact element,

and i is the iteration number.
When FRAT < RCTOL, the global force ratio check is considered converged. You define
the parameter RCTOL on the BCTPARM bulk entry.
Pair force ratio If you define SYSTEM(773)=1, this check is used instead of the global force ratio check.
check (RCTOL)
The pair force ratio check indicates how the traction in each contact pair is changing
relative to the previous iterations. It is computed by:

where c is a contact element,

ncep is the number of contact elements in a pair,

8-44 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Contact convergence

Column Description

is the total contact traction at a contact element,

and i is the iteration number.
When FRAT < RCTOL, the pair force ratio check is considered converged. The
convergence check against the RCTOL parameter is then enforced for each contact pair.
The global contact convergence is only satisfied when every pair has converged. You
define the parameter RCTOL on the BCTPARM bulk entry.
The largest pair based force ratio computed when SYSTEM(773)=1 will be greater than
the default, single global force ratio computed over all of the contact elements. As a
result, the pair based force ratio is a stricter convergence check and will require more
iterations to converge.
In addition, when you are using the pair based force convergence, you can use the
RCONSM parameter on the BCTPARM bulk entry to eliminate contact pairs from the
force convergence check that have a small contact force magnitude. The software
removes pairs from the pair based force convergence check when their force magnitude
is smaller than the product of (RCONSM x maximum force magnitude among all pairs).
The contact pairs with a small force magnitude are typically not in a state of significant
contact, they have a relatively low contribution to the force residual, and they can have
oscillating changes in contact status making their convergence difficult.
Damping The software does the contact damping tolerance check when you have requested
check stabilization damping with the CTDAMP parameter on the BCTPARM bulk entry.
(DCTOL)
The contact damping tolerance check is computed by

where c is a contact element,

nce is the total number of contact elements in all pairs,

are the damping tractions,

and are the total contact tractions.

The DCTOL parameter is available on the BCTPARM bulk entry to adjust the stabilization
damping tolerance. The software ramps the damping tractions down as it iterates at a
solution point until the contact damping tolerance is satisfied.
Relative The software only does the contact relative displacement tolerance check when you
displacment have not requested the global solution displacement convergence criteria by including
check (DPTOL) "U" with the CONV parameter on the NLCNTL bulk entry.
The relative displacement check is computed by

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-45
© 2023 Siemens
 8. Contact conditions (SOL 401)

Column Description
where c is a contact element,
nce is the total number of contact elements in all pairs,
urel is the relative displacement of the nodes associated with a contact element,
and Δurel is the change in the relative displacement from the last converged solution/
time point to the current iteration.
The DPTOL parameter is available on the BCTPARM bulk entry to adjust the tolerance.

Convergence considerations

• A high value of RCTOL (>1.0) or a large percentage change in contact status in each iteration usually
indicates any combination of the following.

• The penalty factor is high.

• The load is being applied too quickly.

• The time step is large.

To correct this situation, you can adjust AUTOSCAL to 0.1 or lower, or you can reduce the load and
time steps.

• If the PRATIO values are consistency higher than 1.0 but RCTOL and other convergence norms are
decreasing, increasing the penalty factor by an order can help achieve penetration convergence.

• Most convergence issues can be attributed to either loss of contact or the penalty factors being too
high or low. If there is rigid body motion present, setting open stiffness or stiffness stabilization would
help at the start of the analysis.

• If the displacements are constantly getting scaled, either the loading is excessive or the contact has
been lost. If there are initial gaps/penetrations in the geometry, setting INIPENE to ignore these would
help.

• If there are excessive numbers of contact pairing updates in a step, then the load or time step is too
large.

• If contact is lost due to difficult geometry or sharp changes in the geometry, reducing the step size or
geometry update tolerance (GUPTOL) can help.

• The contact algorithm monitors these variables for abrupt changes and triggers a bisection if the
number of adverse changes within a step exceeds the value of CNTMDIV.

• Use FRICDLY to delay friction effects until after the first step can also alleviate convergence problems.
With this option turned on, the frictional conditions are applied one time step after contact is

8-46 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Contact convergence

established. This feature can be useful in many problems, since it delays the nonlinearity associated
with friction until contact is established.

• If the convergence is slow or cannot be achieved for models with friction, using the un-symmetric
solver can improve the convergence rates.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-47
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.15 SOL 401 - Contact message output

You can use the MSGLVLC parameter on the NLCNTL bulk entry to control the output of contact
diagnostic messages to the *.f06 file. Descriptions of the following output listings are included below.

• Global contact summary

• Contact force resultants
• Contact pair status summary for each contact pair

• If you use the default (MSGLVLC=1), the Global contact summary is output for every iteration, and
the Contact force resultants are output when convergence occurs.

• If you define MSGLVLC=2, the Global contact summary, the Contact force resultants, and the
Contact pair status summary for each contact pair are output for every iteration.

• If you define MSGLVLC=0, none of this output occurs.

See SOL 401 - Contact convergence.

See SOL 401 - Solution accuracy indicator.

See SOL 401 - Iteration related output data.

Global contact summary

Column Description
AUG.# Augmentation loop number within a time step.
PAIRING# Number of pairing updates in a time step.
RELATIVE DISP Relative displacement tolerance check computed by

where c is a contact element,

nce is the total number of contact elements in all pairs,
urel is the relative displacement of the nodes associated with a contact element,

8-48 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Contact message output

Column Description
and Δurel is the change in the relative displacement from the last converged solution/
time point to the current iteration.
The software only enforces this check for convergence if you did not request the
displacement convergence criteria by including "U" with the CONV parameter on the
NLCNTL bulk entry.
You can adjust this threshold with the DPTOL parameter on the BCTPARM bulk entry.
FORCE Global force ratio which indicates how the total contact traction is changing relative to
the previous iteration. It is computed by:

where c is a contact element,

nce is the total number of contact elements in all pairs,

is the total contact traction at a contact element,

and i is the iteration number.
When FRAT < RCTOL, the contact force ratio is considered converged. You define the
parameter RCTOL on the BCTPARM bulk entry.
DAMPING Contact damping tolerance check when you have requested stabilization damping with
the CTDAMP parameter on the BCTPARM bulk entry. Stabilization damping is useful
when you are relying on the contact condition to prevent rigid body conditions, but the
contact condition is not fully active.
The contact damping tolerance check is computed by

where c is a contact element,

nce is the total number of contact elements in all pairs,

are the damping tractions,

and are the total contact tractions.

The DCTOL parameter is available on the BCTPARM bulk entry to adjust the stabilization
damping tolerance. The software ramps the damping tractions down as it iterates at a
solution point until the contact damping tolerance is satisfied.
TOTAL Total number of contact elements that are both active and inactive.
INACTIVE Number of contact elements that have a large enough separation to be considered
inactive.
OPEN Number of active contact elements that have experienced separation.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-49
© 2023 Siemens
 8. Contact conditions (SOL 401)

Column Description
STICKING Number of active contact elements that are sticking.
SLIDING Number of active contact elements with a tangential traction large enough to
overcome the limiting value of friction.
% CHANGE Percentage of contact elements that have changed status. The status ratio is computed
by

where Nc is the number of contact elements that have changed status from the
previous iteration to the current,
and Na is the total number of contact elements.
Contact elements that have changed status can have a change in the open/closed
status or the sticking/sliding status.

Contact force resultants for each contact pair

Column Description
BCTSET# Contact pair identification number defined on the BCSET bulk entry.
SOURCE ID Contact region identification numbers for the source and target regions referenced by
and TARGET the BCSET bulk entry.
ID
X,Y,Z Sum of the force components for the source and target regions reported in the basic
coordinate system.

Contact pair status summary for each contact pair

8-50 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Contact message output

Column Description
BCTSET# Contact pair identification number defined on the BCSET bulk entry.
MAXIMUM Maximum penetration value for the contact pair. The software computes the averaged
(PMAX) penetration over each face, then determines the maximum value of all averaged values
in a pair.
Note that the system cell 778 setting does not change how the MAXIMUM(PMAX) is
computed. The system cell only changes the separation distance output requested with
the BCRESULTS case control command.
TOLERANCE Tolerance value computed by PTOL*characteristic length for each pair. You define the
(PTOL) parameter PTOL on the BCTPARM bulk entry.
RATIO (P- Penetration ratio tolerance check computed by (PMAX/PTOL). Convergence is satisfied
RATIO) when PMAX/PTOL < 1.0.
FORCE RATIO The force ratio indicates how the contact traction in each contact pair is changing
relative to the previous iterations. It is computed by:

where c is a contact element,

ncep is the number of contact elements in a pair,

is the total contact traction at a contact element,

and i is the iteration number.
TOTAL Number of contact elements in a pair that are both active and inactive.
INACTIVE Number of contact elements in a pair that have a large enough separation to be
considered inactive.
OPEN Number of active contact elements in a pair that have experienced separation.
STICKING Number of active contact elements in a pair that are sticking.
SLIDING Number of active contact elements in a pair with a tangential traction large enough to
overcome the limiting value of friction.
% CHANGE Percentage of contact elements in a pair that have changed status. The status ratio is
computed by

where Ncp is the number of contact elements in a pair that have changed status from
the previous iteration to the current,
and Nap is the total number of contact elements in the pair.
Contact elements that have changed status can have a change in the open/closed
status or the sticking/sliding status.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-51
© 2023 Siemens
 8. Contact conditions (SOL 401)

8.16 Contact Output

Contact results can be requested with the BCRESULTS case control command. Forces, tractions,
separation distance, total and incremental slide or slip distance, and contact status can be output.

For SOL 401, the SEPDIS describer requests the initial separation distance for grids on the source region
and the final separation distance for grids on both the source and target regions. For grids on the source
region, the separation distance is a scalar quantity representing the source side distance to the target in
the source normal direction. For grids on the target region, the separation distance is a scalar quantity
representing the target side distance to the source in the source normal direction. The normal for the
projection is evaluated at the contact element location on the source face.

The initial separation is computed at the start of the solution in the undeformed state. The contact
definition must be either applied globally, or in the first subcase in order for the software to compute
the initial separation. The initial separation is not computed again, even if additional contact pairs are
introduced in later subcases, or if a non-sequentially dependent subcase is defined with the SEQDEP=NO
command.

The final separation distance is computed at the end of each time step in which output occurs. It is
computed based on the current deformed configuration.

When the software recovers the contact separation distance output to the grid points, the software
reports the true gap value from the contact Gauss point closest to the grid point. You can define
SYSTEM(778)=0, and the software will report the face-averaged values at the grid points. The averaged
approach is appropriate when contact is distributed across the element faces, but not when contact is
very localized. The true gap value approach is appropriate when contact is distributed or localized.

In addition for SOL 401, the SEPDIS describer requests the total and incremental slide distance for grids
on both the source and target regions. The slide distance is reported in the basic coordinate system
as the algebraic sum of the incremental slip (elastic and plastic) from each increment. When a contact
grid goes inactive, the total slide distance output resets to zero. The incremental slide distance is the
difference in the total slide distance between two output intervals.

When the contact status is requested with the STATUS describer on the BCRESULTS command, an integer
value indicating the contact status is output on each grid point included in a contact source or target
region. The status values are:

0: No contact exists.

1: A sticking contact condition exist.

2: A sliding contact condition exist.

For grids on the target region, the separation distance is a scalar quantity representing the target side
distance normal to the source.

8-52 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 References

8.17 References
1. T.A. Laursen and J.C. Simo. "Algorithmic Symmetrization of Coulomb Frictional Problems Using
Augmented Lagrangians". Computers Methods in Applied Mechanics and Engineering. Vol. 108,
No. 1& 2. 133-146. 1993.

2. P. Wriggers. “Computational Contact Mechanics”. Second Edition.

3. M. Puso, T. Laursen. “A Mortar Segment-to-Segment Frictional Contact Method for Large

Deformations”, Computer Methods in Applied Mechanics and Engineering, 2003.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 8-53
© 2023 Siemens
 8. Contact conditions (SOL 401)

8-54 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 9. Contact conditions (SOL 402)
9.1 Contact overview
SOL 402 supports surface-surface and edge-edge contact. The algorithm supports large deformations
and finite sliding between contact pairs. For large deformation problems (LGDISP>-1), the contact
stiffness and contact forces are rotated with the geometry consistent with other element formulation in
SOL 402. In addition, the SOL 402 contact algorithm updates the geometry and pairing when there is
finite sliding between the contacting surfaces.

Contact is modeled using a contact set, contact regions, contact segments and contact pairs.

The table below lists the case control commands and bulk entries used to define contact.

Contact definition summary

Case control commands:

BCSET Selects a contact set.
BCRESULTS Selects contact results to output.
Bulk entries related to edge or surface definition:
BSURF Defines contact region on shell elements.
BCPROP Defines contact region on shell elements by property ID.
BSURFS Defines contact region on 3-D solid elements.
BCPROPS Defines contact region on 3-D solid elements by property ID.
BEDGE Defines contact region on 2-D axisymmetric, plane strain and plane
stress elements.
BCTPAR2 Defines parameters for contact region.
Bulk entries related to contact set definition:
BCTSET Defines the contact sets.
BCTADD Defines a union of contact sets.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-1
© 2023 Siemens
 9. Contact conditions (SOL 402)

9.2 Contact subcase control

The BCSET case control command selects the contact conditions defined in the bulk data. The BCSET
command can be defined in any subcase type.

The modal, cyclic, and Fourier subcase types, which are sequentially dependent (default), use the final
stiffness from a previous subcase. The final stiffness from a static or preload subcase includes the contact
stiffness.

Note that if a subcase is sequentially dependent and it includes a new contact set, any contact tractions
from a previous subcase will be used as an initial condition for the current subcase. The previous
tractions define the initial condition for the newly formed contact elements.

9-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact definition

9.3 Contact definition

Edge contact regions

An edge contact region is a collection of axisymmetric, chocking, plane strain, and plane stress element
free edges in a section of the model where you expect contact to occur. You create edge regions with
the BEDGE bulk entry.

• To define a contact edge using the BEDGE entry, you enter the element ID along with the corner GRID
IDs. You can define the edges on the BEDGE entry in any order.

Edge-to-edge contact can be defined on the edges of the following elements:

• Axisymmetric elements CTRAX3, CQUADX4, CTRAX6, CQUADX8.

• Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

• Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8.

The axisymmetric, plane stress, and plane strain elements can be defined in either the XZ plane or in the
XY plane. Edge-to-edge contact is supported in either orientation. The generalized plane strain element
is not supported by glue or contact regions.

Surface contact regions

A surface contact region is a collection of element free faces in a section of the model where you expect
contact to occur. These regions can be created using the shell elements (BSURF and BCPROP) and the
solid element free faces (BSURFS and BCPROPS).

• The BSURF entry is defined by its own unique ID and is a list or range of shell element IDs to include in
the region.

• The BCPROP entry is defined by its own unique ID and is a list of shell element property IDs. Shell
elements that use any of the listed property IDs will be included in the region.

• The BSURFS entry is defined by its own unique ID and is a list of solid element IDs each followed by
three grid points defining which face of the 3D element to include in the contact region.

• The BCPROPS entry is defined by its own unique ID and is a list of solid element property IDs. The
software automatically determines the free faces of the solid elements selected with a property ID.

Surface-to-surface contact can be defined on the faces of the following elements.

• 3-D Solid elements CHEXA, CPENTA, CPYRAM, and CTETRA.

• Shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, and CTRIA3.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-3
© 2023 Siemens
 9. Contact conditions (SOL 402)

A contact surface can be defined with any face of a solid element. All region IDs defined with the BSURF,
BCPROP, BSURFS, BCPROPS, and BEDGE entries must be unique.

Contact pairs

A contact pair combines two contact regions, source and target, in which contact will be analyzed
during the solution. Each contact pair can have its own unique friction value (if desired).

The BCTSET bulk entry is used to define both edge-to-edge and surface-to-surface contact pairs. The CID
field will need to match the value of ‘n' on the BCSET case control entry for the solution to recognize this
contact definition.

The SIDi and TIDi fields on the BCTSET bulk entry are used to define source and target regions
respectively for a pair. As many pairs as desired can be included on a single BCTSET entry. Each pair
can have a unique friction value (optional). You can define the optional coefficient of friction parameter
(FRICi) for each contact pair. When contact is detected, the solver uses this value to calculate any
tangential contact forces.

The regions you select with SID and TID depend on the type of contact:

• For edge-to-edge contact pairs, SID and TID are contact regions defined with the BEDGE entry.

• For surface-to-surface contact pairs, SID and TID are contact regions defined with the BCPROP,
BCPROPS, BSURF, and BSURFS entries.

9-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact definition

Additional recommendations

When defining contact regions and pairs on geometry that are not tangent continuous, creating single
contact regions that cross corner transitions can result in non-uniform stress results around the corners.
It is recommended that you break these areas into multiple regions and pairs as shown below.

When defining contact regions and pairs, it is recommended that you do not include the same element
face in multiple regions. In “A” below, an element is repeated in regions 2 and 3. In “B”, the same
element only exists in region 2. “B” is recommended. Repeating element faces multiple times in the
same or different regions can significantly increase memory requirements and degrade performance.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-5
© 2023 Siemens
 9. Contact conditions (SOL 402)

Note:
The source contact regions (SIDi) that are initially defined as set of element faces or elements are
converted in set of nodes by the solver. This should be taken into account when splitting target
regions as explained above.

9-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact control parameters

9.4 Contact control parameters

The contact control parameters on the BCTPAR2 bulk entry can help you adjust the contact algorithm
when you are having problems getting a solution to converge and complete, or when the contact results
are not as expected. For many solutions, the default settings are appropriate, and the BCTPAR2 entry is
not required.

You can optionally define multiple BCTSET/BCTPAR2 bulk entry sets, each set with unique contact set IDs
(CSID), and then combine them with a single BCTADD bulk entry. The multiple BCTSET/BCTPAR2 bulk
entry sets are created to adjust certain contact parameters locally.

For more information, see the BCTPAR2 bulk entry in the Simcenter Nastran Quick Reference Guide.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-7
© 2023 Siemens
 9. Contact conditions (SOL 402)

9.5 Contact element

For each contact pair defined by BCTSET, the first stage of the contact algorithm consists in the
topological search. For each source node, the software determines the closest target face/element to the
candidate contact elements. Depending on the DISP parameter of the BCTPAR2 bulk entry, the contact
conditions are updated or not during the simulation.

For more information, see the BCTPAR2 bulk entry in the Simcenter Nastran Quick Reference Guide.

A general contact algorithm between a point and a facet follows these two steps:

1. The software computes the projection of the point onto the facet.

2. The software solves the contact condition. The contact algorithm is based on the augmented
Lagrange method.

Projection of the point onto the facet

In general, to find the projection of a source node XA on an element defined by its nodes Pi, the software
uses a local Newton-Raphson scheme.

If P is the projection candidate point on that element, the software solves the following system of
nonlinear equations:

In some cases, convergence is not achieved. In this case, the target element is rejected from the possible
contact targets.

Before performing the iterations, the software checks if the node is not too far from the element.

The software computes the distance between the node and the center of gravity of the element. If this
distance is smaller than a characteristic length of the problem, the target element is validated.

Contact algorithm

If dn is the normal distance, λn the Lagrangian multiplier associated to the normal distance, k a scaling
factor, and p the regularization parameter, the normal condition can be described as:

9-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact element

• If (pdn + kλn) < 0, the contact is active.

The contact internal force is given by: .

• If (pdn + kλn) > 0, there is no contact.

In this case, a force is associated to the Lagrangian multiplier: .

Note:
The contact force is: pdn + kλn.

When contact occurs, the equation associated with the Lagrange multiplier imposes a zero normal
distance. You can release this condition by defining a contact stiffness K that links the contact force
to the normal distance. For more information, see the NCMOD parameter of the BCTPAR2 bulk entry.
Stiffness unit in SI system is N/m3.

The term associated with the Lagrange multiplier, therefore, becomes:

This is not a penalty method. When the contact stiffness is huge, the equation system is still well
conditioned, and it reduces to the case without stiffness.

Note:
In SOL 402, depending on the source mesh, a contact surface is associated with each source node.

Coulomb friction

If friction is defined (μ > 0), an active contact element can have either a sticking or sliding state.

The software first introduces the following quantities:

where 1 and 2 stand for two in-plane element orthogonal directions.

The software computes an equivalent force to detect sticking or sliding: .

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-9
© 2023 Siemens
 9. Contact conditions (SOL 402)

• In the sticking case, σt - μ∣σn∣ ≤ 0.

Forces are computed as:

There are two classical kinematic constraints in which the variation of tangential displacements is set
to 0. The iteration matrix is obtained in a classical way and is symmetrical.

• In the sliding case, σt - μ∣σn∣ ﹥ 0.

The software computes two sliding directions:

Forces are computed as:

The classical Coulomb friction model requires the definition of a friction coefficient. You can define a
constant friction coefficient on the BCTSET bulk entry, or you can define a friction coefficient that is
dependent on time, sliding velocity, and temperature on the BCTPAR2 bulk entry. For more information,
see the FRICMOD parameter on the BCTPAR2 bulk entry.

By default, FRICMOD=0 and the software uses a classical Coulomb model.

To avoid convergence issues due to the discontinuity of the Coulomb model, the following two
regularization models are available to ensure a smooth transition of the friction forces between sliding
and sticking contact conditions:

1. You request and control the first regularization model using the STFR parameter on the BCTPAR2
bulk entry. By default, STFR = -2.0, and the software automatically computes the regularization
stiffness using the contact stiffness and the average element size of the contact target support.

The software applies the regularization stiffness between the friction stress and the relative
tangential displacement. When the friction stress equals the normal pressure multiplied by the
friction coefficient, the regularization stiffness has no more influence and sliding occurs.

9-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact element

When you use the default STFR = -2, you can also define the STFRF parameter to scale the
software computed tangential contact stiffness. For example, you could define STFRF=100.0, and
the software will multiply the computed tangential stiffness by a factor of 100.0.

For more information, see the STFR and STFRF parameters on the BCTPAR2 bulk entry.

2. You request and control the second regularization model using the TOL parameter on the BCTPAR2
bulk entry. This regularization model is only available with the ANALYSIS=DYNAMICS subcase.

The software applies a regularized friction coefficient as a function of the sliding velocity. Once the
sliding velocity becomes greater than or equal to the critical sliding velocity that you define with
the TOL parameter, the regularization stiffness has no more influence and sliding occurs.

For more information, see the TOL parameter on the BCTPAR2 bulk entry.

Damping

For transient analyses, damping can be introduced at contact level. In the DPARA1 and DPARA2
parameters of the BCTPAR2 bulk entry, you can define a normal or a tangential viscous pressure.

Those pressures are equal to the product of a function of the normal distance and the velocity associated
to the normal or tangential relative motions.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-11
© 2023 Siemens
 9. Contact conditions (SOL 402)

9.6 Contact and rigid body motion

Many static problems rely on contact to provide the boundary conditions necessary for a stable problem.
With these problem types, the stiffness matrix can be singular when the contact constraints are inactive.
You can use the following options to avoid singularities.

• Stiffness stabilization

This feature provides a stabilizing effect by scaling all diagonal stiffness terms without affecting the
right-hand-side load vector. You can request this feature by defining STAB parameter on the NLCNTL2
bulk entry.

• Contact damping

You can request the contact stabilization damping to stabilize the model and to avoid singularities in
the static and preload subcase types. See SOL 402 - Contact damping.

• Displacement scaling

The Newton iteration process can fail to converge if there is an excessive initial incremental
displacement. For example, this may occur when contacting surfaces separate. To facilitate
convergence, you can optionally scale down the incremental displacement by defining the existing
parameter MADI on the NLCNTL2 bulk entry. The software uses MADI to compute the displacement
increment scale factor DSCAL. See DSCAL computation below.

When you define MADI>0.0 (in units of length), the scale factor DSCAL is displayed for each iteration
in the .f06 file in the NEWTON ITERATIONS table. Your choice of the MADI value in a subcase affects
how the software calculates DSCAL for each iteration. A suggested value for MADI is 1/4 to 1/3 of the
element size.

DSCAL computation

The displacement for the current iteration is approximated by

di=di-1+(DSCAL× Δd)

where,

di is the unknown displacement for the current iteration,

di-1 is the known displacement from the previous successful iteration,

DSCAL is the scaling factor computed by the software,

and Δd is the incremental displacement for the current iteration.

9-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact and rigid body motion

The software computes DSCAL as follows, where Δdmax is the maximum incremental displacement for
the current iteration.

• If you define MADI<0.0 (default), the software sets DSCAL=1.0 and no scaling occurs.

• If you define MADI=0.0, the software replaces 0.0 with MADI=0.05 × Lmax, where Lmax is the
distance between the most separated nodes in your model. The software-computed MADI is then
used as follows:

■ If MADI<Δdmax, the software sets DSCAL=MADI/(Δdmax+1.0E-10).

■ If MADI>Δdmax, the software sets DSCAL=1.0 and no scaling occurs.

• If you define MADI>0.0, the software uses your MADI definition as follows:

■ If MADI<Δdmax, the software sets DSCAL=MADI/(Δdmax+1.0E-10).

■ If MADI>Δdmax, the software sets DSCAL=1.0 and no scaling occurs.

For more information, see the NLCNTL2 bulk entry in the Simcenter Nastran Quick Reference Guide.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-13
© 2023 Siemens
 9. Contact conditions (SOL 402)

9.7 SOL 402 - Contact damping

Many static problems depend on contact to provide the boundary conditions necessary for a stable
problem. With these problem types, the stiffness matrix can be singular when the contact constraints are
inactive.

You can request the contact stabilization damping with SOL 402 to stabilize the model and to avoid
singularities in the static and preload subcase types. You request the contact stabilization damping with
the following parameters on the BCTPAR2 bulk entry.

Table 9-1. Stabilization Damping Parameters

Name Description

CTDAMP Requests stabilization damping. This is useful, for example, when you are relying on
the contact condition to prevent rigid body conditions, but the contact condition is
not active. It can also be helpful in general to stabilize contact problems that do not
converge. (Integer; Default=0)
0 - No stabilization damping.
1 - Stabilization damping applied only in the first subcase and it is ramped down to
zero by the end of the subcase. The stabilization damping is only applied this way
when the entire pair status is open.
2 - Stabilization damping applied always as long as the entire pair status is open.
3 - Stabilization damping applied always regardless of the time and the pair status.
4 - Stabilization damping applied only in the first subcase regardless of the entire pair
status and it is ramped down to zero by the end of the subcase.

CTDAMPN If you request stabilization damping with the CTDAMP parameter, the CTDAMPN
parameter either scales the normal damping value that the software automatically
computes, or defines the normal damping value explicitly. (Real≠0.0; Default=1.0;
Units depend on the sign of CTDAMPN)
For CTDAMPN > 0.0, the normal damping value = CTDAMPN * automatically
computed damping value. CTDAMPN is unitless in this case.
For CTDAMPN < 0.0, the normal damping value = ABS(CTDAMPN). CTDAMPN has
units of pressure/velocity in this case.

CTDAMPT If you request stabilization damping with the CTDAMP parameter, the CTDAMPT
parameter either scales the tangential damping value which the software
automatically computes, or defines the normal damping value explicitly. (Real≠0.0;
Default=0.001; Units depend on the sign of CTDAMPT)
For CTDAMPT > 0.0, the tangential damping value = CTDAMPT * automatically
computed damping value. CTDAMPT is unitless in this case.

9-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Contact damping

Name Description

For CTDAMPT < 0.0, the tangential damping value = ABS(CTDAMPT). CTDAMPT has
units of pressure/velocity in this case.

OPNTOL Open gap tolerance scale factor. (Real≠0.0; Default=1.0; Units depend on the sign of
OPNTOL)
For OPNTOL > 0.0, the contact damping is applied to the contact elements that
have a gap value less than or equal to OPNTOL * characteristic length, but greater
or equal than 0.0. The contact damping is 0.0 if the gap is greater than OPNTOL *
characteristic length. OPNTOL is unitless in this case.
For OPNTOL < 0.0, the contact damping is applied to the contact elements that have
a gap value less than or equal to ABS(OPNTOL), but greater or equal than 0.0. The
contact damping is 0.0 if the gap is greater than ABS(OPNTOL). OPNTOL has units of
length in this case.

Note that if the parameters DPARA1/DPARA2 and CTDAMP are defined, DPARA1/DPARA2 is used and
CTDAMP is ignored.

• Contact stabilization damping computation

The stabilization normal damping force is computed as follows:

where is the normal damping coefficient, is the pseudo relative velocity of the contact
surfaces in the normal direction.

The normal damping coefficient is internally calculated by the solver. You can either scale or overwrite
the auto computed damping coefficient by entering the value as a function of contact pressure per
velocity.

The damping coefficient is calculated based on the contact stiffness, contact gap and current solution
time with respect to the subcase end time.

where CTDAMPN is the scale factor with a default value of 1.0,

Krep is a fraction of the contact stiffness,

Gapfac = 0 when gap > opntol or gap < 0.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-15
© 2023 Siemens
 9. Contact conditions (SOL 402)

The default value for OPNTOL is equal to 1.0 (times average element length).

where Curtim is the current solution time and Send is the subcase end time.

Similar to normal damping coefficient, tangential damping coefficient is only computed when there is
friction. The tangential damping coefficient is computed as:

where CTDAMPT is the tangential scale factor with default = 0.001.

The tangential damping force is thus calculated as:

Where is the pseudo relative velocity in the tangential direction.

9-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact offsets, initial penetrations, adjustment

9.8 Contact offsets, initial penetrations, adjustment

Contact surface offsets

You can define an offset for any contact pair with the OFFSET parameter on the BCTPAR2 bulk entry.
The offset causes the actual contact surface to be shifted from the plane defined by the contact surface
nodes. For example, you can use a contact offset to model an initial interference.

For shell elements referencing the PSHELL property, the software automatically computes an offset
based on the shell thickness by default. See the SHLTHK parameter on the BCTPAR2 bulk entry for more
details.

Note that specifying an offset on a contact region (BCRPARA) is not supported by SOL 402.

Initial penetrations

The treatment of initial penetrations is governed by the INIPENE parameter on the BCTPAR2 entry.
INIPENE is applied when contact elements are initially created, and if they are recreated as a result of
large displacement effects when PARAM,LGDISP,1 is defined.

• INIPENE = 1 (default): Contact is evaluated exactly as the geometry is modeled. No corrections will
occur for gaps (positive distance between the two contact regions) or penetrations (negative distance
between the two contact regions).

• INIPENE = 2: Only penetrations are reset to a new initial condition in which there is no interference.

• INIPENE = 3: Both gaps and penetrations are both reset to a new initial condition in which there is no
interference.

In this case a constant signed gap distance can be defined by GAPVAL, and it will override the
geometrical penetrations and gaps.

• INIPENE = 12: Penetrations will be reset to a new initial condition in which there is no interference for
the most penetrated node.

• INIPENE = 13: Gaps and penetrations are both reset to a new initial condition in which there is an
interference provided by GAPVAL for the closest node

For more information, see the BCTPAR2 bulk entry in the Simcenter Nastran Quick Reference Guide.

Adjustment

You can request for SOL 402 to remove initial separation in a contact pair by moving grid points.
When you use the ADJUST parameter on the BCTPAR2 bulk entry, the software uses an adjustment
tolerance to move the source grid points onto the target faces when the absolute value of the initial
separation distance is below the adjustment tolerance. The adjustment tolerance is computed as ADJUST

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-17
© 2023 Siemens
 9. Contact conditions (SOL 402)

* characteristic length, or it is equal to the characteristic length when ADJUST=0.0. The software
automatically computes the characteristic length using the mean length of the source and target
element faces.

The ADJUST parameter allows the following settings:

If ADJUST = 0.0, only the grid points that are initially overclosed are adjusted as long as the overclosure
is less than the characteristic length.

If ADJUST > 0.0, in addition to the overclosed grid points described in ADJUST=0.0, the adjustment is
also applied to grid points that are initially open with a gap smaller than value of ADJUST * characteristic
length.

ADJUST < 0.0, the software will adjust both the initially overclosed and the initially separated grid points
when either is smaller than the absolute value of ADJUST.

Interference example

The following example demonstrates the software behavior with INIPENE, the combination of
INIPENE+OFFSET, and the combination of INIPENE+GAPVAL. The red and green areas represent two
3D solid meshes that are modeled with interference and included in a contact definition.

SOL 402 applies the INIPENE settings first, then takes OFFSET or GAPVAL into account. GAPVAL can only
be used when INIPENE=3 or 13, and OFFSET is not allowable when INIPENE=3 or 13.

For the following examples, consider the modeled penetrations are P1=-4.0 and P2=-5.0. After the
software applies the INIPENE, OFFSET, or GAPVAL settings, the initial penetrations are reset to P1* and
P2*, where a negative value is a penetration and a positive value is a gap.

Settings Description P1* P2*

1 INIPENE or OFFSET The modeled penetrations P1 and P2 are not reset to a new initial -4.0 -5.0
are not defined condition.
2 INIPENE is set to 2 All penetrations (or gaps when 3 is defined) are reset to 0.0. 0.0 0.0
(or 3)
3 Same as (2) except The penetrations are reset to 0.0, then the OFFSET of 0.1 is -0.1 -0.1
OFFSET=0.1 applied.
4 INIPENE is set to 12 The penetrations (or gaps when 13 is defined) are reset relative 1.0 0.0
(or 13) to the closest nodes. The closest nodes have either the largest
modeled penetration, or if no penetrations exist, the smallest

9-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact offsets, initial penetrations, adjustment

Settings Description P1* P2*

modeled gap. The largest penetration for this example is P2=5.0.
Therefore, the penetration of P2 is reset from 5.0 to 0.0, and the
penetration of P1 is reset from 4.0 to a gap of 1.0 (P2 - P1 = 5.0 -
4.0 = 1.0).
5 Same as (4) except The penetration of P2 is reset to 0.0 (see description of 4 above), 0.9 -0.1
INIPENE=12 and then the OFFSET of 0.1 is applied. The penetration of P1 is reset to
OFFSET=0.1 a gap of 1.0, then the OFFSET is applied (1.0 - OFFSET = 1.0 - 0.1 =
0.9).
6 INIPENE=13 and The penetration of P2 is reset to 0.0 (see description of 4 above), 2.0 1.0
GAPVAL=1.0 then the GAPVAL of 1.0 is applied. The penetration of P1 is reset to
a gap of 1.0, then the GAPVAL of 1.0 is applied (1.0 + GAPVAL =
1.0 + 1.0 = 2.0).

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-19
© 2023 Siemens
 9. Contact conditions (SOL 402)

9.9 SOL 402 - Tangential contact stiffness in modal subcases

When you sequence subcases with contact conditions defined, the final contact stiffness computed
in the nonlinear subcases (PRELOAD, STATIC, DYNAMICS) is automatically included in the sequentially
dependent modal subcases (MODES, CYCMODES, FOURIER). The magnitude of the tangential contact
stiffness values used in a modal subcase will vary depending on the status (sticking or sliding) of the
individual contact elements.

You can use the KMODTN parameter on the NLCNTL2 bulk entry to control how the software applies
tangential contact stiffness in a modal subcase. This is useful, for example, when the nonlinear subcase
requires frictionless contact, yet the modal subcase needs a tangential contact stiffness to prevent
spurious rigid body modes.

The KMODTN parameter must be defined on a NLCNTL2 bulk entry that is referenced globally in the case
control. Specifically, the NLCNTL=n command that references a NLCNTL2 bulk entry with the KMODTN
parameter defined must be defined above the subcase level in the case control.

The KMODTN parameter settings allow you to independently control the tangential contact stiffness of
the contact pairs with friction (A), and without friction (B).

A: Contact pairs with friction are defined by FRICi>0.0 on the BCTSET bulk entry or FRICMOD>0 on the
BCTPAR2 bulk entry.

B: Contact pairs without friction are defined by FRICi=0.0 on the BCTSET bulk entry and FRICMOD=0 on
the BCTPAR2 bulk entry.

KMODTN Friction
Setting status Tangential contact stiffness in modal subcase
A The software holds the contact pairs tangentially in a modal subcase.
1 (Default) The software does not apply tangential contact stiffness in a modal
B
subcase.
The software applies the actual final tangential contact stiffness from the
A end of a nonlinear subcase in a modal subcase. The applied tangential
2 contact stiffness can be a mixture of sticking and sliding stiffness values.
The software does not apply tangential contact stiffness in a modal
B
subcase.
The software applies the actual final tangential contact stiffness from the
A end of a nonlinear subcase in a modal subcase. The applied tangential
3 contact stiffness can be a mixture of sticking and sliding stiffness values.
B The software holds the contact pairs tangentially in a modal subcase.
A The software holds the contact pairs tangentially in a modal subcase.
4
B The software holds the contact pairs tangentially in a modal subcase.

9-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact convergence

9.10 Contact convergence

Standard output

The software prints all of the relevant information pertaining to each contact pair at the start of the
solution. For each contact pair BCTSET (referred to as MCT in the f06 file), information on initial gaps/
penetrations, characteristic distances, and stiffnesses are provided.

Time step output

Contact change in forces (TESC) are printed as part of the iteration summary.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-21
© 2023 Siemens
 9. Contact conditions (SOL 402)

Convergence considerations

• In the case of convergence issues due to high local contact forces or contact loss, if there are initial
gaps/penetrations in the geometry, setting INIPENE to ignore these would help.

• If your model includes contact friction and convergence is slow or cannot be achieved, the
unsymmetric solver might improve the convergence rates. You can select the unsymmetric solver
with the parameter setting INLY=1 on the NLCNTLG bulk entry.

Note:
Using the unsymmetric solver improves convergence for contact friction, follower forces, and
gyroscopic effects in dynamic analyses. The unsymmetric solver increases computation time
because it doubles the number of arithmetic operations of the linear solution. It uses full
matrices regardless of whether symmetry exists.

In case of divergence, to help to find the origin of the divergence, a summary of the contact status
during the iteration is given. The following table is printed in the output file.

9-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact convergence

By default, the table is only printed for the last time step of the analysis if it is not converged.

The meaning of the columns are:

• 1st column: IT is the iteration number.

• 2nd column: TYPE is the contact type of the contact pair.

• 3rd column: NRis the number of the contact pair.

• 4th to 6th columns: FX, FY, and FZ are the total force going through the contact area in structural
axes. They are the forces acting from the target side on the source side.

They are given in unit of forces.

• 7th and 8th columns: ResS and ResM are the estimations of the norms of the residual forces acting
on the source and target side. They are given in unit of forces.

They are computed as the sum of the forces acting on the contact element and the sum of the forces
acting on the element DOF. So the same DOF is taken into account several times.

The residual forces come from all the nonlinearities; even if there is no contact, the residual forces
could be non zero.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-23
© 2023 Siemens
 9. Contact conditions (SOL 402)

Note:
At the convergence, the residual forces should be negligible.

• 9th and 10th columns: for a contact pair (MCT), Dmin and Dmax are the minimum and maximum
normal distance. The normal distance is equal to 0 when contact occurs and if there is no contact
stiffness.

If these values equal 1E12 and –1E12, that means that the source nodes have no projection on the
target faces.

• 11th column: Glis is the total sliding factor for the contact pair.

By watching the largest values of ResS and ResM, especially in the last iterations, you can discover if
there is a contact condition for which the residual forces are larger than for the other forces on the
model or for which there are oscillations from one iteration to the next one.

First check if the divergence can be explained by a model weakness (sliding of a free body, and so on) or
due to a physical weakness.

In this case, change the contact conditions (consider a larger group of faces, perform a topology search
at each iteration, introduce contact stiffness, and so on).

9-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Contact output

9.11 Contact output

Contact results can be requested with the BCRESULTS case control command. Forces, tractions,
separation distance, total and incremental slide or slip distance can be output.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-25
© 2023 Siemens
 9. Contact conditions (SOL 402)

9.12 SOL 402 - Contact status output

You can request additional contact status to the .f06 file when you need insight into a solution that
is not converging. You use the MSGLVLC parameter to make the request. The MSGLVLC options are
summarized below.

MSGLVLC: Diagnostic output for contact. (Integer = 0, 1, 2, 11 or 12; Default = 11)

0 = No additional diagnostic output.
1 = Information related to each contact pair is printed for each iteration. The information includes
the contact force, normal distance, sliding distance, and the number of inactive/open/sticking/slipping
contact elements. This is a more concise listing as compared to the MSGLVLC=2 option.
2 = Everything described in option 1 but expanded. This option also lists the residual forces and the
variations in the Lagrange multipliers.
11 = Same as option 1, but only printed in the case of non-convergence. (Default)
12 = Same as option 2, but only printed in the case of non-convergence.

The following examples demonstrate the requested output.

MSGLVLC=1 output example

MSGLVLC=1 column definitions:

FORCE Resultant of the sum of contact force components across the contact interface.
DISTANCE Smallest distance in the contact normal direction. The value is either the largest penetration
(most negative value) or the minimum value of the gap (smallest positive value).
SLIDING Maximum absolute value of sliding increment for source node in sticking contact.
INACTIVE Number of source side nodes that are inactive.

9-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Contact status output

OPEN Number of source side nodes that are active but not in contact.
STICK Number of source side nodes that have a status of sticking.
SLIP Number of source side nodes that have a status of sliding.

MSGLVLC=2 output example

MSGLVLC=2 column definitions:

FX, FY, FZ Summation of contact force components across the contact interface.
RESS Residual forces acting on the source side. See note below.
RESM Residual forces acting on the target side. See note below.
DNMIN Smallest distance in the contact normal direction. The value is either the largest penetration
(most negative value) or the minimum value of the gap (smallest positive value).
DNMAX Largest distance in the contact normal direction. The value is the maximum value of the gap
(always positive).
DLAGN Variation in the Lagrange multiplier for the contact normal direction.
DGTMIN Minimum value of incremental contact slip distance.
DGTMAX Maximum value of incremental contact slip distance.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-27
© 2023 Siemens
 9. Contact conditions (SOL 402)

DLAGT Variation in the Lagrange multiplier for the contact tangential direction.
NBDEAD Number of source side nodes that are inactive.
NBGAP Number of source side nodes that are active but not in contact.
NBCONT Number of source side nodes that are in contact (NBSTIC + NBSLID).
NBSTIC Number of source side nodes that have a status of sticking.
NBSLID Number of source side nodes that have a status of sliding.

Note: If RESS or RESM are larger than the other forces in the model, especially in the last iterations,
or if their values oscillate from one iteration to the next, you could have a lack of stiffness or an
unconstrained condition. You could, for example, modify the contact stiffness, or turn on contact
stabilization damping. When the contact condition converges, these residual forces will be negligible.

9-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Virtual thread contact

9.13 SOL 402 - Virtual thread contact

When you model bolts and include the thread detail, the refined mesh needed on the thread geometry
significantly increases the size of the model and the solution times.

A virtual thread contact condition is available for you to include the bolt thread connections but without
the requirement of modeling the threads. The software internally computes the contact normal and
tangential directions relative to the thread angle you provide.

You model the bolt and hole as straight cylindrical surfaces with diameters roughly at the bolt mean
diameter. You can apply the virtual thread contact to the 3D solid elements CHEXA, CTETRA, CPARA,
and CPENTA. Both linear and parabolic elements are supported, but mixing linear and parabolic is not
supported in the contact regions.

The table below lists the inputs used to define virtual thread contact.

Case control commands:

BVTSET=n Selects a virtual thread contact set. It must be defined above the
subcase level (globally).
n references a BVTSET bulk entry or a BVTADD bulk entry. n can also
reference the BVTPAR bulk entry.
BCRESULTS Selects virtual thread contact results to output.
Bulk entries:
BSURFS Defines the 3D solid element face regions for the bolt and the hole.
BVTSET Defines the virtual thread contact connection between the bolt and the
hole face regions.
BVTPAR Defines optional parameters for virtual thread contact sets.
BVTADD Defines a union of virtual thread contact sets defined with multiple
BVTSET entries.

You define the virtual thread contact connection with the BVTSET bulk entry. The BVTSET entry fields are
as follows.

1 2 3 4 5 6 7 8 9 10
BVTSET VTSID OUTSID INSID FRIC N1 N2 DID
PITCH ANGLE THDOPT

● VTSID: Defines the virtual thread contact set identification number.

● OUTSID and INSID: Selects the bolt and hole region IDs defined with the BSURFS bulk entry. The
surfaces in the bolt and hole regions can be separated (gap) or interfering (penetration). The software
will reset these conditions to a 0.0 gap/penetration condition at the beginning of the solution.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-29
© 2023 Siemens
 9. Contact conditions (SOL 402)

● FRIC: Defines static coefficient of friction for the virtual thread contact. This value can be overwritten
using the FRICMOD parameter on the BVTPAR bulk entry. The direction of the frictional force is parallel
with the thread.

● N1 and N2: Defines the bolt center axis and direction. You select either two grid points (GRID bulk
entry) or two points (POINT bulk entry) located on the bolt center axis. If N1 is a grid point, it will only
follow the large rotation of the bolt if it has rotational degree-of-freedom and is connected to the bolt
using RBE2 or RBE3 elements.

The order you define N1 and N2 changes the contact normals for the THDOPT=-1 option described
below.

● DID: References the ID of a DESC bulk entry to include a virtual thread contact set description.

● PITCH: Defines the thread pitch (P) as shown in the following image.

● ANGLE: Defines half the thread angle in degrees (ɑ) as shown in the previous image.

● THDOPT: Defines how the software creates the contact normals. For all of the THDOPT choices in the
following descriptions, the locations where the software creates the contact conditions is the same. The
difference in the options is how the normals are computed at these locations.

• THDOPT=-1 (Default)

The software uses the thread angle (ɑ) and the N1 to N2 vector to determine a consistent contact
normal for all locations on the bolt surface. The thread pitch is ignored in this case.

If N1 is defined on the bottom of the bolt and N2 higher on the bolt, the software uses the contact
normal relative to the top of the thread (bolt in tension) in all locations. The image below illustrates
this case.

9-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Virtual thread contact

If N1 is defined higher on the bolt and N2 is defined on the bottom of the bolt, the software uses the
contact normal relative to the bottom of the thread (bolt in compression) in all locations. The image
below illustrates this case.

• THDOPT=0

The software uses the thread angle and pitch to determine the alternating contact normals for the top
and bottom of the threads. For this case, you must define N1 on the bottom of the bolt and N2 higher
on the bolt. The helix of the thread is not represented.

Additional information:

• The software does not update the virtual thread contact condition as the solution proceeds. As a
result, the bolt and hole surfaces should only experience small relative sliding. Although, the entire
bolt and hole assembly can experience large displacement and rotation.

• Parameters are available on the BVTPAR bulk entry to adjust contact friction and stiffness for the
virtual thread contact set.

• You can approximate the flexibility (normal stiffness) of the threads using the parameters NCMOD,
NPENAL2, and CFACTOR1 on the BVTPAR bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-31
© 2023 Siemens
 9. Contact conditions (SOL 402)

9.14 Recommendations for contact definitions

We recommend the default settings for the contact parameters and stiffness unless you are having
convergence problems. However, if problems occur, the following are some recommendations.

Region selection guidelines:

The SIDi and TIDi fields on the BCTSET bulk entry select the source and target regions for a contact pair.

● You should select the more refined mesh region as the source (SIDi) to maximize the number of
contact conditions.

● You should select the more rigid region as the target (TIDi) because the stiffer region deforms less.

Ramping contact conditions

For subcases that are not the first, the software always ramps the contact conditions beginning with the
status from the previous subcase and ending with the new status. Because there is no previous subcase
at time=0.0, you can use the ACTIVE parameter on the BCTPAR2 bulk entry to define the beginning
contact status for the first subcase. See the remarks on the BCTPAR2 entry for details.

Contact stiffness guidelines

The ideal contact stiffness is infinite because it results in a zero penetration condition when the contact
condition converges. By default, the normal contact condition is a rigid constraint condition similar to an
MPC condition with no actual stiffness defined. We recommend that you use the default condition if your
solution is converging.

● If convergence is difficult with the default settings, you can define a normal contact stiffness with the
NCMOD parameter on the BCTPAR2 bulk entry. As you reduce the contact stiffness, you are releasing
the contact constraints and allowing more compliance, but you are also allowing more penetration. As
a result, when you explicitly define the normal contact stiffness, you should always check the contact
penetration result. You can request the final separation distance with the SEPDIS describer on the
BCRESULTS case control command.

● Your choice for the contact stiffness depends on how accurate you need the contact result to be
(zero penetration), and how difficult the convergence is. If you define a low stiffness, convergence will
be easier, but you will have higher penetrations. If you define a high stiffness, you can have a condition
similar to the default behavior and convergence may not occur. You may need to experiment with
different stiffness values to find a reasonable balance of convergence versus accuracy that works for your
problem.

● You can define NCMOD=-2.0, and the software will automatically compute the contact stiffness using
the element stiffness in the source and target regions along with the average element size in the target
region. Be sure to check your penetration result, especially if your element stiffness is low.

9-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Recommendations for contact definitions

● You can open the .f06 file to see the list of contact parameters used in the solution, which includes
the stiffness value. This table listing refers to the MCT numbers, which are related to the contact set
names listed below the table. "Nastran Name" in the bottom table refers to the description on the DESC
bulk entry that is referenced in the DID field on the BCTSET bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 9-33
© 2023 Siemens
 9. Contact conditions (SOL 402)

9-34 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 10. Glue conditions
10.1 Overview of Gluing Elements
SOL 401 and SOL 402 support the option to glue elements together. Glue is a simple and effective
method to join meshes which are dissimilar. It correctly transfers displacement and loads resulting in an
accurate strain and stress condition at the interface. The grid points on glued edges and surfaces do not
need to be coincident.

By default, the glue formulation in SOL 401 and SOL 402 creates a connection which prevents relative
motion in all directions.

In SOL 401, you can also optionally turn on the sliding glue formulation for the surface-to-surface glue
conditions and the edge-to-edge glue conditions on 2D solid elements. Sliding glue includes a normal
stiffness but no tangential stiffness, and is requested by defining the parameter setting SLIDE=1 on the
BGPARM entry. The sliding glue formulation is not supported with edge-to-edge or edge-to-surface glue
conditions defined on 3D shell elements.

The following table summarizes the supported glue conditions in SOL 401 and SOL 402.

Table 10-1. Glue Summary

Type Description
Edge-to-Edge For SOLs 401 and 402, you can define edge-to-edge glue between the edges
of the following 2D solid elements:
Axisymmetric elements CTRAX3, CQUADX4, CTRAX6, CQUADX8,
Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8,
Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8,
Chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8
For SOL 401 only, you can define edge-to-edge glue between the edges
of the 3D shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, and
CTRIA3 entries.
Edge-to-edge glue conditions on 3D shell elements are not updated when
large displacements are requested (PARM,LGDISP,1). By default, the solution
will end with a fatal error when shell edge glue conditions and large
displacements are requested. If the glue condition is in a location of the
model that will not experience large rotations, the glue condition should be
reasonably accurate. For this case, you can define SYSTEM(784)=1 to allow
the solution to continue.
Edge-to-Surface For SOL 401 only, you can define edge-to-surface glue between:
• The edges of 3D shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8,
CQUAD4, and CTRIA3 entries.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-1
© 2023 Siemens
 10. Glue conditions

Type Description
• The faces of the 3D shell elements CTRIA3, CTRIA6, CTRIAR, CQUAD4,
CQUAD8, CQUADR and the faces of the 3D solid elements CHEXA, CPENTA,
CPYRAM, and CTETRA.
Edge-to-surface glue conditions are not updated when large displacements
are requested (PARM,LGDISP,1). By default the solution will end with a
fatal error when edge-to-surface glue conditions and large displacements
are requested. If the glue condition is in a location of the model that will
not experience large rotations, the glue condition should be reasonably
accurate. For this case, you can define SYSTEM(784)=1 to allow the solution
to continue.
Surface-to-Surface For SOLs 401 and 402, you can define surface-to-surface glue between the
faces of the 3D solid elements CTETRA, CHEXA, CPENTA and CPYRAM and the
faces of 3D shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, and
CTRIA3 entries.

Defining Glue Conditions

• Select the glue condition with the BGSET case control command. The BGSET case control command
must be above the subcases. As a result, the glue conditions apply to all subcases. See Defining and
Selecting Glue Pairs.

• Define source and target regions. See Glue Regions.

• Pair the source and target regions. See Defining and Selecting Glue Pairs.

• Optionally adjust the glue algorithm using glue control parameters. See Glue Control Parameters.

• Optionally request the glue force and traction output with the BGRESULTS case control command.

2D Solid Edge Glue Summary

The 2D solid elements axisymmetric, plane stress, plane strain, and chocking elements can be defined in
either the XZ plane or in the XY plane. Edge-to-edge glue is supported in either orientation.

You create element edge regions with the BEDGE bulk entry. You then pair the regions using the source
and target fields on the BGSET bulk entry.

From the source region, the software searches in the outward normal direction. In addition, the software
searches a small distance in the inward normal direction in order to glue edges that may interfere due to
meshing irregularities. A glue condition is created when a projected normal hits the target side, and the
distance between the edges is equal to or less than the search distance which you specify for the glue
pair on the BGSET entry.

3D Shell Edge Glue Summary (SOL 401 only)

10-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview of Gluing Elements

You create shell element edge regions with the BEDGE bulk entry. You then pair the regions using the
source and target fields on the BGSET bulk entry.

A simplified description of shell element edge-to-edge glue is that the software creates pseudo-faces
along the edges. From the glue points on the source side pseudo-face, the software projects a normal in
the outward normal direction. In addition, the software searches a small distance in the inward normal
direction to glue edges that may interfere due to meshing irregularities.

A glue connection occurs when the following is satisfied.

A. When a projected normal contacts the pseudo-face on the target side.

B. The distance between the two pseudo-faces is equal to or less than the search distance that you
specify for the glue pair on the BGSET entry.

The larger the angle is between neighboring shell elements, the less likely that a successful projection
can occur. For example, a glue connection cannot occur if the neighboring shell elements are
perpendicular. In this case, you could consider an edge-to-surface glue connection.

The image below helps to illustrate. The blue line represents the shell elements, and the red line
represents an internally created pseudo-face along the edges in the source and target regions. The
pseudo-face can be visualized by extruding the element edge from -t/2 to +t/2 in the parent element
normal direction.

Edge-to-Surface Glue Summary (SOL 401 only)

For SOL 401 only, you can define edge-to-surface glue between the edges of the 3D shell elements and
the faces of both 3D shell elements and 3D solid elements.

You create shell element edge regions with the BEDGE bulk entry, and you create shell or solid element
face regions with the BSURF, BSURFS, BCPROP, or BCPROPS bulk entries. You then pair the regions using
the source and target fields on the BGSET bulk entry. The source region in the pair must be the edge
region. The target region consists of shell or solid element faces.

A simplified description of edge-to-surface glue is that the software creates pseudo-faces along the
edges in the source region. It then connects these pseudo-faces to the shell or solid faces in the target
region with weld like connections.

From the glue points on the source side pseudo-face, the software projects a normal in the outward
normal direction. In addition, the software searches a small distance in the inward normal direction in
order to glue edges and surfaces that may interfere due to meshing irregularities.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-3
© 2023 Siemens
 10. Glue conditions

A glue connection occurs when the following is satisfied.

A. When a projected normal contacts the face on the target side.

B. The distance between the two is equal to or less than the search distance that you specify for the glue
pair on the BGSET entry.

For example, the green line below represents shell or solid free faces in a target region, the blue line
represents shell elements, and the red line represents an internally created pseudo-face along the edges
in the source region. The pseudo-face can be visualized by extruding the element edge from -t/2 to +t/2
in the parent shell element normal direction.

Note that shell theory does not account for changes in shell thickness or normal strains perpendicular to
the plane of the shell element. The ESOPT parameter on the BGPARM bulk entry gives you a choice of
how to handle the linking of the zero normal strains, which exist in the shell element associated with the
edge, to the surface being glued. See Glue Parameter Descriptions for SOL 401.

Surface-to-Surface Glue Summary

Surface-to-surface glue can be defined on the faces of the 3D solid elements and the 3D shell elements.

You create shell or solid element face regions with the BSURF, BSURFS, BCPROP, or BCPROPS bulk entries.
You then pair the regions using the source and target fields on the BGSET bulk entry. From elements in
the source region, a normal is projected.

From solid face regions, the software searches in the outward normal direction. In addition, the software
searches a small distance in the inward normal direction in order to glue solid faces that may interfere
due to meshing irregularities.

From shell element face regions, the software searches in both the top and bottom normal directions.

The software creates a glue condition if:

A: Any of the source element normals intersect with an element in the target region.

B: The distance between the two faces is equal to or less than the search distance which you specify for
the glue pair on the BGSET entry.

Additional information

10-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview of Gluing Elements

• When large displacements are requested with PARM,LGDISP,1, the glue stiffness orientation will
update for surface-to-surface glue conditions and the edge-to-edge glue conditions on 2D solid
elements as a result of large displacement effects. The glue stiffness is only computed once, at the
beginning of a solution.

For SOL 401, edge-to-edge gluing on shell elements and edge-to-surface glue conditions are not
updated when large displacements are requested. By default the solution will end with a fatal error
when shell edge glue conditions and large displacements are requested. If the glue condition is in a
location of the model that will not experience large rotations, the glue condition should be reasonably
accurate. For this case, you can define SYSTEM(784)=1 to allow the solution to continue.

• The source side element characteristics are used to define the glue stiffness. Therefore, it is possible
for differences depending on which element faces or edges are selected as the source region.

• The generalized plane strain element is not supported by glue or contact regions.

SOL 402 remarks

• The sliding glue formulation is not available in SOL 402.

• Chocking elements (CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8) cannot be part of gluing conditions
in SOL 402.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-5
© 2023 Siemens
 10. Glue conditions

10.2 Glue Regions

The following describes how edge and surface regions are defined in SOL 401 and SOL 402. An element
should not appear more than once in the regions that are part of a glue/contact pair. All region IDs
defined with the BEDGE, BSURFS, or BCPROPS entries must be unique.

Edge Glue Regions

The edge glue region is a selection of element edges on the 2D solid elements axisymmetric, plane
strain, plane stress, and chocking, or for SOL 401 only, a selection of element edges on the 3D shell
elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, and CTRIA3. An element edge is selected on the
BEDGE bulk entry by entering the element ID along with the corner GRID IDs.

Surface Glue Regions

The surface glue region is a selection of element free faces on the 3D solid elements CTETRA, CHEXA,
CPENTA and CPYRAM, and the 3D shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, and
CTRIA3. These regions are created using the BSURFS and BCPROPS for the 3D solid element free faces,
and using the BSURF and BCPROP entries for the 3D shell element faces.

• The BSURFS entry is a list of solid element IDs each followed by 3 grid points defining which face of
the 3-D element to include in the glue region.

• The BCPROPS entry is a list of solid element property IDs. The free faces of the solid elements selected
with a property ID are automatically determined by the software.

• The BSURF entry is a list or range of shell element IDs to include in the region.

• The BCPROP entry is a list of shell element property IDs. Shell elements which use any of these listed
property IDs will be included in the region.

10-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Defining and Selecting Glue Pairs

10.3 Defining and Selecting Glue Pairs

A glue pair is a way to combine two regions, source and target, in which gluing will be analyzed during
the solution. You use the BGSET bulk entry to define each glue pair. The fields on the BGSET bulk entry
are described as follows:

• GSID (glue set id) will need to match the value of ‘n’ on the BGSET case control entry for the solution
to recognize the glue definition.

• SIDi and TIDi are used to select source and target regions for a pair. For surface-to-surface gluing, they
reference the regions created by the BSURF, BSURFS, BCPROP, or BCPROPS entries. For edge-to-edge
gluing, they select the regions created by the BEDGE entries. As many pairs as desired can be included
on a single BGSET bulk entry.

• SDIST (search distance) defines the distance in which the solver can initially determine if the distance
between element edges or faces in a particular pair are within the threshold for creating glue
elements. The default value of SDIST of 10 is large enough to handle most geometry situations,
but can be adjusted as needed. This value is used once, at the beginning of the solution, to determine
where glue elements are created.

Combining Glue Sets – BGADD

You can optionally define multiple BGSET/BGPARM bulk entry sets, each set with unique glue set IDs
(GSID), and then combine them with a single BGADD bulk entry. The multiple BGSET/BGPARM bulk entry
sets are created to adjust certain glue parameters locally. Glue parameters can also be adjusted globally
with a BGPARM bulk entry having the same GSID as the BGSET case control command.

The following example demonstrates the inputs.

CASE CONTROL
$GSID on the BGSET case control matches GSID on BGADD
BGSET = 108
...
BULK DATA
$Local Glue Set definitions
BGSET 1 1 2
BGSET 2 3 4
5 6
...
$Local Glue Parameters
BGPARM 1 PENN 80 PENT 80
BGPARM 2 PENN 110 PENT 110
...
$Local Glue Sets are combined with BGADD
BGADD 108 1 2
...

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-7
© 2023 Siemens
 10. Glue conditions

$Global Glue Parameters

BGPARM 108 REFINE 0GLUETYPE 1

See the section Glue Control Parameters – BGPARM Bulk Entry in this chapter for more information on
glue parameters.

Gluing Composite Solid Faces

Defining glue regions and pairs on composite solid faces which are perpendicular to the stack direction
(edge faces) may produce poor stress continuity. If the glue definition is between edge faces belonging
to different PCOMPS definitions, and if the number of plies on each PCOMPS definition is small and the
same, and the ply thicknesses are similar, the stress continuity should be fairly smooth. This also applies
to the results requested with the BGRESULTS case control command.

Additional Recommendations

When defining glue regions and pairs on geometry which are not tangent continuous, creating single
glue regions which cross corner transitions can result in non-uniform stress results around the corners. It
is recommended to break these areas into multiple regions and pairs as shown below.

When defining glue regions and pairs, it is recommended to not include the same element face in
multiple regions. In “A” below, an element is repeated in regions 2 and 3. In “B”, the same element only
exists in region 2. “B” is recommended. Repeating element faces multiple times in the same or different
regions can significantly increase memory requirements and degrade performance.

10-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Defining and Selecting Glue Pairs

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-9
© 2023 Siemens
 10. Glue conditions

10.4 Glue Control Parameters

The glue control parameters on the BGPARM bulk entry can help you adjust the glue algorithm. For most
solutions, the default settings are appropriate, thus the BGPARM entry is not required.

You can optionally define multiple BGSET/BGPARM bulk entry pairs, each pair with unique glue set IDs
(GSID), and then combine them with a single BGADD bulk entry.

The multiple BGSET/BGPARM bulk entry pairs are created to adjust certain glue parameters locally. Glue
parameters can also be adjusted globally with a BGPARM bulk entry having the same GSID as the BGSET
case control command.

Global and local glue parameters have the following definition and rules:

• Global Glue Parameters

The BGPARM bulk entry, which uses the same GSID entered on the BGSET case control command,
defines global parameters.

For SOL 401, all of the parameters on the BGPARM bulk entry can be defined globally. A parameter’s
default value is used if it is not defined globally or locally.

• Local Glue Parameters

The BGPARM bulk entries associated to individual BGSET bulk entries, which are then combined with a
BGADD bulk entry, define local parameters.

For SOL 401, the parameters GLUETYPE, PENN, PENT, PENTYP, PENGLUE, and SLIDE can be defined
locally. A local parameter definition overrides a global definition.

Glue Parameter Descriptions for SOL 401

• SOL 401 only supports GLUETYPE=2. As a result, the glue stiffness is determined by the PENTYP and
PENGLUE parameters.

PENTYP – Changes the meaning of the PENGLUE parameter as described in the table below.
(Default=1)

PENGLUE - A scale factor used to adjust the glue stiffness. (Default=1.0)

PENTYP=1 (Default) PENGLUE is a unitless value (glue stiffness scale factor).

PENTYP=2 PENGLUE has the units of F/L2.

• Note: For glued coincident faces, there is little flexibility between the faces with default penalty
factors. The glue condition created between non-coincident faces will not usually produce a local

10-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Glue Control Parameters

stiffness as accurate as using a conventional finite element for the connection. The flexibility in the
glue condition will depend on the value of the penalty factors. If you have non-coincident faces and
the glue joint flexibility is important, then it is recommended that you model this connection with
conventional finite elements.

Average modulus computation

The averaged modulus of the elements associated with the source side region is also used when
computing the glue stiffness. The averaged modulus is computed as follows.

• The modulus is averaged for the elements associated with the source side region.

• For elements using orthotropic and anisotropic materials, the element modulus value used in the
average modulus computation is computed as follows.

MAT9: E=(C11+C22+C33)/3

MAT11: E= (E1+E2+E3)/3

• When a solid composite defined with the PCOMPS entry is included in a source glue region, the
average modulus is computed by averaging all modulus values defined on all materials defined in
the input file.

• SLIDE - Requests the sliding glue. Sliding glue includes normal stiffness but no tangential stiffness.
Gaps between the glued surfaces are preserved as sliding occurs.

0 - Sliding glue is off (default).

1 - Sliding glue is on.

The sliding glue formulation is not supported with edge-to-edge or edge-to-surface glue conditions
defined on 3D shell elements.

• INTORD and REFINE help to improve the accuracy of the glue solution. The number of locations where
normals are projected (glue points) from the source region is dependent on the value assigned to the
INTORD parameter, and on the element face type. The following table summarizes how the INTORD
value adjusts the number of glue points for a particular element face:

Number of Glue Points Used in Glue Element Evaluation

Face Type INTORD=1 INTORD=2 (default) INTORD=3
Linear Triangle 1 3 7
Parabolic Triangle 3 7 12
Linear Quad 1 4 9
Parabolic Quad 4 9 16

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-11
© 2023 Siemens
 10. Glue conditions

REFINE will increase the number of glue points by refining the mesh on the source region. Part of the
refinement process is to project element edges and grids from the associated target region back to the
source region. The resulting refinement on the source region is then more consistent with the target
side, which then gives a better distribution of glue elements. The refined grids and elements are only
used during the solution. The glue results are transferred back to the original mesh for post processing
results.

Refinement occurs when set to 2 (default). REFINE=0 turns the refinement off.

• You can use the PREVIEW parameter to request the export of a bulk data representation of the
element edges and faces where glue elements are created. See Glue Preview.

• You can use the ESOPT parameter to change how the software handles the zero shell normal strain
condition for edge-to-surface glue. Shell theory does not account for changes in shell thickness or
normal strains perpendicular to the plane of the shell element. The ESOPT parameter gives you
a choice of how to handle the linking of the zero normal strains that exist in the shell element
associated with the edge (colored blue in the example), to the surface being glued (colored green in
the example).

Either of the ESOPT options properly transfers all forces and moments through the glue connection.
The resulting difference between these options is the local strains on the surface being glued.

ESOPT=0 (default) The strains in the plane of the surface being glued in the direction
perpendicular to the edge are not constrained by the glue stiffness.

ESOPT=1 The strains in the plane of the surface being glued on the area
corresponding to the shell element thickness (t/2) in the direction
perpendicular to the edge, are constrained by the glue stiffness.

10-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Glue Control Parameters

The following example illustrates the ESOPT options. It includes an equal compressive pressure load
on the top and bottom of the solid element mesh. The edge of the blue shell mesh is glued to the face
of the green solid mesh.

When ESOPT=0 (default), the deformations in the solid mesh demonstrate that the glue stiffness did
not prevent local strain at the glue interface.

When ESOPT=1, the deformations in the solid mesh demonstrate that the glue stiffness prevented
local strain at the glue interface.

Glue Parameter Descriptions for SOL 402

1. SOL 402 only supports BGOPT. Other parameters are ignored. The glue is therefore always a perfect
weld glue (GLUETYPE=2).

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-13
© 2023 Siemens
 10. Glue conditions

The BGOPT parameter must be defined as a local parameter. The BGPARM bulk entries associated
to individual BGSET bulk entries, which are then combined with a BGADD bulk entry, define local
parameters.

2. The BGOPT parameter adds a rotation constraint on the DOFs of the source nodes. You can choose
between the following options:

• You can let the software automatically choose the best option according to the source and target
region configurations that you defined for the glue pair (default).

• You can fully unconstrain the rotations.

• You can constrain the source nodal rotations using the target nodal rotations. This option can be
used for instance when you glue two regions of shells.

• You can constrain the source nodal rotations using target mean nodal displacements. This option
can be used, for example, when you glue shells to faces of volumes.

3. The following table describes the available BGOPT options according to the source and target
regions defined in the glue set GSID (BGSET entry).

Glue Type Source Target Allowed BGOPT values

Edge-to-Edge Glue BEDGE BEDGE 1
2
0 (default); same as BGOPT=2
Edge-to-Surface Glue BEDGE BSURF 2
3
0 (default); same as BGOPT=3
Surface-to-Surface Glue BSURF BSURF 1
2
3
0 (default); same as BGOPT=3
BSURF BSURFS 1
3
0 (default); same BGOPT=3

For the following source and target combinations, the BGOPT option is ignored.

10-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Glue Control Parameters

Glue Type Source Target

Edge-to-Surface Glue BSURFS BEDGE
BEDGE BSURFS
Surface-to-Surface Glue BSURFS BSURFS
BSURFS BSURF

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-15
© 2023 Siemens
 10. Glue conditions

10.5 SOL 401 - Contact and glue characteristic length

The software computes a characteristic length for contact and glue pairs and uses the value for
the penalty stiffness calculation as well as penetration tolerance calculations. The software-computed
penalty stiffness is proportional to the inverse of the characteristic length.

By default, the characteristic length for shell element regions is computed using the element face
geometry. It is computed by averaging the square roots of the element face areas in the source and
target regions. This computation is appropriate for all shell element regions.

You can define SYSTEM(780)=0, and the characteristic length for shell element regions is computed
using the average thickness of the elements. This was the default computation before Simcenter
Nastran version 2206. This calculation is only appropriate when a meaningful thickness is defined for the
shell elements in the contact/glue regions. If you include very thin shell elements in your region, this
calculation can be inappropriate.

The SYSTEM(780) options are as follows.

SYSTEM(780) Characteristic length calculation

=1 (Default) The characteristic length is computed using the face geometry of all shell and solid
element faces in the regions. It is computed by averaging the square roots of the
element face areas in the source and target regions.
=0 Characteristic length is computed using the element thickness over all shell elements in
the regions.
• Case 1: When both the source and target are shell element regions.
Characteristic length= 0.5*(average_source_thickness + average_target_thickness)/2
• Case 2: When the source is a shell element region but the target is not.
Characteristic length= 0.5* average_source_thickness
• Case 3: When the target is a shell element region but the source is not.
Characteristic length= 0.5* average_target_thickness

10-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Glue preview

10.6 SOL 401 - Glue preview

For SOL 401, you can optionally export a bulk data representation of the element edges and faces where
glue conditions are created. To do so, set the PREVIEW parameter on the BGPARM bulk entry to “1”. For
example:

$*
BGSET 100 1 2 0.001000
BGPARM 100 PREVIEW 1
$*

The software writes a bulk data file containing dummy shell element entries for face locations, and
dummy PLOTEL entries for edge locations. Dummy GRID, property, and material entries are also written.
You can import the file into a preprocessor to display both source and target glue locations.

The preview file has the naming convention:

<input_file_name>_glue_preview_<subcaseid>_<gluesetid>.dat

For example, if an input file named test.dat includes a subcase numbered 101 and a glue set numbered
201, the resulting preview file name is:

test_glue_preview_101_201.dat

In the following simple example, the red mesh is glued to the green.

Before applying any loading, the software creates the glue elements. This is the point in the solution in
which the preview output is written.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 10-17
© 2023 Siemens
 10. Glue conditions

The following illustration shows how the preview appears after you import the preview file into the
Simcenter 3D preprocessor. Note that the colors were manually modified in Simcenter 3D Pre/Post after
importing the file.

10-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 11. Output
11.1 Requesting output
The Nouti field on the TSTEP1 bulk entry controls the frequency of results output. See Defining solution
time steps (SOL 401) and Defining solution time steps (SOL 402).

For SOL 402, an output option is available to output displacement, velocity, acceleration, or reaction
forces for specific degrees-of-freedom for selected solution times. See SOL 402 - Plot output request.

The following table lists the supported output for SOLs 401 and 402.

Case Control Description

ACCELERATION Requests accelerations.
ADAPTERR Requests error estimates computed in a statics subcase (SOL 401 only).
BCRESULTS Requests contact forces, tractions, separation distance, and the total
and incremental slide distances.
BGRESULTS Requests glue forces and tractions.
BOLTRESULTS Requests the bolt force and the axial strain output in a bolt preload
subcase.
CKGAP Requests gap result output for chocking elements (SOL 401 only).
CRSTRN Requests grid point creep strains on elements.
CZRESULTS Requests results output for cohesive elements.
DISPLACEMENT Requests displacement output.
EKE Requests element kinetic energy output.
ELAROUT Requests element add/remove status output (SOL 401 only).
ELSTRN Requests elastic strain at grid points on elements.
ELSUM Requests output of an element property summary.
ESE Requests the output of the strain energy.
ESHLPNL Requests output for the tension only shell element for SOL 401.
FLXRESULTS Requests outputs for flexible sliders (SOL 402 only).
FORCE Requests element force output.
GCRSTRN Requests Gauss point creep strains on elements.
GELSTRN Requests elastic strain at Gauss points.
GMESTRN Requests mechanical strain at Gauss points (SOL 401 only).
GPFORCE Requests grid point force balance output.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-1
© 2023 Siemens
 11. Output

GPKE Requests kinetic energy at grid points in a modal subcase (SOL 401
only).
GPLSTRN Requests Gauss point plastic strain output on elements.
GSTRAIN Requests strain at Gauss points.
GSTRESS Requests stress at Gauss points.
GTHSTRN Requests thermal strain at Gauss points.
HOUTPUT Requests the harmonics for results output in the cyclic and Fourier
normal modes subcase types.
JRESULTS Requests outputs for kinematic joints (SOL 402 only).
JINTEG Requests output of the j-integral for crack analysis (SOL 401 only).
MEFFMASS Requests modal effective mass output in a modal subcase.
MESTRN Requests mechanical strain output at grid points on elements (SOL 401
only).
MONVAR Selects degree-of-freedom for a displacement monitor plot (SOL 402
only).
MPCFORCES Requests multipoint constraint force output.
OLOAD Requests the form and type of applied load vector output.
OMODES Requests selects a set of modes for output.
OPRESS For SOLs 401 and 402 including the Simcenter 3D Multiphysics
environment, requests output of the fluid penetrating pressure load
defined with the PLOADFP bulk entry.
For the Simcenter 3D Multiphysics environment running SOL 401,
requests the output of pressure computed by the Simcenter 3D Thermal
solver.
OSTNINI Requests initial strain output when an initial stress or strain is defined
(SOL 401 only).
OTEMP Requests solution temperatures output on grid points.
PFRESULTS Requests progressive failure results output for composite solid
elements.
PLSTRN Requests grid point plastic strain output on elements.
SEKETAB For the modes subcases (normal modes, cyclic modes, Fourier modes,
and complex modes subcases), requests the percentage of strain
energy and the percentage of kinetic energy for groups of elements.
The software writes the output to the .f06 file and to a .csv file. (SOL
402 only).
SET Defines a set of element or grid point numbers to be plotted (SOL 402
only).
SETMC Sets definitions for modal, panel, and grid contribution results (SOL 402
only).

11-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Requesting output

SETMCNAME Specifies the title of a displacement monitor plot (SOL 402 only).
SHELLTHK Requests shell thickness output (SOL 402 only).
SPCFORCES Requests single-point force of constraint vector output.
STATVAR Requests state variable output computed by an external user defined
material routine.
STRAIN Requests element strain output.
STRESS Requests element stress output.
THSTRN Requests thermal strain at grid points on elements.
VELOCITY Requests velocity at grid points.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-3
© 2023 Siemens
 11. Output

11.2 Gauss point output

SOLs 401 and 402 support the following case control commands to request the output of the stress
and strain values computed at the Gauss points, and then reported at the element corners with no
extrapolation:

Output at the element Gauss points

Case control command Requested result
GSTRESS Stress computed at the element Gauss points.
GSTRAIN Total strain computed at the element Gauss points.
GCRSTRN Creep strain computed at the element Gauss points.
GELSTRN Elastic strain computed at the element Gauss points.
GPLSTRN Plastic strain computed at the element Gauss points.
GTHSTRN Thermal strain computed at the element Gauss
points.
GMESTRN (SOL 401 only) Mechanical strain computed at the element Gauss
points.

Note that SOLs 401 and 402 also support the stress and strain output that is extrapolated using the
element shape functions from the Gauss point to the element corners. You use the STRESS, STRAIN,
CRSTRN, ELSTRN, PLSTRN, and THSTRN case control commands to request the output extrapolated to the
element corner.

The following elements support the Gauss point output:

• The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

• The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8.

• The axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6.

• The 3D solids elements CTETRA, CHEXA, CPENTA, CPYRAM.

You can define the number of integration points for an element with the IN field on the PSOLID bulk
entry, or the FOROPT field on the PPLANE bulk entry. Regardless of the number of integration points
you request, the software outputs the same number of Gauss point results as the number of corner
grid points. In general, the Gauss point closest to a corner grid point is used for the output. The SOL
401 Gauss point mapping table and SOL 402 Gauss point mapping table below show the corner grid
point to Gauss point mapping for each element type and integration point option.

SOL 401 Gauss point mapping table

11-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Gauss point output

Element Description Number of integration Corner grid point to

points Gauss point mapping
CPLSTS4, CPLSTN4, Plane stress, plane 4 integration points Corner Grid Gauss
CCHOCK4, CQUADX4 strain, chocking, Point Point
or axisymmetric
quadrilateral element 1 N1
with 4 grid points. 2 N2
3 N4
4 N3

CPLSTS8, CPLSTN8, Plane stress, plane 4 integration points Corner Grid Gauss
CQUADX8 strain, or axisymmetric Point Point
quadrilateral element
with 4 or 8 grid points. 1 N1
2 N2
3 N4
4 N3

9 integration points Corner Grid Gauss

Point Point
1 N1
2 N3
3 N9
4 N7

CCHOCK8 Chocking element with 9 integration points Corner Grid Gauss

8 grid points. Point Point
1 N1
2 N3
3 N9
4 N7

CPLSTS3, CPLSTN3, Plane stress, plane 1 integration point Corner Grid Gauss
CTRAX3 strain, or axisymmetric Point Point
triangular element with
3 grid points. 1 N1

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-5
© 2023 Siemens
 11. Output

2 N1
3 N1

3 integration points Corner Grid Gauss

Point Point
1 N1
2 N2
3 N3

CCHOCK3 Chocking element with 3 integration points Corner Grid Gauss

3 grid points. Point Point
1 N1
2 N2
3 N3

CCHOCK6 Chocking element with 7 integration points Corner Grid Gauss

6 grid points. Point Point
1 N2
2 N3
3 N4

CPLSTS6, CPLSTN6, Plane stress, plane 3 integration points Corner Grid Gauss
CTRAX6 strain, or axisymmetric Point Point
triangular element with
6 grid points. 1 N1
2 N2
3 N3

11-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Gauss point output

7 integration points Corner Grid Gauss

Point Point
1 N2
2 N3
3 N4

CTETRA Four-sided solid element 1 integration point Corner Grid Gauss

with four to ten grid Point Point
points.
1 N1
2 N1
3 N1
4 N1

4 integration points Corner Grid Gauss

Point Point
1 N1
2 N2
3 N3
4 N4

5 integration points Corner Grid Gauss

Point Point
1 N2
2 N3
3 N4
4 N5

CHEXA Six-sided solid element 8 integration points Corner Grid Gauss

with eight to twenty grid Point Point
points.
1 N8
2 N7
3 N5
4 N6
5 N4

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-7
© 2023 Siemens
 11. Output

6 N3
7 N1
8 N2

27 integration points Corner Grid Gauss

Point Point
1 N27
2 N25
3 N19
4 N21
5 N9
6 N7
7 N1
8 N3
CPENTA Five-sided solid element 2 integration points Corner Grid Gauss
with six to fifteen grid Point Point
points.
1 N1
2 N1
3 N1
4 N2
5 N2
6 N2
6 integration points Corner Grid Gauss
Point Point
1 N1
2 N2
3 N3
4 N4
5 N5
6 N6

11-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Gauss point output

9 integration points Corner Grid Gauss

Point Point
1 N1
2 N2
3 N3
4 N7
5 N8
6 N9
21 integration points Corner Grid Gauss
Point Point
1 N7
2 N5
3 N6
4 N21
5 N19
6 N20

CPYRAM Five-sided solid element 8 integration points Corner Grid Gauss

with five to thirteen grid Point Point
points.
1 N8
2 N4
3 N2
4 N6
5 A5*

A5* is the average of

N1, N3, N5, and N7.
27 integration points Corner Grid Gauss
Point Point
1 N27
2 N9
3 N3
4 N21
5 N13

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-9
© 2023 Siemens
 11. Output

SOL 402 Gauss point mapping table

Element Description Number of integration Corner grid point to

points Gauss point mapping
CPLSTS4, CPLSTN4, Plane stress, plane 4 integration points Corner Grid Gauss
CQUADX4, CPLSTS8, strain, or axisymmetric Point Point
CPLSTN8, CQUADX8 quadrilateral element
with 4 or 8 grid points. 1 N1
2 N3
3 N4
4 N2

9 integration points Corner Grid Gauss

Point Point
1 N1
2 N7
3 N9
4 N3

CPLSTS3, CPLSTN3, Plane stress, plane 1 integration point Corner Grid Gauss
CTRAX3 strain, or axisymmetric Point Point
triangular element with
3 grid points. 1 N1
2 N1
3 N1

11-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Gauss point output

3 integration points Corner Grid Gauss

Point Point
1 N3
2 N2
3 N1

CPLSTS6, CPLSTN6, Plane stress, plane 3 Corner Grid Gauss

CTRAX6 strain, or axisymmetric Point Point
triangular element with
6 grid points. 1 N3
2 N2
3 N1

6 integration points Corner Grid Gauss

Point Point
1 N1
2 N2
3 N3

CTETRA Four-sided solid element 1 integration point Corner Grid Gauss

with four to ten grid Point Point
points.
1 N1
2 N1
3 N1
4 N1

4 integration points Corner Grid Gauss

Point Point
1 N4
2 N1
3 N2
4 N3

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-11
© 2023 Siemens
 11. Output

8 integration points Corner Grid Gauss

Point Point
1 N8
2 N5
3 N6
4 N7

CHEXA Six-sided solid element 8 integration points Corner Grid Gauss

with eight to twenty grid Point Point
points.
1 N1
2 N5
3 N7
4 N3
5 N2
6 N6
7 N8
8 N4
27 integration points Corner Grid Gauss
Point Point
1 N1
2 N19
3 N25
4 N7
5 N3
6 N21
7 N27
8 N9

11-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Gauss point output

CPENTA Five-sided solid element 2 integration points Corner Grid Gauss

with six to fifteen grid Point Point
points.
1 N1
2 N1
3 N1
4 N2
5 N2
6 N2
6 integration points Corner Grid Gauss
Point Point
1 N5
2 N3
3 N1
4 N6
5 N4
6 N2
9 integration points Corner Grid Gauss
Point Point
1 N7
2 N4
3 N1
4 N9
5 N6
6 N3
21 integration points Corner Grid Gauss
Point Point
1 N1
2 N4
3 N7
4 N3
5 N6
6 N9

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-13
© 2023 Siemens
 11. Output

CPYRAM Five-sided solid element 5 integration points Corner Grid Gauss

with five to thirteen grid Point Point
points.
1 N1
2 N2
3 N3
4 N4
5 N5

6 integration points Corner Grid Gauss

Point Point
1 N1
2 N2
3 N3
4 N4
5 N6

8 integration points Corner Grid Gauss

Point Point
1 N1
2 N2
3 N3
4 N4
5 A5*

A5* is the average of

N5, N6, N7, and N8.

11-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Iterations per subcase summary

11.3 SOL 402 - Iterations per subcase summary

For each time step, the software iterates until convergence occurs.

Time steps that converge are accepted, and the software continues to the next time step.

Time steps that do not converge are rejected, and the software can subincrement the time step.

The software considers all of the iterations in an accepted time step as "accepted iterations", and
considers all of the iterations in a rejected time step as "rejected iterations".

The software writes the following summary in the *.f06 file at the end of each static, dynamic, and
preload subcase.

MEAN NUMBER OF ITERATIONS PER ACCEPTED TIME STEP... 8.5

MAXIMUM NUMBER OF ITERATIONS FOR AN ACCEPTED STEP.. 44
TOTAL NUMBER OF ITERATIONS......................... 89
...NUMBER OF ACCEPTED ITERATIONS................... 29
...NUMBER OF REJECTED ITERATIONS................... 60
TOTAL NUMBER OF TIME STEPS......................... 25
...NUMBER OF ACCEPTED TIME STEPS................... 10
...NUMBER OF REJECTED TIME STEPS................... 15
ACCEPTED TIME STEP MEAN SIZE....................... 5.0035E-02

• MEAN NUMBER OF ITERATIONS PER ACCEPTED TIME STEP is the average number of iterations
computed for all accepted time steps. When the software computes the total number of iterations for
each accepted time step, it includes all iterations (accepted and rejected) beginning after a previous
accepted time step to the end of an accepted time step. For example, the total number of iterations
computed for the following time steps is listed below.

Example time steps:

….
Time step 5, end time=2.8 is accepted. It included 3 accepted iterations and 1 rejected iteration.
Time step 6, end time=3.0 is accepted. It included 3 accepted iterations.
Time step 7, end time=3.2 is rejected. It included 2 accepted iterations and 3 rejected iterations.
Time step 8, end time=3.1 is accepted. It included 4 accepted iterations and 2 rejected iterations.
…..

Resulting number of iterations:

Time step 5 has a total of 4 iterations.

Time step 6 has a total of 3 iterations.
Time step 7 is rejected, so its iterations carry to the next time step.
Time step 8 has a total of 11 iterations (5 iterations from the previous time step, and 6 iterations from

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-15
© 2023 Siemens
 11. Output

the current time step).

The sum of all iterations for the three accepted time steps is (4 + 3 + 11) = 18, and the mean is (18/3)
= 6 iterations.

• MAXIMUM NUMBER OF ITERATIONS FOR AN ACCEPTED STEP is the maximum number of

iterations out of all the accepted time steps. When the software computes the total number of
iterations for each accepted time step, it includes all iterations (accepted and rejected) beginning after
a previous accepted time step to the end of an accepted time step. For example, for the time steps
listed above, the maximum number of iterations occured at time step 8 (11 iterations).

• TOTAL NUMBER OF ITERATIONS is the sum of all iterations (accepted and rejected iterations) for
all time steps (accepted and rejected time steps) in the subcase.

• NUMBER OF ACCEPTED ITERATIONS is the sum of the accepted iterations for all time steps
(accepted and rejected time steps) in the subcase.

• NUMBER OF REJECTED ITERATIONS is the sum of the rejected iterations for all time steps
(accepted and rejected time steps) in the subcase.

• TOTAL NUMBER OF TIME STEPS is the sum of all time steps (accepted and rejected time steps) in
the subcase.

• NUMBER OF ACCEPTED TIME STEPS is the sum of the accepted time steps in the subcase.

• NUMBER OF REJECTED TIME STEPS is the sum of the rejected time steps in the subcase.

• ACCEPTED TIME STEP MEAN SIZE is the total physical time for the subcase divided by the number
of accepted time steps in the subcase.

11-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Plot output request

11.4 SOL 402 - Plot output request

For SOL 402, an output option is available to output displacement, velocity, acceleration, or reaction
forces for specific degrees-of-freedom for selected solution times. This output is useful, for example,
when you plan to create output plots at specific degrees-of-freedom at many or perhaps all solution
times, but you prefer the results output for the entire model only at the end time. This more specific
request reduces the amount of output data required.

You use the OUTMGT case control command to request the plot output, which selects the OUTMGT bulk
entry. The OUTMGT entry includes the following fields to select the type and location for the output.

1 2 3 4 5 6 7 8 9 10
OUTMGT SID TYPE ID RES COMP CID

• The TYPE field specifies if the result output is for a single grid point ("NODE") or a group of grid points
("NODGRP").

• The ID field is the ID of a single grid point when TYPE=NODE, or the ID of a GROUP bulk entry which
selects multiple grid points when TYPE=NODGRP.

• The RES field selects the result type. SOL 402 supports "DISP", "VELOC", "ACCEL", "REAC".

• The COMP field selects the components to output. Choices are "X", "Y", "Z", "RX", "RY", "RZ", "ALL",
"ALLTRANS", or "ALLROT".

• The CID field selects a coordinate system to output the grid point results. The default is the basic
coordinate system.

You can define the DISPLACEMENT,VELOCITY, ACCELERATION, and SPCFORCE case control commands
to request the results output for the entire model, and also define the OUTMGT command to
request the plot output at specific degrees-of-freedom. You can use the following to control the
output frequency for the DISPLACEMENT,VELOCITY, ACCELERATION, SPCFORCE request and the OUTMGT
request independently:

• You can use the IA19 parameter on the NLCNTL2 bulk entry to control the output frequency for the
OUTMGT request. For example, if you define IA19=1, the results requested with the OUTMGT command
are output at all time steps.

• You can use the NOUT field on the TSTEP1 bulk entry to control the output frequency for the
DISPLACEMENT, VELOCITY, ACCELERATION, and SPCFORCE request (and any other results requests such
as STRESS, STRAIN, etc.). The NOUT definition applies only to the time steps specified by the TSTEP1
entry. If additional time steps are created by the software as a result of the automatic stepping methods,
they would not apply to the NOUT request.

• You can use the IA16 parameter on the NLCNTL2 bulk entry to refine the output frequency for the
DISPLACEMENT, VELOCITY, ACCELERATION, and SPCFORCE request (and any other results requests such

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-17
© 2023 Siemens
 11. Output

as STRESS, STRAIN, etc.). The IA16 definition applies to all computed time steps, including additional
time steps created by the software as a result of the automatic stepping methods.

The relationship between the IA16 parameter and the NOUT field on the TSTEP1 bulk entry is as follows:
NOUT saves results at a frequency relative to the time steps defined on TSTEP1. IA16=n saves results at
a frequency of n between two NOUT time steps. For example, if a computation goes from 0 to 1.0 in 10
increments, the solution points will be (.1, .2, .3, .4, .5, .6, .7, .8, .9, 1.0). If NOUT=5 and IA16=2, the
NOUT=5 request will output results every 5 increments, or at .5 and 1.0. The IA16=2 request will output
results every two increments between the NOUT increments, or every two from (.1 to .5) which is .2 and
.4, and every two increments from (.5 to 1.0) which is .7 and .9. Output will occur at 0.2 (due to IA16),
0.4 (due to IA16), 0.5 (due to NOUT), 0.7 (due to IA16), 0.9 (due to IA16), and 1.0 (due to NOUT).

Note:
Because the software uses grid point results for XY plotting, IA16 and IA19 must be a multiple of
each other (depending on which is larger). Because IA16 is typically used to output results at all
grid points for fewer solution points, and IA19 is used to output results at specific DOF for many
solution points, IA19 is typically defined smaller than IA16.
For example, if IA16=8, IA19 can be 1, 2, 4, 8 (or 16, 24, 32, etc. if you want IA19 to be larger
than IA16).

11-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Iteration related output data

11.5 SOL 401 - Iteration related output data

SOL 401 writes convergence data to the .f06 file. The following example demonstrates the format of this
output.

The software might need to iterate at a time/solution point when searching for a solution that
satisfies convergence. The output format includes the following numbering in the first two columns:

1. The first column is the accumulated number of iterations for the current subcase. This number is
reset to 1 at the start of a new subcase.

2. The second column is the iteration number for the current time/solution point. This number is reset
to 1 at the start of a new time/solution point.

For example, if a subcase includes 4 time points, and the number of iterations for each time point is:

Time Point 1 has five iterations,

Time Point 2 has three iterations,
Time Point 3 has four iterations,
Time Point 4 has three iterations,

the numbers in the first columns would be as follows:

Accumulated number Current iteration Accumulated number Current iteration

of iterations number of iterations number
Time Point 1 Time Point 3
1 1 9 1
2 2 10 2
3 3 11 3
4 4 12 4
5 5

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-19
© 2023 Siemens
 11. Output

Accumulated number Current iteration Accumulated number Current iteration

of iterations number of iterations number
Time Point 2 Time Point 4
6 1 13 1
7 2 14 2
8 3 15 3

You can define any combination of U, P, and W with the CONV parameter on the NLCNTL bulk
entry to request which of displacement (U), force (P), and work (W) the software will consider for the
convergence criteria.

If you do not define force (P) on the CONV parameter, a solution is converged when both of the
following are satisfied (1 and 2):

1. All of the checks requested with CONV (either displacement, work, or both) if you define CONV, or the
work check if you do not define CONV (default behavior).

2. Either of the following is satisfied (a or b):

a. The L2 norm of the residual for the current iteration is less than the L2 norm of the residual from the
first iteration for the time step.

b. The error in force is less than EPSP.

The value listed in the header of the RMAG column is the L2 norm of the residual from the first iteration
for the first time step listed in the table. The software computes a new RMAG value for each time step.

If you define force (P) on the CONV parameter (either CONV=P, UP, PW or UPW), a solution is converged
when all the checks requested with CONV (displacement, load, work) are satisfied, and RMAG is no
longer checked.

For each active convergence criteria, which is designated with the * next to the name in the output, the
software includes the "n" or "y" next to the computed convergence value for that iteration, where "n"
indicates that the specific criteria was not satisfied, and "y" indicates that it was satisfied.

See SOL 401 - Error functions and weighted normalization.

11-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Iteration related output data

For the contact convergence data, there are three convergence tolerance columns. In addition, the
software includes the "n" or "y" next to the computed convergence values for each iteration, where "n"
indicates that the specific criteria was not satisfied, and "y" indicates that it was satisfied.

1. The first column depends on the contact convergence criteria you select with the CNTCONV
parameter on the BCTPARM bulk entry:

- When CNTCONV=1 (default), the contact convergence criteria uses the penetration tolerance
(PTOL parameter). In this case, the first column is labeled PENETR.

- When CNTCONV=2, the contact convergence criteria uses the traction tolerance (CTOL
parameter). In this case, the first column is labeled TRACTN.

2. The second column represents the contact force tolerance (RTOL parameter) and is labeled FORCE.

3. The third column represents the contact damping tolerance (DCTOL parameter). It is labeled DAMP.

The CTDAMP parameter on the BCTPARM bulk entry is available to request the stabilization
damping option when you are relying on the contact condition to prevent rigid body conditions,
but the contact condition is not fully active.

The DCTOL parameter is available on the BCTPARM bulk entry to adjust the stabilization damping
tolerance. When you request stabilization damping, the software will ramp the damping tractions
down as it iterates at a solution point until convergence is satisfied.

See SOL 401 - Contact convergence.

See SOL 401 - Contact message output.

Note:
In addition to the three contact convergence checks described above, if you did not request the
displacement convergence criteria by including "U" with the CONV parameter on the NLCNTL bulk
entry, the software also performs the following contact relative displacement tolerance check.

where c is a contact element,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-21
© 2023 Siemens
 11. Output

nce is the total number of contact elements in all pairs,

urel is the relative displacement of the nodes associated with a contact element, and

Δurel is the change in the relative displacement from the last converged solution/time point to the
current iteration.

You can adjust this threshold with the DPTOL parameter on the BCTPARM bulk entry.

The status of this check is included in the global contact summary message output in the .f06 file under
the column RELATIVE DISP. See SOL 401 - Contact message output.

It is not represented in the three contact data columns described above. It is possible for all three contact
data columns to be satisfied and have a "y" in their respective column, yet the contact displacement
convergence check has failed. If this occurs, the contact problem will not be fully converged, and will
result with an "n" in the CON column described below.

The software includes a column that summarizes the status for the solution convergence (EQU
column), the contact convergence (CON column), and the bolt preload convergence (BLT column). For
example, when both contact and bolt preload are present in the solution, all three must have a "y" for
the iteration to be considered converged.

Note:
The bolt preload convergence column (BLT) is applicable only to bolts defined with ETYPE =1 or
ETYPE=3, and not to a bolt defined with ETYPE=2.

11-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Solution accuracy indicator

11.6 SOL 401 - Solution accuracy indicator

Some nonlinear solutions require stabilization methods such as contact damping or matrix stabilization.
For example, when you are relying on contact to ground one or more bodies. These numerical
stabilization options are appropriate provided they do not influence the structural response.

You can request for SOL 401 to print the following solution accuracy indicators table to the .f06 file by
defining MSGLVL=2 on the NLCNTL bulk entry.

The software prints the table after each time step converges. The table includes the following:
• The L1 norm for the total force and the work computed from the total force.
• The L1 norm for the force attributed to each stabilization mechanism and the work computed from
each of these forces.
• The percentage of force and work each mechanism contributes to the total. The percentage of force
and work attributed to the stabilization mechanisms should be a relatively smaller number.

The L1 vector norm for the total force is computed from the force vector with n degrees of freedom:

The work associated with each of the quantities is computed as follows:

1. Internal work: , where is the total load acting on the structure and is the
displacement vector.

2. Work due to contact damping: , where is the force due to contact damping.

3. Work due to stiffness stabilization: , where is the stiffness stabilization

portion of the stiffness matrix.

The contact damping referenced in the table is requested with the CTDAMP parameter on the BCTPARM
bulk entry, and the stiffness stabilization referenced in the table is requested with the MSTAB parameter
on the NLCNTL bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-23
© 2023 Siemens
 11. Output

If you requested the output but did not request contact damping and/or matrix stabilization, the table is
still printed but with zero values.

11-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Residual output

11.7 SOL 401 - Residual output

For SOL 401, you can request the output of residual force vectors to universal files. You use the NRRFOUT
parameter on the NLCNLTL bulk entry to request the output.

You can open universal files in Simcenter 3D Pre/Post using the companion results import and display
contour plots of the results. Contour displays of the residual vector components or magnitude can help
you determine locations where the residual force is high. For example, you may find the largest residual
occurs in a contact region. If the solution continues to iterate and not converge, you might consider
ending the solution, temporarily softening the contact stiffness in that location to stabilize the problem,
and then restarting the solution.

You can request the output using the following choices:

NRRFOUT=N (where N>0): The software writes a *.unv file after each iteration of the current time step.
It keeps the *.unv files corresponding to the last N iterations of the current time step by removing the
oldest file when a new iteration and new *.unv file begins. This continues until the current time step
converges, in which case the software removes all *.unv files associated with that time step. This process
repeats for each time step.

NRRFOUT=-1: The software writes a*.unv file after each iteration of the current time step. It keeps the
*.unv files corresponding to all iterations of the current time step until the time step converges, in which
case it removes the files associated with that time step. This process repeats for each time step.

NRRFOUT=-2: The software writes a *.unv file after each iteration of each time step. It does not remove
the *.unv files after a time step converges. At the end of the solution, the *.unv files from all iterations
and all time steps remain.

NRRFOUT=0 (default): No output occurs.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-25
© 2023 Siemens
 11. Output

11.8 Types of strain output

The following table summarizes all of the strain output requests supported by SOL 401:

Type of Case Control

strain * Description
Total STRAIN / Total strain = Elastic strain + Thermal strain + Plastic strain + Creep
GSTRAIN strain - Initial strain
Output includes the von Mises total strain and the total strain
tensor.
Elastic ELSTRN / Recoverable strain as a result of mechanical loads.
GELSTRN
Output includes the von Mises elastic strain and the elastic strain
tensor.
Thermal THSTRN / Recoverable strain as a result of thermal loads.
GTHSTRN
Output includes the von Mises thermal strain and the thermal strain
tensor.
Initial OSTNINI Strain resulting from an initial stress or strain defined with the INITS
bulk entry.
Output includes the von Mises initial strain and the initial strain
tensor.
Plastic PLSTRN / Permanent strain resulting from plastic material.
GPLSTRN
Output includes the effective plastic strain and the plastic strain
tensor.
Creep CRSTRN / Permanent strain resulting from creep material.
GCRSTRN
Output includes the effective creep strain and the creep strain
tensor.
Mechanical MESTRN / Mechanical strain = Elastic strain + Plastic strain + Creep strain
GMESTRN
Output includes the effective mechanical strain and the mechanical
strain tensor.

The following table summarizes all of the strain output requests supported by SOL 402:

Type of Case Control

strain * Description
Total STRAIN / Total strain = Elastic strain + Thermal strain + Plastic strain + Creep
GSTRAIN strain - Initial strain

11-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Types of strain output

Type of Case Control

strain * Description
Output includes the von Mises total strain and the total strain
tensor.
Elastic ELSTRN / Recoverable strain as a result of mechanical loads.
GELSTRN
Output includes the von Mises elastic strain and the elastic strain
tensor.
Thermal THSTRN / Recoverable strain as a result of thermal loads.
GTHSTRN
Output includes the von Mises thermal strain and the thermal strain
tensor.
Initial OSTNINI Strain resulting from an initial stress or strain defined with the INITS
bulk entry.
Output includes the von Mises initial strain and the initial strain
tensor.
Plastic PLSTRN / Permanent strain resulting from plastic material.
GPLSTRN
Output includes the effective plastic strain and the plastic strain
tensor.
Creep CRSTRN / Permanent strain resulting from creep material.
GCRSTRN
Output includes the effective creep strain and the creep strain
tensor.

*Most of the strain output types include two case control commands, one to request strain output
at grid points on elements, and the other to request strain output at Gauss points. For example, you
use the STRAIN command to request the total strain at the grid points on elements, and you use the
GSTRAIN command to request the total strain at the Gauss points.

For the initial strain output, you can use the GRID or GAUSS describer on the OSTNINI command to
request the initial strain output at grid points on elements or initial strain output at Gauss points,
respectively.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-27
© 2023 Siemens
 11. Output

11.9 SOL 401 - Grid point force output

The grid point force requested with the GPFORCE case control command outputs the applied loads, the
SPC forces, the MPC forces, and the internal element forces at each grid point.

Pre-Simcenter Nastran 2021.2, the software summed all the applied loads at a grid point and included
this in the "APP-LOAD" row in the grid point force output at each grid point.

Beginning with Simcenter Nastran 2021.2, the software separates the applied load into nodal loads
and element loads. Currently, the element loads only include the rotational body-loads defined with the
RFORCE and RFORCE1 bulk entries. All other applied loads, except for thermal loads, are included as
nodal loads. SOL 401 includes the thermal loads with the internal element forces.

With the new format, the software separates the rotational body-loads at each grid point by the
contribution from each connected element. For example, in the grid point force output below, grid
point 5 is shared by the two CHEXA elements 1 and 2. The two "ELM-LOAD" rows represent the rotational
body-loads for each, the two "HEXA" rows represent the element internal force for each, and the single
"NOD-LOAD" represents all other applied loads.

In addition, beginning with Simcenter Nastran 2021.2, the software computes the rotational body-loads
as a result of the RFORCE and RFORCE1 entries with a new method. The new method computes the load
vectors on an element basis rather than a grid point basis. The element basis is required in order for the
software to separate the rotational body-loads into the new "ELM-LOAD" rows in the GPFORCE output.

The system cell 771 is available to change both the GPFORCE output format and the body-load
computation method.

SYSTEM(771)=0 (default): The new GPFORCE output format and the new element based body-load
computation is used.

SYSTEM(771)=1: The old GPFORCE output format and the new element based body-load computation is
used.

SYSTEM(771)=2: The old GPFORCE output format and the old grid point body-load computation is used.

Note that options 1 and 2 will not produce the refined free body results needed for Simcenter 3D post
processing.

Additional information:

11-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Grid point force output

• Forces as a result of contact and glue conditions are not included in the grid point force output.

• Because a grid point is in equilibrium, the sum of grid point forces at a grid point is 0.0, unless contact
or glue is present at the grid point location.

• Forces from rigid elements will be included with the "MPC-LOAD" unless a rigid element is using the
stiff beam formulation. The stiff beam is included with the internal element forces.

• In a dynamics subcase, the inertia and damping forces are included with the internal element forces.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-29
© 2023 Siemens
 11. Output

11.10 SOL 402 - Modal participation factors and effective mass

For the SOL 402 modal and cyclic modes subcases, you can request modal participation factor and
effective mass output using the MEFFMASS case control command.

Modal participation factor and effective mass measure the amount of mass moving in each direction for
each mode. A high value indicates the mode will be excited by excitations in that direction.

SOL 402 supports the PRINT describer on the MEFFMASS command. For example, the following
instruction causes the software to write the modal participation factor and effective mass output to
the .f06 and .csv files:

MEFFMASS(PRINT)=YES

Results are available in the .f06 file under the headings MODAL PARTICIPATION FACTOR and MODAL
EFFECTIVE MASS.

The MEFFMASS command must be applied above the subcase level (globally), and applies to all modal
and cyclic modes subcases.

For the cyclic modes subcase:

• For harmonics 0 and 1, the output contains modal participation factor and effective mass results for
the entire, recombined structure for both single-stage and multi-stage cyclic symmetry.

• For harmonics > 1, the output contains:

• Modal participation factors and effective mass results for only one sector and using only the real
part of the mode.

• Modal participation factor results for both single-stage and multi-stage cyclic symmetry.

• Effective mass results for only single-stage cyclic symmetry, and only for the translational
components.

• The result for each harmonic is a double mode. When you change the number of processors or
threads with DMP and SMP runs, the form of these mode pairs will change. Because the modal
participation factors are based on the form of the modes, they will also change. You can verify that
the total modal participation result is the same for each mode in a pair by comparing the sum of their
participation factors squared.

Computation details

The modal participation matrix [ε] is computed as:

11-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Modal participation factors and effective mass

where:

m is the generalized mass matrix

φ are the eigenvectors
M is the mass matrix reduced to the a-set (g-set for superelements)
D is the rigid body transformation matrix with respect to the a-set

For a single mode i, the modal participation (εir) is computed as:

where:

i represents the mode number

r represents the rigid body direction (1 - 6)

The modal effective mass (Meff, ir) for a single mode and rigid body direction is computed as:

The modal effective mass fraction is computed by dividing the modal effective mass by the rigid body
mass, where the rigid body mass is computed as:

The total modal effective mass fraction is the sum of all the individual fractions and would total to 1.0
if all modes were computed. But in general, mode truncation results in a total modal effective mass less
than 1.0.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 11-31
© 2023 Siemens
 11. Output

11-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 12. Restart solution
12.1 SOL 401 Restart
A restart solution is a method of continuing from a previous run without having to start from the
beginning. For example, an initial run could be a pre-stressed condition which includes a bolt preload
subcase and multiple static subcases. You can then use the restart file created from the initial run in
repeated restart solutions.

The restart solution is also useful when a solution fails to converge. The software saves the completed
solution points up to the failed time point. When restarting, you can reduce the size of your solution
increments or perhaps adjust the nonlinear control parameters to help convergence.

For the restart run, you can change load, SPC, MPC, element birth/death, contact, and subcase defined
nonlinear control parameters. By default, you cannot create new grid points or elements, change grid
point locations, change glue conditions, or modify materials. See Model check.

Note:
The referenced restart .op2 file must have been generated using a release in the same major
release family as the restart run is being executed in. This is due to the fact that .op2 schema may
change between major releases.

Initial run

The initial solution input file can include any combination of static, dynamic, and preload subcase types.
The modal, cyclic, Fourier subcase types, and nonlinear buckling are not supported in the initial run.

For the initial run, when you include the parameter definition RSTGEN=YES on the NLCNTLG bulk entry,
the software writes restart data to the same .op2 file in which results are written. The .op2 file produced
from the initial run will include saved restart solution points from the end of each static, dynamic, and
preload subcase. In addition, if convergence fails in a static or dynamic subcase, a restart point is written
from the last converged time step. If a preload subcase fails to converge, no restart point is written for
that subcase. A preload subcase must complete for a restart point to be written.

For example, the following input file structure includes the parameter definition RSTGEN=YES on the
NLCNTLG bulk entry to request restart data. If all three subcases complete, restart data will be written to
the .op2 file at the end of each.

....
LGDISP=1
SUBCASE 1
ANALYSIS=PRELOAD
SUBCASE 2
ANALYSIS=STATICS
SUBCASE 3

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 12-1
© 2023 Siemens
 12. Restart solution

ANALYSIS=STATICS
....
BULK DATA
NLCNTLG,RSTGEN,YES
....

When you request an initial solution with RSTGEN = YES, the .op2 file is always written as 64-bit, and the
parameter OP2FMT is ignored.

Restart run

In your restart input file, you will include an ASSIGN statement that references the .op2 file created from
the initial solution. The ASSIGN statement must include a unit number of 161 or larger. In addition, if
the unit number on your ASSIGN statement is not 161, you must define the parameter RSTUNIT=unit
number on the NLCNTLG bulk entry.

Example one:

ASSIGN INPUTT2='OUTDIR:restart_op2_filename.op2' UNIT=161

....
BULK DATA
***NLCNTLG,RSTUNIT is not required for this example since UNIT=161**
....

Example two:

ASSIGN INPUTT2='OUTDIR:restart_op2_filename.op2' UNIT=201

....
BULK DATA
NLCNTLG,RSTUNIT,201
***NLCNTLG,RSTUNIT is required for this example since UNIT>161**
....

If your restart run input file has the same name as your initial run input file, you should rename the .op2
file created from the initial run if you want to preserve it. Otherwise, it will be overwritten during the
restart solution. Your ASSIGN statement should also reflect the new .op2 file name.

The .op2 file created from the initial run can include saved restart solution points from multiple
subcases. For the restart run, you use the parameter RSTFROM=n on the NLCNTLG bulk entry to select
which initial subcase ID to restart from. Since the RSTFROM=n parameter has no default, it is required.

The start time for a restart solution is always the end or final time of the solution point you are restarting
from. For example, let us assume your initial solution included a subcase 1 with time going from 0.0
to 10.0 seconds, a subcase 2 with time going from 10.0 to 30.0 seconds, and all time steps converged
successfully for each subcase. If you restart from subcase 2, the start time will be 30.0 seconds. If your
first subcase in the restart input file includes a TSTEP1 bulk entry with an end time of 40 seconds, and
a number of increments of 5, the time steps for this restart subcase will be 32.0, 34.0, 36.0, 38.0, and
40.0 seconds.

12-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 Restart

The number of subcases and their IDs in the restart input file can be the same as those used in the
initial run, or they can be completely different. You use the parameter EXEFROM=n on the NLCNTLG bulk
entry to select a subcase ID in the restart run input file in which to begin the restart solution. Since
the EXEFROM=n parameter has no default, it is required. The software automatically makes the subcase
you select with EXEFROM=n sequentially dependent on the subcase you select with RSTFROM=n, even if
SEQDEP=NO is defined in the subcase selected by EXEFROM=n.

For example, suppose your initial run included three subcases with IDs 1, 2, and 3, all three completed,
and you have decided to restart from the initial subcase 2 by defining the parameter RSTFROM=2 in your
restart input file. In addition, your restart input file has the subcase IDs 1, 3, 5, and 7 and you would like
to begin the restart solution with subcase 5. As a result, you will also define EXEFROM=5 in your restart
input file. See Special case: EXEFROM=RSTFROM below.

You can request restart data from a restart run by including the parameter definition RSTGEN=YES on
the NLCNTLG bulk entry in the restart run input file. This is useful when convergence problems are
occurring. With each consecutive restart, you are saving the solution progress.

You can define any of the subcase types in the restart input file. Although, if the subcase you select with
RSTFROM is a dynamics subcase, the subcase you select with EXEFROM cannot be a modal, cyclic, or
Fourier.

In all restart runs, the software copies the results from the initial run .op2 file into the .op2 file created
in the restart run. As a result, the restart .op2 will include both the initial run subcase results and the
restart run subcase results. The software automatically relabels any subcase IDs if a conflict occurs
between the initial run subcase IDs and the restart run subcase IDs.

If you are unsure of the resulting subcase IDs and the time steps in a restart .op2 file, you can load
the .op2 file into Simcenter 3D post processing. The Post Processing Navigator organizes the results
according to subcase ID and time step.

Special case: EXEFROM = RSTFROM

The purpose of this special case is to continue a non-converged subcase. Only the solution control
parameters on the NLCNTL bulk entry and the time step intervals on the TSTEP1 bulk entry can change
from the initial run to the restart run.

Specifically:

• The TSTEP1 entry defined for the first subcase in the restart input file must have the same end time as
the end time defined for the non-converging subcase in the initial run. The Ninc and Nout fields that
define the time step intervals and output are applied from the start time to Tend.

• Any new or modified solution control parameters defined on the NLCNTL entry in the restart input file
apply only from the start time to Tend.

• To keep compatibility with the initial run, the general solution parameters LVAR, TVAR, THRMST, and
LOADOFF that are related to loading cannot change.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 12-3
© 2023 Siemens
 12. Restart solution

Model check

By default, during the restart solution, a model check occurs that compares the model data in the restart
input file with the model data stored from the initial run .op2 file. A fatal error will occur if model
differences are found. There are exceptions where the model may need to be modified. For example, you
may need to add a spring element to help a failing solution complete. The parameter MDLVAL on the
NLCNTLG bulk entry is available to turn the model check off.

Restart parameter summary:

RSTGEN For the initial run, requests that restart data will be saved for
static, dynamic, and preload subcases. SOL 401 saves the restart
data in the output OP2 file. (Character; Default = NO).
YES = Restart data is saved.
NO = Restart data is not saved.

RSTUNIT=n For the restart run, defines the unit number of the external
restart file. The unit number must also be specified on an
ASSIGN statement that references the physical file name of
the .op2. (Integer≥161; Default=161)

RSTFROM =n For the restart run, defines the subcase ID from which to restart.
This subcase ID was defined in the initial run input file. RSTFROM
has no default and must be defined. (Integer>0; No default).

EXEFROM = n For the restart run, defines the subcase ID from which to
execute. This subcase ID is defined in the restart run input file.
EXEFROM has no default and must be defined. (Integer>0; No
default)

MDLVAL For the restart run, allows the option to turn off the model
validation check (Character; Default = “YES”).
YES = Request model validation.
NO = Do not request model validation.

Restarts with a CHEXA and CTETRA elements

An improved element architecture is available for SOL 401 with small strains that improves performance
for the following elements:

● The 3D solid elements CHEXA, CTETRA, CPENTA, and CPYRAM referencing a PSOLID property.
● The axisymmetric elements CTRAX3, CTRAX6, CQUADX4, CQUADX8.
● The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

12-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 Restart

When you run your analysis with large strains off (PARAM,LGSTRN,0), the improved approach is used by
default. You can switch to the pre-version 2020.2 architecture by defining SYSTEM(746)=0.

The software automatically uses the pre-2020.2 architecture if any of the following are present.

● Dynamic subcase.
● Collapsed CHEXA element used in the crack simulation.
● J-integral output for a crack simulation.
● User defined materials requested with the MUMAT bulk entry.
● Adaptive meshing output requested with the ADAPTERR case control command.
● Element addition and removal requested with the ELAR case control command.
● MAT3 material entry defined in the model.
● Generalized plane strain element defined in the model.

You can use the improved architecture with a restart, although you must use the same architecture in
both the initial run and in the restart runs. For example, if your initial run includes only static subcases,
but the restart run includes a dynamic subcase, you will need to define SYSTEM(746)=0 for both runs
because the improved architecture is not supported with a dynamic subcase.

Rotational loads in a restart run

The RFORCE and RFORCE1 bulk entries define rotational loads due to an angular velocity and
acceleration. You can define the location through which the rotation vector acts with a grid point, or by
default, using the origin of the coordinate system referenced in the CID field on the RFORCEi entries.

If you want to add or change a rotational load in a restart run, you cannot add a new grid point to define
the location of a new rotation vector. The software requires that the geometry information (grids and
elements) in the restart run must be consistent with the initial run. Although, you can use the POINT
entry with the RFORCE and RFORCE1 bulk entries in a SOL 401 restart solution. A POINT entry can be
added in the restart run even though it did not exist in the initial run.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 12-5
© 2023 Siemens
 12. Restart solution

12.2 SOL 402 Restart

Restarting solutions saves solving time by letting you reuse previously computed results. You can use the
previously computed results to start subcases within the same solution (internal restarts), or you can use
them to start new solutions (external restarts).

Internal restarts (SOL 402 only)

Internal restarts start a specified subcase with the computation state (displacements, velocities, stresses,
state variables, and so on) of a preload, static, or dynamic subcase during the same solve. For example,
you might want to start several non-sequentially dependent (NSD) subcases with the results of a bolt
preload subcase. Similarly, you can start other NSD subcases with the results of a dynamics subcase.

You can use the RSUB=n parameter of the NLCNTL2 bulk entry to make an internal restart.

Although these subcases restart with computation state of the subcase you specify, they do not restart
with the end time of the specified subcase. Time continues to increment for each subcase.

External restarts

External restarts start a new nonlinear solve with results from a previous solve. For example, you can
start a new solution using the computed pre-stress of your model. Or, you can start a new solution from
the last converged step within a static or dynamic subcase.

SOL 402 supports external restarts from the end of a subcase or from the last converged time step. It
does not support restarting from other time steps within a subcase. The restart point can be a static
subcase, dynamic subcase, or the end of preload subcase. Your restart solution can be a clone of your
initial run solution (preferred method), or it can be a new solution (in this case you do not refer to the
initial solution).

Saving the restart data at the initial run

If you plan to make a restart, you must first save the restart data during the initial run.

You do this with the RSTGEN=YES parameter of the NLCNTLG bulk entry. All the subcases of that run will
be potential subcases for a future restart.

For SOL 402, the data is saved in the output OP2 file, the Samcef .sdb and .adb database files, and the
Samcef output .u18 file.

The restart run

In the restart run:

• You must specify the subcase ID from which you restart. You do this with the RSTFROM parameter of
the NLCNTLG bulk entry.

12-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 Restart

See also the RSTFROM parameter.

• You must specify the subcase ID from which you execute. You do this with the EXEFROM parameter of
the NLCNTLG bulk entry.

See also the EXEFROM parameter.

• You must also specify the unit of that external restart file. You do this with the RSTUNIT parameter of
the NLCNTLG bulk entry.

The unit number must also be specified on an ASSIGN statement that references the physical file name
of the initial .op2 file.

Example

ASSIGN inputt2='OUTDIR:k402.op2' unit=170 status=unknown

....
NLCNTLG RSTUNIT 170 RSTFROM 1 EXEFROM
2

Note:
The referenced restart .op2 file must have been generated using a release in the same major
release family as the restart run is being executed in. This is due to the fact that .op2 schema may
change between major releases.

The subcase ID from which you restart (RSTFROM)

RSTFROM specifies the subcase ID from which you restart.

The restart solution uses the restart subcases that precede or equal the specified subcase.

• If you cloned the initial run solution to be your restart solution, the restart solution has the same
subcase ID numbers of the initial run solution. Therefore, the restart subcases in the initial run .op2
file replace the same numbered subcases in the restart solution starting with the subcase you select
here. For example, if three restart subcases are available and you select subcase 2, the solution starts
with the end state of subcase 2 and recomputes subcase 3.

• If you created a new restart solution, the restart solution starts from the end subcase you specify but
the new subcase will be numbered from 1 again. All restart subcases prior to the one you select are
included in the solution. For example, if the initial run .op2 file contains five subcases and you specify
subcase 3 as the subcase from which to restart the solution, subcases 1, 2, and 3 are included in the
restart solution, but subcases 4 and 5 are not.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 12-7
© 2023 Siemens
 12. Restart solution

The subcase ID from which you execute (EXEFROM)

EXEFROM specifies the subcase ID from which you execute.

For example, if the initial run .op2 file contains five subcases and you specify RSTFROM=3 and
EXEFROM=4 in the restart solution, your restart solution executes from the subcase 4 and uses the
restart data of the subcase 3 of the initial run.

Model validation for the restart run

SOL 402 does not allow you to add or remove elements, materials, boundary conditions, and so on
in the restart run model. At most, you can change solution parameters or the numerical values of the
boundary conditions. The MDLVAL parameter of the NLCNTLG bulk entry, therefore, does not apply to
SOL 402.

12-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 13. Considerations for nonlinear analysis
13.1 Discrete system for a nonlinear continuum model
Theories in solid mechanics are dictated by three governing relationships:

• The state equilibrium that

Equation 13-1.

requires where σij are stress tensor components, bi are body forces, and xj are space coordinates.

• The constitutive relations represented by stress-strain relations, e.g., for linear elasticity,

Equation 13-2.

where εkl are strain tensor components and Dijkl are elastic constants.

• The compatibility represented by strain-displacement relations, e.g., for a small deformation,

Equation 13-3.

where ui are displacements.

These systems of governing differential equations must be satisfied for every infinitesimal element
throughout the domain of the continuum. The complete set of state variables, namely displacements,
may be determined by solving these systems of equations supplemented by boundary conditions, and
in dynamic situations by initial conditions as well. For the nonlinear problems, the governing equations

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-1
© 2023 Siemens
 13. Considerations for nonlinear analysis

should be satisfied throughout the history of load application. The material nonlinearity is manifested in
the constitutive relations. The geometric nonlinearity is pronounced in the strain-displacement relations,
but it also affects the equilibrium equation by changing applied loads. Changes in constraints affect the
boundary conditions, which constitute contact problems.

Most of the known solutions for the solid mechanics problems are based on ideal geometry and linear
approximations. However, the real nature is more complicated and inherently nonlinear. The linear
system is a very particular case of a general problem. Even the nonlinear solutions that we seek
deal with only a small subset of special cases in a general category of nonlinear problems. When the
nonlinear system is confronted, no general mathematical solutions exist and superposition no longer
applies. The system may even be non-conservative.

The first phase of the structural analysis is the idealization of a physical system into a simpler and more
manageable engineering problem. The idealization process involves simplifications of the geometry,
boundary and joint conditions, and loading conditions, etc. using engineering intuitions, experimental
data, empirical observations, and classical solutions. If the idealized structural system renders a problem
that cannot be resorted to a classical method of analysis, further idealization is required, namely
discretization, for numerical analysis.

Finite elements represent spatial discretization of a continuum. As such, however, they do not
immediately impose nonlinearity. When nonlinearity has to be taken into account for large
displacements and/or stresses, a numerical model poses new dimensions to the discretization in
addition to the n-dimensional Euclidean space. That is, the discretization is applied to time, load, and
material properties by using piece wise linear curves. While discretization allows approximate solutions
by numerical methods, it introduces numerous mathematical singularities which may complicate
computational processes. Fortunately, the efficiency of modern digital computers makes it feasible to
apply complicated computational procedures to the complex systems of engineering problems.

For the discrete system, governing differential equations are converted to algebraic equations. The finite
element model represents a structure by an assemblage of finite elements interconnected at nodal
points. State variables are the displacements (displacement method or stiffness approach.) of the nodal
points which carry fictitious forces representing distributed stresses actually acting on the element
boundaries. The equilibrium requirements are satisfied at nodal points by the nodal force balance. The
material constitutive laws are satisfied at the integration points of the element. The compatibility is
ensured by the displacement continuity between elements. It is noted, however, that the compatibility
of the nonconforming elements is ensured by a patch test.

13-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Finite element formulation for equilibrium equations

13.2 Finite element formulation for equilibrium equations

The variational principle renders the system governing equilibrium equations when applied to a
functional ll, representing a total potential of a continuum, i.e.,

Equation 13-4.

where U is the strain energy of the system and W is the potential energy of the external loads. The
equilibrium equations can be obtained by invoking the principle of virtual work or the Ritz method, i.e.,

Equation 13-5.

which implies that the total potential of the system must be stationary with respect to the state variables
(displacement) for equilibrium to be ensured. The functional IT is so called because it involves the
integral of implicit functions of the state variables, {u}.

Considering a three-dimensional continuum for a nonlinear problem, the stationarity condition results in

Equation 13-6.

where the dots and δ denote infinitesimal increments and arbitrary variations, respectively. The left-
hand side represents variations in the strain energy increment and the right-hand side represents
variations in the external work which consists of body forces bi (such as a gravity load), traction forces
ti at the boundary surface (such as pressure loads), and concentrated forces pi. Now it remains to
determine admissible functions expressing the arguments of the functional II in terms of state variables
{u}, which are valid throughout the whole region and satisfy the boundary conditions.

The finite element method can be characterized by the following features distinguished from the
conventional Ritz methods or the matrix method for frame structures:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-3
© 2023 Siemens
 13. Considerations for nonlinear analysis

• The whole region of the system is divided into numerous subdomains, called finite elements, which
have simple geometrical shapes.

• The variational process is limited to each finite element, which aggregates into a whole region when
assembled.

• The admissible displacement field within each element, , can be expressed in terms of nodal
displacements using interpolation functions known as shape functions, N, i.e.,

Equation 13-7.

where {u} is a displacement vector consisting of all nodal points of the element.

The strain-displacement relations for the element can then be established in terms of nodal
displacements using the shape functions in Equation 13-7, i.e.,

Equation 13-8.

where

Equation 13-9.

and the element matrix [B] consists of derivatives of the shape functions, evaluated at the current
deformed geometry. Notice that the geometric linear problem requires that the element matrix be
evaluated only at the initial geometry. The software employs an approximate updated Lagrangian
approach for geometric nonlinear problems, by which linear strains are computed in the updated
element coordinate system in order to eliminate the effects of the rigid body rotation but the equilibrium
is established at the final position in the stationary coordinate system. This method does not require
reevaluation of the element matrix [B] (constant in the absence of large strains) while the element
coordinates are reevaluated continuously.

13-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Finite element formulation for equilibrium equations

Equilibrium equations for an element may be obtained by reducing Equation 13-6 after the substitution
of Equations 13-7 and 13-8, based on the small deformation theory. Then the element boundary
stresses are statically equivalent to the nodal forces which balance the applied external loads, i.e.,

Equation 13-10.

with

Equation 13-11.

and

Equation 13-12.

where [Ns] is an appropriate interpolation function for the traction force. Notice that the equilibrium
equation for an incremental load may be expressed as

Equation 13-13.

where should be components of co-rotational stress which is independent of a rigid body rotation.

The element stiffness matrix can be obtained by substituting the constitutive relations into Equation
13-13, i.e.,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-5
© 2023 Siemens
 13. Considerations for nonlinear analysis

Equation 13-14.

where

Equation 13-15.

and [D] is the material tangent matrix. The nodal forces of an element can then be expressed as

Equation 13-16.

where the element stiffness is

Equation 13-17.

Notice that this expression represents an element stiffness due to the material stiffness without
geometric nonlinear effects. As will be shown later, an additional stiffness [J(d)] due to initial stresses
should be included for an incremental process because the initial stresses exist from the second
increment.

The equilibrium must be satisfied in the whole region throughout the complete history of load
application. Equilibrium equations for the global discrete system are obtained when all the elements
are assembled, i.e.,

13-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Finite element formulation for equilibrium equations

Equation 13-18.

where Σ over m denotes a summation over all elements. For the incremental process, the equilibrium
equation may be rewritten as

Equation 13-19.

with

Equation 13-20.

where {σ0} represents an initial stress or the stress state at the preceding load step.

Because of the approximations involved in the interpolation functions, the finite element model provides
an approximate solution even if the equilibrium Equation 13-18 is satisfied exactly. Consequently, the
differential equations of equilibrium are not satisfied exactly even for linear problems, but the error
decreases as the finite element mesh is refined. This convergence condition is required and ensured by
element formulations with regard to the element convergence criteria.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-7
© 2023 Siemens
 13. Considerations for nonlinear analysis

13.3 Coordinate transformations

The coordinate transformation is one of the most frequent operations in the finite element method.
Vectors and matrices defined in a particular coordinate system can be transformed into another system.
Coordinate systems involved are:

• Basic coordinate system: a Cartesian coordinate system on which local coordinate systems are
defined.

• Local coordinate system: defined by the user in the Bulk Data, which may include special coordinates
such as cylindrical and spherical coordinate systems.

• Global coordinate system: a collective coordinate system which comprises all the local coordinate
systems specified for output quantities.

• Element coordinate system: a Cartesian coordinate system unique to each element.

• Displaced element coordinate system: similar to element coordinate system but defined in the
displaced position.

• Material coordinate system: a Cartesian coordinate system used to orient anisotropic material
properties.

• Modal coordinate system: a generalized coordinate system defined for each eigenmode.

It is noted that the global system is a Cartesian coordinate system, although non-Cartesian coordinate
systems are adopted to orient the local Cartesian coordinates for output quantities. In the software, all
the displacements and forces, hence the system matrices, such as the stiffness matrix, are expressed
in the global coordinates. This implies that all the major computations involved in the analysis are
processed in Cartesian coordinates. Element and material coordinate systems are defined in the element
connectivity description. Now we only have to consider linear transformations between Cartesian
coordinate systems.

Let us consider a coordinate transformation between the primed and unprimed systems which are
right-handed Cartesian coordinates. The transformation matrix T consists of direction cosines of unit
vectors of the unprimed coordinate system, i.e.,

Equation 13-21.

where

13-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Coordinate transformations

Equation 13-22.

Notice that T is an orthogonal matrix and thus

Equation 13-23.

Because the work and energy are invariants with respect to coordinate transformation, i.e.,

Equation 13-24.

it follows that

Equation 13-25.

Then the equilibrium equation,

Equation 13-26.

may be expressed in the unprimed coordinate system by

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-9
© 2023 Siemens
 13. Considerations for nonlinear analysis

Equation 13-27.

with

Equation 13-28.

It is noted that the modal matrix Φ is used as a transformation matrix for a modal transformation which
is not elaborated here.

Equation 13-29.

The forces and displacements are transformed from element to global coordinates and vice versa, i.e.

where Tbe transforms from element to basic coordinates and Tbg transforms from global to basic
coordinates.

It is noted that Tbe is identical for all the nodes of an element but Tbg may vary from node to node in the
same element. The element stiffness matrix is transformed into global coordinates by

Equation 13-30.

for which the building blocks of Tbe and Tbg are (3x3) matrices formed for each nodal point and have to
be assembled for an entire element, e.g., for a three-noded triangular shell element.

13-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Coordinate transformations

Equation 13-31.

where the superscript is used to associate each (3x3) matrix with the nodal point and is repeated for the
rotational degrees of freedom.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-11
© 2023 Siemens
 13. Considerations for nonlinear analysis

13.4 Displacement sets and reduction of system equations

The equilibrium equations, and thus system matrices, are reduced in size using the displacement set,
which is a unique feature of this software. Mutually exclusive subsets of the global displacement set,
{ug}, are defined as follows:

um Degrees-of-freedom eliminated by multipoint constraints

us Degrees-of-freedom eliminated by single-point constraints
uo Degrees-of-freedom omitted by static condensation
ur Degrees-of-freedom eliminated by a bulk data SUPORT to suppress rigid body motion
ui Degrees-of-freedom which remain for solution after reductions

For convenience, complementary sets are defined as follows:

un = ug - um

uf = un - us

ua = uf - uo

ul = ua - ur

The subsets are defined by the user with a possible exception in the s-set if PARAM,AUTOSPC,YES is used.
Notice that the rigid elements are equivalent to the multipoint constraints internally in the program, but
they are not selectable in the subcases as for MPCs. Because the set-reduction operations involve many
basic modules and DMAP blocks, the mathematics for elimination of constraints and static condensation
is reviewed here.

The multipoint constraint equations are formed in the module GP4 as follows:

Equation 13-32.

where

13-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Displacement sets and reduction of system equations

The module MCE1 partitions [Rmg] and solves for a transformation matrix [Gmn], i.e.,

Equation 13-33.

where

Then the module MCE2 partitions the global stiffness matrix, [Kgg], and reduce it to the n-set, i.e.,

Equation 13-34.

from which the system is reduced to

Equation 13-35.

where

and

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-13
© 2023 Siemens
 13. Considerations for nonlinear analysis

The primes are used in K’nn, P’n, and Q’n to distinguish from Knn, Pn, and Qn, which are resulting matrices
after the reduction.

Equations in the n-set can be further reduced by eliminating single-point constraints, i.e.,

Equation 13-36.

which is reduced to

Equation 13-37.

where

with

Notice that the effects of constraint forces (Qs and Qm) are not visible in Equation 13-37. The single-
point constraint forces are recovered by

Equation 13-38.

Further reduction of equations in the f-set is performed by an elimination of the o-set, known as static
condensation. The f-set is partitioned by the UPARTN module as follows:

13-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Displacement sets and reduction of system equations

Equation 13-39.

from which

Equation 13-40.

where

and

Then the reduced system of equations in the a-set is obtained as

Equation 13-41.

where

and

There are some rules to remember regarding the displacement sets in SOL 401. They are:

• The r-set is not supported. Do not use the SUPORT bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-15
© 2023 Siemens
 13. Considerations for nonlinear analysis

• PARAM, AUTOSPC is not supported.

• PARAM, AUTOSPCR is not supported.

• Rigid elements are formulated with linear multipoint constraint equations and do not have large
displacement capability. Consequently, erroneous results will be obtained if the rigid element
undergoes a large rotation. To avoid this, stiff elements should be used in place of rigid elements
for large displacement analysis.

13-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Nonlinear solution procedure

13.5 Nonlinear solution procedure

The general-purpose program developer faces the task of providing the best workable solution method
for a wide spectrum of problems, while maintaining flexibility by allowing the user to specify optional
parameters. Based on the extensive numerical experiments, an attempt was made to establish a general
strategy suitable for most problems without requiring insight or experience. Variations in combining
theories, algorithms, criteria and parameter values with numerous test problems resulted in a succinct
implementation.

The major feature of the nonlinear analysis is the requirement for the incremental and iterative
processes to obtain a solution. The main issue is how to choose the most efficient method from the
options available for the incremental and iterative processes in the solution of nonlinear equilibrium
equations. The increment size for time steps has the most significant effect on the efficiency and
the accuracy of the computation, particularly in the path-dependent problems. The incremental and
iterative processes are complementary to each other because the larger the increment size the more
iterations the solution requires. While an excessively small increment reduces the computing efficiency
without any significant improvement in accuracy, a large increment may deteriorate the efficiency as
well as the accuracy; it may even cause divergence.

It is impossible to optimize the incremental step size in the absence of prior knowledge of the structural
response. The best engineering judgment should be exercised to determine the increment size based
on the severity of the nonlinearity. Needless to say, no incremental load steps are required when the
response is linear. In principle, the size of the load increment (or time increment) should be chosen to
yield a uniform rate of change in strains or stresses for the material nonlinear problems and a uniform
rate of change in displacements for geometric nonlinear problems.

Specifying nonlinear analyses parameters in SOL 401

User specifications for solution methods in nonlinear analyses are allowed via:

• The NLCNTL bulk entry for the static analysis. It is selected by the NLCNTL case control command.

• The TSTEP and TSTEP1 bulk entries for the load increment (time-based). It is selected by the TSTEPNL
case control command.

The increment size can vary from subcase to subcase by specifying different TSTEPNL. It is
recommended that you define separate TSTEPNL for every subcase even if the same values are
specified, so that changes can be accommodated at the subcase level as needed.

• The EIGRL bulk entry for the modal analysis. It is selected by the METHOD case control command.

Specifying nonlinear analyses parameters in SOL 402

Solution control parameters

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 13-17
© 2023 Siemens
 13. Considerations for nonlinear analysis

You can define solution control parameters either globally (NLCNTLG bulk entry) or by subcase (NLCNTL2
bulk entry).

On the NLCNTLG bulk entry:

• You can select the solver type.

• You can select the stress-strain measure for all material laws,

• You can choose the type of initial and/or steady-state computation.

On the NLCNTL2 bulk entry:

• You can choose between fixed time steps or automatic time stepping. You can also control the time
step size (minimum, maximum, increase ratio).

• You can control the equilibrium iteration and convergence of the solution.

• You can define the time integration scheme (Newmark, HHT, or Generalized-alpha) for DYNAMICS
subcases. You can also control the integration error.

• For a non-sequentially dependent (NSD) static subcase (SEQDEP=NO), you can optionally reload the
computation state from the end of a previous subcase using the RSUB=n parameter.

For more information, see SOL 401 - Subcase sequencing.

13-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 14. Geometric nonlinearity
14.1 Overview and user interface
Geometric nonlinearities are manifested in problems involving large rotations and large deformation.
The characteristics are follower forces due to large rotations, geometric stiffening due to initial stress
effect (as a result of large rotations), and large strains due to large deformation.

Geometric nonlinear effects should be significant if the deformed shape of the structure appears
distinctive from the original geometry by a visual inspection. A more rigorous and quantitative definition
for the large displacements can be derived from the plate theory of Kirchhoff and Love: the small
deflection theory is valid for a maximum deflection of less than 20% of the plate thickness or 2% of the
small span length. However, this definition seems to be a little conservative for numerical analysis, and
there is no distinct limit for large displacements because geometric nonlinear effects are related to the
boundary conditions as well as the dimensions of the structure. If the load-deflection curve of the critical
point can be estimated, the loading point should be in the nonlinear portion of the curve.

Geometric nonlinear effects in the structure involving large rotations, whether rigid body rotations or
deformation induced rotations, are self-evident. Stiffening of a membrane, stiffness in a pendulum
or snap-through of an arch belong to this category. The motion of a pendulum under gravity is
caused by geometric (differential) stiffness. Follower forces are manifested when the applied loads are
displacement dependent, such as pressure load and thermal load applied on the surface that rotates.
Centrifugal force is another example of follower forces. Large strain effects are pronounced in metal
forming problems which could have strains exceeding 100%. Finite strain formulation is required to treat
the problems in this category. The software does not currently support the large strain capability. In
most structural applications, however, moderately large strains (20 to 30%) appear in local areas if there
is any large deformation. The software can be used for that category of problems. Other geometric
nonlinear effects are treated by updated element coordinates, rotation vector, and the differential
stiffness [Kd].

The geometric nonlinearity is controlled by the parameters LGDISP and LGSTRN for SOLs 401 and 402.

For more information, see Nonlinear Effects in SOL 401 and Nonlinear Effects in SOL 402.

This solver has a distinct approach to the large rotation, for which the element coordinates are
continuously updated to the current configuration during the iteration. The equilibrium is sought in
the deformed position. Consider the internal force computation as follows:

Equation 14-1.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-1
© 2023 Siemens
 14. Geometric nonlinearity

The element matrix is defined from the strain definition as

Equation 14-2.

in which could be divided into two parts (linear and nonlinear), i.e.,

Equation 14-3.

Upon differentiation of Equation 14-1, we have

Equation 14-4.

where {σ} represents stresses with reference to the original coordinates. Substituting Equation 14-3 and

Equation 14-5.

Equation 14-4 becomes

Equation 14-6.

14-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview and user interface

with

Equation 14-7.

and

Equation 14-8.

in which KL represents the usual linear stiffness matrix, KR a stiffness due to large rotation, and Kg a
geometric stiffness dependent on the initial stress level.

Now it remains to define the nonlinear part of the element matrix (BN). The definition of finite strains
based on the Lagrangian formulation (referred to the initial configuration) is as follows:

Equation 14-9.

Equation 14-10.

with other components obtained similarly. In matrix notation

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-3
© 2023 Siemens
 14. Geometric nonlinearity

where {εL} is the usual infinitesimal strain vector and {εN} is the nonlinear strain vector consisting of the
second order terms, i.e.,

Equation 14-11.

where

Equation 14-12.

and

Equation 14-13.

14-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview and user interface

Introducing shape functions (Ni) and nodal displacements {u} (using an example of a 10-noded
tetrahedron), displacement derivatives are expressed by

Equation 14-14.

and

Equation 14-15.

where

Equation 14-16.

and

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-5
© 2023 Siemens
 14. Geometric nonlinearity

Equation 14-17.

From the properties of matrices A and θ, it can be shown that

from which

Equation 14-18.

The initial stress stiffness [Kσ] can be derived as follows:

in which

where

14-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Overview and user interface

Equation 14-19.

with I being the (3x3) identity matrix. Finally the geometric stiffness is

Equation 14-20.

It has been found that stiffness matrices caused by geometric nonlinearity (KR and Kσ) can be computed
from the matrices [A], [G], and [M] with the following observations:

• [G] is dependent upon the initial geometry, hence stays constant unless the geometry is updated. This
matrix is used in forming [KR] and [Kσ].

• [A] is used in forming [KR]. [A] is dependent on the rotations and should be updated continuously.

• [M] is used in forming [Kσ]. [M] is dependent on the stresses and should be updated continuously.

The primary functions of nonlinear stiffness matrices can be interpreted as follows:

• The matrix [KR] takes into account the effects of large rotations. The large displacement effects, due to
rigid body translation and rotation, are treated effectively in the absence of large strains by updating
element coordinates in the software.

• Geometric stiffness matrix [Kσ] takes into account the effects of the initial stresses. This effect
becomes important with geometric stiffening, and is used for instability analysis. The geometric
stiffness matrix [Kσ] is equivalent to the differential stiffness [Kd] in the software.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-7
© 2023 Siemens
 14. Geometric nonlinearity

14.2 Updated element coordinates

When the large displacement effect is included in the nonlinear analysis, the solver employs a method
of displaced element coordinate system. This method allows large rotations by updating element
coordinates to the deformed geometry, and the equilibrium is computed in the deformed configuration.

14-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Concept of convective coordinates

14.2.1 Concept of convective coordinates

The concept is based on the fact that the rigid body motion does not contribute to the strain energy and
is eliminated from the internal force computation. Consider a rod which underwent rigid body motion as
well as deformation as shown below:

Figure 14-1. Net Deformation of a Rod

The net displacement ud is measured in the displaced element coordinate system by overlaying the
original element on top of the deformed element. The element force can simply be computed by

Equation 14-21.

where the superscript e denotes an elemental operation and the subscript d denotes the vectors in the
displaced element coordinate system. Then the element forces should be transformed into the common
coordinate system (namely global coordinate system denoted by a subscript g) before assembly for
global operations, i.e.,

Equation 14-22.

where the summation sign implies an assembly operation, and Tbd and Tbg are transformation matrices
from displaced to basic and from global to basic coordinate systems, respectively.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-9
© 2023 Siemens
 14. Geometric nonlinearity

14.2.2 Updated coordinates and net deformation

Referring to Figure 14-2, a quadrilateral element is shown in its original and deformed positions
(denoted by subscripts e and d, respectively) with reference to the basic coordinate system (denoted
by a subscript b).

Figure 14-2. Element Coordinates vs. Displaced Coordinates

The element coordinate system is established by bisecting the diagonals of the quadrilateral.
Transformation from the element coordinate system to basic coordinates is simply

Equation 14-23.

where the position vector (Xeb in Figure 14-2) of the element coordinate system with respect to the
basic coordinate system is denoted by < xe, ye, ze > Tbasic and transformation matrix [Tbe] is composed of

14-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Updated coordinates and net deformation

direction cosines of unit vectors of the element coordinate system with respect to the basic coordinate
system, i.e.,

Equation 14-24.

As the element deforms or displaces, the element coordinate system moves and this is defined as a
displaced coordinate system. The displaced coordinate system is established in the same manner as the
element coordinate system. Again the transformation should be performed similarly, i.e.,

Equation 14-25.

where < xd, yd, zd > Tbasic is the position vector of the displaced element coordinate system with respect
to the basic coordinate system (Xdb in Figure 14-2) and [Tbd] is formed similarly to [Tbe].

In order to isolate the deformation from the rigid body displacements, nodal displacements are
computed in the displaced element coordinate system by overlaying the original element as shown
in Figure 14-3.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-11
© 2023 Siemens
 14. Geometric nonlinearity

Figure 14-3. Computation of Net Deformation

The net displacements can be computed by subtracting the original nodal coordinates in the element
coordinate system from the displaced nodal coordinates in the displaced element coordinate system,
i.e.,

Equation 14-26.

in which the nodal coordinates in the element and displaced element coordinate systems can be
computed by the following transformations:

Equation 14-27.

14-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Updated coordinates and net deformation

and

Equation 14-28.

Substitution of Equations 14-27 and 14-28 into Equation 14-26 results in

Equation 14-29.

where {ug} is a total displacement (translational components only) in the global coordinates. In the
absence of the large displacement effect, the net displacement ud in Equation 14-29 is reduced to:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-13
© 2023 Siemens
 14. Geometric nonlinearity

14.2.3 Provisions for global operation

It is noted that the net rotations (θ x, θ y, and θ z of each node associated with the shell and beam
elements) are computed by a rotation vector approach before computing element forces. Subsequently,
the element forces have to be transformed to the global coordinate system before assembly for
equilibrium check. The internal forces are computed using net displacements and rotations, ud, i.e.,

Equation 14-30.

if the material is linear or

Equation 14-31.

if nonlinear material is involved. Consequently, the tangent stiffness matrix is formed in the global
system by assembling the element stiffness matrices transformed into the global coordinate system from
the displaced coordinate system, i.e.,

Equation 14-32.

The update process is performed at every iteration and the updated nodal displacements ud are used
whenever strains and stresses are computed. Effectively, the second order effect due to large rigid body
motion is eliminated. However, the displacement output shows the total displacements in the global
coordinates, i.e.,

Equation 14-33.

14-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Provisions for global operation

where the subscript i. denotes operations on each nodal point. The transformation matrix [Tbd] is
computed for each element after each iteration and stored in the ESTNL data block for stiffness matrix
update when required by the stiffness matrix update strategy. On the other hand, the transformation
[Tbg] is computed for each nodal point and it is not stored but recomputed whenever it is needed. The
nodal coordinates in the undeformed geometry, Xb, are available from the data block BGPDT.

This approach can be interpreted as approximate updated Lagrangian method, since the motion of the
body follows Lagrangian description. Stresses are computed in the deformed geometry just like Cauchy
stress. However, this method of displaced coordinate system is a unique and salient feature in the
software. The referential geometry in the updated Lagrangian method is brought up-to-date at every
incremental step upon convergence but fixed during the iterative process, which is inherently different
from the current method of updating the coordinate system.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-15
© 2023 Siemens
 14. Geometric nonlinearity

14.3 Follower forces

The term follower force usually refers to the applied loads that change direction and magnitude with
structural displacements and rotations, e.g.,

Equation 14-34.

where p is the magnitude of the pressure on the surface A, interpolated by a shape function N, and ñdA
changes as a function of u. They generally occur with fluid pressures such as the pressurized balloon,
inflated tire, or the lift load on the airplane wing. Other physical applications involve kinematics such as
the classical fire hose instability problem or inertia loads on spinning bodies. In the software, the term
applies to specific load inputs as defined below.

The FORCE1, FORCE2, MOMENT1, MOMENT2, PLOAD, PLOAD1, PLOAD2, PLOAD4, PLOADE1, PLOADFP,
PLOADX1, RFORCE, and RFORCE1 static forces and moments become follower forces in large
displacement analysis.

Note:
For SOL 401, when a follower force is referenced by the time unassigned LOAD bulk entry in a
large displacement analysis and it used in multiple subcases, for the first subcase, the follower
force is ramped or stepped normally according to the LVAR parameter setting on the NLCNTL bulk
entry. However, for the dependent subcases after the first subcase, the software does not correctly
apply the follower force computed in the previous subcase. Please reference follower forces with
the time assigned DLOAD bulk entry instead to avoid this situation.

Note:
For SOL 402, in areas with small displacements, the direction of the force is defined by the original
positions of G1 and G2 and does not change.

14-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Basic definition

14.3.1 Basic definition

For geometrical nonlinear analysis, static loads belong to one of two categories, namely:

• Loads defined by fixed vector inputs, which may be calculated once per run and cannot change
direction or magnitude.

• Loads defined by the location of one or more GRID points.

The first category includes simple forces, and enforced displacements. The second, follower force
category, includes the following Bulk Data inputs:

FORCE1, The direction changes with displacements of the referenced GRID points. The
FORCE2, magnitudes of these concentrated loads are constant.
MOMENT1,
and
MOMENT2
PLOAD, The pressure loads follow the surface of the solid elements (HEXA, PENTA, PYRAM and
PLOAD1, TETRA).
PLOAD2,
PLOAD4,
PLOADE1,
PLOADFP,
and
PLOADX1
RFORCE and Centrifugal loads change in magnitude and direction with motion of the masses
RFORCE1 attached to the GRID points. The effect may be destabilizing if large motions occur.
It is recommended that lumped masses be used with these loads.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-17
© 2023 Siemens
 14. Geometric nonlinearity

14.3.2 Implementation

The follower forces depend on the GRID displacements and therefore must be recalculated for each
nonlinear iteration and line search. The basic equation for residual error, as defined in Newton’s method
of iteration, becomes:

Equation 14-35.

where the applied load vector {Pal is now a variable. Corrective Loads are computed based on the
updated geometry and added to the initially applied loads to account for the follower forces, i.e.,

Equation 14-36.

where

Equation 14-37.

Note that thermal effects are included in the vector {F}.

Using the following equation presented in Newton’s method of iteration,

[KT] {Δui} = {Ri-1}

the tangent matrix can be calculated using derivatives of the loads, which is termed follower matrix.
However, the nonlinear solution process ignores the stiffness effects of the changing loads and use the
approximation:

14-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Implementation

Equation 14-38.

The effect of the approximation is minor in most cases. However, it could become a major concern in
thin shell models with pressure loads causing large rotations, where the converged solutions will be
correct but the rate of convergence may be slow or cause divergence. Also the buckling solutions or
modal analysis on preloaded structure with pressure load may not be correct due to the approximate
tangent matrix if the effect of the follower matrix is significant.

The follower force effects in the analysis can be controlled by the parameter LGDISP. Three options are
available in PARAM LGDISP:

• = 0 for no geometric nonlinearity

• = 1 for full geometric nonlinearity (including follower forces)

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 14-19
© 2023 Siemens
 14. Geometric nonlinearity

14-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 15. Solution methods
15.1 SOL 401 Singularities
SOL 401 considers two types of singularities:

1. Grid point singularities are identified by considering the stiffness terms of only one grid point.

After matrix assembly, the grid point singularities are detected. At each grid point, a 3X3 partition
of the stiffness matrix for each of the three translational and three rotational DOFs is solved as an
eigenvalue problem to determine the principal stiffnesses. Each stiffness term is compared to the
principal stiffness using the formula

where Kii is the term in the i-th row and i-th column of the matrix and Kmax is the principal stiffness.
If ε is less than 10–8, the global direction nearest i is considered singular. A fatal error will occur if a
grid point singularity is found.

2. Mechanism singularities are identified by considering the stiffness terms of more than one grid
point.

During decomposition, mechanisms can be detected based on the maximum ratio of the matrix
diagonal to the factor diagonal

where Kii is the i-th diagonal term of the original stiffness matrix and Dii is the i-th diagonal term of
the factor diagonal matrix. For a symmetric matrix K it can be represented as

where:

[L] = lower triangular factor

[D] = factor diagonal matrix

All terms whose ratio exceed the value of PARAM,MAXRATIO are printed. The default for
MAXRATIO is 107, and 1010 when contact conditions are present. UIM 4158 prints the statistics
for the decomposition that include the number of negative terms on the factor diagonal and
the maximum ratio of matrix diagonal to factor diagonal at a specified row number and its
corresponding grid point. User Warning Message (UWM) 4698 prints the degrees of freedom that
have a factor diagonal ratio greater than the MAXRATIO value or have negative terms on the factor
diagonal. Both of these messages are issued by the DECOMP module and are shown below:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-1
© 2023 Siemens
 15. Solution methods

*** USER INFORMATION MESSAGE 4158 (DFMSA)

---- STATISTICS FOR SPARSE DECOMPOSITION OF DATA BLOCK KBDD FOLLOW
NUMBER OF NEGATIVE TERMS ON FACTOR DIAGONAL = 1
MAXIMUM RATIO OF MATRIX DIAGONAL TO FACTOR DIAGONAL = 1.4E+14 AT ROW
NUMBER 2095
*** USER FATAL MESSAGE 23278 (NL2SPL2)
RUN TERMINATED DUE TO EXCESSIVE PIVOT RATIOS IN MATRIX KBDD.
USER ACTION: CONSTRAIN MECHANISMS WITH SPCI OR SUPORTI ENTRIES OR SPECIFY
PARAM,BAILOUT,-1 TO
CONTINUE THE RUN WITH MECHANISMS.

For SOL 401, if the MAXRATIO value is exceeded, your job terminates with DMAP Fatal Message
9050. You can override this fatal message by inserting “PARAM,BAILOUT,–1" in your input file.
You should, however, be aware that a large value of the MATRIX/FACTOR DIAGONAL may be an
indication of a potential modeling problem. Taking the log10 of MAXRATIO indicates how many
significant digits may have been lost during the decomposition.

There are exceptions when your model includes chocking or cohesive zone elements, or you have
requested element add/remove or nonlinear buckling (arc-length method). For these cases, the
software does not end with the fatal message 9050 if the MAXRATIO value is exceeded. Instead,
the following warning message is printed, and the solution continues.

*** USER WARNING MESSAGE 23278 (NL2SPL2)

EXCESSIVE PIVOT RATIOS DETECTED IN MATRIX KBDD.
SOLUTION WILL PROCEED AS MODEL CONTAINS CHOKING
ELEMENTS
USER ACTION: VERIFY THAT MECHANISMS DO NOT EXIST AND THE
SINGULARITY IS DUE TO PROBLEM PHYSICS.

Matrix stabilization

An additional option is available to allow a solution to proceed when an unconstrained condition exists.
For example, if you are relying on contact conditions to prevent a mechanism, but they may not be well
established at the start of a solution. This matrix stabilization option is available by setting the parameter
MSTAB to 1 on the NLCNTL bulk entry. The MSFAC parameter, also on the NLCNTL bulk entry, is available
to define a scale factor for matrix stabilization. Specifically, when you define MSTAB=1, the software
scales the diagonal terms by the factor (1+MSFAC).

Note:
Because the element iterative solver requested with SOLVER=ELEMITER on the NLCNTL entry does
not assemble a global stiffness matrix, there are no diagonal matrix terms to scale. As a result, the
software ignores the stiffness matrix stabilization request when the element iterative solve is used.

Some causes for singularities can include:

• Contact conditions are not established at the start of a solution.

• Degrees of freedom without stiffness because of missing elements.

15-2 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 Singularities

• A 2-dimensional plate problem with the normal rotation unconstrained.

• A solid model with rotational DOFs at the corners unconstrained.

• Incorrect modeling of offset beams.

• Incorrect multipoint constraints.

• Mechanisms and free bodies, such as sloped plates, beam to plate connections, beam to solid
connections, and plate-to-solid connections.

• Low stiffness in rotation.

• A stiff element adjacent to a very flexible element.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-3
© 2023 Siemens
 15. Solution methods

15.2 SOL 402 Singularities

SOL 402 uses the parameter MAXRATIO to determine if singularities exists:

where Kmax is the maximum stiffness term on the diagonal, and Kii is the term in the i-th row.

If any of the ratios exceed the value of PARAM,MAXRATIO, a message similar to the following will be
printed in the .f06 file, and the solution continues.

3.7.1. VERIFICATION OF THE STIFFNESS MATRIX

-------------------------------------------
DIAG. MAX. 1.0354297E+11
ELEMENT 21 TYPE CYLF COMP 24
DIAG. MIN. 1.2000000E+04
NODE 12 C 1
%%%A02 - MC331 , THE STIFFNESS IS BADLY CONDITIONNED DIAG. MAX. / DIAG. MIN. >
1.00000E+04

In the .f06 example above, PARAM,MAXRATIO,1.E4 was defined. The SOL 402 default for MAXRATIO is
108. SOL 402 ignores the parameter BAILOUT.

Some causes for singularities can include:

• Contact conditions are not established at the start of a solution.

• When contact is defined between faces, the software resolves the contact problem to the grid points
associated with the face region. If any of these grid points are involved in another contact pair, are
fixed with an SPC, or are involved in cyclic symmetry, the DOF associated with these grid points may
have redundant Lagrange multipliers.

• Degrees of freedom without stiffness because of missing elements.

• A 2-dimensional plate problem with the normal rotation unconstrained.

• A solid model with rotational DOFs at the corners unconstrained.

• Incorrect modeling of offset beams.

• Incorrect multipoint constraints.

• Mechanisms and free bodies, such as sloped plates, beam to plate connections, beam to solid
connections, and plate-to-solid connections.

• Low stiffness in rotation.

15-4 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 Singularities

• A stiff element adjacent to a very flexible element.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-5
© 2023 Siemens
 15. Solution methods

15.3 Solution Algorithm

Let n represent the current time step, i the current iteration, (n-1) will be the last converged time step. If
n=1, the previous converged time step will be the initial conditions.

U represents the displacement vector.

P represents the external force vector.

F represents the internal force vector.

R represents the residual (R= P-F) vector.

t represents time.

∆t represents time step size.

1. Assemble stiffness matrix for the structure if this is the first step, or if a stiffness update is requested
any time during the solution. Decompose the stiffness matrix.

2. Save last converged displacements (Un-1) and external forces (Pn-1)

3. tn=tn-1+∆t

4. Obtain the external force vector Pn1 for the first iteration of current time step.

a. If i>1: Include follower force effects to obtain Pn1.

5. Compute internal forces Fn1(Uni–1)

6. Compute residual: R = Pni - Fni

7. If i>1:

a. Compute: E2=∆Uni-1. R

b. Compute Er=E2/E1

c. If Er>1 or Er<-100, ndiv=ndiv+1

d. Write quasi Newton vectors for BFGS.

8. Compute displacement increment: ∆Uni=K-1 R

9. Compute E1=∆Uni.R

15-6 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Solution Algorithm

10. Compute Uni=Uni-1+ ∆Uni

11. Compute current stiffness parameter

12. Check for convergence.

a. If solution has converged and stiffness update is needed, go to 1.

b. If solution has converged and stiffness update isn’t necessary, go to 2.

c. If solution hasn’t converged and stiffness update is needed, go to 1 (skip 3).

d. If solution hasn’t converged and stiffness update isn’t needed, go to 4.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-7
© 2023 Siemens
 15. Solution methods

15.4 Adaptive Solution Strategies

Nonlinear finite element computations comprise material processes, element force computations, and
various global solution strategies. The computational procedure involves incremental and iterative
processes ranging from local subincrements to global solution processes. Performance of the finite
element program can be scrutinized from three different perspectives: computational efficiency, solution
accuracy, and effectiveness. All of these attributes of the nonlinear program can be improved by
adaptive algorithms.

15-8 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Newton’s method of iteration

15.5 Newton’s method of iteration

The equilibrium equations in the g-set may be written as

{Pg} + {Qg} - {Fg} = {0} where {Pg}, {Qg}, and {Fg} represent vectors of applied loads, constraint forces,
and element nodal forces, respectively. Element nodal forces are nonlinear functions of displacements
for nonlinear elements. Since the equilibrium condition is not immediately attained in the presence of
nonlinear elements, an iterative scheme such as the Newton-Raphson method is required. Since the
error vanishes at constrained points and the constraint forces vanish at free points, the unbalanced
forces acting at nodal points at any iteration step are conveniently defined as an error vector by

{Ra} = {Pa} - {Fa}.

Equation 15-1.

Notice that the a-set is equivalent to the I-set in the nonlinear analysis because the r-set does not exist.
The subscript a will be dropped for simplicity in the following discussion.

Based on Newton's method, a linearized system of equations is solved for incremental displacements by
Gaussian elimination in succession. The Jacobian of the error vector emerges as the tangential stiffness
matrix. The equation to solve at the i-th iteration is

[KT] {Δui} = {Ri-1}

Equation 15-2.

where

and

{Δui} = {ui} – {ui-1},

{Ri} = {P} – {F(ui)}.

The iteration continues until the residual error {R} and the incremental displacements {Δu} become
negligible, which is signified by the convergence criteria.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-9
© 2023 Siemens
 15. Solution methods

The tangential stiffness consists of the geometric stiffness in addition to the material stiffness, i.e.,
without regard to the coordinate transformation,

Equation 15-3.

where [Km] and [Kd] refer to the material and the differential stiffness, respectively. The material stiffness
is given in Equation 4-17 with a material tangential matrix for [D]. The differential stiffness, which is
caused by the initial stress, is defined as follows:

Equation 15-4.

where [BN] represents the second order effects in the strain-displacement relations, [G] consists of
derivatives of shape functions and [M] is a function of stresses. Notice that the initial displacement
stiffness is not included in [KT] because its effects are already eliminated in the element formulation.

Newton's procedure was previously implemented using a corrective force. Recalling that the element
forces for linear elements are expressed as

{F} = [K] {u},

a corrective force vector may be defined as

{C} = {F} – [K] {u}

Equation 15-5.

The iteration starts with initial values

{u0} = last converged displacement;

{R0} = P – F(u0) = {ΔP} + {Re};

15-10 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Newton’s method of iteration

where {ΔP} is an incremental load vector and {Re} is a residual load error carried over from the last
converged solution. Then the successive error vectors can be evaluated by

Ri+1 = Ri – K(ui+1 – ui) – (Ci+1 – Ci).

Equation 15-6.

It is noted that the corrective force vector vanishes for linear elements. The corrective force calculation
has been removed, and the error vector is computed directly from the internal forces, i.e.,

{Ri+1} = {P} – {Fi}

Equation 15-7.

Then the residual load error is automatically carried over to the next incremental process.

The merit of the Newton-Raphson method is the quadratic rate of convergence, i.e.,

||u* – ui+1|| ≤ q||u* – ui||2

Equation 15-8.

where u* is a true value of {u}, q is a constant, and 1111 represents a vector norm. From a practical
standpoint, however, determination of the tangential stiffness and its inverse at each iteration entails a
considerable amount of computation. As Figure 15-1 suggests, one may resort to the modified Newton's
method which requires the tangential stiffness to be evaluated just once at the initial position, {uo}, and
used thereafter to solve for {Δui}. However, more iterations are required for a given accuracy by the
modified Newton's method. The Gaussian elimination method is better suited for this approach than the
iterative descent method because the decomposition is performed only once.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-11
© 2023 Siemens
 15. Solution methods

Figure 15-1. Newton’s Methods for Iteration

15-12 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Newton-Raphson iteration strategy

15.6 SOL 401 - Newton-Raphson iteration strategy

For SOL 401, beginning with Simcenter Nastran 2312, a new Newton-Raphson iteration strategy is
used by default. We have found that the new strategy converges with fewer iterations than the legacy
strategy, especially when nonlinear materials are defined. You can revert to the legacy Newton-Raphson
strategy by defining SYSTEM(779)=0.

The table below compares the methods. The most significant difference is:

• For the legacy method, the residual computed in Step 1 uses the final displacements from the
previous iteration. As a result, the displacements used for the residual computation and the
displacements used for the convergence check are inconsistent. Once the displacements have
converged, it may take another iteration for the residual to catch up and converge.

In addition, for some models, there can be localized element and material issues that result in
problems with the displacements computed for the iteration. When this occurs, the legacy method
continues to compute the updated stiffness using the problematic displacements. As a result, the
computed stiffness matrix can be ill-conditioned causing the solution to fail.

• The new method includes Step 3, which computes a new residual vector using the displacements
computed for the iteration. As a result, the displacements used for the residual computation and the
displacements used for the convergence check are consistent. The displacement and residual are likely
to converge in the same iteration.

The localized element and material issues described above with the legacy method can also occur
with the new method. The difference is that the new method can determine that there is an issue
when it computes the internal forces in Step 3. When an issue is detected, it bisects the time step and
avoids the computation of an ill-conditioned stiffness matrix.

For both methods, the time steps are incremented by tn= tn-1+Δt, and the Newton-Raphson iterations are
incremented by i=i+1.

Legacy Method with SYSTEM(779)=0 New Method with SYSTEM(779)=1 (default)

1. The legacy method first uses the final 1. For the first iteration of a time step, the new
displacement from the previous iteration (or method calculates an initial residual vector
previous time step for the first iteration) using the final displacements from the previous
to compute (a) the residual for the time step.
current iteration , (b) the new displacement
increment, and (c) the new displacements.
a.

2. The new method uses the residual vector

b.
from the previous iteration (or from step
c.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-13
© 2023 Siemens
 15. Solution methods

Legacy Method with SYSTEM(779)=0 New Method with SYSTEM(779)=1 (default)

1 for the first iteration) to compute (a) the
new displacement increment, and (b) the new
displacements.

a.

b.
3. The new method calculates a new residual
vector from the updated displacement.

2. Convergence is checked based on the current 4. Convergence is checked based on the current
iteration residual vector and displacements. iteration residual vector and displacements.

Because the residual vector calculation was With the addition of Step 3, the displacements
computed using the displacements from the used for the residual vector computation and for
previous iteration, the displacements used the convergence check are consistent.
for the residual vector calculation and the
displacements used for the convergence check
are inconsistent.
3. If needed, the stiffness is updated using the 5. If needed, the stiffness is updated using the
new displacements. new displacements.

If convergence is met, the software goes to the If convergence is met, the software goes to the
next time step (n=n+1), and i is reset to 1. next time step (n=n+1), and i is reset to 1.
If convergence fails, the software iterates again If convergence fails, the software iterates again
(i=i+1) repeating steps 1 through 3. (i=i+1) repeating steps 2 through 5.

15-14 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Stiffness update improvement with large strain (SOL 401)

15.7 Stiffness update improvement with large strain (SOL 401)

For solutions that include large strain, you can select a stiffness update improvement which avoids
some repetitive calculations. The most significant performance improvement is with models that require
multiple iterations for time steps to converge, such as models that include nonlinear materials.

The performance improvement is available only when all of the conditions below exist:

• The stiffness update computation must be requested with the system cell setting SYSTEM(801)=1.

• Large strain must be requested with the setting PARAM,LGSTRN,1.

• The default Newton-Raphson architecture must be used (SYSTEM(779)=1).

• Stiffness updates at each iteration should be requested by setting KUPDATE=1 on the NLCNTL bulk
entry.

Note that when KUPDATE=0 and contact is defined, the software internally sets KUPDATE=1 when a
contact set is selected and INTRFC=1 or 2 is used on the BCTPARM bulk entry, or INTRFC=3 or 4 and
GUPDATE>0. This occurs by default because KUPDATE=0 and INTRFC=1 are the default values.

• The model can include any of the following elements (no other element types are permitted):

• 3D solid elements CHEXA, CTETRA, CPENTA, and CPYRAM

• Axisymmetric elements CTRAX3, CTRAX4, CQUADX6, and CQUADX8

• Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, and CPLSTS8

• Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, and CPLSTN8

• Mass elements CMASSi and CONMi (Except when a time-assigned temperature set is defined with
the DTEMP=n case control command. In this case, SYSTEM(801) is internally disabled.)

The software writes the following warning message to the .f06 file when the improved stiffness update
computation is requested with the system cell setting SYSTEM(801)=1, but not all of the conditions are
satisfied:

USER WARNING MESSAGE 23320 (NL2INT2) SYS801 TURNED ON, BUT PERFORMENCE
IMPROVEMENT FOR KUPDATE = 1 DOES NOT APPLY FOR THE CURRENT SUBCASE.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-15
© 2023 Siemens
 15. Solution methods

15.8 Stiffness update strategies

Among other features of the solution algorithm, the stiffness matrix update has probably the most
profound effect on the success of the nonlinear solution. In spite of its significance, however, it is very
difficult to implement a robust algorithm for update strategy due to the lack of a prior information
regarding the right timing for an update. In this section, stiffness update strategies are reviewed with
respect to the static analysis. Variations of the modified Newton’s method are adopted in the software.

However, the modified Newton’s method could lead to divergence when the stiffness changes
drastically, as demonstrated in the figure Newton’s Methods for Iteration, unless the tangential
stiffness is reevaluated at the critical point. To this end, an adaptive matrix update method is
unavoidable. Stiffness update strategies are established to update the stiffness matrix on an as needed
bases such as probable divergence.

15-16 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Update principles

15.8.1 Update principles

Newton’s method could be trapped in an infinite loop, oscillating about the local maximum as illustrated
in the figure Newton’s Methods for Iteration (a). This difficulty is overcome during the Newton’s
iteration by discarding the differential stiffness, [Kd], when the tangential stiffness is not positive definite
as shown in (b) of that figure.

Control over the stiffness update method is achieved with the KUPDATE parameter on the NLCNTL (SOL
401) and NLCNTL2 (SOL 402) entries. See the NLCNTL and NLCNTL2 entry in the Quick Reference Guide
for all KUPDATE options.

For SOL 401, current stiffness parameter approach for the automatic stiffness update method
(KUPDATE=0)

The current stiffness parameter approach proposed by Bergan and Crisfield [*] is used for automatic
stiffness update method. The current stiffness parameter gives a scalar measure for the stiffness of the
structure at the current loading condition.

Where, n is the time step index,

I is the teration index,

∆Pni = Pni-Pn-1i is the incremental applied load between time step n-1 and n,

∆P11 = P11 - P01 is the initial applied load (for the first iteration of the first time step),

P11 is the applied load in the first iteration of the first time step of the first subcase,

∆Uni = Uni - Un-1i is the incremental displacement between time step n-1 and n,

∆U11 = U11U01 is the initial displacement increment (after the first iteration of first step).

After the first iteration of the first step, S11=1, that is, the initial value of the current stiffness parameter is
one. After each iteration, the value of current stiffness parameter is recomputed. The change in current
stiffness parameter is computed for each iteration as:

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-17
© 2023 Siemens
 15. Solution methods

Where, Sref is the reference value for current stiffness parameter. At the start of the solution, Sref is set
to 1.0. Stiffness is updated if ∆S≥α, where α=5.0 for a problem with structural loading only, α=20.0 for a
problem with pure thermal load, and α=10.0 for a problem with a combination of structural and thermal
load. The value for α can be defined by the user on the NLCNTL card through parameter CSTFPAR. Valid
input for CSTFPAR is a real number.

Sref is updated upon updating stiffness to correspond to the value of Sni.

1. Bergan. P, Horrigmoe. G, Krakeland . B, and Soreide T., SOLUTION TECHNIQUES FOR NON-LINEAR
FINITE ELEMENT PROBLEMS, International Journal for Numerical Methods in Engineering, Vol. 12,
1677-1696 (1978)

2. Crisfield M. A. , Non-linear Finite Element Analysis of Solids and Structures, Volume 1: Essentials,
John Wiley & Sons, Chichester, 1991

15-18 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Divergence criteria

15.8.2 Divergence criteria

The MAXDIV parameter in the NLCNTL entry requires an integer to specify a limit on the probable
divergence conditions allowed for each time step to continue. In each iteration of a time step, the
following three quantities are computed:

Equation 15-9.

Equation 15-10.

Equation 15-11.

where,

Rni-1=Pni-1-Fni-1 (Uni-2) is the residual for iteration i-1 for time step n,

ΔUni=K-1 Rni-1 is the displacement increment computed in iteration i-1 for time step n,

Rni=Pni-Fni (Uni-1) is the residual for iteration i for time step n,

εpi is the computed error for the force norm for iteration i for time step n,

εpi-1 is the computed error for the force norm for iteration i-1 for time step n,

εwi is the computed error for the energy norm for iteration i for time step n,

εwi-1 is the computed error for the energy norm for iteration i-1 for time step n.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-19
© 2023 Siemens
 15. Solution methods

For the first iteration of every new time step, the value for λpi and λwi is set to 0.9999. The variable NDIV
is initiated to 0 in the first iteration of each time step. NDIV is incremented if:

1. If Er>1 or Er<-100, NDIV=NDIV+1

2. If λwi>1.00 and λpi>1.00, NDIV=NDIV+1

NDIV is reset to 0 if neither of the two conditions above are met in any given iteration. The solution is
considered to have diverged if NDIV>MAXDIV. MAXDIV is a NLCNTL parameter which controls maximum
allowable divergences in a time step (Default=3).

Upon divergence, the software will:

1. Revert the solution to the last converged point.

2. Reform stiffness at the last converged configuration (unless KUPDATE=-1, in that case no stiffness
update is performed).

3. Perform bisection, and attempt to solve the time step with a reduced size from the last converged
point.

For a timestep of size Δt, on bisection the time step is reduced to:

Δt1=1/2 Δt

Bisection continues until the solution converges, that is,

Δtk = 1/2 Δtk-1 = 1/2k Δt

where k is a bisection count. Once the bisection is successful (rendering a converged solution), the
integration proceeds to the next time step. If k = 1, the same time step size is used for the next
time step.

If k > 1, an effort is made to accelerate the solution process by increasing the time step size for the
next step. The time step size for the next time step is influenced by all of the following factors:

a. The number of iterations (i) that were required to reach convergence with time step size of
Δtk.

b. Number of bisections (k) performed.

c. Remaining time left (δt) to complete the original time step of size Δt.

The time step size used for the next time step is m Δtk, where 1 ≤ m ≤ k – 1. The largest value
of m that satisfied the following conditions is used:

15-20 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Divergence criteria

A. I ≤ 3 or I ≤ MAXITR/2m, where MAXITR is the maximum permissible iterations for a given

timestep.

B. δt/m Δtk is an integer greater than 0.

Although the goal of increasing time step size is to reduce the number of time steps till
completion of solution, for some problems, further bisection may be required in subsequent
steps.

The maximum number of bisections is limited by the parameter MAXBIS (default=5). The
bisection process is activated on an as-needed basis. You also have an option to suppress
bisection by specifying MAXBIS=0.

d. If the solution fails to converge even after attempting maximum permissible bisections, the
solution is terminated with a fatal message. Results corresponding to the last converged user
requested output time are printed.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-21
© 2023 Siemens
 15. Solution methods

15.9 Convergence criteria

The convergence test is an important factor that affects accuracy and overall efficiency in nonlinear finite
element analysis. Out-of-balance forces and changes in displacements should vanish upon convergence
in an iterative process. The energy error accommodates both quantities and is usually adequate for most
problems. However, the displacements could be in gross error while the residual load error is negligible,
or vice versa.

In order to ensure accurate and consistent convergence, multiple criteria with errors measured in terms
of displacements, loads, and energy should be combined. It is the error function and the convergence
tolerance that characterize the criteria. Error functions are formulated using the weighted normalization
so that the error measures are dimensionless. Tolerances should be realistic for the solution scheme to
be efficient. In this context, variations are considered in search of the best workable combinations of
error functions and tolerances for a wide class of structural problems.

15-22 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 Rudimentary considerations

15.9.1 Rudimentary considerations

The convergence test is a decision-making process, on which termination of the iterative process is
based, while the true solution is not known. The convergence criteria are extremely important for
the incremental/iterative solution strategy to be effective and efficient, because improper criteria could
cause inefficiency as well as inaccuracy. It is rather astounding to:find a scarcity of publications on this
subject, considering the significant impact of the convergence criteria on the accuracy and the efficiency
of the computation. Two distinct aspects are involved in the convergence criteria:

• Error functions to be minimized by the iteration.

• Tolerances of error functions within which errors are acceptable.

Both aspects must be defined properly for the criteria to be effective, for the solution scheme to be
efficient, and for the solution to be accurate.

There are no universally accepted convergence criteria to date in the field of finite element analysis.
Conditions to be met by ideal convergence criteria for a general-purpose finite element analysis have
been contemplated. The convergence criteria should:

• be satisfied for linear cases at all times.

• be independent of structural units.

• be reliable (cancellation of errors are not acceptable).

• render consistent accuracy.

• be independent of structural characteristics (stiffening or softening).

• be able to handle all the loading cases including constant loading, unloading, and no external loading
(applicable to creep analysis).

• have smooth transitions after the stiffness updates and loading changes.

These conditions dictate the formulation of error functions to be discussed.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-23
© 2023 Siemens
 15. Solution methods

15.9.2 Convergence conditions

The iteration continues until the convergence is attained by satisfying the convergence criteria and
the residual error vector at convergence is carried over to the next incremental step. When the
convergence criteria are satisfied, the out-of-balance forces and the changes in displacements should be
sufficiently small so that the remaining error is not physically significant nor will it cause any detrimental
effects, numerically or physically, on the succeeding incremental steps. Convergence tolerances have the
following effects:

• excessively tight tolerances cause a waste of computing resources for unnecessary accuracy.

• excessively loose tolerances cause not only inaccuracy but convergence difficulties in the subsequent
steps due to cumulative errors.

The fundamental difficulty of the convergence tests for a structural analysis lies in the fact that the
base vectors (forces and displacements) involve inconsistent units, namely, combinations of forces and
moments or translations and rotations. Indiscriminate use of these vectors will cause unit-dependent
convergence criteria. For example, while an error in forces is dominant when the model is expressed
in newton-meter, the error would be dominated by moments if the same model is described in newton-
millimeter.

The most natural and reasonable criterion for the convergence test is formulated in terms of an energy
error. The energy error is the logical choice because both the out-of-balance forces {R} and the change in
displacements {Δu} should be minimized by the iteration process. Furthermore, energy quantities do not
pose problems of inconsistent units due to mixed units associated with translations and rotations.

Although the convergence test in terms of energy errors is usually adequate, some distinct errors are
not detected with this criterion; i.e., displacements are in gross error while the residual load error is
negligible, or vice versa. This would be the case if the degrees-of-freedom in error have a very small
or a very large stiffness. Such cases compel the need for criteria in terms of loads and displacements.
Nominally, by visualizing the load-deflection curve for a one-dimensional case, it can be noticed that
the convergence criterion in terms of loads governs the stiffening structure and the criterion in terms of
displacements governs the softening structure. Scalar error functions for these criteria are formulated to
be dimensionless by introducing the weighted normalization.

15-24 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Error functions and weighted normalization

15.9.3 SOL 401 - Error functions and weighted normalization

A nonlinear solution iterates until the software computed convergence error functions are less than the
convergence criteria you have defined for each function. A convergence error function is calculated with
a ratio which compares the value of displacement, force, or work for the current increment to the total
value of displacement, force, or work.

You can define any combination of U, P, and W with the CONV parameter on the NLCNTL bulk entry
to request which of displacement (U), force (P), and work (W) the software will consider for the
convergence criteria.

The tolerances (EPSU, EPSP, and EPSW) define the convergence criteria. All the requested criteria
(combination of U, P, and/or W) are satisfied upon convergence.

If you do not define force (P) on the CONV parameter, a solution is converged when both of the
following are satisfied (1 and 2):

1. All of the checks requested with CONV (either displacement, work, or both) if you define CONV, or the
work check if you do not define CONV (default behavior).

2. Either of the following is satisfied (a or b):

a. The L2 norm of the residual for the current iteration is less than the L2 norm of the residual from the
first iteration for the time step. This is represented with RMAG in the .f06 output.

b. The error in force is less than EPSP.

If you define force (P) on the CONV parameter (either CONV=P, UP, PW or UPW), a solution is converged
when all the checks requested with CONV (displacement, load, work) are satisfied, and RMAG is no
longer checked.

See SOL 401 - Iteration related output data.

You can use the NORMP and NORMU parameters on the NLCNTL bulk entry to select the type of force
and displacement vector norm, respectively. The vector norms are used to compute the displacement
and force convergence error function. The norm computation results in a strictly positive value from a
vector space νn such that:

• The displacement convergence error function with the norm criteria is as follows.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-25
© 2023 Siemens
 15. Solution methods

where,

Uni is the displacement vector for iteration i of time step n,

Uni-1 is the displacement vector for iteration i-1 of time step n, and

Un-1 is the displacement vector at convergence for time step n-1.

Optionally, when the REFU parameter is defined, the form of the displacement error function is as
follows.

• The force convergence error function with the norm criteria is as follows.

where,

Pni is the external force vector for iteration i of time step n,

Fni is the internal force vector for iteration i of time step n,

Rni is the residual force vector for iteration i of time step n, and

Rn1 is the residual force vector for iteration 1 of time step n.

Optionally, when the REFP parameter is defined, the form of the force error function is as follows.

• EPSW (work criterion)

15-26 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 401 - Error functions and weighted normalization

Equation 15-12.

Where,

ΔUni is the incremental displacement vector computed for iteration i of time step n,

Rni is the residual force vector for iteration i of time step n,

Uni is the total displacement vector for iteration i of time step n,

Pni is the external force vector for iteration i of time step n,

Fni is the internal force vector for iteration i of time step n,

Rn1 is the residual force vector for iteration 1 of time step n, and

Un1 is the total displacement vector for iteration 1 of time step n.

Default tolerances for these error criteria are:

EPSU (Displacement): 1.0E-2

EPSP (Force): 1.0E-2

EPSW (Work): 1.0E-6

You can specify custom convergence tolerances on the NLCNTL bulk entry. The solution is considered to
have converged if the computed error criteria are less than the tolerance specified.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-27
© 2023 Siemens
 15. Solution methods

15.9.4 SOL 402 - Error functions and weighted normalization

A nonlinear solution iterates until the software computed convergence error functions are less than the
convergence criteria you have defined for each function. A convergence error function is calculated with
a ratio which compares the value of displacements, forces (or contact forces), or work for the current
increment to the total value of displacements, forces, or work.

Although all criteria theoretically need to be satisfied, force is practically used as the principal
convergence criterion. These criteria are computed as follows.

In general, the norm computation results in a strictly positive value from a vector space xn such that:

The displacement convergence error function with the norm criterion is as follows.

where,

is the incremental displacement vector computed for iteration i of time step n,

is the displacement vector for iteration i of time step n,

is the displacement vector for iteration i-1 of time step n.

Optionally, when the REFU parameter is defined, the form of the displacement error function is as
follows.

The force convergence error function with the norm criterion is as follows.

where,

is the external force vector for iteration i of time step n,

is the internal force (including the inertial force if it exists) vector for iteration i of time step n,

15-28 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Error functions and weighted normalization

is the residual force vector for iteration i of time step n.

Optionally, when the REFP parameter is defined, the form of the force error function is as follows.

The energy convergence error function is as follows.

is the incremental displacement vector computed for iteration i of time step n,

is the residual force vector for iteration i of time step n,

is the work by the external force for iteration i of time step n,

is the work by the internal force (including the inertial force if it exists) for iteration i of time step
n.

Note that the work at the time step n also relates to the work at the precedent time step n-1, that is.:

where,

is the work by the external force at convergence for time step n-1,

is the work by the internal force (including the inertial force if it exists) at convergence for time
step n-1,

is the displacement vector at convergence for time step n-1,

is the external force vector at convergence for time step n-1,

is the internal force (including the inertial force if it exists) vector at convergence for time step
n-1,

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-29
© 2023 Siemens
 15. Solution methods

is the displacement vector for iteration i of time step n,

is the external force vector for iteration i of time step n,

is the internal force (including the inertial force if it exists) vector for iteration i of time step n.

Optionally, when the REFE parameter is defined, the form of the force error function is as follows.

The contact force convergence error function with the norm criteria is as follows.

is the incremental contact force vector computed for iteration i of time step n,

is the contact force vector for iteration i of time step n,

is the contact force vector for iteration i-1 of time step n.

Optionally, when the REFP parameter is defined, the form of the contact force error function is as
follows.

Default tolerances for these error criteria are:

PRCQ (Displacement): 1.0E-1

PRCR (Force): 1.0E-3

PRCE (Work): 1.0E-3

PRCF (Contact Force): 1.0E-1

You can specify custom convergence tolerances on the NLCNTL2 bulk entry. The solution is considered
to have converged if the computed error criteria are less than the tolerance specified.

SOL 402 - Relaxed force and energy convergence

15-30 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens
 SOL 402 - Error functions and weighted normalization

The parameters PRDR and PRDE are available on the NLCNTL2 bulk entry for you to define a relaxed force
and energy tolerance, respectively.

When you define these relaxed tolerances, the software will first try to converge using the default
tolerance values defined with the parameters PRCR (force) and PRCE (energy). If convergence is difficult
and the software iterates more than the maximum number of iterations, it then considers the relaxed
criteria (PRDR and PRDE).

PRDR Relaxed relative force tolerance. (Real > 0.0; Default = PRCR;
Unitless).
The software will first try to converge using the default tolerance
value defined with the parameter PRCR. If convergence is difficult and
the software iterates more than the maximum number of iterations,
it then considers the relaxed criteria (PRDR).
To enable the relaxed force tolerance, you must define PRDR>PRCR.
PRDE Relaxed relative energy tolerance. (Real > 0.0; Default = PRCE ;
Unitless).
The software will first try to converge using the default tolerance
value defined with the parameter PRCE. If convergence is difficult and
the software iterates more than the maximum number of iterations,
it then considers the relaxed criteria (PRDE).
To enable the relaxed energy tolerance, you must define PRDE>PRCE.

SOL 402 - Optional force convergence computation

An optional force convergence error computation is also available by setting the system cell setting
SYSTEM(776)=1. The optional computation changes how the contact forces are included when the
software computes the total force value at each increment.

The optional computation can aid in convergence for models that include contact conditions. Sensitive
contact problems that did not converge may now converge. You will likely see the number of iterations
and number of rejected or accepted time steps change. In some cases, the converged solution can be
more accurate with the new computation using the same force tolerance value. You can adjust the force
tolerance using the PRCR parameter on the NLCNTL2 bulk entry.

Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series 15-31
© 2023 Siemens
 15. Solution methods

15.9.5 Implementation

The convergence tolerance determines the efficiency of the solution scheme as well as the accuracy of
the solution. The tolerance should be realistic, not too tight nor too loose. It is difficult to choose optimal
default values for the convergence tolerances. However, efforts have been made to set the default
values to provide reliable solutions to the general class of problems. Thus, default tolerances should be
adhered to until good reasons are found to change them.

SOL 401 error functions

The following three error functions (in terms of displacements, loads, and energy) are computed and
compared to tolerances.

Eu < EPSU (=10-2 by default)

Ep < EPSP (=10-2 by default)

Ew < EPSW (=10-6 by default)

where EPSU, EPSP, and EPSW are tolerances specified in the NLCNTL entry. However, only those criteria
chosen by the user (combinations of U,P, and/or W) are designed to be satisfied for convergence.

It is noted that divergence conditions are established independent of convergence criteria.

SOL 402 error functions

The following error functions (in terms of displacements, loads, and energy) are computed and
compared to tolerances.

Eu < PRCQ (=10-1 by default)

Ep < PRCR (=10-3 by default)

Ew < PRCE (=10-3 by default)

Ec < PRCF (=10-1 by default)

where PRCQ, PRCR, PRCE, and PRCF are tolerances specified in the NLCNTL2 entry.

It is noted that divergence conditions are established independent of convergence criteria.

15-32 Simcenter Nastran Multi-Step Nonlinear User’s Guide (SOL 401 and SOL 402), Simcenter 3D 2312 Series
© 2023 Siemens