Standardization Projects and Groups Related to FMI

The FMI development is organised as a Modelica Association Project (MAP) inside the Modelica Association. See also History.


In many applications there is the need to design, simulate and execute a network of components (simulation models, software, hardware etc.). In order to be able to do this tool independently and seamlessly, the purposes of the “System Structure and Parameterization of Components for Virtual System Design (SSP)” project are:

Link to project page.


The DCP is a platform and communication medium independent standard for the integration of real-time systems into simulation environments. The DCP is standardized by the Modelica Association, where it is maintained as a Modelica Association Project (MAP).

The DCP is defined in a way such that it supports the integration of FMI based systems within DCP slaves. This applies to FMI for Model Exchange as well as FMI for Co-Simulation. The DCP state machine is designed that it matches operations defined in the state machine of the FMI. Furthermore, the DCP slave description file is aligned to the model description file of the FMI. The data types defined in the DCP slave description file may also be converted to FMI compatible data types. This principle supports FMI-based simulation models, considering the fact that FMI is one of the most common co-simulation standards today.

Whereas the FMI represents an application programming interface (API), the DCP represents a communication protocol. Therefore, it becom es possible to integrate various kinds of systems. The DCP specification is suitable for a broad range of computing platforms. It may be implemented on hardware as well as in software. Typical examples are middleware, runtime environments, (virtualized) operating systems, electronic control units, FPGAs, and many more.

Link to project page.


At the beginning of the ITEA2 project MODELISAR (the project in which FMI was initially developed) it was planned to develop FMI for Applications. The intention was to specify an API for simulation tools that allows the access of model parameters, stimulations and simulation results and to control simulation experiments as well. The API was supposed to provide tool independent access to simulation computations for optimization tools, test management and workflow definition tools.

The project group noticed the parallel work of the ASAM XIL standardization group. Thus, both groups came to the conclusion not to develop a parallel standard but to cooperate. The result of this cooperation is available as ASAM XIL-MA, which is a subset from ASAM XIL standard. It contains the model access port specification as well as necessary common functionality for a proper operation of the model access. XIL-MA is open to public and the documentation of the standard can be obtained from ASAM for free without membership.

Link to specification.

ProSTEP Smart System Engineering

One of the topics of the Smart Systems Engineering project is to find solutions for the cross-disciplinary and cross-enterprise exchange of behavioral models. The Functional Mockup Interface (FMI) is viewed as the basic technology for the exchange.

Link to project page.


FMI for PLM was developed as part of the ITEA2 project MODELISAR. The intention is to provide a generic way to handle all FMI related data needed in a simulation of systems in a “Product Lifecycle Management” system.

This includes:

Generic processes are defined here, as well as a format description to communicate between the PLM system and the authoring tools.

Version 1.0 was released on Mar. 31, 2011.

Complete Package Specification Only