> 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/academy/aggregationen-in-eliona.md).
# Aggregations in Eliona
Eliona offers **dynamic real-time aggregations**, which make it possible to efficiently evaluate large amounts of data. Instead of analyzing raw sensor data point by point, users can choose different aggregation methods to quickly identify relevant correlations.
***
## **What are aggregations?**
Aggregations summarize data over a certain period of time to make patterns and trends easier to see. This helps to:
* **Long-term developments** to recognize
* **irregularities or outliers** to identify more quickly
* **Reports & visualizations** to make more clear
* **Efficient calculations** to enable for large amounts of data
Users can choose the aggregation interval and method at any time to display data in the way that makes the most sense for their analysis.
***
## **Available aggregation methods**
Depending on the use case, various aggregation methods are available:
### **Average (Mean)**
**Calculation**: All values within the aggregation period are summed and divided by their number.\
**Application**: Useful for displaying **typical values** of a sensor over a certain period of time, e.g.:
* Average temperature per hour
* Average energy consumption per day
### **Sum counter (Sum Counter)**
**Calculation**: The values within a time interval are summed.\
**Application**: Useful when the total amount of a measured variable is to be determined, e.g.:
* Total water consumption per day
* Total count of people movements per hour
### **Cumulative counter (Cumulative Counter)**
**Calculation**: Continuously adds values over time and returns the accumulated value.\
**Application**: Particularly suitable for **continuously increasing values**, such as:
* **Total energy consumption** over the course of a month
* **Produced quantities** in a production line
### **Minimum (Min)**
**Calculation**: The smallest value within the selected aggregation interval is returned.\
**Application**: Helpful when determining how low a measured variable was, e.g.:
* **Lowest temperature of the day**
* **Minimum humidity during a week**
### **Maximum (Max)**
**Calculation**: The highest value within the aggregation period is returned.\
**Application**: Useful for analyzing peak values, e.g.:
* **Highest electrical load of a building per hour**
* **Maximum speed of a machine during an operating cycle**
### **Time-weighted average (Time Weighted Average / TWA)**
**Calculation:** Each measurement is weighted according to the time for which it was valid within the aggregation interval. Values that occur more frequently or persist longer influence the average more strongly than values that occur only briefly.
**Application:** Particularly useful for time series in which values change rarely or outliers should not be overemphasized, e.g.:
* Temperature trends with rare peak values
* Energy consumption with isolated load peaks
* Status measurements where the duration of a value is decisive
***
## **Flexibility in aggregation**
Users can freely decide in any view that supports aggregations:
* **Aggregation period** (minutes, hours, days, weeks, months...)
* **Aggregation method** (average, minimum, maximum, etc.)
* **Immediate update** of the calculated values without reconfiguration
This flexibility allows data to be optimally adapted to the respective analytical needs - whether for **dashboards, reports, automations, or rules**.
***
### **Where can aggregation be used?**
* [**Data view** → Structured overview of measured values](/collection/english-v14/documentation/assets/asset-daten.md#aggregierte-daten-anzeigen)
* [**Widgets in Smart View & dashboards** → Aggregated visualization of sensor data](/collection/english-v14/documentation/widgets.md)
* [**rule chains** → Use of aggregated values as a basis for decision-making](/collection/english-v14/documentation/alarme-regeln-und-eskalationen/regelketten.md)
* [**Analytics & Reports** → Selection of the desired aggregation level for detailed analyses](/collection/english-v14/documentation/analytics-and-reports.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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.buildings.ability.abb/collection/english-v14/academy/aggregationen-in-eliona.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
.png)