> 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/german-14.2-freezed/dokumentation/analytics-and-reports.md).

# Analytics & Reports

## Was sind Analytics und Reports?

Mit Analytics und Reports bietet eliona 2 leistungsstarke Tools, um Daten auszuwerten und zu visualisieren. Beide Tools sind unverzichtbar, um vorhandene Infrastruktur-Daten intelligent zu nutzen, Prozesse zu optimieren und Kosten zu sparen.

## Wie unterscheiden sich Analytics und Reports?

### Analytics

Analytics dienen der grafischen Visualisierung von Informationen. Mit Elionas umfangreicher Bibliothek erstellen Sie im Handumdrehen aussagekräftige, professionelle Datenvisualisierungen und Graphen – auf Wunsch sogar mit interaktiven Elementen.

### Reports

Reports sind eine Auflistung von Daten. Sie können detailliert festlegen, welche Daten zu welchen Assets aufgelistet werden und sogar bestehende Analytics einbinden. Sie können die Erstellung von Reports automatisieren: Zu von Ihnen festgelegten Zeiten und anhand von vorgegebener Kriterien generiert eliona dann automatisch Berichte. Diese Berichte kann eliona, ebenfalls komplett eigenständig, per Mail an von Ihnen festgelegte Stakeholder versenden.


---

# 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/german-14.2-freezed/dokumentation/analytics-and-reports.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.
