> 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-200bus.md).

# HVAC 500kV 200Bus

## Description

The **HVAC 500 kV 200‑Bus AC Transmission Network** example, located in **File > Open an Example File > Benchmarks**, simulates a 500 kV AC transmission network with 200 buses, 28 hydraulic generation turbine plants, and 60 loads operating at 60 Hz.

The objective is to evaluate network behavior under faults and disturbances, observe electromagnetic transients when machines or lines are lost, and study phenomena such as instability, islanding, and resonances. For this example, two three‑phase faults are configured at Buses 7 and 9, and their timing can be adjusted.

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

## Requirements

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

## Detailed explanation

Each hydraulic plant is modeled as one combined synchronous machine with turbine and governor, excitation system, and power system stabilizer, connected to the grid through a 3‑phase 2‑winding step‑up transformer. All generation machines are controlled by internal exciters, governors (speed regulators), and stabilizers. You can modify a machine’s configuration by double‑clicking its subsystem and editing 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-de83e8352c05a5c635dfc07663328ede5a880046%2Fimage%20(1364).png?alt=media" alt=""><figcaption><p>Synchronous machine configuration settings</p></figcaption></figure>

During simulation, you can introduce different types of faults at various locations, including single‑line‑to‑ground, two‑phase‑to‑ground, and three‑phase faults. In this example, two three‑phase fault subsystems are provided:

* Flt\_B7 (Bus 7)
* Flt\_B9 (Bus 9)

Fault activation and clearing times are set in each fault subsystem using parameters T1 (activation) and T2 (clear). By default, the Bus 7 fault is enabled and the Bus 9 fault is disabled. To run a specific scenario, enable the corresponding fault subsystem and disable the other:

* Scenario 1 (Bus 7): enable Flt\_B7 and disable Flt\_B9.
* Scenario 2 (Bus 9): enable Flt\_B9 and disable Flt\_B7.

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

Default timing for both scenarios is activation at 0.1 s with a duration of 0.1 s (clear at 0.2 s). You can change these times by editing T1 and T2 in the selected fault subsystem.

## Simulation and results

This example provides two three‑phase fault scenarios that can be run individually by enabling the corresponding fault subsystem. Results are plotted in ScopeView.

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

A three‑phase fault is applied on Bus 7 starting at 0.1 s for 0.1 s. By default, only this fault is enabled (Flt\_B7 enabled and Flt\_B9 disabled).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-39522d16cdb7381c8e9951d8e221f391fb72d1cb%2Fimage%20(1371).png?alt=media" alt=""><figcaption><p>Voltage of Buses 7 and 92 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-969673b5644581c5ba8dfeaeda36939ad975e754%2Fimage%20(1372).png?alt=media" alt=""><figcaption><p>Voltage of Bus 7 and primary winding current of transformer 1 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-1d90fd07661982f2b2825e11a9bbc29666e36109%2Fimage%20(1373).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 applied on Bus 9 starting at 0.1 s for 0.1 s. By default, this fault is disabled; to run it, enable Flt\_B9 and disable Flt\_B7.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2d34690737a7021cf2d8d67475489a7bff754981%2Fimage%20(1374).png?alt=media" alt=""><figcaption><p>Voltage of Buses 7 and 92 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-7dcfe61524fd53830ef9c4faa56e6cb601db5893%2Fimage%20(1375).png?alt=media" alt=""><figcaption><p>Voltage of Bus 7 and primary winding current of transformer 1 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-291c233b720b80ccb812355b851151c038fcc4d8%2Fimage%20(1376).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-200bus.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.
