> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/deutsch/berichte/uberblick-uber-die-operative-leistung/bericht-darstellung-und-messwerte.md).

# Bericht: Darstellung und Messwerte

### Visuelle und Maßangaben

Die vollständige Liste aller Karten und Visualisierungen auf allen sechs Registerkarten, jeweils mit den zugrunde liegenden Kennzahlen- und Quelltabellen. Nutzen Sie diese Liste, wenn Sie eine Visualisierung erstellen oder anpassen und wissen möchten, welches Feld ihr als Datenquelle dient.

| <p><br>Tab</p>     | Visual (Display Name)               | Type             | Underlying Measure(s)                 | Source Table(s)                   |
| ------------------ | ----------------------------------- | ---------------- | ------------------------------------- | --------------------------------- |
| Operations Summary | Work Items Started                  | KPI Card         | Work Items Started                    | Work Items, Date                  |
| Operations Summary | Work Items Open                     | KPI Card         | Work Items Started, Status < 5        | Work Items, Date                  |
| Operations Summary | Work Items Overdue                  | KPI Card         | Work Items Started, \_IsOverdue = 1   | Work Items, Date                  |
| Operations Summary | SLA Compliance                      | KPI Card         | SLA % On EndDate                      | Work Items, Date                  |
| Operations Summary | AHT in Hrs                          | KPI Card         | Avg Handling Time in Hrs              | Activity, Work Items, Users, Date |
| Operations Summary | Daily Active Users                  | KPI Card         | Daily Active Users                    | Activity, Date                    |
| Operations Summary | Monthly Volume — Received vs Closed | Clustered Column | Work Items Started; Closed            | Work Items, Date                  |
| Operations Summary | By Process (Top 10)                 | Donut            | Work Items Started                    | Work Items, Process, Date         |
| Operations Summary | Top 10 Agents — Throughput & AHT    | Table            | Closed; AHT; SLA %                    | Work Items, Activity, Users, Date |
| Volume & Workload  | Work Items On Target                | KPI Card         | Started, \_IsOverdue = 0, Status < 5  | Work Items, Date                  |
| Volume & Workload  | Work Items Closed                   | KPI Card         | Work Items Closed                     | Work Items, Date                  |
| Volume & Workload  | Daily Volume Trend                  | Line             | Work Items Started; Closed            | Work Items, Date                  |
| Volume & Workload  | Status Breakdown By Customer        | 100% Stacked Bar | Work Items Started by Status          | Work Items, Date                  |
| Volume & Workload  | Ageing Distribution                 | Clustered Column | Work Items Started by Ageing Category | Work Items, Date                  |
| Volume & Workload  | Queue Wise Count                    | Bar              | Work Items Started by Queue           | Work Items, Queues, Date          |
|                    |                                     |                  |                                       |                                   |

<br>


---

# 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.enate.net/enate-help/deutsch/berichte/uberblick-uber-die-operative-leistung/bericht-darstellung-und-messwerte.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.
