> 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/examples/how-to/psse-import-ieee-118-bus-system.md).

# PSSE Import IEEE 118-Bus System

## Description

The **PSS/E Import 118-Bus** example, located in **File > Open an Example File > How To**, is based on a modified IEEE 118-bus test case \[2] that approximates the American Electric Power system (U.S. Midwest, December 1962). The main objective is to demonstrate the PSS®E-to-HYPERSIM import workflow through the Unified Database, verify correct component mapping and parameters, and validate the imported model using load flow and dynamic short-circuit studies against PSS®E results.

## Requirements

This example model does not require any additional hardware or licenses.

## Detailed explanation

The system comprises 19 generators, 35 synchronous condensers, 177 lines, 9 transformers, and 91 loads \[2]. All generating units except gen\_69 and gen\_89 are identical and each includes GENROU, EXST1, TGOV1, and PSS1A. The unit at gen\_69 (slack bus) includes only GENROU, and the unit at gen\_89 includes GENROU and TGOV1.

The original benchmark is a PSS®E v32.1.0 model. It is imported into HYPERSIM via the Unified Database to automatically parse, map, and export the network and controls:

* Parser: reads PSS®E components and parameters and creates a list of objects.
* Mapper: matches PSS®E objects and parameters to Unified Database entries.
* Exporter: builds the HYPERSIM model after a successful database import.

