> 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/import-models-from-external-software-or-code/import-from-pss-e.md).

# Import from PSS/E

## Overview

The **PSS®E Import** feature allows users to bring PSS®E network models into HYPERSIM for offline or real‑time simulation. The import process reads PSS®E data files and converts the network, machines, and associated models into native HYPERSIM components. This capability enables users to reuse existing PSS®E studies, such as transmission networks, load‑flow cases, and dynamic models, within HYPERSIM while preserving the original system structure and operating point.

## Typical workflow

Importing a PSS®E model into HYPERSIM generally follows these steps:

1. Prepare the PSS®E input files, including the network and (optionally) dynamic data.
2. Import the network into HYPERSIM using the **Network Import** tool.
3. Review the import reports to identify unsupported elements or required adjustments.
4. Initialize the model and run the simulation.

Detailed procedures for each step are provided in the corresponding sections of this guide.

## Key capabilities

Using the PSS®E Import feature, users can:

* Import PSS®E network topology and steady‑state operating conditions
* Include dynamic models when supported
* Automatically generate detailed import reports
* Integrate large transmission‑level systems into HYPERSIM simulations

## When to use PSS®E Import

PSS®E Import is particularly well suited for:

* Reusing existing PSS®E planning or stability studies in HYPERSIM
* Performing real‑time or offline simulation of large transmission networks
* Validating dynamic behavior under disturbances using HYPERSIM
* Transitioning studies from PSS®E to real‑time simulation environments


---

# 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/import-models-from-external-software-or-code/import-from-pss-e.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.
