You are here: Home » Products » alaska/MultibodyDynamics » Properties


Simulation models can be divided into functional units - submodels. This makes it possible to generate simulation models with task-specific functionality and modeling depth very efficiently. Properties of submodels are:

  • can run independently
  • automatic assembly
  • easily replaceable
  • interaction via predefined coupling points
  • data flow across submodels via source-target channels
  • multiple use in a simulation model




Simulation models can be completely parameterized. This applies to the properties of the bodies, the geometric and physical properties of the joints, as well as forces and moments acting in the system or acting on the system from outside. Main features of ParameterSets are:

  • definition in external files (XML)
  • documented format, so that files can be generated automatically
  • clear storage in freely definable tables
  • comfortable set editor in alaska/ModellerStudio
  • ParameterSets can be loaded directly from the model
  • ParameterSets usable with alaska/batch, single or "in one piece"

Analysis Core

alaska/MultibodyDynamics provides all functionalities required for the analysis of multi-body system models. Modern and efficient methods are implemented for this purpose.

  • Calculation of initial positions (assembly, coupling of submodels)
  • Calculation of equilibrium states
  • Calculation of stationary system states
  • Calculation of the system behavior in the time domain
  • Computation of natural frequencies and vibration forms in arbitrary system states
  • various (explicit) solvers for classic MBS
  • efficient and robust (implicit) solver for numerically stiff systems
  • iterative solvers for linear analysis of large simulation models

    Model description

    Simulation models for alaska/MultibodyDynamics are stored in a readable (ASCII) format. These descriptions can be generated with the alaska/ModellerStudio or any text editor. Characteristics of the model description language are:

    • C-oriented syntax
    • description of mathematical dependencies
    • model description completely parameterizable
    • definition of application-specific model elements (templates)
    • use of derivation and inheritance mechanisms
    • any hierarchical structuring of the model