> 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/include-fmu-components/model-fmus.md).

# Model FMUs

## Supported FMU types

ePHASORSIM supports two distinct paradigms for integrating Modelica-based FMUs into a power system simulation: **Predefined Single Controller FMUs** and **GenUnit FMUs**.

### Predefined Single Controller FMUs

* **What it is:** Individual, standalone components (such as a single exciter, governor, stabilizer, or machine) exported as separate `.fmu` files.
* **Signal Routing:** Handled automatically by the ePHASORSIM solver. Standard control signals (e.g., `EFD`, `PMECH`, `SLIP`, `VREF`) are automatically wired between the machine and controllers without manual schematic connections.
* **Best for:** Rapid testing, modular component swapping, and standard control topologies.
* **Input Format:** Supported **exclusively via the ePHASORSIM Excel template** for positive-sequence. Direct integration through third-party imports (PSS®E or PowerFactory) is not supported.

### GenUnit FMUs

* **What it is:** A complete generation unit packaged into a single `.fmu` file containing the generator model alongside all its associated controllers and limiters.
* **Signal Routing:** Handled entirely within the Modelica environment before export. All feedback loops, custom controls, and interconnections are explicitly wired in the Modelica diagram.
* **Best for:** Custom control logic, non-standard topologies, and automated batch network imports.
* **Input Format:** Supported via the **ePHASORSIM Excel template** as well as **third-party dynamic data formats** (PSS/E `.raw`/`.dyr` and PowerFactory).


---

# 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/include-fmu-components/model-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.
