> 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/view-a-target-in-insight-analytics.md).

# View a B\&T Config in Insight Analytics

Compare actual values with a selected baseline's generated target values in [-> Insight Analytics](https://docs.buildings.ability.abb/collection/platform/insight-analytics.md). You need a [-> saved B\&T config](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/create-a-target.md) and at least one [-> active baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/activate-or-pause-a-baseline.md).

{% hint style="info" %}
Generated history may not be available immediately after activation or a settings change because calculations run in the background. Paused baselines are not offered in the analytics baseline selector.
{% endhint %}

<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="B&#x26;T config list with Open target marked at the right of the config header"><figcaption><p>Fig. 1: B&#x26;T configs and baseline controls</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 **Open target** **\[E]** for the required B\&T config.\
   ▷ Insight Analytics opens with the source asset and attribute.
3. Select the required **Analytics type** **\[A]** from the Benchmark and Targets options illustrated below.
4. Select **Y** **\[B]** to display a year.
5. Use the date controls to select a year with generated target history.
6. Select **Baselines** **\[C]**.
7. Select the required active baseline row **\[D]**.\
   ▷ The analytic uses the generated attributes for that baseline.

References **\[A]** to **\[D]** correspond to the analytics figures below, not the B\&T config list figure. Each analytics figure uses the same letters for the analytic type, Year range, Baselines tab, and selected baseline row.

The **Baselines** table identifies each active baseline by its time range, offset, slope mode, timeframe, comment, and percentage deviation. Selecting a different row changes the baseline used by the analytic.

The examples below show populated data for 2025. Choose a year that contains data for your B\&T config. **Function** and **Interval** determine how the generated values are aggregated for display.

## Usage vs target

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-0b9ccf5241029770823d210854b2b2997541492c%2Fbenchmark-targets-usage-vs-target.png?alt=media" alt="Usage vs target analytic for 2025 showing measured usage below the selected active baseline&#x27;s target, with the Baselines table open"><figcaption><p>Fig. 9: Year view of measured usage and target values</p></figcaption></figure>

Select **Usage vs target** at **\[A]** to compare the original measured values with the selected baseline's target values. The example uses a line graph with **Sum counter** and **Day** intervals. Hover over the chart to compare the displayed series at a particular date.

Use this view to answer, "Are we operating as expected, or meeting the intended reduction?" Measured consumption above the target is above the selected allowance; consumption below it is below the allowance. When the curves separate, check whether the gap is occasional, seasonal, or sustained.

An upward or downward consumption trend alone does not establish deterioration or improvement. The target can also change with the modelled operating conditions. For a **Gradual** reduction target, compare measurements with the progressively reduced allowance rather than expecting both curves to fall continuously. A falling measured curve can still miss a target that is reducing faster.

## Overspend

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-b4b1f659944facfbe5955acc16b6a9cd6a8e2442%2Fbenchmark-targets-overspend.png?alt=media" alt="Overspend analytic for 2025 with negative monthly bars and the selected active baseline highlighted in the Baselines table"><figcaption><p>Fig. 10: Year view of actual-minus-target differences</p></figcaption></figure>

Select **Overspend** at **\[A]** to inspect actual-minus-target differences. Positive values are above target; negative values are below target. The example uses a bar graph with **Sum counter** and **Month** intervals, and all displayed bars are below zero. These values are differences in the attribute's values, not automatically monetary costs.

Use this view to locate and quantify periods that contribute most to a missed target. For an energy-reduction goal, positive bars show an excess against the allowance; negative bars show use below it. Increasing positive bars indicate a growing absolute gap. Negative bars moving towards zero indicate a shrinking margin, even though consumption remains below target.

Compare like-for-like periods and intervals. A larger monthly difference than a daily difference is not, by itself, evidence of worse operation. The generated absolute difference can also be used in a rule alarm when an excess in the source unit is more useful than a relative percentage.

## Overspend CUSUM

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-fc762f655dad2fa1fe3b72bcee618f9f698cd49e%2Fbenchmark-targets-overspend-cusum.png?alt=media" alt="Overspend CUSUM analytic for 2025 showing a falling cumulative-difference curve with the selected active baseline highlighted"><figcaption><p>Fig. 11: Year view of cumulative differences</p></figcaption></figure>

