> 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/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/activate-or-pause-a-baseline.md).

# Activate or Pause a Baseline

Activate a saved baseline to generate target and deviation values. Pause it when it should no longer be processed as an active baseline.

First [-> configure the baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/configure-a-baseline.md) and [-> review its preview](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/review-a-target.md). Saving a B\&T config or baseline does not activate the baseline.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-63e68b1dab8f6fb9ca5a980fdac2b00434c9eeb6%2Fbenchmark-targets-list.png?alt=media" alt="Expanded B&#x26;T config showing active baselines with pause icons and a paused baseline with a play icon"><figcaption><p>Fig. 1: B&#x26;T configs and baseline controls</p></figcaption></figure>

## Activate a baseline

1. [-> Open Benchmark and Targets](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/open-benchmark-and-targets.md).
2. Expand the required B\&T config.
3. Click the play icon **\[C]** beside the required paused baseline.\
   ▷ Its status changes to **active**.

Activation creates the [-> generated asset attributes](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets.md#generated-asset-attributes) for target values, differences, percentage differences, and cumulative sums on the source asset. These are normal asset attributes that you can use in rules, rule chains and dashboards. Historical calculations run in the background, followed by processing of newly completed time intervals. An **active** status does not mean that the historical calculation has finished.

Next, [-> view the B\&T config in Insight Analytics](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/view-a-target-in-insight-analytics.md).

## Pause a baseline

{% hint style="warning" %}
Before pausing a baseline or deleting a baseline or B\&T config, check rules, rule chains and dashboard widgets that depend on its generated attributes. Background cleanup removes generated current values and trend history that no active baseline still owns on that asset; shared attribute definitions remain while an active baseline uses the same generated names for that asset type and subtype. References in rules or widgets do not preserve the outputs, so these consumers can lose their data. Do not use pause to preserve generated history. Pausing keeps the baseline configuration, but reactivation can assign a different attribute suffix; recheck dependent selections.
{% endhint %}

1. [-> Open Benchmark and Targets](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/open-benchmark-and-targets.md).
2. Expand the required B\&T config.
3. Click the pause icon beside the active baseline.\
   ▷ Its status changes to **paused** and the play icon becomes available.

Reactivate the saved baseline when you want to generate its values again.

To remove the saved configuration instead, see [-> Delete Baselines and B\&T Configs](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/delete-baselines-and-targets.md).


---

# 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/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/activate-or-pause-a-baseline.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.
