> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/include-fmu-components/integrate-fmus.md).

# Integrate FMUs

Once FMUs have been generated, they must be added to the ePHASORSIM project and referenced by the block.

The integration workflow depends on how the power system model was created:

* **Excel Template workflow:** The FMU must be declared in the Excel configuration file.
* **Imported model workflow:** Additional configuration files are required to map imported components to the FMU.

Follow the steps below to integrate FMU components into an ePHASORSIM project.

{% stepper %}
{% step %}

### Copy the FMU Files

Copy the generated FMU files to the ePHASORSIM project directory. For ease of maintenance, it is recommended to store all FMUs in a dedicated subdirectory within the project.
{% endstep %}

{% step %}

### Configure the model definition

Configure the FMUs according to the workflow being used.

For models built with the **Excel Template**, add the FMU definitions to the Excel configuration file as described in the [Model Built with Excel](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/include-fmu-components/integrate-fmus/model-built-with-excel.md) section.

For imported models, configure the mapping files required by the selected import workflow:

* [PSS/E Model](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/include-fmu-components/integrate-fmus/pss-e-model.md)
* [PowerFactory Model](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/include-fmu-components/integrate-fmus/powerfactory-model.md)
  {% endstep %}

{% step %}

### Configure the FMU path

1. Double-click the **ePHASORSIM Interface** block to open its mask.
2. Navigate to the **Common** tab.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-b6903218662d2440326008f1f230dd099e64857d%2Feph-hyp-fmu-folder.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Next to the **External components (optional)** field, click **Select folder** and choose the folder with the FMU files (`*.fmu`).
4. Next to the **Mappings** field, click **Select folder** and choose the folder with the `*.yaml` mapping files.
   {% endstep %}

{% step %}

### Configure block ports

With the power system model now defined, continue to the [Configure ePHASORSIM Block Ports](https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/configure-ephasorsim-block-ports.md) section to define the signals that will be exchanged between the ePHASORSIM model and the surrounding HYPERSIM environment.

FMU components that expose inputs or outputs for interaction with external HYPERSIM logic require additional FMU-specific I/O pin definitions in the **Pins** worksheet.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/include-fmu-components/integrate-fmus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
