> 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/insight-analytics/analytics-types/sankey-simple-2-layers.md).

# Sankey - Simple 2 layers

Use **Sankey - Simple 2 layers** in [Insight Analytics](https://docs.buildings.ability.abb/collection/platform/insight-analytics.md) to visualize energy flows from selected sources, through one named splitting node, to selected flow targets. The diagram helps you compare the contributions of supply meters and consuming meters over the same period.

Your datapoint selections and their **Source** or **Flow target** roles define the connections shown.

## Before you begin

* You need access to Insight Analytics and permission to edit and save analytics.
* Select attributes with the **Energy** class and readings for the period you want to examine. See [Configure Attributes](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/asset-core/configure-attributes.md) for attribute settings.
* For a consumption-based diagram, use cumulative energy readings with compatible units and the same measurement meaning.
* Start with a new analytic if you want to preserve an existing selection. Changing **Analytics type** clears the selected datapoints.

## Configure the diagram

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-e4247000b10ec54f6e2a91b6fd1b714c96b28696%2Fsankey-analytic-configuration.png?alt=media" alt="Sankey analytic configuration with four Energy attributes, a named splitting node, and populated source and target flows"><figcaption><p>Fig. 1 – Example configuration using simulated Energy readings</p></figcaption></figure></div>

1. Open **Insight Analytics** **\[A]**.
2. Enable **Config mode**.
3. Select **Sankey - Simple 2 layers** in **Analytics type** **\[B]**.
4. Select the required Energy-class attributes in the asset tree **\[C]**.
5. Enter a meaningful **Name of the splitting node** **\[D]**, such as the building or distribution point the flows represent.
6. Select the period to analyze with the [Time Period picker](https://docs.buildings.ability.abb/collection/platform/insight-analytics/the-insight-analytics-interface/time-period-picker.md).
7. Select **Cusum counter** in **Function** when using cumulative meter readings, as in the example.

## Assign sources and targets

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-d4527e6d3a2092b89c8811b96b757972186940ee%2Fsankey-analytic-roles-and-percentages.png?alt=media" alt="Conversion table showing four selected meters, two Source roles, two Flow target roles, totals, and percentages"><figcaption><p>Fig. 2 – Roles, totals, and shares for the same illustrative configuration</p></figcaption></figure></div>

1. Open **Conversion** **\[F]** below the chart.
2. Select **Source** **\[G]** for each datapoint that represents an incoming flow.
3. Select **Flow target** **\[G]** for each datapoint that represents an outgoing flow.\
   ▷ The diagram connects the sources on the left to the splitting node, then connects that node to the targets on the right.

Include at least one source and one flow target with data for the selected period.

## Read the result

The colors beside the meter names identify the corresponding flows in the diagram. Use the table to distinguish meters whose chart labels show the same attribute name, such as **Energy**.

* **Total** **\[H]** shows the counter increase calculated over the selected period, not the arithmetic sum of the meter readings. The flow widths use these totals.
* **%** **\[I]** shows each datapoint's share of its own side: a source is compared with all selected sources, and a target with all selected targets. The table shows decimal percentages; chart labels round them to whole percentages.

The sources and targets each represent 100% of their own side. The splitting node's **100%** label does not mean that the source and target totals are equal. Check the selected meters, units, and data coverage when interpreting differences. The illustrated configuration uses simulated readings and does not establish a physical meter balance.

## Save and reuse the analytic

For a new, unsaved analytic:

1. Click **Save** **\[E]**.\
   ▷ The **Edit analytic** dialog opens.
2. Enter a **Name** that identifies the energy flows.
3. Click **Save** in the dialog.\
   ▷ The named analytic is saved and can be opened again from **Analytics list**.

For an already saved analytic, click **Save** after changing its configuration.

To display the saved diagram in a dashboard or smart view, use the [Analytic widget](https://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/analytic.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/insight-analytics/analytics-types/sankey-simple-2-layers.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.
