> 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/analytics-and-reports.md).

# Analytics & Reports

## What are Analytics and Reports?

With Analytics and Reports, eliona offers 2 powerful tools for analyzing and visualizing data. Both tools are essential for intelligently using existing infrastructure data, optimizing processes, and saving costs.

## How do Analytics and Reports differ?

### Analytics

Analytics are used for the graphical visualization of information. With Eliona's extensive library, you can create meaningful, professional data visualizations and graphs in no time — with interactive elements if desired.

### Reports

Reports are a list of data. You can define in detail which data is listed for which assets and even integrate existing Analytics. You can automate the creation of Reports: At times you define and based on preset criteria, eliona then automatically generates reports. Eliona can also send these reports independently by email to stakeholders you specify.


---

# 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/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.