# Asset Data ## Data View The *Data View* in BuildingPro Suites offers a detailed overview of the raw data written to an *asset*. This includes, among other things, measured values, events, or **aggregated** data from sensors or devices. Unlike in graphical representations (e.g., lines or graphs), the *Data View* displays the values in a tabular form, so that the numbers are directly visible. The *Data View* is particularly useful for: * **Monitoring** the status of an *asset* with concrete measured values in **real time**. * **Tracking and checking** individual **data points precisely**. * Providing data for reports and detailed analyses. The chronological sorting of the data makes it easier to recognize time-based patterns and to identify irregularities more quickly.


[A]	Data	After opening the -> Asset Details, the data view can be opened via the "Data" tab.
[B]	Filter	Here you can select which data from which asset types you want to see.
[C]	Sorting	Here you can select whether the sub-assets should be displayed in geological or functional sorting.
[D]	Go to...	Here you can jump to the map, tickets, and analytics of the asset.
[E]	Search	Here you can search for assets, as in the asset list.
[F]	Current data	This is where the data most recently written to the asset is displayed.
[G]	Display aggregated data	To see the aggregated data, you can click on the small clock. Then the aggregated data opens on the right [H].
[H]	Aggregated data	Here you can see the aggregated data and its time periods. -> Display Aggregated Data
[I]	to the data details	To see all data sorted by date, click on the name of an asset. The chronologically sorted data view of the selected asset will then open.

## Data Details


[J]	Data filter	Allows filtering the displayed data by different categories such as "All," "Input," "Output," and "Status."
[K]	Data table	Displays the raw data of the selected asset in tabular form.
[L]	Aggregated data	Button to display aggregated data in [K].
[M]	Export	Button to export the displayed data as a CSV.
[O]	Time filter	Allows for detailed searching for data by selecting a start and end date as well as the respective time. The filters can be applied or reset.
[P]	Add new entry	Add a new data entry at the current time. -> Add a new data entry
[Q]	Bulk editing of data	Open the window to change past data to a value on a larger scale. -> Bulk editing of data
[R]	Edit individual historical data	Click on the pencil icon next to the value you want to change to manually change this data point. -> Edit individual historical data

*** ## Display Aggregated Data In BuildingPro Suites, measured values can be displayed not only as raw data but also in an **aggregated form**. Aggregations make it possible to display large amounts of data in a **clear manner and in different time intervals**. ### Activate Aggregated Data 1. Click on **\[L]** to display the **aggregated data**. ▷ The view switches from raw data to the aggregation view. 2. **Set time period**: In **\[L1]**, you can define the period for which the data should be aggregated. 3. **Select aggregation interval**: In **\[L2]**, select the time steps in which the data should be aggregated (e.g., hourly, daily, weekly). 4. **Select attribute**: In **\[L3]**, you can determine which attribute should be aggregated. 5. **Set aggregation mode**: In **\[L4]**, various **aggregation modes** are available: * Average * Sum Counter * Cumulative Counter * Minimum * Maximum ▷ You can find out more about this [-> here.](https://docs.buildings.ability.abb/collection/academy/aggregations-in-eliona) 6. **Apply settings**: Click on **\[L5]** to apply the changes. 7. **Reset settings**: If necessary, you can reset the filters with **\[L6]**. 8. **Display aggregated data**: The calculated values appear in **\[L7]** in a tabular view. Aggregated data allows for a **better overview of long-term developments** and helps to **analyze data flows efficiently**. *** ## Add New Data Entry

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 on **Add new entry** again to confirm the entry. ▷ The entry for the attribute is written to the heap with the current timestamp. ## Edit Individual Historical Data

1. **Display 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 set. {% hint style="danger" %} Pay attention to which data you are overwriting. Changes to existing data sets can be irreversible and permanently replace important information. {% endhint %} ## Bulk Editing of Data If you want to change data in large quantities, for example, because a device supplied incorrect data on a certain day, you can easily do so. With the bulk editing function, all data within a defined time period can be set to a desired value.

1. **Open bulk editing window** Click on **\[Q]** to open the **Bulk Editing of Data** window. 2. **Set time period** Enter the **from** and **to** date as well as the times to set 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 is set to the new value. ### Using Timescale for Storing Time-based Data The use of **TimescaleDB** in *Eliona* enables efficient storage and management of time-based data, especially with changing values. By storing only actually changed values, storage space is optimized without affecting the integrity of the data. **Example: Changes over time** Let's look at the data that is recorded at regular time intervals: **Original data without Timescale** Every 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 your devices write "null" values to BuildingPro Suites as data, they are filtered out and not written to the trend. {% endhint %}