> 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-powerfactory-model/opal-format-conversion.md).

# Identify Imported Components

When a **PowerFactory** 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 HYPERSIM model.

Component identifiers generated during import are derived from the PowerFactory `loc_name` (converted to lowercase with spaces removed) and the `ID` attribute (`FID` in DGS v6/v7). The table below summarizes the naming conventions used to generate component identifiers from the data contained in the PowerFactory DGS-XML file. **Use these component identifiers when defining I/O pins in the Excel configuration file.**

| PowerFactory DGS-XML Component                                                                                                        | Converted ePHASORSIM Component Identifier                                                                                                                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| <p><strong>Bus</strong><br>e.g., Bus with <code>loc\_name</code> = B1 and <code>ID</code> = 57</p>                                    | <p><strong>bus\_\[loc\_name]\_\[ID]</strong><br>e.g., bus\_b1\_57</p>                                                                                                                                                    |
| <p><strong>Load</strong><br>e.g., Load with <code>loc\_name</code> = Ld A and <code>ID</code> = 50</p>                                | <p><strong>load\_\[loc\_name]</strong><em><strong>\[ID]</strong></em><br><em>e.g., load\_lda\_50</em><br><br><em><strong>dynamicload</strong></em><strong>\[loc\_name]\_\[ID]</strong><br>e.g., dynamicload\_lda\_50</p> |
| <p><strong>Switch</strong><br>e.g., Switch with <code>loc\_name</code> = Switch A and <code>ID</code> = 220</p>                       | <p><strong>sw\_\[loc\_name]\_\[ID]</strong><br>e.g., sw\_switcha\_220</p>                                                                                                                                                |
| <p><strong>Generator</strong><br>e.g., Generator with <code>loc\_name</code> = G1 and <code>ID</code> = 54</p>                        | <p><strong>gen\_\[loc\_name]\_\[ID]</strong><br>e.g., gen\_g1\_54</p>                                                                                                                                                    |
| <p><strong>Static</strong><br>e.g., Static Generator with <code>loc\_name</code> = Static Gen and <code>ID</code> = 6</p>             | <p><strong>genstat\_\[loc\_name]\_\[ID]\_p</strong><br>e.g., genstat\_staticgen\_6\_p</p>                                                                                                                                |
| <p><strong>Line</strong><br>e.g., Line with <code>loc\_name</code> = Ln1 and <code>ID</code> = 44</p>                                 | <p><strong>line\_\[loc\_name]\_\[ID]</strong><br>e.g., line\_ln1\_44</p>                                                                                                                                                 |
| <p><strong>2-Winding Transformer</strong><br>e.g., Transformer with <code>loc\_name</code> = T1 and <code>ID</code> = 66</p>          | <p><strong>xf2w\_\[loc\_name]\_\[ID]</strong><br>e.g., xf2w\_t1\_66</p>                                                                                                                                                  |
| <p><strong>3-Winding TransformerLoad</strong><br>e.g., Transformer with <code>loc\_name</code> = Lr 3 and <code>ID</code> = 13</p>    | <p><strong>xf3w\_\[loc\_name]\_\[ID]</strong><br>e.g., xf3w\_tr3\_13</p>                                                                                                                                                 |
| <p><strong>Excitation System</strong><br>e.g., Exciter on the machine with <code>loc\_name</code> = G1 and <code>ID</code> = 54</p>   | <p><strong>exc\_\[machine loc\_name]\_\[machine ID]</strong><br>e.g., exc\_g1\_54</p>                                                                                                                                    |
| <p><strong>Power System Stabilizer</strong><br>e.g., PSS on the machine with <code>loc\_name</code> = G2 and <code>ID</code> = 55</p> | <p><strong>pss\_\[machine loc\_name]\_\[machine ID]</strong><br>e.g., pss\_g2\_55</p>                                                                                                                                    |
| <p><strong>Turbine-Governor</strong><br>e.g., TG on the machine with <code>loc\_name</code> = G1 and <code>ID</code> = 54</p>         | <p><strong>gov\_\[machine loc\_name]\_\[machine ID]</strong><br>e.g., gov\_g1\_54</p>                                                                                                                                    |


---

# 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-powerfactory-model/opal-format-conversion.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.
