> 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-96bus-86line.md).

# HVAC 230kV 96Bus 86Line

## Description

The **HVAC 138/230 kV 86‑Bus Network** example, located in **File > Open an Example File > Benchmarks**, models a 60 Hz transmission system with mixed line representations.

The objective is to demonstrate network modeling using distributed-parameter and PI-section lines and to evaluate system behavior under three-phase and other fault conditions.

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

## Requirements

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

## Detailed explanation

This model represents an 86-bus, 138/230 kV HVAC transmission network with the following characteristics:

* 86 transmission lines supplying 23 loads, each rated at 413 MVA (403 MW, 91 MVAR).
* Nine ideal voltage sources with lumped equivalent impedances representing generators; full machine dynamics can be added if needed.
* Line modeling:
  * 60 three-phase PI-section lines with self and mutual impedance representation.
  * 26 distributed-parameter lines for long transmission segments.
  * All line sections 20 km and shorter are modeled using PI sections.
* Fault studies:
  * Supports single-line-to-ground, three-phase, and two-phase-to-ground faults at multiple locations.
  * This example includes three predefined three-phase faults at Buses 5, 17, and 27.
  * Fault timing is configured in the fault subsystems using:
    * T1: activation time.
    * T2: clearing time (fault clears T2 seconds after T1).
  * Enable or disable individual fault subsystems (Fault1, Fault2, Fault3) to run specific scenarios.

## Simulation and results

The model allows enabling or disabling five three-phase faults on different buses. This page presents results for two of the three predefined three-phase faults; each fault is applied independently on a different bus. The remaining three faults can be activated or deactivated using the same procedure.

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

Apply a three-phase fault at Bus 5 with T1 = 0.1 s and T2 = 0.05 s (activated at 0.1 s and cleared 0.05 s later). By default, only this fault is enabled: set Enable = true in the Fault1 subsystem and ensure Fault2 and Fault3 are disabled.

<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><p>Fault configuration settings</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-a0ec3019f5e3cf7c81aa78af0b768addb6724503%2Fimage%20(1349).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-cfb356ab82dde5a087cc54bde26eef9b151f5334%2Fimage%20(1350).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

A second predefined scenario applies a three-phase fault at Bus 17 with the same default timing (T1 = 0.1 s, T2 = 0.05 s). To run only this case, set Enable = true in the Fault2 subsystem and disable Fault1 and Fault3.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-20d1137cc2c9020afedda827935579bb9e601250%2Fimage%20(1351).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-8fe0c45d274cd126bd9568d61b841816828d8c0f%2Fimage%20(1352).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-96bus-86line.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.