Select **Overspend CUSUM** at **\[A]** to inspect the cumulative sum of actual-minus-target differences. A rising curve accumulates positive differences; a falling curve accumulates negative differences. In this example, negative differences continue to accumulate throughout the year.

The example uses **Average** with **Day** intervals to display the cumulative series. Its values are already cumulative totals, not independent increments to add together again.

Use this view to see whether many small differences add up to a lasting performance gap. An upward slope means new above-target differences are accumulating; a downward slope means below-target differences are accumulating. A nearly horizontal section means little net new difference is being added. A steeper slope indicates a larger ongoing imbalance, and a change of slope can help you see when performance changed.

Read the slope separately from the curve's height. A high curve that becomes flat may indicate that a problem has stopped adding further excess, not that the historical excess has been recovered. For an energy-reduction goal, a sustained downward slope generally indicates use below the selected allowance; for another kind of measured attribute, decide whether below-target operation is desirable before calling it an improvement.

## Percentage difference

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-db219c64c0a3c30bedeb54cfb642be8fa49f495b%2Fbenchmark-targets-percentage-difference.png?alt=media" alt="Percentage difference analytic for 2025 showing negative percentage deviations and the selected active baseline in the Baselines table"><figcaption><p>Fig. 12: Year view of percentage deviation</p></figcaption></figure>

Select **Percentage difference** at **\[A]** to inspect percentage deviation calculated from moving averages of actual and target values. Negative values indicate usage below target; positive values indicate usage above target. This is not the percentage difference for each individual observation.

The example uses **Average** with **Day** intervals. Adding percentage samples together does not produce a meaningful overall percentage deviation.

Use this view to judge the relative size of a sustained departure, rather than only its absolute size. Zero means the smoothed measured value matches the smoothed target. Positive values are above the selected target; negative values are below it. A rising line means the relative position is moving upwards, not necessarily that a target has already been exceeded: -20% rising to -5% remains below target, but the margin is shrinking. A fall from +20% to +5% moves closer to the target while still remaining above it.

### Interpret the percentage against the configured baseline

* With **Offset: None**, the percentage compares operation with the modelled reference. For energy use, a sustained positive value can indicate higher consumption than the reference model expects; a negative value can indicate lower consumption. Investigate whether the cause is efficiency, changed use, missing inputs, or data quality.
* With a **Fixed** offset, zero means meeting the reduced allowance once the offset applies, not merely matching the original reference. For example, if the smoothed original model is 100 and a fully applied 10% offset makes the target 90, a smoothed measurement of 95 is about 5.6% above target, despite being 5% below the original model.
* With a **Gradual** offset, the percentage compares operation with the reduction required at that point in the offset period. A positive value means the progressive target is being missed; a negative value means consumption is below the current allowance. Check the offset's dates and percentage before comparing different parts of the year.
* With a **Moving baseline**, the reference advances with time. A percentage returning towards zero may mean the reference has adapted, not that long-term performance has returned to its old level. Compare with a fixed baseline when you need to assess lasting drift or savings.

Treat percentage comparisons cautiously when the target is zero or very close to zero. Review the absolute difference and the underlying measurements instead of interpreting the percentage as a reliable performance indicator.

### Use deviations for operational alarms

After [-> activating the baseline](https://docs.buildings.ability.abb/collection/platform/platform-core/baseline-and-factors/portfolio-benchmark-and-targets/activate-or-pause-a-baseline.md), use its generated absolute difference or percentage-difference attribute as the input to a [-> rule](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rules/create-a-rule.md). For example, monitor an above-target energy excess in the source unit, or a sustained relative departure from recent operation with a moving baseline.

Choose the rule's direction and threshold according to the purpose of the B\&T config. A below-target value can be desirable for energy consumption but undesirable for an output that should remain high. The percentage comparison is smoothed; it will not represent every short spike. Recheck the rule when you change the reference period, offset, or timeframe, because those settings change the comparison.

If no baseline is available, confirm that the source asset and attribute match the B\&T config and that the required baseline is active. If a chart is empty, choose a year with available source and generated history and allow background calculations to finish. If B\&T configs cannot be loaded, resolve the displayed loading error before retrying.


---

# 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/view-a-target-in-insight-analytics.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.
