> 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/distribution-and-industrial-power-systems/feeder-25kv-24bus.md).

# Feeder 25kV 24Bus

## Description

The **Feeder\_25kV\_24Bus** example, located in **File > Open an Example File > Distribution and Industrial Power Systems**, models a radial distribution network to study protection, power quality, and load dynamics.

The objective is to evaluate breaker-recloser behavior, the impact of large loads and induction motors, capacitor switching, load unbalance, harmonic phenomena (including resonance), voltage flicker, and the effects of load modeling.

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

## Requirements

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

## Detailed explanation

The network operates in a radial topology and includes the following characteristics:

* Average load: 5000 kW and 800 kVAR.
* Total line length: approximately 36 km; average main line length: about 5.5 km, except for a remote load separated by 46 km.
* Balanced and unbalanced loads, two induction motors, two capacitor banks, and three breaker-reclosers.
* A 100 kW load with characteristic harmonics of a 6-pulse DC-motor drive.
* Loads modeled as voltage dependent; typical exponents for winter load (electric heating): np = 1.7 and nq = 2.6 (see reference).

## Simulation and results

A single-phase fault is applied at L4 on phase A of a three-phase bus from t = 0.1 s to t = 0.2 s. The simulation records voltage and current at the feeder head, at 11 km from the utility, at 24 km from the utility, and at the remote load. It also records the currents of the different motors in the network and the rotor speeds of the two induction motors.

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

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

The following figures display the current at the different motors in the network and also the machine speed for the two induction motors.

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

## References

Load Representation for Dynamic Performance Analysis. IEEE Task Force on Load Representation for Dynamic Performance IEEE Trans. on Power Systems, Vol.8, No.2 , May 1993.


---

# 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/distribution-and-industrial-power-systems/feeder-25kv-24bus.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.
