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

# PSS/E Component Mapping

## RAW file component mapping

The **RAW (.raw)** file contains the steady-state network data used to build the power system model. It also defines the system base power and nominal frequency.

Not all RAW records and fields are imported. The following sections identify the supported data and any applicable restrictions. Any field that is not listed in the tables is ignored during import.

### Bus data

The table below lists the supported fields and accepted values from the **Bus data** section of the RAW file.

| Entry  | Description                                                                                              |
| ------ | -------------------------------------------------------------------------------------------------------- |
| I      | Bus Number (1-999999)                                                                                    |
| ‘NAME’ | Bus Identifier (Any alpha-numerical string with up to 12 characters)                                     |
| BASEKV | Bus base voltage                                                                                         |
| IDE    | <p>Bus Type Code (Power Flow Only)<br>1 = PQ Load Bus<br>2 = PV Generator Bus<br>3 = Slack/Swing Bus</p> |
| VM     | Bus voltage magnitude (pu)                                                                               |
| VA     | Bus voltage phase angle (degree)                                                                         |

{% hint style="danger" %}
Buses with type 4 will not be imported.
{% endhint %}

### Load data

The table below lists the supported fields and accepted values from the **Load data** section of the RAW file.

<table data-search="false"><thead><tr><th>Entry</th><th>Description</th></tr></thead><tbody><tr><td>I</td><td>Bus Number (1-999999)</td></tr><tr><td>ID</td><td>Load ID (1–2 characters)</td></tr><tr><td>STATUS</td><td>Load Status<br>1 = In Service<br>2 = Out of Service</td></tr><tr><td>PL</td><td>Active power component of constant MVA load (MW)<br>At least one P or Q must be non-zero for the load to be imported</td></tr><tr><td>QL</td><td>Reactive power component of constant MVA load (MVAr)</td></tr><tr><td>IP</td><td>Active power component of constant current load (MW)</td></tr><tr><td>IQ</td><td>Reactive power component of constant current load (MVAr)</td></tr><tr><td>YP</td><td>Active power component of constant admittance load (MW)</td></tr><tr><td>YQ</td><td>Reactive power component of constant admittance load (MVAr)</td></tr></tbody></table>

{% hint style="danger" %}
Loads with all zero values for PL, QL, IP, IQ, YP and YQ are ignored and not imported into the .opal file.
{% endhint %}

### Fixed shunt data

The table below lists the supported fields and accepted values from the **Fixed shunt data** section of the RAW file.

| Entry  | Description                                                 |
| ------ | ----------------------------------------------------------- |
| I      | Bus Number (1-999999)                                       |
| ID     | Shunt ID (1-2 characters)                                   |
| STATUS | <p>Shunt Status<br>1 = In service<br>0 = Out of service</p> |
| GL     | Active component of shunt admit­tance to ground (MW)        |
| BL     | Reactive component of shunt admit­tance to ground (MVAr)    |

### Switched shunt data

The table below lists the supported fields and accepted values from the **Switched shunt data** section of the RAW file.

| Entry | Description                                                          |
| ----- | -------------------------------------------------------------------- |
| I     | Bus Number (1-999999)                                                |
| MODSW | Control Mode (0)                                                     |
| STAT  | <p>Switched shunt Status<br>1 = In service<br>2 = Out of service</p> |
| BINIT | Initial switched shunt admittance (MVAr at unity voltage)            |

### Generator data

The table below lists the supported fields and accepted values from the **Generator data** section of the RAW file.

<table data-search="false"><thead><tr><th>Entry</th><th>Description</th></tr></thead><tbody><tr><td>I</td><td>Bus Number (1-999999)</td></tr><tr><td>ID</td><td>Generator ID (1–2 characters)</td></tr><tr><td>PG</td><td>Generator active power output (MW)<br>Must be ≥ 0</td></tr><tr><td>QG</td><td>Generator reactive power output (MVAr)</td></tr><tr><td>QT</td><td>Maximum generator reactive power output (MVAr)</td></tr><tr><td>QB</td><td>Minimum generator reactive power output (MVAr)</td></tr><tr><td>MBASE</td><td>Machine MVA base</td></tr><tr><td>ZR</td><td>Machine resistance (pu on MBASE base)</td></tr><tr><td>ZX</td><td>Machine reactance(pu on MBASE base)</td></tr><tr><td>STAT</td><td>Generator Status<br>1 = In service<br>0 = Out of service</td></tr></tbody></table>

