> 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/use-a-pss-e-model/prepare-import-files.md).

# Prepare Import Files

## Verify compatibility

Before importing a **PSS®E** model, verify that the required files and model components are supported.

### Supported PSS®E version

* **PSS®E v32**
* Models from other versions must be converted to the v32 format before import: [Migrate PSS/E Versions](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/use-a-pss-e-model/prepare-import-files/migrate-pss-e-versions.md).

### Supported components

ePHASORSIM supports standard PSS®E network components and dynamic models, including:

* Buses, lines, transformers, loads, and generators
* Synchronous machine, exciter, governor, and stabilizer models

The following section describes the PSS®E components that can be imported, their mappings to ePHASORSIM Native Library components, and the parameters used during import: [PSS/E Component Mapping](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/use-a-pss-e-model/prepare-import-files/pss-e-component-mapping.md).

For components that are not supported, users can develop custom components in a Modelica environment and import them as **Functional Mock-up Units (FMUs)**. See [Include FMU Components](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.md) for complete implementation and configuration details.

Replace or remove any unsupported or custom dynamic models before importing.

{% hint style="danger" %}
**PSS®E** imported models support only **positive-sequence components**.
{% endhint %}

## Review required input files

PSS®E models are imported using the following files:

* **RAW (.raw)**: Network data
* **DYR (.dyr)**: Dynamic model definitions

The following sections describe the supported data, accepted values, and import limitations for each file type.


---

# 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/use-a-pss-e-model/prepare-import-files.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.
