> 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/prepare-the-sxst-file.md).

# Prepare the SXST File

## Verify compatibility

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

### Supported CYME version

* **CYME 7.2**.
* If the model was created in a newer CYME version, downgrade or export it to a **CYME 7.2-compatible format**.

### Supported network types and components

ePHASORSIM supports both **balanced** and **unbalanced** CYME networks.

{% hint style="danger" %}
All supported components found in the SXST file are imported and considered **in service**. Components marked as out of service in CYME are still imported as active components. Remove such components from the input file if they must remain out of service during simulation.
{% endhint %}

The following sections describe the CYME components that can be imported, their mappings to ePHASORSIM Native Library components, and the parameters used during import: [CYME 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-cyme-model/prepare-the-sxst-file/cyme-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.

#### Balanced networks

When the network is balanced, uncheck the **Unbalanced** option in the **Network data** tab. In this mode, ePHASORSIM uses a default system base power of **100 MVA** and a nominal frequency of **50 Hz**.

For balanced networks, ePHASORSIM builds the model using its **positive-sequence** **components**.

{% hint style="danger" %}
When the **Unbalanced** option is **unchecked**, the **Power-flow report** field is unavailable and power-flow results exported from CYME cannot be used. Instead, ePHASORSIM initializes the network using its internal power flow routine.
{% endhint %}

#### Unbalanced networks

When the CYME network contains unbalanced data, enable the **Unbalanced** option in the **Network data** tab. Otherwise, ePHASORSIM assumes the network is balanced.

For unbalanced networks, ePHASORSIM builds the model using its **multiphase components.**

{% hint style="danger" %}
When the **Unbalanced** option is **checked**, it is recommended to initialize the network using a **CYME power-flow results file**. The ePHASORSIM internal power-flow routine can also be used, but support for multiphase components is limited.
{% endhint %}

{% hint style="danger" %}
User-defined models are not supported when importing **unbalanced CYME networks**.
{% endhint %}

## Review required input files

* **SXST (.sxst)**: Network model data.
* **Excel Power-Flow Results File** (optional): Provides network initialization data. The power-flow results file can be exported from CYME and used as an alternative to ePHASORSIM's built-in three-phase power-flow initialization. See [Export CYME Power-Flow Results](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/prepare-the-sxst-file/export-cyme-power-flow-results.md) for details.


---

# 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/prepare-the-sxst-file.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.