1. Create a new HYPERSIM model.
2. Follow [PSS®E Network Import](broken://pages/a5126d5a0d545625837adf494e992d1649a2e998) to import the model.

* The `PSSE_ref_model` folder contains three files: IEEE\_118\_bus.raw, IEEE\_118\_bus.dyr, and IEEE\_118\_bus.gps. The `.raw` and `.dyr` files are required; the `.gps` file is optional. All three share the same base name.

3. Wait for the “Import successful” message in the Import Panel.

### Post-import analysis and adjustments

Analyze the imported model using the Analyze button in the Network section of the HYPERSIM tab. An error may be reported:

| Error                                                                                                                                                                                                                                                       |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Error during network analysis. Cause: Line or decoupling element with both ends terminating on the same sub-station Element: line\_35\_to\_37\_1 Line or decoupling element with both ends terminating on the same sub-station Element: line\_54\_to\_55\_1 |

This occurs when a CP transmission line model and a PI transmission line model are connected in parallel. The CP model supports network decoupling into independent cores, whereas the PI model does not, leading to the error. Replace the two CP lines (line\_35\_to\_37\_1 and line\_54\_to\_55\_1) with PI lines using the following parameters.

For line\_35\_to\_37\_1:

| **General**           |
| --------------------- |
| Type:                 |
| line length           |
| Base power (perPhase) |
| Base voltage (rmsLN)  |
| Base frequency        |

| **Sequence**            |
| ----------------------- |
| Self impedance - Line 1 |
|                         |
| R                       |
| L                       |
| C                       |

For line\_54\_to\_55\_1:

| **General**           |
| --------------------- |
| Type:                 |
| line length           |
| Base power (perPhase) |
| Base voltage (rmsLN)  |
| Base frequency        |

| **Sequence**            |
| ----------------------- |
| Self impedance - Line 1 |
|                         |
| R                       |
| L                       |
| C                       |

After replacing the two CP lines with PI lines, re-run the analysis. The error is resolved and the output below the schematic displays:

Network analysis of \[PSSE\_Import\_118\_Bus.exe] done in 1.1317 sec.

### Dynamic short-circuit test setup

The short-circuit scenario is a three-phase-to-ground fault at bus 1 at t = 3 s, cleared at t = 3.1 s by tripping the lines connected to bus 1. Fault data are not contained in PSS®E `.raw` or `.dyr` files, so a manual setup in HYPERSIM is required.

## Fault implementation

* Add a three-phase fault (Network Switches and Breakers) and connect it to bus 1.
* In Timing, enable General operation. In General, set Control type to External (input pins).
* Set the Timing parameters as follows:

| Ropen                | 1.000  | MΩ  |
| -------------------- | ------ | --- |
| Rclosed              | 10E-9  | Ω   |
| Breaking Capacity    | 0.00   | A   |
| Base power (total)   | 100.00 | MVA |
| Base voltage (rmsLL) | 138.00 | kV  |
| Base frequency       | 60.0   | Hz  |

* Trigger the fault at t = 3 s with a Constant (1), a Pulse Delay (Td = 3 s, Ton = 1e9 s), and a Gain of 15 (1111 in binary to operate all three phases and ground).

Clear the fault by disconnecting bus 1 at t = 3.1 s:

* Insert two circuit breakers (CBs) at the terminals of line\_1\_to\_2 and line\_1\_to\_3 on bus 1.
* Enable Generation operation and set Control type to External for both CBs.
* Use a Constant (1), a Pulse Delay (Td = 3.1 s, Ton = 1e9 s), a Gain of 7 (111 in binary for three phases), and a NOT gate to generate trip commands and connect the signals to both CBs.

Before running the simulation, enable “Perform load flow and set initial conditions at simulation start” in the general simulation settings.

## Recording with Datalogger

Set the HYPERSIM time step to 5 μs. Use the [Datalogger](https://opal-rt.atlassian.net/wiki/spaces/HDI/pages/3548177/Datalogger) to record selected sensors from t = 0 s to t = 15 s with decimation = 1. For chosen signal groups, set number of frames = 1 and frame length = 15 s, and disable output file autonaming. Additional sensors can be configured per [Sensor Management](broken://pages/3ad65ddf9fc914e2b6436095a544b15a8d791354).

The supplied [ScopeView](https://opal-rt.atlassian.net/wiki/spaces/PSV) template `PSSE_Import_118_Bus.svt` compares PSS®E and HYPERSIM recordings. Replace the source files before playback. PSS®E results for this case are provided in `Reports_SC_PSSe.csv`. For new cases (e.g., a different fault location), replace the PSS®E results in the template accordingly. HYPERSIM recordings are saved as `.oprec` files in the `Recordings` folder under `PSSE_Import_118_Bus_hyp` after running the model.

## Simulation and results

### Load flow test

Before dynamic validation, perform a load flow. In HYPERSIM, use the Load Flow tool in the Network section of the HYPERSIM ribbon. For consistency with PSS®E, enable “Use Qmin and Qmax limits” and set: Frequency (Hz) = 60.0, Power base (MVA) = 100.0, PQ tolerance (WA) = 0.001, Max iterations = 60. Enable “Display voltage in PU” in Reports and run the analysis. The load flow converges and detailed results appear in the log window.

Comparison between HYPERSIM and PSS®E shows:

* Maximum bus voltage error ≈ 0.00102 pu
* Maximum bus angle error ≈ 0.131 degrees
* Maximum generator active power error ≈ 0.01178 pu
* Maximum generator reactive power error ≈ 0.0139 pu

These differences are small and acceptable, confirming close agreement.

### Dynamic test

The three-phase fault at bus 1 (t = 3 s to 3.1 s) is applied and cleared by tripping the lines connected to bus 1 in both PSS®E and HYPERSIM (implemented manually in HYPERSIM). The comparison shows good alignment across bus voltages, line active/reactive power flows (e.g., line\_2\_to\_12, line\_3\_to\_5, line\_3\_to\_12), and generator outputs (e.g., generators at buses 10 and 12). Minor transient differences are expected due to:

1. Electromagnetic transient simulation in HYPERSIM includes DC fault current components, unlike PSS®E phasor simulation.
2. Different saturation modeling: quadratic in PSS®E versus linear interpolation in HYPERSIM.
3. HYPERSIM positive-sequence calculations use instantaneous values over a one-cycle moving window, introducing slight measurement delay.
4. HYPERSIM circuit breakers open at current zero crossings, affecting clearing and pole opening timing.

## References

\[1] ePHASORsim example model phasor06\_IEEE118, “Islanding of power grid in presence of large disturbances”.

\[2] <http://publish.illinois.edu/smartergrid/ieee-118-bus-system/>

\[3] PSS®E 35.1.0 Program Application Guide Volume 2.

Document generated by Confluence on Dec 15, 2025 14:24

[Atlassian](http://www.atlassian.com/)


---

# 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/examples/how-to/psse-import-ieee-118-bus-system.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.
