> 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-powerfactory.md).

# Import from PowerFactory

## Overview

The **PowerFactory Import** feature allows users to bring PowerFactory network models into HYPERSIM for offline or real‑time simulation. The import process relies on exporting the PowerFactory model in DGS (XML) format, which is then converted into native HYPERSIM components. This capability enables users to reuse existing PowerFactory studies, such as transmission and distribution networks and load‑flow configurations, within HYPERSIM while preserving the original network structure and operating conditions.

## Typical workflow

Importing a PowerFactory model into HYPERSIM generally follows these steps:

1. Export the network from PowerFactory as an XML file in DGS format.
2. Import the DGS file into HYPERSIM using the **Network Import** tool.
3. Review the import reports to identify unsupported elements or required adjustments.
4. Run the simulation in HYPERSIM.

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

## Key capabilities

Using the PowerFactory Import feature, users can:

* Import PowerFactory network topology and load‑flow data
* Convert supported PowerFactory components into HYPERSIM equivalents
* Automatically generate detailed import reports
* Execute PowerFactory‑derived network models in HYPERSIM

## When to use PowerFactory Import

PowerFactory Import is particularly well suited for:

* Reusing existing PowerFactory network studies in HYPERSIM
* Migrating load‑flow‑based models to offline or real‑time simulation
* Validating network behavior under dynamic events
* Transitioning PowerFactory models to HYPERSIM execution 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-powerfactory.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.
