> 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/english-v14/documentation/assets/asset-daten.md).

# Asset data

## Data view

The *Data view* in Eliona offers a detailed overview of the raw data written into a *asset* written raw data. This includes, among other things, measurements, events or **aggregated** data from sensors or devices. Unlike in graphical representations (e.g. lines or charts), the *Data view* displays the values in tabular form, so that the numbers are directly visible.

The *Data view* is especially useful for:

* Monitoring the status of a *Assets* using concrete measured values in **real time**.
* Individual **tracking data points precisely** and checking them.
* providing data foundations for reports and detailed analyses.

The chronological sorting of the data makes it easier to recognize time-based patterns and identify irregularities more quickly.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/UX6Xvpu2dvuF0rNkM9a1/Asset%20Daten.png" alt=""><figcaption></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="87"></th><th width="253"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Data</td><td>After opening the <a href="/collection/english-v14/documentation/assets/asset-details.md">-> asset details</a> the data view can be opened via the "Data" tab.</td></tr><tr><td><strong>[B]</strong></td><td>Filter</td><td>Here you can select which data from which <em>asset</em>-types you want to see.</td></tr><tr><td><strong>[C]</strong></td><td>Sorting</td><td>Here you can select whether the <em>subassets</em> should be displayed in geological or functional sorting.</td></tr><tr><td><strong>[D]</strong></td><td>Go to...</td><td>Here you can jump to the map, to <em>Tickets</em> and <em>Analytics</em> of the <em>Assets</em> jumped to.</td></tr><tr><td><strong>[E]</strong></td><td>Search</td><td>Here can, as in the <em>Asset list</em>, after <em>Assets</em> search.</td></tr><tr><td><strong>[F]</strong></td><td>Current data</td><td>Here the data last written into the <em>asset</em> are displayed.</td></tr><tr><td><strong>[G]</strong></td><td>Show aggregated data</td><td>To see the aggregated data, click the small clock. Then, on the right, <strong>[H]</strong> the aggregated data open.</td></tr><tr><td><strong>[H]</strong></td><td>Aggregated data</td><td>Here you can see the aggregated data and their periods. <a href="#aggregierte-daten-anzeigen">-> <strong>Show aggregated data</strong></a></td></tr><tr><td><strong>[I]</strong></td><td>to the details about the data</td><td>To see all data sorted by date, click the name of a <em>Assets</em>. Then the chronologically sorted <em>Data view</em> of the chosen <em>Assets</em> opens.</td></tr></tbody></table>

## Details about the data

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/hT3WR3DwXtYqwEqkhjQ1/Asset%20Daten%20(1).png" alt=""><figcaption></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="103"></th><th width="180"></th><th></th></tr></thead><tbody><tr><td><strong>[J]</strong></td><td>Data filter</td><td>Allows filtering the displayed data by various categories such as „All“, „Input“, „Output“ and „Status“.</td></tr><tr><td><strong>[K]</strong></td><td>Data table</td><td>Shows the raw data of the selected <em>Assets</em> in tabular form.</td></tr><tr><td><strong>[L]</strong></td><td>Aggregated data</td><td>Button for aggregated data in <strong>[K]</strong> display.</td></tr><tr><td><strong>[M]</strong></td><td>Export</td><td>Button to export the displayed data as CSV.</td></tr><tr><td><strong>[O]</strong></td><td>Time filter</td><td>Allows detailed searching of data by selecting a start and end date as well as the respective time. The filters can be applied or reset.</td></tr><tr><td><strong>[P]</strong></td><td>Add new entry</td><td>Add a new data entry at the current time. <a href="#neuen-dateneintrag-hinzufugen">-> add new data entry</a></td></tr><tr><td><strong>[Q]</strong></td><td>bulk editing of data</td><td>Open the window to change past data for a value on a larger scale. <a href="#massenbearbeitung-von-daten">-> bulk editing of data</a></td></tr><tr><td><strong>[R]</strong></td><td>Edit individual historical data</td><td>Click the pencil icon on the value you want to change to manually modify this data point. <a href="#einzelne-historische-daten-bearbeiten">-> edit individual historical data</a></td></tr></tbody></table>

***

## **Show aggregated data**

In Eliona, measured values can be displayed not only as raw data, but also in **aggregated form** displayed. Aggregations make it possible to **present large amounts of data clearly and in different time intervals** .

### **Enable aggregated data**

