> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hyperlab/model-and-simulation/designing-a-model.md).

# Designing a Model

The model is the core of the project. This is where we define the system to be simulated. There can only be one model per project.

## Steps to create a model

{% stepper %}
{% step %}

### Find the desired blocks in the library

The library contains electrical blocks and mathematical/logical blocks to design control systems. Browse the library for the desired blocks and drag-and-drop them into the model canvas.
{% endstep %}

{% step %}

### Assemble the blocks

Rearrange the blocks in the model canvas and connect them to create the desired electrical system and/or algorithm. The links between blocks have different colors depending on whether they belong to an electrical diagram or a control diagram.
{% endstep %}

{% step %}

### Configure the blocks

Double click on a block to display its parameters on the side bar. From there, parameter values can be set.
{% endstep %}
{% endstepper %}

<figure><img src="https://2712201518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbs0l9jugXixa0ghErrqs%2Fuploads%2Fzr3dU8oEl0PZjfU4qkrS%2FModel_1.png?alt=media&amp;token=409a55b1-b99e-4508-9463-97b6bad635a7" alt=""><figcaption></figcaption></figure>


---

# 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://www.opal-rt.com/docs/hyperlab/model-and-simulation/designing-a-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.
