> 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-cyme-model.md).

# Use a CYME Model

ePHASORSIM can import power system models developed in **PowerFactory** using standard **DGS-XML File**. During import, supported network and dynamic models are mapped to corresponding **ePHASORSIM** [Native Library components](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/integrate-a-power-system-model-to-ephasorsim/native-library-components.md) and converted into the data structures required by the solver.

ePHASORSIM provides two categories of power system components:

* **Positive-sequence components** for balanced network simulations.
* **Multiphase components** for unbalanced network simulations.

{% hint style="info" %}
**CYME** imported models support both **positive-sequence** and **multiphase components**.
{% endhint %}

## Requirements

### Simulator license

Your simulator license must include the **EPHASOR\_INPUTFORMAT\_CYME** feature. To verify, [check that EPHASOR\_INPUTFORMAT\_CYME is listed and enabled in your license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md).

### Workstation license

Your workstation license must include the **EPHASOR\_INPUTFORMAT\_CYME** feature. To verify, [check that EPHASOR\_INPUTFORMAT\_CYME is listed and enabled in your license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/workstation-license.md).

## Import workflow

Follow these steps to import a PowerFactory model:

1. **Prepare the DGS-XML File**\
   Ensure that the PowerFactory model and its DGS-XML file meet the import requirements.
2. **Import the PowerFactory Model**\
   Import the DGS-XML file into ePHASORSIM.
3. **Identify Imported Components**\
   Identify the component identifiers generated for imported components. These identifiers are required when defining I/O pins.

You may also, if needed, **augment an imported model** by adding new components that are not present in the original network data.

Once the power system model is imported, continue to the [Configure ePHASORSIM Block Ports](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/configure-ephasorsim-block-ports.md) section.

## Limitations

FMU-based component integration is not supported for CYME import workflows.


---

# 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-cyme-model.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.
