> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/apps/apps/forecast/neue-vorhersage-erstellen.md).

# Create a new forecast

## Forecast Overview

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/C0FIOVs4x67lvfeWhsV3/forecast%20app%20(1).png" alt=""><figcaption></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="98.60000610351562">Icon</th><th width="247">Label</th><th>Description</th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Add forecast</td><td>Opens a form for creating a new forecast configuration.</td></tr><tr><td><strong>[B]</strong></td><td>Restart app</td><td>Starts the <em>Forecast app</em> again, e.g. after changes to a configuration.</td></tr><tr><td><strong>[C]</strong></td><td>Uninstall app</td><td>Removes the <em>Forecast app</em> completely from the project.</td></tr><tr><td><strong>[D]</strong></td><td>Start/Pause forecast</td><td>Starts or stops the prediction.</td></tr><tr><td><strong>[E]</strong></td><td>Forecast status</td><td>Shows whether the prediction is currently active or inactive.</td></tr><tr><td><strong>[F]</strong></td><td>Asset-GAI</td><td>The <em>Global Asset Identifier</em> of the assigned asset.</td></tr><tr><td><strong>[G]</strong></td><td>Forecast length</td><td>Specifies how many steps into the future are predicted.</td></tr><tr><td><strong>[H]</strong></td><td>Context length</td><td>Number of historical values used for the forecast calculation.</td></tr><tr><td><strong>[I]</strong></td><td>target attribute</td><td>The asset attribute that is predicted (e.g. <em>temperature</em>).</td></tr><tr><td><strong>[J]</strong></td><td>Remove configuration</td><td>Deletes the individual forecast configuration.</td></tr><tr><td><strong>[K]</strong></td><td>More options</td><td>Opens a context menu with additional editing options. <a href="/collection/english-v14/apps/apps/forecast/forecast-and-training-starten.md">→ Forecast Details</a></td></tr></tbody></table>

## Create new forecast

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/FBltrYB5ZOdRn6CT0qGr/forecast%20app%20(3).png" alt=""><figcaption></figcaption></figure>

1. Click on **\[A] Add forecast**.\
   ▷ The form *Add Forecast* opens.
2. Select in the field **\[A1] Select asset** the desired asset whose attribute you want to predict.
3. Select in the field **\[A2] Target attribute** the attribute to be forecast.
4. Select in the field **\[A3] Input attribute** in *Feature attribute* out.\
   ◈ *Feature attributes* are supporting input variables that improve the model when calculating the forecast.
5. If necessary, add via **\[A5] Add attribute** additional *Feature attributes* or remove existing entries via **\[A4] Remove attribute**.
6. Enter in the field **\[A6] Forecast length** the number of forecast steps.\
   ◈ This determines how far into the future the forecast extends (e.g. 12 time units).
7. Enter in the field **\[A7] Context length** enter the number of historical data points the model should use for the calculation.
8. Click on **\[A8] Save**, to create the new forecast.\
   ▷ The configuration is saved and appears in the list.


---

# 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://docs.buildings.ability.abb/collection/english-v14/apps/apps/forecast/neue-vorhersage-erstellen.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.
