Importing simulation entities

Use the Import Simulation Entities command to import loads, constraints, solutions and other simulation entities from a source simulation into a target simulation. The Import Simulation Entities command supports the following simulation entities:

• Loads

• Constraints

• Simulation objects

• Materials

• Physical properties

• Modeling objects

• Fields

• Groups

• Regions

• Solutions

• Condition sequences

• Layout states

• Result probes

When you import simulation data, the software performs a correspondence check between the FEM or assembly FEM referenced by the source simulation and the FEM, component FEM, or assembly FEM referenced by the target simulation. If the source and target match, the software automatically reattaches any imported simulation entities to the corresponding geometry or mesh entities in the target. For more information, see Correspondence checks and reattachment.

If the source and target do not match, the software still imports the entities, but does not attach them to geometry or mesh entities. You can edit the imported entities to reattach them as needed.

If you do not want the software to import all entity types, you can select specific entities to import. For example, you can select Loads as the entity type and then select a specific loads to import.

If you import a Solution entity type, the software also imports any result probes and reference points associated with the solution.

Using imported loads and constraints in a solution

When you create loads and constraints, they are automatically assigned to the active solution. Imported boundary conditions, however, are not automatically assigned to any solution. To use imported loads and constraints, in the Simulation Navigator, drag the imported boundary conditions to the appropriate container in your solution or subcase. For more information, see Boundary condition status in Simulation Navigator and Explicitly add a boundary condition to a solution, step, or subcase.

Importing component boundary conditions to an assembly FEM simulation

Typically, you use the Import Simulation Entities command when working with simulations referencing assembly FEMs. Using the Import Simulation Entities command, you can:

• Import simulation entities defined for component FEMs, such as complex loads or boundary conditions. You can also import materials and physical property tables to use as overrides.

• Reuse simulation entities in multiple component instances. For example, you can define a bolt pre-load once for a single bolt, and then import that bolt pre-load to an array of bolt occurrences in the assembly FEM.

• Import simulation entities defined for a subassembly FEM to the simulation referencing the parent assembly FEM. For example, suppose you create an assembly FEM and then create a simulation in which you define multiple surface-to-surface glue or contact simulation objects. If you subsequently map this assembly FEM into a parent assembly FEM, you can import the glue or contact objects into the parent assembly FEM's simulation.

Surface-to-surface glue objects imported to an assembly FEM simulation.

When working with assembly FEM simulations, you only need to import materials, physical property tables, and simulation objects once for those entities to be available to the entire simulation. When importing spatial fields, however, you will need to import the spatial field for each component instance that references it.

Reusing entities in unrelated simulations

The Import Simulation Entities command is also useful for sharing and reusing simulation entities, whether you are working with an assembly FEM simulation or a simulation that references a single FEM file. Depending on the types of analyses you perform, simulation entities such as solutions, fields, property table overrides, or solver-specific modeling objects may be time-consuming to set up and configure. Using Import Simulation Entities, you can share and reuse highly configured simulation entities among multiple simulations, even if the referenced FEMs do not correspond.

Renumbering of boundary conditions

During the import of a simulation, boundary conditions are renumbered using an offset specified in the Import Simulation Entities dialog box. This renumbering only applies to streams, voids, and convecting zones (the index-based loads). Since the load IDs are the inputs to the expression functions that support these types of loads (for example, ST(), SM(), etc.), it is important to manage the IDs carefully. This allows you to efficiently manage the load IDs for index-based loads as you make changes to your model, such as importing loads from other models.

The software adds the following number to the imported boundary conditions:

i+p

where i is the index of the source boundary condition and p is the offset specified in the Specify Offset box. If the number is not available (that is, already assigned), a second round of renumbering takes place where the software assigns the next highest number after i+p.

In addition, you can link the name and ID number of the index-based loads using the %%ID parameter. For example, if you want all of your streams named Stream1, Stream2, Stream3, and so on, you would specify Stream%%ID in the Specify Offset box.

Entity behavior during import

During the import of a simulation, the software may rename some entities, partially import others, and exclude some.