1. Click on **\[L]**, to display the **aggregated data** .\
   ▷ The view switches from raw data to aggregation view.
2. **Set period**: In **\[L1]** you can define for which period the data should be aggregated.
3. **Select aggregation interval**: Select in **\[L2]** which time steps the data should be aggregated in (e.g. hourly, daily, weekly).
4. **Select attribute**: In **\[L3]** you can determine which attribute should be aggregated.
5. **Set aggregation mode**: In **\[L4]** there are various **aggregation modes** available:
   * Average
   * Sum counter
   * Cumulative counter
   * Minimum
   * Maximum

     ▷ more about this can be found [-> here](/collection/english-v14/academy/aggregationen-in-eliona.md).
6. **Apply settings**: Click on **\[L5]**, to apply the changes made.
7. **Reset settings**: If necessary, you can reset the filters with **\[L6]** .
8. **Show aggregated data**: The calculated values appear in **\[L7]** in a tabular view.

Aggregated data enable a **better overview of long-term developments** and help **to analyze data flows efficiently**.

***

## Add new data entry

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/tGHs2iVsXWAbXXfiNDyV/Asset%20Daten%20(5).png" alt=""><figcaption></figcaption></figure>

1. **Add new entry**\
   Click on **Add new entry** \[P].\
   ▷ The "Add new data entry" window opens.
2. **Select attribute**\
   Select the desired **Attribute** from \[S].
3. **Enter value**\
   Enter the desired value in the corresponding field \[T].
4. **Confirm entry**\
   Click again on **Add new entry**, to confirm the entry.\
   ▷ The entry for the attribute is written to the heap with the current timestamp.

## Edit individual historical data

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/zadWFbXMlcWWsCbiP2uq/image.png" alt=""><figcaption></figcaption></figure>

1. **Show pencil icon**\
   Move the mouse over the desired data entry.\
   ▷ A pencil icon appears next to the entry.
2. **Edit data entry**\
   Click on the **Pencil icon** \[R], to edit the data entry.\
   ▷ The "Edit asset data entry" window opens.
3. **Enter new value**\
   Enter the **new value** for the entry.
4. **Save changes**\
   Click on **Save**, to apply the changes.\
   ▷ The new value replaces the old value in the data record

{% hint style="danger" %}
Make sure which data you overwrite. Changes to existing data records can be irreversible and permanently replace important information.
{% endhint %}

## bulk editing of data

If you want to change data in bulk, e.g. because a device delivered incorrect data on a certain day, you can do this easily. With the bulk editing function, all data within a defined period can be set to a desired value.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/KmcL5hq5GMSmgtGO3JCM/image.png" alt=""><figcaption></figcaption></figure>

1. **Open bulk editing window**\
   Click on **\[Q]**, to open the window **bulk editing of data** .
2. **Set period**\
   Enter the **of**- and **to**-date as well as the times, to define the period in which the data should be changed.
3. **Select attribute**\
   Select the attribute whose data you want to change.
4. **Set value**\
   Enter the new value that should replace the existing data.
5. **Save change**\
   Click on **Save**, to apply the changes.\
   ▷ All data of the selected attribute in the specified period will be set to the new value.

### Use of Timescale for storing time-based data

The use of **TimescaleDB** in *Eliona* enables efficient storage and management of time-based data, especially for changing values. By storing only values that have actually changed, storage space is optimized without compromising the integrity of the data.

**Example: Changes over time**

Let us look at the data recorded at regular intervals:

**Original data without Timescale**

Each time record contains all values, even if they have not changed:

```yaml
ts: 2024-07-24T16:20: {cop: 36, jaz: 56, power: 18.83, energy: 461.51}
ts: 2024-07-24T16:21: {cop: 50, jaz: 56, power: 18.83, energy: 461.51}
ts: 2024-07-24T16:22: {cop: 100, jaz: 56, power: 18.83, energy: 461.51}
```

**Data structure with Timescale**

With **TimescaleDB** we only store the values that have actually changed. This reduces redundant data and improves performance:

```yaml
ts: 2024-07-24T16:20: {cop: 36, jaz: 56, power: 18.83, energy: 461.51}
ts: 2024-07-24T16:21: {cop: 50}
ts: 2024-07-24T16:22: {cop: 100}
```

{% hint style="info" %}
**Good to know:**\
If "**Null**" values are written into Eliona by your devices, then these are **filtered out** and not written into the trend.
{% endhint %}


---

# 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/english-v14/documentation/assets/asset-daten.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.