About Abstractions

An abstraction describes how a component subsystem manages input/output and how it reacts to external events.

You must have one or more abstractions defined for each component before an experiment is valid for execution. An abstraction has the following characteristics:

• It is an executable model of the responsiveness of a subsystem to various conditions.
• It provides input and output interfaces.
• It might optionally provide for modifiable internal parameters.

Multiscale Experiment Creation recognizes two basic types of abstractions:

• 0D logical plant or controller models formatted as Functional Mockup Units (FMUs)
• 3D physics simulations published from the 3DEXPERIENCE platform authoring apps such as Mechanical Scenario Creation and Fluid Scenario Creation

Abstractions are assigned within components. The abstractions must have the same port definitions as the component.

An FMU represents a single abstraction, but a component can accomodate multiple abstractions for use in different experiment runs.