> 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/hypersim/model-and-simulation/create-oem-controller-code/customize-user-interface-of-controller-blocks.md).

# Customize the User Interface of Controller Blocks

HYPERSIM allows custom graphical interfaces (Forms) to be created for CIGRÉ, UCM and Simulink-based controller blocks. These Forms simplify parameter configuration through intuitive controls such as drop-down lists, sliders, and check boxes. They also support dynamic field visibility and parameter validation, improving usability and reducing configuration errors.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-360b2fb8a6510c1c20845ef04edec8a16e1b3af3%2Foem-customisation-bloc.jpg?alt=media" alt=""><figcaption></figcaption></figure>

Additionally, to provide a cleaner, high-level user interface and hide implementation details, the controller block can be encapsulated within a [**Subsystem**](https://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/create-manage-subcircuits.md). In this configuration, the custom Form is associated with the top-level Subsystem rather than the underlying UCM. This approach is particularly useful for model abstraction, improved documentation, and the distribution of protected models to external users.

HYPERSIM also supports advanced interface customization through the [**built-in Form Editor**](https://www.opal-rt.com/docs/hypersim/model-and-simulation/edit-a-model-schematic/create-manage-subcircuits/block-form-editor.md). Using the Rules tab, developers can define logical expressions and scripting rules to dynamically calculate parameter values, control field visibility, and adapt the interface based on user selections. These capabilities improve usability, simplify configuration, and help reduce input errors.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-42c83e8f926e41d7a83c4e4497965365bedb001e%2Foem-customisation-bloc-rules.jpg?alt=media" alt=""><figcaption></figcaption></figure>

These customization options allow you to design professional-grade parameter editors tailored to your workflow and team, enhancing clarity, reducing risk, and streamlining simulation setup.


---

# 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/hypersim/model-and-simulation/create-oem-controller-code/customize-user-interface-of-controller-blocks.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.
