> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/process-analysts/process-analysis-and-simulation/process-mining/analyzing-projects/using-the-analytics-panel.md).

# Using the Analytics Panel

Access and interpret key metrics and charts that summarize performance and behavior across your dataset.

The **Analytics Panel** provides real-time, data-driven insights from your event log, supporting quick exploration of performance trends, bottlenecks, and case-level behavior without disrupting your workflow.

{% hint style="info" %}
The panel updates automatically to reflect any filters applied, ensuring that all metrics align with your current process view.
{% endhint %}

***

## Panel Layout & Behavior

* The **Analytics Panel** is expanded by default. 
  * To toggle the panel open or closed, use the **Collapse/Expand** ( <i class="fa-circle-chevron-right">:circle-chevron-right:</i> ) button located on its edge.
* It includes the following tab:
  * **Overview** — Displays active analytics

***

### Overview Tab — Key Metrics & Visualizations

The **Overview** tab presents six core insights, organized into four metric cards and two interactive charts:

<figure><img src="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FVAjx1KCy5l1WXHRFoqHD%2FIMS-V16-Apps-PM-Analytics.gif?alt=media&amp;token=da56d905-e09d-4484-9565-fbe69eb6a4f8" alt=""><figcaption></figcaption></figure>

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th>Example</th></tr></thead><tbody><tr><td align="center"><strong>Number of Cases</strong></td><td>The total <strong>number</strong> of cases in the event log and the associated time range.</td><td>A total of 200 cases were identified between January 2025 and June 2025</td></tr><tr><td align="center"><strong>Cases Displayed</strong></td><td>The <strong>percentage</strong> of total cases currently visible based on the applied filters.</td><td>Filters applied show 80% of total cases</td></tr></tbody></table>

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th></tr></thead><tbody><tr><td align="center"><strong>Average Case Duration</strong></td><td>The average amount of time cases take to complete, based on event timestamps</td></tr><tr><td align="center"><strong>Distinct Activities</strong></td><td>The total number of unique activities present in the event log.</td></tr></tbody></table>

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th></th><th></th><th>Chart Tooltip</th></tr></thead><tbody><tr><td align="center"><strong>Cases Over Time</strong></td><td>A <strong>line chart</strong> showing the number of cases started in each time period.</td><td><ul><li><strong>X-axis:</strong> Time (formatted as Month-Year)</li><li><strong>Y-axis:</strong> Number of cases per month</li></ul></td><td><p>On hover over the shaded area, a tooltip appears, indicating:</p><ul><li>Start month and year</li><li>Number of cases that started in that month</li></ul></td></tr><tr><td align="center"><strong>Activity Percentage</strong></td><td>A <strong>bar chart</strong> (inverted) visualizing how frequently the 10 most common activities appear across all cases.</td><td><ul><li><strong>X-axis:</strong> Percentage of cases</li><li><strong>Y-axis:</strong> Activity names</li></ul></td><td><p>On hover over the shaded area, a tooltip appears, indicating:</p><ul><li>Activity name</li><li>Percentage of cases containing that activity</li></ul></td></tr></tbody></table>

***


---

# 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://interfacing.gitbook.io/interfacing-help-files/process-analysts/process-analysis-and-simulation/process-mining/analyzing-projects/using-the-analytics-panel.md?ask=<question>&goal=<endgoal>
```

`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.