> For the complete documentation index, see [llms.txt](https://docs.voltmasters.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltmasters.io/voltmasters-platform/10.-project-settings/10.6-consumption-planning.md).

# Consumption planning

Under **Configuration → Consumption planning**, you can inform the EMS about periods when your expected energy consumption will differ from the automatically predicted value. When the EMS knows in advance that consumption will be higher than usual, it can adjust the battery planning accordingly, for example by building up a larger energy buffer during cheap periods, so that more of the stored energy is available when it is actually needed and less needs to be purchased at higher prices.

{% hint style="info" %}
**kW vs kWh**: Values in this screen are entered in **kW**, which is a measure of **power**, the rate at which energy is used at any given moment. This is different from **kWh**, which measures the total **energy** consumed over a period of time.

**Example**: A process that runs at 50 kW for 2 hours consumes 100 kWh of energy. In this screen, you enter **50 kW** (the power demand during that period) and not the total energy figure.
{% endhint %}

### Entry types

Each entry is either **one-off** or **recurring**:

* **One-off**: applies once, over a fixed start and end date-and-time. Use this for a specific event, such as a production run on a particular afternoon.
* **Recurring**: repeats **every week** on a fixed **day of the week**, between a start and end time. Use this for a regular weekly pattern, such as a shift that runs every Tuesday.

{% hint style="info" %}
When a one-off entry and a recurring entry overlap the same moment, the **one-off entry takes priority**.
{% endhint %}

### How to fill in the consumption planning

Add one entry per planned period. Depending on the entry type, specify:

| Field                | Description                                                                                  |
| -------------------- | -------------------------------------------------------------------------------------------- |
| **Type**             | One-off or recurring                                                                         |
| **Day of the week**  | *(Recurring)* The weekday the entry repeats on                                               |
| **Start / end date** | *(One-off)* The date-and-time the period starts and ends                                     |
| **Start / end time** | The beginning and end of the period                                                          |
| **Amount (kW)**      | The average power demand during this period                                                  |
| **Total (kWh)**      | Calculated automatically from the amount and the duration — shown for reference, not entered |

**Example**: A production run that draws 50 kW on a specific afternoon. Add a **one-off** entry for that date, from 13:00 to 17:00, with an amount of 50 kW. The **Total (kWh)** column then shows 200 kWh (50 kW × 4 h).

### How consumption planning works

During the planned period, the EMS **replaces its standard consumption prediction** with the value you have entered. The battery and other controllable components are prepared in advance to meet the demand, reducing the risk of exceeding the import limit or drawing unnecessary power from the grid at an unfavourable price.

{% hint style="info" %}
Changes to consumption planning entries are recorded in the project [change log](/voltmasters-platform/10.-project-settings/10.4-change-log.md).
{% endhint %}

### How to delete a consumption planning entry

To remove an entry, delete the corresponding row on the consumption planning screen and save. The EMS will revert to its standard consumption forecast for that time period.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.voltmasters.io/voltmasters-platform/10.-project-settings/10.6-consumption-planning.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.