{% hint style="info" %}
For machine types GENROU, GENROE, GENSAL, GENSAE and CIMTR3-double cage, the reactance value is replaced by sub-transient reactance values from the `.dyr` file.
{% endhint %}

### Non-transformer branch data

The table below lists the supported fields and accepted values from the **Non-transformer branch data** section of the RAW file.

<table data-search="false"><thead><tr><th width="342">Entry</th><th>Description</th></tr></thead><tbody><tr><td>I</td><td>Branch from bus number (1-999999)</td></tr><tr><td>J</td><td>Branch to bus number</td></tr><tr><td>CKT</td><td>Branch circuit ID (1-2 characters)</td></tr><tr><td>R</td><td>Branch resistance (pu)<br>Must be ≥ 0</td></tr><tr><td>X</td><td>Branch reactance (pu)</td></tr><tr><td>B</td><td>Total branch charging susceptance (pu)</td></tr><tr><td>ST</td><td>Branch Status<br>1 = In service<br>0 = Out of service</td></tr></tbody></table>

### Transformer data

The table below lists the supported fields and accepted values from the **Transformer data** section of the RAW file.

<table data-search="false"><thead><tr><th>Entry</th><th width="399.111083984375">Description</th></tr></thead><tbody><tr><td>I</td><td>Winding 1 bus number (1-999999</td></tr><tr><td>J</td><td>Winding 2 bus number</td></tr><tr><td>K</td><td>Winding 3 bus number</td></tr><tr><td>CKT</td><td>Branch circuit ID (1-2 characters)</td></tr><tr><td>CW</td><td>The winding data I/O code defines the units in which the turns ratios are specified</td></tr><tr><td>CZ</td><td>The impedance data I/O code defines the units in which the winding impedances are specified</td></tr><tr><td>CM</td><td>The magnetizing admittance I/O code defines the units in which are specified</td></tr><tr><td>MAG1, MAG2</td><td>Magnetizing conductance and sus­ceptance respectively (for CW=1, pu on system MVA and winding 1 bus voltage base)</td></tr><tr><td>STAT</td><td>Transformer Status<br>1 = In Service<br>2 = Out of Service</td></tr><tr><td>R1-2, R3-1, R2-3</td><td>Measured resistance between wind­ings 1-2, 3-1 and 2-3 respectively (for CZ=1, pu on system MVA and winding voltage base)</td></tr><tr><td>X1-2, X3-1, X2-3</td><td>Measured reactance between wind­ings 1-2, 3-1 and 2-3 respectively (for CZ=1, pu on system MVA and winding voltage base)</td></tr><tr><td>WINDV1, WINDV2, WINDV3</td><td>For CW=1, winding 1, 2 and 3 off-nominal turn ratio in pu</td></tr><tr><td>ANG1, ANG2, ANG3</td><td>Winding 1, 2 and 3 phase shift (-180 to +180 Degrees)</td></tr></tbody></table>

## DYR file component mapping

The DYR file format (.dyr) stores the dynamic model parameters required for transient and dynamic analysis. The following table includes the PSS/E dynamic models that ePHASORSIM's built-in library can import from a DYR file:

| Category                    | Supported Model                                                                                                                                  |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Synchronous machine**     | GENCLS, GENROE, GENROU, GENSAE and GENSAL.                                                                                                       |
| **Induction machine**       | CIMTR3                                                                                                                                           |
| **Excitation system**       | ESAC1A, ESAC5A, ESAC6A, ESDC1A, ESDC2A, ESST1A, ESST4B, EXAC1, EXAC2, EXAC4, EXDC2, EXPIC1, EXST1, IEEET1, IEEEX1, IVOEX, SCRX, SEXS and URST5T. |
| **Power system stabilizer** | IEE2ST, IEEEST, PSS2A, PSS2B, STAB1, STAB3 and STAB4.                                                                                            |
| **Turbine-governor**        | GAST, HYGOV, IEEEG1, IEEEG2, IEESGO and TGOV1.                                                                                                   |

{% hint style="info" %}
If your DYR file contains models that are not listed above, you must implement them using the User-Defined Models feature.
{% endhint %}


---

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