> 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/configure-a-baseline.md).

# Configure a Baseline

Configure a saved baseline's target offset, trend treatment, aggregation timeframe, and comment. These settings apply to the selected baseline, not every baseline in the B\&T config.

First [-> create a baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/create-a-baseline.md), using fixed dates, a moving period, or automatic detection.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-4b65357c3b2bc10de1d37d7835955cb82e09b0bd%2Fbenchmark-targets-configure.png?alt=media" alt="General settings for a selected baseline showing Offset, Slope mode, Timeframe, Comment, and Save Configuration"><figcaption><p>Fig. 3: Baseline period and general settings</p></figcaption></figure>

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 **Configure target** for the required B\&T config.
3. Select the required saved baseline in the left pane.
4. Select **General**.
5. Select **Offset** **\[C]**.
6. Enter **Percentage** if you selected **Fixed** or **Gradual**.\
   ◈ Use a value from 0 to 100.
7. Select the offset's start date if you selected **Fixed** or **Gradual**.
8. Select the offset's end date if you selected **Gradual**.\
   ◈ The end date must be later than the start date.
9. Select **Slope mode**.
10. Select **Timeframe**.
11. Enter a **Comment** if you want to describe the baseline or its settings.
12. Click **Save Configuration** **\[D]**.\
    ▷ The selected baseline's settings are saved.

{% hint style="info" %}
Changing **Offset** resets the offset inputs and restores the form's default slope mode and timeframe. Check those fields again before saving.
{% endhint %}

## Offset

An offset turns the modelled operating pattern into a lower allowance. Choose the option according to whether you are monitoring normal operation or measuring progress towards an improvement goal.

### None: monitor against expected operation

Select **None** when you want to compare measurements with the fitted model without adding a reduction goal. This is useful for detecting unusual consumption or checking whether operation has changed since the reference period.

For an energy-consumption target, a positive difference means more energy was used than the model allowed; a negative difference means less. It is a reason to investigate, not proof of a fault or saving.

### Fixed: apply a reduction from a specific date

Select **Fixed** when the full improvement is expected from a known date, such as after commissioning an efficiency measure. A 10% offset makes the target 90% of the fitted model from the offset's start date onward. Before that date, no percentage reduction applies.

Use this to check whether an intervention delivers the intended reduction. A positive difference now means the measurement is above the reduced target, even if it is already below the original model.

### Gradual: track a progressive improvement

Select **Gradual** when improvement is expected over time, such as a programme of HVAC adjustments across a year. The reduction starts at zero on the start date, increases evenly to the selected percentage on the end date, and remains at that percentage afterward.

For a 10% energy-reduction goal, the allowance is 100% of the fitted model at the start, 95% halfway through the offset period, and 90% at its end. Use **Usage vs target** to see whether actual consumption keeps pace with this changing allowance.

The target is a progressively reduced model, not a straight line through the consumption chart. Weather, calendar patterns, and selected feature inputs can still make the target rise or fall from one interval to the next.

## Percentage

**Percentage** is the intended reduction from the fitted model, not an alarm threshold or the percentage difference reported in Analytics. Enter a value from 0 to 100 when **Fixed** or **Gradual** is selected.

Choose the value from your approved improvement goal. For example, enter **10** for a 10% reduction, not **90**. A value of 0 adds no reduction; 100 reduces the calculated allowance to zero, which makes relative-percentage comparisons unsuitable. Review the target and absolute difference rather than treating a percentage near a zero target as meaningful.

## Offset start and end dates

The start date controls when the reduction begins. Use the commissioning date for an immediately effective measure, or the start of an improvement programme for a gradual target. **Gradual** also needs an end date later than its start date; this is when the full reduction should be achieved.

These dates do not select the historical data used to fit the model. The baseline's reference period does that. Keep the reference representative of the operation you want to compare against, rather than moving it forward simply to make an improvement target easier to meet.

## Slope mode

Slope mode determines how an existing trend in the reference period influences the model. First [-> review the target charts](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/review-a-target.md#read-the-charts): a reference period with little unexplained drift is usually easier to interpret.

### Standard: retain the fitted model

Select **Standard** for a representative reference period when you do not want an additional trend adjustment. This is a useful starting point for evaluating normal operation and comparing performance before and after a change.

Check whether differences are broadly balanced within the reference period. A persistent slope there can indicate that the period mixes changing operating conditions or that relevant influences are missing.

### Extend: continue an existing trend

Select **Extend** when the baseline's existing trend is expected to continue and you deliberately want the target to follow it. The calculation extends the trend in the differences between measurements and the fitted model into the target.

For example, a known gradual increase in operating demand may be part of the expected comparison. Do not use this option merely to hide increasing energy use: extending an unwanted deterioration into the target can make that deterioration appear normal.

### Adjust: remove a trend before fitting

Select **Adjust** when you need a model fitted to reference data with its measured trend removed, rather than carrying that trend into the comparison. This can help when you want to assess deviations separately from a trend already present in the baseline.

Review the result carefully. Removing a trend is not the same as explaining its cause; choosing a more stable reference period or adding a relevant feature attribute may produce a more meaningful comparison.

## Timeframe

**Timeframe** sets the aggregation interval used to calculate the target. Choose **15 minutes**, **Hour**, **Day**, **Week**, or **Month** according to the behaviour you want to evaluate and the available source history.

* Use shorter intervals to inspect operating cycles or intraday departures, provided the source data is sufficiently frequent and complete. These comparisons expose more short-term variation.
* Use **Day** to review daily building consumption and recurring operating patterns.
* Use **Week** or **Month** to assess broader performance trends. Aggregation can make long-term comparisons easier to read, but can conceal short-lived excursions.

Match any absolute-deviation alarm threshold to the selected timeframe and source unit. An excess over an hour is not equivalent to the same numerical excess over a month. This calculation setting is separate from the display interval you later select in Insight Analytics.

## Comment

Use **Comment** to record why the reference and settings were chosen. For example, record that the baseline represents operation before a plant replacement, or that the gradual offset tracks a 10% reduction programme. This context helps other users interpret the baseline and select the right row in Analytics.

## Change the reference period

Use a different reference period when the current period is incomplete, unrepresentative, or spans an operating change. Changing the reference changes what counts as expected operation; it is not a substitute for explaining an unexpected result.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-18753fb6deb4cec399dc141068c9239060c5538c%2Fbenchmark-targets-correlation-period.png?alt=media" alt="Open Correlation period view with source history, baseline segments, fixed-period boundary handles, and Save target"><figcaption><p>Fig. 8: Source history and selectable correlation periods</p></figcaption></figure>

1. Select the required saved baseline in the left pane.
2. Select **Correlation period** **\[A]**.
3. Select the required segment **\[B]** to see its position in the source history.
4. Update its reference-period fields as described in [-> Create a Baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/create-a-baseline.md), or drag a fixed period's boundary handle **\[C]**.\
   ◈ Fixed baselines use **From** and **To**; moving baselines use **Offset days** and **Baseline length**.
5. Click **Save target** **\[D]**.\
   ▷ The selected baseline's reference period is saved.

**Apply** persists the date range while keeping range editing open. **Reset** restores the selected baseline's saved range values; it does not undo a range already saved with **Apply**.

Saving settings does not activate a paused baseline. Changes to an active baseline are recalculated in the background, so its generated values may take time to update.

Next, [-> review the B\&T config's selected baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/review-a-target.md) and [-> activate the baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/activate-or-pause-a-baseline.md) when it is ready.


---

# 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/configure-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.
