> 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/delete-baselines-and-targets.md).

# Delete Baselines and B\&T Configs

Delete an individual baseline when you no longer need its reference period and settings. Delete a B\&T config when you no longer need its asset-attribute configuration or any of its baselines.

{% hint style="warning" %}
Before deleting, check rules, rule chains, dashboard widgets and analytics that depend on the generated attributes. Deletion starts background cleanup of generated values and history that no active baseline still uses on the source asset. These consumers can lose their data; their references do not prevent cleanup.
{% endhint %}

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-249d203d07346c8243df3b70810efb7fd5643c06%2Fbenchmark-targets-delete-controls.png?alt=media" alt="Expanded B&#x26;T config list with the whole-config trash icon marked A and an individual baseline&#x27;s trash icon marked B"><figcaption><p>Fig. 14: Delete controls for a B&#x26;T config and an individual baseline</p></figcaption></figure>

## Delete a baseline

Deleting one baseline leaves the B\&T config and its other baselines available.

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 trash icon **\[B]** at the far right of the required baseline row.\
   ▷ A deletion confirmation opens.\
   ◈ Use the baseline row's icon **\[B]**, not the B\&T config header's icon **\[A]**.
4. Confirm the deletion.\
   ▷ The baseline is removed from the B\&T config's baseline list. Generated-data cleanup continues in the background.

## Delete a B\&T config <a href="#delete-a-target" id="delete-a-target"></a>

Deleting a B\&T config removes its configuration and all of its baselines. To keep the B\&T config and remove only one reference period, use [-> Delete a baseline](#delete-a-baseline) instead.

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. Click the B\&T config's trash icon **\[A]** beside **Configure target**.\
   ▷ A deletion confirmation opens.\
   ◈ The baseline-row icon **\[B]** deletes only one baseline, not the whole B\&T config.
3. Confirm the deletion.\
   ▷ The B\&T config is removed from the list. Generated-data cleanup continues in the background.

## What happens to generated attributes

Deleting a baseline or B\&T config does not delete the original source measurements. Background cleanup removes generated current values and trend history that no active baseline still owns on the affected asset.

An attribute definition can remain visible after deletion because it belongs to the shared asset type (template), not only to the deleted baseline. Another active baseline, including one on a different asset, can still use the same source attribute, subtype and output schema number for that asset type. Its generated attributes and data must remain available.

A remaining definition does not mean that the deleted baseline is still active or that its generated history is preserved. See [-> generated asset attributes](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets.md#generated-asset-attributes) for the exact names, where they are added, and an example of shared definitions.


---

# 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/delete-baselines-and-targets.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.
