> 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/copilot-assistant/use-cases.md).

# Typical Use Cases

Explore common scenarios where Copilot Assistant can be applied to streamline data analysis and decision-making.

Copilot Assistant accelerates self-service analytics while keeping governance in place. It makes advanced portfolio analysis accessible to business users, not only technical analysts.

| Scenario               | Example                                                                           |
| ---------------------- | --------------------------------------------------------------------------------- |
| Ad-hoc portfolio check | "What is the average energy consumption per building this month?"                 |
| Operational drill-down | "Which rooms on the 3rd floor of Building A are above 24°C?"                      |
| Data quality review    | "Which sensors haven't reported data in the last 7 days?"                         |
| Comparative analysis   | "Compare CO₂ levels in meeting rooms during morning and afternoon hours."         |
| Asset exploration      | "How many assets are configured in Location X, grouped by asset type?"            |
| Alarm review           | "Show me all high-priority alarms triggered in the east wing since last Tuesday." |


---

# 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/copilot-assistant/use-cases.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.