> 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/benchmarks/hvac-230kv-86bus.md).

# HVAC 230kV 86Bus

## Description

The **HVAC 230 kV 86-Bus** example, located in **File > Open an Example File > Benchmarks**, is a 60 Hz, 138/230 kV HVAC transmission system model of an 86-bus network.

The main objective of this example is to demonstrate how to configure and analyze three-phase faults at different buses, and to observe resulting bus voltages and fault currents across the network.

The network includes 86 transmission lines supplying a total of 23 loads, each rated at 413 MVA (403 MW, 91 MVAR). Nine ideal voltage sources with lumped equivalent impedance represent the generators; full machine dynamics can be added if needed. Long lines use distributed-parameter models, while shorter lines use PI sections. Specifically, the model contains 60 three-phase PI-section lines with self and mutual impedance representation and 26 distributed-parameter lines. All line sections 20 km and shorter are modeled using PI sections. The model supports insertion of single-line-to-ground, three-phase, and two-phase-to-ground faults at different locations. In this example, three three-phase faults are configured at Buses 5, 17, and 27; their activation and clearing times can be modified, and additional faults can be added.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d99d2773149f7f903769027425313805a15b6e24%2Fimage%20(1314).png?alt=media" alt=""><figcaption></figcaption></figure>

## Requirements

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

## Detailed explanation

### Network configuration

* Frequency and voltage levels: 60 Hz, 138/230 kV HVAC
* Buses and lines: 86 buses and 86 transmission lines
* Loads: 23 loads, each rated at 413 MVA (403 MW, 91 MVAR)
* Sources: Nine ideal voltage sources with lumped equivalent impedance (generators)
* Line models: 60 three-phase PI-section lines with self and mutual impedance; 26 distributed-parameter lines
* Modeling guideline: Lines of 20 km and shorter use PI sections; longer lines use distributed parameters

### Fault configuration

* Fault types supported: single-line-to-ground, three-phase, and two-phase-to-ground
* Predefined faults: three-phase to-ground faults at Buses 5, 17, and 27
* Timing parameters: within each fault subsystem (Fault1, Fault2, Fault3), set T1 for activation time and T2 for clearing time
* Default timing: activate at 0.1 s and clear 0.05 s later
* Default enable state: only Fault1 is enabled by default; Fault2 and Fault3 are disabled

### To adjust a scenario

* Open the corresponding fault subsystem (Fault1, Fault2, or Fault3)
* Set T1 (activation) and T2 (clearing) as required
* Enable the intended fault and disable the others to run a single-fault scenario

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1e738d9d77c46a84a06f0d49b043429d101ea2a4%2Fimage%20(1296).png?alt=media" alt=""><figcaption></figcaption></figure>

## Simulation and results

You can run the three predefined scenarios independently by enabling one fault at a time and disabling the others. Results can be viewed in ScopeView.

### Scenario 1: Three-phase fault on Bus 5

Enable Fault1 (Bus 5) and disable Fault2 and Fault3. By default, this is the active scenario. The fault activates at 0.1 s and clears 0.05 s later.

Observe the bus voltage dip during the fault, the corresponding fault current, and recovery after clearing.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6e9bd2493f95f61d0943f2037b26465a7a7e4676%2Fimage%20(1315).png?alt=media" alt=""><figcaption><p>Bus Voltage and Fault current with a three-phase to-ground fault at Bus 5</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-87c2f13225cd649bf4f7ad7fee9aec594bf1c9fe%2Fimage%20(1317).png?alt=media" alt=""><figcaption><p>Voltage of some buses with a three-phase to-ground fault at Bus 5</p></figcaption></figure>

### Scenario 2: Three-phase fault on Bus 17

Enable Fault2 (Bus 17) and disable Fault1 and Fault3. The default timing is activation at 0.1 s and clearing 0.05 s later.

Monitor Bus 5 and other buses to compare network response relative to Scenario 1.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a0b1e4351c4dd5ab5e53bca6c9d7d28777e0a6bb%2Fimage%20(1318).png?alt=media" alt=""><figcaption><p>Bus Voltage and Fault current on Bus 5 with a three-phase to-ground fault at Bus 17</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-79b1eb3dbc38ab574a76c83e892fc0fb904ac90f%2Fimage%20(1316).png?alt=media" alt=""><figcaption><p>Voltage of some buses with a three-phase to-ground fault at Bus 17</p></figcaption></figure>

### Scenario 3: Three-phase fault on Bus 27

Enable Fault3 (Bus 27) and disable Fault1 and Fault2. The default timing is activation at 0.1 s and clearing 0.05 s later.

Review bus voltages and fault currents to assess how the fault location affects the wider network.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-1bdedb43be4cc8d85ef445507ec1e58c646aa5c3%2Fimage%20(1319).png?alt=media" alt=""><figcaption><p>Bus Voltage and Fault current on Bus 5 with a three-phase to-ground fault at Bus 27</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7173c57766c8ac6da2da1a540cdc3d21cbd4ccba%2Fimage%20(1320).png?alt=media" alt=""><figcaption><p>Voltage of some buses with a three-phase to-ground fault at Bus 17</p></figcaption></figure>


---

# 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/benchmarks/hvac-230kv-86bus.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.
