> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/principais-funcionalidades/modelos-semanticos.md).

# Semantic Models

Everything Power Monitor does for semantic models: refresh monitoring, inventory, schedules, quality, size and performance assessment.

**Semantic model** is Microsoft's current name for what used to be called a *dataset* in Power BI: the item that contains the tables, relationships, DAX measures and connections to the data sources. Power Monitor tracks semantic models on several fronts.

## Refresh monitoring

* **Refresh failures:** checked **every 15 minutes** for models on capacity in the monitored workspaces, with the **Dataset Refresh Failed** alert (error code and message, who triggered it, links).
* **History:** status, time and duration of each refresh in **Monitoring › Semantic Models**. Hovering over the **Failed** status shows the last attempt error and the model's recent history.
* **Investigation:** the **Investigate** item (right-click on a failed row) opens a technical dossier with an AI analysis, when the AI feature is configured.
* **Reprocessing:** administrators can place failed refreshes in the **Retry Queue**, and Power Monitor triggers the new refreshes in a controlled way.
* **Duration:** **Performance › Average Execution Time** and the optional **Execution Duration Deviation** alert.
* **Data delay:** **Monitoring › Data Freshness** checks whether the most recent date in a table is within the acceptable delay.

See [Data Refresh Failures](/en/principais-funcionalidades/falhas-de-atualizacao.md).

## Inventory and governance

In **Governance › Semantic Models**, you find the models of the monitored workspaces, with their technical and governance metadata (responsible person, business area responsible, area and criticality level), and you can **bulk edit governance metadata** (administrators). The **Model Size** and **Model Mapping** screens (in **Mapping**) complement this information.

**Governance › Operations › Schedules** shows a heat map and a timeline of refresh schedules, to identify congested time slots.

## Quality

* **Best Practices Score (BPA):** 55 rules (the Tabular Editor rule set and Microsoft guidelines) in categories such as Performance, DAX Expressions, Formatting, Metadata, Naming Conventions and Model Layout.
* **AI Score:** 23 rules that assess the model's readiness for Copilot and natural language questions (descriptions, date table, explicit measures, naming).
* **Performance › Model Cleanup:** columns, tables and measures not used by any visual or filter in the connected reports.
* **Data Dictionary** and **Data Lineage**.

## Performance Assessment (beta)

In **Performance › Performance Assessment**, an administrator requests an on-demand analysis of a model: VertiPaq structure (tables and columns), Power Query, best practices, unused columns and capacity consumption (interactive and background), with prioritized recommendations. With the organization's AI provider configured, you can also generate an **AI suggestion**.

## Import, DirectQuery and Direct Lake

| Mode                              | Refresh monitored?                              | Note                                                                                           |
| --------------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| **Import**                        | ✅ Yes                                           | Most common failures: credentials, gateway, data volume, capacity                              |
| **DirectQuery / Live Connection** | Not applicable (there is no data refresh)       | Depends on the availability of the source and the gateway                                      |
| **Direct Lake**                   | According to the refreshes recorded by Power BI | Depends on the source Delta tables being up to date; use **Data Freshness** to check the delay |

## Related pages

* [Semantic Models (Monitoring)](/en/power-monitor/monitoramento/modelos-semanticos.md)
* [Semantic Models (Governance)](/en/power-monitor/governanca/modelos-semanticos.md)
* [Best Practices Score](/en/power-monitor/qualidade-de-dados/score-de-boas-praticas-bpa.md)
* [Performance Assessment](/en/power-monitor/performance/avaliacao-de-performance.md)


---

# 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.powermonitor.com.br/en/principais-funcionalidades/modelos-semanticos.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.