5.15.16.3. Shell-to-Solid Submodels

In the shell-to-solid submodeling technique, the coarse model is a shell model, and the submodel is a 3D solid model, as shown in this example:

Figure 5.17: 3D Solid Submodel Superimposed on Coarse Shell Model

3D Solid Submodel Superimposed on Coarse Shell Model

The procedure for shell-to-solid submodeling is essentially the same as that for solid-to-solid submodeling, with these exceptions:

  • Shell-to-solid submodeling is activated by setting the Transfer Key to Shell-Solid in the Imported Load details view.

  • Cut boundaries on the submodel are the end planes that are normal to the shell plane (see Figure 5.18: Node rotations (a) before mapping command, (b) after mapping command).

  • To determine the degree-of-freedom values at a cut-boundary node, the program first projects the node onto the nearest element in the shell plane. The degree-of-freedom values of this projected point are then calculated by interpolation and assigned to the corresponding node.

  • In a structural analysis, only translational displacements are calculated for the cut-boundary nodes, but their values are based on both the translations and rotations of the projected point. Also, the node is rotated such that the nodal UY direction is always perpendicular to the shell plane, as shown in Figure 5.18: Node rotations (a) before mapping command, (b) after mapping command. A UY constraint is calculated only for nodes that are within 10 percent of the average shell element thickness from the shell plane, preventing overconstraint of the submodel in the transverse direction.

    Figure 5.18: Node rotations (a) before mapping command, (b) after mapping command

    Node rotations (a) before mapping command, (b) after mapping command


Note:
  • If you are using the Material Assignment feature on source bodies that are different (shell and beam), you could experience mapping errors. The application may skip a source body during the mapping process. To address this issue, use the feature on the bodies individually – do not mix body types.

  • The application only considers beam and shell section type elements from the source data. It ignores all other section types.