With CATIA Systems Engineering , system architects, product engineers, designers and technical experts define both technical and business aspects. The RFLP approach (Requirements, Functional, Logical and Physical Design) upholds a full traceability during product development and product introduction. This helps shortening the gap between requirements analysis and the choice of the right solution.

CATIA Systems DBM Export for Simulink

A complete systems model developed in CATIA DBM can be simulated within a Simulink environment

Today, more and more equipment such as specialized machine tools, vehicles, aircraft or nuclear power plants, control logic is performed by programs embedded within Electronic Control Units (ECU’s). Often written on their own, these controller programs lack overall simulation of the controller coupled to the formal model of the controlled equipment.

To stimulate and validate these ECU’s, CATIA Systems DBM export for Simulink enables systems engineers to export the plant model code to a MATLAB/Simulink environment. As a result, the important Simulink community of systems engineers can benefit from these Modelica plant models developed in CATIA DBM with its tight integration to 3D CAD modeling. The Simulink interface ensures the simulation of both the controlled plant and controller models to validate the closed loop system.

With this export capability, systems engineers tighten their cross-discipline collaboration – whether they are CATIA Systems V6 or Simulink users.

Export a Modelica plant model developed in CATIA DBM to use it in a Simulink environment

Strengthen collaborative work between systems engineers using CATIA Systems V6 or Simulink

Refine easily the design from simple start model to detailed product

Re-use components in many different situations and reduce maintenance time

Ability to generate Simulink “S-Functions” from CATIA DBM models to run them in a Simulink environment.

Use the Simulink interface on platforms other than Microsoft Windows

as it is implemented using a two-step export/import procedure without any dependence on DDE (Dynamic Data Exchange).

Component oriented approach for complex multi-domain systems

It is not immediately obvious from the block diagram what this model contains and to be able to understand what effects are included. The engineer would have to figure out what equations are represented in this model and then decide if this system of equations included the required effects. The component orientated approach is much more efficient.