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

# HVAC 230kV 16Bus

## Description

The **HVAC 230kV 16Bus** example, located in **File > Open an Example File > Benchmarks**, evaluates electromagnetic transient overvoltages caused by line switching, fault initiation, and clearing, and demonstrates testing of protection relays interfaced with the simulator through digital-to-analog converters and power amplifiers or via the IEC 61850 Ethernet communication protocol with model relays.

The benchmark includes three synchronous machines with built-in voltage and speed regulators and stabilizers, two voltage sources, four two-winding transformers, ten constant-parameter lines, and four loads operating at 13.8 kV, 110 kV, and 230 kV. Various fault types can be applied at different locations; the included scenario applies a three-phase fault at Bus 5.1.

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

## Requirements

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

## Detailed explanation

The model is structured to support transient studies and relay testing in a multi-voltage network:

* Generation system: three synchronous machines with internal exciters, governors (speed regulators), and stabilizers.
* Network equipment: two voltage sources, four two-winding transformers, ten constant-parameter transmission lines, and four loads.
* Operating voltages: 13.8 kV, 110 kV, and 230 kV.
* Fault capability: single-line-to-ground, three-phase, and two-phase-to-ground faults can be introduced at different locations. The example scenario places a three-phase fault on Bus 5.1.

Machine control configuration can be modified by double-clicking the machine subsystem and editing the parameters in the mask.

## Simulation and results

The example includes one scenario with a ready-to-use ScopeView template to display key signals.

A three-phase fault is applied on Bus 5.1 starting at 0.1 s and lasting 0.1 s. You can adjust the timing in the fault subsystem by editing T1 (activation time) and T2 (clear time).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2d5cf12285f666386dc205a7f367f268e0cba91e%2FHVAC_230_16bus_param_simul.png?alt=media" alt="" width="563"><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-290a3e730b7a9aac74c4072de15c0d4deaff4acc%2FHVAC_230_16bus_simul1.png?alt=media" alt=""><figcaption><p>Three-phase voltage on buses 4 and 5 of the 16-Bus model with a three-phase to ground fault at Bus 5.1.</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-52bacfbcb8e10a9aeaf1c4cc1aa4058b559a0a81%2FHVAC_230_16bus_simul2.png?alt=media" alt=""><figcaption><p>Machine speed and voltages with three-phase to ground fault at Bus 5.1.</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-16bus.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.
