> 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/create-a-target.md).

# Create a B\&T Config

Create a [-> B\&T config](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets.md#targets-and-baselines) to select the asset attribute you want to compare with a historical baseline. You can also select contextual inputs, such as outside temperature or occupancy.

First [-> 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). Ensure that the source attribute and any feature attributes have historical values for the period you plan to use.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-aea47abe941add6794eb3941d3fa70469925bd5b%2Fbenchmark-targets-create.png?alt=media" alt="New B&#x26;T config form with source asset, Target attribute, optional feature attributes, and Save and continue"><figcaption><p>Fig. 2: Create a B&#x26;T config</p></figcaption></figure>

1. Click **Add Target** in the B\&T config list.\
   ▷ The **Target and baseline** form opens.
2. Select the source **Asset** **\[A]**.\
   ▷ **Target attribute** becomes available.
3. Select the measured source attribute in **Target attribute** **\[B]**.
4. Select a feature asset under **Feature attributes**, if you want to use an additional modelling input.\
   ◈ Leave the feature fields empty if no additional inputs are required.
5. Select that asset's feature attribute **\[C]**, if you selected a feature asset.
6. Click **Add additional feature attribute** **\[D]** if you need another input.\
   ◈ Complete both the asset and attribute selection for each additional input.
7. Click **Save and continue** **\[E]**.\
   ▷ The B\&T config is saved and **Target Line Settings** opens.

## Choose useful feature attributes

Feature attributes help the model account for influences on the measured value. For example, outdoor temperature can help distinguish weather-related heating demand from a change in operating efficiency, and occupancy can help distinguish changes in use from unexplained consumption.

Choose inputs that are relevant to the building and have usable history over the reference and comparison periods. Adding an input does not guarantee a better model; [-> review the target preview and metrics](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/review-a-target.md) to check whether the resulting comparison is credible.

Next, [-> create a baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/create-a-baseline.md), choosing fixed dates, a moving reference, or automatic detection. Creating the B\&T config alone does not start baseline processing.


---

# 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/create-a-target.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.
