> 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/identify-imported-components.md).

# Identify Imported Components

When a **PSS®E** model is imported, component names are converted to ePHASORSIM naming conventions. The resulting names, referred to as **component identifiers**, are used to identify imported components when defining **I/O pins**.

I/O pins are ports defined in an Excel configuration file that enable signal exchange between the **ePHASORSIM** power system model and the surrounding Simulink model.

The table below summarizes the naming conventions used to generate component identifiers from the data contained in the PSS®E RAW and DYR files. **Use these component identifiers when defining I/O pins in the Excel configuration file.**

<table data-search="false"><thead><tr><th>PSS/E Component</th><th>Converted OPAL Component Identifier</th></tr></thead><tbody><tr><td><strong>BUS</strong><br>e.g., Bus with <code>ID</code> = 30</td><td><strong>bus_</strong><br>e.g., bus_30</td></tr><tr><td><strong>LOAD</strong><br>e.g., Load with <code>ID</code> = 1 connected to bus 10</td><td><strong>load_Z_</strong> , <strong>load_I_</strong> , or <strong>load_P_</strong><br>e.g., load_Z_10_,</td></tr><tr><td><strong>Fixed Shunt and Switch Shunt</strong><br>e.g., Shunt with <code>ID</code> = 1 connected to bus 10</td><td><strong>fSH_</strong> or <strong>swSH_</strong><br>e.g., fSH_10_1</td></tr><tr><td><strong>GENERATOR</strong><br>e.g., Generator with <code>ID</code> = G1 connected to bus 39</td><td><strong>gen_</strong><br>e.g., gen_39_G1</td></tr><tr><td><strong>BRANCH</strong> (line)<br>e.g., Line with <code>ID</code> = 1 between bus 9 and 39</td><td><strong>line_b1_to_b2</strong><br>e.g., line_9_to_39_1</td></tr><tr><td><strong>2-Winding TRANSFORMER</strong><br>e.g., Transformer with <code>ID</code> = T1 between bus 2 and 30</td><td><strong>xf_b1_to_b2</strong><br>e.g., xf_2_to_30_T1</td></tr><tr><td><strong>3-Winding TRANSFORMER</strong><br>e.g., Transformer with <code>ID</code> = T1 between buses 100, 101, and 102</td><td><strong>xf_b1_b2_b3</strong><br>e.g., xf_100_101_102_T1</td></tr><tr><td><strong>Excitation system</strong><br>e.g., Exciter at bus 37 connected to machine with <code>ID</code> = G1</td><td><strong>ex_</strong><br>e.g., ex_37_G1</td></tr><tr><td><strong>Power system stabilizer</strong><br>e.g., PSS at bus 38 connected to machine with <code>ID</code> = 2</td><td><strong>pss_</strong><br>e.g., pss_38_2</td></tr><tr><td><strong>Turbine-governor</strong><br>e.g., TG at bus 37 connected to machine with <code>ID</code> = 1</td><td><strong>tg_</strong><br>e.g., tg_37_1</td></tr></tbody></table>

Note that running the simulation in Simulink, with or without configured pins, generates a `*_solver.opal` file containing the imported component identifiers.

These identifiers correspond exactly to those recognized by the solver and can be used in the **Pins** worksheet to reference components.


---

# 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/identify-imported-components.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.
