> 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/library-blocks-reference/control-microgrid/bess-management.md).

# BESS Management

## Description

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

The **BESS Power Reference Compensation** block, located in the **Control Microgrid** library, sums the components of the battery energy storage system (BESS) real power reference: the main real power reference from the real power controller, the point of common coupling (PCC) real power error, load reduction compensation, and a frequency compensation term computed here to help the Diesel Generator maintain microgrid bus frequency in islanded operation. It also sums the reactive power reference components: the reference from the reactive power controller and the PCC reactive power error. This block is part of the OP1420 microgrid library and is intended to be used with the other library blocks.

## Mask parameters

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-cb15c3fadb3a29733379bd4db1261ba56e577a89%2FBESS%20management.jpg?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="General" %}

| Parameter                | Description                                                       |
| ------------------------ | ----------------------------------------------------------------- |
| **Global nominal power** | Nominal power of the microgrid (Unit: W). Default value: 12e3.    |
| **Nominal frequency**    | Nominal frequency of the microgrid (Unit: Hz). Default value: 50. |
| {% endtab %}             |                                                                   |

{% tab title="BESS compensation parameters" %}

| Parameter                                       | Description                                                                                  |
| ----------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **BESS frequency compensation (kW per 0.1 Hz)** | Proportional control factor for BESS frequency compensation (Unit: kW/Hz). Default value: 3. |
| {% endtab %}                                    |                                                                                              |

{% tab title="Dynamic filter" %}

<table><thead><tr><th width="239.39996337890625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Time constant</strong></td><td>Low-pass filter time constant for power measurements (s). Default value: 1.</td></tr><tr><td><strong>Bypass time</strong></td><td>Wait time before bypassing the filter (s). Default value: 5.</td></tr><tr><td><strong>Start of the dead zone</strong></td><td>Dead zone lower limit.<br>Set <strong>Start of the dead zone</strong> less than or equal to <strong>End of the dead zone</strong>. Default value: -2e-3.</td></tr><tr><td><strong>End of the dead zone</strong></td><td>Dead zone upper limit.<br>Set <strong>End of the dead zone</strong> greater than or equal to <strong>Start of the dead zone</strong>. Default value: 2e-3.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## Inputs

<table><thead><tr><th width="259.5999755859375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Frequency</strong></td><td>Measured microgrid frequency (Hz).</td></tr><tr><td><strong>Islanded</strong></td><td>Microgrid operating mode<br>0 = grid-connected, 1 = islanded.</td></tr><tr><td><strong>Total load reduction</strong></td><td>Total load reduction used to adjust the BESS power reference (pu).</td></tr><tr><td><strong>P ref BESS*</strong></td><td>Active power reference from the dispatch controller (pu).</td></tr><tr><td><strong>Q ref BESS*</strong></td><td>Reactive power reference from the dispatch controller (pu).</td></tr><tr><td><strong>P error Grid</strong></td><td>Difference between active power through the PCC and the user demand (pu).</td></tr><tr><td><strong>Q error Grid</strong></td><td>Difference between reactive power through the PCC and the user demand (pu).</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="260.39996337890625">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>P ref BESS</strong></td><td>Active power reference sent to the battery energy storage system (pu).</td></tr><tr><td><strong>Q ref BESS</strong></td><td>Reactive power reference sent to the battery energy storage system (pu).</td></tr></tbody></table>


---

# 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/library-blocks-reference/control-microgrid/bess-management.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.