You can rename an entity by entering a string in the String to prepend to simulation entity names box in the Import Simulation Entities dialog box. The software prepends the string to the existing entity name. If you do not enter a string, the software uses the following name convention for the entities:

source-part-name**copied**source-name

The following table describes the import behavior for specific entity types. Note that the source simulation is the simulation being imported and the target simulation is the simulation into which the source simulation is being imported.

Entity type	Import behavior
Condition sequence	If the target simulation has a condition sequence, the software imports the condition parameters from the source simulation, but does not add any new time points to the target simulation condition sequence.If the target and source condition names match, the software imports the parameters and values, but not the condition. The software maintains the relationship between condition sequences and solutions if the solutions are also imported.If a condition parameter exists in the current simulation with the same name and measure, the software does not import it.If a condition parameter exists with the same name but a different measure, the software imports it using the format source-part-name**copied**source-name. If there is a conflict with the imported name, the software appends a number to it. If the condition parameter does not exist in the current simulation, the software uses the original name.
Solution	When you import solutions, the software imports all of the result probes attached to the solutions, including their result variables. If the result probe references geometry, nodes, or elements that are available, the imported result probe also references the geometry. If the geometry is not available in the target simulation, the result probe is not valid after the import until it is reattached to a valid geometry.The software imports all result variables used by any imported result probes being imported, with a prepended name and updates the probe formula.If there is a reference point with the same name in the target simulation, the software automatically attaches the reference point.If the reference point does not exist in the target simulation but the finite element models in the target and source simulation are the same, the software imports the reference point in the same relative location with respect to the finite element model; otherwise, it imports to its existing XYZ location.If a result variable exists in the current simulation with the same name and attributes, the software does not import it. If a result variable exists with the same name but a different attributes, the software imports it using the format source-part-name**copied**source-name. If it does not exist in the current simulation, the software uses the original name.
Layout states	When you import a simulation, the software imports fields referenced by the layout state. Variables are copied with the fields.If you do not select solutions, result probes, and boundary conditions explicitly, the software does not import them.Mesh collectors, nodes, and elements are not imported.
Result probe	When you import individual result probes, the software imports the selected result probes with their referenced result variables, expressions, fields, condition sequence parameters, and other entities needed to support them. These are the same entities that are included when you import the entire solution. For more information, see Solution above. You select the source simulation containing the result probe and the target simulation in which to import the result probe. You can also choose not to associate the result probe with a target simulation. In that case, the software imports the source solution without referenced boundary conditions.When you import a result probe, its state is active or asleep (inactive), depending on whether the entities of the result probe can be mapped to the target simulation.For more information, see Correspondence checks and reattachment.

Naming conflicts of expressions

When you import a simulation entity that contains expressions, there is a possibility that an expression has the same name as an existing expression in the simulation. An example of a simulation entity that contains expressions is a force whose magnitude is defined by an expression.

The options in the Import Simulation Entities dialog box, in the Advanced Options group, allow you control how the software resolves such naming conflicts.

• Select the Keep Existing option to replace the formula of the expression in the simulation entity with the formula of the existing expression in the simulation.For this case, the dimensionality of both expressions must be the same. If they are not, the expression is imported using the Keep Both option.

• Select the Keep Imported option to replace the formula of the existing expression in the simulation with the formula of the expression in the simulation entity.For this case, the dimensionality of both expressions must be the same. If they are not, the expression is imported using the Keep Both option.

• Select the Keep Both option to rename the expression in the simulation entity so that a naming conflict no longer exists.The expression is renamed by appending a text string to its name. You specify the text string in the Suffix Key box.

Where do I find it?

Application	Pre/Post
Prerequisite	The Simulation file must be displayed.
Menu	File→Import→Simulation Entities
Simulation Navigator	Right-click a component FEM→Import Simulation Entities

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Importing simulation entities, Simcenter 3D 2021.1 Series

© 2020 Siemens

window.mainLanguage="en_US"

window.delivId=""

window.projectId=""

MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });