> 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/introduction-to-industrial-loads.md).

# Introduction to Industrial Loads

## Description

The **Industrial Loads Introduction** example, located in **File > Open an Example File > Distribution and Industrial Power Systems**, demonstrates three common industrial load representations: dynamic load, harmonic load, and AC arc furnace.

The main objective is to illustrate how these load types can be modeled and simulated to observe their electrical behavior.

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

## Requirements

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

## Detailed explanation

This example includes the following configurations:

* Dynamic Load
* Harmonic Load
* AC Arc Furnace

Each configuration is intended to be simulated to observe its characteristic electrical response.

## Simulation and results

The example provides simulation results for each configuration:

* Dynamic Load
* Harmonic Load
* AC Arc Furnace

The associated figures illustrate representative waveforms and behaviors for each load type.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ab394bd529b376f076ce3279df43f633b0c17752%2Fimage%20(1471).png?alt=media" alt=""><figcaption><p>Dynamic load</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-38dc4938a996600c2a0728464aa4ba0810790bfd%2Fimage%20(1472).png?alt=media" alt=""><figcaption><p>Harmonic load</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-70ea380c9b506bca39f28c8be9e125cf9162b5eb%2Fimage%20(1473).png?alt=media" alt=""><figcaption><p>AC arc Furnace</p></figcaption></figure>

## References

\[1] 2017 Microgrid Controller Procurement Information Packet Volume 1.6, P. Koralewicz, ed.: NREL, 2017. \[Online].

\[2] R. Salcedo et al., "Banshee distribution network benchmark and prototyping platform for hardware-in-the-loop integration of microgrid and device controllers," in The Journal of Engineering, vol. 2019, no. 8, pp. 5365-5373, 8 2019.


---

# 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/introduction-to-industrial-loads.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.
