> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/semantic-model-editor/creating-a-semantic-model.md).

# Creating a semantic model

Create a semantic model to organize physical data into a multi-dimensional structure that has meaning to your business so that you can better understand the data and make informed decisions about your business based on that data. &#x20;

{% hint style="info" %}
**Note:** Only JDBC connections are supported.&#x20;
{% endhint %}

To create a semantic model for analyzing data, complete the following procedures:&#x20;

* [Create a basic semantic model](https://docs.pentaho.com/pba/semantic-model-editor/creating-a-semantic-model/create-a-basic-semantic-model.md)  &#x20;

  Create a basic semantic model with the minimum information of the model's name and physical data connection details.&#x20;
* [Create a cube in a semantic model](https://docs.pentaho.com/pba/semantic-model-editor/creating-a-semantic-model/create-a-cube-in-a-semantic-model.md)

  Create a cube with a fact table, dimensions, and measures to contain aggregated data from a semantic model’s physical connection. The fact table contains the data you want to aggregate in the cube. Dimensions describe the aggregated data so that it can be grouped for analysis. Measures quantify the data in the cube to facilitate operations for analyzing the data.
* [Create a shared dimension](https://docs.pentaho.com/pba/semantic-model-editor/creating-a-semantic-model/create-a-shared-dimension.md)

  Create a shared dimension for aggregated data that you want to use consistently across multiple cubes in the same semantic model. For example, a shared time dimension with annotations like Year, Month, and Week can be linked to several cubes, ensuring uniform time-based analysis.


---

# 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.pentaho.com/pba/semantic-model-editor/creating-a-semantic-model.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.
