> 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-500kv-35bus.md).

# HVAC 500kV 35Bus

## Description

The **HVAC 500 kV 35‑Bus** example, located in **File > Open an Example File > Benchmarks**, simulates a 500 kV, 60 Hz transmission network with 35 buses, 67 lines, 8 hydraulic generation turbine plants (synchronous machines and regulators), and 15 loads.

The main objective is to analyze electromagnetic transients and system behavior during faults and component outages, including instability, islanding, and resonances. The model supports introducing single-line-to-ground, two-phase-to-ground, and three-phase faults at different locations. By default, two three-phase faults are configured at Buses 7 and 9 with user-adjustable timing.

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

## Requirements

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

## Detailed explanation

All generation machines use internal exciters, governors (speed regulators), and stabilizers. To modify these settings, double-click the machine subsystem and update the parameters in the mask.

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

The model includes two configurable three-phase faults implemented as separate subsystems:

* Fault1 on Bus 7
* Fault2 on Bus 9

Each fault uses parameters T1 and T2 to set the activation and clearing times, respectively. By default, Fault1 is enabled and Fault2 is disabled. To change which fault is active, open the corresponding fault subsystem and adjust the Enable/Disable options and the T1 and T2 values as needed. Additional faults can be added on other buses if required.

## Simulation and results

The example provides one scenario configuration with two optional three-phase faults that can be enabled or disabled as needed. Results are plotted in ScopeView.

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

A three-phase fault is applied on Bus 7 at 0.1 s and cleared 0.1 s later (default settings). Adjust T1 (activation) and T2 (clearing) in the Fault1 subsystem to change timing. By default, enable Fault1 and disable Fault2.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c7ea0fe50f46b7e6a1cbf15e131672b4485973f6%2Fimage%20(1379).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-8fbf20d65c7d933a025c2e1f5db5c244abd55645%2Fimage%20(1380).png?alt=media" alt=""><figcaption><p>Voltage of Bus7 and Fault1 current with a three-phase to ground fault at Bus 7.</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-2d5bfdaedde2adcf4d6d62c1402a50fd9a624b6c%2Fimage%20(1381).png?alt=media" alt=""><figcaption><p>Machine speed and voltages with a three-phase to-ground fault at Bus 7.</p></figcaption></figure>

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

A three-phase fault is available on Bus 9 with default timing identical to Scenario 1 (activate at 0.1 s and clear 0.1 s later). By default, Fault2 is disabled. To run only this fault, enable Fault2 and disable Fault1.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d6e9af7d6d145f675c80c6e445873012236643a8%2Fimage%20(1382).png?alt=media" alt=""><figcaption><p>Voltage of Bus7 and Fault1 current with a three-phase to ground fault at Bus 9.</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-7385f47361e2c494354fa037e91a6324e0b20181%2Fimage%20(1383).png?alt=media" alt=""><figcaption><p>Machine speed and voltages with a three-phase to-ground fault at Bus 9</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-500kv-35bus.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.
